load csv file into oracle table

CREATE OR REPLACE PROCEDURE p_import_csv (
  p_FileDir  IN VARCHAR2,
  p_FileName IN VARCHAR2,
  p_TotalInserted IN OUT NUMBER
  ) AS

  v_FileHandle                               UTL_FILE.FILE_TYPE;
  v_NewLine                                  VARCHAR2(100);  -- Input line
  v_empid                                    i_importtimeattendance.employeeid%TYPE;
  v_timeentry                                i_importtimeattendance.timeentry%TYPE;
  v_date                                     i_importtimeattendance.datetimesheet%TYPE;
  v_remarks                                  i_importtimeattendance.remarks%TYPE;
  v_dateofwork                               i_importtimeattendance.date_of_work%TYPE;
  v_FirstComma                               NUMBER;
  v_SecondComma                              NUMBER;
  v_ThirdComma                               NUMBER;
  v_FourthComma                              NUMBER;
  veer                                       VARCHAR2(500);
  vdept                                      VARCHAR2(50);  

BEGIN
  v_FileHandle := UTL_FILE.FOPEN(p_FileDir, p_FileName, 'r');

  p_TotalInserted := 0;

  LOOP
    BEGIN
      UTL_FILE.GET_LINE(v_FileHandle, v_NewLine);
    EXCEPTION
      WHEN NO_DATA_FOUND THEN
        EXIT;
    END;

    v_FirstComma    := INSTR(v_NewLine, ',', 1, 1);
    v_SecondComma   := INSTR(v_NewLine, ',', 1, 2);
    v_ThirdComma    := INSTR(v_NewLine, ',', 1, 3);
    v_FourthComma   := INSTR(v_NewLine, ',', 1, 4);
   
    v_empid         := SUBSTR(v_NewLine, 1, v_FirstComma - 1);
    v_date          := SUBSTR(v_NewLine, v_FirstComma + 1,v_SecondComma-1-v_FirstComma);
    v_timeentry     := SUBSTR(v_NewLine, v_SecondComma + 1,v_ThirdComma - v_SecondComma - 1);
    v_remarks       := SUBSTR(v_NewLine,v_ThirdComma+1,v_FourthComma - v_ThirdComma - 1);
    v_dateofwork    := SUBSTR(v_NewLine,v_FourthComma+1);
   
    SELECT dept_code
      INTO vdept
      FROM M_Department
     WHERE M_Department_ID = (SELECT M_Department_ID
                                FROM M_Employee_Master
                               WHERE value = v_empid);
    INSERT INTO i_importtimeattendance (i_importtimeattendance_id,ad_client_id,ad_org_id,employeeid, datetimesheet, timeentry,remarks,
                                        i_isimported,processed,ischk,isactive,dept_name,date_of_work
                                        )
         VALUES (ad_sequence_nextno('I_ImportTimeAttendance'),1000133,1000305,v_empid, v_date, v_timeentry,v_remarks,'N','N','N','Y',vdept,
                v_dateofwork
                );

    p_TotalInserted := p_TotalInserted + 1;
  END LOOP;
 
  UTL_FILE.FCLOSE(v_FileHandle);
 -- UTL_FILE.FRENAME ('UTL_DIR',p_FileName,'UTL_DIR',REPLACE (p_FileName,substr(p_FileName,-4,4),TO_CHAR (SYSDATE, 'DD-MON-RR')) || '.csv'); 
 
  COMMIT;
EXCEPTION
  WHEN UTL_FILE.INVALID_OPERATION THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20051, 'Loading Failed: Invalid Operation');
  WHEN UTL_FILE.INVALID_FILEHANDLE THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20052, 'Loading Failed: Invalid File Handle');
  WHEN UTL_FILE.READ_ERROR THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20053, 'Loading Failed: Read Error');
  WHEN UTL_FILE.INVALID_PATH THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20054, 'Loading Failed: Invalid Path');
  WHEN UTL_FILE.INVALID_MODE THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20055, 'Loading Failed: Invalid Mode');
  WHEN UTL_FILE.INTERNAL_ERROR THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20056, 'Loading Failed: Internal Error');
  WHEN VALUE_ERROR THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    RAISE_APPLICATION_ERROR(-20057, 'Loading Failed: Value Error');
  WHEN OTHERS THEN
    UTL_FILE.FCLOSE(v_FileHandle);
    --RAISE;
    veer:=sqlerrm;
END p_import_csv;
/




DECLARE
      v NUMBER;
    BEGIN
          p_import_csv('UTL_DIR','1749.CSV',v);   
   END;
   /
  

DataBase Daily Backup

SET NAME =RAQFIN_%Date:~-4,4%%Date:~-10,2%%Date:~-7,2%
MD RAQFINBKP\RAQFIN_%Date:~-4,4%%Date:~-10,2%%Date:~-7,2%
SET AA=RAQFINBKP
EXP raqfin_080512/raqfin_080512@orcl FILE = D:\%AA%\RAQFIN_%Date:~-4,4%%Date:~-10,2%%Date:~-7,2%\RAQFIN_%Date:~-4,4%%Date:~-10,2%%Date:~-7,2%

ORA-01036: illegal variable name/number

ORA-01036: illegal variable name/number

Cause: Unable to find bind context on user side


Action: Make sure that the variable being bound is in the sql statement.

ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege

ORA-01035: ORACLE only available to users with RESTRICTED SESSION  privilege

Cause: Logins are disallowed because an instance started in restricted mode. Only  users with RESTRICTED SESSION system privilege can log on.
Action: Request that Oracle be restarted without the restricted option or obtain  the RESTRICTED SESSION system privilege.

ORA-01034: ORACLE not available

ORA-01034: ORACLE not available

Cause: Oracle was not started up. Possible causes include the following:


Action: Refer to accompanying messages for possible causes and correct the  problem mentioned in the other messages. If Oracle has been initialized, then on  some operating systems, verify that Oracle was linked correctly. See the platform  specific Oracle documentation.

ORA-01033: ORACLE initialization or shutdown in progress

ORA-01033: ORACLE initialization or shutdown in progress

Cause: An attempt was made to log on while Oracle is being started up or  shutdown.


Action: Wait a few minutes. Then retry the operation.

ORA-01032: no such userid

ORA-01032: no such userid

Cause: This is an internal error message related to Export/Import.


Action: Contact customer support.

ORA-01031: insufficient privileges

ORA-01031: insufficient privileges

Cause: An attempt was made to change the current username or password  without the appropriate privilege. This error also occurs if attempting to install a  database without the necessary operating system privileges. When Trusted Oracle  is configure in DBMS MAC, this error may occur if the user was granted the  necessary privilege at a higher label than the current login.
Action: Ask the database administrator to perform the operation or grant the  required privileges. For Trusted Oracle users getting this error although granted  the the appropriate privilege at a higher label, ask the database administrator to  regrant the privilege at the appropriate label.

ORA-01030: SELECT ... INTO variable does not exist

ORA-01030: SELECT ... INTO variable does not exist
Cause: The SELECT... INTO specified in the bind call does not correspond to a  variable in the SQL
statement.
Action: If it is not possible to correct the statement, call customer support.

ORA-01029: internal two task error

ORA-01029: internal two task error

Cause: Received a request to send the long again when there is no long
Action: Report as a bug

ORA-01028: internal two task error

ORA-01028: internal two task error

Cause: Received send long message but don"t have the cursor context.

Action: Report as a bug.

ORA-01027: bind variables not allowed for data definition operations

ORA-01027: bind variables not allowed for data definition operations
Cause: An attempt was made to use a bind variable in a SQL data definition  operation.

