ORA-00125 Connection Refused Invalid Presentation

Error Code
ORA-00125

Description
Connection refused, invalid presentation.

Cause
Possible cause of this error is, the PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

Action
To fix this error, correct the PRESENTATION specified in the TNS address.

reference

ORA-00124 DISPATCHERS Specified without MAX_SHARED_SERVERS

Error Code
ORA-00124

Description
DISPATCHERS specified without MAX_SHARED_SERVERS.

Cause
Possible cause of this error is, a definition for DISPATCHERS was specified in the initialization parameter file, but MAX_SHARED_SERVERS was specified as zero.

Action
To fix this error, specify MAX_SHARED_SERVERS to be greater than zero.

reference

ORA-00123 Idle Public Server Terminating

Error Code
ORA-00123

Description
Idle public server terminating.

Cause
Possible cause of this error is, too many idle servers were waiting on the common queue.

Action
This error is used internally, no action is required.

reference

ORA-00122 Cannot Initialize Network Configuration

Error Code
ORA-00122

Description
Cannot initialize network configuration.

Cause
Possible cause of this error is, ORACLE could not initialize SQL*Net version 2.

Action
To fix this error, check the error stack for detailed information.

reference

ORA-00121 SHARED_SERVERS Specified without DISPATCHERS

Error Code
ORA-00121

Description
SHARED_SERVERS specified without DISPATCHERS.

Cause
Possible cause of this error is, a definition for SHARED_SERVERS was specified in the initialization parameter file, but no definition for DISPATCHERS was specified. Without a value for DISPATCHERS, shared servers will never be used.

Action
To fix this error, add a definition for DISPATCHERS in the initialization parameter file (or remove the definition for SHARED_SERVERS, if shared servers are not being used).

reference

ORA-00120 Dispatching Mechanism not Enabled or Installed

Error Code
ORA-00120

Description
Dispatching mechanism not enabled or installed.

Cause
Possible cause of this error is, either the dispatching mechanism was not enabled or the Oracle executable image was not installed with the dispatching mechanism.

Action
To fix this error, refer to the >Oracle9i Database Administrator's Guide and your operating system-specific documentation for procedures for starting and configuring the dispatcher process.

reference

ORA-00119 Invalid Specification for System Parameter String

Error Code
ORA-00119

Description
Invalid specification for system parameter string.

Cause
Possible cause of this error is, the syntax for the specified parameter is incorrect.

Action
To fix this error, refer to the Oracle Reference Manual for the correct syntax.

reference

ORA-00118 Only One of PROTOCOL, ADDRESS or DESCRIPTION may be specified

Error Code
ORA-00118

Description
Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified.

Cause
Possible cause of this error is, more than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.

Action
To fix this error, use only one of the attributes:
PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.

reference

ORA-00117 PROTOCOL, ADDRESS or DESCRIPTION must be specified

Error Code
ORA-00117

Description
PROTOCOL, ADDRESS or DESCRIPTION must be specified.

Cause
Possible cause of this error is, PROTOCOL, ADDRESS or DESCRIPTION was not specified.

Action
To fix this error, use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.


reference

ORA-00097 Use of Oracle SQL feature not in SQL92 string Level

Error Code
ORA-00097
Description
Use of Oracle SQL feature not in SQL92 string Level.

Cause
Possible cause of this error is, usage of Oracle's SQL extensions.

Action
none

reference

ORA-00096 Invalid Value String for Parameter String, must be from among String

Error Code
ORA-00096

Description
Invalid value string for parameter string, must be from among string.

Cause
Possible cause of this error is, the value for the initialization parameter is invalid.

Action
To fix this error, choose a value as indicated by the message.

reference

ORA-00094 %s Requires an Integer Value

Error Code
ORA-00094

Description
%s requires an integer value.

Cause
Possible cause of this error is, the parameter value is not an integer.

Action
To fix this error, modify the parameter value to be an integer.

reference

ORA-00093 %s must be between String and String

Error Code
ORA-00093

Description
%s must be between string and string.

Cause
Possible cause of this error is, the parameter value is not in a valid range.

Action
To fix this error, modify the parameter value to be within the specified range.

reference

ORA-00092 LARGE_POOL_SIZE must be Greater than LARGE_POOL_MIN_ALLOC

Error Code
ORA-00092

Description
LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC

Cause
Possible cause of this error is, the value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.

Action
To fix this error, increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.

reference

ORA-00091 LARGE_POOL_SIZE must be at least String

Error Code
ORA-00091

Description
LARGE_POOL_SIZE must be at least string.

Cause
Possible cause of this error is, the value of LARGE_POOL_SIZE is below the minimum size.

Action
To fix this error, increase the value of LARGE_POOL_SIZE past the minimum size.

