Oracle Error Messages

Error: ORA-01006: bind variable does not exist
Cause: You tried to issue a bind call for a variable that was not listed in the corresponding SQL statement.
Action: The options to resolve this Oracle error are:
.Modify your bind call to reference a variable that was listed in the corresponding SQL statement. Variables must be prefixed with either a colon ( or an ampersand (&) to be referenced in a BIND call, OBIND, or OBINDN.
.This error may also be caused by a mismatch between a precompiler program and the SQLLIB library.

Error: ORA-01007: variable not in select list
Cause: You tried to reference a variable that was not in the SELECT clause.
Action: The options to resolve this Oracle error are:
.This error can occur in OCI when the value for the position parameter is not a value between 1 and the number of variables in the SELECT clause.
.This error can occur in SQL*Forms or SQL*Report when you specify more variables in the INTO clause than there are values in the SELECT clause.

Error: ORA-01008: not all variables bound
Cause: You tried to execute an SQL statement that contained substitution variables where all variables were not bound.
Action: The options to resolve this Oracle error are:
.In OCI, try using an OBIND or OBINDN call to substitute the values.

Error: ORA-01012: not logged on
Cause: You tried to execute a call to Oracle before logging in.
Action: The options to resolve this Oracle error are:
.Log onto Oracle by calling OLON or OLOGON.

Error: ORA-01013: user requested cancel of current operation
Cause: You interrupted an Oracle operation by pressing Ctrl-C or by canceling the operation through another method (ie: front-end application).
Action: The options to resolve this Oracle error are:
.The current operation has been terminated by the user. There is no course of action to take. This message is informational only.
.This error may also have been caused by a timeout in a sql pass-through query. To resolve this error, properties of the timeout parameter need to be changed to a higher value.

Error: ORA-01014: Oracle shutdown in progress
Cause: You tried to connect to Oracle, but a shutdown is in progress. Users can not log into Oracle while it is being shutdown.
Action: The options to resolve this Oracle error are:
.Wait until Oracle is back up and then try logging in again.

Error: ORA-01017: invalid username/password; logon denied
Cause: You tried to log into Oracle with an invalid username/password combination.
Action: The options to resolve this Oracle error are:
.Log into Oracle with a correct username/password combination. If the username and password are entered together, the correct format is:
username/password

Error: ORA-01023: cursor context not found (invalid cursor number)
Cause: You tried to reference a cursor, but the cursor is not open.
Action: The options to resolve this Oracle error are:
.Open the cursor and retry the operation.

Error: ORA-01031: insufficient privileges
Cause: You attempted to perform an operation for which you do not have the appropriate privileges. Some of the more common causes are:
.You tried to change an Oracle username or password without having the appropriate privileges.
.You tried to perform an UPDATE to a table, but you only have SELECT access to the table.
.You tried to start up an Oracle database using CONNECT INTERNAL.
.You tried to install an Oracle database without having the appropriate privileges to the operating-system.

Action: The options to resolve this Oracle error are:
.You can have the Oracle DBA grant you the appropriate privileges that you are missing.
.You can have the Oracle DBA execute the operation for you.
.If you are having trouble starting up Oracle, you may need to add the Oracle user to the dba group.

Error: ORA-01033: Oracle startup or shutdown in progress
Cause: You have attempted to log onto Oracle while Oracle was being either shut down or started up.
Action: The options to resolve this Oracle error are:
.Wait until the Oracle database has been properly restarted before attempting to log in.

Error: ORA-01034: Oracle not available
Cause: You tried to access Oracle, but Oracle was not started up.
Action: The options to resolve this Oracle error are:
.This error may occur because the operating system variable pointing to the instance was not properly defined.
.This error may also have occurred because the SGA requires more space.

Error: ORA-01035: Oracle only available to users with RESTRICTED SESSION privilege
Cause: You tried to connect to Oracle, but logins are not allowed because the Oracle instance was started in restricted mode. Only users with RESTRICTED SESSION privileges can log in.
Action: The options to resolve this Oracle error are:
.Contact your DBA and have the Oracle instance restarted without the restriction.
.Contact your DBA and ask for RESTRICTED SESSION privileges.

Error: ORA-01037: maximum cursor memory exceeded
Cause: You tried to process a cursor whose SQL was so complex that it used up all available memory.
Action: The options to resolve this Oracle error are:
.Try to re-write your cursor SQL to simplify it.

Error: ORA-01039: insufficient privileges on underlying objects of the view
Cause: You tried to access someone else's view without having the appropriate privileges to the underlying objects of the view.
Action: The options to resolve this Oracle error are:
.Have the Oracle DBA grant you privileges to the underlying objects of the view.
.Do not reference the view.

Error: ORA-01040: invalid character in password; logon denied
Cause: You tried to logon to Oracle using a password that either contained a multi-byte character or a character that is not part of the US7ASCII character set.
Action: The options to resolve this Oracle error are:
.Enter a valid password and retry logon.

Error: ORA-01042: detaching a session with open cursors not allowed
Cause: You tried to detach from an Oracle session while there was an open cursor.
Action: The options to resolve this Oracle error are:
.Close all cursors and then retry detaching the session.

Error: ORA-01045: user name lacks CREATE SESSION privilege; logon denied
Cause: You tried to log into Oracle with a username that has not been granted the CREATE SESSION privilege.
Action: The options to resolve this Oracle error are:
.Have the Oracle DBA grant the username the CREATE SESSION privilege.
.Try logging into Oracle with a different username that has the CREATE SESSION privilege.

Error: ORA-01052: one of the two must-succeed archive destinations is not specified
Cause: You have LOG_ARCHIVE_MIN_SUCCEED_DEST set to 2, while LOG_ARCHIVE_DUPLEX_DEST is not specified.
Action: The options to resolve this Oracle error are:
.Set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1, or specify a value for LOG_ARCHIVE_DUPLEX_DEST.

Error: ORA-01074: cannot shut down Oracle; inside a logon session - log off first
Cause: You tried to shutdown Oracle from inside a logon session.
Action: The options to resolve this Oracle error are:
.Log off Oracle, then try shutting down Oracle.

Error: ORA-01089: immediate shutdown in progress - no operations are permitted
Cause: Your DBA has initiated the SHUTDOWN IMMEDIATE command. This will shutdown Oracle and terminate all active operations.
Action: The options to resolve this Oracle error are:
.Wait until Oracle has been restarted by your DBA.

Error: ORA-01109: database not open
Cause: You tried to perform an operation on a database that was not opened.
Action: The options to resolve this Oracle error are:
.Open the database and then retry the operation.

Error: ORA-01113: file name needs media recovery
Cause: You tried to open a datafile, but the file needs media recovery.
Action: The options to resolve this Oracle error are:
.Apply media recovery to the datafile and then try to re-open it.

Error: ORA-01114: IO error writing block to file name block # num
Cause: You tried to write to a file, but the device where the file resides is offline.
Action: The options to resolve this Oracle error are:
.You need to restore access to this device and then try re-writing to the file.

Error: ORA-01133: length of log file name <name> exceeds limit of num characters
Cause: You tried to execute an operation that specified a redo log file, but the filename was too long.
Action: The options to resolve this Oracle error are:
.Reduce the length of the redo log filename and re-execute the operation.

Error: ORA-01200: actual file size of num is smaller than correct size of num blocks
Cause: A file that you tried to access is smaller in size than what the file header and control file have recorded.
Action: The options to resolve this Oracle error are:
.The file has been truncated. Try restoring the file from a backup.