Action: Such bind variables are not allowed.

ORA-01026: multiple buffers of size > 4000 in the bind list

ORA-01026: multiple buffers of size > 4000 in the bind list

Cause: More than one long buffer in the bind list.
Action: Change the buffer size to be less than 4000 for the bind variable bound to  a normal column.

ORA-01023: Cursor context not found (Invalid cursor number)

ORA-01023: Cursor context not found (Invalid cursor number)

Cause: The cursor number is not a valid open cursor.
Action: Make sure that the cursor is open.

ORA-01025: UPI parameter out of range

ORA-01025: UPI parameter out of range
Cause: An integer parameter to a upi function is out of range.

Action: This usually indicates an error in a tool built on top of the oracle dbms.  Report the error to your customer support representative.

ORA-01019: unable to allocate memory in the user side

ORA-01019: unable to allocate memory in the user side

Cause: The user side memory allocator returned error.
Action: Increase the processes heap size or switch to the old set of calls.

ORA-01022: database operation not supported in this configuration

ORA-01022: database operation not supported in this configuration
Cause: The attempted database operation does not conform to the user  programming interface (UPI)
for the two communicating ORACLE servers.
Action: You may need to upgrade one or more of your ORACLE servers or re-link  your user side application with new libraries. Report the problem to Worldwide  Customer Support.

ORA-01010: invalid OCI operation

ORA-01010: invalid OCI operation

Cause: One of the following: 1) You attempted an invalid OCI operation. 2) You  are using an
Oracle client application linked with version 7.1 (or higher) libraries,  the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you  attempted to connect to a version 7.0 (or lower) Oracle Server. 3) You are  connected to a version 7.1 (or higher) Oracle Server, the initialization parameter  DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database  link pointing to a version 7.0 (or lower) Oracle Server. 4) You are connected to a  version 9.0.2(or higher) Oracle Server and you attempted to use a database link  pointing to a version 9.0.1(or lower) Oracle Server for distributed autonomous  transaction.
Action: For the above causes: 1) Do not use the invalid OCI operation. 2) If you do  not wish to use encrypted connect passwords in your distributed database, set  ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect  passwords, you must upgrade all Oracle Servers to version 7.1 (or higher). 3) If  you do not wish to use encrypted database links in your distributed database, set  DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database  links, you must upgrade all Oracle Servers to version 7.1 (or higher). 4) Do not  attempt distributed autonomous transaction on version 9.0.1(or lower) Oracle  Server.

ORA-01016: This function can be called only after a fetch

ORA-01016: This function can be called only after a fetch
Cause: Cursor in an invalid state.

Action: Make sure that the oci/upi function is called after fetch.

ORA-00991: only MAC privileges may be granted to procedures

ORA-00991: only MAC privileges may be granted to procedures
Cause: Object privileges or non-MAC system privileges were granted to the  procedure.

Action: Only grant MAC privileges using the PROCEDURE clause.

ORA-00981: cannot mix table and system auditing options

ORA-00981: cannot mix table and system auditing options
Cause: Table and system-wide auditing options were specified in the same  AUDIT or NOAUDIT
statement.
Action: You must issue table and system options in separate statements.

ORA-00983: cannot audit or noaudit SYS user actions

ORA-00983: cannot audit or noaudit SYS user actions

Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions.
Action: Execute the statement again with a valid user.

ORA-00977: duplicate auditing option

ORA-00977: duplicate auditing option
Cause: AUDIT or NOAUDIT statement specifies an option more than once

Action: Either use ALL with no other auditing options or make sure no option is  listed more than once.

ORA-00981: cannot mix table and system auditing options

ORA-00981: cannot mix table and system auditing options

Cause: Table and system-wide auditing options were specified in the same  AUDIT or
NOAUDIT statement.
Action: You must issue table and system options in separate statements.

ORA-00976: LEVEL- PRIOR- or ROWNUM not allowed here

ORA-00976: LEVEL- PRIOR- or ROWNUM not allowed here
Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location.

Action: Remove LEVEL, PRIOR, or ROWNUM.

ORA-00977: duplicate auditing option

ORA-00977: duplicate auditing option

Cause: AUDIT or NOAUDIT statement specifies an option more than once
Action: Either use ALL with no other auditing options or make sure no option is  listed more than once.

ORA-00965: column aliases not allowed for '*'

ORA-00965: column aliases not allowed for '*'
Cause: The statement is trying to alias the * expression in the select list which is  not legal.

Action: Remove the alias.

ORA-00972: identifier is too long

ORA-00972: identifier is too long

Cause: An identifier with more than 30 characters was specified.
Action: Specify at most 30 characters.

ORA-00964: table name not in FROM list

ORA-00964: table name not in FROM list

Cause: The table name referred in the select list is not specified in the from list.
Action: Make sure the name is correctly specified and matches one of the names  in the from list.

ORA-00960: ambiguous column naming in select list

ORA-00960: ambiguous column naming in select list
Cause: A column name in the order-by list matches more than one select list  columns.
Action: Remove duplicate column naming in select list.

ORA-00962: too many group-by / order-by expressions

ORA-00962: too many group-by / order-by expressions
Cause: The group-by or order-by column list contain more than 1000 expressions.

Action: Use 1000 or less expressions in the group-by or order-by list.

ORA-00956: missing or invalid auditing option

ORA-00956: missing or invalid auditing option
Cause: AUDIT or NOAUDIT statement contains an invalid auditing option.

Action: Use a valid option.

ORA-00912: input parameter too long

ORA-00912: input parameter too long

Cause: one of your input strings was too long
Action: shorten the input parameter length

ORA-00953: missing or invalid index name

ORA-00953: missing or invalid index name
Cause: An index name of the form [ <identifier> . ] <identifier> is expected but  not present. If
OIDINDEX clause, index name must be <identifier>
Action: Enter an appropriate index name.

ORA-00910: specified length too long for its datatype

ORA-00910: specified length too long for its datatype

Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise,  the length
specified was > 4000.
Action: use a shorter length or switch to a datatype permitting a longer length  such as a VARCHAR2, LONG CHAR, or LONG RAW

ORA-00911: invalid character

ORA-00911: invalid character
Cause: identifiers may not start with any ASCII character other than letters and  numbers. $#_ are
also allowed after the first character. Identifiers enclosed by  doublequotes may contain any character other than a doublequote. Alternative  quotes (q"#...#") cannot use spaces, tabs, or carriage returns as delimiters. For all  other contexts, consult the SQL Language Reference Manual.
Action: none

ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled

ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled

Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA  enabled which
cannot be done because auto-tune SGA cannot work with  statistics_level set to BASIC.
Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again.

ORA-00832: no streams pool created and cannot automatically create one

ORA-00832: no streams pool created and cannot automatically create one
Cause: A database feature which needs STREAMS SGA was being used, however,  the
streams_pool_size parameter was not defined and the value of db_cache_size  was too small to permit an automatic transfer of SGA to the streams pool from the  buffer cache.
Action: Please set the parameter streams_pool_size or set sga_target.

ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings

ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal  settings
Cause: Unable to set shared_pool_reserved_size to specified value if sga_target  set, either because
the specified value is too small, or because it is too large for the  current internal size of shared pool. More details can be found in the alert log.
Action: If possible, do not set shared_pool_reserved_size without setting shared_  pool_size if sga_target set. Examine the alert log for information about current  internal size of shared pool, and valid range of values for shared_pool_reserved_  size.

ORA-00827: could not shrink sga_target to specified value

ORA-00827: could not shrink sga_target to specified value

