Oracle 11g Error Codes and Solution Suggestions from ORA-15600 to ORA-16000
- ORA-15601: Invalid value specified for parameter “string“
- Cause: An invalid value was specified for the given parameter.
- Action: Correct the value being specified for the parameter.
- ORA-15602: Parameter “string” cannot be NULL.
- Cause: An attempt was made to call a procedure without a required parameter.
- Action: Specify a valid value for this parameter.
- ORA-15603: Action cannot be performed when database is in read-only mode.
- Cause: A procedure in DBMS_AUTO_TASK_ADMIN package was invoked when database was open in read-only mode.
- Action: Retry when database is open in read/write mode.
- ORA-15604: Initialization parameters prevent client from being enabled.
- Cause: An attempt was made to enable a client that was disabled for automatic execution by an initialization parameter.
- Action: Check the related client parameters and try again.
- ORA-15605: “string” is not a Maintenance Window
- Cause: Window name passed to DBMS_AUTO_TASK_ADMIN.ENABLE procedure must be a member of the MAINTENANCE_WINDOW_GROUP.
- Action: Make the window a member of the MAINTENANCE_WINDOW_GROUP and retry the call.
- ORA-15700: SQL limit already reached by prior task execution
- Cause: An attempt was made to resume the execution of a task when the prior execution already reached the SQL limit.
- Action: Task execution is complete. Examine the report to review Advisor’s recommendations.
- ORA-15701: All “SQL Tuning Set(s)” with name like “string” and owner like “string” are empty
- Cause: An attempt was made to pack one or more SQL Tuning Sets, none
- * of which contained any statements.
- Action: Check the input and try again.
- ORA-15702: duplicate values for plan line ID in input collection
- Cause: An invalid input was provided containing duplicate values for plan line IDs causing the load of the statement to fail.
- Action: Check the input and try again.
- ORA-15703: invalid version number “number” for SQL tuning set staging table
- Cause: An invalid version number was provided for a staging table used to pack a SQL tuning set.
- Action: Check the input and try again.
- ORA-15739: invalid name “string” for SQL Performance Analyzer task
- Cause: An invalid SQL Performance Analyzer task name was used.
- Action: Check the name of the SQL Performance Analyzer task to ensure that it is correct.
- ORA-15740: parameter “string” not set for SQL Performance Analyzer task “string“
- Cause: Could not find the specified parameter name for the SQL Performance Analyzer task.
- Action: Check that the specified parameter exists for the SQL Performance Analyzer task so that the parameter is set.
- ORA-15741: no COMPARE_PERFORMANCE execution exists for SQL Performance Analyzer task “string“
- Cause: Could not find an execution of type COMPARE_PERFORMANCE for specified SQL Performance Analyzer task.
- Action: Ensure that the given SQL Performance Analyzer task has at least one execution of type COMPARE_PERFORMANCE.
- ORA-15742: specified execution name “string” is not a valid COMPARE_PERFORMANCE execution for SQL Performance Analyzer task “string“.
- Cause: The specified execution name was not a valid execution of type COMPARE_PERFORMANCE for the SQL Performance Analyzer task.
- Action: Ensure that a valid COMPARE_PERFORMANCE execution name is used for the SQL Performance Analyzer task.
- ORA-15743: need to specify the object ID if the tuning task is on a SQL set.
- Cause: There could be multiple objects in the SQL tuning task. Specify which one.
- Action: Add object ID to the interface.
- ORA-15744: The directory name is null.
- Cause: The directory name for finding the SQL traces was null.
- Action: Create the directory.
- ORA-15745: The plan type is not valid.
- Cause: The specified plan type was not valid
- Action: Check the existing plan types and specify the right one.
- ORA-15746: Missing EXECUTE privilege on DBMS_AUTO_SQLTUNE.
- Cause: The current user was missing the necessary privileges to execute the API.
- Action: Grant the privilege and try again.
- ORA-15747: The previous Oracle Data Masking job is unfinished. “string” table is not empty.
- Cause: The previously executed Oracle Data masking job was not successfully completed.
- Action: Execute Oracle Data masking cleanup.
- ORA-16000: database open for read-only access
- Cause: The database was opened for read-only access. Attempts to modify the database using DML or DDL statements generate this error.
- Action: In order to modify the database, it must first be shut down and reopened for read/write access.