Shulou(Shulou.com)05/31 Report--

This article introduces you how to handle Oracle exceptions, the content is very detailed, interested friends can refer to, hope to be helpful to you.

1. Advantages of exception

If there are no exceptions, in the program, you should check the success or failure of each command, such as

BEGIN

SELECT...

-- check for'no data found' error

SELECT...

-- check for'no data found' error

SELECT...

-- check for'no data found' error

The disadvantage of this method is that error handling is not separated from normal processing, poor readability, using exceptions, it is convenient to handle errors, and exception handlers are separated from normal transaction logic, which improves readability, such as

BEGIN

SELECT...

SELECT...

SELECT...

...

EXCEPTION

WHEN NO_DATA_FOUND THEN-- catches all'no data found' errors

2. Classification of anomalies

There are two types of exceptions, an internal exception and a custom exception for the user, which are ORACLE errors returned to PL/SQL blocks during execution or errors caused by an operation of PL/SQL code, such as a divisor of zero or a memory overflow. User-customized exceptions are defined by the developer display and pass information in the PL/SQL block to control error handling for the application.

Whenever PL/SQL violates the ORACLE principle or goes beyond the principle of system dependency, an internal exception is implicitly generated. Because every ORACLE error has a number and exceptions are handled by name in PL/SQL, ORACLE provides predefined internal exceptions. For example, the ORACLE exception NO_DATA_FOUND generated when the SELECT INTO statement does not return a row. For predefined exceptions, the most commonly used exceptions are listed as follows:

Exception oracle error sqlcode value condition

The no_data_found ora-01403 + 100select into statement returned no qualified records.

Too_many_rows ora-01422-1422 select into statement eligible records have multiple returns

Dup_val_on_index ora-00001-1 for a column in a database table, the column has been restricted to a unique index, and the program attempts to store two duplicate values

This exception occurs when value_error ora-06502-6502 converts a character type, intercepts, or is limited in length. If a character is assigned to a variable and the length of the variable declaration is shorter than that character, the exception is thrown.

Storage_error ora-06500-6500 memory overflow

Zero_divide ora-01476-1476 divisor is zero

Case_not_found ora-06592-6530 there are no matching conditions for selecting case statements, and no else statements capture other conditions

The cursor_already_open ora-06511-6511 program attempted to open a cursor that was already open

The timeout_on_resource ora-00051-51 system is waiting for a certain resource and the time has timed out.

If you want to handle unnamed internal exceptions, you must use an OTHERS exception handler or PRAGMA EXCEPTION_INIT. The PRAGMA is controlled by the compiler, or comments to the compiler. PRAGMA handles it at compile time, not at run time. EXCEPTION_INIT tells the compiler to combine the exception name with the ORACLE error code so that any internal exception can be referenced by name, and an appropriate exception handler can be written for the exception by name.

The syntax for using EXCEPTION_INIT in a subroutine is as follows:

PRAGMA EXCEPTION_INIT (exception_name,-Oracle_error_number)

In this syntax, the exception name is the declared exception, and the following example is its usage:

DECLARE

Deadlock_detected EXCEPTION

PRAGMA EXCEPTION_INIT (deadlock_detected,-60)

BEGIN

...-- Some operation that causes an ORA-00060 error

EXCEPTION

WHEN deadlock_detected THEN

-- handle the error

END

For user-defined exceptions, you can only declare the exception in the declaration section of the PL/SQL block. The name of the exception is introduced by the EXCEPTION keyword:

Reserved_loaned Exception

After the exception is generated, the control is passed to the exception part of the subroutine, and the exception is transferred to the respective exception control block. The following structure must be used in the code to handle the error:

Exception

When exception1 then

Sequence of statements

When exception2 then

Sequence of statements

When others then

3. Exception thrown

An exception is thrown in three ways

1. Through the PL/SQL runtime engine

two。 Use the RAISE statement

3. Call RAISE_APPLICATION_ERROR stored procedure

When an error occurs in the database or PL/SQL runtime, an exception is automatically thrown by the PL/SQL runtime engine. Exceptions can also be thrown through the RAISE statement

RAISE exception_name

Explicitly throwing exceptions is an idiom for programmers to handle declared exceptions, but RAISE is not limited to declared exceptions; it can throw any exception. For example, if you want to detect new runtime exception handlers with TIMEOUT_ON_RESOURCE errors, you simply use the following statement in your program:

RAISE TIMEOUT_ON_RESOUCE

For example, in the following example of order input, if the order is less than the inventory quantity, an exception is thrown, and the exception is caught and handled.

DECLARE

Inventory_too_low EXCEPTION

-other declaration statements

BEGIN

IF order_rec.qty > inventory_rec.qty THEN

RAISE inventory_too_low

END IF

EXCEPTION

WHEN inventory_too_low THEN

Order_rec.staus:='backordered'

END

The RAISE_APPLICATION_ERROR built-in function is used to throw an exception and give the exception an error number and an error message. The default error number for a custom exception is + 1, and the default information is User_Defined_Exception. The RAISE_APPLICATION_ERROR function can be called in the execution and exception parts of the pl/sql block, explicitly throwing a named exception with a special error number. Raise_application_error (error_number,message [, true,false]))