Cause: Attempted to shrink the SGA to the specified value but did not succeed  because the
SGA components could not be shrunk as they were already at their  minimum sizes.
Action: Do not set sga_target to a value below the current value without first  shrinking the individual SGA components.

ORA-00825: cannot set db_block_buffers if sga_target set

ORA-00825: cannot set db_block_buffers if sga_target set
Cause: sga_target set with db_block_buffers set.

Action: Do not set sga_target or use new cache parameters and do not use db_  block_buffers which is a old cache parameter.

ORA-00826: cannot set sga_target for an ASM instance

ORA-00826: cannot set sga_target for an ASM instance
Cause: sga_target set for an ASM instance.

Action: Do not set sga_target.

ORA-00824: cannot set sga_target due to existing internal settings - see alert log for more

ORA-00824: cannot set sga_target due to existing internal settings - see alert log for  more
information
Cause: Unable to set sga_target due to current parameter settings.
Action: See alert log for more information.

ORA-00822: MMAN process terminated with error

ORA-00822: MMAN process terminated with error

Cause: The Memory Management process died.
Action: Warm start instance

ORA-00823: Specified value of sga_target greater than sga_max_size

ORA-00823: Specified value of sga_target greater than sga_max_size
Cause: The specified value of sga_target is greater than sga_max_size.

Action: Increase sga_max_size to match up with sga_target or decrease sga_target  to match up with sga_maxsize.

ORA-00821: Specified value of sga_target stringM is too small - needs to be at least stringM

ORA-00821: Specified value of sga_target stringM is too small - needs to be at least  stringM
Cause: The specified value of sga_target is too small for the SGA to accommodate  all of the
necessary SGA components such as the log buffer, buffer pools, shared  pool, etc.
Action: Set sga_target to the recommended value or reduce the values of any SGA  component size parameters you have specified.

ORA-00750: database has been previously mounted and dismounted

ORA-00750: database has been previously mounted and dismounted
Cause: The instance has already mounted and dismounted the database, which is  only allowed once
in its lifetime.
Action: Shut down the database.

ORA-00820: Specified value of sga_max_size is too small- needs to be at least stringM

ORA-00820: Specified value of sga_max_size is too small- needs to be at least  stringM

Cause: The specified value of sga_max_size is too small for the SGA to  accommodate all of the
necessary SGA components such as the log buffer, buffer  pools, shared pool, etc.
Action: Set sga_max_size to the recommended value or reduce the values of any  SGA component size parameters you have specified.

ORA-00740: datafile size of (string) blocks exceeds maximum file size

ORA-00740: datafile size of (string) blocks exceeds maximum file size

Cause: The user specified datafile size exceeded maximum file size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.

ORA-00741: logfile size of (string) blocks exceeds maximum logfile size

ORA-00741: logfile size of (string) blocks exceeds maximum logfile size
Cause: The user specified logfile size exceeded maximum logfile size.

Action: Please check REFERENCE for maximum size. Reduce the size and retry.

ORA-00723: Initialization parameter COMPATIBLE must be explicitly set

ORA-00723: Initialization parameter COMPATIBLE must be explicitly set

Cause: Oracle detected that the initialization parameter COMPATIBLE was not  explicitly
specified, and the compatibility of the database is lower than the default  value of the COMPATIBLE parameter. In order to use the new compatible setting,  the intialization parameter must be explicitly set by the user.
Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or  SPFILE, whichever is used.

ORA-00724: ALTER DATABASE CONVERT command has been de-supported

ORA-00724: ALTER DATABASE CONVERT command has been de-supported
Cause: ALTER DATABASE CONVERT command has been de-supported since  Oracle 10i.

Action: No action required.

ORA-00722: Feature string

ORA-00722: Feature string
Cause: Reporting name of the feature for details of another error.

Action: See associated error message.

ORA-00721: changes by release string cannot be used by release string
Cause: An attempt to import a tablespace failed because the tablespace contains  changes that require a newer software release or that violate the compatibility  parameters.
Action: Use a version of the software that can understand the changes or relax the  compatibility requirements in the initialization parameter file.

ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported

ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been  de-supported
Cause: ALTER DATABASE RESET COMPATIBILITY command has been  de-supported since Oracle 10i.
Action: No action required.

ORA-00711: new tablespace name is invalid

ORA-00711: new tablespace name is invalid

Cause: An attempt to rename a tablespace failed because the new name is invalid.
Action: Choose a valid new name and retry the command.

ORA-00712: cannot rename system tablespace

ORA-00712: cannot rename system tablespace
Cause: An attempt to rename the system tablespace failed.

Action: No action required.

ORA-00710: new tablespace name is the same as the old tablespace name

ORA-00710: new tablespace name is the same as the old tablespace name
Cause: An attempt to rename a tablespace failed because the new name is the  same as the old name.

Action: No action required.

ORA-00706: error changing format of file string

ORA-00706: error changing format of file string

Cause: An attempt to change the block0 format of the specified file failed because  the file is read-only or offline.
Action: Make the file read-write or bring the file online and set the BLK0_  FMTCHG event.

ORA-00705: inconsistent state during start up; shut down the instance, then restart it

ORA-00705: inconsistent state during start up; shut down the instance, then restart it

Cause: A previous attempt to start an instance was terminated.

Action: Shut down the instance completely, then restart it.

ORA-00704: bootstrap process failure

ORA-00704: bootstrap process failure
Cause: Failure in processing bootstrap data - see accompanying error.

Action: Contact your customer support representative.

ORA-00702: bootstrap verison "string" inconsistent with version "string"

ORA-00702: bootstrap verison "string" inconsistent with version "string"

Cause: The reading version of the boostrap is incompatible with the current  bootstrap version.
Action: Restore a version of the software that is compatible with this bootstrap  version.

ORA-00703: maximum number of row cache instance locks exceeded

ORA-00703: maximum number of row cache instance locks exceeded
Cause: There are not enough row cache enqueues.

Action: Increase the row cache enqueue parameter and warm start the system.

ORA-00701: object necessary for warmstarting database cannot be altered

ORA-00701: object necessary for warmstarting database cannot be altered
Cause: Attempt to alter or drop a database object (table, cluster, or index) which  are needed for
warmstarting the database.
Action: None.

ORA-00609: could not attach to incoming connection

ORA-00609: could not attach to incoming connection
Cause: Oracle process could not answer incoming connection

Action: If the situation described in the next error on the stack can be corrected,  do so; otherwise contact Oracle Support.

ORA-00610: Internal error code

ORA-00610: Internal error code

Cause: Oracle process started too late
Action: This error should never be seen by the customer. Contact Oraclce Support

ORA-00608: testing error [string] [string] [string] [string] [string]

ORA-00608: testing error [string] [string] [string] [string] [string]

Cause: Internal error reserved for testing.
Action: call Oracle Support

ORA-00607: Internal error occurred while making a change to a data block

ORA-00607: Internal error occurred while making a change to a data block
Cause: An internal error or memory exception occurred while Oracle was  applying redo to a data
block.
Action: call Oracle Support

ORA-00606: Internal error code

ORA-00606: Internal error code

Cause: A call to deferred upi functions was made in non deferred mode
Action: Report as a bug.

ORA-00603: ORACLE server session terminated by fatal error

ORA-00603: ORACLE server session terminated by fatal error

Cause: An ORACLE server session is in an unrecoverable state.
Action: Login to ORACLE again so a new server session will be created

ORA-00604: error occurred at recursive SQL level string

ORA-00604: error occurred at recursive SQL level string
Cause: An error occurred while processing a recursive SQL statement (a  statement applying to
internal dictionary tables).
Action: If the situation described in the next error on the stack can be corrected,  do so; otherwise contact Oracle Support.

