INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16013',' log string sequence# string does not need archiving',' An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.',' No action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16014',' log string sequence# string not archived, no available destinations',' An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.',' Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16015',' log string sequence# string not archived, media recovery disabled',' An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.',' Disable the standby destination or enable media recovery and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16016',' archived log for thread string sequence# string unavailable',' The managed standby database recovery operation has timed out waiting for the requested archived log file.',' Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16017',' cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination',' The LOG_ARCHIVE_DUPLEX_DEST parameter was set to a non-NULL value when the primary archive destination was explicitly set to NULL.',' Set the primary archive destination to a valid non-NULL value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16018',' cannot use string with LOG_ARCHIVE_DEST_n',' One of the following events caused an incompatibility:',' Eliminate any incompatible parameter definitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16019',' cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST',' One of the following events caused an incompatibility:',' Eliminate any incompatible parameter definitions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16020',' less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST',' With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.',' Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16021',' session string destination cannot be the same as session string destination',' An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.',' Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16022',' LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL',' An attempt was made to change the LOG_ARCHIVE_DEST initialization parameter to NULL when the LOG_ARCHIVE_DUPLEX_DEST initialization parameter is non-NULL.',' Either set the LOG_ARCHIVE_DEST initialization parameter to a non-NULL value, or set the LOG_ARCHIVE_DUPLEX_DEST initialization parameter to a NULL value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16023',' system string destination cannot be the same as session string destination',' An attempt to change the first specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM statement. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.',' Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16024',' parameter string cannot be parsed',' The value for the indicated LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.',' Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16025',' parameter string contains repeated or conflicting attributes',' The value for the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) contained either repeated attributes or attributes that conflicted with each other.',' Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16026',' parameter string contains an invalid numeric attribute value',' The value for the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) contained a REOPEN attribute with an invalid numeric value. The valid range is 0 - 65535.',' Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16027',' parameter string is missing a destination option',' The value for the indicated LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attribute.',' Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16028',' new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires',' With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1, 2, ... 10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.',' Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16029',' cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations',' An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.',' Define one or more log archive destinations using the LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n parameters (n = 1, 2, ... 10). Then, change the value of the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16030',' session specific change requires a LOG_ARCHIVE_DEST_n destination',' The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION statement.',' Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1, 2, ... 10) parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16031',' parameter string destination string exceeds string character limit',' The value for the specified parameter contained a destination string that is too long.',' Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16032',' parameter string destination string cannot be translated',' The value for the specified parameter contained a destination string that could not be translated.',' Use a valid destination string in the specified parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16033',' parameter string destination cannot be the same as parameter string destination',' An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.',' Specify a different value for one of the archive log parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16034',' FROM parameter is incompatible with MANAGED recovery',' Use of the FROM ''location'' parameter is not allowed when MANAGED recovery has been specified.',' Correct the syntax and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16035',' missing required keyword string',' The indicated keyword is required but was not specified.',' Correct the syntax and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16036',' invalid MANAGED recovery CANCEL option',' A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.',' Specify either nothing or IMMEDIATE following CANCEL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16037',' user requested cancel of managed recovery operation',' The managed standby database recovery operation has been canceled per user request.',' No action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16038',' log string sequence# string cannot be archived',' An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.',' No action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16039',' RFS request version mismatch',' A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.',' Verify that compatible versions of Oracle are running on the primary and all standby sites.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16040',' standby destination archive log file is locked',' The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.',' Check for and eliminate duplicate standby destination archive log service names defined for the primary database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16041',' Remote File Server fatal error',' The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.',' Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible, take corrective action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16042',' user requested cancel immediate of managed recovery operation',' The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16043',' managed recovery session canceled',' The standby database managed recovery operation has been canceled per user request or operation timeout.',' More specific messages will accompany this message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16044',' destination string attribute cannot be specified at session level',' An archive log destination attribute was attempted to be modified at the session level.',' Use the ALTER SYSTEM command to modify the destination attribute.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16045',' circular archive log destination dependency chain',' An archive log destination contains a dependency to another archive log destination that also contains a dependency.',' The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM statement to remove one of the dependency attributes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16046',' Archive log destination failed due to failed dependent destination',' The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16047',' Dependent archive log destination cannot be a standby database',' The parent archive log destination cannot be a standby database. It must be a local archive log destination.',' Change the parent archive log destination from referencing a standby database to referencing a local archive log repository.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16048',' enable simulated error on archive log write',' Causes an I/O error to be signalled during the writing of an archival operation.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16049',' simulated error on archive log write',' I/O error returned for a simulated archival failure during an archival operation.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16050',' destination exceeded specified quota size',' An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16051',' parameter string contains an invalid delay time',' The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).',' Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16052',' Problem with fetching gap sequence, media recovery cancelled.',' A gap sequence is detected on the standby database while it was trying to perform managed standby recovery. The fetching of the gap sequence fails. The failures are logged in the alert log on the primary database.',' Check the alert log on primary and standby database. Take appropriate action to make the gap sequence available again. Managed standby recovery on the standby database cannot proceed further until the standby database is able to get the gap sequence redo log files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16053',' FAL archive failed, cannot archive thread# string sequence# string',' The FAL server on the primary database has problem archiving a redo log file requested by the standby database. The cause for this failure is logged in the alert log file.',' Check the alert log on the primary database. Take the appropriate action to solve the problem. Re-issue Managed Standby Recovery on the standby database again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16055',' FAL request rejected',' FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.',' Check the alert log on the primary database. Take the appropriate action to solve the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16056',' backup control file archival requires proper syntax',' An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.',' If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16057',' current control file archival requires proper syntax',' An attempt was made to perform an online log file archival using a current control file. However, the USING BACKUP CONTROLFILE syntax was specified.',' If the archival operation is correct when using a current control file, then the USING BACKUP CONTROLFILE syntax is not required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16058',' standby database instance is not mounted',' The RFS process on the standby database received an internal error.',' Check the standby alert log and RFS trace files for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16059',' Log file is empty or invalid next available block',' Archiving not allowed of an empty or invalid log file.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16060',' Log file is current',' The current log file cannot be archived using its file name.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16061',' Log file status has changed',' It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16062',' The log was NOT archived',' Archiving not allowed of current log file.',' Check the alert log and archive trace files for additional information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16063',' remote archival is enabled by another instance',' Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.',' Set the REMOTE_ARCHIVE_ENABLE parameter to true and restart this instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16064',' remote archival is disabled by another instance',' Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.',' Set the REMOTE_ARCHIVE_ENABLE parameter to false and restart this instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16065',' remote archival disabled at standby destination',' Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.',' If appropriate, change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to true and restart the standby database instance before further REDO log file archivals occur.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16066',' remote archival disabled',' An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.',' If appropriate, change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to true and restart the database instance before further REDO log file archivals occur.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16067',' activation identifier mismatch in archive log string',' The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.',' Locate the appropriate archive log for the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16068',' redo log file activation identifier mismatch',' The activation identifier of the indicated redo log file does not match the activation identifier of the database.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16069',' Archive Log standby database activation identifier mismatch',' The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.',' Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16070',' parameter string contains an invalid REGISTER attribute value',' The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an operating system-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).',' Correct the value for the LOG_ARCHIVE_DEST_n parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16071',' dependency archived log file not found string',' The specified archived log file was not found at the indicated standby destination.',' Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16072',' a minimum of one standby database destination is required',' No standby database archive log destinations were specified.',' Specify a standby archive log destination in the initialization parameter file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16073',' archiving must be enabled',' Online log file archiving is disabled.',' Enable log file archiving.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16074',' ARCH processes must be active',' There are no active ARCH processes.',' It is required that at least one ARCH process be active.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16075',' standby database destination mismatch',' A standby database destination was specified that is not accessed by another instance.',' All database instances must access the same standby databases.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16076',' unknown standby database destination',' A standby database destination was specified that is not accessed by another instance.',' All database instances must access the same standby databases.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16078',' media recovery disabled',' The database is not in ARCHIVELOG mode.',' Place the database in ARCHIVELOG mode.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16079',' standby archival not enabled',' The standby database does not have archival enabled.',' In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16080',' invalid LogMiner session string for APPLY',' Logical standby apply engine was started with an invalid LogMiner session identifier.',' Fix the problem with the LogMiner session or create a new session.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16081',' insufficient number of processes for APPLY',' Logical standby apply engine was started with fewer processes available than needed.',' Increase the values of the initialization parameters PROCESSES and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16082',' logical standby is not initialized correctly',' Logical standby apply engine was started but it found inconsistencies in its metadata.',' Look in the trace file for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16083',' LogMiner session has not been created',' Logical standby apply engine was started without creating a LogMiner session.',' Create a LogMiner session and restart the apply engine.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16084',' an apply engine is already running',' A logical standby apply engine was running when another was created.',' Shut down the previous apply engine before starting a new one.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16086',' standby database does not contain available standby log files',' The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files".',' Add one or more standby log files to the standby database. This can be done while the standby database is mounted.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16087',' graceful switchover requires standby or current control file',' An attempt was made to perform a graceful switchover operation using a backup or clone control file.',' Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16088',' archive log has not been completely archived',' An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a "current" log file.',' Specify a completed archive log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16089',' archive log has already been registered',' An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.',' Use the V$ARCHIVED_LOG fixed view to verify the archive log information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16090',' archive log to be replaced not created by managed standby process',' An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.',' No user action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16091',' dependent archive log destination already archived',' An archive log destination contains a dependency to another archive log destination that has previously been archived.',' The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM statement to remove one of the dependency attributes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16092',' dependent archive log destination is not active',' An archive log destination contains a dependency to another archive log destination that is not active.',' The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM statement to remove one of the dependency attributes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16093',' dependent archive log destination is not LGWR-enabled',' An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process.',' The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM statement to change the parent archive log to specify the LGWR process.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16094',' database shutdown during archival operation',' The database was shut down while an online log file archival was active.',' No action required. The ARCH process is terminated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16095',' Dependent destination removal for inactivation',' A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16098',' inaccessible standby database forced shutdown to protect primary',' No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode.',' Specify an alternate standby archive log destination in the initialization parameter file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16099',' internal error ORA-00600 occurred at standby database',' The RFS process on the standby database received an internal error.',' Check the standby alert log and RFS trace files for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16100',' not a valid Logical Standby database',' This database has not been completely configured as a Logical Standby database.',' Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle9i SQL Reference for the statement syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16101',' a valid start SCN could not be found',' An SCN from which to start could not be found.',' Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGFILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16102',' remote information is not available on the specified primary',' The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.',' Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16103',' Logical Standby apply must be stopped to allow this operation',' Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.',' Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or re-specify the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16104',' invalid Logical Standby option requested',' The option requested is not valid.',' Check spelling or refer to the Oracle9i SQL Reference for the correct statement syntax, then re-enter the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16105',' Logical Standby is already running in background',' A Logical Standby apply operation is already running.',' no action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16107',' all log data from primary has been processed',' On the primary system, the log stream has been ended by the ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY statement.',' Issue one of the following statements to make this standby a primary or resume applying changes from a new primary:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16108',' database is no longer a standby database',' The current database has already been made a primary database.',' Issue the following statements to make this primary a standby:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16109',' failed to apply log data from previous primary',' Log data from previous primary could not be completely applied.',' Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, re-issue command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16110',' user procedure processing of logical standby apply DDL',' A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.',' No action required; this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16111',' log mining and apply setting up',' This logical standby process is setting up to begin processing changes.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16112',' log mining and apply stopping',' This logical standby process is cleaning up and stopping Logical Standby apply.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16113',' applying change to table or sequence object number string',' The process is applying changes to a specific schema object.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16114',' applying DDL transaction with commit SCN string',' The process is applying a DDL change that''s committed at the given SCN.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16115',' loading Log Miner dictionary data',' The process is loading dictionary information from the redo stream. This activity may take a few minutes.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16116',' no work available',' The process is idle waiting for additional changes to be made available.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16117',' processing',' The process is performing its primary function and is not waiting on any significant event.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16119',' building transaction at SCN string',' The transaction being committed at the given SCN is being prepared for apply.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16120',' dependencies being computed for transaction at SCN string',' The transaction committed at the given SCN is being analyzed for dependencies.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16121',' applying transaction with commit SCN string',' The transaction committed at the given SCN is being applied.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16122',' applying large dml transaction at SCN string',' A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16123',' transaction string string string is waiting for commit approval',' The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16124',' transaction string string string is waiting on another transaction',' The apply process is waiting to apply additional changes. This transaction likely depends on another.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16125',' large transaction string string string is waiting on another transaction',' The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16126',' loading table or sequence object number string',' Information on the given table or sequence is being loaded into an in memory cache for future use.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16127',' stalled waiting for additional transactions to be applied',' This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.',' No action required; this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, then increase available SGA or the number of apply processes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16128',' User initiated shut down successfully completed',' Logical standby was shutdown in an orderly fashion.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16129',' unsupported dml encountered',' DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support.',' Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16130',' supplemental log information is missing from log stream',' Supplemental logging is not enabled at the primary database.',' Issue the following statement to enable supplemental logging:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16131',' An error occurred during a Terminal Recovery of the standby.',' An error occurred during a Terminal Recovery of the standby.',' Check the standby alert log additional information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16132',' An error occurred during activation of the standby.',' An error occurred during activation of the standby database following a Terminal Recovery.',' Check the standby alert log additional information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16133',' Datafile string has incorrect terminal recovery stamp.',' After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.',' A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16134',' invalid MANAGED recovery FINISH option',' A mode other than NOWAIT follows the FINISH keyword in the RECOVER MANAGED STANDBY DATABASE statement.',' Specify either nothing or NOWAIT following FINISH.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16135',' terminal recovery could not find log for thread# string seq# string.',' A terminal recovery (initiated by the RECOVER MANAGED STANDBY FINISH command) could not find the current log for the requested thread and sequence.',' Check that the standby current logs are in the correct location.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16136',' Managed Standby Recovery not active',' An attempt was made to cancel a managed recovery session but no managed recovery session was active.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16137',' No terminal recovery is required',' All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required.',' No action required. The standby database may be activated as a new primary or may continue as a standby.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16138',' end of log stream not received from primary',' The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.',' Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16139',' media recovery required',' The database has not been recovered through the end of log stream. Graceful switchover is not possible.',' Ensure that the entire log stream has been applied. If appropriate, re-issue the graceful switchover command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16140',' standby online logs have not been recovered',' The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.',' To recover the standby online logs issue the following command:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16143',' RFS connections not allowed during or after terminal recovery',' An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.',' The primary must not attempt to archive to the standby after a terminal recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16145',' archival for thread# string sequence# string in progress',' The indicated archived log file is not available for recovery due to the fact that it is still being archived.',' Verify that archival of the indicated log file has completed and re-issue the RECOVER STANDBY DATABASE command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16146',' standby destination control file enqueue unavailable',' The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.',' Check for and eliminate the standby destination archive log parameter in question.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16147',' standby database referenced by multiple archive log destinations',' Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.',' Remove one of the duplicate archive log destinations.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16148',' user requested expiration of managed recovery operation',' The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16150',' FINISH recovery performed on another, older standby database',' An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16151',' Managed Standby Recovery not available',' The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.',' Wait for the managed standby recovery session to end. Then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16152',' standby database is in ''no-data-loss'' protected mode',' The attempted database operation is not allowed while the standby database is in ''no-data-loss'' protected mode.',' Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and re-issue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16154',' suspect attribute: string',' Use of the indicated attribute is illegal in the given context.',' Make the appropriate changes and re-issue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16156',' LGWR archive log dependency not allowed if database is standby protected',' The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.',' Remove the LGWR archive log dependency and use normal LGWR archival instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16157',' media recovery not allowed following successful FINISH recovery',' A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.',' Issue one of these operations following a FINISH recovery:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16159',' Cannot change protected standby destination attributes',' An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16160',' Cannot change protected standby database configuration',' An attempt was made to change the standby database configuration when the primary database is in standby protected mode.',' The standby database must be added to the configuration before the primary database is opened.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16161',' Cannot mix standby and online redo log file members for group string',' An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.',' Verify the log file group type using the TYPE column of the V$LOG fixed view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16162',' Cannot add new standby databases to protected configuration',' An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.',' The standby database must be added to the configuration before the primary database is opened.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16163',' LGWR network server host attach error',' The LGWR network server could not attach to remote host.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16164',' LGWR network server host detach error',' The LGWR network server could not detach from remote host.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16165',' LGWR failed to hear from network server',' The LGWR lost its connection to the network server.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16166',' LGWR network server failed to send remote message',' The LGWR network server could not communicate with the remote host.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16167',' LGWR network server could not switch to non-blocking mode',' The LGWR network server could not switch to non-blocking mode.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16168',' LGWR network server could not switch to blocking mode',' The LGWR network server could not switch to blocking mode.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16169',' LGWR network server invalid parameters',' The LGWR network server could not switch to blocking mode.',' The alert log contains more problem-specific information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16170',' Parallel terminal recovery may lose more data than necessary',' Serial terminal recovery can always recover the standby database to the last consistent point in the redo stream. Parallel terminal recovery cannot.',' Retry with serial terminal recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16171',' RECOVER...FINISH not allowed due to gap for the string, seq string-string',' See alert log for more details.',' Copy missing archived logs from primary or another standby. Register the logs and re-issue the RECOVER...FINISH command. If the logs are not available, then issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP statement to ignore the standby redo log files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16172',' archive logs detected beyond Terminal End-Of-Redo',' An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16173',' incompatible archival network connections active',' One of two situations can cause this error:',' Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16174',' user requested thread/sequence termination of managed recovery',' The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16175',' cannot shut down database when media recovery is active',' An attempt was made to shut down a standby database while media recovery was active.',' Cancel media recovery to proceed with the shutdown.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16199',' Terminal recovery failed to recover to a consistent point',' See alert log for more details.',' Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, then contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16200',' Skip procedure requested to skip statement',' Logical standby called a skip procedure that requested for a particular statement not to be applied.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16201',' Skip procedure requested to apply statement',' Logical standby called a skip procedure that requested for a particular statement to be applied.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16202',' Skip procedure requested to replace statement',' Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16203',' Unable to interpret skip procedure return values',' The skip procedure returned conflicting or invalid values.',' Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE, and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16204',' DDL successfully applied',' A DDL statement has successfully committed on the logical standby database.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16205',' DDL skipped due to skip setting',' A setting in the logical standby skip table indicates that this type of DDL should always be skipped.',' No action required; this informational statement is provided to record the event for diagnostic purposes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16206',' database already configured as Logical Standby database',' This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.',' Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16207',' Logical standby dictionary build not permitted.',' A dictionary build is currently in progress. Only one build can be active at a time.',' Wait for the active build to complete before invoking a new build.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16208',' Logical standby dictionary build failed to start.',' Failure to start the logical standby dictionary build process (LSP1).',' Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16209',' Logical standby dictionary build failed to complete.',' The logical standby dictionary build process terminated abnormally.',' Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16210',' Logical standby coordinator process terminated with error',' The logical standby coordinator process terminated abnormally.',' Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16211',' unsupported record found in the archived redo log',' Log apply services encountered a record in the archived redo log that could not be interpreted.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16212',' number processes specified for APPLY is too great',' Logical standby apply engine was started with more processes requested than are available.',' Adjust the values of the initialization parameters PROCESSES and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16213',' ddl encountered, stopping apply engine',' stop_on_ddl callout specified and DDL was encountered.',' Either disable stop_on_ddl callout or remove DDL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16214',' apply stalled for apply delay',' A delay has been specified on the primary database for this destination.',' Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET(''APPLY_DELAY''); to override.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16501',' the Data Guard broker operation failed',' The Data Guard broker operation failed.',' See other messages for details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16502',' the Data Guard broker operation succeeded with warnings',' The Data Guard broker operation succeeded with warnings.',' See other messages for details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16503',' site ID allocation failure',' Number of sites in the Data Guard configuration has exceeded the limit.',' Delete unused sites.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16504',' the Data Guard configuration already exists',' A request to create a Data Guard configuration was made on a site that is part of an existing configuration.',' Delete the existing configuration if you desire to create a new configuration.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16505',' site ID is invalid',' The request contained an invalid site ID.',' Make the request again with a valid site ID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16506',' out of memory',' Process exceeded private or shared memory limits.',' Check for memory leaks, increase system parameters, and restart.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16507',' unrecognized request identifier',' The specified request identifier was not recognized by the Data Guard broker.',' Re-issue the request using a valid request identifier.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16508',' channel handle not initialized',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16509',' the request timed out',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16510',' messaging error using ksrwait',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16511',' messaging error using ksrget',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16512',' parameter exceeded maximum size limit',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16513',' maximum requests exceeded',' Non-blocking commands were issued but responses are not read or the commands did not complete execution.',' Read pending responses or delete outstanding requests and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16514',' the request was not found',' An attempt was made to read a response but a matching request was not found.',' Verify request identifier is valid and references a previously issued request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16515',' no rcv channel',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16516',' the resource state is invalid for the attempted operation',' The broker will return this error for switchover operations and for resource state change operations. If this error is returned for a switchover operation, then the broker has determined that either:',' If this error is returned when attempting a switchover operation, then make sure that:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16517',' the object handle is invalid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16518',' unable to allocate virtual instance id',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16519',' the resource handle is invalid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16520',' unable to allocate resource id',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16521',' unable to create generic template id',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16522',' generic template not found',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16523',' property count exhausted',' Total number of resource properties exceeded the limit.',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16524',' unsupported operation',' A command or option is not supported in this release.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16525',' the Data Guard broker is not yet available',' The Data Guard broker process has not yet been started, is initializing, or has failed to start.',' If the broker has not been started, then set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, then check the Data Guard log for possible errors. Otherwise, retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16526',' unable to allocate task element',' The Data Guard broker was unable to allocate memory for a request.',' Increase the size of your SGA.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16527',' unable to allocate SGA heap',' The Data Guard broker was unable to allocate a heap within the SGA.',' Increase SGA memory.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16528',' unable to allocate PGA heap',' No space in PGA to allocate heap.',' Increase process virtual memory.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16529',' bad sender id',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16530',' invalid buffer or length',' A NULL buffer or a length of zero was specified.',' Correct command parameters and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16531',' unable to post message',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16532',' Data Guard configuration does not exist',' The Data Guard configuration does not exist.',' Create a DRC prior to issuing other requests.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16533',' inconsistent Data Guard broker state',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16534',' no more requests accepted',' The Data Guard broker returns this status when:',' Wait until the operation is complete and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16535',' failover request rejected',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16536',' unknown object type',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16537',' child count exceeded',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16538',' no match on requested item',' The Data Guard broker did not recognize the specified property or state name.',' Verify command parameters and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16539',' task element not found',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16540',' invalid argument',' One of the arguments for the specified request is invalid for the request type. In the case of failover, the failover level must be specified. That is, a graceful failover or a forced failover.',' Verify arguments and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16541',' site is not enabled',' The site specified in the request is not enabled.',' Select an enabled site and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16542',' unrecognized operation',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16543',' invalid request made to broker',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16544',' unable to make request',' The Data Guard broker was unable to accept the request.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16545',' unable to get response',' The Data Guard broker was unable to return the result of a previous request.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16546',' missing or invalid piece',' The piece of the request to return was not specified or is invalid.',' Specify the piece of the response starting from 1.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16547',' unable to delete request',' The Data Guard broker was unable to delete the given request.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16548',' the resource is not enabled',' An attempt was made to modify or query a disabled Data Guard resource. This error is also returned on an attempt to enable, modify, or query a resource that the broker has permanently disabled. A permanently disabled resource cannot be re-enabled. The broker permanently disables site resources when it detects that the database on that site needs to be reinstantiated. The broker also permanently disables sites that lag behind in terms of DRC Unique ID sequence value.',' If the resource is not permanently disabled, enable the resource and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16549',' invalid string',' A request contains an invalid or NULL string value.',' Correct command parameters and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16550',' truncated result',' A string property value was truncated due to insufficient buffer size.',' Specify a larger recieve buffer.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16551',' short string copied',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16552',' the Data Guard broker process (DMON) failed to start',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16553',' the Data Guard broker process (DMON) failed to shutdown',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16554',' translation not valid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16555',' the Data Guard resource is not active',' An operation was attempted on a resource that is currently not active (off path).',' Verify that the resource is active.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16557',' the resource is already in use',' An attempt was made to create a duplicate resource.',' Check the resource to be added and be sure there are no duplicates.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16558',' the site specified for switchover is not a standby',' An attempt was made to switchover to a site that is not a standby site.',' Locate an enabled standby site and select that site as the target of the switchover.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16559',' out of memory at string',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16560',' unable to convert document, syntax error at "string"',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16561',' must use ONLINE parent state, syntax error at "string"',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16562',' intended_state not used here, syntax error at "string"',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16563',' unable to add value, syntax error at "string"',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16564',' lookup failed, syntax error at string',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16565',' duplicate property, syntax error at "string"',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16566',' unsupported document type',' The submitted XML document is not supported.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16567',' Data Guard broker internal parser error at "string"',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16568',' cannot set property string',' The named property could not be modified. The property may not be editable or may not exist.',' Retry the operation with a valid property.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16569',' Data Guard configuration is not enabled',' The requested operation requires the Data Guard configuration to be enabled.',' Enable the Data Guard configuration and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16570',' Operation requires restart of site "string"',' Some Data Guard broker operations require the given site to be shut down and restarted.',' If the client has not already done so, then shut down the Oracle instance at the given site and then restart it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16571',' Data Guard configuration file creation failure',' The Data Guard broker was unable to create the configuration file on permanent storage.',' Verify space, permissions, and filename as indicated by the DG_BROKER_CONFIG_FILE[1 | 2] parameter and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16572',' Data Guard configuration file not found',' The Data Guard broker configuration file is either unavailable or does not exist.',' Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1 | 2] parameter was changed, then ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16573',' attempt to change configuration file in an enabled DRC',' An attempt was made to change the Data Guard broker configuration file parameter while a DRC was enabled.',' Disable the configuration and shut down the Data Guard broker before changing this value. Also be sure to rename the file at the operating system level.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16574',' switchover disallowed when required resources are offline',' Switchover fails because the primary database resource and/or the designated standby database resource are offline.',' Check the states of the configuration, primary site, primary database resource, standby site, and standby database resource. Set their states to ONLINE if necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16575',' request terminated at broker discretion',' This status is returned when the Broker terminates a user-initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16576',' failed to update Data Guard configuration file',' A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16577',' corruption detected in Data Guard configuration file',' The Data Guard broker detected errors while loading the configuration file.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16578',' failed to read Data Guard configuration file',' A failure was encountered while the broker was reading the configuration file on permanent storage.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16579',' bad Data Guard NetSlave state detected',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16580',' bad Data Guard NetSlave network link',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16581',' Data Guard NetSlave failed to send message to DRCX',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16582',' Data Guard connection process received error from NetSlave',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16583',' bad Data Guard Connection Process DRCX state',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16584',' illegal operation on a standby site',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16585',' illegal operation on a primary site',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16586',' Data Guard broker unable to update configuration on site',' The Data Guard broker was unable to update the configuration file on a particular site.',' Verify that your Oracle Net connections are operational between the Data Guard sites.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16587',' ambiguous object handle',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16588',' no more internal buffers',' See trace file.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16589',' Data Guard Connection process detected a network transfer error',' The Data Guard Connection Process (DRCX) detected an error while transferring data from one site to another. This error is returned in the following situations:',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16590',' no primary established in Data Guard configuration',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16591',' unknown field "string" in document',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16592',' missing field "string" in document',' There was an error at the given token.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16593',' XML conversion failed',' There was an error in the XML request document.',' Correct the errors and resubmit the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16594',' string process discovered that DMON process does not exist',' The Data Guard NetSlave (NSV*) processes discovered that the Data Guard broker process (DMON) is not running.',' Check the Data Guard console log and DMON process trace file to determine why the DMON process is missing.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16595',' NetSlave process string failed to terminate',' The specified NetSlave process did not terminate at the request of the Data Guard broker.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16596',' site is not a member of the Data Guard configuration',' A request was made on a site that is not a member of the Data Guard configuration.',' Re-issue the request on a site that is a part of the configuration.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16597',' Data Guard broker detects two or more primaries',' The Data Guard broker has detected two or more primaries in the configuration and cannot continue.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16598',' The Data Guard broker has detected a mismatch in configuration',' The Data Guard broker on this site has detected a mismatch in configuration generation. This can occur when the primary site has a stale configuration.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16599',' The Data Guard broker has detected a stale configuration',' The Data Guard broker has detected a stale configuration during initialization on this site.',' The broker will automatically resolve this situation once the primary site completes its initialization.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16600',' Failover operation can only be submitted on target site',' This error is returned when a failover request specifies a different site than the site the client is currently connected to.',' Explicitly connect to the site you wish to failover to and re-issue the failover request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16601',' site contains required resources that are disabled',' The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled.',' Enable all required resources and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16602',' resource must be disabled to perform this operation',' An attempt was made to modify a resource that can only be changed while that resource is disabled.',' Disable the resource and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16603',' Data Guard broker detected mismatch in configuration ID',' The Data Guard broker on this site has detected a mismatch in configuration Unique ID. This can occur if the original configuration was re-created while this site was disconnected from the network or the same site was added to two different configurations.',' Make sure the site belongs to only one configuration. Remove Data Guard broker configuration files and restart the server.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16604',' unable to describe template using package "string"',' The Data Guard broker was unable to execute the OnDescribe function in the named package.',' Verify that the named package is loaded on the primary site. Also verify that the OnDescribe function is in the package.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16605',' unable to delete template, template is in use',' The Data Guard broker was unable to delete the template because the template is still being used by one or more resources.',' Delete all resources using the template before deleting the template. You cannot delete the database template.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16606',' unable to find property "string"',' The named property does not exist.',' Specify a valid property name and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16607',' one or more sites have failed',' The Data Guard broker detected a failure on one or more sites.',' Locate the sites with a failure status and correct it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16608',' one or more sites have warnings',' The Data Guard broker detected a warning status on one or more sites.',' Locate the sites with a warning status and correct it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16609',' one or more resources have failed',' The Data Guard Broker detected a failure on one or more resources on a site.',' Locate the resources with a failure status and correct it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16610',' one or more resources have warnings',' The Data Guard broker detected a warning status on one or more resources on a site.',' Locate the resources with a warning status and correct it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16611',' operation aborted at user request',' The Data Guard broker aborted an operation at the user''s request.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16612',' string value too long for attribute "string"',' The string value for the named attribute is too long.',' Use a shorter string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16613',' initialization in progress for site',' The site received a directive to change its initialization state or a change in its configuration before it has completed initialization.',' Wait until the site has completed initialization before issuing requests to modify run-time state or configuration.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16614',' object has an ancestor that is disabled',' A request to enable an object that has an ancestor that is disabled was received by the server. The Data Guard broker has enabled the object to the extent that it can, but cannot fully enable the object until its ancestor is enabled.',' Determine the ancestor object that is disabled and enable that ancestor prior to enabling the child object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16617',' Unknown object identifier specified in request',' The Data Guard broker returns this error when the object identifier specified in the request is invalid or unknown. For example, this error is returned if an invalid or unknown site object identifier is specified in a request that requires a site object identifier.',' Verify that a valid object identifier was specified in the request and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16618',' response document of size "string" bytes is too large',' The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard console log.',' View the console log on the given site directly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16619',' Health Check timed out',' This status is returned when the Data Guard broker could not reach a standby site during routine health check.',' This typically indicates a network problem where the standby site is unable to respond to the primary within the predefined time frame.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16620',' one or more sites could not be contacted for a delete operation',' This status is returned when the Data Guard broker could not reach one or more standby sites for either a delete site or a delete configuration operation.',' This typically indicates a network problem where the standby site is unable to respond to the primary. In the event of this situation, examine the Data Guard broker log file on the primary site to determine which standby sites could not be reached. Then for each standby site not reached, connect to that site and shut down the broker by setting the DG_BROKER_START initialization parameter to false. After the broker has been shut down on the standby site, locate the Data Guard broker configuration files from the standby site''s DG_BROKER_CONFIG_FILE[1 | 2] parameter values and delete them.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16621',' host and SID names for create site must be unique',' This status is returned when an attempt is made to add a site whose host and SID names match those of an existing site.',' Verify that you have specified a unique host and SID name pair for the new site you wish to add. This can be done by checking that there are no sites with the same host and SID names.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16622',' two or more Broker sites resolve to the same physical site',' This status is returned when the Broker determines that there are multiple site objects referring to the same physical or material site.',' Examine the host names, SID names, and connect descriptors of all sites in the configuration and verify that there are not two or more sites that refer to the same physical site. If you detect this situation, then correct the site definition to eliminate the ambiguity.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16623',' stale DRC UID sequence number detected',' This status is returned when the Broker detects a stale sequence value during bootstrap or during health check. The sequence value is changed each time a role change occurs. A site that is unavailable for the role change operation will end up with a stale sequence number. Should that site attempt to rejoin the configuration, the broker will determine that it missed a role change and disable that site. The broker permanently disables the site since it may no longer be a viable standby site for the new primary.',' Examine the configuration and the sites that were permanently disabled to determine if they require manual intervention.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16624',' broker protocol version mismatch detected',' This status is returned when the Broker detects a network protocol version number mismatch. This can happen if the sites in question are not running the same release of Oracle. The broker will permanently disable the sites that do not have the same network protocol version number as the primary.',' Examine the release of Oracle installed on all sites to make sure they are identical. Once the Oracle releases are the same on all sites, delete and re-add the sites that were permanently disabled.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16625',' cannot reach the primary site',' This status is returned when the Broker rejects a write operation requested by the client when the primary site is not reachable from the site the request is made. All write operations made to the DataGuard configuration must be processed by the primary site.',' Check your network connection from the site your client is connected to, to the primary site. Alternatively, you can connect your client to a different site in the DataGuard Configuration and try your request again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16626',' failed to enable specified object',' This status is returned when the broker fails to enable an object (most typically a standby site). You can expect to see this status when attempting to enable a standby site that:',' To correct the problem, try one of these actions:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16627',' no standby databases support overall protection mode',' This status is returned in the following situations:',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16628',' The Broker protection mode is inconsistent with the database setting',' The Data Guard Broker protection mode saved in metadata is inconsistent with the actual database setting.',' Reset the protection mode through the Data Guard Broker.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16629',' database reports a different protection level from the protection mode',' The actual protection level supported by the standby database is different from the protection mode set on the primary. This is likely caused by the log transport problems.',' Check the database alert logs and Data Guard Broker console logs for more details. Check the log transport status. Make sure at least one standby log transport is supporting the protection mode and that the network to the standby has no problems.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16701',' generic resource guard request failed',' Request to modify or query the resource failed.',' Check the Data Guard console log for the reason for the failure, and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16702',' generic resource manager warning',' Request to modify or query the resource resulted in a warning.',' Check the console log for the reason for the warning, and re-issue the request if necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16703',' status of request is unknown',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16704',' a previous set state operation is pending',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16705',' severe internal error in resource guard',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16706',' no resource guard is available',' No resource guard is available to service the request.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16707',' the value supplied to resource guard is invalid',' The value specified in the request is invalid.',' Check value and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16708',' the state supplied to resource guard is invalid',' The state name specified is invalid for the resource.',' Check the state name and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16709',' the resource guard is busy and cannot service the request',' Request to resource guard failed because the guard is busy.',' Wait for resource guard to finish previous request and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16710',' the resource guard is out of memory',' The resource guard was unable to allocate memory while trying to service a request.',' Disable the configuration, shutdown oracle, increase SGA size, and restart.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16711',' the resource guard index is out of bounds',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16712',' the resource handle is invalid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16713',' the resource guard timed out while servicing the request',' The resource guard timed out while servicing the request.',' Verify that the operation is valid for the resource and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16714',' the resource guard exceeded its retry limit',' The resource guard exceeded its retry limit while trying to service a request.',' Verify that the resource is operational and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16715',' the logical standby database requires instantiation',' The resource guard could not execute the request since the logical standby database requires instantiation.',' Instantiate logical standby on the site and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16716',' clearing parameter LOG_ARCHIVE_DEST failed',' An attempt to clear the LOG_ARCHIVE_DEST initialization parameter failed.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16717',' clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed',' An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST initialization parameter failed.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16718',' failed to locate the database resource',' The resource guard was unable to locate the database resource in the configuration.',' Add the database resource and then re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16719',' unable to query V$ARCHIVE_DEST fixed view',' A SQL statement to query V$ARCHIVE_DEST failed.',' Test and clear the problem using SQL*Plus.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16720',' no available LOG_ARCHIVE_DEST_n parameters to use',' All LOG_ARCHIVE_DEST_n parameters have been defined.',' Set some of the LOG_ARCHIVE_DEST_n parameters to an empty string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16721',' unable to set LOG_ARCHIVE_DEST_n parameters',' An attempt of setting some of the LOG_ARCHIVE_DEST_n parameters failed.',' Check the Data Guard console log and database alert logs for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16722',' unable to set LOG_ARCHIVE_DEST_STATE_n parameters',' An attempt of setting some of the LOG_ARCHIVE_DEST_STATE_n parameters failed.',' Check the Data Guard console log and database alert logs for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16723',' the connect descriptor is missing from V$ARCHIVE_DEST',' The resource guard was unable to locate a connect descriptor to a certain standby site in V$ARCHIVE_DEST.',' Check the Data Guard console log for further details. One may need to reset log transport service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16724',' the intended state for resource has been set to OFFLINE',' The intended state of the resource has been set to offline.',' If resource is managed, change intended state to online.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16725',' the phase supplied to resource manager is invalid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16726',' the external condition supplied to resource manager is invalid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16727',' resource guard cannot close database',' The resource guard could not close the database.',' If there are any active sessions connected to the database, then terminate them and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16728',' Log archive destination could not be set',' The resource guard could not set the log archive destination.',' Check the Data Guard console log and the Oracle Alert log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16729',' Error executing dbms_logstdby.log procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16730',' Error executing dbms_logstdby.skip_txn procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16731',' Error executing dbms_logstdby.unskip_txn procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16732',' Error executing dbms_logstdby.skip procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16733',' Error executing dbms_logstdby.unskip procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16734',' Error executing dbms_logstdby.skip_error procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16735',' Error executing dbms_logstdby.unskip_error procedure',' Logical standby package may not be installed.',' Install logical standby packages and re-issue the request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16736',' Standby log archive destination parameter could not be set',' Resource guard could not set the standby log archive destination parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16737',' Log archive format parameter could not be set',' Resource guard could not set the log archive format parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16738',' Database file name convert parameter could not be set',' Resource guard could not set the database file name convert parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16739',' Log file name convert parameter could not be set',' Resource guard could not set log file name convert parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16740',' Log archive trace parameter could not be set',' Resource guard could not set log archive trace parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16741',' Control files parameter could not be set',' Resource guard could not set the control files parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16742',' lock name trace parameter could not be set',' Resource guard could not set lock name trace parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16743',' FAL client parameter could not be set',' Resource guard could not set FAL client parameter.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16744',' FAL server parameter could not be set',' Resource guard could not set FAL server.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16745',' Resource guard encountered error during database dismount',' Resource guard could not dismount database.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16746',' Resource guard encountered error during database mount',' Resource guard could not mount database.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16747',' Logical standby guard could not be turned on',' Resource guard could not turn on the logical standby guard.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16748',' Resource guard encountered errors during database open',' Resource guard could not open database.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16749',' Resource guard encountered errors in switchover to logical primary',' Resource guard could not prepare to switch to logical primary.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16750',' Resource guard encountered errors while activating logical primary',' Resource guard could not activate logical primary.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16751',' Resource guard encountered errors in switchover to primary',' Resource guard could not prepare to switch to primary.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16752',' Resource guard could not mount standby',' Resource guard could not mount standby.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16753',' Resource guard could not open standby database',' Resource guard could not open standby database.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16754',' Resource guard could not activate standby',' Resource guard could not activate standby.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16755',' Resource guard could not dismount standby',' Resource guard could not dismount standby.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16756',' Resource guard could not open standby read-only',' Resource guard could not open standby read-only.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16757',' Resource guard could not get property',' Resource guard failed to get property.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16758',' Resource guard could not verify property',' Resource guard failed to verify property.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16759',' Resource guard unable to start logical apply engine with initial SCN',' Resource guard failed to start logical apply engine with an initial SCN.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16760',' Resource guard could not start logical apply engine',' Resource guard failed to start logical apply engine.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16761',' Resource guard could not stop logical apply engine',' Resource guard failed to stop logical apply engine correctly.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16762',' Invalid database state',' Database is not in the intended state.',' Determine the reason for invalid state, and re-issue get status request.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16763',' Log transport service for some site unexpectedly online',' Log transport service for some site is online when it should be offline.',' Check the Data Guard console log for further details. If necessary, stop the log transport service for the site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16764',' Log transport service for some site unexpectedly offline',' Log transport service for some site is offline when it should be online.',' Check the Data Guard console log for further details. If necessary, start the log transport service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16765',' Physical apply service unexpectedly online',' Physical apply service is online when it should be offline.',' If necessary, stop the physical apply service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16766',' Physical apply service unexpectedly offline',' Physical apply service is offline when it should be online.',' If necessary, start the physical apply service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16767',' Logical apply service unexpectedly online',' Logical apply service is online when it should be offline.',' If necessary, stop the logical apply service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16768',' Logical apply service unexpectedly offline',' Logical apply service is offline when it should be online.',' If necessary, start the logical apply service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16769',' Error executing apply_set procedure',' There was an error executing dbms_logstdby$apply_set procedure.',' Check the values for the property, and set configuration property again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16770',' Error executing apply_unset procedure',' There was an error executing dbms_logstdby$apply_unset procedure.',' Check the values for the property, and set configuration set property again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16771',' Error starting ARCH process(es)',' There was an error starting the archival processes.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16772',' Error in switching over between primary and standby databases',' There was an error during switchover of primary and standby databases.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16773',' Error in starting the physical apply service (MRP process)',' There was an error in starting the physical apply service (MRP process).',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16774',' Error in stopping the physical apply service (MRP process)',' There was an error in stopping the physical apply service (MRP process).',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16775',' The physical apply service terminated prematurely',' The physical apply service terminated prematurely with an error.',' Check the Data Guard console log and Oracle Alert log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16776',' Health check of the log transport service failed',' Due to some internal failure, the database resource guard cannot complete the health check of the log transport service.',' Check the Data Guard console log and Oracle Alert log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16777',' Unable to find the destination entry of a site in V$ARCHIVE_DEST',' Some destination may be manually deleted, or no entry is available for Data Guard.',' Check the Data Guard console log and Oracle Alert log for further details. One may need to reset log transport service.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16778',' The log transport service for some site has an error',' Some problem in communicating with a standby site causes the log transport to fail.',' Check the Data Guard console log and Oracle Alert log for further details. Query the LogXptStatus property to see the error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16779',' The destination parameter of some site has wrong syntax',' The destination is defined in the initialization parameter file with wrong syntax, and the Data Guard broker fails to update the destination when the log transport is turned on.',' Check the Data Guard console log to see which site has the problem. Fix the syntax error in the initialization parameter file or remove the entry. Check if the syntax of the log transport related properties are correct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16780',' Some site has used up its quota',' Some site has used up its quota for storing archived redo logs.',' Check the Data Guard console log to see which site has the problem. Remove some archived logs at the standby site or increase its quota.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16781',' The status of log transport service for some site is unknown',' Log transport to some site has an unknown status.',' Check the Data Guard console log and Oracle Alert log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16782',' Unable to get values of some critical configurable properties',' Log transport cannot be turned on because some critical property values cannot be retrieved from Data Guard metadata.',' Check the Data Guard console log and Oracle Alert log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16783',' Some critical configurable property has not been set',' Log transport cannot be turned on because some critical property has not been set.',' Check the Data Guard console log to see which property has not been set, and set it properly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16784',' The site name given in property Dependency or Alternate is incorrect',' Site name provided in property Dependency or Alternate is wrong.',' Reset property to the correct name of the site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16785',' The database is not in ARCHIVELOG mode',' The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to the primary database.',' Reset the primary database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16786',' Resource guard cannot access Data Guard metadata',' The Data Guard broker configuration files do not exist or the resource guard cannot access the Data Guard metadata.',' Check the Data Guard console log for further details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16788',' Unable to set one or more database configuration property values',' This situation occurs when database resource guard attempts to set database configuration property values into the database by issuing ALTER SYSTEM or ALTER DATABASE statements. Typical causes of this error are:',' Check the Data Guard console log to see which property has the problem and reset the property correctly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16789',' Missing standby redo logs',' Standby redo logs are missing when needed for certain log transport modes.',' Check the Data Guard documentation to create standby redo logs on the standby.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16790',' The value of the configurable property is invalid',' An invalid property value was entered.',' Reset the value to a correct one.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16791',' Unable to check the existence of the standby redo logs',' The database may not be mounted, or the query of V$STANDBY_LOG failed.',' Bring the database to an online state, or fix the problem during the query of V$STANDBY_LOG.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16792',' Some configurable property value is inconsistent with the database setting',' The values of one or more configurable properties are inconsistent with database in-memory settings or SPFILE settings. This may be caused by a user operation on database outside of the Data Guard broker control.',' Query property InconsistentProperties on the site or check the Data Guard console log to find which properties are inconsistent. Reset these properties to make them consistent with the database settings.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16793',' Logical Standby Database Guard is unexpectedly OFF',' The logical standby database guard is OFF.',' Issue the ALTER DATABASE GUARD ALL statement to turn the guard ON and verify that Data Guard health check error/warning is cleared.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16794',' Database Guard is ON for primary database',' Primary database has database guard ON, which is not normal.',' Issue the ALTER DATABASE GUARD NONE statement to turn the guard OFF and verify that Data Guard health check error/warning is cleared.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16795',' Database resource guard detects that database reinstantiation is required',' In the act of failover or switchover, the database resource guard may detect that reinstantiation of the database is necessary due to the impending role change. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database.',' Reinstantiate the database on the site indicated by the broker and then re-add that site to your broker configuration.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16796',' One or more property cannot be imported from database',' Importing existing database settings into the Data Guard properties failed for one or more properties. The cause may be that the database is not mounted or open, or the connection to the standby database being imported is down.',' Check the Data Guard console log to find more details about the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16797',' SPFILE is missing in the Data Guard Broker environment',' Server parameter file is not being used in the database, or the resource guard failed to retrieve the status of the SPFILE.',' Issue a CREATE SPFILE=''...'' FROM PFILE=''...'' statement to create an SPFILE, and restart the database to use the SPFILE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16798',' Unable to complete terminal recovery on the standby',' Terminal recovery on the standby failed during the graceful failover operation.',' Check Data Guard console log and alert logs to see more details on the reason of the failure.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16799',' Physical apply service is offline',' Either the Data Guard metadata indicates the physical apply service is turned off, or the recovery process MRP0 is not running. In either of the cases, physical apply related properties cannot be set.',' Turn on the physical apply service through Data Guard broker, then reset the physical apply related property again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16800',' Log transport service for some site is incorrectly set to ALTERNATE',' Log transport service for some site is currently set to ALTERNATE while no other destinations is set to alternate to this site.',' Check the Data Guard console log for further details. Reset database state to turn on log transport again if necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16801',' Some log transport related property is inconsistent',' The values of one or more log transport related configurable properties of a standby database resource are inconsistent with the primary''s log transport service settings. This may be caused by a user operation on database outside of the Data Guard broker control.',' Query property InconsistentLogXptProps on the primary or Check the Data Guard console log to find which properties are inconsistent. Reset these properties on the appropriate standby to make them consistent with the primary''s log transport settings.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16802',' Cannot set property ''Alternate'' to the primary site name',' Data Guard Broker does not allow the primary site to be an alternate archival destination for a standby site.',' Set property Alternate to empty or to the name of a standby site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16803',' Unable to query a database table or fixed view',' Failed to query a database table or fixed view. The database may not be open or mounted.',' Check Data Guard console log for more details.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16804',' One or more configuration properties in metadata have invalid values',' Data Guard Broker health check detects that one or more configuration properties in metadata have invalid values. They may be entered during the disabled period of database resource or through other means.',' Check Data Guard console log for more details on which properties have invalid values and reset them through Data Guard Broker.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16805',' Change of LogXptMode property violates overall protection mode',' The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database resource. The rejection was necessary since doing so would violate the overall protection mode for the configuration.',' If the LogXptMode configuration property must be changed for the specified standby database resource, then first downgrade the overall protection mode for the configuration. After that operation has completed, you will be able to change the LogXptMode configuration property for the standby database resource.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16806',' Supplemental logging is not turned on',' Supplemental logging is not turned on while there is a logical standby database in the configuration. This could happen either6854// on the primary or on the logical standby that is being switched over to the primary.',' Check Data Guard console log for more details. Issue ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16807',' unable to set protection mode to the database',' An attempt to issue an ALTER DATABASE SET STANDBY TO ... statement failed.',' Check database alter logs and Data Guard console logs for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16900',' Unable to initialize client',' The client could not be initialized.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16901',' Unable to initialize environment',' The database environment could not be allocated and initialized.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16902',' Unable to allocate handle',' The database handles could not be allocated.',' This is an internal error. Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16903',' Unable to connect to database',' The specified database was unreachable because it does not exist or was not started.',' Correct the request or start the database and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16904',' Unable to set attribute',' The server attributes could not be set.',' check additional error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16905',' Failed.',' The given action failed.',' check additional error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16906',' Unable to accept commands: no memory',' No memory was available for the program.',' Increase memory and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16907',' missing field',' A required field was missing.',' Type "help" for syntax and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16908',' Unknown option: "string"',' The given option is not supported.',' Try again using the proper command line syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16909',' Fatal Error. quitting...',' A fatal error was encountered.',' See additional error messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16910',' unable to issue command to server',' Commands cannot be issued to the server.',' See additional error messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16911',' Warning:',' An action succeeded with warnings.',' See error message and take appropriate action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16912',' Unknown command "string". Try "help"',' An unknown command was issued.',' Try again using a valid command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16914',' Missing connect string. Try "help"',' The connect string for the database is missing.',' Try the command again with a valid connect string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16916',' Missing site. Try "help"',' The site name is missing.',' Try the command again using correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16917',' Missing XML document. Try "help"',' The XML document argument was missing.',' Try the command again using correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16939',' Could not start up "string" as primary',' The named site could not be started in the primary role.',' See additional messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16940',' Started "string" as new primary',' The named site was started as the new primary site.',' No action is required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16942',' Could not start up "string" as standby',' The named site could not be started in the standby role.',' See additional messages..');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16943',' Started "string" as standby',' The named site was started as the new primary site.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16944',' Failover succeeded. New primary is "string"',' The failover operation succeeded.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16945',' Syntax error before or at "string"',' The given command could not be processed because a syntax error occurred at the named token.',' Try the command again using valid syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16946',' Site "string" was not found',' The named site could not be found.',' Try the command again using a valid site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16947',' "string" does not run in the primary role',' The named resource does not run in the primary role.',' Try the command again using a resource that runs in the primary role.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16948',' "string" does not run in the standby role',' The named resource does not run in the standby role.',' Try the command again using a resource that runs in the standby role.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16949',' Resource "string" was not found',' The named resource was not found.',' Try the command again using a valid resource.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16950',' Unable to retrieve "string" for editing',' The named object could not be retrieved for editing.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16951',' manager information not found',' The manager information could not be retrieved for a generic resource.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16952',' unable to describe configuration',' The configuration could not be described.',' The framework could not be contacted. Check to see that the DMON process is running.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16953',' site or resource "string" does not exist',' The named site or resource does not exist.',' Try the command again using a valid site or resource.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16954',' a resource cannot run on multiple sites this way',' An attempt was made to create a resource that depends on multiple sites. This is not possible using one command.',' Issue the command twice; one with the first site and the second using the second site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16955',' unable to create or locate template',' The template could not be found.',' See additional error messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16956',' missing template name',' The template name was omitted from the command.',' Try the command again using a valid template name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16957',' template "string" was not found',' The named template could not be found.',' Try the command again using a valid template name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16958',' unable to convert document',' The document could not be converted.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16959',' NULL answer from framework',' No answer came from the framework.',' The framework is not available. Check to see that the DMON process exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16960',' status not available',' The status could not be retrieved.',' The framework is not available. Check to see that the DMON process exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16991',' ambiguous resource name',' The named resource exists on more than one site.',' The request must be more specific. Issue the command again using the ON SITE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-16992',' You must restart site "string" manually.',' The operation was successfully completed, and it requires a restart of given site. However, DGMGRL was unable to perform an automatic restart. The user has to shutdown and startup the site manually.',' Shut down the given site and start it up.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17500',' ODM err:string',' An error returned by ODM library',' Look at error message and take appropriate action or contact Oracle Support Services for further assistance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17501',' logical block size string is invalid',' logical block size for oracle files must be a multiple of the physical block size, and less than the maximum',' check parameters in the initialization parameter file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17502',' ksfdcre: string Failed to create file string',' file creation failed due to either insufficient OS permission or the file already exists',' check additional error messages');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17503',' ksfdopn: string Failed to open file string',' file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.',' check additional error messages');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17504',' ksfddel:Failed to delete file string',' The file thats being deleted is still in use or the process has insufficient permission to delete file.',' check additional error messages');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17505',' ksfdrsz: string Failed to resize file to size number blocks',' There is insufficient space left on the device or the process has insufficient permission to resize file.',' check additional error messages');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17506',' I/O Error Simulation',' The i/o request is marked with error because the i/o error simulation event is turned on.',' none');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17507',' I/O request size string is not a multiple of logical block size',' i/o''s are done in multiple of logical block size',' Check additional error messages');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17508',' I/O request buffer ptr is not alligned',' i/o request buffer should be alligned, check additional information for buffer ptr value',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17509',' Attempt to do i/o beyond block1 offset',' When a file is identified with logical block size of 0, only i/o''s to block1 is allowed.',' check additional error messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17510',' Attempt to do i/o beyond file size',' The i/o request points to a block beyond End Of File',' check additional error messages and contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17610',' file ''string'' does not exist and no size specified',' An attempt to create a file a file found neither an existing file nor a size for creating the file.',' Specify a size for the file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-17611',' ksfd: file ''string'' cannot be accessed, global open closed',' An attempt to write to a file which has gone offline/unidentified.',' Check for other errno in the stack.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18000',' invalid outline name',' The parser detected a missing or invalid outline name.',' reissue the command, specifying a valid outline name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18001',' no options specified for ALTER OUTLINE',' The parser detected that no clause was specified on the command.',' reissue the command, specifying a valid ALTER OUTLINE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18002',' the specified outline does not exist',' Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.',' Check for the existence of the outline and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18003',' an outline already exists with this signature',' The signature generation algorithm generates signatures that are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.',' Either reissue the statement that led to the outline being created with some white space added or force the outline to be created in a different category.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18004',' outline already exists',' An outline already exists, either with the specified name, or for the specified SQL text.',' Try again with another name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18005',' create any outline privilege is required for this operation',' Create any outline privilege is required for the attempted operation.',' Make sure you have create any outline privilege and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18006',' drop any outline privilege is required for this operation',' Drop any outline privilege is required for the attempted operation.',' Make sure you have drop any outline privilege and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18007',' alter any outline privilege is required for this operation',' Alter any outline privilege is required for the attempted operation.',' Make sure you have alter any outline privilege and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18008',' cannot find OUTLN schema',' The database creation script that creates this schema must not have been executed.',' Review the log files to see what happened when the database was created.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18009',' one or more outline system tables do not exist',' Either the database creation script that creates these tables was not executed or a user accidently deleted the table.',' Review the log files to see what happened when the database was created.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18010',' command missing mandatory CATEGORY keyword',' User failed to specify the CATEGORY keyword.',' reissue the command with the CATEGORY keyword included.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18011',' the outline specified in the FROM clause does not exist',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18012',' select_catalog_role role is required for this operation',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18013',' timed out while waiting for resource string',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18014',' deadlock detected while waiting for resource string',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-18015',' invalid source outline signature',' User imported an 8i outline into a 9i database without updating signatures.',' Execute dbms_outln.update_signatures.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19000',' missing RELATIONAL keyword',' The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.',' Supply the RELATIONAL keyword in the storage clause');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19001',' Invalid storage option specified',' An invalid storage option was specified for the XMLType.',' Supply a valid storage option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19002',' Missing XMLSchema URL',' A XML schema URL must be specified in the storage option.',' Specify a URL for the XMLSchema.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19003',' Missing XML root element name',' A root element in the XMLSchema must be specified if the XML schema is given.',' Specify a root element in the XML schema.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19004',' Duplicate XMLType OBJECT RELATIONAL storage option',' A duplicate storage option for the XMLType column was specified',' Specify a single storage option for an XMLType column');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19005',' Duplicate XMLType LOB storage option',' A duplicate storage option for the XMLType column was specified',' Specify a single storage option for an XMLType column');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19006',' XMLType TYPE storage option not appropriate for storage type',' The TYPE option can only be used in case of OBJECT RELATIONAL storage option',' Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19007',' Schema and element do not match',' The schema and element specified in the inserted data does not match that of the column',' Insert/Update only the XML documents that conform to that particular schema and element.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19008',' Invalid version of the XMLType',' An invalid version of the XMLType was found.',' This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19009',' Missing XMLSchema keyword',' The XMLSchema keyword is missing',' Specify the XMLSchema URL and element name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19010',' Cannot insert XML fragments',' XML fragments got from extractNode cannot be inserted into the database.',' Convert the fragment into a proper XML document before insertion.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19011',' Character string buffer too small',' The string result asked for is too big to return back',' Get the result as a lob instead');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19012',' Cannot convert XML fragment to the required datatype',' A conversion to a datatype was requested which cannot be performed',' The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19013',' Cannot create VARRAY columns containing XMLType',' An attempt was made to create a VARRAY column which contains a XMLType',' You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19015',' Invalid XML tag identifier (string)',' An invalid XML identifier was detected during XML generation.',' Fix the offending tag so it does not contain characters or symbols that are not allowed by the XML specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19016',' attributes cannot occur after element specifications',' Attributes specified using the "@" identifier can only occur before any other element definition when creating XML.',' Change the order of the types so that the attributes occur at the beginning.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19017',' Attributes can only be simple scalars',' Attribute values can only be simple scalar values.',' Use only simple datatypes for attribute values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19018',' Invalid character in XML tag ''string''',' A tag name was found to have an invalid XML character during XML generation.',' Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19019',' Invalid context passed to DBMS_XMLGEN.GETXML',' The value of context passed to GETXML was invalid.',' Rewrite the query so that the value of context passed to GETXML is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19020',' invalid dereference of XMLType columns',' An attempt was made to dereference the attributes of an XMLType column which is not part of a base table.',' You can only dereference the attributes of a base table XMLType column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19023',' The first argument to UPDATEXML operator has to be an XMLTYPE',' The first argument passed to the update value operator was not an XMLTYPE.',' Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19024',' Cursor expression must be named',' The value of context passed to GETXML was invalid.',' Rewrite the query so that the value of context passed to GETXML is valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19025',' EXTRACTVALUE returns value of only one node',' Given XPath points to more than one node.',' Rewrite the query so that exactly one node is returned.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19026',' EXTRACTVALUE can only retrieve value of leaf node',' Given XPath does not point to a leaf node.',' Rewrite the query so that a leaf node is returned.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19028',' Invalid ADT parameter passed to toObject() function',' The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.',' Pass an object of the correct type to toObject().');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19029',' Cannot convert the given XMLType to the required type',' The passed in XMLType could not be converted to the required type.',' Binary XMLtype instances or other objects cannot be converted to the required object or collection types.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19030',' Method invalid for non-schema based XML Documents.',' The method can be invoked on only schema based xmltype objects.',' Don''t invoke the method for non schema based xmltype objects.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19031',' XML element or attribute string does not match any in type string.string',' The passed in XML tag does not match any in the object type.',' Pass a valid canonical XML that can map to the given object type.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19032',' Expected XML tag string got string',' When converting XML to object, a wrong tag name was present.',' Pass a valid canonical XML that can map to the given object type');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19033',' schema specified in the XML document does not match the schema parameter',' When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the ''schema'' parameter.',' Change the schema parameter to match the schema specified in the XML document.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19034',' Type not supported during schema generation',' The object type contained a type that is not supported for schema generation.',' Use a different type or do not generate a schema.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19200',' Invalid column specification',' All input arguments must be valid columns',' Specify a valid list of columns');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19201',' Datatype not supported',' The particular datatype is not supported in the XMLGEN operator',' Specify only supported datatypes as arguments to the XMLGEN operator');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19202',' Error occurred in XML processing string',' An error occurred when processing the XML function',' Check the given error message and fix the appropriate problem');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19203',' Error occurred in DBMS_XMLGEN processing string',' An error occurred when processing the DBMS_XMLGEN functions',' Check the given error message and fix the appropriate problem');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19204',' Non-scalar value ''string'' is marked as XML attribute',' Only scalar values (that is values which are not of object or collection type) can be marked as XML attribute, that is prefixed by ''@''. In this case, a non-scalar value was prefixed with ''@''.',' Remove the ''@'' sign, or make the value a scalar.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19205',' Attribute ''string'' qualifies a non-scalar value in the select list',' The attribute immediately follows a value of object or collection type in the select list or type definition.',' Remove the ''@'' sign, or make the previous value a scalar.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19206',' Invalid value for query or REF CURSOR parameter',' The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query or REF CURSOR.',' Rewrite the query so that the queryString argument is a valid query or REF CURSOR.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19207',' scalar parameter string of XMLELEMENT cannot have an alias.',' The scalar parameter to XMLELEMENT has been qualified with an alias.',' Remove the AS clause of the scalar element.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19208',' parameter string of function string must be aliased',' The indicated parameter of the XML generation function has not been aliased, although it is an expression.',' Specify an alias for the expression using the AS clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19209',' invalid or unsupported formatting argument',' An invalid or unsupported formatting argument was supplied.',' Change the formatting argument to legal supported values.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19300',' Error occurred in uri processing string',' An error occurred when processing the URL',' Check the given error message and fix the appropriate problem');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19320',' Host name not specified in HTTP URL',' A host name was not specified in the HTTP url',' Specify a host name in the HTTP url when creating the URL string');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19321',' Could not open HTTP connection to host (string): port (string)',' A HTTP connection could not be opened to the host',' Specify a valid host name and port to connect to');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19322',' An error occurred while reading from host (string): port (string)',' An error occurred while reading from the HTTP host',' Specify a valid host name and port to read from');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19323',' Invalid url string',' The URL must be a valid URL string',' Specify a valid url string');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19330',' Type ''string''.''string'' not installed. Please install the type before using the CREATE_DBURI operator',' The type required for the CREATE_DBURI operator has not been installed correctly.',' Read the installation notes to install the type correctly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19331',' Last argument to CREATE_DBURI operator must be a column',' The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.',' Specify a valid column name in the query.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19332',' Invalid column in the CREATE_DBURI operator',' The argument to the CREATE_DBURI operator can only be a column.',' Specify a valid column name for the operator');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19333',' Invalid flags for the CREATE_DBURI operator',' The flags argument given to the DBURI operator is invalid',' Specify a valid flag value (TEXT) for the DBURI operator');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19334',' Invalid column specification for CREATE_DBURI operator',' All columns must be valid and pointing to the same table or view',' Specify valid list of columns that are from the same table or view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19335',' Invalid format type object',' An invalid format type object was specified for the XML function',' Specify a valid format type object');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19336',' Missing XML root element',' The XML being generated does not have an enclosing root element.',' The generated XML must have a root element.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01500',' failure in getting date/time',' During CREATE DATABASE or ALTER TABLESPACE, there was a failure in getting the date and time.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01501',' CREATE DATABASE failed',' An error occurred during CREATE DATABASE.',' See accompanying errors.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01502',' index ''string.string'' or partition of such index is in unusable state',' An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation.',' DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01503',' CREATE CONTROLFILE failed',' An error occurred during CREATE CONTROLFILE.',' See accompanying errors.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01504',' database name ''string'' does not match parameter db_name ''string''',' The name in a database create or mount does not match the name given in the initialization parameter DB_NAME.',' Correct or omit one of the two names.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01505',' error in adding log files',' During CREATE or ALTER DATABASE, error(s) occurred when adding new log files.',' Check error stack for detailed error information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01506',' missing or illegal database name',' No database name was specified in the CREATE/ALTER DATABASE statement, and no DB_NAME initialization parameter was specified.',' Either the database name must be given in the statement or in the DB_NAME initialization parameter. Note that the SVRMGR or SQL*PLUS STARTUP command issues an ALTER DATABASE statement using the database name specified as part of STARTUP (if any).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01507',' database not mounted',' A command was attempted that requires the database to be mounted.',' If you are using the ALTER DATABASE statement via the SVRMGR or SQL*PLUS STARTUP command, specify the MOUNT option to restart; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01508',' cannot create database; error in file ''string'' at line string',' CREATE DATABASE was unable to process the specified file.',' Check the offending line in the specified file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01509',' specified name ''string'' does not match actual ''string''',' The database name specified in ALTER DATABASE does not match the name of the currently mounted database.',' Correct the database name spelling or DISMOUNT the mounted database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01510',' error in deleting log files',' During ALTER DATABASE, an error occurred while dropping log files.',' Check the error stack for detailed error information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01511',' error in renaming log/data files',' During ALTER DATABASE, an error occurred while renaming log or datafiles.',' Check the error stack for detailed error information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01512',' error renaming log file string - new file string not found',' An attempt to change a log file''s name in the control file failed because no file was found with the new name.',' Make sure that the log file has been properly renamed by the operating system and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01513',' invalid current time returned by operating system',' The operating system returned a time that was not between 1988 and 2121.',' Correct the time kept by the operating system.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01514',' error in log specification: no such log',' A log file name, or list of member names, did not correspond to an existing log.',' Specify an existing log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01515',' error dropping log group string: no such log',' ALTER DATABASE is attempting to drop a log file which is not known to the database control file.',' Specify the name of an existing log file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01516',' nonexistent log file, datafile, or tempfile "string"',' An attempt was made to use ALTER DATABASE to rename a log file, datafile, or tempfile; or to change attributes of a datafile or tempfile (for example, such as resize, autoextend, online/offline, and so on); or to re-create a datafile. The attempt failed because the specified file is not known to the database''s control file or is not of a type supported by the request.',' Specify the name or number of an existing file of the correct type, as appropriate. Check the relevant V$ table for a list of possible files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01517',' log member: ''string''',' This message indicates the filename involved with other messages.',' See the accompanying messages and take appropriate action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01518',' CREATE DATABASE must specify more than one log file',' Only one log file was specified in the CREATE DATABASE statement.',' Specify at least two log files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01519',' error while processing file ''string'' near line string',' CREATE DATABASE encountered a problem while processing specified file. The specified file is bad.',' Retry your system installation procedure or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01520',' number of data files to add (string) exceeds limit of string',' CREATE TABLESPACE statement specifies more files than is permitted for this database.',' Use fewer files or re-create the control file with a larger value of MAXDATAFILES.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01521',' error in adding data files',' During CREATE or ALTER TABLESPACE, an error was detected while adding datafiles.',' Check the error stack for detailed error information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01522',' file ''string'' to be renamed does not exist',' During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.',' Specify the correct file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01523',' cannot rename data file to ''string'' - file already part of database',' During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.',' Rename the file to a name not already being used as part of the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01524',' cannot create data file as ''string'' - file already part of database',' During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.',' Create the file as a name not already being used as part of the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01525',' error in renaming data files',' An error occurred when renaming files as part of ALTER TABLESPACE.',' Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01526',' error in opening file ''string''',' CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error.',' Retry your system installation procedure or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01527',' error while reading file',' CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.',' Retry your system installation procedure or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01528',' EOF while processing SQL statement',' CREATE DATABASE unexpectedly hit EOF while reading the specified file. The SQL.BSQ file is bad.',' Retry your system installation procedure or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01529',' error closing file ''string''',' CREATE DATABASE was not able to close the specified file.',' Retry your system installation procedure or contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01530',' a database already mounted by the instance',' During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted.',' If you wish to mount the database, shut down and then restart the instance and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01531',' a database already open by the instance',' During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.',' If you wish to open a new database on the instance, first shut down and then restart the instance and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01532',' cannot create database; instance being started elsewhere',' During CREATE DATABASE, another user appears to be simultaneously altering the instance.',' Make sure no one else is simultaneously altering the instance. If no one is, contact Oracle Support Services; otherwise, retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01533',' cannot rename file ''string''; file does not belong to tablespace',' During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.',' Specify the correct file name or the correct tablespace name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01534',' rollback segment ''string'' doesn''t exist',' During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.',' Use the correct rollback segment name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01535',' rollback segment ''string'' already exists',' Specified rollback segment already exists.',' Use a different name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01536',' space quota exceeded for tablespace ''string''',' The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace.',' Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01537',' cannot add data file ''string'' - file already part of database',' During CREATE or ALTER TABLESPACE, a file being added is already part of the database.',' Use a different file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01538',' failed to acquire any rollback segment',' Failed to acquire any rollback segment during startup in shared mode.',' Restart in exclusive mode to create one more public segment or specify available private segments in the initialization parameter. ROLLBACK_SEGMENTS_REQUIRED, then start in shared mode');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01539',' tablespace ''string'' is not online',' Failed to either make a tablespace read only or offline because it is not online. A tablespace must be online before it can become read only or offline normal.',' Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01540',' tablespace ''string'' is not offline',' Failed to bring a tablespace online because it is not offline.',' Check the status of the tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01541',' system tablespace cannot be brought offline; shut down if necessary',' An attempt was made to bring system tablespace offline.',' Shut down if necessary to do recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01542',' tablespace ''string'' is offline, cannot allocate space in it',' An attempt was made to allocate space in an offline tablespace.',' Bring the tablespace online or create the object in other tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01543',' tablespace ''string'' already exists',' An attempt was made to create a tablespace which already exists.',' Use a different name for the new tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01544',' cannot drop system rollback segment',' An attempt was made to drop system rollback segment.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01545',' rollback segment ''string'' specified not available','See Oracle',NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01546',' tablespace contains active rollback segment ''string''',' An attempt was made to make a tablespace that contains active rollback segment(s) offline or read only.',' Shut down instances that use the active rollback segments in the tablespace and then make the tablespace offline or read only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01547',' warning: RECOVER succeeded but OPEN RESETLOGS would get error below',' Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.',' Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01548',' active rollback segment ''string'' found, terminate dropping tablespace',' An attempt was made to drop a tablespace that contains active rollback segment(s).',' Shut down instances that use the active rollback segments in the tablespace and then drop the tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01549',' tablespace not empty, use INCLUDING CONTENTS option',' An attempt was made to drop a non-empty tablespace.',' To drop all the objects in the tablespace, use the INCLUDING CONTENTS option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01550',' cannot drop system tablespace',' An attempt was made to drop system tablespace. This is not allowed.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01551',' extended rollback segment, pinned blocks released',' Doing recursive extent of rollback segment, trapped internally by the system.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01552',' cannot use system rollback segment for non-system tablespace ''string''',' An attempt was made to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.',' Create one or more private/public segment(s), shut down and restart. May need to modify the initialization parameter ROLLBACK_SEGMENTS to acquire private rollback segment. If this is a clone database being used for tablespace point in time recovery then this operation is not allowed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01553',' MAXEXTENTS must be no smaller than the string extents currently allocated',' The number of extents allocated is greater than the MAXEXTENTS specified.',' Specify a larger MAXEXTENTS value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01554',' out of transaction slots in transaction tables',' Too many concurrent transactions.',' Shut down the system, modify the initialization parameters TRANSACTIONS, ROLLBACK_SEGMENTS or ROLLBACK_SEGMENTS_REQUIRED, and then restart.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01555',' snapshot too old: rollback segment number string with name "string" too small',' Rollback records needed by a reader for consistent read are overwritten by other writers.',' If in Automatic Undo Management mode, increase the setting of UNDO_RETENTION. Otherwise, use larger rollback segments.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01556',' MINEXTENTS for rollback segment must be greater than 1',' Specified MINEXTENTS of less than 2 for rollback segment.',' Specify larger MINEXTENTS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01557',' rollback segment extents must be at least string blocks',' Specified extent of less than minimum size for rollback segment.',' Specify larger extents.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01558',' out of transaction ID''s in rollback segment string',' All the available transaction IDs have been used.',' Shut down the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction IDs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01559',' MAXEXTENTS for rollback segment must be greater than 1',' Specified MAXEXTENTS of less than 2 for rollback segment.',' Specify larger MAXEXTENTS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01560',' LIKE pattern contains partial or illegal character',' Like pattern is not formed correctly.',' Make sure like pattern is specified correctly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01561',' failed to remove all objects in the tablespace specified',' Failed to remove all objects when dropping a tablespace.',' Retry the drop tablespace until all objects are dropped.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01562',' failed to extend rollback segment number string',' Failure occurred when trying to extend rollback segment.',' This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintenance. Use SELECT SEGMENT_NAME FROM DBA_ROLLBACK_SEGS WHERE SEGMENT_ID=string (where string is the segment number from the message) to determine the rollback segment name. Then use the ALTER ROLLBACK SEGMENT OFFLINE command to take the rollback segment offline.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01563',' rollback segment is PUBLIC, need to use the keyword PUBLIC',' Did not use the keyword PUBLIC to identified public rollback segment.',' Use the keyword PUBLIC when identifying public rollback segment.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01564',' rollback segment is not PUBLIC',' The rollback segment identified is not public.',' Do not use the keyword PUBLIC when identifying private rollback segment.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01565',' error in identifying file ''string''',' An error occurred while trying to identify a file.',' Check the error stack for detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01566',' file specified more than once in DROP LOGFILE',' The list of files supplied to DROP LOGFILE contains at least one duplicate.',' Remove the duplicate file specification and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01567',' dropping log string would leave less than 2 log files in thread string',' Dropping all the logs specified would leave fewer than the required two log files per enabled thread.',' Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01568',' cannot set space quota on PUBLIC',' An attempt was made to set space quota on a tablespace for PUBLIC.',' If trying to grant system-wide or tablespace-wide space privileges to all users, use GRANT RESOURCE [ON tablespace] TO PUBLIC.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01569',' data file too small for system dictionary tables',' The datafile specified during creation of the database is too small to hold the system dictionary tables.',' Re-create the database by specifying a larger file or more files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01570',' MINEXTENTS must be no larger than the string extents currently allocated',' The number of extents allocated is smaller than the MINEXTENTS specified.',' Specify a smaller MINEXTENTS value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01571',' redo version string incompatible with ORACLE version string',' This software version cannot read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.',' Shut down and restart using the compatible software. Do any required media recovery, and open the database. Shut down and restart using the current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01572',' rollback segment string cannot be brought online, string extents exceeded',' The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.',' Drop and re-create the rollback segment.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01573',' shutting down instance, no further change allowed',' Some process tried to make changes while the database was being shut down.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01574',' maximum number of concurrent transactions exceeded',' The limit on the number of concurrent transactions has been hit.',' Shut down the system, increase the value of the initialization parameter TRANSACTIONS, and then restart the system.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01575',' timeout waiting for space management resource',' Failed to acquire necessary resource to do space management.',' Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01576',' instance locking protocol version string incompatible with ORACLE version string',' Current software uses incompatible locking protocol.',' Upgrade software used to start instances so that they use compatible locking protocol.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01577',' cannot add log file ''string'' - file already part of database',' During CREATE or ALTER DATABASE, a file being added is already part of the database.',' Use a different file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01578',' ORACLE data block corrupted (file # string, block # string)',' The data block indicated was corrupted, probably due to program errors.',' Determine which object was corrupted using a command like the following:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01579',' write error occurred during recovery',' A write error occurred during recovery.',' Consult trace files for the nature of the write error, and correct error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01580',' error creating control backup file string',' An operating system error occurred while attempting to create a control file backup.',' Check the error stack for more detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01581',' attempt to use rollback segment (string) new extent (string) which is being allocated',' Undo generated to extend a rollback segment has run out of current undo block space. Oracle is attempting to write into the new extent which has not been completely allocated.',' The rollback segment extending will be rolled back by the system, no more extension will be possible until the next extent is freed up by rolling back or committing other transactions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01582',' unable to open controlfile for backup',' An operating system error occurred while attempting to open a control file for backup.',' Check the error stack for more detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01583',' unable to get block size of controlfile to be backed up',' An operating system error occurred while attempting to get the block size of a control file for backup.',' Check the error stack for more detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01584',' unable to get file size of controlfile to be backed up',' An operating system error occurred while attempting to get the file size of a control file for backup.',' Check the error stack for more detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01585',' error identifying backup file string',' An operating system error occurred when attempting to identify the file to be used for control file backup.',' Check the error stack for more detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01586',' unable to open destination file string for backup',' An operating system error occurred while attempting to open a control file for backup.',' Check the error stack for more detailed information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01587',' error during controlfile backup file copy',' An operating system error occurred while attempting to copy a control file for backup.',' Check the accompanying message stack for detailed information and then take appropriate action.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01588',' must use RESETLOGS option for database open',' An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup.',' Use the RESETLOGS option when opening the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01589',' must use RESETLOGS or NORESETLOGS option for database open',' Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.',' Specify the appropriate option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01590',' number of segment free list (string) exceeds maximum of string',' The value of the storage parameter FREELIST GROUPS is too large.',' Reduce the value of the storage parameter FREELIST GROUPS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01591',' lock held by in-doubt distributed transaction string',' An attempt was made to access resource that is locked by a dead two-phase commit transaction that is in prepared state.',' The database administrator should query the PENDING_TRANS$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, the database administrator should contact the database administrator at the commit point if known or the end user for correct outcome, or use heuristic default if given to issue a heuristic COMMIT or ABORT command to finalize the local portion of the distributed transaction.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01592',' error converting Version 7 rollback segment (string) to Oracle 8 format',' Look at the accompanying internal error; Version 7 database may not have shut down cleanly.',' Investigate the internal error; may have to reload the Version 7 database (from backup) and shut down the database cleanly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01593',' rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)',' Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.',' Specify a larger OPTIMAL size.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01594',' attempt to wrap into rollback segment (string) extent (string) which is being freed',' Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and/or there are too many extents to free.',' The rollback segment shrinking will be rolled back by the system; increase the optimal size of the rollback segment.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01595',' error freeing extent (string) of rollback segment (string))',' Some error occurred while freeing inactive rollback segment extents.',' Investigate the accompanying error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01596',' cannot specify system in string parameter',' The system rollback segment is specified in the initialization parameter referred to in the error message.',' Change the value of the initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01597',' cannot alter system rollback segment online or offline',' An attempt was made to online or offline the system rollback segment.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01598',' rollback segment ''string'' is not online',' Could have been taken offline before by the database administrator or cleaned up by SMON.',' Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS to make sure the rollback segment is actually online.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01599',' failed to acquire rollback segment (string), cache space is full',' The amount statically allocated is not enough based on the value of the MAX_ROLLBACK_SEGMENTS parameter.',' For now, take another rollback segment offline or increase the value of the parameter MAX_ROLLBACK_SEGMENTS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01600',' at most one "string" in clause "string" of string',' The initialization parameter was incorrectly specified.',' Correct the initialization parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01601',' illegal bucket size in clause "string" of string',' The bucket size was invalid for this parameter.',' Correct the initialization parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01603',' illegal grouping size in clause "string" of string',' The grouping size was invalid for this parameter.',' Correct the initialization parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01604',' illegal number range in clause "string" of string',' The number range was invalid for this parameter.',' Correct the initialization parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01605',' missing numbers in clause "string" of string',' The numbers were missing for this parameter.',' Correct the initialization parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01606',' gc_files_to_locks not identical to that of another mounted instance',' The GC_FILES_TO_LOCKS parameters were different on two instances.',' Modify the initialization parameter GC_FILES_TO_LOCKS and restart.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01607',' gc_lck_procs (string) is not the same as other instances (string)',' The GC_LCK_PROCS initialization parameter is not the same as in other instances that already have the database open.',' Modify the GC_LCK_PROCS parameter and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01608',' cannot bring rollback segment ''string'' online, its status is (string)',' Could have been brought online before by the database administrator or left as a result of process crash.',' Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01609',' log string is the current log for thread string - cannot drop members',' A member of the current log for a thread cannot be dropped.',' If the thread is opened, request a log switch by the instance that is using it. If it is not open, disable the thread, manually archive the log, or clear it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01610',' recovery using the BACKUP CONTROLFILE option must be done',' Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was re-created with the RESETLOGS option, or the control file being used is a backup control file. After that only BACKUP CONTROLFILE recovery is allowed and it must be followed by a log reset at the next database open.',' Perform recovery using the BACKUP CONTROFILE option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01611',' thread number string is invalid - must be between 1 and string',' A thread number in a command is greater than the number of threads supported by the control file.',' Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01612',' thread string is already enabled',' An attempt was made to enable a thread that is already enabled.',' Either use this thread or enable another thread.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01613',' thread string only has string logs - at least 2 logs required to enable',' The thread cannot be enabled because it only has two online log files associated with it.',' Add logs to the thread or pick another thread to enable.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01614',' thread string is busy - cannot enable',' The mount enqueue for the thread could not be acquired when attempting to enable the thread. This probably means that another process has already started enabling this thread.',' Wait and try again, or find another thread to enable.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01615',' thread string is mounted - cannot disable',' Some instance, possibly this one, has allocated the thread for its use. The thread may not be disabled while in use.',' Shut down cleanly the instance using the thread.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01616',' thread string is open - cannot disable',' The thread is not closed. The last instance to use the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for crash or instance recovery.',' If the database is open, instance recovery should close the thread soon; wait a few minutes. Otherwise open the database; crash recovery will close the thread.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01617',' cannot mount: string is not a valid thread number',' The value of the initialization parameter THREAD is not between 1 and the number of threads allowed by the control file.',' Shut down the instance, change the value of the initialization parameter and restart, or resize the thread record and/or checkpoint progress record sections of the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01618',' thread string is not enabled - cannot mount',' The value of the initialization parameter THREAD requests a thread that is not enabled. A thread must be enabled before it can be mounted.',' Shut down the instance, change the value of the initialization parameter and restart, mounting a different thread. If the database is open in another instance, then the thread may be enabled.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01619',' thread string is mounted by another instance',' The value of the initialization parameter THREAD requests a thread that has been mounted by another instance. Only one instance may use a thread.',' Shut down the instance, change the value of the initialization parameter and restart, mounting a different thread.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01620',' no public threads are available for mounting',' The value of the initialization parameter THREAD is zero, its default value. There are no threads which have been publicly enabled, and not mounted.',' Shut down the instance, change the value of the initialization parameter to a thread which is privately enabled and not mounted. If the database is open in another instance, then a thread may be publicly enabled.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01621',' cannot rename member of current log if database is open',' This is a rename command for a member of the current log for an open thread. If the database is open anywhere, the log may be in use, so the rename cannot be done.',' Wait until the log is not current, or mount the database exclusively.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01622',' thread number must be specified - default not specific',' The thread was not specified when adding a log, and the currently mounted thread was chosen by default at mount time. Since the current thread was not specified explicitly the user cannot know which thread the log will be added to.',' Explicitly specify the thread number either in the initialization parameter THREAD, or in the ADD command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01623',' log string is current log for thread string - cannot drop',' A thread''s current log cannot be dropped even if the thread is closed. A disabled thread usually does not have a current log, but a half completed disable may need to be disabled again.',' If the database is not open then disable the thread. If the database is open and an instance has the thread open, then the instance can be requested to switch logs. If the database is closed the log can be archived or cleared to force a switch.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01624',' log string needed for crash recovery of thread string',' A log cannot be dropped or cleared until the thread''s checkpoint has advanced out of the log.',' If the database is not open then open it. Crash recovery will advance the checkpoint. If the database is open force a global checkpoint. If the log is corrupted so that the database cannot be opened, it may be necessary to do incomplete recovery until cancel at this log.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01625',' rollback segment ''string'' does not belong to this instance',' An attempt was made to shrink or take a rollback segment offline that does not belong to this instance.',' Take only those rollback segments offline that belong to the current instance. To take the rollback segment offline, connect to the instance containing it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01626',' rollback segment number ''string'' cannot handle more transactions',' Too many transactions in this segment.',' Choose a different rollback segment, or reduce the number of concurrent transactions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01627',' rollback segment number ''string'' is not online',' Could have been taken offline before by the database administrator or cleaned up by SMON.',' Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS to make sure the rollback segment is actually online.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01628',' max # extents (string) reached for rollback segment string',' An attempt was made to extend a rollback segment that was already at the MAXEXENTS value.',' If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, raise this value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01629',' max # extents (string) reached saving undo for tablespace string',' Save undo for the offline tablespace at MAXEXTENTS.',' Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01630',' max # extents (string) reached in temp segment in tablespace string',' A temporary segment tried to extend past MAXEXTENTS.',' If MAXEXTENTS for the tablespace is less than the system maximum, you can raise that. Otherwise, raise PCTINCREASE for the tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01631',' max # extents (string) reached in table string.string',' A table tried to extend past MAXEXTENTS.',' If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01632',' max # extents (string) reached in index string.string',' An index tried to extend past MAXEXTENTS.',' If the value of MAXEXTENTS in the index storage clause is less than the maximum (based on your block size), raise it. Otherwise, re-create the index with larger extent sizes so that the total number of extents falls below the maximum.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01633',' Real Application Clusters Option needed for this operation',' System does not have Real Application Clusters configured.',' Obtain Real Application Clusters option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01634',' rollback segment number ''string'' is about to go offline',' The rollback segment specified was marked to go offline by the database administrator.',' Bring the rollback segment online first.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01635',' rollback segment #string specified not available',' One of the following:',' For the above, one of the following:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01636',' rollback segment ''string'' is already online',' A rollback segment can only be used by one instance and an instance is trying to bring a rollback segment online that is already in use.',' Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See the Oracle9i Database Administrator''s Guide for more information about using rollback segments in parallel mode.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01637',' rollback segment ''string'' is being used by another instance (#string)',' A rollback segment can only be used by one instance, and an instance is trying to access a rollback segment online that is already in use.',' Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See the Oracle9i Database Administrator''s Guide for more information about using rollback segments in parallel mode.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01638',' parameter string does not allow ORACLE version string to mount cluster database',' The value of the RECOVERY_COMPATIBLE parameter is set too low to allow this software version to mount in cluster database mode.',' Either use an earlier software release or advance the RECOVERY_COMPATIBLE parameter. If this happens when no RECOVERY_COMPATIBLE parameter has been specified then set it to the current software release.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01640',' cannot make tablespace read only with active transactions',' An attempt was made to make a tablespace read only while there are active transactions in the database. All transactions must commit or rollback to insure that there is no undo for a tablespace before it can be made read only. This includes in doubt distributed transactions.',' Prevent any more transactions from being started. Putting the database in restricted mode usually helps. If there are any in doubt transactions they must also be resolved.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01641',' tablespace ''string'' is not online - cannot add data file',' An attempt was made to add a datafile to a tablespace that has been set to read only or offline.',' Make the tablespace online and read write then add the datafile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01642',' begin backup not needed for read only tablespace ''string''',' An attempt was made to begin or end a backup for a tablespace that has been set to read only.',' Take the backup without any BEGIN or END commands. The files are not being modified so the backup will be consistent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01643',' system tablespace can not be made read only',' An attempt was made to set the system tablespace to read only. The system tablespace must remain read write for database operation.',' Leave system tablespace read write.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01644',' tablespace ''string'' is already read only',' An attempt was made to make tablespace read only that is already read only.',' Leave tablespace read only, or make read write then make read only again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01645',' previous attempt to make read write is half complete',' A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be usable after a resetlogs if its files are offline.',' Repeat the command to make the tablespace read write.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01646',' tablespace ''string'' is not read only - cannot make read write',' An attempt was made to make a tablespace read write that is not read only. It may be either online or offline.',' Leave tablespace read write.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01647',' tablespace ''string'' is read only, cannot allocate space in it',' An attempt was made to allocate space in a read-only tablespace.',' Create the object in another tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01648',' log string is the current log of disabled thread string',' An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log cannot be cleared or archived.',' Complete the thread enable by issuing the ENABLE command again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01649',' operation not allowed with a backup controlfile',' An attempt is being made to perform a command that does not make sense when the control file is a restored backup.',' Wait until after the database has been opened and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01650',' unable to extend rollback segment string by string in tablespace string',' Failed to allocate an extent for rollback segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01651',' unable to extend save undo segment by string for tablespace string',' Failed to allocate an extent for saving undo entries for the indicated offline tablespace.',' Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01652',' unable to extend temp segment by string in tablespace string',' Failed to allocate an extent for temporary segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01653',' unable to extend table string.string by string in tablespace string',' Failed to allocate an extent for table segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01654',' unable to extend index string.string by string in tablespace string',' Failed to allocate an extent for index segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01655',' unable to extend cluster string.string by string in tablespace string',' Failed to allocate an extent for cluster segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01656',' max # extents (string) reached in cluster string.string',' A cluster tried to extend past MAXEXTENTS.',' If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01657',' invalid SHRINK option value',' The specified value must be an integer.',' Choose an appropriate integer value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01658',' unable to create INITIAL extent for segment in tablespace string',' Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.',' Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01659',' unable to allocate MINEXTENTS beyond string in tablespace string',' Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.',' Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01660',' tablespace ''string'' is already permanent',' An attempt was made to make tablespace permanent that is already permanent.',' Leave tablespace permanent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01661',' tablespace ''string'' is already temporary',' An attempt was made to make tablespace temporary that is already temporary.',' Leave tablespace permanent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01662',' tablespace ''string'' is non-empty and cannot be made temporary',' An attempt was made to convert a non-empty tablespace to a temporary tablespace',' Drop all the objects in the tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01663',' the contents of tablespace ''string'' is constantly changing',' The contents of the tablespace is always changing between PERMANENT and TEMPORARY.',' Decide what the tablespace contents should be and stay with it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01664',' Transaction which has expanded the Sort Segment has aborted',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01665',' controlfile is not a standby controlfile',' An attempt was made to mount, recover or activate a standby database without a standby control file.',' Create a standby control file before attempting to use the database as a standby database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01666',' controlfile is for a standby database',' An attempt was made to mount, recover, or open a standby database without the appropriate command option to designate a standby database.',' Use the standby option or appropriate commands, or mount with the primary control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01667',' cannot add any more tablespaces: limit of string exceeded',' There is no more room in the control file for adding tablespaces.',' Resize the control file or drop other tablespaces.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01668',' standby database requires DROP option for offline of data file',' An attempt was made to take a datafile offline in a standby database without specifying the DROP option. Files that are offline in a standby database are not recovered, and are likely to be unusable if the standby is activated. Note that specifying DROP does not prevent bringing the file online later.',' Specify the DROP option or leave the file online.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01669',' standby database controlfile not consistent',' An attempt was made to activate a standby database with a control file that has not been recovered to the same point as the datafiles. Most likely the control file was just copied from the primary database and has not been used for recovery.',' Recover the standby database until all the files are consistent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01670',' new datafile string needed for standby database recovery',' Standby database recovery noticed that a file was added to the primary database, but is not available on the standby.',' Either copy the file from the primary database or do an ALTER DATABASE CREATE DATAFILE command on the standby to create a file to recover.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01671',' controlfile is a backup, cannot make a standby controlfile',' The currently mounted control file is a backup control file, and attempting to create a control file for a standby database.',' Complete any needed recovery and open the database with the resetlogs option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01672',' controlfile may be missing files or have extra ones',' An attempt was made to create a standby control file, but the control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the control file and the ones in the data dictionary may not match.',' Open the database, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01673',' data file string has not been identified',' This datafile was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we cannot create a standby control file.',' Find the file and bring it online. If desired it may be taken offline again. If you intend to drop this file, then taking it offline with the DROP option will avoid this error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01674',' data file string is an old incarnation rather than current file',' Recovery encountered redo that indicates this file was dropped from the database and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file.',' Rebuild the control file using CREATE CONTROLFILE, and give the correct file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01675',' max_commit_propagation_delay inconsistent with other instances',' The MAX_COMMIT_PROPAGATION_DELAY initialization parameter is inconsistent with those in other instances.',' Make sure all instances have the same MAX_COMMIT_PROPAGATION_DELAY.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01676',' standby file name convert of ''string'' exceeds maximum length of string',' When the given file name is converted to the name used for the standby database, the converted name is bigger than the maximum allowed file name.',' Change the value of the initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01677',' standby file name convert parameters differ from other instance',' The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT initialization parameters are not the same as in other instances that already have the database mounted.',' Change the value of the initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match other instances.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01678',' parameter string must be pairs of pattern and replacement strings',' The initialization parameter does not have an even number of strings for its value. The odd numbered strings are patterns to be found in file names. The even numbered strings are used to replace the corresponding patterns when found in file names.',' Specify an even number of strings for the parameter, or omit the parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01679',' database must be mounted EXCLUSIVE and not open to activate',' An attempt to activate a standby database was made when the database was not mounted EXCLUSIVE or was already open.',' Mount the database EXCLUSIVE and retry the ACTIVATE command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01680',' unable to extend LOB segment by string in tablespace string',' Failed to allocate an extent for a LOB segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01681',' max # extents (string) reached in LOB segment in tablespace string',' A LOB segment tried to extend past MAXEXTENTS.',' If MAXEXTENTS for the tablespace is less than the system maximum, you can raise that. Otherwise, raise PCTINCREASE for the tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01682',' read-only DB cannot allocate temporary space in tablespace string',' Temporary space (usually for sorting) could not be allocated in either main storage or a temporary file. An attempt was made to allocate the space from the tablespace named, but the database is opened read only. The database open requires a sort work space.',' Either allow sufficient workspace in main storage (SORT_AREA_SIZE initialization parameter), or create a temporary tablespace before making the database read only. Use ALTER TABLESPACE ADD TEMPFILE statement to add temporary files to the temporary tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01683',' unable to extend index string.string partition string by string in tablespace string',' Failed to allocate an extent for index segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01684',' max # extents (string) reached in table string.string partition string',' A table tried to extend past MAXEXTENTS.',' If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01685',' max # extents (string) reached in index string.string partition string',' An index tried to extend past MAXEXTENTS.',' If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01686',' max # files (string) reached for the tablespace string',' The number of files for a given tablespace has reached its maximum value.',' Resize existing files in the tablespace, or partition the objects among multiple tablespaces, or move some objects to a different tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01687',' specified logging attribute for tablespace ''string'' is same as the existing',' An attempt was made to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute.',' Change the specified logging attribute.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01688',' unable to extend table string.string partition string by string in tablespace string',' Failed to allocate an extent for table segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01689',' syntax error in clause "string" of string',' There was a syntax in the initialization parameter.',' Fix the syntax error and restart the instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01690',' sort area size too small',' The sort area size was too small to fit two records in memory.',' Increase the SORT_AREA_SIZE initialization parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01691',' unable to extend lob segment string.string by string in tablespace string',' Failed to allocate an extent for LOB segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01692',' unable to extend lob segment string.string partition string by string in tablespace string',' Failed to allocate an extent for LOB segment in tablespace.',' Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01693',' max # extents (string) reached in lob segment string.string',' A LOB segment tried to extend past MAXEXTENTS.',' If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01694',' max # extents (string) reached in lob segment string.string partition string',' A LOB segment tried to extend past MAXEXTENTS.',' If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01695',' error converting rollback segment string to version 8.0.2',' Version 8.0.1 database may not have shut down cleanly.',' May have to reload the 8.0.1 database and shut down cleanly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01696',' controlfile is not a clone controlfile',' An attempt was made to mount, a database as a clone when it is already mounted by another instance not as a clone or attempting to use a current control file for a clone.',' Mount without the clone option or use a backup control file and shut down the other instances before mounting as a clone.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01697',' controlfile is for a clone database',' An attempt was made to mount a clone database without the appropriate command option to designate a clone database.',' Use the clone option or appropriate commands, or mount with the primary control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01698',' a clone database may only have SYSTEM rollback segment online',' An attempt was made to online a rollback segment in a clone database.',' Do not use this command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01699',' tablespace ''string'' is being imported for point in time recovery',' An attempt was made to online a tablespace or begin another point in time import while a point in time import is already in progress.',' Wait until the import completes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01700',' duplicate username in list',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01701',' a cluster is not appropriate here',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01702',' a view is not appropriate here',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01703',' missing SYNONYM keyword',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01704',' string literal too long',' The string literal is longer than 4000 characters.',' Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01705',' an outer join cannot be specified on a correlation column',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01706',' user function result value was too large',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01707',' missing LIST keyword',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01708',' ACCESS or SESSION expected',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01709',' program does not exist',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01710',' missing OF keyword',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01711',' duplicate privilege listed',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01712',' you cannot grant a privilege which you do not have',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01713',' GRANT OPTION does not exist for that privilege',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01714',' error in execution of user function',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01715',' UNIQUE may not be used with a cluster index',' An attempt was made to create a cluster index with the UNIQUE attribute.',' Remove UNIQUE from the CREATE INDEX statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01716',' NOSORT may not be used with a cluster index',' An attempt was made to create a cluster index using the NOSORT option.',' Remove NOSORT from the CREATE INDEX statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01717',' seccta: invalid access mode token passed',NULL,NULL);
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01718',' BY ACCESS | SESSION clause not allowed for NOAUDIT',' Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.',' Remove BY ACCESS | SESSION.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01719',' outer join operator (+) not allowed in operand of OR or IN',' An outer join appears in an or clause.',' If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) union all (select where (B)).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01720',' grant option does not exist for ''string.string''',' A grant was being performed on a view and the grant option was not present for an underlying object.',' Obtain the grant option on all underlying objects of the view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01721',' USERENV(COMMITSCN) invoked more than once in a transaction',' The USERENV(''COMMITSCN'') function can only be used once in a transaction.',' Re-write the transaction to use USERENV(''COMMITSCN'') only once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01722',' invalid number',' The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.',' Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01723',' zero-length columns are not allowed',' During CREATE TABLE, a zero-length column was specified, for example, CHAR(0).',' Correct the column declaration so that the length is at least 1 and try the operation again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01724',' floating point precision is out of range (1 to 126)',' Floating point precision is too small or large.',' Correct and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01725',' USERENV(''COMMITSCN'') not allowed here',' The function USERNEV(''COMMMITSCN'') is only allowed as a top-level expression in the VALUES clause of an INSERT statements, and on the right hand side of an assignment in an UPDATE statement.',' Correct the use of the function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01726',' a table is not appropriate here',' A table name was used in a statement in which tables are not permitted.',' Enter a valid table statement or use the current statement on the appropriate object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01727',' numeric precision specifier is out of range (1 to 38)',' The precision specified for a number column in a CREATE/ALTER TABLE or CREATE CLUSTER statement must be a digit between 1 and 38. If no precision is specified, a default precision of 22 digits is used.',' Specify numeric precision between 1 and 38 and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01728',' numeric scale specifier is out of range (-84 to 127)',' The scale specified for a numeric field in a CREATE/ALTER TABLE or CREATE CLUSTER statement is not in the valid range. It should be between -84 and 127.',' Specify a numeric scale between -84 and 127. If a number is not specified, the default scale of the column is 0 decimal places.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01729',' database link name expected',' A database link name does not follow the at-sign (@) in a reference to a table in a remote database.',' Correct the reference and retry the operation. The correct syntax for denoting a table in a remote database follows:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01730',' invalid number of column names specified',' The number of column names specified in a CREATE VIEW statement did not correspond to the number of columns listed in the SELECT clause. If column names are specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause.',' Specify one view column name for each column in the SELECT clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01731',' circular view definition encountered',' Through a series of CREATE and DROP VIEW statements, a view was defined that refers to itself. For example, VIEW1 might include a column from VIEW2 that is defined as a column in VIEW1. View definitions may be seen by querying the data dictionary.',' Check the view definitions, remove any circular references, and retry the statements.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01732',' data manipulation operation not legal on this view',' An attempt was made to use an UPDATE, INSERT, or DELETE statement on a view that contains expressions or functions or was derived from more than one table. If a join operation was used to create the view or the view contains virtual columns derived from functions or expressions, then the view may only be queried.',' UPDATE, INSERT, or DELETE rows in the base tables instead and restrict the operations on the view to queries.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01733',' virtual column not allowed here',' An attempt was made to use an INSERT, UPDATE, or DELETE statement on an expression in a view.',' INSERT, UPDATE, or DELETE data in the base tables, instead of the view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01734',' illegal parameters - EXTENT MIN higher than EXTENT MAX',' An incorrect value is specified for the parameter.',' Correct the parameter and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01735',' invalid ALTER TABLE option',' An invalid option was specified in an ALTER TABLE statement.',' Check the statement syntax, specify a valid option, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01736',' [NOT] SUCCESSFUL expected',' An AUDIT or NOAUDIT statement contained WHENEVER followed by something other than SUCCESSFUL or NOT SUCCESSFUL.',' Correct the WHENEVER clause and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01737',' valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE',' The lock mode entered was not recognized.',' Enter one of the following: SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, SHARE ROW EXCLUSIVE, or SHARE UPDATE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01738',' missing IN keyword',' In a LOCK TABLE statement, the keyword IN was missing.',' Place the keyword IN and lock mode directly after the table name in the LOCK TABLE statement and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01739',' missing MODE keyword',' In a LOCK TABLE statement, the keyword MODE was missing. The keyword MODE must directly follow the specified lock mode.',' Check the statement syntax, insert the keyword MODE where required, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01740',' missing double quote in identifier',' An initial double quote (") was found without a closing quote. If an identifier contains a blank or special characters other than $, #, or _, it must be enclosed in double quotes.',' Add a closing double quote (") to the end of the identifier.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01741',' illegal zero-length identifier',' An attempt was made to use two double quotes ("") as an identifier. An identifier must be at least one character long.',' Insert at least one character between the double quotes in the identifier. If a blank identifier is required, specify a blank space between the double quotes (" ").');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01742',' comment not terminated properly',' The indicated comment or hint begun with the /* token did not have the terminating */.',' Properly terminate the comment or hint with a */.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01743',' only pure functions can be indexed',' The indexed function uses SYSDATE or the user environment.',' PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV(), or anything else dependent on the session state. NLS-dependent functions are OK.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01744',' inappropriate INTO',' The INTO clause may not be used in a subquery.',' Check the syntax, place the INTO clause in the top-level query, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01745',' invalid host/bind variable name',' A colon in a bind variable or INTO specification was followed by an inappropriate name, perhaps a reserved word.',' Change the variable name and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01746',' indicator variable not permitted here',' An indicator variable is not permitted in this context.',' Remove the indicator variable and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01747',' invalid user.table.column, table.column, or column specification',' A column name was specified improperly in the current SQL statement.',' Check the statement''s syntax, especially references to column names, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01748',' only simple column names allowed here',' This SQL statement does not allow a qualified column name, such as username.table.column or table.column.',' Remove the qualifications from the column and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01749',' you may not GRANT/REVOKE privileges to/from yourself',' Grantor is not allowed to grant or revoke object or system privileges to self.',' Issue the GRANT or REVOKE of system privileges from another database administrator account.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01750',' UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column',' Although it is possible to GRANT update privileges on a column-by-column basis, it is only possible to REVOKE them for an entire table.',' Do not identify specific columns. To revoke update privileges for certain columns, use REVOKE for the entire table and GRANT the user privileges for specific columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01751',' Invalid dump undo option',' An invalid option is specified in the ALTER DUMP UNDO command.',' Correct and reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01752',' cannot delete from view without exactly one key-preserved table',' The deleted table either had no key preserved tables, had more than one key-preserved table, or the key-preserved table was an unmerged view or a table from a read-only view.',' Redefine the view or delete it from the underlying base tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01753',' column definition incompatible with clustered column definition',' When adding a table to a cluster, the definition of the column in the table was inconsistent with the definition of the column in the cluster.',' The table cannot be added to the cluster until all cluster column definitions are consistent.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01754',' a table may contain only one column of type LONG',' An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.',' Remove the LONG column currently in the table by using the ALTER TABLE command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01755',' Must specify an extent number or block number',' Expecting an extent or block number but something else was specified.',' Correct the error and reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01756',' quoted string not properly terminated',' A quoted string must be terminated with a single quote mark ('').',' Insert the closing quote and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01757',' Must specify an object number',' Expecting an object number but something else was specified.',' Correct the error and reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01758',' table must be empty to add mandatory (NOT NULL) column',' It is not possible to define a new column as NOT NULL if rows already exist in the table being modified.',' Retry the statement without the NOT NULL specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01759',' user function is incorrectly defined',' A user function has been improperly defined.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01760',' illegal argument for function',' The argument or arguments specified for the function are not valid in this context.',' Check the definition of the function and correct the arguments.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01761',' DML operation does not map to a unique table in the join',' The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.',' Change the join specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01762',' vopdrv: view query block not in FROM',' This is an internal error message not normally issued.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01763',' update or delete involves outer joined table',' For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer- joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table.',' Change the join specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01764',' new update value of join is not guaranteed to be unique',' A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.',' Change the join specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01765',' specifying table''s owner name is not allowed',' A table or view name was specified with a period (.) or identified with an invalid prefix.',' Check that the object is identified correctly and if necessary remove the period from the name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01766',' dictionary table not allowed in this context',' The name of a data dictionary object was used outside the FROM clause of a SELECT statement. The only operation allowed on a data dictionary object is to SELECT from it.',' Restrict operations on data dictionary objects to queries.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01767',' UPDATE ... SET expression must be a subquery',' An attempt was made to use a single expression without a subquery to update a list of columns.',' Check the syntax for using subqueries to update data and add the necessary subquery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01768',' number string too long',' A number entered exceeds the limit of 255 characters, including digits, sign, decimal point, and exponent.',' Shorten the number string, perhaps by expressing it in scientific notation, for example, 1.85E9 instead of 1,850,000,000.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01769',' duplicate CLUSTER option specifications',' During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.',' Remove the extra CLUSTER option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01770',' CLUSTER option not allowed in CREATE CLUSTER command',' An attempt was made to use the CLUSTER option within a CREATE CLUSTER statement.',' Remove the CLUSTER clause and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01771',' illegal option for a clustered table',' During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE, CACHE, NOCACHE. These options may only be specified for the cluster itself.',' Remove the illegal option(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01772',' Must specify a value for LEVEL',' Expecting the value of LEVEL but something else was specified.',' Correct the error and reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01773',' may not specify column datatypes in this CREATE TABLE',' Column datatypes were specified in a SELECT statement used to create and load a table directly.',' Remove column datatypes. The datatypes of the SELECT list expressions are automatically used as the column datatypes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01774',' Dump undo option specified more than once',' The same option for ALTER DUMP UNDO was specified twice.',' Remove the redundant options and reissue the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01775',' looping chain of synonyms',' Through a series of CREATE synonym statements, a synonym was defined that referred to itself. For example, the following definitions are circular:',' Change one synonym definition so that it applies to a base table or view and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01776',' cannot modify more than one base table through a join view',' Columns belonging to more than one underlying table were either inserted into or updated.',' Phrase the statement as two or more separate statements.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01777',' WITH GRANT OPTION not allowed in this system',' This version of Oracle does not support the WITH GRANT OPTION.',' Remove the WITH GRANT option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01778',' maximum subquery nesting level exceeded',' An attempt was made to use more than 255 levels of nested subqueries.',' Merge some of the subqueries into their containing queries, until there are less than 255 levels of nesting.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01779',' cannot modify a column which maps to a non key-preserved table',' An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.',' Modify the underlying base tables directly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01780',' string literal required',' In a COMMENT statement, the Comment following the keyword IS must be a quoted string literal.',' Check that the Comment is a string literal.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01781',' UNRECOVERABLE cannot be specified without AS SELECT',' UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.',' Do not specify UNRECOVERABLE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01782',' UNRECOVERABLE cannot be specified for a cluster or clustered table',' A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.',' Do not specify UNRECOVERABLE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01783',' only one RECOVERABLE or UNRECOVERABLE clause may be specified',' RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.',' Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01784',' RECOVERABLE cannot be specified with database media recovery disabled',' A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.',' Do not specify RECOVERABLE, or restart the database with media recovery enabled.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01785',' ORDER BY item must be the number of a SELECT-list expression',' Either an ORDER BY item for a set expression is not a column number, or the ORDER BY item is not the number of a SELECT list column.',' The ORDER BY item must be a number between 1 and the number of columns in the SELECT list. Check the column number and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01786',' FOR UPDATE of this query expression is not allowed',' An attempt was made to use a FOR UPDATE clause on the result of a set expression involving GROUP BY, DISTINCT, UNION, INTERSECT, or MINUS.',' Check the syntax, remove the FOR UPDATE clause, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01787',' only one clause allowed per query block',' An attempt was made to use more than one WHERE, GROUP BY, CONNECT BY, or HAVING clause in the query.',' Combine the duplicate clauses into a single clause and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01788',' CONNECT BY clause required in this query block',' A START WITH clause was specified without a CONNECT BY clause.',' Check the syntax, specify a CONNECT BY clause, and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01789',' query block has incorrect number of result columns',' All of the queries participating in a set expression do not contain the same number of SELECT list columns.',' Check that all the queries in the set expression have the same number of SELECT list columns.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01790',' expression must have same datatype as corresponding expression',' A SELECT list item corresponds to a SELECT list item with a different datatype in another query of the same set expression.',' Check that all corresponding SELECT list items have the same datatypes. Use the TO_NUMBER, TO_CHAR, and TO_DATE functions to do explicit data conversions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01791',' not a SELECTed expression',' There is an incorrect ORDER BY item. The query is a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY items must be constants, SELECT list expressions, or expressions whose operands are constants or SELECT list expressions.',' Remove the inappropriate ORDER BY item from the SELECT list and retry the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01792',' maximum number of columns in a table or view is 1000',' An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.',' If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01793',' maximum number of index columns is 32',' While creating an index, more than 32 columns were specified.',' Remove some columns from the index definition. If all the columns indexed are required, split them into two indexes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01794',' maximum number of cluster columns is 32',' More than 32 columns were specified in the cluster key.',' Remove some of the columns from the cluster key definition. Consider concatenating multiple character strings into a single column.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01795',' maximum number of expressions in a list is 1000',' More than 254 columns or expressions were specified in a list.',' Remove some of the expressions from the list.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01796',' this operator cannot be used with lists',' A relational operator is not allowed in this context. When comparing lists, use only an operator that tests for equivalence, such as =, !=, or IN.',' Rephrase the query so that it only compares lists for equivalence. For example, the following clause is invalid:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01797',' this operator must be followed by ANY or ALL',' The keyword ANY or ALL was missing.',' Check the statement syntax and add ANY or ALL where appropriate.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01798',' missing EXCEPTION keyword',' The EXCEPTION keyword is missing from the ENABLE clause.',' Correct the syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01799',' a column may not be outer-joined to a subquery',' expression(+) relop (subquery) is not allowed.',' Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01800',' a literal in the date format was too large to process',' A literal specified in a date format was too large. If a literal is entered as a date, it must be less than 220 characters long.',' Use only literals less than 220 characters long in the date format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01801',' date format is too long for internal buffer',' The date format string was too long to process. This should occur only if several long literals are specified as part of a date.',' Remove long literals from the date format string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01802',' Julian date is out of range',' An invalid Julian date was entered. Valid Julian dates run from 1 to 3,442,447.',' Enter a valid Julian date between 1 and 3,442,447.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01803',' failure in getting date/time',' This is an internal error message that is not likely to occur. It is usually caused by a failure in the system clock.',' Investigate the system clock and the process that requested the date or time. If necessary, contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01804',' failure to initialize timezone information',' The timezone information file was not properly read.',' Please contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01810',' format code appears twice',' A format code was listed twice in a date specification. Each format code may be specified only once in the function TO_DATE.',' Remove the duplicate format code from the date specification, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01811',' Julian date precludes use of day of year',' Both a Julian date and a day of the year were specified in the TO_DATE function. If a Julian date is specified, the day of the year (DDD) may not be specified, as it is contained in the Julian date.',' Remove the day of the year or the Julian date from the specification, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01812',' year may only be specified once',' More than one year format code was listed in a date specification. Only one of the following year format codes may be specified in a date: YYYY, YYY, YY, Y.',' Remove all but one year format from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01813',' hour may only be specified once',' More than one hour format code was listed in a date specification. Only one of the following hour format codes may be specified in a date: HH, HH12, HH24.',' Remove all but one hour format from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01814',' AM/PM conflicts with use of A.M./P.M.',' Both types of meridian indicators, AM and PM, were listed in a date specification. If one of the meridian indicator format masks, such as AM or A.M., is specified in the date, the other may not be specified.',' Use one meridian indicator format, with or without periods, consistently.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01815',' BC/AD conflicts with use of B.C./A.D.',' Both types of BC/AD indicators were listed in a date specification. If one of the BC/AD indicator format masks, such as BC or B.C., is specified in the date, the other may not be specified.',' Use one BC/AD indicator format, with or without periods, consistently.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01816',' month may only be specified once',' More than one month format code was listed in a date specification. Only one of the following month format codes may be specified in a date: MM, MON, MONTH.',' Remove all but one month format from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01817',' day of week may only be specified once',' More than one day-of-the-week format code was listed in a date specification. Only one of the following day-of-the-week format codes may be specified in a date: D, DY, DAY.',' Remove all but one day-of-the-week format from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01818',' ''HH24'' precludes use of meridian indicator',' A date specification contained both a 24-hour time format code and a meridian indicator code. If hours are specified using the 24-hour time format (HH24), a meridian indicator, AM or PM, may not be specified.',' Remove the meridian indicator format code, AM/PM or A.M./P.M., or the 24-hour time format code, HH24, from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01819',' signed year precludes use of BC/AD',' A date specification contained both a signed year and a B.C./A.D. indicator. If the year is specified with a sign, such as SYYYY, then B.C. or A.D. is implicit in the date and must not be entered.',' Remove the B.C./A.D. indicator from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01820',' format code cannot appear in date input format',' A date specification contained an invalid format code. Only the following may be specified when entering a date: year, month, day, hours, minutes, seconds, Julian day, A.M./P.M. and B.C./A.D.',' Remove the invalid format code from the date specification.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01821',' date format not recognized',' A date specification contained an invalid format code.',' Check that only valid date format codes are specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01822',' era format code is not valid with this calendar',' An era format code, E or EE, was specified with a calendar which does not use era information.',' Retry the operation using a date format mask which does not contain era format codes.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01830',' date format picture ends before converting entire input string',' A valid date format picture included extra data. The first part of the format picture was converted into a valid date, but the remaining data was not required.',' Check the specifications for date format pictures and correct the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01831',' year conflicts with Julian date',' The wrong year was specified with a Julian day. If a year is specified with a Julian date, it must be the year in which the Julian date occurs.',' Remove the year value from the date specification or enter the correct year for the Julian date.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01832',' day of year conflicts with Julian date',' A Julian date was specified with the day of the year but the day did not correspond to the Julian date. If the day of the year is specified with a Julian date, it must be the same day as the Julian date.',' Remove the day of the year value from the date specification or enter the correct day for the Julian date.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01833',' month conflicts with Julian date',' The wrong month was specified with a Julian date. If a month is specified with a Julian date, it must be the month in which the Julian date occurs.',' Remove the month value from the date specification or enter the correct month for the Julian date.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01834',' day of month conflicts with Julian date',' A Julian date was specified with the day of the month, but the month day did not correspond to the Julian date. If the day of the month is specified with a Julian date, it must be the same day of the month as the Julian date.',' Remove the day of the month value from the date specification or enter the correct day of the month for the Julian date.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01835',' day of week conflicts with Julian date',' A Julian date was specified with the day of the week, but the weekday did not correspond to the Julian date. If the day of the week is specified with a Julian date, it must be the same day of the week as the Julian date.',' Remove the day of the week value from the date specification or enter the correct day of the week for the Julian date.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01836',' hour conflicts with seconds in day',' The wrong hour was specified with seconds in the day. If an hour is specified with seconds past midnight (SSSSS), it must be the hour in which the seconds value falls.',' Remove the hour value from the date specification or specify the correct hour for the seconds past midnight.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01837',' minutes of hour conflicts with seconds in day',' A date specification contained both minutes of the hour and seconds in the day but the values did not correspond. If both minutes in the hour (MI) and seconds past midnight (SSSSS) are specified, the minutes value must be the minute in which the seconds value will occur.',' Remove the minutes value from the date specification or enter the correct minute value for the specified seconds value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01838',' seconds of minute conflicts with seconds in day',' A date specification contained both seconds of the minute and seconds in the day but the values did not correspond. If both types of seconds are specified, the seconds of the minute value (SS) must be the second in which the seconds past midnight value (SSSSS) will fall.',' Remove the seconds of the minute value from the date specification or enter a value that corresponds to the given seconds in the day.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01839',' date not valid for month specified',' The day of the month specified in the date is invalid for the given month. The day of the month (DD) must be between 1 and the number of days in the month.',' Enter a valid day of the month for the specified month.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01840',' input value not long enough for date format',' The data to be converted to date format was incomplete; the date format picture was longer than the input data.',' Either add more input or shorten the date picture format, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01841',' (full) year must be between -4713 and +9999, and not be 0',' A date specified a year that is not in the valid date range. A valid date is any date between January 1, 4712 B.C. and December 31, 9999 A.D.',' Enter a valid date value between 4712 B.C. and 9999 A.D.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01842',' quarter must be between 1 and 4',' An invalid value was specified for the quarter of the year in a date. The quarter (Q) must be between 1 and 4.',' Enter a value for quarter between 1 and 4.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01843',' not a valid month',' A date specified an invalid month. Valid months are: January-December, for format code MONTH, and Jan-Dec, for format code MON.',' Enter a valid month value in the correct format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01844',' week of year must be between 1 and 52',' An invalid value was specified for the week of the year in a date. Week of the year (WW) must be between 1 and 52.',' Enter a week of the year value between 1 and 52.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01845',' week of month must be between 1 and 5',' An invalid value was specified for the week of the month in a date. Week of the month (W) must be between 1 and 5.',' Enter a week of the month value between 1 and 5.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01846',' not a valid day of the week',' A date specified an invalid day of the week. Valid days are:',' Enter a valid day of the week value in the correct format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01847',' day of month must be between 1 and last day of month',' The day of the month listed in a date is invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month.',' Enter a valid day value for the specified month.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01848',' day of year must be between 1 and 365 (366 for leap year)',' An invalid day of the year was specified in a date. Day of the year (DDD) must be between 1 and 365 for a non-leap year or 1 and 366 for a leap year.',' Enter a day of the year value between 1 and 365 (or 366).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01849',' hour must be between 1 and 12',' An invalid hour was specified for a date using the 12-hour time format. If a 12-hour format code (HH or HH12) is used, the specified hour must be between 1 and 12.',' Enter an hour value between 1 and 12.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01850',' hour must be between 0 and 23',' An invalid hour was specified for a date using the 24-hour time format. If the 24-hour format code (HH24) is listed, the specified hour must be between 0 and 23.',' Enter an hour value between 0 and 23.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01851',' minutes must be between 0 and 59',' An invalid minute value was specified in a date. Minutes must be between 0 and 59.',' Enter a minute value between 0 and 59.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01852',' seconds must be between 0 and 59',' An invalid seconds value was specified in a date. Seconds must be between 0 and 59 if the seconds format code (SS) is used.',' Enter a seconds value between 0 and 59.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01853',' seconds in day must be between 0 and 86399',' An invalid value for seconds in the day was specified in a date. Seconds must be between 0 and 86399 if the seconds past midnight format code (SSSSS) is used.',' Specify a seconds value between 0 and 86399.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01854',' julian date must be between 1 and 5373484',' An invalid Julian date was entered.',' Enter a valid Julian date between 1 and 5373484.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01855',' AM/A.M. or PM/P.M. required',' A date specification contained a meridian indicator format code but a valid meridian indicator was not specified. If a meridian indicator code, A.M./P.M. or AM/PM, is included in a date format, the date must include a valid meridian indicator.',' Specify the meridian indicator in the correct format, A.M./AM or P.M./PM.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01856',' BC/B.C. or AD/A.D. required',' A date specification contained a BC/AD format code but a valid BC/AD indicator was not specified. If one of the BC/AD format codes, BC/AD or B.C./A.D., is specified in a date format, the date must include BC/B.C. or AD/A.D.',' Specify the BC/AD indicator in the date using the correct format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01857',' not a valid time zone',' An incorrect time zone code was specified for the NEW_TIME function.',' Correct the invalid time zone code, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01858',' a non-numeric character was found where a numeric was expected',' The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.',' Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01859',' a non-alphabetic character was found where an alphabetic was expected',' The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.',' Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01860',' week of year must be between 1 and 53',' A week number outside the range 1 to 53 was specified.',' Use only a value within the valid range for the week number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01861',' literal does not match format string',' Literals in the input must be the same length as literals in the format string (with the exception of leading white space). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra white space.',' Correct the format string to match the literal.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01862',' the numeric value does not match the length of the format item',' When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will.',' Correct the input date or turn off the FX or FM format specifier in the format string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01863',' the year is not supported for the current calendar',' The year is not supported for the current calendar.',' Check the documentation to find out what years are supported for the current calendar.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01864',' the date is out of range for the current calendar',' Your calendar does not extend to the specified date.',' Specify a date which is legal for this calendar.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01865',' not a valid era',' Era input does not match a known era.',' Provide a valid era on input.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01866',' the datetime class is invalid',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01867',' the interval is invalid',' The character string you specified is not a valid interval.',' Specify a valid interval.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01868',' the leading precision of the interval is too small',' The leading precision of the interval is too small to store the specified interval.',' Increase the leading precision of the interval or specify an interval with a smaller leading precision.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01869',' reserved for future use',' Not an error.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01870',' the intervals or datetimes are not mutually comparable',' The intervals or datetimes are not mutually comparable.',' Specify a pair of intervals or datetimes that are mutually comparable.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01871',' the number of seconds must be less than 60',' The number of seconds specified was greater than 59.',' Specify a value for seconds that is 59 or smaller.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01872',' reserved for future use',' Not an error.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01873',' the leading precision of the interval is too small',' The leading precision of the interval is too small to store the specified interval.',' Increase the leading precision of the interval or specify an interval with a smaller leading precision.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01874',' time zone hour must be between -12 and 13',' The time zone hour specified was not in the valid range.',' Specify a time zone hour between -12 and 13.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01875',' time zone minute must be between -59 and 59',' The time zone minute specified was not in the valid range.',' Specify a time zone minute between -59 and 59.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01876',' year must be at least -4713',' The specified year was not in range.',' Specify a year that is greater than or equal to -4713.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01877',' string is too long for internal buffer',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01878',' specified field not found in datetime or interval',' The specified field was not found in the datetime or interval.',' Make sure that the specified field is in the datetime or interval.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01879',' the hh25 field must be between 0 and 24',' The specified hh25 field was not in the valid range.',' Specify an hh25 field between 0 and 24.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01880',' the fractional seconds must be between 0 and 999999999',' The specified fractional seconds were not in the valid range.',' Specify a value for fractional seconds between 0 and 999999999.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01881',' timezone region id number is invalid',' The region id referenced an invalid region.',' Please contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01882',' timezone region string not found',' The specified region name was not found.',' Please contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01883',' overlap was disabled during a region transition',' The region was changing state and the overlap flag was disabled.',' Please contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01890',' NLS error detected',' An NLS error was detected.',' Look for additional error messages and take appropriate action. If there are no additional errors, contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01891',' Datetime/Interval internal error',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01898',' too many precision specifiers',' While trying to truncate or round dates, extra data was found in the date format picture.',' Check the syntax of the date format picture and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01899',' bad precision specifier',' An invalid precision code was specified in a date.',' Enter a valid precision code in the date format. Valid precision types are: century, year, month, day, Julian date, hours, minutes, and seconds.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01900',' LOGFILE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01901',' ROLLBACK keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01902',' SEGMENT keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01903',' EVENTS keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01904',' DATAFILE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01905',' STORAGE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01906',' BACKUP keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01907',' TABLESPACE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01908',' EXISTS keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01909',' REUSE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01910',' TABLES keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01911',' CONTENTS keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01912',' ROW keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01913',' EXCLUSIVE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01914',' invalid auditing option for sequence numbers',' AUDIT or NOAUDIT on a sequence number specifies an auditing option that is not legal for sequence numbers.',' The following options may not be used for sequence numbers and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, EXECUTE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01915',' invalid auditing option for views',' AUDIT or NOAUDIT on a view specifies an auditing option that is not legal for views.',' The following options may not be used for views and should be removed: ALTER, INDEX, REFERENCES, EXECUTE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01916',' keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected',' An expected keyword was not used for DATAFILE/TEMPFILE clause',' Use correct syntax.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01917',' user or role ''string'' does not exist',' There is not a user or role by that name.',' Re-specify the name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01918',' user ''string'' does not exist',' User does not exist in the system.',' Verify the user name is correct.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01919',' role ''string'' does not exist',' Role by that name does not exist.',' Verify you are using the correct role name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01920',' user name ''string'' conflicts with another user or role name',' There is already a user or role with that name.',' Specify a different user name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01921',' role name ''string'' conflicts with another user or role name',' There is already a user or role with that name.',' Specify a different role name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01922',' CASCADE must be specified to drop ''string''',' Cascade is required to remove this user from the system. The user own''s object which will need to be dropped.',' Specify cascade.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01923',' CASCADE aborted, objects locked by another user',' Cannot drop the user''s objects; someone has them locked.',' Use the lock monitor to determine who has the objects locked.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01924',' role ''string'' not granted or does not exist',' Set role can only be performed with roles granted directly to your account (for example, a sub-role cannot be enabled).',' Do not try to set the role.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01925',' maximum of string enabled roles exceeded',' The initialization parameter MAX_ENABLED_ROLES has been exceeded.',' Increase MAX_ENABLED_ROLES and warm start the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01926',' cannot GRANT to a role WITH GRANT OPTION',' Role cannot have a privilege with the grant option.',' Perform the grant without the grant option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01927',' cannot REVOKE privileges you did not grant',' You can only revoke privileges you granted.',' Do not revoke these privileges.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01928',' GRANT option not granted for all privileges',' In order to grant a privilege, you must first have the privilege with the grant option.',' Obtain the privilege with the grant option and try again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01929',' no privileges to GRANT',' "ALL" was specified but the user does not have any privileges with the grant option.',' Do not grant privileges on that object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01930',' auditing the object is not supported',' AUDIT or NOAUDIT was specified for an object that cannot be audited.',' Do not attempt to AUDIT the object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01931',' cannot grant string to a role',' UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER privilege cannot be granted to a role.',' Grant privilege directly to the user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01932',' ADMIN option not granted for role ''string''',' The operation requires the ADMIN option on the role.',' Obtain the grant option and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01933',' cannot create a stored object using privileges from a role',' An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles.',' Grant the privileges required to the user directly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01934',' circular role grant detected',' Roles cannot be granted circularly. Also, a role cannot be granted to itself.',' Do not perform the grant.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01935',' missing user or role name',' A user or role name was expected.',' Specify a user or role name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01936',' cannot specify owner when creating users or roles',' Users and roles do not have owners.',' Do not specify an owner.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01937',' missing or invalid role name',' A valid role name was expected.',' Specify a valid role name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01938',' IDENTIFIED BY must be specified for CREATE USER',' Cannot create a user without specifying a password or IDENTIFIED EXTERNALLY.',' Specify one of the password clauses.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01939',' only the ADMIN OPTION can be specified',' System privileges and Roles can only be granted with the ADMIN option. The grant option cannot be used with these privileges.',' Specify the ADMIN option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01940',' cannot drop a user that is currently connected',' Attempt was made to drop a user that is currently logged in.',' Make sure user is logged off, then repeat command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01941',' SEQUENCE keyword expected',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01942',' IDENTIFIED BY and EXTERNALLY cannot both be specified',' A user cannot be specified to have and not have a password.',' Specify only one of the options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01943',' IDENTIFIED BY already specified',' The IDENTIFIED clause has been given twice.',' Use only one IDENTIFIED BY clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01944',' IDENTIFIED EXTERNALLY already specified',' The IDENTIFIED EXTERNALLY clause has been given twice.',' Use only one IDENTIFIED clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01945',' DEFAULT ROLE[S] already specified',' The DEFAULT ROLES clause has been given twice.',' Use only one DEFAULT ROLE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01946',' DEFAULT TABLESPACE already specified',' The DEFAULT TABLESPACE clause has been given twice.',' Use only one DEFAULT TABLESPACE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01947',' TEMPORARY TABLESPACE already specified',' The TEMPORARY TABLESPACE clause has been given twice.',' Use only one TEMPORARY TABLESPACE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01948',' identifier''s name length (string) exceeds maximum (string)',' A name has been specified that is too long. For example, DBMS_SESSION.IS_ROLE_ENABLED() specifies that is too long.',' Change the application or command to use a correct identifier.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01949',' ROLE keyword expected',' The ROLE keyword is required here.',' Specify the ROLE keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01950',' no privileges on tablespace ''string''',' User does not have privileges to allocate an extent in the specified tablespace.',' Grant the user the appropriate system privileges or grant the user space resource on the tablespace.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01951',' ROLE ''string'' not granted to ''string''',' The role you tried to revoke was not granted to the user.',' Do not try to revoke a privilege which is not granted.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01952',' system privileges not granted to ''string''',' A system privilege you tried to revoke was not granted to the user.',' Make sure the privileges you are trying to revoke are granted.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01953',' command no longer valid, see ALTER USER',' The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality.',' Use the ALTER USER command instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01954',' DEFAULT ROLE clause not valid for CREATE USER',' Default roles cannot be specified for create user.',' Grant and alter the user''s default roles after creating the user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01955',' DEFAULT ROLE ''string'' not granted to user',' The user being altered does not have the specified role granted directly to the user. Note, sub-roles cannot be used in the DEFAULT ROLE clause.',' Grant the role to the user.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01956',' invalid command when OS_ROLES are being used',' This command cannot be used when the initialization parameter OS_ROLES is TRUE.',' Grant the role to the user in the operating system.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01957',' Keyword MIN or MAX expected, not found',' The keyword MIN or MAX was expected as an argument.',' Enter the keyword MIN or MAX and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01958',' Must supply an integer for the LAYER option',' An item other than an integer was entered for the LAYER option.',' Enter an integer for the LAYER option and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01959',' Must supply an integer for the OPCODE option',' An item other than an integer was entered for the OPCODE option. The value in ALTER SYSTEM DUMP ... OPCODE value must be an integer.',' Enter an integer for the OPCODE option and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01960',' Invalid dump logfile option',' An invalid option was entered for the ALTER SYSTEM DUMP LOGFILE option command.',' For a list of valid options for DUMP LOGFILE, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01961',' invalid dump option',' An invalid option was entered for the ALTER SYSTEM DUMP statement.',' Enter a valid option for ALTER SYSTEM DUMP. Examples of valid options are LOGFILE and UNDO. For more information on the DUMP option, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01962',' Must specify a file number or log sequence number',' An invalid file number or log sequence number was specified.',' Enter a valid file number or log sequence number and retry the operation. For more information on valid file and log sequence numbers, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01963',' Must specify a block number',' An invalid block number was specified.',' Enter a valid block number and retry the operation. For more information on valid block numbers, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01964',' Must specify a time for the TIME option',' A value was entered for the TIME option that could not be interpreted as a date.',' Enter a valid date. For more information on the TIME option, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01965',' Must specify a PERIOD',' A period is missing between the file number and the block number.',' Enter a period between the file number and the block number, then retry the operation. For more information on file numbers and block numbers, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01967',' invalid option for CREATE CONTROLFILE',' An invalid CREATE CONTROLFILE option is present.',' Specify only valid CREATE CONTROLFILE options.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01968',' Only specify RESETLOGS or NORESETLOGS once',' The keyword RESETLOGS or NORESETLOGS has appeared more than once.',' Be sure to specify RESETLOGS or NORESETLOGS exactly once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01969',' You must specify RESETLOGS or NORESETLOGS',' Missing a RESETLOGS or a NORESETLOGS.',' Be sure to specify RESETLOGS or NORESETLOGS exactly once.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01970',' You must specify a database name for CREATE CONTROLFILE',' Missing a database name.',' Retype CREATE CONTROLFILE command with the DATABASE keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01971',' Illegal ALTER TRACING option',' An invalid ALTER TRACING option is present.',' Specify only valid ALTER TRACING options. Examples of valid options are ENABLE and DISABLE. For more information, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01972',' Must specify a string for ALTER TRACING ENABLE or DISABLE',' Something other than a valid identifier was specified for ALTER TRACING ENABLE or DISABLE.',' Specify a valid identifier for ALTER TRACING ENABLE or DISABLE and retry the operation. For more information on valid identifiers, see the Oracle9i SQL Reference.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01973',' Missing change number',' Keyword CHANGE found but change number not specified.',' Fix the command line and resubmit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01974',' Illegal archive option',' An invalid option to the ALTER SYSTEM ARCHIVE command was specified.',' Check the syntax of the command and retry it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01975',' Illegal character in change number string',' An invalid change number was supplied.',' Resubmit the command with a valid change number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01976',' Missing change number',' A change number was required, but not supplied.',' Check the syntax of the command, supply a change number where needed, then retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01977',' Missing thread number',' Keyword THREAD found but thread number not specified.',' Fix the command line and resubmit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01978',' Missing sequence number',' Keyword SEQUENCE found but sequence number not specified.',' Fix the command line and resubmit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01979',' missing or invalid password for role ''string''',' An attempt was made to enable a role without giving the proper password.',' Use the IDENTIFIED BY clause in SET ROLE to specify the correct password.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01980',' error during OS ROLE initialization',' An operating system error occurred while loading a users OS ROLES.',' Check the operating system error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01981',' CASCADE CONSTRAINTS must be specified to perform this revoke',' During this revoke some foreign key constraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified.',' Remove the constraints or specify CASCADE CONSTRAINTS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01982',' invalid auditing option for tables',' AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables.',' The following options may not be used for tables and should be removed: REFERENCES, EXECUTE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01983',' invalid auditing option for DEFAULT',' AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT.',' The following options may not be used for DEFAULT and should be removed: REFERENCES.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01984',' invalid auditing option for procedures/packages/functions',' AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions.',' The following options may not be used for procedures, packages, and functions and should be removed: all but EXECUTE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01985',' cannot create user as LICENSE_MAX_USERS parameter exceeded',' Maximum users in the database license limit exceeded.',' Increase license limit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01986',' invalid option for OPTIMIZER_GOAL',' An invalid OPTIMIZER_GOAL option is present.',' Check the syntax for OPTIMIZER_GOAL, specify a valid option and re-execute the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01987',' client os username is too long',' A client''s operating system username is too long for the operating system logon to succeed.',' Use a shorter operating system username.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01988',' remote os logon is not allowed',' Remote operating system login attempted when not allowed.',' Use a local client, or use the REMOTE_OS_AUTHENT system parameter to turn on remote operating system logon.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01989',' role ''string'' not authorized by operating system',' The operating system role does not exist, is not granted to you, or you did not provide the correct password.',' Re-attempt the SET ROLE with a valid operating system role and password, if necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01990',' error opening password file ''string''',' An attempt to open the specified password file failed because of one of the following errors:',' Check for the above causes and correct as necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01991',' invalid password file ''string''',' The specified password file name is invalid.',' Specify a correct password file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01992',' error closing password file ''string''',' The password file could not be closed because of an operating system error or because an authentication action failed.',' Check for the above causes and correct as necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01993',' error writing password file ''string''',' The password file could not be written to because of an operating system error or because an authentication action failed.',' Check for the above causes and correct as necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01994',' GRANT failed: cannot add users to shared password file',' A grant failed because a user could not be added to the password file. This is because the value of the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED.',' To add a user to the password file, shut down the database, change the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE, and restart the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01995',' error reading password file ''string''',' An operating system error occurred when trying to read the password file.',' Fix the operating system error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01996',' GRANT failed: password file ''string'' is full',' The grant failed when a user could not be added to the password file, because all available slots in it were used already.',' Either create a larger password file or free up slots in the password file by revoking the SYSOPER and SYSDBA privileges from some of the remote users. You can determine which remote users are valid and their privileges by issuing the following query in SQL*DBA:');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01997',' GRANT failed: user ''string'' is identified externally',' You cannot grant the SYSOPER or SYSDBA privilege to a user created with the IDENTIFIED EXTERNALLY clause.',' If you wish to grant the user the SYSOPER or SYSDBA privileges, drop and re-create the user without the IDENTIFIED EXTERNALLY clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01998',' REVOKE failed: user SYS always has SYSOPER and SYSDBA',' You attempted to revoke one of the necessary privileges, SYSOPER or SYSDBA, from user SYS. These privileges cannot be revoked.',' Do not attempt this operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-01999',' password file mode has changed from ''string'' to ''string''',' Another instance has started with the FORCE_PASSWORD_FILEMODE initialization parameter, which is incompatible with the startup mode of your instance.',' Shut down your instance and start up later when the password file changes are completed for the other instance.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02000',' missing string keyword',' The statement entered requires the missing keyword.',' Use the specified keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02001',' user SYS is not permitted to create indexes with freelist groups',' An attempt was made to create an index while running with SYS authorization.',' Indexes cannot be created with SYS authorization. Either do not create the index or switch to USER authorization.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02002',' error while writing to audit trail',' The auditing facility is unable to write to the AUDIT_TRAIL table. If this error occurs, SQL statements that are currently being audited may also fail. This error will occur if the SYSTEM tablespace runs out of disk space.',' Add space to the SYSTEM tablespace or delete rows from the AUDIT_TRAIL table. If these operations fail or do not eliminate the problem, shut down and restart Oracle with auditing disabled. This is done by setting the initialization parameter AUDIT_TRAIL to FALSE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02003',' invalid USERENV parameter',' An invalid parameter was specified for the USERENV function.',' Specify one of the allowable parameters TERMINAL, SESSIONID, ENTRYID, or NLS_LANG.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02004',' security violation',' A user is attempting to perform an operation without the proper permission, and this fact is being recorded in the AUDIT_TRAIL table. This message only appears in the AUDIT_TRAIL table''s return code column.',' For auditing information only; no action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02005',' implicit (-1) length not valid for this bind or define datatype',' A negative length for the define variable was passed to a define function.',' An explicit, non-negative, length parameter must be passed.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02006',' invalid packed decimal format string',' A packed decimal datatype was passed to a bind or define function, and the format string parameter was either not present or invalid.',' A valid format string parameter must be passed for a packed decimal variable. Check the programming manual for the definition of a packed decimal format string.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02007',' can''t use ALLOCATE or DEALLOCATE options with REBUILD',' Allocate or deallocate storage and rebuild index are not compatible.',' Choose one or the other.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02008',' non-zero scale specified for nonnumeric column',' A scale factor was specified for a bind or define of a non-numeric variable.',' Set the scale factor to zero, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02009',' the size specified for a file must not be zero',' A value of zero was specified in a SIZE or RESIZE clause of a file specification.',' Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02010',' missing host connect string',' A quoted character string does not follow the keyword USING in the USING clause of a CREATE DATABASE LINK statement.',' Specify the host connect string, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02011',' duplicate database link name',' The database link name specified in a CREATE DATABASE LINK statement already exists.',' Either specify a new name or drop the existing link.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02012',' missing USING keyword',' The keyword USING does not follow the CONNECT TO clause in a CREATE DATABASE LINK statement.',' Specify the USING clause after the CONNECT TO clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02013',' missing CONNECT keyword',' The keyword CONNECT does not follow the database link name in a CREATE DATABASE LINK statement.',' Specify the CONNECT clause after the database link name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02014',' cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.',' An attempt was made to SELECT... FOR UPDATE from a view whose defining SELECT statement uses at least one of the following constructs in its outer block: outer join, GROUP BY clause, aggregate functions, SELECT DISTINCT, CONNECT BY clause, or set operation, UNION, INTERSECT, or MINUS.',' Do not use SELECT... FOR UPDATE on this view.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02015',' cannot select FOR UPDATE from remote table',' An attempt was made to SELECT... FOR UPDATE from a table in a remote database.',' It is not currently possible to SELECT... FOR UPDATE from a table in a remote database. Instead, log in or connect directly to the remote database before entering a SELECT... FOR UPDATE on its tables.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02016',' cannot use a subquery in a START WITH on a remote database',' An attempt was made to use a subquery in a START WITH clause. Such a subquery is not currently permitted if the table in the FROM clause of the tree query is in a remote database.',' It is necessary to connect directly to the remote database before using a subquery in the START WITH clause.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02017',': integer value required',' The specified value must be an integer.',' Specify an appropriate integer value, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02018',' database link of same name has an open connection',' The user is currently connected to a PUBLIC database link with the same name as the database link name specified in a CREATE or DROP DATABASE LINK statement.',' Close the cursors that use the PUBLIC database link.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02019',' connection description for remote database not found',' An attempt was made to connect or log in to a remote database using a connection description that could not be found.',' Specify an existing database link. Query the data dictionary to see all existing database links. See your operating system-specific Net8 documentation for valid connection descriptors.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02020',' too many database links in use',' The current session has exceeded the INIT.ORA OPEN_LINKS maximum.',' Increase the OPEN_LINKS limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02021',' DDL operations are not allowed on a remote database',' An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname...".',' To alter the remote database structure, you must connect to the remote database with the appropriate privileges.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02022',' remote statement has unoptimized view with remote object',' The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database.',' Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02023',' START WITH or CONNECT BY predicate cannot be evaluated by remote data base',' The statement contains a tree query on a remote database, and the tree query''s START WITH or CONNECT BY predicate contains a term that cannot be evaluated at the remote database. Such terms include calls to user functions, calls to USERENV, and references to ROWID.',' Remove the disallowed term, directly connect, or log on to the remote database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02024',' database link not found',' Database link to be dropped is not found in dictionary.',' Correct the database link name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02025',' all tables in the SQL statement must be at the remote database',' A SQL statement referenced tables from multiple databases, and one or more of the remote databases are not Oracle Servers.',' Remote updates can be performed only if all databases in the SQL statement are Oracle Servers. Update the earlier version databases in a separate statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02026',' missing LINK keyword',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02027',' multi-row UPDATE of LONG column is not supported',' A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row.',' You may only update a single row with such a bind variable.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02028',' fetching an exact number of rows is not supported by the server',' The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.',' Connect to a valid server or do not use an exact fetch.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02029',' missing FILE keyword',' A keyword is missing.',' Supply the missing keyword.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02030',' can only select from fixed tables/views',' An attempt is being made to perform an operation other than a retrieval from a fixed table/view.',' You may only select rows from fixed tables/views.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02031',' no ROWID for fixed tables or for external-organized tables',' An attempt was made to access rowid from a fixed table or from an external-organized table.',' Do not access ROWID from a fixed table or from an external-organized table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02032',' clustered tables cannot be used before the cluster index is built',' User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created.',' Create the cluster index.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02033',' a cluster index for this cluster already exists',' A cluster index already exists for the cluster.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02034',' speed bind not permitted',' Speed bind not allowed with supplied bind variables. Trapped internally by the system.',' No action required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02035',' illegal bundled operation combination',' User requested that the UPI bundled execution call perform an illegal combination of operations.',' Use a legal combination of operations and retry.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02036',' too many variables to describe with automatic cursor open',' UPI-bundled execution call tried to perform automatic cursor open and close on a describe operation. There were too many SELECT list items or bind variables to do this.',' Open and close cursor explicitly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02037',' uninitialized speed bind storage',' An attempt was made to perform a speed-execution call on a SQL statement containing host variables without first performing a speed-bind call.',' Perform a speed-bind call before performing a speed-execution call.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02038',' define is not allowed for array type',' A user attempted to define a select list variable of type "array". Arrays may serve only as host bind variables.',' Correct the offending code.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02039',' bind by value is not allowed for array type',' User attempted to bind an array host variable by value. Arrays may be bound only by reference.',' Correct the offending code.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02040',' remote database string does not support two-phase commit',' A distributed update of more than one database was attempted, but the named database does not support the prepare phase of the two-phase commit, as determined by its logon transaction traits. The transaction was rolled back.',' Do not attempt to update the named database, unless it is the only database updated in the transaction. Distributed updates of more than one database in a single transaction can be performed only if all databases support the two-phase commit mechanism.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02041',' client database did not begin a transaction',' An update occurred at a coordinated database without the coordinator beginning a distributed transaction. This may happen if a stored procedure commits and then performs updates, and the stored procedure is invoked remotely. It could also happen if an external transaction monitor violates the XA protocol.',' If the cause is the former, check that any commit is not followed by an update.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02042',' too many distributed transactions',' The distributed transaction table is full because too many distributed transactions are active.',' Increase the DISTRIBUTED_TRANSACTIONS parameter in the initialization parameter file, shut down and restart Oracle, or run fewer transactions. If it is certain there are not too many concurrent distributed transactions, this may be an internal error. In this case, contact Oracle Support Services. Shutting down and restarting the instance could be a workaround.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02043',' must end current transaction before executing string',' A transaction was in progress and one of the following commands was issued:',' COMMIT or ROLLBACK the current transaction and retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02044',' transaction manager login denied: transaction in progress',' A remote transaction manager tried to log in while a distributed transaction is in progress. A protocol error occurred in the remote transaction manager.',' End the current transaction.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02045',' too many local sessions participating in global transaction',' There are too many sessions at this site to accommodate this transaction.',' Use an existing database link so that another session need not be created at the remote site.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02046',' distributed transaction already begun',' This is an internal error not normally encountered. A server session received a BEGIN_TRAN remote procedure call before finishing with a previous distributed transaction.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02047',' cannot join the distributed transaction in progress',' This can happen only when attempting to update an Oracle Version 6 and an Oracle7 database in the same transaction, because either',' Complete the current transaction before attempting the action that caused the error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02048',' attempt to begin distributed transaction without logging on',' The client program did not issue a distributed transaction login. This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02049',' timeout: distributed transaction waiting for lock',' Exceeded INIT.ORA DISTRIBUTED_LOCK_TIMEOUT seconds waiting for lock.',' Treat as a deadlock.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02050',' transaction string rolled back, some remote DBs may be in-doubt',' Network or remote failure during a two-phase commit.',' Notify operations; remote databases will automatically re-sync when the failure is repaired.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02051',' another session in same transaction failed',' A session at the same site with same global transaction ID failed.',' No action necessary; the transaction is automatically recovered.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02052',' remote transaction failure at string',' There was some error in a remote transaction at the named database link.',' More descriptive messages will follow. Correct the problem specified in the following messages and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02053',' transaction string committed, some remote DBs may be in-doubt',' There was a network failure or a remote failure during the two-phase commit.',' Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02054',' transaction string in-doubt',' There was a network failure or a remote failure in the two-phase commit.',' Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired. Monitor the DBA_2PC_PENDING table for the outcome and resubmit the transaction, if necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02055',' distributed update operation failed; rollback required',' A failure during a distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent with others, the transaction must roll back to a savepoint or roll back entirely.',' Roll back to a savepoint or roll back the entire transaction and resubmit the rolled-back statements.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02056',' 2PC: string: bad two-phase command number string from string',' There was a two-phase commit protocol error.',' The transaction may automatically recover. Monitor the DBA_2PC_PENDING table to determine the resolution. Enter the transaction again, if necessary. Contact Oracle Support Services if necessary.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02057',' 2PC: string: bad two-phase recovery state number string from string',' An internal error in the two-phase recovery protocol occurred.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02058',' no prepared transaction found with ID string',' No transaction with LOCAL_TRAN_ID or GLOBAL_TRAN_ID found in the PENDING_TRANS$ table in prepared state.',' Check the PENDING_TRANS$ table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02059',' ORA-2PC-CRASH-TEST-string in commit comment',' This is a special comment used to test the two-phase commit.',' Do not use this special comment (string a number 1-10).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02060',' select for update specified a join of distributed tables',' An attempt was made to join tables in different remote databases in a SELECT... FOR UPDATE statement.',' Joined tables in a SELECT statement with the FOR UPDATE clause must reside at the same database. Simplify the SELECT... FOR UPDATE statement so that it joins only tables in the same database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02061',' lock table specified list of distributed tables',' Tables in a LOCK TABLE statement must reside at the same database.',' Issue multiple LOCK TABLE commands.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02062',' distributed recovery received DBID string, expected string',' A database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different database mounted.',' Restore the link definition or the remote database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02063',' preceding stringstring from stringstring',' An Oracle error was received from a remote database link.',' Refer to the preceding error message(s).');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02064',' distributed operation not supported',' One of the following unsupported operations was attempted:',' Simplify the remote update statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02065',' illegal option for ALTER SYSTEM',' The option specified for ALTER SYSTEM is not supported.',' Refer to the Oracle9i SQL Reference for information about options supported.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02066',' missing or invalid DISPATCHERS text',' A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS.',' Place the string literal containing the dispatcher''s specification after ALTER SYSTEM SET DISPATCHERS.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02067',' transaction or savepoint rollback required',' A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.',' Roll back to a previous savepoint or roll back the transaction and resubmit.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02068',' following severe error from stringstring',' A severe error (disconnect, fatal Oracle error) was received from the indicated database link. See following error text.',' Contact the remote system administrator.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02069',' global_names parameter must be set to TRUE for this operation',' A remote mapping of the statement is required but cannot be achieved because GLOBAL_NAMES should be set to TRUE for it to be achieved.',' Issue ALTER SESSION SET GLOBAL_NAMES = TRUE if possible.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02070',' database stringstring does not support string in this context',' The remote database does not support the named capability in the context in which it is used.',' Simplify the SQL statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02071',' error initializing capabilities for remote database string',' Could not load a remote-specified capability table.',' Contact Oracle Support Services for the remote SQL*Connect product.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02072',' distributed database network protocol mismatch',' This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.',' Upgrade the older release.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02073',' sequence numbers not supported in remote updates',' Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.',' Perform the operation without specifying a sequence number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02074',' cannot string in a distributed transaction',' A commit or rollback was attempted from session other than the parent of a distributed transaction.',' Only commit or roll back from the parent session.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02075',' another instance changed state of transaction string',' A commit force or rollback force was issued from a session in another instance.',' Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02076',' sequence not co-located with updated table or long column',' All referenced sequences must be located on the same node as the updated table or the long column.',' Correct the problem and then reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02077',' selects of long columns must be from co-located tables',' All tables returning values of long columns in a SELECT statement must be located at the same node.',' Correct the problem, then reissue the statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02078',' invalid setting for ALTER SYSTEM FIXED_DATE',' An invalid value was used.',' Use a correct value.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02079',' no new sessions may join a committing distributed transaction',' A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch; that is, a call to UPI2EN was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02080',' database link is in use',' A transaction is active or a cursor is open on the database link given in the ALTER SESSION CLOSE DATABASE LINK link command.',' Commit or roll back, and close all cursors');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02081',' database link is not open',' An attempt was made to use a database link that is not currently open.',' Resolve network problems or contact the remote database administrator to determine if the remote database''s problem has been fixed. Contact the local database administrator to determine if network problems have been resolved. Wait until the link is open and try the operation again.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02082',' a loopback database link must have a connection qualifier',' An attempt was made to create a database link with the same name as the current database.',' This database link needs a trailing qualifier to make the name unique. These qualifiers are operating system-specific. See your operating system-specific Oracle documentation for more information about creating database links.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02083',' database name has illegal character ''string''',' The database name supplied contains an invalid character. For example, there can be no periods, semicolons, single quotes, double quotes, blanks, or non-printable characters in the database name. See the Oracle9i Database Administrator''s Guide for naming rules.',' Specify a valid database name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02084',' database name is missing a component',' The complete database name was not provided.',' Specify the full database name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02085',' database link string connects to string',' The database link attempted to connect to a database with a different name. The name of the database link must be the same name as the name of the database.',' Create a database link with the same name as the database to which it connects.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02086',' database (link) name is too long',' The name of the database or database link is too long. Database and database link names can be no longer than 128 characters.',' Specify the correct database or database link name or specify a name with fewer characters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02087',' object locked by another process in same transaction',' A database link is being used in the cluster database environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session.',' Get the more restrictive lock first. For example, if session 1 gets a share lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or use the same session to access the object.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02088',' distributed database option not installed',' The distributed database option is not installed at this site, so the requested operation is not possible.',' Contact Oracle Support Services about obtaining the distributed database option.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02089',' COMMIT is not allowed in a subordinate session',' COMMIT was issued in a session that is not the two-phase commit global coordinator.',' Issue commit at the global coordinator only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02090',' network error: attempted callback+passthru',' This is an internal error.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02091',' transaction rolled back',' The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back.',' Complete the current transaction and then do the operation required.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02092',' out of transaction table slots for distributed transaction',' The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back.',' Add a rollback segment and retry the transaction.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02093',' TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)',' Value of the parameter specified is greater than allowed on this port.',' Use default or reduce it to less than the maximum.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02094',' replication option not installed',' The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable.',' Install the replication option. The replication option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02095',' specified initialization parameter cannot be modified',' Specified initialization parameter is not modifiable with this option.',' Check the Oracle9i Database Administrator''s Guide for information about under what scope the parameter may be modified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02096',' specified initialization parameter is not modifiable with this option',' Though the initialization parameter is modifiable, it cannot be modified using the specified command.',' Check the Oracle9i Database Administrator''s Guide for information about under what scope the parameter may be modified');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02097',' parameter cannot be modified because specified value is invalid',' Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter.',' Check the Oracle9i Database Administrator''s Guide for range of acceptable values for this parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-02098',' error parsing index-table reference (:I)',' An incorrect index-table (:I) syntax was encountered.',' This syntax is for Oracle internal use only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19400',' System type conflict with object SYS.string',' The user had an object with the same name as one of the system types. The system types were not initialized properly.',' Remove the conflicting object and re-run migration.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19500',' device block size string is invalid',' The device block size returned by sequential I/O OSD is invalid.',' If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19501',' read error on file "string", blockno string (blocksize=string)',' Read error on input file.',' Check the file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19502',' write error on file "string", blockno string (blocksize=string)',' Write error on output file.',' Check the file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19503',' cannot obtain information on device, name="string", type="string", parms="string"',' Call to get device information returned an error.',' Check device name, type, and parameters.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19504',' failed to create file "string"',' Call to create file returned an error.',' Check additional messages and check access permissions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19505',' failed to identify file "string"',' Call to identify the file returned an error.',' Check additional messages, and check whether the file exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19506',' failed to create sequential file, name="string", parms="string"',' Call to create the sequential file returned an error.',' Check additional messages, check access permissions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19507',' failed to retrieve sequential file, handle="string", parms="string"',' Call to retrieve the sequential file returned an error.',' Check additional messages, and check if the file exists.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19508',' failed to delete file "string"',' Call to delete the file returned an error.',' Check additional messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19509',' failed to delete sequential file, handle="string", parms="string"',' Call to delete the sequential file returned an error.',' Check additional messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19510',' failed to set size of string blocks for file "string" (blocksize=string)',' Call to resize the file returned an error.',' Check additional messages.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19511',' Error received from media manager layer, error text: string',' An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager.',' If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19550',' cannot use backup/restore functions while using dispatcher',' An attempt was made to use backup/restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.',' Connect directly to the instance then re-execute the backup or restore function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19551',' device is busy, device type: string, device name: string',' The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.',' Either attempt to allocate another device or wait until the required device is no longer busy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19552',' device type string is invalid',' The device type indicated is invalid.',' Supply a correct device type and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19553',' device name string is invalid',' The device name indicated is invalid.',' Supply a correct device name and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19554',' error allocating device, device type: string, device name: string',' The specified device could not be allocated.',' One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19555',' invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value',' The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.',' Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19556',' required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred',' The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination.',' Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19557',' device error, device type: string, device name: string',' An error occurred in the platform-specific device code.',' One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19558',' error de-allocating device',' The specified device could not be de-allocated.',' One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19559',' error sending device command: string',' An error occurred while sending the indicated command to the session device.',' One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19560',' string is not a valid device limit',' An invalid type of device limit was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT.',' Use one of the documented limits: KBYTES, READRATE, or PARALLEL.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19561',' string requires a DISK channel',' The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.',' Deallocate the current device and allocate a DISK channel, then retry the command.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19562',' file string is empty',' The indicated file, which is an archive log, control file, or datafile was found to be empty during a copy, backup, or scan] operation.',' Ensure that the correct files are being specified for the copy or backup operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19563',' string header validation failed for file string',' When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, the header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file), belonging to the current database.',' Ensure that the correct files are being specified for the copy or backup operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19564',' error occurred writing string bytes at block number string',' An error occurred while writing to a file.',' One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19565',' BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices',' An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.',' Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19566',' exceeded limit of string corrupt blocks for file string',' The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.',' No action required. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19567',' cannot shrink file string because it is being backed up or copied',' An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.',' Retry the resize after the backup or copy is complete.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19568',' a device is already allocated to this session',' A device cannot be allocated to a session if another device is already allocated.',' Deallocate the current device.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19569',' no device is allocated to this session',' An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.',' Allocate a device then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19570',' file number string is outside valid range of 1 through string',' A file number used in a copy, backup, or restore operation is not valid for the current database.',' Specify a valid file number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19571',' string recid string stamp string not found in controlfile',' The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file.',' Specify a correct RECID/stamp and retry the copy or backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19572',' cannot process file string, file is being being resized',' The input file specified for a copy or backup operation could not be opened because the file is being resized.',' Wait for the resize to complete then retry the copy or backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19573',' cannot obtain string enqueue for datafile string',' The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation. If the enqueue type shown is SHARED, then the file is the input file for a backup or copy. If the type is EXCLUSIVE, then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed. If the type is read-only, then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode.',' Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19574',' output filename must be specified',' This type of copy or restore requires an output file name.',' Specify an output file name and retry the copy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19575',' expected string blocks in file string, found string',' During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header.',' The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19576',' datafile string not defined in control file',' The specified file number was not found in the control file.',' Specify a correct file number and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19577',' file string is MISSING',' A copyDataFileCopy, restoreDataFileTo or proxyRestoreDataFile function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration.',' Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19578',' end of volume while duplexing to sequential files, backup piece incomplete',' An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.',' Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19579',' archivelog record for string not found',' No archived log record corresponding to the input file could be found in the control file.',' Specify a valid archive log file name and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19580',' string conversation not active',' A backup or restore operation was attempted before a conversation was started.',' Start a conversation then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19581',' no files have been named',' An attempt was made to proceed from the file naming phase to the piece processing phase of a backup or restore conversation before any files have been specified for backup or restore.',' Specify some files then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19582',' archivelog file header validation for string failed',' The archived log file header is corrupt and could not be validated.',' Provide a valid archive log file and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19583',' conversation terminated due to error',' An error occurred which forced the termination of the current backup or restore conversation.',' There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19584',' file string already in use',' The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database.',' Specify a different name and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19585',' premature end of volume on piece string',' While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set.',' Retry the piece with a larger piece of output media.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19586',' string k-byte limit is too small to hold piece directory',' The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.',' Use the setLimit procedure to increase the k-byte limit and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19587',' error occurred reading string bytes at block number string',' An error occurred while reading from a file.',' One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19588',' string recid string stamp string is no longer valid',' The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was ''consumed'' by a switchToCopy operation.',' If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19589',' string is not a snapshot or backup controlfile',' The control file that is the source for a backup or copy operation is not a snapshot or backup control file.',' Specify the name of a snapshot or backup control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19590',' conversation already active',' An attempt was made to begin a backup or restore conversation, but another conversation is already active in this session.',' Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19592',' wrong string conversation type',' An attempt was made to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation.',' No action required. The conversation is still active, and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19593',' datafile number string already included as string',' This datafile is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of a datafile.',' No action required. The conversation is still active, and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19594',' controlfile already included as string',' The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.',' No action required. The conversation is still active, and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19595',' archivelog string already included in backup conversation',' The indicated archive log has already been specified for inclusion in this backup conversation.',' No action required. The conversation is still active, and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19596',' SPFILE already included',' The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.',' No action required. The conversation is still active, and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19597',' file string blocksize string does not match set blocksize of string',' A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.',' Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19598',' can not backup SPFILE because the instance was not started with SPFILE',' A backup command requested a backup of the SPFILE, but no SPFILE was used to start up the instance.',' Create an SPFILE and restart the instance using the SPFILE.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19599',' block number string is corrupt in string string',' A corrupt block was found in a controlfile, archivelog, or backup piece that is being read for a backup or copy. Corruption is not tolerated in controlfiles, archivelogs, or backup pieces.',' No action required. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19600',' input file is string string (string)',' This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown.',' Other messages should display to help pinpoint the cause and the solution.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19601',' output file is string string (string)',' This message identifies the output file for a failed copy operation. The fields are as described in message 19600. When creating a new datafile copy, its control file record number may not have been determined when the message is printed. In that case, the record number shown is zero.',' See other error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19602',' cannot backup or copy active file in NOARCHIVELOG mode',' An attempt was made to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.',' Take the tablespace offline clean or close the database and retry the copy or backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19603',' cannot backup or copy active file with KEEP .. UNRECOVERABLE option',' The user tried to copy or backup a file that was not closed cleanly, with the KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the file will require redo application before it is usable, and redo will not be saved because of the KEEP .. UNRECOVERABLE option.',' Take the tablespace offline cleanly, or close the database and retry the copy or backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19604',' conversation file naming phase is over',' A call was made to specify a file to be backed up or restored after the first backup piece has been processed.',' You cannot specify more files to be processed during a backup or restore conversation after the first backup piece has been processed. If more files must be specified, you must begin a new conversation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19605',' input filename must be specified',' The input file name was not specified for a control file copy operation.',' Specify an input file name and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19606',' Cannot copy or restore to snapshot controlfile',' A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file.',' Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19607',' string is an active controlfile',' A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file.',' Specify a different file name and retry the operation. If this is a backup or restore conversation, then the conversation remains active and more files may be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19608',' string is not a backup piece',' The specified file is not a backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is corrupt or this file is not a backup piece.',' Specify a different file name and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19609',' string is from different backup set: stamp string count string',' The specified file is not from the backup set which is currently being processed. It is part of a different backup set. The identification of the set containing this piece is shown.',' Specify the correct backup piece and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19610',' directory block string is corrupt',' The indicated directory block failed checksum validation. This backup piece is unusable.',' Supply another copy of the same backup piece, or terminate the restore conversation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19611',' backup piece out of order. Expected string but found string',' This backup piece is out of sequence.',' Supply the correct backup piece.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19612',' datafile string not restored due to string',' The indicated file could not be restored, because all of its data blocks were not found in the backup piece.',' The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19613',' datafile string not found in backup set',' The indicated file could not be restored, because it is not in this backup set. If the file number is zero, then this refers to the control file.',' This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19614',' archivelog thread string sequence string not found in backup set',' The indicated archived log file was named explicitly for restoration but is not contained in this backup set.',' This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19615',' some files not found in backup set',' Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each file that was not found.',' See the instructions for message 19613.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19616',' output filename must be specified if database not mounted',' A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file.',' The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name must be specified on all datafile restoration calls.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19617',' file string contains different resetlogs data',' The indicated file contains resetlogs data which is different from the archived log files which are already included in the backup set. All archived log files in a backup set must have the same resetlogs data.',' The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19618',' cannot name files after restoreValidate has been called',' A call was made to specify a file to restore from a backup set, but a previous call to restoreValidate has already been made.',' You must cancel and restart the conversation if you wish to specify files to restore.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19619',' cannot call restoreValidate after files have been named',' restoreValidate was called after some files had already been specified for restoration.',' You must cancel and restart the conversation if you wish to call restoreValidate.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19621',' archivelog range has already been specified',' A range of logs has already been specified. Only one SCN range may be specified per conversation.',' The restore conversation remains active and more logs may be specified by thread and sequence number, if desired.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19622',' archivelog thread string sequence string not restored due to string',' The indicated file could not be restored, because all of its data blocks were not found in the backup piece.',' The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19623',' file string is open',' A SwitchToCopy operation specified a datafile copy whose parent datafile is open.',' Take the owning tablespace offline or close the database, then retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19624',' operation failed, retry possible',' A backup, restore or image copy operation failed with an I/O error. If the source of the I/O error can be corrected, then the operation may be retried.',' This message is used by Recovery Manager to decide whether or not to retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19625',' error identifying file string',' A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An operating system-specific error accompanies this error to help pinpoint the problem.',' Specify an different file and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19626',' backup set type is string - can not be processed by this conversation',' The data in the backup set is not compatible with the current conversation.',' Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19627',' cannot read backup pieces during controlfile application',' This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation.',' The conversation is still active and more control files may be applied.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19628',' invalid SCN range',' The starting SCN for restoreRedoLogRange is greater than the ending SCN.',' Specify a starting SCN which is less than or equal to the ending SCN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19629',' no files in specified archivelog SCN range',' This backup set contains no files in the specified range.',' Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19630',' end of volume encountered while copying backup piece',' While copying a backup piece from the operating system native file system to an output device, the output device encountered end-of-volume.',' The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19631',' archivelog record contains no file name',' This archive log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost.',' Specify the RECID of an archive log record that contains a file name. Fixed view V$ARCHIVED_LOG can be used to examine the archived logs.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19632',' file name not found in controlfile',' The name passed to getFno was not found in the control file.',' Supply a valid file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19633',' controlfile record string is out of sync with recovery catalog',' The control file record describing the file to be deleted in a call to deleteBackupPiece, deleteDataFilecopy, proxyDelete or deleteArchivedLog does not match the validation data supplied by Recovery Manager.',' Contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19634',' filename required for this function',' The FNAME or handle parameter was not specified for deletePiece, deleteDataFileCopy, deleteRedoLog or proxyDelete.',' Specify the FNAME or handle parameter when calling these functions.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19635',' input and output filenames are identical',' Identical input and output file names were specified for a datafile copy operation.',' Specify an output file name which is different from the input file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19636',' archivelog thread string sequence string already included',' The indicated archive log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archive log.',' No action required. The conversation is still active, and more files can be specified.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19637',' backupPieceCreate requires file name when using DISK device',' The session device is currently allocated to disk, and so a file name is required.',' Supply a file name and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19638',' file string is not current enough to apply this incremental backup',' The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost.',' Supply a backup set that can be applied and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19639',' file string is more current than this incremental backup',' The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it.',' Supply a backup set that can be applied and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19640',' datafile checkpoint is SCN string time string',' This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied.',' See other error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19641',' backup datafile checkpoint is SCN string time string',' This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.',' See other error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19642',' incremental-start SCN is string',' This message identifies the starting SCN of an incremental backup that could not be applied.',' See other error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19643',' datafile string: incremental-start SCN is too recent',' The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed.',' Specify a smaller incremental-start SCN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19644',' datafile string: incremental-start SCN is prior to resetlogs SCN string',' The incremental-start SCN which was specified when starting an incremental datafile backup is less than the resetlogs SCN.',' Specify a larger incremental-start SCN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19645',' datafile string: incremental-start SCN is prior to creation SCN string',' The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile''s creation SCN.',' Specify a larger incremental-start SCN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19646',' cannot change size of datafile string from string to string',' The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size.',' Examine the other messages which should be present to indicate the cause of the failure.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19647',' non-zero LEVEL cannot be specified when INCREMENTAL is FALSE',' BackupSetDataFile was called with a non-zero BACKUP_LEVEL and a FALSE incremental indication.',' Either set incremental to TRUE or change BACKUP_LEVEL to zero.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19648',' datafile string: incremental-start SCN equals checkpoint SCN',' The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile''s checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to.',' Specify a smaller incremental-start SCN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19649',' offline-range record recid string stamp string not found in file string',' applyOfflineRange was called with a RECID/stamp which was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is.',' Specify the RECID/stamp of a record that exists in the control file copy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19650',' Offline-range record recid string stamp string in file string has SCN string',' This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.',' See other error message.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19651',' cannot apply offline-range record to datafile string: SCN mismatch',' applyOfflineRange cannot apply an offline-range record to a target datafile unless the datafile''s checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record.',' Specify an offline-range record whose offline-clean SCN matches the target datafile''s checkpoint.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19652',' cannot apply offline-range record to datafile string: file is fuzzy',' The target datafile for an applyOfflineRange call is fuzzy.',' Specify a target datafile that is closed cleanly.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19653',' cannot switch to older file incarnation',' SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up.',' Restore and mount an earlier control file. It is acceptable to use a control file that was backed up prior to the creation of the specified datafile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19654',' must use backup controlfile to switch file incarnations',' This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file.',' Restore and mount a backup control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19655',' cannot switch to incarnation with different resetlogs data',' This switchToCopy operation is attempting to switch to a datafile which comes from a different resetlogs version of the database.',' Either restore a backup control file that was taken from the same database version as the target datafile-copy, or switch to a different datafile-copy.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19656',' cannot backup, copy, or delete online log string',' The indicated log file is an active log. You can only backup, copy, or delete archived logs.',' The indicated log file cannot be processed. Select another file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19657',' cannot inspect current datafile string',' The file being inspected is already part of the currently mounted database.',' No action required. The file is already part of the database.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19658',' cannot inspect string - file is from different resetlogs',' The resetlogs data in the log file being inspected does not match that in the currently mounted control file.',' The indicated file cannot be processed; inspect another file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19659',' incremental restore would advance file string past resetlogs',' This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database.',' This incremental cannot be applied to this datafile. If you wish to recover the file to the resetlogs SCN so that the database can be opened with the RESETLOGS option, then you must use redo-log recovery, not incremental restore, to continue recovering this file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19660',' some files in the backup set could not be verified',' A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set.',' Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19661',' datafile string could not be verified',' Some data blocks for the indicated datafile were corrupt in the backup set.',' Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19662',' archived log thread string sequence string could not be verified',' Some data blocks for the indicated archived log were corrupt in the backup set.',' Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19663',' cannot apply current offline range to datafile string',' An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range.',' The datafile remains unchanged.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19664',' file type: string, file name: string',' This message is issued to identify the file which is the subject of an error.',' No action required. This is an informational message. There should be other Oracle messages explaining the cause of the error.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19665',' size string in file header does not match actual file size of string',' The size of the file as indicated in the file header does not match the true size of the file. The two differing sizes are shown in units of logical blocks.',' This file is not usable; it has most likely been truncated.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19666',' cannot do incremental restore of the controlfile',' The control file was included in an incremental restore conversation',' If you wish to restore the control file, you must do a full restore of the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19667',' cannot do incremental restore of datafile string',' The backup of the datafile is a full backup.',' If you wish to restore the datafile, you must do a full restore of the datafile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19668',' cannot do full restore of datafile string',' The backup of the datafile is an incremental backup.',' If you wish to restore the datafile, you must do an incremental restore of the datafile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19669',' proxy copy functions cannot be run on DISK channel',' A proxy copy procedure was called, but the device which is allocated to the current session has type DISK.',' Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a third-party media management software product that supports the this backup/restore feature.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19670',' file string already being restored',' A proxy restore function has already named this file as a restore destination.',' Use a different file name. If this message occurs during a Recovery Manager job, then this is an internal error in Recovery Manager, and you should contact Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19671',' media management software returned invalid proxy handle',' During a proxy backup or restore, the media management software returned an invalid file handle. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services.',' Contact the media management software vendor.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19672',' media management software returned invalid file status',' During a proxy backup or restore, the media management software returned an invalid file status. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services.',' Contact the media management software vendor.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19673',' error during proxy copy of file string',' During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully.',' There should be other errors on the error stack which explain why the file could not be successfully copied.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19674',' file string is already being backed up with proxy copy',' Recovery Manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another Recovery Manager job.',' Wait until the other Recovery Manager backup of this file is complete, then retry the backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19675',' file string was modified during proxy copy',' A proxy backup of the specified file failed because the file was brought online or otherwise modified while the proxy backup was in progress. This file was offline or read only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress.',' Take another backup of this file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19676',' one or more files failed during proxy backup or restore',' During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully.',' Examine the messages regarding the specific files to determine the cause of the problems.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19677',' RMAN configuration name exceeds maximum length of string',' The configuration name string exceeds the maximum length.',' Supply a correct configuration name and retry the function.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19678',' RMAN configuration value exceeds maximum length of string',' The configuration value string exceeds the maximum length.',' Supply a correct configuration value and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19679',' RMAN configuration number string is outside valid range of 1 through string',' An invalid RMAN Configuration number was specified.',' Specify a correct datafile number and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19680',' some blocks not recovered. See trace file for details',' Some blocks were not recovered during block media recovery.',' See trace files for details of the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19681',' block media recovery on control file not possible',' File number 0 was specified in block media recovery.',' Check file number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19683',' real and backup blocksize of file string are unequal',' The block size changed between the backup &amp; the real file.',' Use the correct backup.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19684',' block media recovery failed because database is suspended',' Database is suspended, probably by an ALTER SYSTEM SUSPEND statement.',' Execute ALTER SYSTEM RESUME then retry block media recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19690',' backup piece release string incompatible with Oracle release string',' The backup piece was created by incompatible software.',' Either restart with a compatible software release or create another backup using the current release.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19700',' device type exceeds maximum length of string',' The device type indicated is invalid.',' Supply a correct device type and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19701',' device name exceeds maximum length of string',' The device name indicated is invalid.',' Supply a correct device name and retry the allocation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19702',' device parameter exceeds maximum length of string',' The device parameter exceeds the port-specific maximum length.',' Correct the parameter and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19703',' device command string exceeds maximum length of string',' The device command string exceeds maximum length.',' Correct the command and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19704',' file name exceeds maximum length of string',' The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system.',' Retry the operation with a shorter file name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19705',' tag value exceeds maximum length of string characters',' During a backup or copy operation, the user supplied a tag value too long to fit in the file header.',' Supply a shorter tag and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19706',' invalid SCN',' The input SCN is either not a positive integer or too large.',' Check the input SCN and make sure it is a valid SCN.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19707',' invalid record block number - string',' The input number is either negative or too large.',' Check the input record block number and make sure it is a valid number clauses in the CREATE DATABASE statement.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19708',' log destination exceeds maximum length of string characters',' When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.',' Supply a shorter destination and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19709',' numeric parameter must be non-negative integer',' A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.',' Supply a valid numeric parameter.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19710',' unsupported character set string',' When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.',' Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19711',' cannot use reNormalizeAllFileNames while database is open',' An attempt was made to re-normalize all the file names in the control file while the database is open.',' Close the database before using the reNormalizeAllFileNames procedure.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19712',' table name exceeds maximum length of string',' The table name string exceeds the maximum length.',' Retry the operation with a shorter table name.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19713',' invalid copy number: string',' The copy number is not in a valid range or you have reached the maximum limit.',' Report the error and other information to support.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19714',' length for generated piece name longer than string',' The specified format exceeds the maximum length for the piece name.',' Change the format to create shorter piece names.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19715',' invalid format for piece name',' A restricted format was used incorrectly.',' Change the format by removing the restricted format.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19720',' Error occurred when converting an OCI number into an SCN',' This is most likely caused by an invalid SCN number that came from an external file, such as an export file.',' See other errors on the error stack to look for the source of the problem.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19721',' Cannot find datafile with absolute file number string in tablespace string',' Cannot find one of the data files that should be in the pluggable set.',' Make sure all datafiles are specified via import command line option or parameter files.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19722',' datafile string is an incorrect version',' The datafile is an incorrect version. It contains either less or more changes then the desired version.',' Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19723',' Cannot recreate plugged in read-only datafile string',' The datafile is plugged in read only. It cannot re-created.',' Use ALTER DATABASE RENAME FILE command instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19724',' snapshot too old: snapshot time is before file string plug-in time',' The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.',' retry the query.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19725',' can not acquire plug-in enqueue',' There maybe another ALTER DATABASE RESET COMPATIBILITY command issued concurrently, preventing this process from acquiring the plug-in enqueue.',' Retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19726',' cannot plug data [string] at level string into database running at compatibility level string',' Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data.',' Raise the value of the COMPATIBLE initialization parameter and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19727',' cannot plug data [string] at level string into database running Oracle string',' Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data.',' Upgrade Oracle and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19728',' data object number conflict between table string and partition string in table string',' The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One cannot exchange the table with the partition in this case.',' Use the ALTER TABLE MOVE PARTITION command to move the offending partition, so that the partition will get a new data object number. Retry the operation then.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19729',' File string is not the initial version of the plugged in datafile',' The file is not the initial version of the plugged in datafile.',' Use the correct initial version of the plugged in datafile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19730',' can not convert offline plugged-in datafile string',' As part of making a tablespace read-write, we need to convert datafiles that are plugged in read only. The file must be online.',' Bring the datafile online and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19731',' cannot apply change to unverified plugged-in datafile string',' Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery.',' Use the correct control file and continue recovery.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19732',' incorrect number of datafiles for tablespace string',' The number of datafiles in the export file for the referred tablespace is not the same as expected. This is most likely caused by a user editing the export file.',' Use the correct export file and retry the operation.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19733',' COMPATIBLE parameter needs to be string or greater',' 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.',' Shutdown and restart with a higher compatibility setting.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19734',' wrong creation SCN - control file expects converted plugged-in datafile',' When a tablespace is plugged into a database, the tablespace is initially read only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile.',' Either restore the converted datafile or continue recovering the datafile.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19735',' wrong creation SCN - control file expects initial plugged-in datafile',' When a tablespace is plugged into a database, the tablespace is initially read only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the converted datafile.',' Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19736',' can not plug a tablespace into a database using a different national character set',' Oracle does not support plugging a tablespace into a database using a different national character set.',' Use import/export or unload/load to move data instead.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-19999',' skip_row procedure was called',' The SKIP_ROW procedure was called which raises this error.',' SKIP_ROW should only be called within a trigger or a procedure called by a trigger.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-20000',' string',' The stored procedure RAISE_APPLICATION_ERROR was called which causes this error to be generated.',' Correct the problem as described in the error message or contact the application administrator or database administrator for more information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21000',' error number argument to raise_application_error of stringstring is out of range',' An attempt was made to specify a number not in the allowed range.',' Use an error number in the range of -20000 to -20999, inclusive.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21001',' error number argument to raise_system_error of stringstring is out of range',' An attempt was made to specify a number not in the allowed range.',' Use an error number in the range of -23300 to -24299, or -29300 to -29399, inclusive.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21300',' objects option not installed',' The objects option is not installed at this site. object types and other object features are, therefore, unavailable.',' Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact Oracle Support Services if the objects option needs to be purchased.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21301',' not initialized in object mode',' This function requires the OCI process to be initialized in object mode.',' Specify OCI_OBJECT mode when calling OCIInitialize().');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21500',' internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]',' This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition.',' Report to Oracle Support Services. The first argument is the internal error number.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21501',' program could not allocate memory',' The operating system has run out of memory.',' Take action to make more memory available to the program.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21503',' program terminated by fatal error',' A program is in an unrecoverable error state.',' Report to Oracle Support Services.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21520',' database server driver not installed',' User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in.',' Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21521',' exceeded maximum number of connections in OCI (object mode only)',' User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.',' Close some of existing and unused connections before opening more connections.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21522',' attempted to use an invalid connection in OCI (object mode only)',' User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to de-reference a REF obtained from a connection which has been terminated.',' Ensure that the connection exists and is still valid.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21523',' functionality not supported by the server (object mode only)',' User attempted to use a functionality that the server does not support.',' Upgrade the server.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21524',' object type mismatch',' The object type of the object is different from what is specified.',' Check the type of the object and correct it.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21525',' attribute number or (collection element at index) string violated its constraints',' Attribute value or collection element value violated its constraint.',' Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element''s schema information.');
INSERT INTO errors (CODE,DESCRIPTION,CAUSE,ACTION) VALUES ('ORA-21526',' initialization failed',' The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value.',' Check that all NLS environment variables are well-formed.');
