Tuesday 10 January 2012

ORA-01119: error in creating database file string

ORA-01119: error in creating database file string

Cause: Usually due to not having enough space on the device.

Action: none

ORA-01118: cannot add any more database files: limit of string exceeded

ORA-01118: cannot add any more database files: limit of string exceeded

Cause: There is no more room in the control file for adding database files.

Action: Resize the control file or drop other tablespaces.

ORA-01117: adding file string with illegal block size: string; limit is string

ORA-01117: adding file string with illegal block size: string; limit is string

Cause: An attempt was made to add a database file with a block size that is greater than the maximum block size allowed.

Action: Retry the DDL command with a smaller block size.

ORA-01116: error in opening database file string

ORA-01116: error in opening database file string

Cause: Usually the file is not accessible.

Action: Restore the database file.

ORA-01115: IO error reading block from file string (block # string)

ORA-01115: IO error reading block from file string (block # string)

Cause: Device on which the file resides is probably offline

Action: Restore access to the device

ORA-01114: IO error writing block to file string (block # string)

ORA-01114: IO error writing block to file string (block # string)

Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.

Action: Restore access to the device or remove unnecessary files to free up space.

ORA-01113: file string needs media recovery

ORA-01113: file string needs media recovery

Cause: An attempt was made to online or open a database with a file that is in need of media recovery.

Action: First apply media recovery to the file.

ORA-01112: media recovery not started

ORA-01112: media recovery not started

Cause: An attempt to continue media recovery is being made but media recovery was not started.

Action: None.

ORA-01111: name for data file string is unknown - rename to correct file

ORA-01111: name for data file string is unknown - rename to correct file

Cause: The data file was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created.

Action: Rename the MISSING file to the name of the real file.

ORA-01110: data file string: string

ORA-01110: data file string: string

Cause: Reporting file name for details of another error

Action: See associated error message

ORA-01109: database not open

ORA-01109: database not open

Cause: A command was attempted that requires the database to be open.

Action: Open the database and try the command again

ORA-01108: file string is in backup or media recovery

ORA-01108: file string is in backup or media recovery

Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery.

Action: Complete or cancel the media recovery session or backup.

ORA-01107: database must be mounted for media recovery

ORA-01107: database must be mounted for media recovery

Cause: An attempt to perform media recovery was made but the database is not mounted.

Action: Mount the database.

ORA-01106: database must be closed before dismounting

ORA-01106: database must be closed before dismounting

Cause: Obvious

Action: none

ORA-01105: mount is incompatible with mounts by other instances

ORA-01105: mount is incompatible with mounts by other instances

Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why.

Action: See accompanying errors.

ORA-01104: number of control files (string) does not equal string

ORA-01104: number of control files (string) does not equal string

Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.

Action: Check to make sure that all control files are listed.

ORA-01103: database name string in control file is not string

ORA-01103: database name string in control file is not string

Cause: The database name in the control file does not match your database name.

Action: Either find the correct control file or change your database name.

ORA-01102: cannot mount database in EXCLUSIVE mode

ORA-01102: cannot mount database in EXCLUSIVE mode

Cause: Some other instance has the database mounted exclusive or shared.

Action: Shutdown other instance or mount in a compatible mode.

ORA-01101: database being created currently mounted by some other instance

ORA-01101: database being created currently mounted by some other instance

Cause: Some other instance has the database of same name currently mounted and you are trying to create it.

Action: Either change the database name or shutdown the other instance.

ORA-01100: database already mounted

ORA-01100: database already mounted

Cause: A database is already mounted in this instance.

Action: none

ORA-01099: cannot mount database in SHARED mode if started in single process mode

ORA-01099: cannot mount database in SHARED mode if started in single process mode

Cause: Obvious

Action: none

ORA-01097: cannot shutdown while in a transaction - commit or rollback first

ORA-01097: cannot shutdown while in a transaction - commit or rollback first

Cause: Obvious

Action: none

ORA-01096: program version (string) incompatible with instance (string)

ORA-01096: program version (string) incompatible with instance (string)

Cause: A program is trying to connect to an instance using a different version of code than the database was started with. This is not allowed.

Action: Either relink the program with the same version as the database or restart the database using the old version of code.

ORA-01095: DML statement processed zero rows

ORA-01095: DML statement processed zero rows

Cause: During a call to OTEX, an update, delete, or insert statement being executed processed zero rows. The execution of statements by OTEX was halted at this point.

Action: none

ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected

ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected

Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted.

Action: Find the other sessions and log them out and resubmit the command

ORA-01092: ORACLE instance terminated. Disconnection forced

ORA-01092: ORACLE instance terminated. Disconnection forced

Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance.

Action: Examine the alert log for more details. When the instance has been restarted, retry action.

ORA-01091: failure during startup force

ORA-01091: failure during startup force

Cause: Unable to destroy the old SGA.

Action: Manually remove the old SGA and reissue the STARTUP command

ORA-01090: shutdown in progress - connection is not permitted

ORA-01090: shutdown in progress - connection is not permitted

Cause: The SHUTDOWN command was used to shut down a running ORACLE instance, so you cannot connect to ORACLE.

Action: Wait for the instance to be restarted, or contact your DBA.

ORA-01089: immediate shutdown in progress - no operations are permitted

ORA-01089: immediate shutdown in progress - no operations are permitted

Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running ORACLE instance, so your operations have been terminated.

Action: Wait for the instance to be restarted, or contact your DBA.

ORA-01088: cannot shut down ORACLE while active processes exist

ORA-01088: cannot shut down ORACLE while active processes exist

Cause: Users are still logged into the instance.

Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE.

ORA-01086: savepoint string never established

ORA-01086: savepoint string never established

Cause: Trying to roll back to a save point that was never established.

Action: none

ORA-01085: preceding errors in deferred rpc to string.string.string

ORA-01085: preceding errors in deferred rpc to string.string.string

Cause: Errors were encountered when the named procedure was executed as a deferred remoted procedure call.

Action: Correct the cause of the preceding errors.

ORA-01084: invalid argument in OCI call

ORA-01084: invalid argument in OCI call

Cause: The failing OCI call contains an argument with an invalid value.

Action: Use valid argument values. For more information, see the Programmer s Guide to the Oracle Call Interfaces and the appropriate programming language supplement.

ORA-01083: value of parameter string is inconsistent with that of other instances

ORA-01083: value of parameter string is inconsistent with that of other instances

Cause: The value of the given parameter is required to be the same for all instances in the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2 examples.

Action: Change the value of the parameter in INIT.ORA file to match that of other cluster database instances.

ORA-01082: row_locking = always requires the transaction processing option

ORA-01082: row_locking = always requires the transaction processing option

Cause: row_locking = always is specified in INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option.

Action: Remove it from INIT.ORA file or set it to default or intent .

ORA-01081: cannot start already-running ORACLE - shut it down first

ORA-01081: cannot start already-running ORACLE - shut it down first

Cause: Obvious

Action: none

ORA-01080: error in shutting down ORACLE

ORA-01080: error in shutting down ORACLE

Cause: Failure during system shutdown.

Action: Further diagnostic information should be in the error stack.

ORA-01079: ORACLE database was not properly created, operation aborted

ORA-01079: ORACLE database was not properly created, operation aborted

Cause: There was an error when the database or control file was created.

Action: s to recreate the database or a new control file.

ORA-01078: failure in processing system parameters

ORA-01078: failure in processing system parameters

Cause: Failure during processing of INIT.ORA parameters during system startup.

Action: Further diagnostic information should be in the error stack.

ORA-01077: background process initialization failure

ORA-01077: background process initialization failure

Cause: Failure during initialization of ORACLE background processes.

Action: Further diagnostic information should be in the error stack or in the trace file.

ORA-01076: multiple logons per process not yet supported

ORA-01076: multiple logons per process not yet supported

Cause: Obvious

Action: none

ORA-01075: you are currently logged on

ORA-01075: you are currently logged on

Cause: Attempt to login while logged in.

Action: none

ORA-01074: cannot shut down ORACLE; inside a login session - log off first

ORA-01074: cannot shut down ORACLE; inside a login session - log off first

Cause: Obvious

Action: none

ORA-01073: fatal connection error: unrecognized call type

ORA-01073: fatal connection error: unrecognized call type

Cause: An illegal internal operation was attempted.

Action: Contact your customer support representative.

ORA-01072: cannot stop ORACLE; ORACLE not running

ORA-01072: cannot stop ORACLE; ORACLE not running

Cause: Obvious

Action: none

ORA-01071: cannot perform operation without starting up ORACLE

ORA-01071: cannot perform operation without starting up ORACLE

Cause: Obvious

Action: none

ORA-01070: Using an old version of Oracle for the server

ORA-01070: Using an old version of Oracle for the server

Cause: Using pre 7.0.10.1 version of oracle for server

Action: Upgrade server to post 7.0.10.1 version

ORA-01062: unable to allocate memory for define buffer

ORA-01062: unable to allocate memory for define buffer

Cause: Exceeded the maximum buffer size for current plaform

Action: Use piecewise fetch with a smaller buffer size

ORA-01061: cannot start up a V8 server using a V7 client application

ORA-01061: cannot start up a V8 server using a V7 client application

Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.

Action: Use a client application linked with V8 (or higher) libraries.60

ORA-01060: array binds or executes not allowed

ORA-01060: array binds or executes not allowed

Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL or SQL block with a bind variable of type cursor.

Action: Bind a single cursor or execute the PL or SQL block once.

ORA-01059: parse expected before a bind or execute

ORA-01059: parse expected before a bind or execute

Cause: The client application attempted to bind a variable or execute a cursor opened in a PL or SQL block before the statement was parsed.

Action: Ensure the statement is parsed before a bind or execute.

ORA-01058: internal New Upi interface error

ORA-01058: internal New Upi interface error

Cause: Attempt to delete non existant hstdef extension.

Action: Report as a bug.

ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified

ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified

Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two.

Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one.

ORA-01051: deferred rpc buffer format invalid

ORA-01051: deferred rpc buffer format invalid

Cause: The deferred rpc data in sys.def$_call is corrupted.

Action: Contact your customer support representive.

ORA-01049: Bind by name is not spupportted in streamed RPC

ORA-01049: Bind by name is not spupportted in streamed RPC

Cause: A newer version of server is talking with this version requesting an operation not supported in this version.

Action: none

ORA-01048: Couldn t find the specified procedure in the given context

ORA-01048: Couldn t find the specified procedure in the given context

Cause: The procedure user specified in deferred RPC doesn t exist.

Action: Check to make sure that the procedure exists and is visible to the replication process.

ORA-01045: user string lacks CREATE SESSION privilege; logon denied

ORA-01045: user string lacks CREATE SESSION privilege; logon denied

Cause: A connect was attempted to a userid which does not have create session privilege.

Action: Grant the user CREATE SESSION privilege.

ORA-01044: size string of buffer bound to variable exceeds maximum string

ORA-01044: size string of buffer bound to variable exceeds maximum string

Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_ size)*(number of elements)

Action: Reduce buffer size.

ORA-01043: user side memory corruption (string(, (string(, (string(, (string(

ORA-01043: user side memory corruption (string(, (string(, (string(, (string(

Cause: The application code corrupted some of the usr memory used by oracle

Action: Make sure that the application code is not overwriting memory.

ORA-01042: detaching a session with open cursors not allowed

ORA-01042: detaching a session with open cursors not allowed

Cause: An attempt was made to detach a seesio n which had open cursors.

Action: Close all the cursors before detaching the session.