ORA-00601: cleanup lock conflict

ORA-00601: cleanup lock conflict

Cause: PMON process runs into lock conflict trying to recovery processes
Action: This is trapped internally, no action necessary

ORA-00602: internal programming exception

ORA-00602: internal programming exception
Cause: Internal programming exception

Action: Report as bug

ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string],

ORA-00600: internal error code, arguments: [string], [string], [string], [string],  [string],
[string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions.  This indicates that a
process has encountered an exceptional condition.
Action: Report as a bug - the first argument is the internal error number

ORA-00568: Maximum number of interrupt handlers exceeded

ORA-00568: Maximum number of interrupt handlers exceeded
Cause: User specified too many ^c handlers

Action: Remove some old handlers.

ORA-00569: Failed to acquire global enqueue.

ORA-00569: Failed to acquire global enqueue.


Cause: A prior error occurred on one of the instances in the cluster. Typically  errors are caused by shared pool resource contention.
Action: Check for and resolve prior errors on all instances in the cluster. If there is  shared pool resource contention, increase the SHARED_POOL_SIZE, DML_  LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES  and PARALLEL_MAX_SERVERS initialization parameters.

ORA-00566: cannot request processor group - NUMA not enabled

ORA-00566: cannot request processor group - NUMA not enabled
Cause: Cannot start process in a requested processor group when the NUMA  feature is disabled.

Action: Start the process without requesting a NUMA processor group.

ORA-00567: Requested processor group string is too large (maximum string)

ORA-00567: Requested processor group string is too large (maximum string)

Cause: The process could not be started in the requested processor group.
Action: Start the process in another processor group.

ORA-00489: ARB* process terminated with error

ORA-00489: ARB* process terminated with error
Cause: An ASM rebalance worker process died.

Action: Wait for process to restart.

ORA-00490: PSP process terminated with error

ORA-00490: PSP process terminated with error

Cause: The process spawner died
Action: Warm start instance

ORA-00487: CTWR process terminated with error

ORA-00487: CTWR process terminated with error
Cause: The change tracking process died

Action: Warm start instance

ORA-00488: RBAL process terminated with error

ORA-00488: RBAL process terminated with error

Cause: The ASM rebalance coordinator process died.
Action: Warm start instance.

ORA-00485: DIAG process terminated with error string

ORA-00485: DIAG process terminated with error string
Cause: A global diagnostic process died

Action: Wait for process to restart

ORA-00486: ASMB process terminated with error

ORA-00486: ASMB process terminated with error

Cause: An ASM background process died.
Action: Warm start instance. Also check that ASM Instance is running.

ORA-00484: LMS* process terminated with error

ORA-00484: LMS* process terminated with error

Cause: A global cache service process died
Action: Warm start instance

ORA-00483: During shutdown a process abnormally terminated

ORA-00483: During shutdown a process abnormally terminated

Cause: One of the background processes did not exit normally at or near the time  of shutdown.
Action: Use shutdown abort.

ORA-00481: LMON process terminated with error

ORA-00481: LMON process terminated with error

Cause: The global enqueue service monitor process died
Action: Warm start instance

ORA-00482: LMD* process terminated with error

ORA-00482: LMD* process terminated with error
Cause: A global enqueue service daemon process died

Action: Warm start instance

ORA-00479: RVWR process terminated with error string

ORA-00479: RVWR process terminated with error string

Cause: The RVWR process died
Action: Warm start instance

ORA-00480: LCK* process terminated with error

ORA-00480: LCK* process terminated with error
Cause: A system lock process died

Action: Warm start instance

ORA-00478: SMON process terminated due to error string

ORA-00478: SMON process terminated due to error string
Cause: SMON was unable to service the requests due to error in cleanup of  resources

Action: Warm start instance

ORA-00477: SNP* process terminated with error

ORA-00477: SNP* process terminated with error

Cause: A materialized view refresh process died
Action: PMON will restart SNP process shortly. If SNP process does not get  started, contact Oracle support.

ORA-00475: TRWR process terminated with error

ORA-00475: TRWR process terminated with error

Cause: The system tracing process died
Action: Warm start instance

ORA-00476: RECO process terminated with error

ORA-00476: RECO process terminated with error
Cause: The distributed transaction (two-phase commit) recovery process died.

Action: Warm start instance

ORA-00474: SMON process terminated with error

ORA-00474: SMON process terminated with error
Cause: The system cleanup process died

Action: Warm start instance

ORA-00473: ARCH process terminated with error

ORA-00473: ARCH process terminated with error
Cause: The archive process died

Action: Warm start instance

ORA-00471: DBWR process terminated with error

ORA-00471: DBWR process terminated with error
Cause: The database writer process died

Action: Warm start instance

ORA-00472: PMON process terminated with error

ORA-00472: PMON process terminated with error

Cause: The process cleanup process died
Action: Warm start instance

ORA-00469: CKPT process terminated with error

ORA-00469: CKPT process terminated with error
Cause: The checkpoint process died

Action: Warm start instance

ORA-00470: LGWR process terminated with error

ORA-00470: LGWR process terminated with error

Cause: The log writer process died
Action: Warm start instance

ORA-00453: backgroud process string is dead

ORA-00453: backgroud process string is dead
Cause: The background process that was being messaged was dead or its  incarnation was invalid.

Action: Restart the background process.

ORA-00452: foreground process unexpectedly terminated with error string

ORA-00452: foreground process unexpectedly terminated with error string
Cause: The foreground process for the new connection did not start.
Action: Reconnect to Oracle.

ORA-00450: background process string did not start

ORA-00450: background process string did not start

Cause: The specified process did not start.
Action: Consult the error code, and the trace file for the process.

ORA-00451: foreground process died unexpectedly

ORA-00451: foreground process died unexpectedly
Cause: The foreground process for the new connection did not start.

Action: Reconnect to Oracle.

ORA-00448: normal completion of background process

ORA-00448: normal completion of background process

Cause: One of the background processes completed normally (i.e. exited). The  background
process thinks that somebody asked it to exit.
Action: Warm start the system.

ORA-00449: background process string unexpectedly terminated with error string

ORA-00449: background process string unexpectedly terminated with error string
Cause: A foreground process needing service from a background process has  discovered the process
died.
Action: Consult the error code, and the trace file for the process.

ORA-00446: background process started when not expected

ORA-00446: background process started when not expected

Cause: The background process specified started up AFTER the RDBMS was  already running.
Action: If nobody at your site started the process, then this is an internal error.

ORA-00447: fatal error in background process

ORA-00447: fatal error in background process
Cause: One of the background processes died unexpectedly.

Action: Warm start the system.

ORA-00444: background process string failed while starting

ORA-00444: background process string failed while starting

Cause: Usually due to a bad (or non-existent) background process image.
Action: Get a good background process image.

ORA-00445: background process string did not start after string seconds

ORA-00445: background process string did not start after string seconds
Cause: The specified process did not start after the specified time.

Action: Ensure that the background did not die and leave a trace file.

ORA-00443: background process string did not start

ORA-00443: background process string did not start
Cause: The specified process did not start.

Action: Ensure that the executable image is in the correct place with the correct  protections, and that there is enough memory.

ORA-00438: %s Option not installed

ORA-00438: %s Option not installed

Cause: The specified option is not installed.

Action: Purchase and install the option.

ORA-00439: feature not enabled: string

ORA-00439: feature not enabled: string

Cause: The specified feature is not enabled.

Action: Do not attempt to use this feature.

ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE

ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT  SPACE
MANAGEMENT

Cause: This is due to migrating from an older release of Oracle with tablespaces  created using AUTO SEGMENT SPACE MANAGEMENT. To open the database,  the COMPATIBLE parameter needs to be set to the specified value.

Action: Shutdown and startup with the specified compatibility setting.

ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance

ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance

Cause: ORACLE feature is not licensed.

Action: Contact ORACLE for assistance.

ORA-00406: COMPATIBLE parameter needs to be string or greater

ORA-00406: COMPATIBLE parameter needs to be string or greater

Cause: The COMPATIBLE initialization parameter is not high enough to allow the  operation.
Allowing the command would make the database incompatible with  the release specified by the current COMPATIBLE parameter.

Action: Shutdown and startup with a higher compatibility setting.

ORA-00407: rolling upgrade from release string.string to string.string is not allowed

ORA-00407: rolling upgrade from release string.string to string.string is not allowed

Cause: Another instance executing software at a different point release already  has the database
mounted.

Action: Shutdown all instances then startup with the new software.

ORA-00408: parameter string is set to TRUE

ORA-00408: parameter string is set to TRUE

Cause: Reporting the parameter that resulted in the compatibility error.

Action: Shutdown and startup with a higher compatibility setting.

ORA-00403: %s (string) is not the same as other instances (string)

ORA-00403: %s (string) is not the same as other instances (string)

Cause: Another instance has set the compatible or compatible no recovery  parameters differently
than this instance.

Action: Change the parameters of the current instance to match other instances  already running.

ORA-00404: Convert file not found: string

ORA-00404: Convert file not found: string

Cause: The file used for converting the database from V7 to V8 could not be  found.

Action: Verify that the migration process has been started on this database and  that the convert filename is accessable.

ORA-00405: compatibility type string

ORA-00405: compatibility type string

Cause: Reporting a type associated with another error.

Action: See accompanying error

ORA-00400: invalid release value string for parameter string

ORA-00400: invalid release value string for parameter string

Cause: The release level given for the specified init parameter is invalid.

Action: Correct the parameter value in the parameter file and retry.

ORA-00401: the value for parameter string is not supported by this release

ORA-00401: the value for parameter string is not supported by this release

Cause: The value specified cannot be supported by this release of the software.

Action: Choose an appropriate value, or remove the parameter value to use the  default value.

ORA-00402: database changes by release string cannot be used by release string

ORA-00402: database changes by release string cannot be used by release string

Cause: Changes have been made to the database that require a newer software  release or that violate
the compatibility parameters.

Action: Use a version of the software that can understand the changes or relax the  compatibility requirements in the init file.

ORA-00398: abort thread recovery due to reconfiguration

ORA-00398: abort thread recovery due to reconfiguration

Cause: Global enqueue service reconfiguration occurred during instance/crash  recovery.

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

ORA-00399: corrupt change description in redo log

ORA-00399: corrupt change description in redo log

Cause: A change vector in the redo log failed validation checks.

Action: Do recovery with a good version of the log or do time based recovery up  to the indicated time.

ORA-00395: online logs for the clone database must be renamed

ORA-00395: online logs for the clone database must be renamed

Cause: A clone database open forces logfile renaming to avoid overwriting the  primary logfiles

Action: Rename the logfiles manually or using the log_file_name_convert  initialization parameter

ORA-00396: error string required fallback to single-pass recovery

ORA-00396: error string required fallback to single-pass recovery

Cause: The indicated error caused two-pass instance or crash recovery to fail.  Recovery was retried
with an alternate (slower) method to avoid the error.

Action: Correct the cause of the indicated error (also recorded) so that future  instance or crash recovery can succeed with the two-pass algorithm. This usually  requires making more main memory available to the recovery process.

ORA-00397: instance recovery process terminated with error

ORA-00397: instance recovery process terminated with error

Cause: The foreground process doing instance recovery died.

Action: Check the foreground trace file for the cause of recovery failure.

ORA-00392: log string of thread string is being cleared - operation not allowed

ORA-00392: log string of thread string is being cleared - operation not allowed

Cause: An operation encountered this online log in the middle of being cleared.  The command that
began the clearing may have terminated without completing  the clearing.

Action: If the clear command is still executing then wait for its completion. If it  terminated then reissue the clear command, or drop the log.

ORA-00393: log string of thread string is needed for recovery of offline datafiles

ORA-00393: log string of thread string is needed for recovery of offline datafiles

Cause: Log cannot be cleared because the redo in it is needed to recover offline  datafiles. It has not
been archived so there is no other copy available. If the log is  cleared the tablespaces containing the files will have to be dropped.

Action: Archive the log then repeat the clear command. If archiving is not  possible, and dropping the tablespaces is acceptible, then add the clause  UNRECOVERABLE DATAFILE at the end of the clear command.

ORA-00394: online log reused while attempting to archive it

ORA-00394: online log reused while attempting to archive it

Cause: It has been detected that an online log that is being archived has been  reused

Action: Cannot archive the logfile anymore since it has been overwritten

ORA-00390: log string of thread string is being cleared - cannot become current log

ORA-00390: log string of thread string is being cleared - cannot become current log

Cause: An attempt to switch to a new online log for the redo thread failed because  no reusable log
could be found. This log is being cleared and will be useable when  the clearing completes. The command that began the clearing may have  terminated without completing the clearing.

Action: If the clear command is still executing then wait for its completion. If it  terminated then reissue the clear command, or drop the log.

ORA-00391: All threads must switch to new log format at the same time

ORA-00391: All threads must switch to new log format at the same time

Cause: An attempt to switch the current log of a single thread is not allowed  because the
compatiblity requirements force a new log format version number.  When changing log formats, all threads must switch to the new format at the same  time.

Action: Open the database to cause the coordinated log switch. If that is not  possible then return to the same software version and compatibility setting last  used to open the database.

ORA-00385: cannot enable Very Large Memory with new buffer cache parameters

ORA-00385: cannot enable Very Large Memory with new buffer cache parameters

Cause: User specified one or more of { db_cache_size , db_recycle_cache_size, db_ 
keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32) } AND use_  indirect_data_buffers is set to TRUE. This is illegal.

Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2)  parameters.

