Oracle 12c R2 Error Codes and Solution Suggestions from ORA-02600 to ORA-02800
- ORA-02600: credential name is invalid: string
Cause: An invalid credential name was specified.
Action: Verify credential name and retry the operation.
Cause: Credential name specified already used by an existing object.
Action: Verify credential name and retry the operation.
Cause: The specified credential does not exist.
Action: Verify credential name and retry the operation.
Cause: An invalid file name was specified.
Action: Verify credential name and retry operation.
Cause: File name specified already used by an existing object.
Action: Verify filename and retry the operation.
Cause: The specified file does not exist.
Action: Verify file name and retry the operation.
Cause: An invalid destination name was specified.
Action: Verify destination name and retry the operation.
Cause: A destination must be specified in the command.
Action: Provide destination and retry the operation.
Cause: The specified destination does not exist.
Action: Verify destination and retry the operation.
Cause: The specified remote scheduler agent cannot be contacted.
Action: Confirm that the agent is running and retry the operation.
Cause: Unable to successfully run specified job.
Action: Check errors returned and retry the operation.
Cause: An invalid shardgroup name was specified.
Action: Verify the shardgroup name and retry the operation.
Cause: The specified shardgroup did not exist.
Action: Verify the shardgroup name and retry the operation.
Cause: An invalid shardspace name was specified.
Action: Verify the shardspace name and retry the operation.
Cause: The specified shardspace did not exist.
Action: Verify the shardspace name and retry the operation.
Cause: A shardgroup or shardspace name was not specified.
Action: Update the parameters and retry the operation.
Cause: A shardgroup and a shardspace name were both specified. For this command, either a shardgroup or shardspace name may be specified, but not both.
Action: Update the parameters and retry the operation.
Cause: Either a credential or login information must be specified.
Action: Update the parameters and retry the operation.
Cause: For this command, either a credential or login information may be specified, not both.
Action: Update the parameters and retry the operation.
Cause: A file name and file contents were both specified.
Action: Update the parameters and retry the operation.
Cause: The value specified for db_domain exceeded the 128 character limit.
Action: Modify the value specified for db_domain and retry the operation.
Cause: The specified file was in use by an undeployed shard.
Action: Drop the undeployed shard and retry the operation.
Cause: The shard was not opened in the correct mode.
Action: Open the shard in write mode and retry the operation.
Cause: A request to create the broker configuration failed.
Action: Check the broker logs for details.
Cause: A request to enable the broker configuration failed.
Action: Check the broker logs for details.
Cause: A request to add the shard to the broker configuration failed.
Action: Check the broker logs for details.
Cause: A request to enable the shard for the broker configuration failed.
Action: Check the broker logs for details.
Cause: The requested shardspace did not exist.
Action: Check the name and try again.
Cause: The shardgroup name was invalid.
Action: Use a different name for the shardgroup.
Cause: The shardgroup was already deployed and could no longer be modified.
Action: Do not modify a deployed shardgroup. Delete it and add it again.
Cause: The shardgroup already contained a shard and could not be converted from a primary shard to a standby shard or from a standby shard to a primary shard.
Action: Do not modify the primary or standby status of this shardgroup.
Cause: An invalid shardspace name was provided.
Action: Check the name and try again.
Cause: The shardspace was already deployed and could no longer be modified.
Action: Do not modify deployed shardspaces.
Cause: An invalid shardpsace name was provided.
Action: Check the name and try again.
Cause: Oracle XML DB was required for remote scheduler agent configuration but was not installed.
Action: Install Oracle XML DB in the catalog database.
Cause: An invalid value of chunks was passed.
Action: Set chunks to a value greater than one.
Cause: The shard was already in a shardspace.
Action: Remove the shard from the sharding schema before adding it to another shardspace.
Cause: The source and target shards for a chunk move operation were in different shardgroups.
Action: Chunks cannot be moved across shardgroups. Specify a source and target shard that are in the same shardgroup.
Cause: The containing shardgroup for the source and target shards was not yet deployed.
Action: Chunks cannot be moved until the shardgroup has been deployed. Deploy the shardgroup before moving chunks.
Cause: The source and target shards for a chunk move were the same.
Action: Chunks cannot be moved to the same shard. Specify a different source and target.
Cause: An attempt was made to add a primary shardgroup to a shardspace that already had a primary shardgroup. When Oracle Data Guard replication is used, only one primary shardgroup is allowed in each shardspace.
Action: Do not add another primary shardgroup to this shardspace.
- ORA-02641: Shard string was not deployed because it does not contain a corresponding shard in all shardgroups.
Cause: The shard did not have a corresponding shard in all shardgroups in an Oracle Data Guard configuration, therefore it was not deployed.
Action: This is only a warning and the deployment will continue without this shard. In order to make use of this shard, either remove shardgroups, or add shards to other shardgroups so that there are the same number of shards in all shardgroups.
Cause: The ‘deploy’ command was issued, but there were no new shards to deploy.
Action: This is only a warning. Deploy may continue to recover previous deployment attempts, if any exist, but no new shards will be deployed.
Cause: A request to enable fast-start failover failed.
Action: Check the broker logs for details.
Cause: The specified rack already contained another shard in the same Oracle Data Guard configuration.
Action: Specify a different value for the rack parameter.
Cause: The specified shardspace already contained a primary shard.
Action: Specify a different shardspace or create a standby shard instead.
Cause: The Oracle GoldenGate configurations contained standby shards.
Action: Create a primary shard instead of a standby shard.
Cause: An invalid rack name was provided.
Action: Check the name and try again.
Cause: A SYS password was not specified when creating a new shard using Oracle Database Configuration Assistant (DBCA).
Action: Retry the operation and specify a SYS password.
Cause: An attempt was made to change the region value for a system-managed or composite shard.
Action: Change the region value at the shardgroup level instead.
Cause: An operation failed when performed using the remote scheduler agent.
Action: Correct the error specified in the remote scheduler agent output.
Cause: The specified pool was not sharded.
Action: Specify a sharded pool and retry the operation.
Cause: The maximum number of Global Data Services (GDS) sharded pools had been reached.
Action: No more Global Data Services (GDS) sharded pools can be added without first removing a pool.
Cause: The specified shardgroup was already in existence.
Action: Verify the shardgroup name and retry the operation.
Cause: The specified database pool already contained either a conflicting shard or shardgroup.
Action: Verify the database pool name and retry the operation.
Cause: The catalog was not enabled for sharding and a sharding command was executed.
Action: Re-create the catalog with ‘create shardcatalog’ or verify the command issued.
Cause: The specified shardspace was already in existence.
Action: Verify the shardspace name and retry the operation.
Cause: The number of chunks in the specified shardspace was less than twice the number of shards in one of its shardgroups.
Action: If the shardspace is not deployed, modify the shardspace to increase the number of chunks it contains.
Cause: The specified shardspace was already in existence.
Action: Verify the shardspace name and retry the operation.
Cause: An attempt was made to remove a shard which currently contains chunks.
Action: Move the chunks to another shard and then retry the operation.
Cause: When a shard was removed, all other shards in the same Oracle Data Guard configuration were also removed.
Action: This is an informational message only.
Cause: A command was issued that included both the shardspace and and shardgroup parameters.
Action: Remove one of the conflicting parameters from the command.
Cause: An invalid chunk number or source database was provided.
Action: Check the number and try again.
Cause: The ‘-agent_port’ parameter specified a new agent port value. The already registered scheduler agents must re-register with the catalog database to use this new value.
Action: This is only a warning. Re-register the existing scheduler agents as necessary.
Cause: The ‘-agent_port’ parameter specified a new agent port value. The port specified may already have been in use by another process in the system.
Action: This is only a warning. Confirm that there is no port conflict before continuing the operation.
Cause: A command was issued that did not include shardspace”.
Action: Specify shardspace.
Cause: An attempt was made to split a chunk before creating a tablespace set.
Action: Create a tablespace set before issuing the SPLIT command.
Cause: An attempt was made to split a chunk before creating a sharded table.
Action: Create a sharded table before issuing the SPLIT command.
Cause: One or more conditions required by Data Guard observer were not met.
Action: Confirm that Data Guard technology is used for replication, the database belongs to disaster recovery group with FSFO enabled, and there is an online primary database in that group.
Cause: An attempt was made to issue an ALTER TABLE statement to modify the data type or length of a column used to super-partition the specified sharded table.
Action: Do not modify the data type or length of a sharded table super- partitioning column or columns.
Cause: The query had a construct that was not supported for inter shard query.
Action: Rewrite the query to avoid using an unsupported construct. Consult Oracle documentation for details.
Cause: The DML was applied to more than one shard.
Action: Rewrite the DML to limit operation to a single shard.
Cause: An attempt was made to update the sharding key value using the UPDATE command.
Action: Drop and re-create the sharding key.
Cause: The aggregate, group by, semi-join, or anti-join subquery was mapped to multiple shards.
Action: Rewrite the query so that subqueries map to a single shard.
Cause: The query had illegal or no join predicate on the sharding key.
Action: Rewrite the query to include join on sharding columns.
Cause: The query had a sharded table outer joined to the replicated table.
Action: Rewrite the query to remove the outer join.
Cause: The query had a non-equality join on the sharding key.
Action: Rewrite the query to remove the non-equality join.
Cause: The query had an object defined by user-specified sharding.
Action: None
Cause: The query had an object defined under composite sharding.
Action: None
Cause: The query referenced a private and a sharded table.
Action: Rewrite the query to refer to either private tables or sharded tables, but not both.
Cause: The query referenced unsupported constructs which could not be fetched from the shard.
Action: Rewrite the query to avoid using unsupported constructs.
Cause: The statement attempts an array DML operation on a sharded table.
Action: Rewrite the array DML statement as separate DML statements.
Cause: The INSERT statement was used to insert a row in the sharded table without inserting a value for the shard column.
Action: Insert a value for the shard key column.
Cause: The schema definition on the shard and the coordinator did not match.
Action: Verify and fix the schema inconsistency between the shard and the coordinator.
Cause: A valid partition was not found for the chunk number passed to the shard database.
Action: Check the chunks handled by the shard database.
Cause: Two-task driver could not find the value of ORACLE_SID in the environment.
Action: Make sure that the ORACLE_SID environment variable has been properly set and exported.
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
Cause: ORACLE_HOME environment variable not set.
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
Cause: The pipe driver failed to create pipes for communications with the orapop process.
Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.
Cause: The two-task driver could not fork orapop.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: The pipe driver failed while polling the communications channel.
Action: Contact your customer support representative.
Cause: The length of your host-string specified by the TWO_TASK environment variable exceeds the ORACLE system-imposed limit.
Action: Contact your customer support representative.
Cause: The invoked Unix two-task driver could not allocate heap space for the context area.
Action: Contact your customer support representative.
Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied.
Action: First, check whether you have read access to oratab, and see if the desired sid is there. Add an entry to oratab for the desired sid, if necessary.
Cause: The pipe driver failed to create pipes for two-task communications with the oracle shadow process.
Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.
Cause: The pipe driver could not fork the oracle shadow process.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: The pipe driver failed to write to the orapop process.
Action: Contact your customer support representative.
Cause: The pipe driver failed to allocate enough heap space for its context area buffers.
Action: Contact your customer support representative.
Cause: The pipe driver failed to read a message from the communications channel.
Action: Contact your customer support representative.
Cause: The pipe driver failed to write a message to the communications channel.
Action: Contact your customer support representative.
Cause: The pipe driver received a message having an unrecognizable message type.
Action: Contact your customer support representative.
Cause: The Pipe driver received a message having an unrecognizable message type.
Action: Contact your customer support representative.
Cause: The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver.
Action: Contact your customer support representative.
Cause: The two-task driver could not reset the connection.
Action: Contact your customer support representative.
Cause: The fast driver could not fork the oracle shadow process.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer.
Action: Try invoking the Fast driver later, or use the default attach address.
Cause: The Fast driver failed to get a semaphore set.
Action: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and check with your system administrator.
Cause: The Pipe driver could not send a break message to orapop.
Action: Contact your customer support representative.
Cause: The Pipe driver could not send a break message to the ORACLE shadow process.
Action: Contact your customer support representative.
Cause: The Pipe driver could not send a break message to orapop.
Action: Contact your customer support representative.
Cause: The Pipe driver could not send a break message to the ORACLE shadow process.
Action: Kill system call failed. Check errno and contact customer support.
Cause: The Pipe driver could not access the oracle executable.
Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path.
Cause: The Pipe driver could not access the orapop executable.
Action: Check the permissions on the orapop executable and each component of the ORACLE_HOME/bin path.
Cause: The Fast driver could not access the oracle executable.
Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path.
Cause: The driver you have specified is not supported.
Action: Check with your database administrator which drivers are supported.
Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file.
Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your uid and home directory are correct in the /etc/passwd file.
Cause: The specified driver could not find enough heap space to malloc a buffer.
Action: Contact your customer support representative.
Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet.
Action: Create the alias in a file called .sqlnet in your home directory for personal use or ask your system administrator to create the alias in /etc/sqlnet for system-wide use.
Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the ORACLE system-imposed limit.
Action: Contact your customer support representative.
Cause: The Fast driver was unable to reset shared memory permissions.
Action: Contact your customer support representative.
Cause: The Fast driver failed to create a shared memory segment for two-task communication.
Action: Check whether the system-imposed limit on shared memory identifiers has already been reached for your system.
Cause: The Fast driver failed to establish a default shared memory address.
Action: Contact your customer support representative.
Cause: The Pipe driver failed to send orapop the command to exit.
Action: Contact your customer support representative.
Cause: The pipe driver apparently sent an imcomplete break message.
Action: Contact your customer support representative.
Cause: The alias used for a sqlnet host is longer than 161 characters.
Action: Use a shorter alias.
Cause: The Fast driver failed to create a shared memory file for two-task communication.
Action: Check the permissions on the directory ?/dbs
Cause: The Fast driver failed to map a shared memory file for two-task communication.
Action: Contact your customer support representative.
Cause: The Fast driver failed to attach shared memory at the expected location.
Action: Contact your customer support representative.
Cause: The Fast driver cannot close the shared memory file.
Action: Contact your customer support representative.
Cause: The Fast driver could not alter the inheritence attributes of the shared memory.
Action: Contact your customer support representative.
Cause: The Fast driver failed to create a file for shared memory.
Action: Check the permissions on the directory ?/dbs
Cause: The Fast driver encountered an error translating the shared memory filename ?/dbs/ftt_pid.dbf.
Action: Contact your customer support representative.
Cause: The Fast driver failed to fork a process onto the desired cluster and node number.
Action: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If these seem valid, contact customer support.
Cause: The package was unable to allocate memory for an array because the system ran out of memory.
Action: Either reclaim memory by killing other processes or reboot the machine with more memory.
Cause: All of the package’s request descriptors are in use performing other requests.
Action: Either wait until enough requests are done, or shut the package down and re-initialize it with more request descriptors.
Cause: The client was unable to close a file after forking the servers.
Action: This is a system problem – contact your System Administrator.
Cause: The file number contained with the sfiov structure is less than zero.
Action: This may be a programming error. If it is not, contact ORACLE support.
Cause: The file number contained with the sfiov structure is greater than the maximum.
Action: This may be a programming error. If it is not, contact ORACLE support.
Cause: No requests were found that could be cancelled.
Action: This error can occur if all the requests dealing with that file number have already been filled.
Cause: The mode of the package can only be parallel or duplex.
Action: See sfa.h for the correct values.
Cause: The number of servers given was less than or equal to zero.
Action: Use a number greater than zero.
Cause: The number of request descriptors was less than or equal to zero.
Action: Use a number greater than zero.
Cause: The package requires that the number of request descriptors be greater than or equal to the number of servers used.
Action: Use a higher number
Cause: The maximum number of files to be used by the package was less than or equal to zero.
Action: Use a positive number.
Cause: The package was unable to set up handling by the server for the termination signal. This is an internal error.
Action: Contact ORACLE support.
Cause: The total number of blocks to be allocated for use by the package was not greater than zero.
Action: Use a positive number.
Cause: The number was not a positive number.
Action: Use a positive number.
Cause: The time given was not a positive number.
Action: Use a positive number.
Cause: The time given was not a positive number.
Action: Use a positive number.
Cause: The time given was not a positive number.
Action: Use a positive number.
Cause: The signal number was not a positive number.
Action: Use a positive number.
Cause: The value sent to the package for use as the “request done” signal exceeds the maximum allowed by the operating system.
Action: n/a
Cause: The package was unable to get information about the directory in which the log files are to reside.
Action: Check the permissions on the directory or use a different directory name.
Cause: The name given for the directory in which the logs are to be kept does not correspond to a directory.
Action: Use a different name.
Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception.
Action: Check the permissions on the directory or use a different directory name.
Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory.
Action: Use a different name.
Cause: The value given was not TRUE or FALSE.
Action: n/a
Cause: To ensure that the functions act symmetrically, pointers to both the read and write functions must be given.
Action: Either specify both functions or specify neither. The package will supply its own functions.
Cause: To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given.
Action: Either specify both functions or specify neither. The package will supply its own functions.
Cause: The ID of the segment specified for use as the shared buffer region was invalid.
Action: Use a different ID, or let the package specify its own.
Cause: The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero.
Action: Use a positive number.
Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the “additional information” field is the size needed. The second is the size of the segment.
Action: Use a larger size segment or let the package allocate its own.
Cause: The package cannot allocate memory for an internal segment list because the system has run out of memory. The “additional information” field is the amount of memory that the package attempted to allocate.
Action: n/a
Cause: Internal error – Contact ORACLE support.
Action: n/a
Cause: The maximum number of files that can be used for asynchronous I/O has been reached.
Action: Shut down the servers and re-initialize the package with a higher number.
Cause: The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The “additional information” field is the maximum length.
Action: Use a shorter name.
Cause: The package could not open file for some reason.
Action: Check the file name.
Cause: The fstat(2) call on a file being used for asynchronous I/O failed.
Action: Check the file name.
Cause: The client was unable to close a file being used for asynchronous I/O.
Action: Contact ORACLE support – this should not happen.
Cause: The client was unable to get a key so that it obtain shared memory for use with shared memory.
Action: Contact ORACLE support – this is an internal error.
Cause: The client was signalled by a server that it was done with a request but the “done” list was empty.
Action: Internal error – contact ORACLE support.
Cause: A request is not in the right state.
Action: Internal error – contact ORACLE support.
Cause: No free request descriptors are available.
Action: Wait until some requests are filled and then retry the request, or shutdown the servers and initialize the package with a higher number of requests.
Cause: The number of operations sent to either sfard() or sfawrite() is less than zero.
Action: This is a user programming error.
Cause: The arming of a signal handler for the “done” signal failed.
Action: Internal error – contact ORACLE support.
Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time.
Action: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with sfainit(). If the server processes are dying due to unexpected signals, this is an internal error, and ORACLE support should be contacted.