Oracle 12c R2 Error Codes and Solution Suggestions from ORA-02500 to ORA-02600
- ORA-02500: IN SHARD option already specified
Cause: In the CREATE TABLESPACE, the IN SHARD option was specified more than once.
Action: Remove all but one of the IN SHARD options.
Cause: An invalid option IN SHARD was specified for the CREATE TABLESPACE SET statement.
Action: Remove the invalid option.
Cause: An attempt to specify the TEMPLATE option without the CREATE TABLESPACE SET statement failed.
Action: Specify the USING TEMPLATE option in the CREATE TABLESPACE SET statement.
Cause: In the CREATE TABLESPACE SET, the USING TEMPLATE option was specified more than once.
Action: Remove all but one of the USING TEMPLATE options.
Cause: A nonexistent SHARDSPACE was specified in the CREATE TABLESPACE or CREATE TABLESPACE SET statement.
Action: Reissue the CREATE TABLESPACE or CREATE TABLESPACE SET statement with valid SHARDSPACE name.
Cause: In the CREATE TABLESPACE SET, the IN SHARDSPACE option was specified more than once.
Action: Remove all but one of the IN SHARDSPACE options.
Cause: The SHARDSPACE option was not specified in the CREATE TABLESPACE SET statement.
Action: Correct the syntax. Insert the missing keyword where required and then retry the statement.
Cause: The SHARDSPACE keyword was omitted in the IN SHARDSPACE option.
Action: Correct the syntax. Insert the keyword SHARDSPACE where required and then retry the statement.
Cause: An attempt was made to create a shard tablespace in a non-shard database.
Action: Deploy the sharding environment before creating a shard tablespace.
Cause: An attempt was made to define multiple PARTITIONSETS in the SHARDSPACE.
Action: Specify the different PARTITIONSETS in different SHARDSPACES.
Cause: An attempt was made to reference a tablespace set at the table level.
Action: Remove the reference to the tablespace set at the table level.
Cause: An attempt was made to run a shard DDL on a nondeployed shard or with the shard DDL option disabled.
Action: Deploy the shards or enable shard DDL before executing the DDL.
Cause: The CREATE TABLE statement contained more than one PARTITIONSET option.
Action: Specify PARTITIONSET option at most once in the CREATE SHARDED TABLE statement.
Cause: An invalid PARTITIONSET method was specified in the CREATE TABLE statement. A table may be partitioned by RANGE or LIST.
Action: Modify PARTITIONSET method to RANGE or LIST in the CREATE SHARDED TABLE statement.
Cause: The number of columns in a PARTITIONSET column list exceeded the legal limit of one for list partitioned tables.
Action: Modify PARTITIONSET column list so that it consists of at most one column.
Cause: Interval PARTITIONSET was not supported for a sharded table.
Action: Use a LIST or RANGE PARTITIONSET instead.
Cause: Only tables can have the SHARDED type.
Action: Remove the SHARDED option.
Cause: definition of a table with both PARTITIONSET and CLUSTER clauses which is illegal.
Action: Remove the PARTITIONSET or the CLUSTER clause.
Cause: definition of a non sharded table with PARTITIONSET clause is illegal.
Action: remove the PARTITIONSET clause.
Cause: All shards where this chunk is stored were unavailable.
Action: Rerun the command when the shards become avalaible.
Cause: All shards where this chunk is stored were unavailable.
Action: Rerun the command when the shards become available.
Cause: An attempt was made to enable shard DDL in a non-shard database.
Action: Deploy the sharding environment before enabling shard DDL.
Cause: An attempt was made to get a new range of data object numbers which resulted in a failure.
Action: Check that the shard can connect to the catalog.
Cause: PARENT clause was specified on a non-sharded table.
Action: Create a SHARDED table or remove the PARENT clause.
Cause: The parent table specified was not a valid identifier.
Action: Check that the parent table specified is valid.
Cause: The child and parent tables did not have the same owner.
Action: Check the owner of the child table.
Cause: The child and parent tables did not have the same sharding method.
Action: Ensure the sharding method for the two tables is the same.
Cause: The child and parent tables did not have the same shard key columns.
Action: Ensure the shard key for the two tables is the same.
Cause: The child and parent tables did not have the same partition set key columns.
Action: Ensure the partition set key for the two tables is the same.
Cause: The table name specified was not the one of the root table.
Action: Check the root table name specified.
Cause: An attempt was made to create a child table without specifying the PARENT clause.
Action: Specify the PARENT clause in the CREATE SHARDED TABLE command.
Cause: An attempt was made to create a sharded table on a non-sharded database.
Action: Ensure that the sharded database was deployed correctly.
Cause: An attempt was made to create a primary key constaint on non-sharding columns.
Action: Use the sharding columns as a prefix of key columns of a UNIQUE index.
Cause: The PARTITION clause was expected but was not supplied.
Action: Add a PARTITION clause to the CREATE SHARDED TABLE command.
Cause: The PARTITION clause was supplied with CONSISTENT HASH sharding.
Action: Remove the PARTITION specification.
Cause: The TABLESPACE SET clause was expected but was not supplied.
Action: Add the TABLESPACE SET clause to the CREATE SHARDED TABLE command.
Cause: The TABLESPACE SET supplied did not exist.
Action: Supply a valid TABLESPACE SET.
Cause: Data file explicit name was specified as part of the tablespace set template. Only Oracle Managed Files are supported by a tablespace set.
Action: Remove the file name from the data file definition.
Cause: The TABLESPACE SET clause was not expected.
Action: Remove the keyword SET to specify just TABLESPACE.
Cause: An attempt was made to perform an operation with shard DDL enabled, which is not supported for propagation from catalog to shards.
Action: Disable the shard DDL to perform the operation on the catalog and go to each individual shard to perform the operation locally.
Cause: An attempt was made to create a global index on a sharded table, which is not supported.
Action: Create a local index instead.
Cause: The TABLESPACE SET clause was not supplied when creating an index on a system-managed sharded table.
Action: Add the TABLESPACE SET clause to the CREATE INDEX command, or use the same tablespace set as the table by not specifying the TABLESPACE SET clause.
Cause: The partitioning method specified was not compatible with user-defined sharding.
Action: Choose a supported partitioning method.
Cause: The partitioning method specified was not compatible with system-managed or composite sharding.
Action: Choose a supported partitioning method.
Cause: Supported data types were not used for the sharding or partition set columns.
Action: Use the supported data types for sharding or partition set columns.
Cause: Virtual column was used in the sharding or partition set key, which is not supported.
Action: Remove the virtual column from the sharding or partition set key.
Cause: An invalid option was specified while creating duplicated tables.
Action: Verify the option specified.
Cause: An invalid option was specified while creating duplicated tables.
Action: Verify the option specified.
Cause: An invalid option was specified while altering duplicated tables.
Action: Verify the option specified.
Cause: An attempt was made to create an index-organized sharded table. This is not supported.
Action: Create a heap-organized table and the primary key.
Cause: Duplicated tables were created when shard DDL was disabled.
Action: Enable shard DDL.
Cause: Invalid operation was specified on a duplicated table.
Action: Use “delete from table” instead.
Cause: The shard name specified was not valid.
Action: Choose a valid shard.
Cause: The TABLESPACE clause was not supplied when specifying a partition of a user-defined sharded table.
Action: Add the TABLESPACE clause.
Cause: The DROP TABLESPACE SET command was not compatible with user-defined sharding.
Action: Choose a supported sharding method.
Cause: An attempt was made to perform online redefinition on a sharded table or a duplicated table for sharding, which is not supported.
Action: Use the ALTER TABLE statement instead.
Cause: An attempt was made to create a non-sharded, non-duplicated table across shards, which is not supported.
Action: Connect to each shard and create the table locally.
Cause: An attempt was made to operate on a sharded or a duplicated object across shards when the shard DDL was not enabled.
Action: Enable shard DDL to perform the operation.
Cause: An attempt was made to ALTER or DROP a non-sharded object when the shard DDL was enabled.
Action: Disable shard DDL to perform the operation.
Cause: The TABLESPACE SET supplied existed in a different shardspace from the one to which the table belonged.
Action: Supply a valid TABLESPACE SET in the shardspace of the table.
Cause: An attempt was made to modify partitions on system-managed or composite sharded tables.
Action: Use the ‘gdsctl split chunk’ or ‘move chunk’ commands instead.
Cause: An attempt was made to create a duplicated table with 1000 columns when there was no primary key defined. Note that unused columns in the table are counted toward the 1000 column limit.
Action: Reduce the number of columns in the command and resubmit.
Cause: An attempt was made to create a duplicated table in a non-shard schema.
Action: Try creating the duplicated table in a sharded schema.
Cause: XMLType column in a duplicated table required an automatic segment space management (ASSM) tablespace.
Action: Specify an ASSM tablespace for the XMLType column in a duplicated table.
Cause: An attempt was made to rebuild an outline with shard DDL enabled, which is not supported.
Action: Connect to each shard and rebuild the outline locally.
Cause: An individual chunk tablespace which was part of a tablespace set was used.
Action: Use a normal tablespace.
Cause: An attempt was made to create a duplicated table when the user did not have sufficient privileges.
Action: Ensure that the user has CREATE DATABASE LINK and CREATE MATERIALIZED VIEW privileges before creating a duplicated table.
Cause: An attempt was made to create a sharded table without any columns.
Action: Use valid columns to create a sharded table.
Cause: An attempt was made to create a sharded table with an identity column.
Action: Create a sharded table without an identity column.
Cause: An attempt was made to drop a system tablespace part of the sharding environment when the sharding environment was deployed.
Action: Do not drop a tablespace created by the system.
Cause: An attempt was made to alter the password for a user who created duplicated tables but did not have the privilege to execute the ALTER DATABASE LINK statement.
Action: Ensure that the user, whose password has to be changed, has the ALTER DATABASE LINK privilege and try again.
Cause: An invalid operation was specified on a duplicated table.
Action: Use DELETE FROM table_name PARTITION (partition_name) instead.
- ORA-02572: A non all-shard user cannot operate on schema objects that are sharded or duplicated on all shards.
Cause: An attempt was made to operate on a sharded or duplicated schema object by a non all-shard user.
Action: Operate on such objects as an all-shard user.
Cause: Shard DDL is not supported after a session’s current schema has been altered.
Action: Reconnect as the correct user to perform shard DDL operations.
Cause: An attempt was made to create a nested sharded table, which is not supported.
Action: Create a non-nested sharded table.
Cause: An invalid sharding method was set for a sharded database.
Action: Check the database configuration and correct the settings.
Cause: Fewer number of partition set specifications were specified than the number of shardspaces in the composite sharding environment.
Action: Specify one partition set specification for each shardspace in the composite sharding environment.
Cause: PARTITIONSETS were specified while creating a sharded table in non-composite sharding environment.
Action: Remove the PARTITION SET specifications in the create sharded table statement.
Cause: PARTITIONSET specifications were missing.
Action: Specify PARTITIONSETS for the sharded table.
Cause: An attempt was made to create a tablespace set with the SMALLFILE option.
Action: Create a tablespace set with the default BIGFILE option.
Cause: An attempt was made to add or drop a data file from a tablespace set.
Action: Do not add or drop a data file from a tablespace set.
Cause: An attempt was made to create a foreign key constraint in a sharded table on a column referencing a duplicated table.
Action: Remove the foreign key constraint referencing a column in the duplicated table.
Cause: The tablespace set name specified for the paritition set was either invalid or belonged to a different shardspace.
Action: Specify a tablespace set name that belongs to the same shardspace.
- ORA-02583: option PARALLEL not supported when creating duplicated table as select from another table
Cause: An attempt was made to create a duplicated table as select from another table in parallel mode.
Action: Create a duplicated table as select without the PARALLEL clause.
Cause: An attempt was made to create or alter a duplicated table by enabling INMEMORY options.
Action: Verify the option specified.
Cause: One of the tablespaces in the tablespace set was not created.
Action: Verify the creation of the tablespaces.
Cause: An attempt was made to change the dupl_table_refresh_rate in the non-catalog database.
Action: Connect to the catalog database to change the refresh rate of duplicated tables.
Cause: An attempt was made to create a duplicated table of object type.
Action: Create a duplicated table without specifying the object type.
Cause: An attempt was made to change the dupl_table_refresh_rate to less than 20 seconds.
Action: Set the refresh rate for duplicated tables to atleast 20 seconds.
Cause: An invalid partition set name was specified.
Action: Specify a valid partition set name.
Cause: The sequence used to specify partition sets was invalid.
Action: Specify the partition sets in an increasing order.
Cause: An attempt was made to specify a tablespace set for indexes on a sharded table in a composite sharding environment which is not supported.
Action: Create index on sharded tables without the tablespace set clause in the composite sharding environment.
Cause: An attempt was made to drop a user who owns a duplicated table when the shard database was down or the gsm_requests were pending execution.
Action: Ensure that all gsm_requests are completed and all shards are up before dropping a user with duplicated table.
- ORA-02593: cannot drop duplicated table until all shard databases are up and all gsm_requests are completed
Cause: An attempt was made to drop a duplicated table when the shard database was down or the gsm_requests were pending execution.
Action: Ensure that all gsm_requests are completed and all shards are up before dropping a duplicated table.
- ORA-02594: cannot alter shard user password until all shard databases are up and all gsm_requests are completed
Cause: An attempt was made to alter shard user password when the shard database was down or the gsm_requests were pending execution.
Action: Ensure that all gsm_requests are completed and all shards are up before altering a shard user password.
Cause: An invalid option was specified while creating duplicated tables.
Action: Verify the option specified.
Cause: An attempt was made to truncate a duplicated table on a shard database.
Action: Connect to the catalog database to truncate the duplicated table.
Cause: An invalid option was specified while creating a sharded table.
Action: Verify the specified option.
Cause: A DROP or ALTER TABLESPACE operation was attempted on a shard where the tablespace does not exist.
Action: Create the tablespace in the shard first.
Cause: An attempt was made to drop a column used as the super-partitioning key for a sharded table.
Action: This action is not allowed.
Cause: An invalid credential name was specified.
Action: Verify credential name and retry the operation.