ORA-00386: use_indirect_data_buffers not supported

ORA-00386: use_indirect_data_buffers not supported

Cause: The system could not allocate sufficient memory to grow the cache to the  specified size.

Action: Attempt a smaller increase in the value of the parameter.

ORA-00382: %s not a valid block size - valid range [string..string]

ORA-00382: %s not a valid block size - valid range [string..string]

Cause: User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16,  32}, but nk is not
a valid block size for this platform.

Action: Remove corresponding parameter from the "init.ora" file and restart the  instance.

ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero

ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero

Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce 
db_<n>K_cache_size to zero while there were still online tablespaces with  blocksize <n>K. Note that since the SYSTEM tablespace cannot be taken offline, it  is always illegal to set db_cache_size to zero.

Action: Offline any tablespaces with the corresponding blocksize and then  perform the operation again.

ORA-00384: Insufficient memory to grow cache

ORA-00384: Insufficient memory to grow cache

Cause: The system could not allocate sufficient memory to grow the cache to the  specified size.

Action: Attempt a smaller increase in the value of the parameter.

ORA-00379: no free buffers available in buffer pool string for block size stringK

ORA-00379: no free buffers available in buffer pool string for block size stringK

Cause: All buffers in the specified buffer pool for the specified block size are in  use and no free
buffers are available.

Action: Increase the number of buffers in the specified pool for the specified block  size

ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard block size

ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard  block size

Cause: User specified the parameter db_nk_cache_size (where n is one of  2,4,8,16,32), while the
standard block size for this database is equal to n Kbytes.  This is illegal.

