Try my app Expense Manager @ google play and amazon store.

Tuesday, January 29, 2013

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

Monday, January 28, 2013

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.


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

Follow by Email

Google+ Badge