Oracle Database Error Message Codes and Their Description from ORA-00041-ORA-00070

ORA-00041: active time limit exceeded – session terminated
Cause: The Resource Manager SWITCH_TIME limit was exceeded.
Action: Reduce the complexity of the update or query, or contact your database administrator for more information.

 


ORA-00042: Unknown Service name string
Cause: An attempt was made to use an invalid application service.
Action: Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package.

 

 

ORA-00043: remote operation failed
Cause: Execution of the inter-instance operation failed.
Action: Check the status of the target instance. The operation may have partially executed. Verify the result of the intended operation.

 

ORA-00044: timed_statistics must be TRUE when statistics_level is not BASIC
Cause: The user attempted to set timed_statistics to FALSE when statistics_level was not BASIC. timed_statistics is required to be TRUE to collect meaningful statistics when statistics_level is set to TYPICAL or ALL.
Action: Either set timed_statistics to TRUE or set statistics_level to BASIC.

 

ORA-00050: operating system error occurred while obtaining an enqueue
Cause: Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low.
Action: Look up the operating system error in your system documentation and perform the needed action.

 

ORA-00051: timeout occurred while waiting for a resource
Cause: Usually due to a dead instance.
Action: Check for any dead, unrecovered instances and recover them.

 

ORA-00052: maximum number of enqueue resources (string) exceeded
Cause: Ran out of enqueue resources.
Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.

 

ORA-00053: maximum number of enqueues exceeded
Cause: Ran out of enqueue state objects.
Action: Increase the value of the ENQUEUES initialization parameter.

 

 

 

ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired
Cause: Interested resource is busy.
Action: Retry if necessary or increase timeout.

 

ORA-00055: maximum number of DML locks exceeded
Cause: Ran out of DML lock state objects.
Action: Increase the value of the DML_LOCKS initialization parameter and warm start.

 

ORA-00056: DDL lock on object ‘string.string’ is already held in an incompatible mode
Cause: An attempt was made to acquire a DDL lock that is already locked.
Action: This happens if you attempt to drop a table that has parse locks on it.

 

ORA-00057: maximum number of temporary table locks exceeded
Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.

 

ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.
Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

 

ORA-00059: maximum number of DB_FILES exceeded
Cause: The value of the DB_FILES initialization parameter was exceeded.
Action: Increase the value of the DB_FILES parameter and warm start.

 

ORA-00060: deadlock detected while waiting for resource
Cause: Transactions deadlocked one another while waiting for resources.
Action: Look at the trace file to see the transactions and resources involved. Retry if necessary.

 

ORA-00061: another instance has a different DML_LOCKS setting
Cause: The shared instance being started is using DML locks, and the running instances are not, or vice-versa.
Action: Ensure that all instances’ INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.

 

ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0
Cause: The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).
Action: Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement.

 

ORA-00063: maximum number of log files exceeded string
Cause: The number of log files specificied exceeded the maximum number of log files supported in this release.
Action: Re-create the control file with the highest number of log files no greater than the maximum supported in this release.

 

ORA-00064: object is too large to allocate on this O/S (string,string,string)
Cause: An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.
Action: Reduce the value of the initialization parameter.

 

ORA-00065: initialization of FIXED_DATE failed
Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
Action: Make sure the initialization parameter is in the correct date format.

 

ORA-00066: SID string contains an illegal character
Cause: The specified SID contains an illegal character which cannot occur in an SPFILE setting. Illegal characters include ,#”‘=() and whitespace.
Action: Use a SID that does not contain a special character or whitespace.

 

 

ORA-00067: invalid value string for parameter string; must be at least string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.

 

ORA-00068: invalid value string for parameter string, must be between string and string
Cause: The value for the initialization parameter is invalid.
Action: Choose a value as indicated by the message.

 

ORA-00069: cannot acquire lock — table locks disabled for string
Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE … ADD (…), and so on.
Action: Use the ALTER TABLE … ENABLE TABLE LOCK command, and retry the command.

 

ORA-00070: command string is not valid
Cause: An invalid debugger command was specified.
Action: Type HELP to see the list of available commands.

 145 views last month,  9 views today

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience. I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource. I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks. I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients. If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress mehmetsalih.deveci@outlook.com. -                                                                                                                                                                                                                                                 - Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  mehmetsalih.deveci@outlook.com a mail atabilirsiniz.

Check Also

blank

ORA-01438: value larger than specified precision allowed for this column

Hi, I got ” ORA-01438: value larger than specified precision allowed for this column” error …

Leave a Reply