Action: Specify the standard block size cache using db_cache_size (DEFAULT  pool) (and db_recycle_cache_size, db_keep_cache_size if additional buffer pools  are required). Do NOT use the corresponding db_nk_cache_size parameter for the  standard block size.

ORA-00381: cannot use both new and old parameters for buffer cache size specification

ORA-00381: cannot use both new and old parameters for buffer cache size  specification

Cause: User specified one or more of { db_cache_size , db_recycle_cache_size, db_ 
keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32), db_cache_  advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_  recycle }. This is illegal.

Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don"t  specify both. If old size parameters are specified in the parameter file, you may  want to replace them with new parameters since the new parameters can be  modified dynamically and allow you to configure additional caches for additional  block sizes. Cache advisory can only be enabled with the new cache parameters.

ORA-00376: file string cannot be read at this time

ORA-00376: file string cannot be read at this time
Cause: attempting to read from a file that is not readable. Most likely the file is  offline.

Action: Check the state of the file. Bring it online

ORA-00377: Frequent backups of file string causing write operation to stall

ORA-00377: Frequent backups of file string causing write operation to stall

Cause: Backups are occurring too frequently on this file. Each time a new backup  is started for a
file, any writes which have been previously issued (but not  completed) have to be re-issued. If hot backups are started very, very frequently, it  is possible that some writes will be re-issued repeatedly and never complete.

Action: Increase the interval between begin hot-backup commands for this file.

ORA-00378: buffer pools cannot be created as specified

ORA-00378: buffer pools cannot be created as specified

Cause: Either the number of buffers or the number of lru latches is too small to  satisfy the specified
buffer pool configuration.

Action: Either increase the number of buffers and/or number of lru latches or  configure smaller buffer pools.

ORA-00373: online log version string incompatible with ORACLE version string

ORA-00373: online log version string incompatible with ORACLE version string
Cause: The online log was written by incompatible version of Oracle. Can occur  when the log file
was created by either a new or older version of Oracle.
Action: Recover the database with the compatible software, shut it down cleanly,  then restart with current software.

ORA-00374: parameter db_block_size = string invalid - must be a multiple of string in the

ORA-00374: parameter db_block_size = string invalid - must be a multiple of string  in the range [string..string]
Cause: invalid value for db_block_size parameter

Action: adjust parameter and restart

ORA-00375: unable to get default db_block_size

ORA-00375: unable to get default db_block_size
Cause: the system was unable to determine the default db_block_size

Action: see accompanying system specific error. As a workaround, specify the  blocksize in the INIT.ORA file.

ORA-00371: not enough shared pool memory - should be atleast string bytes

ORA-00371: not enough shared pool memory - should be atleast string bytes
Cause: Init.ora parameter shared_pool_size is too small

Action: Increase the parameter value

ORA-00372: file string cannot be modified at this time

ORA-00372: file string cannot be modified at this time
Cause: attempting to modify the contents of a file that cannot be modified. The  file is most likely
part of a read only tablespace but may be in the process of going  offline, or the database may be in the process of closing.
Action: check the status of the file and its tablespace

ORA-00368: checksum error in redo log block

ORA-00368: checksum error in redo log block
Cause: The redo block indicated by the accompanying error, is not vaild. It has a  checksum that
does not match the block contents.
Action: Restore correct file or reset logs.

ORA-00369: Current log of thread string not useable and other log being cleared

ORA-00369: Current log of thread string not useable and other log being cleared
Cause: Attempt to open thread failed because it is necessary to switch redo  generation to another
online log, but all the other logs are being cleared or need to  be archived before they can be used.
Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then  wait for it to complete. Otherwise reissue the CLEAR command. If there are other  online logs for the thread, that are not being cleared, then archive the logs.

ORA-00370: potential deadlock during kcbchange operation

ORA-00370: potential deadlock during kcbchange operation
Cause: Error code used internally by software. Should never be reported

Action: Treat as internal error. See error 600.

ORA-00365: the specified log is not the correct next log

ORA-00365: the specified log is not the correct next log
Cause: The specified log failed to pass checks to ensure it corresponds to the log  that was just
applied. This is probably the result of using a log that was generated  against a cold backup image of the database.
Action: Find the log that was generated by this copy of the database and give that  filename to recovery.

ORA-00366: log string of thread string - checksum error in the file header

ORA-00366: log string of thread string - checksum error in the file header
Cause: The file header for the redo log contains a checksum that does not match  the value calculated
from the file header as read from disk. This means the file  header is corrupted
Action: Find and install correct version of log or reset logs.

ORA-00367: checksum error in log file header

ORA-00367: checksum error in log file header
Cause: The file header for the redo log contains a checksum that does not match  the value calculated
from the file header as read from disk. This means the file  header is corrupted
Action: Find the correct file and try again.

ORA-00362: member is required to form a valid logfile in group string

ORA-00362: member is required to form a valid logfile in group string
Cause: A request to drop a logfile member was denied because it would remove  data required to
form a complete logfile.
Action: If desired, delete the entire log (after archiving if required), by using  DROP LOGFILE;

ORA-00363: log is not the archived version

ORA-00363: log is not the archived version
Cause: d by failing to list the current log of an enabled thread in a CREATE  CONTROLFILE
command.
Action: Find the archived version of the log and supply its name. If this is media  recovery immediately following a CREATE CONTROLFILE, be sure the current  log for this thread was included.

ORA-00364: cannot write header to new log member

ORA-00364: cannot write header to new log member
Cause: An i/o error occurred when attempting to write the header to a log  member that is being
added to an existing group.
Action: See accompanying errors. Fix problem or use another file.

ORA-00360: not a logfile member: string

ORA-00360: not a logfile member: string
Cause: A filename was given to drop logfile member that is not a part of the  database, or which is a
data file.
Action: Supply a valid logfile member name.

ORA-00361: cannot remove last log member string for group string

ORA-00361: cannot remove last log member string for group string
Cause: An attempt has been made to remove the last member of a log file group.

Action: If desired, delete the entire log, by using DROP LOGFILE.

ORA-00358: Too many file members specified - the maximum is string

ORA-00358: Too many file members specified - the maximum is string
Cause: A create or alter statement specified too many members in a parenthesised  file list.

Action: Specify a number of file members that is within the port-defined limit.

ORA-00359: logfile group string does not exist

ORA-00359: logfile group string does not exist
Cause: An add logfile member or drop logfile request specified a logfile group  number that does not
exist.
Action: Check the configuration of the log files and reissue the command.

ORA-00357: too many members specified for log file - the maximum is string

ORA-00357: too many members specified for log file - the maximum is string
Cause: An add logfile or add logfile member command would result in a log with  too many
members. The number of members is set when the database is created.
Action: Use fewer log file members.

ORA-00356: inconsistent lengths in change description

ORA-00356: inconsistent lengths in change description
Cause: A change record in the redo log contains lengths that do not add up to a  consistent value. The
log is corrupted in some way.
Action: Do recovery with a good version of the log or do time based recovery up  to the indicated time.

ORA-00355: change numbers out of order

ORA-00355: change numbers out of order
Cause: A change number found in the redo log is lower than a previously  encountered change
number. The log is corrupted in some way. The corruption  may be at the earlier change or at this one.
Action: Do recovery with a good version of the log or do time based recovery up  to the indicated time.

ORA-00354: corrupt redo log block header

ORA-00354: corrupt redo log block header
Cause: The block header on the redo block indicated by the accompanying error,  is not reasonable.

