Sep 22 2016

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-17500 to ORA-18000

Category: Errors and SolutionsFatih Acar @ 21:24

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-17500 to ORA-18000

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 was marked with an error because the I/O error simulation event was turned on.

Action: n/a

ORA-17507: I/O request size string is not a multiple of logical block size.

Cause: I/O’s were done in a multiple of the logical block size.

Action: Check additional error messages.

ORA-17508: I/O request buffer pointer is not aligned.

Cause: I/O request buffer was not aligned. Check additional information for a buffer pointer value.

Action: Contact Oracle Support Services.

ORA-17509: An 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 contact Oracle Support Services.

ORA-17510: An attempt to do I/O of size string to block string is beyond file size string. Logical block size: string.

Cause: The I/O request pointed to a block beyond the end of the file.

Action: Check additional error messages and contact 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 Direct NFS (dNFS) package in a non-dNFS environment.

Action: Ensure that 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 data file in a CloneDB environment failed.

Action: Ensure that 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: Ensure that 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: Ensure that 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: Ensure that 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: Reason(string): data file string cannot be prepared

Cause: The snapshot layer could not prepare the specified data file.

Action: Ensure that the file does not already exist, is already part of a clone setup, or is being repopulated by an Instant Restore background process. Ensure that the path specified is accessible 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: Ensure that Instant Restore initialization parameters are set as required for this feature.

ORA-17522: file string is already being repopulated

Cause: The file was already being repopulated from a previous restore.

Action: Ensure that the file completes restore before you start another restore.

ORA-17523: Instance number cannot spawn repopulation (RPOP) process

Cause: The instance had too many running processes.

Action: Ensure that the maxmimum number of processes initialization parameter is set properly for this feature.

ORA-17524: Repopulation cannot take place – no RPOP processes

Cause: The maxmimum processes initialization parameter was not set properly.

Action: Ensure that the maxmimum number of processes initialization parameter is set properly for this feature. Check the alert log for other related errors.

ORA-17525: Database clone using storage snapshot not supported on file string

Cause: Cloning a database using storage level snapshot is not supported on the underlying storage.

Action: Use storage product that has snapshot based cloning support for Oracle.

ORA-17526: Block size of file string is too small string. Must be >= string.

Cause: Files with block sizes smaller than a minimum size cannot be used for clones backed by snapshot file.

Action: Use files with larger block size.

ORA-17527: Creation of a snapshot failed because the destination string was not a sparse disk group.

Cause: Creating a snapshot failed because the destination disk group was not a sparse disk group.

Action: Ensure that the CREATE_FILE_DEST clause passed to the snapshot copy is in a sparse disk group.

ORA-17528: A read-only file or a file opened read-only cannot be written to: string.

Cause: The file was read-only or was opened read-only and an attempt was made to write to the file, or there was an internal error.

Action: If the file is a parent of a snapshot, then you cannot open read/write, drop or unplug the database. Otherwise, look at the trace file and contact Oracle Support Services.

ORA-17529: creation of compressed file failed

Cause: An attempt was made to create a compressed file on an instance that was not a CloneDB instance.

Action: Set CLONEDB parameter to TRUE and retry the operation.

ORA-17530: snapshot (parent), string, modified after clone (child) created, string

Cause: The snapshot referred to by the clone was incompatible with what the clone was created.

Action: Locate the appropriate snapshot and place it in the named location.

ORA-17531: snapshot (parent)=string modification time string is different from snapshot creation time string recorded in file string

Cause: The clone (child) referred to a snapshot at a specific point in time. The snapshot (parent) currently in that place is at the wrong time.

Action: Locate the appropriate snapshot (parent) and place it in the named location.

ORA-17532: snapshot (parent)=string checkpoint SCN string is different from snapshot checkpoint SCN string recorded in file string

Cause: The clone (child) referred to an SCN at a specific point in time. The snapshot (parent) currently in that place is at the wrong SCN.

Action: Locate the appropriate snapshot (parent) and place it in the named location.

ORA-17533: sparse merge copy operation failure because string and string do not share a valid relationship

Cause: Files specified with the ‘sparse_merge_begin’ and ‘sparse_merge_end’ options did not share a valid relationship.

Action: Check additional error messages.

ORA-17534: sparse merge copy operation failure because request to change file access permissions for string failed

Cause: File access permissions for the file could not be modified.

Action: Check additional error messages.

ORA-17535: sparse merge copy operation failure because it tried to merge to the base parent string

Cause: The sparse merge copy operation was not successful because it tried to merge to the base parent.

Action: Check additional error messages.

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: Initialization of the Oracle Disk Manager (ODM) for the thread failed due to insufficient privilege or memory.

Action: Ensure that there is enough system resources available for the Oracle process and that 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 Oracle Disk Manager (ODM) library returned an error while trying to register the network adapter.

Action: Ensure that the network adapter name specified in the FILEIO_NETWORK_ADAPTERS initialization parameter 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-17634: network file transfer operation aborted

Cause: An error occurred during network file transfer operation.

Action: Check addtional error messages.

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.

ORA-17636: Invalid sparse block format (string). Start block=string. Error=string. File=string

Cause: An error occurred while reading the block on sparse media.

Action: Contact Oracle Support Services.

ORA-17637: failed to change permission on file ‘string

Cause: An error occurred while changing permission on a database file.

Action: Verify that Oracle user has ownership on the database file.

ORA-17638: Error in accessing a compressed file string. ‘string‘.

Cause: An error occurred while accessing a compressed file.

Action: Verify that the Oracle user has permission to access the compressed file.

ORA-17639: Snapshot backing file not read-only ‘string‘.

Cause: An error occurred while opening the snapshot backing file.

Action: Verify that the backing file has not changed since the creation of the snapshot file and set the backing file permissions to read-only.

ORA-17640: SQL statement execution failed

Cause: The remote SQL statement execution failed on primary database.

Action: Check for the required privileges to run the SQL statement.

ORA-17675: execution of OFS procedure failed with error:’string

Cause: Either the procedure was called on a platform where Oracle File System (OFS) is not supported or an invalid file system type was provided.

Action: Check additional error messages in the trace file.

ORA-17676: Failed to mount ‘string‘ with error:’string

Cause: Mounting database file system failed with an error.

Action: Check additional error messages in the trace file.

ORA-17677: failed to unmount ‘string‘ with error:’string

Cause: Unmounting database file system failed with an error.

Action: Check additional error messages in the trace file.

ORA-17678: failed to mount ‘string‘ with error:’string

Cause: Mounting of the database file system failed with an error.

Action: Check additional error messages in the trace file.

ORA-17679: failed to makefs ‘string‘ with error:’string

Cause: Either an invalid file system creation option was specified, the file system already existed, or a failure to create the tables occurred.

Action: Check additional error messages in the trace file.

ORA-17680: failed to destroy database file system ‘string‘ with error:’string

Cause: Either the database file system was invalid, it was still busy, it did not exist, or some other error has occurred.

Action: Check additional error messages in the trace file.

ORA-17681: cannot connect to the remote database server

Cause: An attempt was made to connect to the remote server using a shared server connection. This is not supported.

Action: Verify the connect string and use a dedicated server to connect to remote database.

ORA-18000: invalid outline name

Cause: The parser detected a missing or invalid outline name

Action: n/a

5,725 total views, 15 views today

Tags: Oracle Error Solutions

facebook comments:

Leave a Reply

Time limit is exhausted. Please reload CAPTCHA.