Oracle 12c R2 Error Codes and Solution Suggestions from ORA-03700 to ORA-04000
- ORA-03700: More than one shardspace not allowed with system-managed sharding.
Cause: An attempt to add a shardspace to the catalog was attempted when a shardspace already existed.
Action: Only one shardspace is allowed per system-managed catalog. Use the existing shardspace or re-create the catalog with a different sharding type.
Cause: Mutually exclusive parameters were specified in a command.
Action: Verify the parameters and retry command.
Cause: A reserved word was used as the name of an object.
Action: Verify the parameters and retry command.
Cause: A command was issued which required a sharded database pool, but none existed.
Action: Add a sharded database pool and retry the command.
Cause: A command was issued which required a sharded database pool, but more than one existed.
Action: Remove a sharded database pool and retry the command.
Cause: A command was issued without specifying a shardgroup and a default shardgroup could not be determined.
Action: Do not omit ‘-shardgroup’ when multiple shardgroups exist.
Cause: A command was issued without specifying a shardspace and a default shardspace could not be determined.
Action: Do not omit ‘-shardspace’ when multiple shardspaces exist.
Cause: An environment variable required for the operation was not set at the specified destination.
Action: Provide a value for the variable and retry operation.
Cause: The requested shard did not exist.
Action: Check the name and try again.
Cause: The input file contained a parameter that was too long.
Action: Confirm the file contents and parameter being used and retry the operation.
Cause: A directory required for successful operation did not exist or was not writeable at the destination.
Action: Confirm that the directory exists and that permissions allow for the creation of files.
Cause: A shard with the same database identifier was a member of a shardgroup in another shardspace.
Action: All shards with the same database identifier must be members of the same shardgroup. Specify a different shardroup and retry the operation.
Cause: A shard with the same database identifier was a member of the specified shardgroup.
Action: All shards in a shardgroup must have unique database identifiers. Specify a different shardroup and retry the operation.
Cause: A shard that contained chunks was removed from the catalog. Those chunks are no longer available.
Action: This is an informational message only.
Cause: The chunk recovery procedure was not able to automatically recover corrupted chunks.
Action: Examine the trace files and manually fix the problems by altering shard tablespaces.
Cause: The specified user did not exist on this shard.
Action: Ensure that the shard DDL is up to date and re-try.
Cause: The statement was too long.
Action: Reduce the size of the statement to 3800 bytes or less.
Cause: A nonexistent shard was provided for execution.
Action: Ensure that the shard exists and try again.
- ORA-03718: Service management is not available at this time because broker configuration string does not have a registered primary database.
Cause: The primary database was not registered. Service management requires registration of all primary databases.
Action: Wait for new primary database to be registered and try again.
Cause: The specified shard character set did not match the catalog character set.
Action: Ensure that the character sets match and try again.
Cause: The specified shard national character set did not match the catalog national character set.
Action: Ensure that the national character sets match and try again.
Cause: The specified database was not in the sharded schema.
Action: Ensure that the name is correct and try again.
Cause: The specified chunk move could not be suspended.
Action: Either the move has already started or is no longer in the the queue. Check the status and try again.
Cause: The specified chunk could not be removed from the queue.
Action: Either the move has already started or is no longer in the queue. Check the status and try again.
Cause: The specified database was not configured to be a catalog.
Action: Specify a valid catalog database and retry the operation.
Cause: Unable to successfully complete shard deployment.
Action: Check error returned and retry the operation.
Cause: Unable to retrieve default Oracle Database Configuration Assistant (DBCA) template from shard.
Action: Verify that General_Purpose.dbc exists on shard and retry the operation. Alternately, explicity provide a template via ‘create shard’ command options.
Cause: Chunk migration pre-check failed because one of the transporting tablespaces was either read-only or in hot backup mode.
Action: Alter the tablespace to fulfill chunk migration requirements.
Cause: An attempt was made to create a service in a sharded pool that specified preferred and available databases.
Action: Use only preferred_all option for sharded services.
Cause: The requested operation required one or more involved shards to be up-to-date with the DDL state of the sharded system.
Action: Recover shards, which are in DDL Error state, wait for DDL execution to finish on every shard, then retry executing the operation.
Cause: The master global service manager was no longer connected to the catalog.
Action: Restart the global service manager and retry operation.
Cause: The GSMUSER account was not granted SYSDG and SYSBACKUP privileges.
Action: Grant the necessary privileges and retry the operation.
Cause: New shardspaces could not be added because a root table already existed in the sharded database.
Action: Drop the root table and retry operation.
Cause: A previous request for deploy operation was still in progress.
Action: Wait for the previous deploy operation to complete and check if another deploy operation is required before resubmitting the request.
Cause: A database condition that prevents chunk move was detected.
Action: Refer to the following error message for additional information. Correct the error, if possible, and try the move again.
Cause: The flashback database was not enabled on the database being configured.
Action: Enable flashback database and retry the operation.
Cause: User-defined sharding was not supported on the database being configured.
Action: Use either system-managed or composite sharding.
Cause: The specified valid node check for registration (VNCR) was in use by at least one database or shard.
Action: Remove any databases or shards that use the VNCR and retry the operation.
Cause: SYS.EXEC_SHARD_PLSQL can only execute a limited set of PL/SQL procedures.
Action: Execute a procedure manually on each shard.
Cause: An attempt was made to create a shardgroup with user-defined sharding.
Action: Use either system-managed or composite sharding.
Cause: An attempt was made to create a primary shard from a standby database or a standby shard from a primary database.
Action: Validate the current database role and confirm that it matches the role of the specified shardgroup (for system-managed or composite sharding) or that it matches the -deploy_as parameter specified in the ‘add shard’ command (for user-defined sharding).
Cause: There was an incomplete split operation on the same chunk ID.
Action: Wait until the split finishes and try again.
Cause: An attempt was made to skip a system DDL request such as SPLITCHUNK.
Action: Fix the error at the shard, which cause the DDL to fail, and then recover.
Cause: There was an incomplete move operation.
Action: Wait until the move finishes and try again.
Cause: An attempt was made to set a database parameter that cannot be set using this procedure.
Action: Do not set this parameter using this procedure.
Cause: An attempt to enable affinity on non-Oracle RAC database was made
Action: Enable affinity on Oracle RAC database
Cause: The table specification was not correct.
Action: Specify a valid table name in the ALTER SYSTEM ENABLE AFFINITY statement.
Cause: The specified table was not partitioned.
Action: Enable affinity for a partitioned table.
Cause: The specified table was not partitioned by either RANGE, LIST or HASH.
Action: Enable affinity for a partitioned table.
Cause: A table affinity was already specified. Multiple table affinities are currently not supported.
Action: Disable affinity for existing table.
Cause: An attempt was made to delete a service that was already deleted.
Action: None. The previous delete request completes and the service is removed.
Cause: An attempt was made to modify a service that was already deleted.
Action: None. The previous delete request completes and the service is removed.
Cause: An attempt was made to directly alter or drop an internal database link for sharding, which is not allowed.
Action: Do not alter or drop shard internal database links.
Cause: An attempt was made to rename a shard key column or a partition set key column of a sharded table, which is not allowed.
Action: Do not rename shard key or partition set key column of a sharded table.
- ORA-03902: cannot shrink a system-managed or composite sharded table with primary key or any sharded table with functional index
Cause: An attempt was made to shrink a system-managed or composite sharded table with primary key or a sharded table with functional index, which is not allowed.
Action: Do not perform shrink such tables.
Cause: An attempt was made to use a tablespace for multiple partitions of a user-defined sharded table.
Action: Use different tablespaces for different partitions in a user-defined sharded table.
Cause: An attempt was made to specify a tablespace for LOBs that belonged to a different shardspace.
Action: Specify tablespaces that belong to the same shardspace for the partition as well as for the LOBs.
Cause: An operation failed when performed using Oracle GoldenGate.
Action: Correct the error specified in Oracle GoldenGate output.
Cause: One or more components of the Oracle GoldenGate (OGG) service descriptor could not be verified.
Action: Refer to the Oracle GoldenGate message for the required action.
Cause: Oracle GoldenGate (OGG) AdminService or DistributionService could not be reached.
Action: Refer to the HTTP message for the required action.
Cause: Oracle GoldenGate (OGG) AdminService or DistributionService operation failed.
Action: Refer to the Oracle GoldenGate message for the required action.
Cause: Internal error. An Oracle GoldenGate (OGG) sharding functionality was called in an invalid context, for example, catalog function in shard or vice versa.
Action: Contact Oracle Support Services.
- ORA-03955: Invalid combination of OGG deployment parameters specified for shardgroup: string (S=string, C=string, R=string)
Cause: The values specified for Oracle GoldenGate (OGG) deployment parameters (number of shards – S, number of chunks – C and replication factor – R) for the shardgroup were not compatible with each other.
Action: Ensure that the following invariants hold for the shardgroup: number of chunks >= number of shards number of shards >= replication factor
Cause: Internal error. The payload for Oracle GoldenGate (OGG) command sent from the sharding catalog to the shard database contained an invalid entry.
Action: Contact Oracle Support Services.
Cause: Internal error. A database initialization parameter required by the shard database was not set during deployment.
Action: Contact Oracle Support Services.
Cause: A request to remove a shard database failed.
Action: Check the shard error message for details.
Cause: Internal error. Chunk allocation algorithm for Oracle GoldenGate (OGG) detected inconsistencies in the sharding configuration.
Action: Contact Oracle Support Services.
Cause: An invalid chunk number or target shard name was provided.
Action: Check the chunk number, shard name and try again.
Cause: An invalid chunk number or source shard name was provided.
Action: Check the chunk number, shard name and try again.
Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100
Action: create the table/cluster specifying values whose sum is <= 100