Action: Do recovery with a good version of the log or do time based recovery up  to the indicated time. If this happens when archiving, archiving of the problem log  can be skipped by clearing the log with the UNARCHIVED option. This must be  followed by a backup of every datafile to insure recoverability of the database.

ORA-00353: log corruption near block string change string time string

ORA-00353: log corruption near block string change string time string
Cause: Some type of redo log corruption has been discovered. This error describes  the location of
the corruption. Accompanying errors describe the type of  corruption.
Action: Do recovery with a good version of the log or do incomplete recovery up  to the indicated change or time.

ORA-00351: recover-to time invalid

ORA-00351: recover-to time invalid
Cause: The time specified in a recover-until statement must be after January 1st  1,988

Action: Specify a time after January 1st 1988.

ORA-00352: all logs for thread string need to be archived - cannot enable

ORA-00352: all logs for thread string need to be archived - cannot enable
Cause: Attempting to enable a thread with all logs needing to be archived, and  media recovery has
been enabled. There is no log that can be made the new  current log for the thread.
Action: Archive a log for the thread or disable media recovery.

ORA-00349: failure obtaining block size for "string"

ORA-00349: failure obtaining block size for "string"
Cause: The operating system was unable to determine the blocksize for the given  filename.

Action: Consult the accompanying error message, and correct the device or  specify another filename.

ORA-00350: log string of instance string (thread string) needs to be archived

ORA-00350: log string of instance string (thread string) needs to be archived
Cause: The command cannot be done because the log has not been archived, and  media recovery
has been enabled.
Action: Archive the log or disable media recovery. If the command supports an  UNARCHIVED option then it can be used. However this may result in making  backups unuseable, and forcing the drop of some offline files.

ORA-00347: log string of thread string, expected block size string doesn"t match string

ORA-00347: log string of thread string, expected block size string doesn"t match  string
Cause: On header read the blocksize indicated in the control file did not match the  blocksize
contained in the log file.
Action: Restore correct file or reset logs.

ORA-00348: single-process redo failure. Must abort instance

ORA-00348: single-process redo failure. Must abort instance
Cause: A failure occurred during a critical portion of the log code during single  process operation.
This error does not occur during normal multi-process  operation.
Action: Shutdown abort and warmstart the database.

ORA-00344: unable to re-create online log "string"

ORA-00344: unable to re-create online log "string"

Cause: An I/O failure occurred when attempting to re-create an online as part of  either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR  LOGFILE command.

Action: Correct the file/device as indicated by accompanying errors.

ORA-00345: redo log write error block string count string

ORA-00345: redo log write error block string count string
Cause: An IO error has occurred while writing the log

Action: Correct the cause of the error, and then restart the system. If the log is lost,  apply media/incomplete recovery.

ORA-00346: log member marked as STALE

ORA-00346: log member marked as STALE
Cause: A log file member no longer is complete.

Action: Correct the underlying problem by referring to the other error messages  found with this one.

ORA-00341: log string of thread string, wrong log # string in header

ORA-00341: log string of thread string, wrong log # string in header
Cause: The internal information in an online log file does not match the control  file.

Action: Restore correct file or reset logs.

ORA-00342: archived log does not have expected resetlogs SCN string

ORA-00342: archived log does not have expected resetlogs SCN string
Cause: Recovery was given a log that does not belong to current incarnation or  one of the parent
incarnation. There should be another log that contains the correct  redo.
Action: Supply the correct log file.

ORA-00343: too many errors, log member closed

ORA-00343: too many errors, log member closed

Cause: The maximum number of errors on this log member has been exceeded.

Action: Correct the underlying problem by referring to the other error messages  found with this one.

ORA-00339: archived log does not contain any redo

ORA-00339: archived log does not contain any redo

Cause: The archived log is not the correct log. It is a copy of a log file that has  never been used for redo generation, or was an online log being prepared to be the  current log.


Action: Restore the correct log file.

ORA-00340: IO error processing online log string of thread string

ORA-00340: IO error processing online log string of thread string
Cause: An IO error occurred on the named online log.

Action: Restore accessibility to file, or restore file from backup.

ORA-00338: log string of thread string is more recent than control file

ORA-00338: log string of thread string is more recent than control file
Cause: The control file change sequence number in the log file is greater than the  number in the
control file. This implies that the wrong control file is being used.  Note that repeatedly causing this error can make it stop happening without  correcting the real problem. Every attempt to open the database will advance the  control file change sequence number until it is great enough.
Action: Use the current control file or do backup control file recovery to make the  control file current. Be sure to follow all restrictions on doing a backup control file  recovery.

ORA-00337: log file "string" does not exist and no size specified

ORA-00337: log file "string" does not exist and no size specified
Cause: An attempt to add a log found neither an existing file nor a size for  creating the file.

Action: Specify a size for the log file.

ORA-00336: log file size string blocks is less than minimum string blocks

ORA-00336: log file size string blocks is less than minimum string blocks
Cause: The log file size as specified in create database is too small.

Action: Increase the log file size.

ORA-00334: archived log: "string"

ORA-00334: archived log: "string"
Cause: Reporting filename for details of another error

Action: See associated error messages

ORA-00335: online log string: No log with this number, log does not exist

ORA-00335: online log string: No log with this number, log does not exist
Cause: Reporting filename for details of another error

Action: See associated error messages

ORA-00332: archived log is too small - may be incompletely archived

ORA-00332: archived log is too small - may be incompletely archived
Cause: The log is smaller than the space allocated in it. May be the result of a  shutdown abort while it was being written by the archiver.


Action: Get a complete version of this log and use it for recovery. There should  either be an online version of it or a copy that was successfully archived.

ORA-00333: redo log read error block string count string

ORA-00333: redo log read error block string count string
Cause: An IO error occurred while reading the log described in the accompanying  error.

Action: Restore accessibility to file, or get another copy of the file.

ORA-00330: archived log ends at change string, need change string

ORA-00330: archived log ends at change string, need change string
Cause: The archived log is not the correct log. A later log is needed.

Action: Restore the correct log file.

ORA-00331: log version string incompatible with ORACLE version string

ORA-00331: log version string incompatible with ORACLE version string
Cause: The log was written by incompatible version of Oracle.

Action: Recover the database with the compatible software, shut it down cleanly,  then restart with current software.

ORA-00329: archived log begins at change string, need change string

ORA-00329: archived log begins at change string, need change string

Cause: The archived log is not the correct log. An earlier log is needed.

Action: Restore the correct log file.

ORA-00328: archived log ends at change string, need later change string

ORA-00328: archived log ends at change string, need later change string

Cause: The archived log supplied for recovery was generated before the log that is  needed. Can
not use the log for applying redo.

Action: Find correct archived log.

ORA-00326: log begins at change string, need earlier change string

ORA-00326: log begins at change string, need earlier change string
Cause: The archived log supplied for recovery was generated after the log that is  needed. Can not
yet use the log for applying redo.
Action: Find correct archived log.

ORA-00327: log string of thread string, physical size string less than needed string

ORA-00327: log string of thread string, physical size string less than needed string

Cause: A log file has shrunk in size. This is likely to have been caused by operator  or operating
system error.

Action: Restore the log file from backup. If backup is not available, drop this log  and re-create. If the database was shut down cleanly, no further action should be  required; otherwise incomplete recovery may be required.

ORA-00324: log file "string" translated name "string" too long, string characters exceeds

ORA-00324: log file "string" translated name "string" too long, string characters  exceeds string limit
Cause: the translated name for a log file is too long.

Action: Choose a untranslated name that yields a shorter translated name.

ORA-00325: archived log for thread string, wrong thread # string in header