reference

ORA-00090 Failed to Allocate Memory for Cluster Database ORADEBUG Command

Error Code
ORA-00090

Description
Failed to allocate memory for cluster database ORADEBUG command.

Cause
Possible cause of this error is, could not allocate memory needed to execute cluster database oradebug.

Action
To fix this error, reissue the command on each instance with single-instance oradebug.

reference

ORA-00089 Invalid Instance Number in ORADEBUG Command

Error Code
ORA-00089

Description
Invalid instance number in ORADEBUG command.

Cause
Possible cause of this error is, an invalid instance number was specified in a cluster database ORADEBUG command.

Action
To fix this error, reissue the command with valid instance numbers.

reference

ORA-00088 Command cannot be executed by shared server

Error Code
ORA-00088

Description
Command cannot be executed by shared server.

Cause
Possible cause of this error is, debug command issued on shared server.

Action
To fix this error, reissue the command using a dedicated server.

reference

ORA-00087 Command cannot be executed on remote instance

Error Code
ORA-00087

Description
Command cannot be executed on remote instance.

Cause
Possible cause of this error is, cluster database command issued for non cluster database ORADEBUG command.

Action
To fix this error, issue the command without the cluster database syntax.

reference

ORA-00086 User call does not exist

Error Code
ORA-00086

Description
User call does not exist

Cause
Possible cause of this error is, an invalid attempt was made to dump the user call heap.

Action
To fix this error, wait until the process starts a call.

reference

ORA-00085 Current call does not exist

Error Code
ORA-00085

Description
Current call does not exist

Cause
Possible cause of this error is, an invalid attempt was made to dump the current call heap.

Action
To fix this error, wait until the process starts a call.

reference

ORA-00084 Global area must be PGA, SGA, or UGA

Error Code
ORA-00084

Description
Global area must be PGA, SGA, or UGA

Cause
Possible cause of this error is, an attempt was made to dump an invalid global area.

Action
To fix this error, specify either PGA, SGA, or UGA.

reference

ORA-00083 Possibly corrupt SGA mapped

Error Code
ORA-00083

Error Description
warning: possibly corrupt SGA mapped

Cause
Possible cause of this error is, even though there may be SGA corruptions, the SGA was mapped.

Action
To fix this error, use the DUMPSGA command to dump the SGA.

reference

ORA-00082 Memory size of string is not in valid set

Error Code
ORA-00082

Description
memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring.

Cause
Possible cause of this error is, an invalid length was specified for the POKE command.

Action
To fix this error, use a valid length (either 1, 2, 4, or possibly 8).

reference

ORA-00081 Address range [string, string) is not readable

Error Code
ORA-00081

Description
address range [string, string) is not readable.

Cause
Possible cause of this error is, an attempt was made to read/write an invalid memory address range.

Action
To fix this error, try another address or length.

reference

ORA-00080 Invalid global area specified by level string

Error Code
ORA-00080

Description
Invalid global area specified by level string

Cause
Possible cause of this error is an attempt was made to dump an invalid global area.

Action
To fix this error, use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use <extra + level> to dump global area <level> as well as <extra> bytes for every pointer; <extra> must be a multiple of 4.

reference

ORA-00079 Variable string not found

Error Code
ORA-00079

Description
Variable string not found

Cause
Possible cause of this error is, an attempt was made to dump a variable that does not exist.

Action
To fix this error, use a valid variable name.

reference

ORA-00078 Cannot dump variables by name

Error Code
ORA-00078

Description
Cannot dump variables by name

Cause
Possible cause of this error is, an attempt was made to dump a variable by name on a system that does not support this feature.

Action
To fix this error, try the PEEK command.

reference

ORA-00077 Dump string is not valid

Error Code
ORA-00077

Description
Dump string is not valid

Cause
Possible cause of this error is, an attempt was made to invoke an invalid dump.

Action
To fix this error, try another dump.

reference

ORA-00076 Dump string not found

Error Code
ORA-00076

Description
Dump string not found

Cause
Possible cause of this error is, an attempt was made to invoke a dump that does not exist.

Action
To fix this error, type DUMPLIST to see the list of available dumps.

reference

ORA-00075 Process string not found in this instance

Error Code
ORA-00075

Description
Process "string" not found in this instance

Cause
Possible cause of this error is, the specified process was not logged on to the current instance.

Action
To fix this error, specify a valid process.

reference

ORA-00074 No process has been specified

Error Code
ORA-00074

Description
No process has been specified

Cause
Possible cause of this error is, no debug process has been specified.

Action
To fix this error, specify a valid process.

reference

ORA-00073 command string takes between string and string arguments

Error Code
ORA-00073

Description
command string takes between string and string argument(s).