Error numbers range from-20000 to-20999. The error message is a text string with a maximum of 2048 bytes. TRUE and FALSE indicate whether to add (TRUE) to the error heap (ERROR STACK) or overwrite (overwrite) the error heap (FALSE). The default is FALSE.

The following code is shown:

IF product_not_found THEN

RAISE_APPLICATION_ERROR (- 20123 heroine Invald product code' TRUE)

END IF

4. Exception handling

The exception part of the PL/SQL program block contains the code for the program to handle the error. When the exception is thrown, an exception trap occurs automatically, and the program control leaves the execution part to the exception part. Once the program enters the exception part, it can not return to the execution part of the same block. Here is the general syntax for the exception section:

EXCEPTION

WHEN exception_name THEN

Code for handing exception_name

[WHEN another_exception THEN

Code for handing another_exception]

[WHEN others THEN

Code for handing any other exception.]

The user must design exception handling code for each exception in a separate WHEN substring, and the WHEN OTHERS substring must be placed at the end as the default handler to handle exceptions that are not explicitly handled. When an exception occurs, the control goes to the exception section, ORACLE looks for the corresponding WHEN..THEN statement of the current exception, catches the exception, and the code after the THEN is executed. If the error trap code just exits the corresponding nested block, then the program will continue to execute the statements following the internal block END. If no corresponding exception trap is found, WHEN OTHERS is executed. There is no limit on the number of WHEN substrings in the exception section.

EXCEPTION

WHEN inventory_too_low THEN

Order_rec.staus:='backordered'

Replenish_inventory (inventory_nbr= >

Inventory_rec.sku,min_amount= > order_rec.qty-inventory_rec.qty)

WHEN discontinued_item THEN

-- code for discontinued_item processing

WHEN zero_divide THEN

-- code for zero_divide

WHEN OTHERS THEN

-- code for any other exception

END

When the exception is thrown, the control goes to the exception part unconditionally, which means that the control cannot return to the location where the exception occurred, and when the exception is handled and resolved, the control returns to the next statement in the execution part of the previous layer.

BEGIN

DECLARE

Bad_credit exception

BEGIN

RAISE bad_credit

-- an exception occurs, controlling the turn

EXCEPTION

WHEN bad_credit THEN

Dbms_output.put_line ('bad_credit')

END

-- after handling the bad_credit exception, the control is transferred here

EXCEPTION

WHEN OTHERS THEN

-- Control will not be transferred here from the bad_credit exception

-- because bad_credit has been processed

END

When an exception occurs, when there is no exception handler inside the block, control will be transferred or propagated to the exception handling part of the upper block.

BEGIN

DECLARE-Internal block start

Bad_credit exception

BEGIN

RAISE bad_credit

-- an exception occurs, controlling the turn

EXCEPTION

WHEN ZERO_DIVIDE THEN-cannot handle bad_credite exceptions

Dbms_output.put_line ('divide by zero error')

END-ends the internal block

The control cannot get here because the exception has not been resolved

-- abnormal part

EXCEPTION

WHEN OTHERS THEN

-- since bad_credit is not resolved, control will be transferred here

END

5. Abnormal propagation

Unhandled exceptions will propagate to the outside along the detection exception calling program, when the exception is handled and resolved or when the propagation stops at the outermost layer of the program. The exception thrown in the declaration section transfers control to the exception part of the previous layer.

BEGIN

Executable statements

BEGIN

Today DATE:='SYADATE';-ERRROR

BEGIN-- Internal block start

Dbms_output.put_line ('this line will not execute')

EXCEPTION

WHEN OTHERS THEN

Exceptions will not be handled here

End of END;-- internal block

EXCEPTION

WHEN OTHERS THEN

Handling exceptions

END

-

-

In addition to handling the automatic generation of system exceptions by the oracle system, you can use raise to manually generate errors.

L Raise exception

L Raise package.exception

L Raise

These are three ways to use raise. The first is used to generate exceptions defined in the current program or system exceptions in standard.

Declare

Invalid_id exception

Id_values varchar (2)

Begin

Id_value:=id_for ('smith')

If substr (id_value,1,1)! ='x'

Then

Raise invalid_id

End if

Exception

When invalid_id

Then

Dbms_output.put_line ('this is an invalid idlers')

End

This is an example of generating custom exceptions, as well as system exceptions:

Declare

Employee_id_in number

Begin

Select employee_id into employee_id_in from employ_list where employee_name=&n

If employee_id_in=0

Then

Raise zero_devided

End if

Exception

When zero_devided

Then

Dbms_output.put_line ('Wrongaming')

End

Some exceptions are defined in non-standard packages, such as UTL_FILE, DBMS_SQL, and programmer-created package exceptions. You can use the second use of raise to generate exceptions.

If day_overdue (isbn_in, browser_in) > 365

Then

Raise overdue_pkg.book_is_lost

End if

In the last form of raise, there are no parameters. This occurs only when you want to pass the current exception to an external program.

Exception

When no_data_found

Then

Raise

End

Pl.sql uses the raise_application_error procedure to generate an exception with a specific description. When using this procedure, the current program is aborted and the input and output parameters are set to the original values, but any changes made by DML to the database are retained and can be rolled back later with the rollback command. Here is the prototype of the process:

Procedure raise_application_error (

Num binary_integer

Msg varchar2

Keeperrorstack Boolean default false

)

Num is any number between-20999 and-20000 (but in fact, DBMS_OUPUT and DBMS_DESCRIBLE packages use numbers from-20005 to-20000); msg is a description language of less than 2K characters, and any characters greater than 2K will be discarded automatically; keeperrorstack defaults to false, which means to clear the exception stack and put the current exception into the stack, and press the current exception directly into the stack if true is specified.

CREATE OR REPLACE PROCEDURE raise_by_language (code_in IN PLS_INTEGER)

IS

L_message error_table.error_string%TYPE

BEGIN

SELECT error_string

INTO l_message

FROM error_table, v$nls_parameters v

WHERE error_number = code_in

AND string_language = v.VALUE

AND v.parameter = 'NLS_LANGUAGE'

RAISE_APPLICATION_ERROR (code_in, l_message)

END

ORACL internal exception:

ORA-00001: violation of unique constraints (.)

ORA-00017: request a session to set trace events

ORA-00018: maximum number of sessions exceeded

ORA-00019: maximum number of session licenses exceeded

ORA-00020: maximum number of processes exceeded ()

ORA-00021: the session is attached to some other process; the session cannot be converted

ORA-00022: invalid session ID; access denied

ORA-00023: private memory used by the session reference process; cannot detach the session

ORA-00024: registration from multiple processes is not allowed in single process mode

ORA-00025: unable to assign

ORA-00026: missing or invalid session ID

ORA-00027: cannot delete the current session

ORA-00028: your session has been deleted

ORA-00029: session is not a user session

ORA-00030: user session ID does not exist.

ORA-00031: marks the session to be deleted

ORA-00032: invalid session migration password

ORA-00033: the current session has an empty migration password

ORA-00034: cannot be in the current PL/SQL session

ORA-00035: LICENSE_MAX_USERS cannot be less than the number of current users

ORA-00036: the maximum value that exceeds the recursive SQL () level

ORA-00037: cannot convert to a session that belongs to a different server group

ORA-00038: unable to create session: server group belongs to another user

ORA-00050: an operating system error occurred while getting enlisted

ORA-00051: timeout waiting for resources

ORA-00052: exceeds the maximum number of enrollment resources ()

ORA-00053: exceeds the maximum number of enrollment

ORA-00054: resource is busy, request to specify NOWAIT

ORA-00055: the maximum number of DML locks exceeded

ORA-00056: object'.' The DDL lock on the is suspended in incompatible mode

ORA-00057: maximum number of temporary table locks exceeded

ORA-00058: DB_BLOCK_SIZE must be to install this database (not)

ORA-00059: exceeds the maximum value of DB_FILES

ORA-00060: deadlock detected while waiting for resources

ORA-00061: another routine sets a different DML_LOCKS

ORA-00062: unable to get DML full table lock; DML_LOCKS is 0

ORA-00063: the maximum number of LOG_FILES exceeded

ORA-00064: the object is too large to be assigned to this Omax S (,)

ORA-00065: initialization of FIXED_DATE failed

ORA-00066: LOG_FILES is but needs to be compatible

ORA-00067: the value is not valid for the parameter; it must be at least

ORA-00068: the value is not valid for the parameter and must be between and

ORA-00069: unable to get lock-table locking disabled

ORA-00070: invalid command

ORA-00071: the process number must be between 1 and

ORA-00072: process "" is not active

ORA-00073: used when the command is between and parameters

ORA-00074: no process specified

ORA-00075: no process found in this routine ""

ORA-00076: dump not found

ORA-00077: invalid dump

ORA-00078: cannot dump variables by name

ORA-00079: no variables found

ORA-00080: the global zone specified by the hierarchy is invalid

ORA-00081: address range [,) is not readable

The memory size of ORA-00082: is not within the valid set [1], [2], [4].

ORA-00083: warning: SGA that may damage the mapping

ORA-00084: global zone must be PGA, SGA or UGA

ORA-00085: the current call does not exist

ORA-00086: user call does not exist

ORA-00087: commands cannot be executed on remote routines

ORA-00088: the shared server cannot execute the command

ORA-00089: invalid routine number in the ORADEBUG command

ORA-00090: failed to allocate memory to cluster database ORADEBUG command

ORA-00091: LARGE_POOL_SIZE must at least be

ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC

ORA-00093: must be between and

ORA-00094: requires an integer value

ORA-00096: the value is not valid for the parameter, it must come from between

ORA-00097: using the Oracle SQL feature is not in the SQL92 level

ORA-00099: timeout occurred while waiting for resources, possibly due to PDML deadlock

ORA-00100: no data found

ORA-00101: the description of the system parameter DISPATCHERS is invalid

ORA-00102: the scheduler cannot use the network protocol

ORA-00103: invalid network protocol; standby for scheduler

ORA-00104: deadlock detected; all public servers locked waiting resources

ORA-00105: scheduling mechanism with no network protocol configured

ORA-00106: unable to start / shut down the database when connecting to the scheduler

ORA-00107: unable to connect to the ORACLE listener process

ORA-00108: unable to set scheduler to connect synchronously

ORA-00111: not all servers are started because the number of servers is limited to

ORA-00112: only up to (specified) schedulers can be created

ORA-00113: the protocol name is too long

ORA-00114: missing the value of the system parameter SERVICE_NAMES

ORA-00115: connection denied; scheduler connection table full

ORA-00116: SERVICE_NAMES name is too long

ORA-00117: the value of the system parameter SERVICE_NAMES is out of range

ORA-00118: the value of the system parameter DISPATCHERS is out of range

ORA-00119: invalid description of system parameter

ORA-00120: scheduling mechanism is not enabled or installed

ORA-00121: SHARED_SERVERS specified in the absence of DISPATCHERS

ORA-00122: unable to initialize network configuration

ORA-00123: idle public server terminates

ORA-00124: DISPATCHERS specified in the absence of MAX_SHARED_SERVERS

ORA-00125: connection denied; invalid presentation

ORA-00126: connection denied; invalid duplicate

ORA-00127: scheduling process does not exist

ORA-00128: this command requires a scheduling process name

ORA-00129: listener address verification failed''

ORA-00130: invalid listener address''

ORA-00131: network protocols do not support registration''

ORA-00132: incorrect syntax or unresolvable network name''

ORA-00150: duplicate transaction ID

ORA-00151: invalid transaction ID

ORA-00152: the current session does not match the requested session

ORA-00153: internal error in the XA library

ORA-00154: protocol error in transaction monitor

ORA-00155: cannot perform work outside of a global transaction

ORA-00160: the global transaction length exceeds the maximum ()

ORA-00161: illegal branch length of transaction (maximum allowed length is)

ORA-00162: the length of the external dbid exceeds the maximum ()

ORA-00163: the internal database name length exceeds the maximum ()

ORA-00164: independent transactions are not allowed in distributed transactions

ORA-00165: portable distributed autonomous transformations for remote operations are not allowed

ORA-00200: unable to create control file

ORA-00201: the control file version is incompatible with the ORACLE version

ORA-00202: control file:''

ORA-00203: using the wrong control file

ORA-00204: error reading control file (block, # block)

ORA-00205: error identifying control file. For more information, please check the warning log.

ORA-00206: error writing control file (block, # block)

ORA-00207: control files cannot be used in the same database

ORA-00208: the number of names of control files exceeds the limit

ORA-00209: control file block size mismatch. For more information, check the warning log.

ORA-00210: unable to open the specified control file

ORA-00211: the control file does not match the previous control file

ORA-00212: the block size is less than the required minimum size (bytes)

ORA-00213: the control file cannot be reused; the original file size is required

ORA-00214: control file''version and file' 'version is inconsistent

ORA-00215: at least one control file must exist

ORA-00216: unable to resize control files migrated from 8.0.2

ORA-00217: migration from 9.0.1 failed to resize the control file

ORA-00218: the block size of the control file does not match DB_BLOCK_SIZE ()

ORA-00219: the required control file size exceeds the maximum allowed

ORA-00220: the control file is not installed in the first routine. For more information, check the warning log.

ORA-00221: error writing control file

ORA-00222: the action will reuse the name of the currently installed control file

ORA-00223: invalid translation file or incorrect version

ORA-00224: control file resizing attempt to use illegal record type ()

ORA-00225: the expected size of the control file is different from the actual size

ORA-00226: operations are not allowed when the standby control file is opened

ORA-00227: damaged blocks detected in the control file: (blocks, # blocks)

ORA-00228: the backup control file name length exceeds the maximum length

ORA-00229: operation is not allowed: snapshot control files have been suspended to join the queue

ORA-00230: operation is not allowed: cannot use snapshot control file to join the queue

ORA-00231: snapshot control file is not named

ORA-00232: snapshot control file does not exist, corrupted or cannot be read

ORA-00233: control file copy is corrupted or cannot be read

ORA-00234: error identifying or opening snapshot or replication control file

ORA-00235: control file fixed tables are inconsistent due to concurrent updates

ORA-00236: snapshot operation is not allowed: suspended control files are backup files

ORA-00237: snapshot operation is not allowed: control file newly created

ORA-00238: the action reuses the file names that are part of the database

ORA-00250: the archiver is not started

ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as a string

ORA-00252: the log is empty on the thread and cannot be archived

ORA-00253: the character limit is limited, and the archive destination string exceeds this limit

ORA-00254: error archiving control string''

ORA-00255: error archiving log (thread, sequence #)

ORA-00256: the archive destination string cannot be translated

ORA-00257: archiver error. Limited to internal connections until released

ORA-00258: manual archives in NOARCHIVELOG mode must identify logs

ORA-00259: log (open thread) is the current log and cannot be archived

ORA-00260: unable to find online log sequence (thread)

ORA-00261: archiving or modifying logs (threads)

ORA-00262: current log (shutdown thread) cannot be switched

ORA-00263: threads have no records to archive

ORA-00264: no recovery required

ORA-00265: routine recovery is required, ARCHIVELOG mode cannot be set

ORA-00266: archive log file name is required

ORA-00267: no archive log file name is required

ORA-00268: the specified log file does not exist''

ORA-00269: the specified log file is part of the thread (not)

ORA-00270: error creating archive log

ORA-00271: no logs need to be archived

ORA-00272: error writing archive log

ORA-00273: media recovery of unrecorded directly loaded data

ORA-00274: illegal recovery option

ORA-00275: media recovery has started

ORA-00276: the CHANGE keyword is specified but no change number is given

ORA-00277: illegal option for the UNTIL recovery flag

ORA-00278: log files are no longer required for this restore

ORA-00279: changes (during build) are required for threads

ORA-00280: changes are made in sequence # for threads

ORA-00281: media recovery cannot be performed using the scheduling process

ORA-00282: UPI call is not supported, please use ALTER DATABASE RECOVER

ORA-00283: the recovery session was cancelled due to an error

ORA-00284: the recovery session is still in progress

ORA-00285: TIME is not given as a string constant

ORA-00286: no members are available, or members have no valid data

ORA-00287: the specified change number was not found (in thread)

ORA-00288: to continue with the recovery, type ALTER DATABASE RECOVER CONTINUE

ORA-00289: recommended:

ORA-00290: an archiving error occurred in the operating system. Please refer to the following error

ORA-00291: the PARALLEL option requires a numeric value

ORA-00292: parallel recovery is not installed

ORA-00293: control files are out of sync with redo logs

ORA-00294: invalid archive log format ID''

ORA-00295: invalid data file number, must be between 1 and

ORA-00296: the maximum number of files that have been exceeded by RECOVER DATAFILE LIST ()

ORA-00297: RECOVER DATAFILE LIST must be specified before RECOVER DATAFILE START

ORA-00298: missing or invalid TIMEOUT interval

ORA-00299: must be restored using file-level media on the data file

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

ORA-00301: error adding log file''- unable to create file

ORA-00302: log exceeds limit

ORA-00303: unable to handle redo with multiple interrupts

ORA-00304: the requested INSTANCE_NUMBER is in use

ORA-00305: log (thread) is inconsistent; belongs to another database

ORA-00306: routine restrictions in this database

ORA-00307: the requested INSTANCE_NUMBER exceeds the limit, with a maximum of

ORA-00308: unable to open archive log''

ORA-00309: the log belongs to the wrong database

ORA-00310: archived logs contain sequences; required sequences

ORA-00311: unable to read title from archive log

ORA-00312: online log thread:''

ORA-00313: cannot open a member of a log group (thread)

ORA-00314: log (thread), expected sequence number does not match

ORA-00315: log (thread), thread # error in title

ORA-00316: log (thread), the type in the title is not a log file

ORA-00317: the file type in the title is not a log file

ORA-00318: log (thread), expected file size does not match

ORA-00319: log (thread) has an incorrect log reset state

ORA-00320: unable to read the file title from the log (thread)

ORA-00321: log (thread), unable to update log file title

ORA-00322: log (thread) is not the current copy

ORA-00323: the thread's current log is not available and all other logs need to be archived

ORA-00324: the translation name of the log file''is too long and the characters exceed the limit

ORA-00325: log of archived thread, thread # error in title

ORA-00326: the log starts with changes, and earlier changes are required

ORA-00327: log (thread), the actual size is smaller than needed

ORA-00328: the archive log is at the end of the change, which needs to be changed later

ORA-00329: the archive log needs to be changed when the change starts.

ORA-00330: the archive log is at the end of the change and needs to be changed.

ORA-00331: log version is not compatible with ORACLE version

ORA-00332: the archive log is too small-it may not be fully archived

ORA-00333: error in read block count of redo log

ORA-00334: archive log:''

ORA-00335: online log: there is no log with this number, the log does not exist

ORA-00336: the number of log file blocks of size is less than the minimum

ORA-00337: log file''does not exist and the size is not specified

ORA-00338: logs (threads) are newer than control files

ORA-00339: the archive log does not contain any redo

ORA-00340: an Icano error occurred while processing online logs (threads)

ORA-00341: log (thread), log # error in title

ORA-00342: the archive log creates the package before the previous RESETLOGS

ORA-00343: too many errors, log member closed

ORA-00344: unable to recreate online log''

ORA-00345: error in redo log write block count

ORA-00346: log members are marked as STALE

ORA-00347: log (thread), expected block size does not match

ORA-00348: single process redo failed; routine must be aborted

ORA-00349: unable to get block size of''

ORA-00350: archiving is required in logs (threads)

ORA-00351: invalid recover-to time

ORA-00352: all logs for a thread need to be archived-cannot be enabled

ORA-00353: log corruption approaching block change time

ORA-00354: corrupt redo log block title

ORA-00355: change numbering out of order

ORA-00356: inconsistent length in change description

ORA-00357: the log file specifies too many members, with a maximum of

ORA-00358: too many file members specified, the maximum being

ORA-00359: log filegroup does not exist

ORA-00360: non-log file member:

ORA-00361: cannot delete the last log member (group)

ORA-00362: valid log files in a group require input members

ORA-00363: log is not an archived version

ORA-00364: unable to write title to new log member

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

ORA-00366: log (thread), checksum error in file header

ORA-00367: checksum error in log file header

ORA-00368: checksum error in redo log block

ORA-00369: the thread's current log is not available and other logs have been cleared

ORA-00370: deadlocks may occur during Rcbchange operations

ORA-00371: the shared pool is out of memory

ORA-00372: cannot modify the file at this time

ORA-00373: online log version is not compatible with ORACLE version

ORA-00374: parameter db_block_size = invalid; it must be a multiple of, with a range of [..]

ORA-00375: unable to get default db_block_size

ORA-00376: cannot read the file at this time

ORA-00377: frequent backups of files cause write delays

ORA-00378: unable to create buffer pool as specified

ORA-00379: free buffers of K-block size are not available in the buffer pool

ORA-00380: db_k_cache_size cannot be specified because K is the standard block size

ORA-00381: size description that new and old parameters cannot be used for buffer cache at the same time

ORA-00382: not a valid block size, valid range is [..]

ORA-00383: the block size of DEFAULT cache cannot be reduced to zero

ORA-00384: not enough memory to increase cache size

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

ORA-00390: the log (thread) is being cleared and cannot become the current log

ORA-00391: all threads must convert to the new log format at the same time

ORA-00392: log (thread) is being cleared, operation is not allowed

ORA-00393: logging (thread) is required for offline data file recovery

ORA-00394: reuse online logs when attempting to archive

ORA-00395: the online log of the 'clone' database must be renamed

ORA-00396: error needs to be returned to a single traversal recovery

ORA-00397: for files (blocks), write loss detected

ORA-00398: thread recovery aborted due to reconfiguration

ORA-00399: the change description in the redo log is corrupted

ORA-00400: invalid version value (for parameters)

ORA-00401: parameter values are not supported in this version

ORA-00402: database changes for version cannot be used for version

ORA-00403: () different from other routines ()

ORA-00404: no translation file found:''

ORA-00405: compatible type ""

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

ORA-00407: not allowed from the version. To. Rolling upgrade

ORA-00408: parameter is set to TRUE

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

ORA-00436: no right to use ORACLE software, please contact Oracle for assistance

ORA-00437: no right to use ORACLE software features, please contact Oracle for assistance

ORA-00438: no option installed

ORA-00439: property is not enabled:

ORA-00443: background process''not started

ORA-00444: background process "" failed to start

ORA-00445: the background process "" still does not start after a second

ORA-00446: background process started unexpectedly

ORA-00447: fatal error occurred in the background process

ORA-00448: the background process ends normally

ORA-00449: background process''terminated abnormally due to error

ORA-00470: the LGWR process was terminated due to an error

ORA-00471: the DBWR process was terminated due to an error

ORA-00472: the PMON process was terminated due to an error

ORA-00473: the ARCH process was terminated due to an error

ORA-00474: the SMON process was terminated due to an error

ORA-00475: the TRWR process was terminated due to an error

ORA-00476: the RECO process was terminated due to an error

ORA-00477: the SNP* process was terminated due to an error

ORA-00478: the SMON process was terminated due to an error

ORA-00480: the LCK* process was terminated due to an error

ORA-00481: the LMON process was terminated due to an error

ORA-00482: the LMD* process was terminated due to an error

ORA-00483: abnormal termination during shutdown process

ORA-00484: the LMS* process was terminated due to an error

ORA-00485: the DIAG process was terminated due to an error

ORA-00486: features are not available

ORA-00568: maximum number of interrupt handlers exceeded

ORA-00574: osndnt: $CANCEL failed (interrupt)

ORA-00575: osndnt: $QIO failed (sending out-of-band interrupt)

ORA-00576: in-band interrupt protocol error

ORA-00577: out-of-band interrupt protocol error

ORA-00578: reset protocol error

ORA-00579: osndnt: the server received the connection request in an incorrect format

ORA-00580: protocol version mismatch

ORA-00581: osndnt: unable to assign context area

ORA-00582: osndnt: cannot undo the allocation context area

ORA-00583: osndnt: $TRNLOG failed

ORA-00584: unable to close the connection

ORA-00585: incorrect format of host name

ORA-00586: osndnt: LIB$ASN_WTH_MBX failed

ORA-00587: unable to connect to the remote host

ORA-00588: the message from the host is too short

ORA-00589: incorrect length of information data from the host

ORA-00590: incorrect type of information from the host

ORA-00591: incorrect number of bytes written

ORA-00592: osndnt: $QIO failed (mailbox queue)

ORA-00593: osndnt: $DASSGN failed (network device)

ORA-00594: osndnt: $DASSGN failed (mailbox)

ORA-00595: osndnt: $QIO failed (receive)

ORA-00596: osndnt: $QIO failed (send)

ORA-00597: osndnt: $QIO failed (mailbox queue)

ORA-00598: osndnt: $QIO IO failed (mailbox read)

ORA-00600: internal error code, parameter: [], []

ORA-00601: clearing lock conflicts

ORA-00602: internal programming exception error

ORA-00603: ORACLE server session terminated due to fatal error

ORA-00604: an error occurred in the recursive SQL layer

ORA-00606: internal error cod

ORA-00607: an internal error occurred while changing the block

ORA-00701: unable to change the objects required for the hot boot database

ORA-00702: bootstrapper version''is not consistent with version''

ORA-00703: the maximum number of row cache routine locks exceeded

ORA-00704: bootstrap process failed

ORA-00705: inconsistent state during startup; restart after closing the routine

ORA-00706: error changing the format of file''

ORA-00816: error message cannot be converted

ORA-00900: invalid SQL statement

ORA-00901: invalid CREATE command

ORA-00902: invalid data type

ORA-00903: invalid table name

ORA-00904:: invalid identifier

ORA-00905: missing keyword

ORA-00906: missing left parenthesis

ORA-00907: missing closing parenthesis

ORA-00908: missing NULL keyword

ORA-00909: invalid number of parameters

ORA-00910: the specified length is too long for the data type

ORA-00911: invalid character

ORA-00913: too much value

ORA-00914: missing ADD keyword

ORA-00915: currently, network access to dictionary tables is not allowed

ORA-00917: missing comma

ORA-00918: columns are not clearly defined

ORA-00919: invalid function

ORA-00920: invalid relational operator

ORA-00921: unexpected end of the SQL command

ORA-00922: missing or invalid option

ORA-00923: no expected FROM keyword found

ORA-00924: missing BY keyword

ORA-00925: missing INTO keyword

ORA-00926: missing VALUES keyword

ORA-00927: missing equal sign

ORA-00928: missing SELECT keyword

ORA-00929: missing full stop

ORA-00930: missing asterisk

ORA-00931: missing identity

ORA-00932: inconsistent data types: what is required is

ORA-00933: the SQL command did not end correctly

ORA-00934: grouping functions are not allowed here

ORA-00935: grouping functions are too deeply nested

ORA-00936: missing expression

ORA-00937: non-single group grouping function

ORA-00938: the function does not have enough arguments

ORA-00939: the function has too many arguments

ORA-00940: invalid ALTER command

ORA-00941: missing cluster name

ORA-00942: table or view does not exist

ORA-00943: cluster does not exist

ORA-00944: there are not enough clusters

ORA-00945: the specified cluster column does not exist

ORA-00946: missing TO keyword

ORA-00947: not enough values

ORA-00948: ALTER CLUSTER statements are no longer supported

ORA-00949: illegal reference to remote database

ORA-00950: invalid DROP option

ORA-00951: cluster is not empty

ORA-00952: missing GROUP keyword

ORA-00953: missing or invalid index name

ORA-00954: missing IDENTIFIED keyword

ORA-00955: the name is already used by an existing object

ORA-00956: missing or invalid audit option

ORA-00957: duplicate column names

ORA-00958: missing CHECK keyword

ORA-00959: tablespace''does not exist

ORA-00960: ambiguous naming in the selection list

ORA-00961: wrong date / interval value

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

ORA-00963: unsupported interval type

ORA-00964: table name is not in the FROM list

ORA-00965:'*'is not allowed in column aliases

ORA-00966: missing TABLE keyword

ORA-00967: missing WHERE keyword

ORA-00968: missing INDEX keyword

ORA-00969: missing ON keyword

ORA-00970: missing WITH keyword

ORA-00971: missing SET keyword

ORA-00972: the identity is too long

ORA-00973: invalid row count estimate

ORA-00974: invalid PCTFREE value (percentage)

ORA-00975: date + date is not allowed

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

ORA-00977: duplicate audit option

ORA-00978: nested grouping functions do not have GROUT BY

ORA-00979: not a GROUP BY expression

ORA-00980: synonym conversion is no longer valid

ORA-00981: tables cannot be mixed with system audit options

ORA-00982: missing plus sign

ORA-00984: listed here is not allowed

ORA-00985: invalid program name

ORA-00986: missing or invalid group name

ORA-00987: missing or invalid user name

ORA-00988: missing or invalid password

ORA-00989: too many user names and passwords are given

ORA-00990: missing or invalid permissions

ORA-00991: the procedure has only MAC permissions

Invalid format of ORA-00992: REVOKE command

ORA-00993: missing GRANT keyword

ORA-00994: missing OPTION keyword

ORA-00995: missing or invalid synonym identity

ORA-00996: the concatenation operator is | instead of |

ORA-00997: illegal use of LONG data type

ORA-00998: this expression must be named with a column alias

ORA-00999: invalid view name

ORA-01000: exceeds the maximum number of cursors opened

ORA-01001: invalid cursor

ORA-01002: read out of order

ORA-01003: the statement is not parsed

ORA-01004: default username feature is not supported; login denied

ORA-01005: no exit order is given; login denied

ORA-01006: assignment variable does not exist

ORA-01007: there are no variables in the selection list

ORA-01008: not all variables are associated

ORA-01009: missing legal parameter

ORA-01010: invalid OCI operation

ORA-01011: version 7 compatibility mode cannot be used when talking to a version 6 server

ORA-01012: not logged in

ORA-01013: the user requests to cancel the current operation

ORA-01014: ORACLE is in the process of shutting down

ORA-01015: circular login request

ORA-01016: this function can only be called after reading

ORA-01017: invalid username / password; login denied

ORA-01018: the column does not have a LONG data type

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

ORA-01020: unknown context state

ORA-01021: the specified context size is invalid

ORA-01022: database operations are not supported in this configuration

ORA-01023: cursor context not found (invalid cursor number)

ORA-01024: invalid data type in OCI call

ORA-01025: UPI parameter is out of range

ORA-01026: there are multiple buffers of size > 4000 in the assignment list

ORA-01027: variables are not allowed to be assigned in data definition operations

ORA-01028: internal duplex error

ORA-01029: internal duplex error

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

ORA-01031: insufficient permissions

ORA-01032: there is no such user ID

ORA-01033: ORACLE is in the process of initialization or shutdown

ORA-01034: ORACLE is not available

ORA-01035: ORACLE is only allowed for users with RESTRICTED SESSION permissions

ORA-01036: illegal variable name / number

ORA-01037: exceeds the maximum cursor memory

ORA-01038: cannot write to the database file version (using the ORACLE version)

ORA-01039: insufficient permissions for view base objects

ORA-01040: invalid characters in password; login denied

ORA-01041: internal error, hostdef extension does not exist

ORA-01042: opening cursors to detach sessions is not allowed

ORA-01043: user side memory corruption [], []

ORA-01044: buffer size (associated with variables) exceeds the maximum limit

ORA-01045: the user does not have CREATE SESSION permission; login is denied

ORA-01046: unable to get space to extend the context area

ORA-01047: the above error occurs in schema=, package=, procedure=

ORA-01048: the specified procedure cannot be found in the given context

ORA-01049: assignment by name is not supported in mobile RPC

ORA-01050: unable to get the space to open the context area

ORA-01051: invalid format of delay rpc buffer

ORA-01052: no desired destination LOG_ARCHIVE_DUPLEX_DEST specified

ORA-01053: unable to read user storage address

ORA-01054: unable to write to user storage address

ORA-01057: invalid or ambiguous block.field referenced in user exit

ORA-01058: internal New Upi interface error

ORA-01059: parsing before assignment or execution

ORA-01060: array assignment or execution is not allowed

ORA-01061: unable to start the version 8 server using the version 7 customer application

ORA-01062: unable to allocate the memory needed to define the buffer

ORA-01070: the server uses an older version of Oracle

ORA-01071: cannot perform an operation without starting ORACLE

ORA-01072: cannot stop ORACLE; because ORACLE is not running

ORA-01073: fatal connection error: unrecognized call type

ORA-01074: unable to close ORACLE;. Please log out in the registration session first.

ORA-01075: you are now logged in

ORA-01076: multiple logins per process are not supported yet

ORA-01077: background process initialization failed

ORA-01078: failed to process system parameters

ORA-01079: the ORALCE database was not created correctly and the operation was aborted

ORA-01080: error closing ORACLE

ORA-01081: unable to start ORACLE that is already running-Please close first

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

ORA-01083: the value of parameter "" is not consistent with the corresponding parameter value of other sample programs.

ORA-01084: invalid parameter in OCI call

ORA-01085: delay rpc to ".." Previous mistakes

ORA-01086: never create a retention point''

ORA-01087: cannot start ORALCE-logged in now

ORA-01088: ORACLE cannot be turned off when there is an active process

ORA-01089: emergency shutdown in progress-no operations allowed

ORA-01090: closing is in progress-connection is not allowed

ORA-01091: forced startup error

ORA-01092: the ORACLE routine terminates. Forcibly disconnect

ORA-01093: ALTER DATABASE CLOSE is only allowed when there is no connection session

ORA-01094: ALTER DATABASE CLOSE is in progress. Connections are not allowed

The ORA-01095: DML statement processed zero rows

ORA-01096: program version () is not compatible with routine ()

ORA-01097: cannot be closed during a transaction-commit or return first

ORA-01098: a program interface error occurred during Long Insert

ORA-01099: if you start in single-process mode, you cannot install the database in SHARED mode

ORA-01100: database installed

ORA-01101: the database to be created is currently being installed by another routine

ORA-01102: unable to install database in EXCLUSIVE mode

ORA-01103: the database name in the control file''not''

ORA-01104: number of control files () is not equal to

ORA-01105: installation is not compatible with installation of other routines

ORA-01106: the database must be shut down before being removed

ORA-01107: the database must be installed for media recovery

ORA-01108: the file is in the process of backup or media recovery

ORA-01109: the database is not open

ORA-01110: data file:''

ORA-01111: data file name unknown-please rename to correct the file

ORA-01112: media recovery is not started

ORA-01113: files need media recovery

ORA-01114: an IO error occurred while writing a block to a file (block #)

ORA-01115: an IO error occurred while reading blocks from a file (block #)

ORA-01116: error opening database file

ORA-01117: add illegal block size to file'':; limit to

ORA-01118: cannot add any other database files: limit exceeded

ORA-01119: error creating database file''

ORA-01120: unable to delete online database file

ORA-01121: database files cannot be renamed-files are in use or in recovery

ORA-01122: database file validation failed

ORA-01123: unable to start online backup; media recovery not enabled

ORA-01124: unable to restore data file-file in use or in recovery

ORA-01125: media recovery cannot be disabled-online backup is set for files

ORA-01126: for this operation, the database must be installed in EXCLUSIVE mode and not open

ORA-01127: database name''exceeds the limit of characters

ORA-01128: unable to start online backup-the file is offline

ORA-01129: user default or temporary tablespace does not exist

ORA-01130: the database file version is not compatible with the ORACLE version

ORA-01131: DB_FILES system parameter value exceeds the limit

ORA-01132: the database file name''exceeds the limit of characters.

ORA-01133: the log file name''exceeds the limit of characters.

ORA-01134: the database has been installed independently by other routines

ORA-01135: files accessed by DML/query are offline

ORA-01136: the specified size of the file (block) is less than the original size of the block

ORA-01137: the data file is still offline

ORA-01138: the database must be open in this routine or not at all

ORA-01139: the RESETLOGS option is valid only after an incomplete database recovery

ORA-01140: unable to end online backup-all files are offline

ORA-01141: error renaming data file-New file not found''

ORA-01142: cannot end online backup-there are no files in the backup

ORA-01143: media recovery cannot be disabled-media recovery is required for files

On how to do Oracle exception handling to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.