ORA-00325: archived log for thread string, wrong thread # string in header
Cause: The archived log is corrupted or for another thread. Can not use the log for  applying redo.

Action: Find correct archived log.

ORA-00322: log string of thread string is not current copy

ORA-00322: log string of thread string is not current copy
Cause: Check of log file header at database open found that an online log appears  to be an
incorrectly restored backup.
Action: Restore correct file or reset logs.

ORA-00323: Current log of thread string not useable and all others need archiving

ORA-00323: Current log of thread string not useable and all others need archiving
Cause: Attempt to open thread failed because it is necessary to switch redo  generation to another
online log, but all the other logs need to be archived before  they can be used.
Action: Archive the logs for the thread then retry open.

ORA-00319: log string of thread string has incorrect log reset status

ORA-00319: log string of thread string has incorrect log reset status
Cause: Check of log file header at database open found that an online log has log  reset data that is
different from the control file. The log is probably an incorrectly  restored backup.
Action: Restore correct file or reset logs.

ORA-00320: cannot read file header from log string of thread string

ORA-00320: cannot read file header from log string of thread string
Cause: The file is not available.

Action: Restore the log file.

ORA-00321: log string of thread string, cannot update log file header

ORA-00321: log string of thread string, cannot update log file header
Cause: Cannot write to the log file.

Action: Restore the access to the file.

ORA-00317: file type string in header is not log file

ORA-00317: file type string in header is not log file
Cause: This is not an archived log file.

Action: Find the correct file and try again.

ORA-00318: log string of thread string, expected file size string doesn"t match string

ORA-00318: log string of thread string, expected file size string doesn"t match string
Cause: On header read the file size indicated in the control file did not match the  file size contained
in the log file.
Action: Restore correct file or reset logs.

ORA-00315: log string of thread string, wrong thread # string in header

ORA-00315: log string of thread string, wrong thread # string in header
Cause: The online log is corrupted or is an old version.

Action: Find and install correct version of log or reset logs.

ORA-00316: log string of thread string, type string in header is not log file

ORA-00316: log string of thread string, type string in header is not log file
Cause: The online log is corrupted or is an old version.

Action: Find and install correct version of log or reset logs.

ORA-00313: open failed for members of log group string of thread string

ORA-00313: open failed for members of log group string of thread string
Cause: The online log cannot be opened. May not be able to find file.

Action: See accompanying errors and make log available.

ORA-00314: log string of thread string, expected sequence# string doesn"t match string

ORA-00314: log string of thread string, expected sequence# string doesn"t match  string
Cause: The online log is corrupted or is an old version.

Action: Find and install correct version of log or reset logs.

ORA-00311: cannot read header from archived log

ORA-00311: cannot read header from archived log
Cause: An I/O error occurred when attempting to read the log file header from  the specified
archived redo log file.

Action: Other messages will accompany this message. See the associated  messages for the appropriate action to take.

ORA-00312: online log string thread string: string

ORA-00312: online log string thread string: string
Cause: This message reports the filename for details of another message.

Action: Other messages will accompany this message. See the associated  messages for the appropriate action to take.

ORA-00310: archived log contains sequence string; sequence string required

ORA-00310: archived log contains sequence string; sequence string required
Cause: The archived log is out of sequence, probably because it is corrupted or the  wrong redo log
filename was specified
Action: Specify the correct redo log file; then retry the operation.

ORA-00309: log belongs to wrong database

ORA-00309: log belongs to wrong database
Cause: The system cannot access the archived redo log because it belongs to  another database.

Action: Specify the correct redo log file, then retry the operation.

ORA-00307: requested INSTANCE_NUMBER out of range- maximum is string

ORA-00307: requested INSTANCE_NUMBER out of range- maximum is string
Cause: The initialization parameter INSTANCE_NUMBER specified a number  that was out of
range.
Action: Change INSTANCE_NUMBER to a valid range and restart the instance.  The minimum value is one and the maximum value is the lower of the operating  system-specific maximum or the MAXINSTANCES option specified in the  CREATE DATABASE statement. See also your operating system-specific Oracle  documentation.

ORA-00308: cannot open archived log string

ORA-00308: cannot open archived log string
Cause: The system cannot access a required archived redo log file.

Action: Check that the off line log exists, the storage device is online, and the  archived file is in the correct location. Then attempt to continue recovery or restart  the recovery session.

ORA-00305: log string of thread string inconsistent; belongs to another database

ORA-00305: log string of thread string inconsistent; belongs to another database
Cause: The database ID in the redo log file does not match the database ID in the  control file. This
redo log file is not from the current database.
Action: Specify the correct redo log file, then retry the operation.

ORA-00306: limit of string instances in this database

ORA-00306: limit of string instances in this database
Cause: Starting this instance would exceed the maximum number of instances  allowed for this
database. This message occurs only with STARTUP shared and  multiple instances.
Action: You cannot start more than the lower of a) port-specific limit as to the  number of instances b) the number of instances specified at create-database time

ORA-00304: requested INSTANCE_NUMBER is busy

ORA-00304: requested INSTANCE_NUMBER is busy
Cause:An instance tried to start by using a value of the initialization parameter
INSTANCE_NUMBER that is already in use
Action: Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number  c) wait for instance recovery to complete on the instance with this number.

ORA-00303: cannot process Parallel Redo

ORA-00303: cannot process Parallel Redo
Cause: A redo log containing Parallel Redo has been detected. The current Oracle  release cannot
process this format of redo.
Action: Use a later release that supports Parallel Redo. to process this log.

ORA-00301: error in adding log file string - file cannot be created

ORA-00301: error in adding log file string - file cannot be created
Cause: The creation of the redo log file failed

Action: Check: 1) there is enough storage space on the device 2) the name of the  file is valid 3) the device is online 4) an IO error occurred Also, it is possible  REUSE was specified on the command line and a file of the incorrect size exists.  Either do not specify REUSE or use a file of the correct size.

ORA-00302: limit of string logs exceeded

ORA-00302: limit of string logs exceeded
Cause: The maximum number of redo log files has been exceeded.

Action: Use the CREATE CONTROLFILE command with a larger value for  MAXLOGFILES if the compatibility is lower than 10.2.0. Otherwise, allocate more  storage space for the control file.

ORA-00299: must use file-level media recovery on data file string

ORA-00299: must use file-level media recovery on data file string
Cause: The control file does not contain an entry for this file, so block media  recovery cannot be
done.
Action: Restore the data file and perform file-level media recovery.

ORA-00300: illegal redo log block size string specified - exceeds limit of string

ORA-00300: illegal redo log block size string specified - exceeds limit of string
Cause: The specified block size of the redo log is greater than the maximum block  size for the
operating system.
Action: Create the redo log on a device with a smaller block size

ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE

ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE  START
Cause: The RECOVER DATAFILE START command was issued, but no  RECOVER DATAFILE
LIST commands had been issued. This only happens when  doing recovery with Recovery Manager, and is an internal error in Recovery  Manager, because Recovery Manager should always issue RECOVER DATAFILE  LIST before RECOVER DATAFILE START.
Action: Contact customer support

ORA-00298: Missing or invalid attribute value

ORA-00298: Missing or invalid attribute value
Cause: A non-zero integer value is required when the following keyword  attributes are specified:
TIMEOUT, EXPIRE, DELAY, NEXT
Action: Correct the syntax and retry the command.

ORA-00295: datafile/tempfile number string is invalid- must be between 1 and string

ORA-00295: datafile/tempfile number string is invalid- must be between 1 and  string
Cause: An invalid file number was specified.

Action: Specify a valid datafile or tempfile number and retry the operation.