Cause
Possible cause of this error is, an incorrect number of arguments was specified.

Action
To fix this error, specify the correct number of arguments. Type HELP to see the list of commands and their syntax.

reference

ORA-00072 process string is not active

Error Code
ORA-00072

Description
process string is not active

Cause
Possible cause of this error is, an invalid process was specified.

Action
To fix this error, specify a valid process.

reference

ORA-00071 process number must be between 1 and string

Error Code
ORA-00071

Description
process number must be between 1 and string

Cause
Possible cause of this error is, an invalid process number was specified.

Action
To fix this error, specify a valid process number.

reference

ORA-00070 command string is not valid

Error Code
ORA-00070

Description
command string is not valid

Cause
Possible cause of this error is, an invalid debugger command was specified.

Action
To fix this error, type HELP to see the list of available commands.

reference

ORA-00069 cannot acquire lock -- table locks disabled for string

Error Code
ORA-00069

Description
cannot acquire lock -- table locks disabled for string

Cause
Possible cause of this error is, 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
To fix this error, use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command.

reference

ORA-00068 invalid value string for parameter string, must be between string and string

Error Code
ORA-00068

Description
invalid value string for parameter string, must be between string and string

Cause
Possible cause of this error is, the value for the initialization parameter is invalid.

Action
To fix this error, choose a value as indicated by the message.

reference

ORA-00067 invalid value string for parameter string; must be at least string

Error Code
ORA-00067

Description
invalid value string for parameter string; must be at least string

Cause
Possible cause of this error is, the value for the initialization parameter is invalid.

Action
To fix this error, choose a value as indicated by the message.

reference

ORA-00066 LOG_FILES is string but needs to be string to be compatible

Error Code
ORA-00066

Description
LOG_FILES is string but needs to be string to be compatible

Cause
Possible cause of this error is, the maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.

Action
To fix this error, change the value of the LOG_FILES initialization parameter to be compatible.

reference

ORA-00065 initialization of FIXED_DATE failed

Error Code
ORA-00065

Description
initialization of FIXED_DATE failed

Cause
Possible cause of this error is, the FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.

Action
To fix this error, make sure the initialization parameter is in the correct date format.

reference

ORA-00064 object is too large to allocate on this O/S (string,string)

Error Code
ORA-00064

Description
object is too large to allocate on this O/S (string,string)

Cause
Possible cause of this error is, an initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.

Action
To fix this error, reduce the value of the initialization parameter.

reference

ORA-00063 maximum number of log files exceeded string

Error Code
ORA-00063

Description
maximum number of log files exceeded string

Cause
Possible cause of this error is, the number of log files specificied exceeded the maximum number of log files supported in this release.

Action
To fix this error, re-create the control file with the highest number of log files no greater than the maximum supported in this release.

reference

ORA-00062 DML full-table lock cannot be acquired; DML_LOCKS is 0

Error Code
ORA-00062

Description
DML full-table lock cannot be acquired; DML_LOCKS is 0

Cause
Possible cause of this error is, the instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).

Action
To fix this error, restart the instance with DML_LOCKS not equal to zero, and reexecute the statement.

reference

ORA-00061 another instance has a different DML_LOCKS setting

Error Code
ORA-00061

Description
another instance has a different DML_LOCKS setting

Cause
Possible cause of this error is, the shared instance being started is using DML locks, and the running instances are not, or vice-versa.

Action
To fix this error, ensure that all instances' INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.

reference

ORA-00060 deadlock detected while waiting for resource

Error Code
ORA-00060

Description
deadlock detected while waiting for resource

Cause
Possible cause of this error is, when transactions deadlocked one another while waiting for resources.

Action
To fix this error, look at the trace file to see the transactions and resources involved. Retry if necessary.

reference

ORA-00059 maximum number of DB_FILES exceeded

Error Code
ORA-00059

Description
maximum number of DB_FILES exceeded

Cause
Possible cause of this error is, the value of the DB_FILES initialization parameter was exceeded.

Action
To fix this error, increase the value of the DB_FILES parameter and warm start.


reference

ORA-00058 DB_BLOCK_SIZE must be string to mount this database (not string)

Error Code

ORA-00058

Description

DB_BLOCK_SIZE must be string to mount this database (not string)

Cause

Possible cause of this error is, DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.

Action

To solve this error, fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

reference

ORA-00057 maximum number of temporary table locks exceeded

Error Code
ORA-00057

Description
maximum number of temporary table locks exceeded

Cause
Possible cause of this error is when 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.


reference

ORA-00056 DDL lock on object 'string.string' is already held in an incompatible mode

Error Code
ORA-00056 

Description
DDL lock on object 'string.string' is already held in an incompatible mode

Cause
A possible cause of this error is that 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.


reference