ORA-00092: LARGE_POOL_SIZE must be greater than
LARGE_POOL_MIN_ALLOC
Cause: The value of LARGE_POOL_SIZE is less than the value of
LARGE_POOL_MIN_ALLOC.
Action: Increase the value of LARGE_POOL_SIZE past the value of
LARGE_POOL_MIN_ALLOC.
Sunday, 24 April 2016
ORA-00091:
ORA-00091: LARGE_POOL_SIZE must be at least string
Cause: The value of LARGE_POOL_SIZE is below the minimum size.
Below are answers to some frequently asked questions about this error:-
1. What is ORA-00091?
- ORA-00091 is an Oracle error code that indicates a transaction has attempted to change the session's state after a transaction control statement (such as COMMIT or ROLLBACK) has been issued and before the transaction has been completed.
2. What causes ORA-00091?
- This error typically occurs when a session tries to execute a DML (Data Manipulation Language) statement, such as INSERT, UPDATE, DELETE, or SELECT FOR UPDATE, after issuing a transaction control statement like COMMIT or ROLLBACK, without starting a new transaction. It indicates an attempt to perform a DML operation outside the bounds of a transaction.
3. How can I resolve ORA-00091?
- To resolve ORA-00091, ensure that DML operations are performed within the boundaries of a transaction. This involves ensuring that every transaction begins with a transaction control statement (usually BEGIN TRANSACTION or START TRANSACTION) and ends with either a COMMIT or ROLLBACK statement. If you encounter this error, review your transaction management logic to ensure proper handling of transaction boundaries.
4. Can ORA-00091 be encountered in distributed transactions?
- Yes, ORA-00091 can also occur in distributed transactions involving multiple databases. In distributed transactions, it's important to ensure that transaction boundaries are managed correctly across all involved databases to avoid encountering this error.
5. Is there any way to prevent ORA-00091 from occurring?
- Yes, to prevent ORA-00091, it's essential to follow best practices for transaction management. Ensure that each transaction begins with a transaction control statement and ends with either a COMMIT or ROLLBACK statement. Additionally, carefully review and test transaction logic to ensure it operates as expected and doesn't violate transaction boundaries.
By understanding the causes and resolution of ORA-00091, database developers and administrators can effectively manage transactions and mitigate the occurrence of this error in Oracle databases.
ORA-00090
ORA-00090: failed to allocate memory for cluster
database ORADEBUG command
Cause: Could not allocate memory needed to execute cluster database
oradebug.
ORA-00089
ORA-00089: invalid instance number in ORADEBUG
command
Cause: An invalid instance number was specified in a cluster database
ORADEBUG command.
Action: Reissue the command with valid instance numbers.
ORA-00088
ORA-00088: command cannot be executed by shared
server
Cause: Debug command issued on shared server.
Action: Reissue the command using a dedicated server.
ORA-00087
ORA-00087: command cannot be executed on remote
instance
Cause: Cluster database command issued for non cluster database ORADEBUG
command.
Action: Issue the command without the cluster database syntax.
ORA-00086
ORA-00086: user call does not exist
Cause: An invalid attempt was made to dump the user call heap.
Action: Wait until the process starts a call.
ORA-00085
ORA-00085: current call does not exist
Cause: An invalid attempt was made to dump the current call heap.
Action: Wait until the process starts a call.
ORA-00084
ORA-00084: global area must be PGA, SGA, or UGA
Cause: An attempt was made to dump an invalid global area.
ORA-00083
ORA-00083: warning: possibly corrupt SGA mapped
Cause: Even though there may be SGA corruptions, the SGA was mapped.
Action: Use the DUMPSGA command to dump the SGA.
ORA-00082
ORA-00082: memory size of string is not in valid
set of [1], [2], [4]stringstringstringstringstring
Cause: An invalid length was specified for the POKE command.
Action: Use a valid length (either 1, 2, 4, or possibly 8).
ORA-00081
ORA-00081: address range [string, string) is not
readable
Cause: An attempt was made to read/write an invalid memory address
range.
Action: Try another address or length.
ORA-00080
ORA-00080: invalid global area specified by level
string
Cause: An attempt was made to dump an invalid global area.
Action: 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.
ORA-00079
ORA-00079: variable string not found
Cause: An attempt was made to dump a variable that does not exist.
Action: Use a valid variable name.
ORA-00078
ORA-00078: cannot dump variables by name
Cause: An attempt was made to dump a variable by name on a system that
does not support this feature.
Action: Try the PEEK command.
ORA-00077
ORA-00077: dump string is not valid
Cause: An attempt was made to invoke an invalid dump.
Action: Try another dump.
ORA-00076
ORA-00076: dump string not found
Cause: An attempt was made to invoke a dump that does not exist.
Action: Type DUMPLIST to see the list of available dumps.
ORA-00075
ORA-00075: process "string" not found in
this instance.
Cause: The specified process was not logged on to the current instance.
ORA-00074
ORA-00074: no process has been specified
Cause: No debug process has been specified.
Action: Specify a valid process.
ORA-00072
ORA-00072: process "string" is not active
Cause: An invalid process was specified.
Action: Specify a valid process.
ORA-00071
ORA-00071: process number must be between 1 and
string
Cause: An invalid process number was specified.
Action: Specify a valid process number.
ORA-00070
ORA-00070: command string is not valid.
Cause: An invalid debugger command was specified.
ORA-00069
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.
ORA-00068
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-00067
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-00066
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.
ORA-00065
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-00064
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.
Saturday, 23 April 2016
ORA-00063
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.
ORA-00062:
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-00061
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-00060
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-00059
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-00058
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-00057
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-00056
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-00055
ORA-00055: maximum number of DML locks exceeded.
Cause: Ran out of DML lock state objects.
ORA-00054
ORA-00054: resource busy and acquire with NOWAIT
specified or timeout expired
Cause: Interested resource is busy.
ORA-00053
ORA-00053: maximum number of enqueues exceeded.
Cause: Ran out of enqueue state objects.
Action: Increase the value of the ENQUEUES initialization parameter.
ORA-00052
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-00051
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-00050
ORA-00050: operating system error occurred while
obtaining an enqueue.
Action: Look up the operating system error in your system documentation
and perform the needed action.
ORA-00044
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.
ORA-00043
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-00042
ORA-00042: Unknown Service name string
Cause: An attempt was made to use an invalid application service.
ORA-00041
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-00040
ORA-00040: active time limit exceeded - call
aborted.
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-00039
ORA-00039: error during periodic action
Cause: An unexpected error occurred while executing a periodically invoked
Action: Check the error stack for detailed error information.
Subscribe to:
Posts (Atom)