Oracle 11g Error Codes and Solution Suggestions from ORA-17500 to ORA-17635
- ORA-17500: ODM err:string
- Cause: An error returned by ODM library
- Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance
- ORA-17501: logical block size string is invalid
- Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum
- Action: check INIT.ORA file parameters
- ORA-17502: ksfdcre:string Failed to create file string
- Cause: file creation failed due to either insufficient OS permission or the file already exists
- Action: check additional error messages
- ORA-17503: ksfdopn:string Failed to open file string
- Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.
- Action: check additional error messages
- ORA-17504: ksfddel:Failed to delete file string
- Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file.
- Action: check additional error messages
- ORA-17505: ksfdrsz:string Failed to resize file to size string blocks
- Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.
- Action: check additional error messages
- ORA-17506: I/O Error Simulation
- Cause: The i/o request is marked with error because the i/o error simulation event is turned on.
- Action: None
- ORA-17507: I/O request size string is not a multiple of logical block size
- Cause: i/o’s are done in multiple of logical block size
- Action: Check additional error messages
- ORA-17508: I/O request buffer ptr is not alligned
- Cause: i/o request buffer should be alligned, check additional information for buffer ptr value
- Action: Call Oracle Support Services
- ORA-17509: Attempt to do i/o beyond block1 offset
- Cause: When a file is identified with logical block size of 0, only i/o’s to block1 is allowed.
- Action: check additional error messages and call Oracle Support Services
- ORA-17510: Attempt to do i/o beyond file size
- Cause: The i/o request points to a block beyond End Of File
- Action: check additional error messages and call Oracle Support Services
- ORA-17512: Block Verification Failed
- Cause: Block Verification after a read operation on a database file failed since the block is media corrupt.
- Action: check additional error messages in the trace file and call Oracle Support Services
- ORA-17513: dNFS package call failed
- Cause: An attempt was made to call a dNFS package in a non-dNFS environment
- Action: Make sure dNFS is enabled and the file can be accessed using dNFS.
- ORA-17514: Access to clonedb bitmap file failed
- Cause: Accessing the bitmap block file in clonedb environment has encountered an error
- Action: check additional error messages in the trace file and call Oracle Support Services
- ORA-17515: Creation of clonedb failed using snapshot file string
- Cause: Creating a datafile in a clonedb environment failed.
- Action: Make sure the snapshot file passed to clonedb is not from another clonedb instance and call Oracle Support Services for further assistance
- ORA-17516: dNFS asynchronous I/O failure
- Cause: The asynchronous I/O request failed due to storage server reboot.
- Action: Make sure the storage server does not reboot repeatedly during database operations.
- ORA-17517: Database cloning using storage snapshot failed on file string:string
- Cause: An invocation of the storage clone command was returned with an error.
- Action: Make sure all necessary steps are performed for storage cloning and check the Oracle trace file for additional information.
- ORA-17518: backup file string cannot be found
- Cause: Access to the specified backup file was required for Instant Restore.
- Action: Make sure the path and file name are correct for the backup file and the path to the backup file can be accessed from the node of the instance.
- ORA-17519: string: data file string cannot be prepared
- Cause: Instant Restore could not prepare the specified data file.
- Action: Make sure the file does not already exist and is being repopulated by the Instant Restore background process. Make sure the path specified is accessable and writable by the instance.
- ORA-17520: data file string cannot be added to repopulation
- Cause: Instant Restore could not add the file to the repopulation work queue.
- Action: The repopulation process may be working on too many files for the system. Try waiting for some files to complete and try again.
- ORA-17521: Instant Restore is not enabled
- Cause: The initialization parameters for Instant Restore were not set.
- Action: Make sure Instant Restore initialization parameter is set as required for this feature.
- ORA-17522: file string is already being repopulated
- Cause: The file is currently being repopulated from a previous restore.
- Action: Make sure the file compeletes restore before you start another restore.
- ORA-17610: file ‘string‘ does not exist and no size specified
- Cause: An attempt to create a file found neither an existing file nor a size for creating the file.
- Action: Specify a size for the file.
- ORA-17611: ksfd: file ‘string‘ cannot be accessed, global open closed
- Cause: An attempt to write to a file which has gone offline/unidentified
- Action: Check for other errno in the stack
- ORA-17612: Failed to discover Oracle Disk Manager library, return value string
- Cause: Discovery of the odm library by calling odm_discover() failed
- Action: Contact your storage vendor who has provided the ODM library or call Oracle Support
- ORA-17613: Failed to initialize Oracle Disk Manager library: string
- Cause: ODM initialization for the thread failed due to insufficient previlige or memory.
- Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library
- ORA-17618: Unable to update block 0 to version 10 format
- Cause: An attempt was made to update block 0 to version 10 format.
- Action: Check additional error messages and call Oracle Support Services
- ORA-17619: max number of processes using I/O slaves in a instance reached
- Cause: An attempt was made to start large number of processes requiring I/O slaves.
- Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance.
- ORA-17620: failed to register the network adapter with Oracle Disk Manager library: string
- Cause: The ODM library returned an error while trying to register the network adapter.
- Action: Make sure the network adapter name given in the fileio_network_adapters is a valid name, and that the Oracle user has the correct access privileges.
- ORA-17621: failed to register the memory with Oracle Disk Manager library
- Cause: The ODM library returned an error while trying to register the memory.
- Action: Contact the Oracle Disk Manager Library provider.
- ORA-17622: failed to deregister the memory with Oracle Disk Manager library
- Cause: The ODM library returned an error while trying to deregister the memory.
- Action: Contact the Oracle Disk Manager Library provider
- ORA-17624: Failed to delete directory string
- Cause: The directory that was being deleted is still in use or the process had insufficient permission to delete the directory.
- Action: check additional error messages.
- ORA-17626: ksfdcre: string file exists
- Cause: trying to create a database file, but file by that name already exists
- Action: verify that name is correct, specify REUSE if necessary
- ORA-17627: string
- Cause: An error returned by OCI while sending/receiving message from remote instance
- Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance
- ORA-17628: Oracle error string returned by remote Oracle server
- Cause: Oracle server on the remote instance has returned an error.
- Action: Look at remote instance alert log/trace file for more information and take appropriate action or contact Oracle Support Services for further assistance
- ORA-17629: Cannot connect to the remote database server
- Cause: Connecting to the remote server specified by database connect string for netowrk file transfer failed.
- Action: Check additional error messages
- ORA-17630: Mismatch in the remote file protocol version client string server string
- Cause: Cannot communicate with the remote database server as there is a mismatch in the Oracle file protocol version.
- Action: Check additional error messages
- ORA-17631: dbname ‘string‘ specified by remote server does not match the instance name ‘string‘
- Cause: The dbname specified by the remote server is not intended for this instance.
- Action: Check the dbname specified in the command of the remote instance and look for further error messages.
- ORA-17632: file ‘string‘ is a formatted ASM disk
- Cause: An attempt to create a datafile on a device that was formatted for ASM disk failed.
- Action: Check that the device specified is not an ASM disk. If you would like to use the disk for datafiles, please clear the disk before you retry the operation.
- ORA-17633: Operation not supported as one of the servers involved is not capable of performing the requested operation
- Cause: An attempt was made to perform an operation involving two Oracle servers where both servers did not have the capability required for carrying out the operation. It is likely that one of the servers needs a patch or an upgrade to successfully participate in the operation.
- Action: Apply the required fix or update on the lower version server. Contact Oracle Support Services for further assistance.
- ORA-17635: failure in obtaining physical sector size for ‘string‘
- Cause: An error occurred while determining the physical sector size from the underlying storage (ASM/ODM/OSD).
- Action: Check additional error messages.