/*******************************************************************************/ /* Document : Just a listing of a number of ORA- messages that you might */ /* encounter using Oracle RDBMS 9i, 10g, 11g. */ /* Doc. Version : 11 */ /* File : oracle_ora_messages.txt */ /* Purpose : providing some info on ORA- messages/errors, and */ /* possible solutions. */ /* This note is not meant to be a "reference" of any kind. */ /* It's just a very dumb collection of some ORA- errors */ /* and possible solutions. */ /* Date : 21-04-2009 */ /* Compiled by : Albert */ /* */ /* Best use : Just use find/search of your editor, to search */ /* for a keyword or ORA- number. */ /* Because such a ORA- message can be repeated many times in */ /* this document, it's advisable to search troughout the */ /* whole document (search multiple times). */ /*******************************************************************************/ #################################################################################################### SECTION 1: Introduction - Probably a few of the most common (and simplest) Oracle error codes: #################################################################################################### Although there are a couple of thousends of ORA- (error-) messages, the list below shows (some) of the most common ones. ORA-00001 Unique constraint violated. (Invalid data has been rejected) ORA-00600 Internal error (general identifier of some internal error) ORA-03113 End-of-file on communication channel (you have lost the Network connection) ORA-03114 Not connected to ORACLE ORA-00942 Table or view does not exist ORA-01017 Invalid Username/Password ORA-01031 Insufficient privileges ORA-01034 Oracle not available (the database might be down) ORA-01401 inserted value too large for column (or ORA-12899: value too large for column) ORA-01403 No data found ORA-01555 Snapshot too old (Long running Query terminates, because Rollback/Undo has been overwritten) ORA-12154 TNS:could not resolve service name ORA-12203 TNS:unable to connect to destination ORA-12500 TNS:listener failed to start a dedicated server process" ORA-12545 TNS:name lookup failure" ORA-12560 TNS:protocol adapter error" Other prefix codes PLS-????? PL/SQL Error MOD-????? SQL Module error FRM-????? Oracle Forms error SQL-Loader-??? SQL Loader error IMP-????? Import error EXP-????? Export error RMAN-????? RMAN messages (the 8i,9i,10g,11g main backup, restore, and recovery tool) But there exists more categories. >> How do you "see" or find the ORA- errors? There are two main situations where you can be confronted with ORA- error messages: - You might find them in the main logfile of an Oracle instance, namely the "alert.log" of the database which usually has a filename like "alert.log", like for example "alertSALES.log". (In older versions of Oracle, and 9i, and 10g, the alert.log file is a simple ascii and thus readable file. In Oracle 11g, the situation is a little more complex. This will not be the subject of this note. But in SECTION 4 you will find an article called "11g Diagnosability: Frequently Asked Questions"). - They might appear when you are working with a tool,like "sqlplus", and you were "doing something", that lead to some sort of error condition, and that the database reacted upon with an ORA- message. Usually, those messages (the more serious ones) are also written in the "alert.log" file. In fact, the ORA- messages that may arise because you are doing something that the database does not "like" much at that time, will probably NOT logged into the alert.log if the errorcondition only affects your session. But if (whatever you were doing), had any "database wide" impact, it will probably be logged in the alert.log file as well. Simply put: you will see them on your screen (working with some application or tool) when an error condition arose. Or you may find them when you inspect the alert.log file. The ORA-600 or ORA-00600 error is a special type of general message, alerting you to "some serious internal error". It can be so that a "bug" has revealed itself and leads to a condition where the database throws this error to the alertlog. Or there was a some other sort of condition, severely enough, to show this error. You cannot tell much from the ORA-600 iself. But it is almost always accompanied with a list of arguments, and some descriptive text, like in the following example: ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [12700], [3383], [41957137], [44], [], [], [], [] New to Oracle 11g are the ORA-700 errors or "soft asserts". ORA-700 errors are referred to as soft asserts in 11g. Basically these are internal errors that do not cause anything fatal to occur in the process, and so the process can continue. You might consider them to be like "mild or soft" ORA-600 errors. #################################################################################################### SECTION 1: Notes about a number of important ORA- and ORA-600 messages. #################################################################################################### ======================================================================= Notes Related to ORA-1110 & ORA-1113 & ORA-1547 & ORA-1194 & ORA-1195: ======================================================================= ----- Note: ----- Applies to: Oracle Server - Enterprise Edition - Version: 9.0.1.0 to 10.2.0.1 Information in this document applies to any platform. Goal The goal of this article is to assist DBA's who encounter the ORA-1110, and to point them in the right direction. Several notes have been referenced depending on the subsequent errors. If the DBA is unable to resolve the issue after reading the appropriate note, a script to collect diagnostic information has been provided below. The output of this script should be uploaded into the service request. Solution How to troubleshoot and resolve an ORA-1110 Definition Error: ORA 1110 Text: datafile : ------------------------------------------------------------------------------- Cause: This message reports the filename involved with other messages. Action: See the associated messages for a description of the problem. The ORA-1110 displays the physical datafile in which Oracle is having a problem accessing. The ORA-1110 is followed by one or more messages. These messages may be Oracle specific messages or be related to the operating system. The first aim is to identify all error messages encounted prior to addressing the issue: Below is a list of the common errors that may follow the ORA-1110. ORA-1157 "cannot identify datafile - file not found" ORA-1578 "ORACLE data block corrupted (file # %s, block # %s)" ORA-376 "file cannot be read at this time" ORA-1194 "file needs more recovery to be consistent" ORA-1547 "warning: RECOVER succeeded but OPEN RESETLOGS would get error" Addressing an ORA-1157 (cannot identify datafile - file not found) Note 184327.1 covers the ORA-1157 in greater detail. Addressing an ORA-1578 (ORACLE data block corrupted (file # %s, block # %s)) Note 28814.1 covers the ORA-1578 in greater detail. Addressing an ORA-376 (file cannot be read at this time) Note 183327.1 covers the ORA-376 in greater detail. Addressing an ORA-1194 (file needs more recovery to be consistent) & ORA-1547 (warning: RECOVER succeeded but OPEN RESETLOGS would get error) Note 435201.1 covers the ORA-1194 & ORA-1547 in greater detail. After following the above notes if you are not able to restore, recover and open the database please run the following script below. Please provide the output in the service request that you may raise. (upload recovery_info.txt) set pagesize 20000 set linesize 180 set pause off set serveroutput on set feedback on set echo on set numformat 999999999999999 Spool recovery_info.txt select substr(name, 1, 50), status from v$datafile; select substr(name,1,40), recover, fuzzy, checkpoint_change# from v$datafile_header; select GROUP#,substr(member,1,60) from v$logfile; select * from v$recover_file; select distinct status from v$backup; select hxfil FILENUMBER,fhsta STATUS,fhscn SCN,fhrba_Seq SEQUENCE from x$kcvfh; select distinct (fuzzy) from v$datafile_header; spool off exit Keywords ORA-00376 ; ORA-01113 ; ORA-01157 ; ORA-01194 ; ORA-01547 ; ORA-01578 ; ORA-1113 ; ORA-1157 ; ORA-1194 ; ORA-1547 ; ORA-1578 ; ORA-376 ----- Note: ----- Subject: DIAGNOSING ORA-1547 & ORA-1194 ERRORS DURING RECOVERY Doc ID: 435201.1 Type: HOWTO Applies to: Oracle Server - Enterprise Edition - Version: 9.0.0 to 10.2.0 Information in this document applies to any platform. Goal The following note provides an example of ORA-1157 & ORA 1194 and how to resolve it. Error message descriptions ORA 1157 Text: warning: RECOVER succeeded but OPEN RESETLOGS would get error ------------------------------------------------------------------- Cause: The background process was not able to find one of the datafiles. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online datafiles. Accompanying messages from the operating system will describe why the file was not found. ORA 1194 Text: file needs more recovery to be consistent ------------------------------------------------------ Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The named file was not closed cleanly when it was last opened by the database. The most likely cause of this message is forgetting to restore the file from a backup before doing incomplete recovery. Solution Errors ORA-1157 & ORA 1194 are commonly received together following a recovery attempt. SQL> recover database using backup controlfile until cancel ORA-00279: change 2008250 generated at 06/07/2007 11:50:32 needed for thread 1 ORA-00289: suggestion : /recovery_area/V102/archivelog/2007_06_07/o1_mf_1_2_%u_.arc ORA-00280: change 2008250 for thread 1 is in sequence #2 Specify log: {=suggested | filename | AUTO | CANCEL} cancel ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 3 needs more recovery to be consistent ORA-01110: data file 3: '/oradata/V102/sysaux01.dbf' Following this error message issue the following SQL command, you will most commonly find at least one datafile which is in FUZZY mode. SQL> select file#,STATUS, FUZZY from v$datafile_header; FILE# STATUS FUZ -------- ------------ ------ 1 ONLINE NO 2 ONLINE NO 3 ONLINE YES 4 ONLINE NO This example shows file#3 in fuzzy mode. The best solution at this point is to apply more archivelogs in order to get offending datafile/s out of FUZZY mode. In many cases the recovery session may be requesting an archivelog which has not been generated. The reason for this is because the recovery clause included "using backup controlfile" If this is the case you need to apply the current online redo log to complete the recovery: This command below will return the current online redo log/s. SQL> select member from v$logfile lf , v$log l where l.status='CURRENT' and lf.group#=l.group#; then proceed to issue: SQL> recover database using backup controlfile until cancel; When the recovery session prompts for an archive log specify the online redo log from above and hit enter. This should complete the recovery and then you will be able to open the database. SQL> alter database open resetlogs; Note: If after applying all archive logs and online redo logs the database does not open please provide the following script output to Oracle support to assist with the recovery. ( Please upload recovery_info.txt) set pagesize 20000 set linesize 180 set pause off set serveroutput on set feedback on set echo on set numformat 999999999999999 Spool recovery_info.txt select substr(name, 1, 50), status from v$datafile; select substr(name,1,40), recover, fuzzy, checkpoint_change# from v$datafile_header; select GROUP#,substr(member,1,60) from v$logfile; select * from v$recover_file; select distinct status from v$backup; select hxfil FILENUMBER,fhsta STATUS,fhscn SCN,fhrba_Seq SEQUENCE from x$kcvfh; select distinct (fuzzy) from v$datafile_header; spool off exit ----- Note: ----- Problem: ======== When you startup your database, the mount is successful but the database fails to open with the following error: ORA-1571 redo version 8.0.5 incompatible with Oracle Version 8.0.0 Since the error is misleading, you try to recover until cancel and open the database with the ResetLogs option. When you apply the online redo logs, you get the following stack of errors: recover database until cancel; -> apply log1orcl.ora ORA-331 log version 8.0.5 incompatible with Oracle version 8.0.0 ORA-334 archived log: log1orcl.ora ORA-1547 "warning: RECOVER succeeded but OPEN RESETLOGS would get error below" ORA-1194 file #1 needs more recovery to be consistent ORA-1110 file .. Solution: ========= Edit the init.ora file and assign the correct value to the COMPATIBLE parameter. Make this parameter the same as the database version. Explanation: ============ This problem occurs when your database is shutdown with the abort option and the compatible setting is commented out or changed to a lower value inside the init.ora file. If the compatible parameter inside the init.ora file is changed to a lower value or commented out, then this error appears when the redo log files are opened ----- Note: ----- Important: Always be sceptical with advice and solutions from any type of document (including this one). Suppose the system comes with: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/u03/oradata/tstc/dbsyst01.dbf' Either you had the database in archive mode or in non archive mode: archive mode RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; ALTER DATABASE OPEN RESETLOGS; non-archive mode: # RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; ALTER DATABASE OPEN RESETLOGS; If you have checked that the scn's of all files are the samed number, you might try in the init.ora file: _allow_resetlogs_corruption = true You should be fully aware of what this init.ora parameter does with your instance. If you are not aware of the impact, please investigate that first. ----- Note: ----- Doc ID: Note:41767.1 Subject: ORA-600 [1113] "Parent SO is free when adding a child" Type: REFERENCE Status: PUBLISHED Content Type: TEXT/PLAIN Creation Date: 23-JAN-1997 Last Revision Date: 29-OCT-2002 Note: For additional ORA-600 related information please read [NOTE:146580.1] PURPOSE: This article discusses the internal error "ORA-600 [1113]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [1113][a][b][c][d][e] VERSIONS: versions 7.3.X to 8.1.7 DESCRIPTION: We are freeing a state object but it already appears to be on the free list. This is generally an in memory (SGA) corruption or due to a bug in mishandling the state objects. FUNCTIONALITY: STATE OBJECT MANAGER IMPACT: PROCESS FAILURE POSSIBLE INSTANCE FAILURE IF DETECTED BY PMON PROCESS NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: For repeatable occurrances and further analysis, please submit the trace files (include any PMON traces also) and alert.log to Oracle Support Services. Known Issues: Bug 425862: ORA-600 [1113] OR [KSSRMP1] WHEN SELECTING FROM V$PWFILE_USERS fixed in 8.0.6 and 8.1.6 releases. Workaround is to use ORDER BY clause in the select statement. Bug 1307247: ORA-600 [1113] WHEN AN ANALYZE OPERATION FAILS OR IS CANCELLED fixed in 8.0.6.3, 8.1.7.1 and 9.0.0 releases. REFERENCES: [NOTE:139162.1] ORA-600 [kssrmp1] ----- Note: ----- Problem Description ------------------- You restored your hot backup and you are trying to do a point-in-time recovery. When you tried to open your database you received the following error: ORA-01195: online backup of file needs more recovery to be consistent Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The reported file is an online backup that must be recovered to the time the backup ended. Action: Either apply more redo logs until the file is consistent or restore the file from an older backup and repeat the recovery. For more information about online backup, see the index entry "online backups" in the . This is assuming that the hot backup completed error free. Solution Description -------------------- Continue to apply the requested logs until you are able to open the database. Explanation ----------- When you perform hot backups on a file, the file header is frozen. For example, datafile01 may have a file header frozen at SCN #456. When you backup the next datafile the SCN # may be differnet. For example the file header for datafile02 may be frozen with SCN #457. Therefore, you must apply archive logs until you reach the SCN # of the last file that was backed up. Usually, applying one or two more archive logs will solve the problem, unless there was alot of activity on the database during the backup. ----- Note: ----- ORA-01194: file 1 needs more recovery to be consistent I am working with a test server, I can load it again but I would like to know if this kind of problem could be solved or not. Just to let you know, that I am new in Oracle Database Administration. I ran a hot backup script, which deleted the old ARCHIVE, logs at the end. After checking the script's log, I realized that the hot backup was not successful and it deleted the Archives. I tried to startup the database and an error occurred; "ORA-01589: must use RESETLOGS or NORESETLOGS option for database open" I tried to open it with the RESETLOGS option then another error occurred; "ORA-01195: online backup of file 1 needs more recovery to be consistent" Just because, it was a test environment, I have never taken any cold backups. I still have hot backups. I don't know how to recover from those. If anyone can tell me how to do it from SQLPLUS (SVRMGRL is not loaded), I would really appreciate it. Thanks, Hi Hima, The following might help. You now have a database that is operating like it's in noarchive mode since the logs are gone. 1. Mount the database. 2. Issue the following query: SELECT V1.GROUP#, MEMBER, SEQUENCE#, FIRST_CHANGE# FROM V$LOG V1, V$LOGFILE V2 WHERE V1.GROUP# = V2.GROUP# ; This will list all your online redolog files and their respective sequence and first change numbers. 3. If the database is in NOARCHIVELOG mode, issue the query: SELECT FILE#, CHANGE# FROM V$RECOVER_FILE; If the CHANGE# is GREATER than the minimum FIRST_CHANGE# of your logs, the datafile can be recovered. 4. Recover the datafile, after taking offline, you cannot take system offline which is the file in error in your case. RECOVER DATAFILE '' 5. Confirm each of the logs that you are prompted for until you receive the message "Media recovery complete". If you are prompted for a non-existing archived log, Oracle probably needs one or more of the online logs to proceed with the recovery. Compare the sequence number referenced in the ORA-280 message with the sequence numbers of your online logs. Then enter the full path name of one of the members of the redo group whose sequence number matches the one you are being asked for. Keep entering online logs as requested until you receive the message "Media recovery complete". 6. Bring the datafile online. No need for system. 7. If the database is at mount point, open it Perform a full closed backup of the existing database ----- Note: ----- Recover until time using backup controlfile Hi, I am trying to perform an incomplete recovery to an arbitrary point in time in the past. Eg. I want to go back five minutes. I have a hot backup of my database. (Tablespaces into hotbackup mode, copy files, tablespaces out of hotbackup mode, archive current log, backup controlfile to a file and also to a trace). (yep im in archivelog mode as well) I shutdown the current database and blow the datafiles,online redo logs,controlfiles away. I restore my backup copy of the database - (just the datafiles) startup nomount and then run an edited controlfile trace backup (with resetlogs). I then RECOVER DATABSE UNTIL TIME 'whenever' USING BACKUP CONTROLFILE. I'm prompted for logs in the usual way but the recovery ends with an ORA-1547 - Recover succeeded but open resetlogs would give the following error. The next error is that datafile 1 (system ts) - would need more recovery. Now metalink tells me that this is usually due to backups being restored that are older than the archive redo logs - this isn't the case. I have all the archive redo logs I need to cover the time the backup was taken up to the present. The time specified in the recovery is after the backup as well. What am I missing here? Its driving me nuts. I'm off back to the docs again! Thanks in advance Tim -------------------------------------------------------------------------------- From: Anand Devaraj 15-Aug-02 15:15 Subject: Re : Recover until time using backup controlfile The error indicates that Oracle requires a few more scns to get all the datafiles in sync. It is quite possible that those scns are present in the online redo logfiles which were lost. In such cases when Oracle asks for a non-existent archive log, you should provide the complete path of the online log file for the recovery to succeed. Since you dont have an online log file you should use RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE. In this case when you exhaust all the archive log files, you issue the cancel command which will automatically rollback all the incomplete transactions and get all the datafile headers in sync with the controlfile. To do an incomplete recovery using time,you usually require the online logfiles to be present. Anand -------------------------------------------------------------------------------- From: Radhakrishnan paramukurup 15-Aug-02 16:19 Subject: Re : Recover until time using backup controlfile I am not sure whether you have missed this step or just missed in the note. You need to also to switch the log at the end of the back up (I do as a matter of practice else you need the next log which is not sure to be available in case of a failure). Otherwise some of the changes to reach a consistant state is still in the online log and you can never open untill you reach a consistent state. Hope this helps ........ -------------------------------------------------------------------------------- From: Mark Gokman 15-Aug-02 16:41 Subject: Re : Recover until time using backup controlfile To successfully perform incomplete recovery, you need a full db backup that was completed prior to the point to which you want to recover, plus you need all archive logs containing all SCNs up to the point to which you want to recover. Applying these rules to your case, I have two questions: - are you recovering to the point in time AFTER the time the successful full backup was copleted? - is there an archive log that was generated AFTER the time you specify in until time? If both answers are yes, then you should have no problems. I actually recently performed such a recovery several times. -------------------------------------------------------------------------------- From: Tim Palmer 15-Aug-02 18:02 Subject: Re : Re : Recover until time using backup controlfile Thanks Guys! I think Mark has hit the nail on the head here. I was being an idiot! Ive ran this exercise a few more times (with success) and I am convinced that what I was doing was trying to recover to a point in time that basically was before the latest scn of any one file in the hot backup set I was using - convinced myself that I wasnt - but I must have been..... perhaps I need a holiday! Thanks again Tim -------------------------------------------------------------------------------- From: Oracle, Rowena Serna 16-Aug-02 15:44 Subject: Re : Recover until time using backup controlfile Thanks to mark for his input for helping you out. ----- Note: ----- ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01152: file 2 was not restored from a sufficiently old backup ORA-01110: data file 2: 'D:\ORACLE\ORADATA\\UNDOTBS01.DBF' File number, name and directory may vary depending on Oracle configuration Details: Undo tablespace data description In an Oracle database, Undo tablespace data is an image or snapshot of the original contents of a row (or rows) in a table. This data is stored in Undo segments (formerly Rollback segments in earlier releases of Oracle) in the Undo tablespace. When a user begins to make a change to the data in a row in an Oracle table, the original data is first written to Undo segments in the Undo tablespace. The entire process (including the creation of the Undo data) is recorded in Redo logs before the change is completed and written in the Database Buffer Cache, and then the data files via the database writer (DBWn) process. If the transaction does not complete due to some error or should there be a user decision to reverse (rollback) the change, this Undo data is critical for the ability to roll back or undo the changes that were made. Undo data also ensures a way to provide read consistency in the database. Read consistency means that if there is a data change in a row of data that is not yet committed, a new query of this same row or table will not display any of the uncommitted data to other users, but will use the information from the Undo segments in the Undo tablespace to actually construct and present a consistent view of the data that only includes committed transactions or information. During recovery, Oracle uses its Redo logs to play forward through transactions in a database so that all lost transactions (data changes and their Undo data generation) are replayed into the database. Then, once all the Redo data is applied to the data files, Oracle uses the information in the Undo segments to undo or roll back all uncommitted transactions. Once recovery is complete, all data in the database is committed data, the System Change Numbers (SCN) on all data files and the control_files match, and the database is considered consistent. As for Oracle 9i, the default method of Undo management is no longer manual, but automatic; there are no Rollback segments in individual user tablespaces, and all Undo management is processed by the Oracle server, using the Undo tablespace as the container to maintain the Undo segments for the user tablespaces in the database. The tablespace that still maintains its own Rollback segments is the System tablespace, but this behavior is by design and irrelevant to the discussion here. If this configuration is left as the default for the database, and the 5.022 or 5.025 version of the VERITAS Backup Exec (tm) Oracle Agent is used to perform Oracle backups, the Undo tablespace will not be backed up. If Automatic Undo Management is disabled and the database administrator (DBA) has modified the locations for the Undo segments (if the Undo data is no longer in the Undo tablespace), this data may be located elsewhere, and the issues addressed by this TechNote may not affect the ability to fully recover the database, although it is still recommended that the upgrade to the 5.026 Oracle Agent be performed. Scenario 1 The first scenario would be a recovery of the entire database to a previous point-in-time. This type of recovery would utilize the RECOVER DATABASE USING BACKUP CONTROLFILE statement and its customizations to restore the entire database to a point before the entry of improper or corrupt data or to roll back to a point before the accidental deletion of critical data. In this type of situation, the most common procedure for the restore is to just restore the entire online backup over the existing Oracle files with the database shutdown. (See the Related Documents section for the appropriate instructions on how to restore and recover an Oracle database to a point-in-time using an online backup.) In this scenario, where the entire database would be rolled back in time, an offline restore would include all data files, archived log files, and the backup control_file from the tape or backup media. Once the RECOVER DATABASE USING BACKUP CONTROLFILE command was executed, Oracle would begin the recovery process to roll forward through the Redo log transactions, and it would then roll back or undo uncommitted transactions. At the point when the recovery process started on the actual Undo tablespace, Oracle would see that the SCN of that tablespace was too high (in relation to the record in the control_file). This would happen simply because the Undo tablespace wasn't on the tape or backup media that was restored, so the original Undo tablespace wouldn't have been overwritten, as were the other data files, during the restore operation. The failure would occur because the Undo tablespace would still be at its SCN before the restore from backup (an SCN in the future as related to the restored backup control_file). All other tablespaces and control_files would be back at their older SCNs (not necessarily consistent yet), and the Oracle server would respond with the following error messages: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01152: file 2 was not restored from a sufficiently old backup ORA-01110: data file 2: 'D:\ORACLE\ORADATA\\UNDOTBS01.DBF' At this point, the database cannot be opened with the RESETLOGS option, nor in a normal mode. Any attempt to do so yields the error referenced above. SQL> alter database open resetlogs; alter database open resetlogs * Error at line 1: ORA-01152: file 2 was not restored from a sufficiently old backup ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DRTEST\UNDOTBS01.DBF' The only recourse here is to recover or restore an older backup that contains an Undo tablespace, whether from an older online backup, or from a closed or offline backup or copy of the database. Without this ability to acquire an older Undo tablespace to rerun the recovery operation, it will not be possible to start the database. At this point, Oracle Technical Support must be contacted. Scenario 2 The second scenario would involve the actual corruption or loss of the Undo tablespace's data files. If the Undo tablespace data is lost or corrupted due to media failure or other internal logical error or user error, this data/tablespace must be recovered. Oracle 9i does offer the ability to create a new Undo tablespace and to alter the Oracle Instance to use this new tablespace when deemed necessary by the DBA. One of the requirements to accomplish this change, though, is that there cannot be any active transactions in the Undo segments of the tablespace when it is time to actually drop it. In the case of data file corruption, uncommitted transactions in the database that have data in Undo segments can be extremely troublesome because the existence of any uncommitted transactions will lock the Undo segments holding the data so that they cannot be dropped. This will be evidenced by an "ORA-01548" error if this is attempted. This error, in turn, prevents the drop and recreation of the Undo tablespace, and thus prevents the successful recovery of the database. To overcome this problem, the transaction tables of the Undo segments can be traced to provide details on transactions that Oracle is trying to recover via rollback and these traces will also identify the objects that Oracle is trying to apply the undo to. Oracle Doc ID: 94114.1 may be referenced to set up a trace on the database startup so that the actual transactions that are locking the Undo segments can be identified and dropped. Dropping objects that contain uncommitted transactions that are holding locks on Undo segments does entail data loss, and the amount of loss depends on how much uncommitted data was in the Undo segments at the point of failure. When utilized, this trace is actually monitoring or dumping data from the transaction tables in the headers of the Undo segments (where the records that track the data in the Undo segments are located), but if the Undo tablespace's data file is actually missing, has been offline dropped, or if these Undo segment headers have been corrupted, even the ability to dump the transaction table data is lost and the only recourse at this point may be to open the database, export, and rebuild. At this point, Oracle Technical Support must be contacted. Backup Exec Agent for Oracle 5.022 and 5.025 should be upgraded to 5.026 When using the 5.022 or 5.025 version of the Backup Exec for Windows Servers Oracle Agent (see the Related Documents section for the appropriate instructions on how to identify the version of the Oracle Agent in use), the Oracle Undo tablespace is not available for backup because the Undo tablespace falls into the type category of Undo, and only tablespaces with a content type of PERMANENT are located and made available for backup. Normal full backups with all Oracle components selected will run without error and will complete with a successful status since the Undo tablespace is not actually flagged as a selection. In most Oracle recovery situations, this absence of the Undo tablespace data for restore would not cause any problem because the original Undo tablespace is still available on the database server. Restores of User tablespaces, which do not require a rollback in time, would proceed normally since lost data or changes would be replayed back into the database, and Undo data would be available to roll back uncommitted transactions to leave the database in a consistent state and ready for user access. However, in certain recovery scenarios, (in which a rollback in time or full database recovery is attempted, or in the case of damaged or missing Undo tablespace data files) this missing Undo data can result in the inability to properly recover tablespaces back to a point-in-time, and could potentially render the database unrecoverable without an offline backup or the assistance of Oracle Technical Support. The scenarios in this TechNote describe two examples (this does not necessarily imply that these are the only scenarios) of how this absence of the Undo tablespace on tape or backup media, and thus its inability to be restored, can result in failure of the database to open and can result in actual data loss. The only solution to the problems referenced within this TechNote is to upgrade the Backup Exec for Windows Servers Oracle Agent to version 5.026, and to take new offline (closed database) and then new online (running database) backups of the entire Oracle 9i database as per the Oracle Agent documentation in the Backup Exec 9.0 for Windows Servers Administrator's Guide. Oracle 9i database backups made with the 5.022 and 5.025 Agent that shipped with Backup Exec 9.0 for Windows Servers build 4367 or build 4454 should be considered suspect in the context of the information provided in this TechNote. Note: The 5.022, 5.025, and 5.026 versions of the Oracle Agent are compatible with Backup Exec 8.6 for Windows NT and Windows 2000, which includes support for Oracle 9i, as well as Backup Exec 9.0 for Windows Servers. See the Related Documents section for instructions on how to identify the version of the Oracle Agent in use. ----- Note: ----- Subject: Unable To Open Database Due To ORA-01113 And ORA-01110 Errors Doc ID: 221772.1 Type: PROBLEM Modified Date : 22-NOV-2007 Status: PUBLISHED fact: Oracle Server - Enterprise Edition fact: Oracle Server - Standard Edition fact: Tablespace contains rollback segments symptom: Unable to open database symptom: Cannot Startup Database symptom: ORA-01113: file %s needs media recovery symptom: ORA-01110: data file %s: '%s' cause: The non-SYSTEM rollback segments are to be used for recovery (specifically the clean up of dead transactions). When the rollback segments cannot be accessed due to an inconsistent file, the ORA-01113 and ORA-01110 errors occur. fix: The steps to resolve the datafile inconsistency are: 1) comment out the ROLLBACK_SEGMENTS parameter from INIT.ORA 2) start the instance and recover the datafile: SVRMGR> STARTUP MOUNT SVRMGR> ALTER DATABASE DATAFILE '[datafile_name]' OFFLINE; SVRMGR> RECOVER TABLESPACE [rollback_tablespace_name]; SVRMGR> ALTER TABLESPACE [rollback_tablespace_name] ONLINE; SVRMGR> ALTER ROLLBACK SEGMENT [rollback_segment_name] ONLINE; 3) reapply the ROLLBACK_SEGMENTS parameter in INIT.ORA for future instance startups When the above steps do not help in bringing the rollback segments online again, you can follow the steps in: drop the rollback tablespace. ----- Note: ----- if you cannot open the database, because a datafile needs recovery (and you do not have the corresponding archive logs), this method only helps IF YOU CAN AFFORD TO LOOSE THAT DATAFILE. symptom: Database startup fails symptom: ORA-01113: file %s needs media recovery symptom: ORA-01110: data file %s: '%s' symptom: Database in archive log mode symptom: Backup available symptom: Datafile requiring media recovery is not needed change: The following command was issued: SQL> alter database datafile offline; cause: Datafile was taken offline while the database was up. Therefore, the database is expecting media recovery for that datafile. fix: Do the following only if the datafile requiring recovery is not needed and can be dropped. 1. Mount the database: SVRMGR> startup mount pfile=xxxxx.ora 2. Offline drop the datafile needing media recovery: SVRMGR> alter database datafile 'full path filename' offline drop; 3. Open the database: SVRMGR> alter database open; 4. Export the objects out of the remaining datafiles belonging to the affected tablespace. 5. Drop the affected tablespace: SVRMGR> drop tablespace including contents; 6. Recreate the tablespace. 7. Import the objects into the new tablespace from the export dump file. Please note that this will only work if the tablespace remains online. If it is taken offline for any reason (eg manually, by ALTER TABLESPACE xxxx OFFLINE IMMEDIATE, or automatically by Oracle) then you will not be able to bring it back online unless you recover ALL the datafiles. ----- Note: ----- Subject: How to recover and open the database if the archivelog required for recovery is either missing, lost or corrupted? Doc ID: Note:465478.1 Type: HOWTO Last Revision Date: 28-MAY-2008 Status: PUBLISHED In this Document Goal Solution References Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1 Information in this document applies to any platform. Goal How to recover and open the database if the archivelog required for recovery is either missing, lost or corrupted? Solution The assumption here is that we have exhausted all possible locations to find another good and valid copy or backup of the archivelog that we are looking for, which could be in one of the following: directories defined in the LOG_ARCHIVE_DEST_n another directory in the same server or another server standby database RMAN backup OS backup If the archivelog is not found in any of the above mentioned locations, then the approach and strategy on how to recover and open the database depends on the SCN (System Change Number) of the datafiles, as well as, whether the log sequence# required for the recovery is still available in the online redologs. For the SCN of the datafiles, it is important to know the mode of the database when the datafiles are backed up. That is whether the database is open, mounted or shutdown (normally) when the backup is taken. If the datafiles are restored from an online or hot backup, which means that the database is open when the backup is taken, then we must apply at least the archivelog(s) or redolog(s) whose log sequence# are generated from the beginning and until the completion of the said backup that was used to restore the datafiles. However, if the datafiles are restored from an offline or cold backup, and the database is cleanly shutdown before the backup is taken, that means that the database is either not open, is in nomount mode or mounted when the backup is taken, then the datafiles are already synchronized in terms of their SCN. In this situation, we can immediately open the database without even applying archivelogs, because the datafiles are already in a consistent state, except if there is a requirement to roll the database forward to a point-in-time after the said backup is taken. The critical key thing here is to ensure that all of the online datafiles are synchronized in terms of their SCN before we can normally open the database. So, run the following SQL statement, as shown below, to determine whether the datafiles are synchronized or not. Take note that we query the V$DATAFILE_HEADER, because we want to know the SCN recorded in the header of the physical datafile, and not the V$DATAFILE, which derives the information from the controlfile. select status, checkpoint_change#, to_char(checkpoint_time, 'DD-MON-YYYY HH24:MI:SS') as checkpoint_time, count(*) from v$datafile_header group by status, checkpoint_change#, checkpoint_time order by status, checkpoint_change#, checkpoint_time; The results of the above query must return one and only one row for the online datafiles, which means that they are already synchronized in terms of their SCN. Otherwise, if the results return more than one row for the online datafiles, then the datafiles are still not synchronized yet. In this case, we need to apply archivelog(s) or redolog(s) to synchronize all of the online datafiles. By the way, take note of the CHECKPOINT_TIME in the V$DATAFILE_HEADER, which indicates the date and time how far the datafiles have been recovered. The results of the query above may return some offline datafiles. So, ensure that all of the required datafiles are online, because we may not be able to recover later the offline datafile once we open the database in resetlogs. Even though we can recover the database beyond resetlogs for the Oracle database starting from 10g and later versions due to the introduction of the format "%R" in the LOG_ARCHIVE_FORMAT, it is recommended that you online the required datafiles now than after the database is open in resetlogs to avoid any possible problems. However, in some cases, we intentionally offline the datafile(s), because we are doing a partial database restore, or perhaps we don't need the contents of the said datafile. You may run the following query to determine the offline datafiles: select file#, name from v$datafile where file# in (select file# from v$datafile_header where status='OFFLINE'); You may issue the following SQL statement to change the status of the required datafile(s) from "OFFLINE" to "ONLINE": alter database datafile online; If we are lucky that the required log sequence# is still available in the online redologs and the corresponding redolog member is still physically existing on disk, then we may apply them instead of the archivelog. To confirm, issue the following query, as shown below, that is to determine the redolog member(s) that you can apply to recover the database: set echo on feedback on pagesize 100 numwidth 16 alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS'; select LF.member, L.group#, L.thread#, L.sequence#, L.status, L.first_change#, L.first_time, DF.min_checkpoint_change# from v$log L, v$logfile LF, (select min(checkpoint_change#) min_checkpoint_change# from v$datafile_header where status='ONLINE') DF where LF.group# = L.group# and L.first_change# >= DF.min_checkpoint_change#; If the above query returns no rows, because the V$DATABASE.CONTROLFILE_TYPE has a value of "BACKUP", then try to apply each of the redolog membes one at a time during the recovery. You may run the following query to determine the redolog members: select * from v$logfile; If you have tried to apply all of the online redolog members instead of an archivelog during the recovery, but you always received the ORA-00310 error, as shown in the example below, then the log sequence# required for recovery is no longer available in the online redolog. ORA-00279: change 189189555 generated at 11/03/2007 09:27:46 needed for thread 1 ORA-00289: suggestion : +BACKUP ORA-00280: change 189189555 for thread 1 is in sequence #428 Specify log: {=suggested | filename | AUTO | CANCEL} +BACKUP/prmy/onlinelog/group_2.258.603422107 ORA-00310: archived log contains sequence 503; sequence 428 required ORA-00334: archived log: '+BACKUP/prmy/onlinelog/group_2.258.603422107' After trying all of the possible solutions mentioned above, but you still cannot open the database, because the archivelog required for recovery is either missing, lost or corrupted, or the corresponding log sequence# is no longer available in the online redolog, since they are already overwritten during the redolog switches, then we cannot normally open the database, since the datafiles are in an inconsistent state. So, the following are the 3 options available to allow you to open the database: Option#1: Force open the database by setting the _ALLOW_RESETLOGS_CORRUPTION=TRUE in the init.ora. But there is no 100% guarantee that this will open the database. However, once the database is opened, then we must immediately rebuild the database. Database rebuild means doing the following, namely: (1) perform a full-database export, (2) create a brand new and separate database, and finally (3) import the recent export dump. This option can be tedious and time consuming, but once we successfully open the new database, then we expect minimal or perhaps no data loss at all. Before you try this option, ensure that you have a good and valid backup of the current database. Option#2: If you have a good and valid backup of the database, then restore the database from the said backup, and recover the database by applying up to the last available archivelog. In this option, we will only recover the database up to the last archivelog that is applied, and any data after that are lost. If no archivelogs are applied at all, then we can only recover the database from the backup that is restored. However, if we restored from an online or hot backup, then we may not be able to open the database, because we still need to apply the archivelogs generated during the said backup in order to synchronize the SCN of the datafiles before we can normally open the database. Option#3: Manually extract the data using the Oracle's Data Unloader (DUL), which is performed by Oracle Field Support at the customer site on the next business day and for an extra charge. If the customer wants to pursue this approach, we need the complete name, phone# and email address of the person who has the authority to sign the work order in behalf of the customer. ----- Note: ----- PURPOSE ------- To consolidate the common reasons & solutions for the ORA-1113 error. SCOPE & APPLICATION -------------------- Customers facing ORA-1113 and analysts requiring information on known issues with ORA-1113 errors. ORA-1113 ======== An ORA-1113 occurs when a datafile needs recovery. Error Explanation: ------------------ 01113, 00000, "file %s needs media recovery" Cause: An attempt was made to online or open a database with a file that is in need of media recovery. Action: First apply media recovery to the file. This error is usually followed with ORA-1110 error which will indicate the name of the datafile that needs media recovery. Eg: ORA-01113: file 28 needs media recovery ORA-01110: data file 28: '/h04/usupport/app/oracle/oradata/v817/nar.dbf' This error message indicates that a datafile that is not up-to-date with respect to the controlfile and other datafiles. Oracle's architecture is tightly coupled in the sense that all database files i.e., datafiles, redolog files, and controlfiles -- must be in sync when the database is opened or at the end of a checkpoint. This implies that the checkpoint SCN (System Commit Number) of all datafiles must be the same. If that is not the case for a particular datafile, an ORA-1113 error will be generated. For example, when you put a tablespace in hot backup mode, the checkpoint SCN of all its datafiles is frozen at the current value until you issue the corresponding end backup. If the database crashes during a hot backup and you try to restart it without doing recovery, you will likely get ORA-1113 for at least one of the datafiles in the tablespace that was being backed up, since its SCN will probably be lower than that of the controlfile and the datafiles in other tablespaces. Likewise, offlining a datafile causes its checkpoint SCN to freeze. If you simply attempt to online the file without recovering it first, its SCN will likely be much older than that of the online datafiles, and thus an ORA-1113 will result. ********************************************** Before Starting these actions do the following: ********************************************** Note : If you are using Oracle9i, use SQL*Plus, instead of Server Manager to execute the mentioned commands, since Server Manager is not available in Oracle9i. Query the V$LOG and V$LOGFILE. 1. If the database is down, you need to mount it first. SVRMGR> STARTUP MOUNT PFILE=; 2. Then connect internal Server Manager and issue the query: SVRMGR> CONNECT INTERNAL; or SQL> connect / as sysdba (for Oracle9i) SVRMGR> SELECT V1.GROUP#, MEMBER, SEQUENCE#, FIRST_CHANGE# FROM V$LOG V1, V$LOGFILE V2 WHERE V1.GROUP# = V2.GROUP# ; This will list all your online redolog files and their respective sequence and first change numbers. The steps to take next depend on the scenario in which the ORA-1113 was issued. This is discussed in the following sections. POSSIBLE CAUSES AND SOLUTIONS SUMMARY: ===================================== I. AT STARTUP AFTER CRASH WITH TABLESPACE(S) IN HOT BACKUP II. AT STARTUP AFTER RESTORING A DATAFILE OR TABLESPACE FROM A BACKUP III. TRYING TO ONLINE A DATAFILE OR TABLESPACE IV. WHEN RECOVERING ' USING BACKUP CONTROLFILE' OPTION TO DO INCOMPLETE RECOVERY I. AT STARTUP AFTER CRASH WITH TABLESPACE(S) IN HOT BACKUP ********************************************************** A. WITH ORACLE 7.1 OR LOWER 1. Mount the database.(If the database is NOT already mounted) SVRMGR> STARTUP MOUNT PFILE=; 2. Apply media recovery to the database. SVRMGR> RECOVER DATABASE; 3. Confirm each of the archived logs that you are prompted for until you receive the message "Media recovery complete". If you are prompted for an archived log that does not exist, Oracle probably needs one or more of the online logs to proceed with the recovery. Compare the sequence number referenced in the ORA-280 message with the sequence numbers of your online logs. Then enter the full path name of one of the members of the redo group whose sequence number matches the one you are being asked for. 4. Open the database. SVRMGR> ALTER DATABASE OPEN; B. WITH ORACLE 7.2 OR HIGHER 1. Mount the database. SVRMGR> STARTUP MOUNT; 2. Find out which datafiles were in hot backup mode when the database crashed or was shutdown abort or the machine was rebooted by running the query: SVRMGR> SELECT V1.FILE#, NAME FROM V$BACKUP V1, V$DATAFILE V2 WHERE V1.STATUS = 'ACTIVE' AND V1.FILE# = V2.FILE# ; 3. For each of the files returned by the above query, issue the command: SVRMGR> ALTER DATABASE DATAFILE '' END BACKUP; 4. Open the database. SVRMGR> ALTER DATABASE OPEN; II. AT STARTUP AFTER RESTORING A DATAFILE OR TABLESPACE FROM A BACKUP ********************************************************************* A. WITH THE DATABASE IN ARCHIVELOG MODE 1. Mount the database. SVRMGR> STARTUP MOUNT; 2. Recover the datafile: SVRMGR> RECOVER DATAFILE ''; If recovering more than one datafile in a tablepace issue a SVRMGR> RECOVER TABLESPACE; If recovering more than one tablespace issue a SVRMGR> RECOVER DATABASE; 3. Confirm each of the archived logs that you are prompted for until you receive the message "Media recovery complete". If you are prompted for an archived log that does not exist, Oracle probably needs one or more of the online logs to proceed with the recovery. Compare the sequence number referenced in the ORA-280 message with the sequence numbers of your online logs. Then enter the full path name of one of the members of the redo group whose sequence number matches the one you are being asked for. 4. Open the database. SVRMGR> ALTER DATABASE OPEN; B. WITH THE DATABASE IN NOARCHIVELOG MODE In this case, you will only succeed in recovering the datafile or tablespace if the redo to be applied to it is within the range of your online logs. Issue the query: SVRMGR> SELECT FILE#, CHANGE# FROM V$RECOVER_FILE; Compare the change number you obtain with the FIRST_CHANGE# of your online logs. If the CHANGE# is GREATER than the minimum FIRST_CHANGE# of your logs, the datafile can be recovered. In this case, the procedure to be followed is analogous to that of scenario II.A above, except that you must always enter the appropriate online log when prompted, until recovery is finished. If the CHANGE# is LESS than the minimum FIRST_CHANGE# of your logs, the file cannot be recovered.Your options at this point include: - If the datafile is in a temporary or index tablespace, you may drop it with an ALTER DATABASE DATAFILE '' OFFLINE DROP statement and then open the database. Once the database is up, you must drop the tablespace to which the datafile belongs and recreate it. - If the datafile is in the SYSTEM or in a rollback tablespace, restore an up-to-date copy of the datafile (if available) or your most recent full backup.In case you do not have either of this, then it might not be possible to recover the database fully. For more details or to assist you in your decision, please contact Oracle Customer Support. For all other cases in this scenario, you must weigh the cost of going to a backup versus the cost of recreating the tablespace involved, as described in the two previous cases.For more details or to assist you in your decision, please contact Oracle Customer Support. III. TRYING TO ONLINE A DATAFILE OR TABLESPACE ********************************************** 1. Recover the datafile: SVRMGRL> RECOVER DATAFILE ''; If recovering a tablespace, do SVRMGRL> RECOVER TABLESPACE ; If recovering a database, do SVRMGRL> RECOVER DATABASE; 2. Confirm each of the archived logs that you are prompted for until you receive the message "Media recovery complete". If you are prompted for an archived log that does not exist, Oracle probably needs one or more of the online logs to proceed with the recovery. Compare the sequence number referenced in the ORA-280 message with the sequence numbers of your online logs. Then enter the full path name of one of the members of the redo group whose sequence number matches the one you are being asked for. 3. Open the database. SVRMGR> ALTER DATABASE OPEN; IV. WHEN RECOVERING ' USING BACKUP CONTROLFILE' OPTION TO DO INCOMPLETE RECOVERY ******************************************************************************* If the database is recovered with the "RECOVER DATABASE USING BACKUP CONTROLFILE;" option without specifying the "UNTIL CANCEL" option, then upon "ALTER DATABASE OPEN RESETLOGS;" you will encounter the ORA-1113 error. Steps to workaround this issue: 1. Recover database again using: SVRMGR> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL; 2. Cancel recovery by issuing the "CANCEL" command. 3. Open the database using: SVRMGR> ALTER DATABASE OPEN RESETLOGS; Notes that explain other possible recovery scenarios involving ORA-1113: ------------------------------------------------------------------------ Note 116374.1 -- "ORA-1113 on Datafile After Moving Datafile Using USFDMP Utility" ORA-1113 on Datafile After Moving Datafile Using USFDMP Note 1079626.6 -- "VMS: Mount Phase of Database Startup Results in ORA-01113, ORA-01186 & ORA-01122" ORA-1113 due to datafile getting locked on OpenVMS Note 1020262.102 -- "ORA-01113, ORA-01110: TRYING TO STARTUP DATABASE AFTER INCOMPLETE RECOVERY" Another scenario of ORA-1113 Note 168115.1 -- "ORA-01113 ORA-01110 on Database Startup after Write Disk failure" Datafile header contains different SCN comparing to other database files due to a write disk failure Note 146039.1 -- "Database Startup Fails with ORA-01113, ORA-01110" Dropping the datafile while ORA-1113, if the datafile is not required Some usefull queries: set pagesize 20000 set linesize 1000 set pause off set serveroutput on set feedback on set echo on set numformat 999999999999999 Spool recover.lst show parameter pfile; archive log list; select * from v$backup; select file#, status, substr(name, 1, 70) from v$datafile; select distinct checkpoint_change# from v$datafile_header; select status,resetlogs_change#,resetlogs_time,checkpoint_change#, to_char(checkpoint_time, 'DD-MON-YYYY HH24:MI:SS') as checkpoint_time,count(*) from v$datafile_header group by status, resetlogs_change#, resetlogs_time, checkpoint_change#, checkpoint_time order by status, checkpoint_change#, checkpoint_time ; select substr(name,1,60), recover, fuzzy, checkpoint_change#, resetlogs_change#, resetlogs_time from v$datafile_header; select name, open_mode, checkpoint_change#, ARCHIVE_CHANGE# from v$database; select GROUP#,THREAD#,SEQUENCE#,MEMBERS,ARCHIVED,STATUS,FIRST_CHANGE# from v$log; select GROUP#,substr(member,1,60) from v$logfile; select * from v$log_history; select * from v$recover_file; select * from v$recovery_log; select HXFIL File_num,substr(HXFNM,1,70) File_name,FHTYP Type,HXERR Validity, FHSCN SCN, FHTNM TABLESPACE_NAME,FHSTA status ,FHRBA_SEQ Sequence from X$KCVFH; select hxfil FileNo,FHSTA status from x$kcvfhall; spool off ======================================================================= Notes Related to ORA-00313 ORA-00313 messages: ======================================================================= ORA-312 ORA-313 ------ Note: ------ ORA-00313 ,ORA-00312 open failed for members of log group Error Description: --------------------------- Whenever you start your database you returned by the following message, ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata2/data1/dbase/redo02.log' Cause of The problem: ----------------------------- Your database was in archive log file, you shutdown your database and whenever you start it up either your redo log file is deleted or it is corrupted (if you overwrite or truncate the file). In this case you had 1 redo log member on each group. Solution of The problem: -------------------------------- It is not possible to recover missing redo log file. In order to solve the problem do the following. A)Mount the database. SQL>STARTUP MOUNT Database mounted. B)Check the status of the logile to see whether it is current. Here it is, SQL> SELECT STATUS FROM V$LOG WHERE GROUP#=2; STATUS ---------------- CURRENT i)If the status did not CURRENT then simply drop the log file by, SQL>ALTER DATABASE DROP LOGFILE GROUP 2; If there are only 2 log groups then it will be necessary to add another group before dropping this one. So, before dropping do, SQL>ALTER DATABASE ADD LOGFILE GROUP 4 '/oradata2/redo3.log' SIZE 10M; ii)If/As the status is CURRENT then simply perform fake recovery and then open resetlogs. SQL>RECOVER DATABASE UNTIL CANCEL; and print CANCEL. SQL>ALTER DATABASE OPEN RESETLOGS; ------ Note: ------ Subject: Loss Of Online Redo Log And ORA-312 And ORA-313 Doc ID: 117481.1 Type: BULLETIN Modified Date : 04-AUG-2008 Status: PUBLISHED Scenario -------- You have a database in archive log mode, shutdown immediate and deleted one of the online redo logs, in this case there are only 2 groups with 1 log member in each. When you try to open the database you receive the following errors: ora-313 open failed for memebers of log group 2 of thread 1. ora-312 online log 2 thread 1 'filename' It is not possible to recover the missing log, so the following needs to be performed - Mount the database and check v$log to see if the deleted log is current; -If the log is not current, simply drop the log group (alter database drop logfile group N). If there are only 2 log groups then it will be necessary to add another group before dropping this one. -If the log is current they should simply perform fake recovery and then open resetlogs connect internal startup mount recover database until cancel; (cancel immediately) alter database open resetlogs; The database will open up as required, providing the log file directory is available. If not available then create it and rerun the resetlogs. This will give error ora-344 unable to recreate online log search words ------------ lost online redo ora-312 ora-313 Recovering After the Loss of Online Redo Log Files: Scenarios ============================================================= If a media failure has affected the online redo logs of a database, then the appropriate recovery procedure depends on the following: The configuration of the online redo log: mirrored or non-mirrored The type of media failure: temporary or permanent The types of online redo log files affected by the media failure: current, active, unarchived, or inactive 1) Recovering After Losing a Member of a Multiplexed Online Redo Log Group --------------------------------------------------------------------------- If the online redo log of a database is multiplexed, and if at least one member of each online redo log group is not affected by the media failure, then the database continues functioning as normal, but error messages are written to the log writer trace file and the alert_SID.log of the database. ACTION PLAN ============= If the hardware problem is temporary, then correct it. The log writer process accesses the previously unavailable online redo log files as if the problem never existed. If the hardware problem is permanent, then drop the damaged member and add a new member by using the following procedure. To replace a damaged member of a redo log group: =============================================== Locate the filename of the damaged member in V$LOGFILE. The status is INVALID if the file is inaccessible: SQL> SELECT GROUP#, STATUS, MEMBER FROM V$LOGFILE WHERE STATUS='INVALID'; GROUP# STATUS MEMBER ------- ----------- --------------------- 0002 INVALID /oracle/oradata/trgt/redo02.log ++ Drop the damaged member. For example, to drop member redo01.log from group 2, issue: SQL > ALTER DATABASE DROP LOGFILE MEMBER '/oracle/oradata/trgt/redo02.log'; ++ Add a new member to the group. For example, to add redo02.log to group 2, issue: SQL> ALTER DATABASE ADD LOGFILE MEMBER '/oracle/oradata/trgt/redo02b.log' TO GROUP 2; If the file you want to add already exists, then it must be the same size as the other group members, and you must specify REUSE. For example: SQL > ALTER DATABASE ADD LOGFILE MEMBER '/oracle/oradata/trgt/redo02b.log' REUSE TO GROUP 2; 2) Losing an Inactive Online Redo Log Group =========================================== If all members of an online redo log group with INACTIVE status are damaged, then the procedure depends on whether you can fix the media problem that damaged the inactive redo log group. If the failure is . . Temporary... then Fix the problem. LGWR can reuse the redo log group when required. If the failure is ... Permanent then the damaged inactive online redo log group eventually halts normal database operation. ACTION PLAN ============ Reinitialize the damaged group manually by issuing the ALTER DATABASE CLEAR LOGFILE You can clear an inactive redo log group when the database is open or closed. The procedure depends on whether the damaged group has been archived. To clear an inactive, online redo log group that has been archived: -------------------------------------------------------------------- If the database is shut down, then start a new instance and mount the database: STARTUP MOUNT Reinitialize the damaged log group. For example, to clear redo log group 2, issue the following statement: ALTER DATABASE CLEAR LOGFILE GROUP 2; Clearing Inactive, Not-Yet-Archived Redo ======================================== Clearing a not-yet-archived redo log allows it to be reused without archiving it. This action makes backups unusable if they were started before the last change in the log, unless the file was taken offline prior to the first change in the log. Hence, if you need the cleared log file for recovery of a backup, then you cannot recover that backup. Also, it prevents complete recovery from backups due to the missing log. To clear an inactive, online redo log group that has not been archived: If the database is shut down, then start a new instance and mount the database: STARTUP MOUNT Clear the log using the UNARCHIVED keyword. For example, to clear log group 2, issue: ALTER DATABASE CLEAR LOGFILE UNARCHIVED GROUP 2; If there is an offline datafile that requires the cleared log to bring it online, then the keywords UNRECOVERABLE DATAFILE are required. The datafile and its entire tablespace have to be dropped because the redo necessary to bring it online is being cleared, and there is no copy of it. For example, enter: ALTER DATABASE CLEAR LOGFILE UNARCHIVED GROUP 2 UNRECOVERABLE DATAFILE; Immediately back up the whole database with an operating system utility, so that you have a backup you can use for complete recovery without relying on the cleared log group. For example, enter: % cp /disk1/oracle/dbs/*.f /disk2/backup Back up the database's control file with the ALTER DATABASE statement. For example, enter: ALTER DATABASE BACKUP CONTROLFILE TO '/oracle/dbs/cf_backup.f'; Failure of CLEAR LOGFILE Operation ---------------------------------------- The ALTER DATABASE CLEAR LOGFILE statement can fail with an I/O error due to media failure when it is not possible to: * Relocate the redo log file onto alternative media by re-creating it under the currently configured redo log filename * Reuse the currently configured log filename to re-create the redo log file because the name itself is invalid or unusable (for example, due to media failure) In these cases, the ALTER DATABASE CLEAR LOGFILE statement (before receiving the I/O error) would have successfully informed the control file that the log was being cleared and did not require archiving. The I/O error occurred at the step in which the CLEAR LOGFILE statement attempts to create the new redo log file and write zeros to it. This fact is reflected in V$LOG.CLEARING_CURRENT. ------ Note: ------ Subject: ORA-00313 at Startup After a New Redo Log Memeber is Added Doc ID: 1005110.6 Type: PROBLEM Modified Date : 02-JUL-2007 Status: PUBLISHED Problem Description: ==================== A new redo log member is added to the database. However, if a shutdown and a subsequent startup is issued BEFORE the status of the log member as per V$LOGFILE goes from 'INVALID' (which is expected) to blank entry (i.e., 'IN USE'), you get an ORA-00313 and a trace file is generated. This scenario takes place after adding a redo log member to the database. For example: SQLDBA> ALTER DATABASE ADD LOGFILE MEMBER '' TO GROUP ; If you shutdown the database before the new member is used at the next startup, then an ORA-00313 is written to the alert.log file and a trace file (filename 'lgwr_xxxxx.trc') is also dumped. For the command above, such a trace file shows the following: *** SESSION ID:(3.1) ORA-00313: open failed for members of log group 1 of thread 1 The entire database, however, is still working just fine. Solution Description: ===================== This error message is meant to have useful information reported at startup. Since the new log member is still labeled as 'INVALID', it still does not have all file headers properly initialized, hence its contents cannot be trusted for recovery of any kind. However, once a log switch operation switches into the redo log group, the new redo log member will be then initialized and ready to write redo entries copied from the log buffer. What Development should have done was to just warn the DBA in the alert.log file. A trace file (lgwr_xxxxx.trc) is really not necessary. To accomplish this, however, Development has to come up with a new routine that only dumps warning messages of this nature to the alert.log file and NOT to the trace file. ------ Note: ------ Subject: STARTING DATABASE, GETS ERROR, ORA-313. Doc ID: 1006148.6 Type: PROBLEM Modified Date : 20-JAN-2009 Status: PUBLISHED Problem Description: ==================== Database gives ORA-313 upon startup. ORA-00313: cannot open online '%s' (log #^ %s, log sequence # %s) Cause: The online log cannot be opened. Action: Restore online log. Solution Description: ===================== The Tape backup software had locked the logfile so Oracle could not update it. Everything worked fine once the tape backup job was terminated. Explanation: ============ The online logs are opened by the database at the time of startup. If these online logs are not available (maybe they have been deleted by mistake) or have been locked by a process, the above error will occur. The solution is to find out why they are not available and make them available. In this particular case, the tape backup software had locked the logfile. Terminating the tape backup job removed the lock on the online log files and made them available to oracle. Note: The online redo logfiles is another name for redo logfiles. ------ Note: ------ Subject: ORA-1157 ORA-1110 ORA-312 ORA-313 ORA-202 ORA-27086 Doc ID: 365560.1 Type: PROBLEM Modified Date : 06-NOV-2008 Status: MODERATED In this Document Symptoms Cause Solution Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.2 This problem can occur on any platform. Symptoms You are receiving the following errors: Wed Nov 30 15:43:26 2005 Errors in file /oracle/dsprdb01_orabin/admin/dsprdb01/bdump/dsprdb01_dbw0_19375.trc: +RA-01157: cannot identify/lock data file 2 - see DBWR trace file +RA-01110: data file 2: '/oracle/dsprdb01_index/sub_rule_bal_tran_indexes_02.dbf' +RA-27086: skgfglk: unable to lock file - already in use SVR4 Error: 11: Resource temporarily unavailable Additional information: 8 . . Errors in file /oracle/dsprdb01_orabin/admin/dsprdb01/bdump/dsprdb01_lgwr_19377.trc: +RA-00313: open failed for members of log group 3 of thread 1 +RA-00312: online log 3 thread 1: '/oracle/dsprdb01_redo_B/redo03B.log' +RA-27086: skgfglk: unable to lock file - already in use SVR4 Error: 11: Resource temporarily unavailable Additional information: 8 +RA-00312: online log 3 thread 1: '/oracle/dsprdb01_redo_A/redo03A.log' +RA-27086: skgfglk: unable to lock file - already in use SVR4 Error: 11: Resource temporarily unavailable Additional information: 8 . . ALTER DATABASE MOUNT Wed Nov 30 16:10:19 2005 +RA-00202: controlfile: '/oracle/dsprdb01_redo_A/control01.ctl' +RA-27086: skgfglk: unable to lock file - already in use SVR4 Error: 11: Resource temporarily unavailable Additional information: 8 Cause Host name was changed which caused locking confusion between Oracle and the OS. If the netapp gets a fully qualified hostname from dns, then the machine's hostname must be fully qualified as well. E.g. Don't set the hostname to ca-test90(returned by uname -n) , if the dns lookup returns ca-test90.us.oracle.com , otherwise lock recovery on the netapp will not work which will cause locking problems and the above errors to be reported. Solution Change the hostname so that hostname,as seen by uname -n, is same as the hostname returned by DNS to Netapps. ------ Note: ------ Subject: ORA-313 Received Intermittently Doc ID: 210886.1 Type: PROBLEM Modified Date : 09-OCT-2002 Status: PUBLISHED Fact(s) ~~~~~~~ The OS is windows NT/2000. The errors generally appear intermittently. There are no hardware issues. (i.e. harddisk is healthy) Symptom(s) ~~~~~~~~~~ Following set of errors are recieved in the logwriter trace file: ORA-00321: log 11 of thread 1, cannot update log file header ORA-00312: online log 11 thread 1: 'U:\ORACLE\P01\MIRRLOGA\LOG_G11M2.DBF' ORA-27091: skgfqio: unable to queue I/O OSD-04008: WriteFile() failure, unable to write to file O/S-Error: (OS 5) Access is denied. ORA-00313: open failed for members of log group 11 of thread 1 Cause ~~~~~ There is some 3rd party software that has acquired locks on the failing redolog member group file. This is generally caused by some backup utility or antivirus software that has acquired locks on the failing log member. Solution(s) ~~~~~~~~~~~ Disable the file locking in the backup and antivirus software. -or- Disable backup and scanning of Oracle datafiles. For more information, please consult your system administrator to find the exact application holding locks on the failing redolog file members. ======================================================================= Notes Related to other ORA- error messages: ======================================================================= ORA-00257: archiver error: ========================== Most of the time, it's due that the maximum in the flash recovery area is reached, or db_recovery_file_dest_size . Solution: increase flash recovery area, or delete old backups. ORA-00604: ========== 00604 - 604 -------- Note 1: -------- ORA-00604: error occurred at recursive SQL level string ORA-00604: error occurred at recursive SQL level string Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables). Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support. ORA-00604 error can occur in so many different contexts. The following is one such scenario Connecting as DB User gives ORA-00604, ORA-01986: OPTIMIZER_GOAL is Obsolete and ORA-6512 Errors This error applies to Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.3 This problem can occur on any platform When you try to log-in to the database as a particular user, you get disconnected with the error : ORA-01986 SQL> conn dvamin/dvamin ERROR: ORA-00604: error occurred at recursive SQL level 1 ORA-01986: OPTIMIZER_GOAL is obsolete ORA-06512: at line 2 Warning: You are no longer connected to ORACLE. You check the init.ora / spfile and verify that you haven't set any parameter : OPTIMIZER_GOAL still the database login errors out indicating that OPTIMIZER_GOAL is obsolete. In the alert.log, you find : Errors in file $ORACLE_BASE/admin/hrupg/udump/_ora_.trc: ORA-00604: error occurred at recursive SQL level 1 ORA-01986: OPTIMIZER_GOAL is obsolete ORA-06512: at line 2 Why this error is occurring ? Troubleshoot Please check the tracefile : $ORACLE_BASE/admin/hrupg/udump/_ora_.trc This shows : ----------------------------------------------------------------------------------------------------------- *** SERVICE NAME:(SYS$USERS) 2006-11-21 08:20:41.909 *** SESSION ID:(104.17) 2006-11-21 08:20:41.909 Error in executing triggers on connect internal *** 2006-11-21 08:20:41.911 ksedmp: internal or fatal error ORA-00604: error occurred at recursive SQL level 1 ORA-01986: OPTIMIZER_GOAL is obsolete ORA-06512: at line 2 ----------------------------------------------------------------------------------------------------------- You have configured some Database Login Triggers. These triggers are trying to set a parameter that is obsolete in 10.2 Hence errors. You might have configured a login trigger of the type : ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CREATE OR REPLACE TRIGGER LoginTrigger AFTER LOGON ON xxxxxx.SCHEMA BEGIN execute immediate 'alter session set OPTIMIZER_GOAL=FIRST_ROWS'; ... ... END; / ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SIMPLE TEST-CASE : +++++++++++++++++++++++++++++++++++++++++++++++++++++ ############################################################# SQL> create user dvamin identified by dvamin quota 5M on users; User created. SQL> grant connect to dvamin; Grant succeeded. SQL> CREATE OR REPLACE TRIGGER LoginTrigger AFTER LOGON ON dvamin.schema 2 BEGIN 3 execute immediate 4 'alter session set OPTIMIZER_GOAL=FIRST_ROWS'; 5 END; 6 / Trigger created. SQL> conn dvamin/dvamin ERROR: ORA-00604: error occurred at recursive SQL level 1 ORA-01986: OPTIMIZER_GOAL is obsolete ORA-06512: at line 2 Warning: You are no longer connected to ORACLE. ############################################################# What is the Solution? (i) Log-in as a user with ADMINISTER DATABASE TRIGGER privilege (ii) Drop this trigger. (iii) Log in as the required user successfully. SQL> conn / as sysdba Connected. SQL> drop trigger LoginTrigger; Trigger dropped. SQL> conn dvamin/dvamin Connected. Rewrite the trigger as necessary if required. Please refer to the Oracle Administrator's Guide 10g as available in OTN if needed. --------- Note 2: --------- Check if invalid packages of SYS are present. If so: re-compiling all package using SYS. Running this repeatedly until invalid packages no longer show, should clear up any issues throwing ORA-00604. -------- Note 3: -------- Hi, I have the following problem: SQL> select * from t; select * from t * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 1 ORA-04092: cannot COMMIT in a trigger ORA-06512: at line 12 ORA-00942: table or view does not exist And table `t' does not exist. But this happens no matter what user I am, no matter what I do but only if there are errors (assuming that it would normally give only the last error). I was looking for the trigger that might do commit but there is no single one in any schemas in our database. What does this ORA-00604 mean? Does it have something to do with recursive SQL queries? Is this some kind of internal problem? How can I get rid of it? Thanx in advance, Piotr and we said... someone created an "after servererror" trigger and is committing in it. consider: ops$tkyte@ORA9I.WORLD> drop user a cascade; User dropped. ops$tkyte@ORA9I.WORLD> ops$tkyte@ORA9I.WORLD> grant create session to a identified by a; Grant succeeded. ops$tkyte@ORA9I.WORLD> ops$tkyte@ORA9I.WORLD> @connect a/a ops$tkyte@ORA9I.WORLD> set termout off a@ORA9I.WORLD> REM GET afiedt.buf NOLIST a@ORA9I.WORLD> set termout on a@ORA9I.WORLD> select * from t; select * from t * ERROR at line 1: ORA-00942: table or view does not exist a@ORA9I.WORLD> a@ORA9I.WORLD> @connect / a@ORA9I.WORLD> set termout off ops$tkyte@ORA9I.WORLD> REM GET afiedt.buf NOLIST ops$tkyte@ORA9I.WORLD> set termout on ops$tkyte@ORA9I.WORLD> drop table log; Table dropped. ops$tkyte@ORA9I.WORLD> create table log( msg varchar2(255) ); Table created. ops$tkyte@ORA9I.WORLD> ops$tkyte@ORA9I.WORLD> create or replace trigger error_trigger 2 after servererror on database 3 begin 4 insert into log values ( 'hi' ); 5 commit; 6 end; 7 / Trigger created. ops$tkyte@ORA9I.WORLD> ops$tkyte@ORA9I.WORLD> @connect a/a ops$tkyte@ORA9I.WORLD> set termout off a@ORA9I.WORLD> REM GET afiedt.buf NOLIST a@ORA9I.WORLD> set termout on a@ORA9I.WORLD> select * from t; select * from t * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 1 ORA-04092: cannot COMMIT in a trigger ORA-06512: at line 3 ORA-00942: table or view does not exist a@ORA9I.WORLD> a@ORA9I.WORLD> @connect / a@ORA9I.WORLD> set termout off ops$tkyte@ORA9I.WORLD> REM GET afiedt.buf NOLIST ops$tkyte@ORA9I.WORLD> set termout on ops$tkyte@ORA9I.WORLD> select owner, trigger_name 2 from dba_triggers 3 where trigger_type = 'AFTER EVENT'; OWNER TRIGGER_NAME ------------------------------ ------------------------------ SYS AURORA$SERVER$STARTUP OPS$TKYTE ERROR_TRIGGER ops$tkyte@ORA9I.WORLD> ops$tkyte@ORA9I.WORLD> drop trigger error_trigger; Trigger dropped. Use that last query to find the offending trigger and either make it an autonomous transaction so it can commit or remove the commit. ---------- Note 4: ---------- ORA-12705: ========== ----------- Note 1: ----------- On Windows, Verify your regional Settings in the Control Panel. In the "Regional Options" tab, select English(United States). We had two machines with that problems and changing that setting solved. ----------- Note 2: ----------- ORA-12705 invalid or unknown NLS parameter value specified Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set. Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable ---------- Note 3: ---------- Windows - The NLS_LANG must be unset in the Windows registry (re-named is best). Look for the NLS_LANG subkey in the registry at \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE, and rename it. We tried changing it to what I had in my registry: AMERICAN_AMERICA.WE8MSWIN1252 That didn't work. Tried renaming it as the article suggested, that didn't work. Finally, my colleague (without prompting from me), cleared the key (didn't delete, just blanked it)...and voila! Labels: obiee, ORA-12705, oradb ---------- Note 3: ---------- On unix, set the NLS_LANG variable to point to the right location. ----- Note: ----- Good article, describing how to deal with ORA-600 errors. Subject: How to Analyze Problems Related to Internal Errors (ORA-600) and Core Dumps (ORA-7445) using Metalink Doc ID: 260459.1 Type: TROUBLESHOOTING Modified Date : 05-SEP-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1 Information in this document applies to any platform. Goal How to Analyze Problems Related to Internal Errors (ORA-600) and Core Dumps (ORA-7445) ================================================================================= 1.1 Abstract ============ This document provides guidelines for customers to do an initial analysis of problems related to internal errors (ORA-600) and core dumps (ORA-7445) by using Metalink keyword searches. After finding a set of documents, either bug database entries or notes, these must be correlated to the specific circumstances to further narrow down the search results. Hints to do this are given. 1.2 Introduction ================= It is often the case that certain problems have been already discovered and are documented in Metalink notes and in published bug information. With the proper techniques it is often possible to narrow down to a particular bug that matches your problem and find documented workarounds or patch information. This document is mainly aimed at rediscovering bugs in Oracle code that cause internal errors or core dumps but it may be equally applicable to all kinds of problems that may be encountered. The following paragraphs aim at extracting the relevant keywords from the trace file to find the documents that are relevant to the specific error condition. It also tries to help in further narrowing down the list of relevant documents by correlating them to the specific circumstances of the error. Solution 2.1 ORA-00600: internal error code, arguments: [argument1] [argumentX] .... ========================================================================== The internal argument ORA-600 is raised within the Oracle kernel when an exceptional condition occurs. Inside the kernel code at various stages of processing, so called assertions are executed.These are certain conditions that must be true to be able to proceed. The assertions are internal health checks and guard over the integrity of memory and data of the instance and the database. When such an assertion fails, an ORA-600 error is raised with either a numeric or alphanumeric first argument and possibly more arguments depending on the particular error. Note that not all ORA-600 errors are necessary fatal errors causing the session to terminate; some are quite benign. Others however can be severe so they must always be carefully investigated. 2.1.1 The First Argument of the Internal Error ORA-600 ====================================================== The single most important piece of information is the first argument of the internal error, either numeric or alphanumeric; it uniquely identifies the specific module where it was raised and what assertion was failing. Always include this first argument in your keyword search when trying to rediscover known problems. 2.2 ORA-07445: exception encountered: core dump ============================================== A core dump is an exceptional condition similar to the internal error ORA-600, however, the big difference is that the kernel did not anticipate the error. Whereas in the case of the internal error the exceptional condition was discovered by an assertion which is a predefined check, the core dump happens because the operating system at some point aborts the process because it is doing a forbidden action such as trying to access an area of memory that does not belong to the process. This is why core dumps are often referred to as access violations. The term 'core dump' stems from a period when memory was stored with the use of magnetic cores, in computer terminology 'core' equates to 'memory'. A core dump means that the memory of the process was dumped in a file 'core' on the file system. 2.2.1 Identify the failing module ================================= It is important to know in which internal module the core dump occurs, this is often printed together with the error but not always. If not refer to the section 3.2.5 Call Stack Trace. If known include the failing module in your keyword search. 3.1 Trace files =============== For both internal errors and core dumps a trace file is written in either user_dump_dest for user processes and background_dump_dest for background processes. In 11g all trace files will be written to the location defined by the parameter diagnostic_dest. The trace files for both types are treated in the same manner although the particular information in the trace files, whether a certain section is present, may depend on the particular error. In case of a core dump it is possible for the kernel to still dump relevant information by calling the dump routines such as ksedmp() because the error is trapped by a signal handler. On the other hand, for most internal errors, the process is crashed (aborted) when the dump is ready. 3.2 Relevant sections in Trace files ==================================== While not intended to provide a detailed explanation or in depth understanding, the following sections in the trace file can usually be identified, this will help you to glean the relevant keywords for the search and understand the specific conditions under which the error occured, you should then be able to narrow down your search results. 3.2.1 Header ============ The header section includes such information as the name of the trace file, the specific oracle version, ORACLE_HOME ,system name, node name, OS version, instance name and process information. While not directly relevant for your keyword search this information is vital later to correlate the documents to your problem. 3.2.2 Error Section =================== The error as it was written in the alert.log is usually repeated, possibly along with some extra information dependent on the error. When an internal error occurs a developer may have decided to write some crucial state information apart from the ORA-600 arguments directly to the trace file. When this is the case, those are usually gems for your search. 3.2.3 Current SQL statement for this session ============================================ You may or may not know what was being conducted at the time of the error. While common keywords like 'insert', 'update' or 'delete' may not be beneficial to your search (they are simply too common) this is of course very useful to correlate documented rediscovery information to your problem. If for example a certain bug has in its rediscovery information that it happens on insert only and you are performing a delete statement, then it is safe to say that this bug is not your problem. See also 3.2.6 Cursor Dump in case the current SQL statement is not present in the trace file. 3.2.4 PL/SQL Call Stack ======================= This section is present if the session was performing PL/SQL- it shows what user or internal PL/SQL packages where called. Call Stacks are read bottom up; if there are Oracle packages in there include them in your keyword search. 3.2.5 Call Stack Trace ====================== The modules listed in the call stack trace provide excellent keywords that can be used for rediscovery; they usually uniquely identify specific bugs. However, care must be taken to discard the top and bottom modules. Modules such as the following must be ignored : sigacthandler(), ssexhd(), ksedmp(), ksesicX() (where X is a number that designates the number of extra arguments to an ora-600 besides the first). All kse* and kge* modules in general can be ignored, they stand for Kernel Service Error and Kernel Generic Error respectively; these are modules that are invoked AFTER the error has occurred and perform such tasks as dumping the trace file and as such are common to most internal errors and core dumps so will not help in narrowing down your search. The same goes for the bottom modules that are always present because they are used to initiate process startup; everyting below (and including) opiexe() can safely be ignored. When you include three or four relevant modules from the top of the call stack trace (together with some other relevant keywords), this will usually result in the relevant documents popping up on a Metalink search. If none are returned you may have to reduce the number of modules searched upon, removing the modules further down the stack from the search. If you still have no results returned you may have hit an as yet undiscovered problem. 3.2.6 Cursor Dump ================= Even when the current SQL statement is not listed in the top section of the trace file together with the error, the cursor dump can still reveal the SQL statement being performed at time of error. Simply search for 'current cursor' identify the cursor number and scroll down until you find the cursor with that number. A a bonus you may also be able to identify the bind variables (if any) used for the statement in this section. See Note 154170.1 for further information. 3.2.7 Process State - Session State Object ========================================== A process state is a list of the process state objects, it is beyond the scope of this document to explain these in detail, for now it is enough to understand that state objects are used to organize memory objects that contain the relevant state information of a session in an hierarchical manner. One of the state objects contains relevant session information that helps in narrowing down the specifics of the error condition. Simply search for 'program' in your trace file and you will find a section similar to the following : SO: 7000000223acfe0, type: 4, owner: 700000022357868, flag: INIT/-/-/0x00 (session) trans: 7000000230d47a0, creator: 700000022357868, flag: (18100041) USR/- BSY/-/-/-/-/- DID: 0001-0012-00000083, short-term DID: 0000-0000-00000000 txn branch: 0 oct: 2, prv: 0, sql: 70000002831a5a0, psql: 70000002831a5a0, user: 48/ISIS O/S info: user: someuser, term: SOMETTY01, ospid: 628:1948, machine: BOX\SOMETTY01 program: someprogram.exe application name: someprogram.exe, hash value=0 last wait for 'db file sequential read' blocking sess=0x0 seq=1054 wait_time=16729 file#=1, block#=2ec3, blocks=1 temporary object counter: 0 When a specific program is being used, you may want to include that in your keyword search, whether it is an oracle client program or not; we sometimes provide information on third party products in relation to Oracle on an 'as is' basis. Try to identify what type of program is being used, these include JDBC (thin or OCI), Pro*C, OCI etc. Some problems are for example specific to JDBC and this will help greatly in identifying the problem. 4.1 Use 'Advanced Search' ========================= To find relevant bug database entries (more likely to contain call stack trace modules) always perform the Advanced search and make sure to check the 'Bug Database' check box from the 'sources' section on the right of the page, in addition to the 'Knowledge Base' which consists of the Notes written by Oracle personnel. Uncheck the 'Technical Forum' checkbox at first; when nothing is found in the knowlege base and bug database, some relevant info maybe found in the forums (this is not to downplay the forums, they just have a different use). The tips on the advanced search page provide further guidelines on how to search efficiently. 4.2 General Comments on Keyword Searches ======================================== The important thing is trial and error. When a search returns an overwhelming mound of documents, try to narrow it down by including another keyword that is unique to your problem. On the other hand, when no results are returned, omit a few; if you have included too many modules from a call stack trace, delete some from your search but retain the topmost module(s); the specific module may have been called from a different one to your's when the bug was discovered or the call stack trace was not clearly documented in the bug. 4.3 No Relevant Bug or Document is Found ======================================== You may of course be the first customer to have hit an as yet undiscovered problem. In that case, file a service request using Metalink and try to describe in detail what the problem is. You may also include a summary of the analysis that you have already performed based on these guidelines. 4.4 Provide Feedback ==================== If you find documents that are unclear or you think contain errors, or if you think you can add some relevant information based on your experience using our products, please use the feedback button and state the document number and your comment (use the 'Technical Library feedback/questions' radio button in step 2). We are very grateful for quality feedback as it improves our knowledge base. 5.1 Correlate Bugs and Documents to Your Problem ================================================ Now that you have gained more understanding of the problem by browsing through the trace file's relevant sections and have identified sufficiently suitable keywords both in terms of quantity and quality (uniqueness) you have executed your search and you are presented with some relevant documents. The Notes are usually clear enough; they go through a well defined process of QA and will provide you with detailed circumstances to match your problem. Bugs can be more cumbersome to read; try scrolling down to the bottom immediately (click 'Go to End') to find the 'Rediscovery' or 'Release Note' section (or search for it) to match the bug description with your specifics. A closed published bug should have such a section unless it is a duplicate of another bug. In that case the base bug must be checked. For bugs resolved in 9.2 onwards there is often a summary note, with the reference .8, which is easier to read. You are hitting a certain bug if you can match all circumstances listed in the rediscovery information to your problem AND the designated fix (either a patch or workaround) solves the problem. 6.0 Summary =========== Good search keywords include error messages, first arguments of internal errors and relevant internal module names. Program names and type may help narrow down further. Correlate with the documented rediscovery information. If unsure, file a service request with your findings, this helps the analyst. References Note 153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool Note 154170.1 - How to find the offending SQL from a trace file Note 156657.1 - How To Find Known Issues or BUGs Through a MetaLink Search Note 1812.1 - TECH: Getting a Stack Trace from a CORE file Note 153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool Note 211909.1 - Customer Introduction to ORA-7445 Errors ----- Note: ----- Control file missing Example ORA-00202: controlfile: 'g:\oradata\airm\control03.ctl' ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) The system cannot find the file specified. Sat May 24 20:02:40 2003 ORA-205 signalled during: alter database airm mount... If the databse is down: - Unix: Is it really missing or is the filesystem(s) where they are placed, just not mounted? - Windows: are all filesystems "up" and the drive letters as they used to be? Possible Solution: just copy one good controlfile to the exact location of the missing one. Note this: if the "bad" controlfile seems to be at the "right" location, first make a copy of it, before you copy a "good" controlfile over the "bad" controlfile. Or follow you regular rman recovery procedure. ----- Note: ----- alter system disable distributed recovery ORA-2019 ORA-2058 ORA-2068 ORA-2050: FAILED DISTRIBUTED TRANSACTIONS for step by step instructions on how to proceed. The above errors indicates that there is a failed distributed transaction that needs to be manually cleaned up. See In some cases, the instance may crash before the solutions are implemented. If this is the case, issue an 'alter system disable distributed recovery' immediately after the database starts to allow the database to run without having reco terminate the instance. ----- Note: ----- SVRMGR> connect internal SVRMGR> startup mount SVRMGR> SELECT df.name,bk.time FROM v$datafile df,v$backup bk 2> WHERE df.file# = bk.file# and bk.status = 'ACTIVE'; Shows the datafiles currently in a hot backup state. SVRMGR> alter database datafile 2> '/u03/oradata/PROD/devlPROD_1.dbf' end backup; Do an "end backup" on those listed hot backup datafiles. SVRMGR> alter database open; ----- Note: ----- Subject: ORA-600 [4147] Experienced When Performing Query From FLASHBACK_TRANSACTION_QUERY Doc ID: 467144.1 Type: PROBLEM Modified Date : 13-MAY-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.2.0 This problem can occur on any platform. Symptoms While attempting to perform queries against the flashback_transaction_query table, an ORA-600 [4147] is experienced. Example: --------------- select * from flashback_transaction_query where start_timestamp > sysdate -1/6 ORA-00600: internal error code, arguments: [4147], [6], [5] Stack trace is similar to the following: ---------------------------------------- ksedst ksedmp ksfdmp kgeriv kgesiv ksesic2 kturef kcbgtcr ktuq_get_urec ktuqup_get_startslo ktuqup_init ktuqqp_init ktuqfcbk qerfxFetch opifch2 opifch opiodr ttcpip opitsk opiino opiodr opidrv sou2o opimai_real main Cause This is unpublished Bug 5726687. This is a non-corruptive issue that occurs during the query in flashback because the query is being performed against the undo blocks while the transaction id is most likely in memory. This is why the ORA-600 [4147] error is generated as the block scn's do not match. This bug is fixed in 11g, however, it can be back-ported to 10.2.0.3. Solution To implement the solution, please execute the following steps: Apply Patch 5726687. If you'd like to check for Patch Availability from Metalink 1) Click on Patches & Updates 2) Click on Simple Search 3) Enter patch number: 5726687 4) Select your O/S 5) Click Go. ----- Note: ----- Subject: Database Crashes With ORA-07445 [kgldtin:xxxx[kgl.c] [SIGSEGV] [Address not mapped to object] Doc ID: 551885.1 Type: PROBLEM Modified Date : 12-MAY-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.6 to 10.2.0.1 This problem can occur on any platform. Symptoms The database crashes after the following errors: ORA-07445: exception encountered: core dump [kgldtin:7285[kgl.c]] [SIGSEGV] [Address not mapped to object] [0x000000000] [] [] ORA-07445: exception encountered: core dump [kglobcl:2690[kgl2.c]] [SIGSEGV] [Address not mapped to object] [0x000000000] [] [] The call stack will look similar to the following: kgldtin kgldti kkdlgob qcsfgob qcsprfro qcspqb kkmdrv opiSem opiprs kksald rpiswu2 kkslod kglobld kglobpn kglpim kglpin kksfbc kkspsc0 opiosq0 . . . The PROCESS STATE section in the tracefile may show a latch is being held. For example: holding 455b66948 Child library cache level=5 child#=1 Location from where latch is held: kgldti: 2child: Context saved from call: 0 state=busy Changes This problem is introduced in 9.2.0.6 by the fix for unpublished Bug 3749490. Any database with a one-off or merge patch containing the fix for unpublished Bug 3749490 can be affected. Cause The problem is caused by unpublished Bug 3949307 " SGA memory corruption / OERI:KGHALO4 with high concurrency," which is fixed in the 9.2.0.7 patchset. Solution The following solutions are available: 1. Upgrade to 11g, when released for your platform. 2. Upgrade to 10gR2/ 3. For 10gR1, apply a patchset on top of 10.1.0.2 10.1.0.5 recommended). 4. Apply one-off Patch 3949307 if available for your RDBMS version and OS platform. References Keywords KGLOBCL; KGLDTIN; ----- Note: ----- Database does not start (1) SGADEF.DBF LK.DBF -------------------------------------------------- Note:1034037.6 Subject: ORA-01102: WHEN STARTING THE DATABASE Type: PROBLEM Status: PUBLISHED Content Type: TEXT/PLAIN Creation Date: 25-JUL-1997 Last Revision Date: 10-FEB-2000 Problem Description: ==================== You are trying to startup the database and you receive the following error: ORA-01102: cannot mount database in EXCLUSIVE mode Cause: Some other instance has the database mounted exclusive or shared. Action: Shutdown other instance or mount in a compatible mode. or scumnt: failed to lock /opt/oracle/product/8.0.6/dbs/lkSALES Fri Sep 13 14:29:19 2002 ORA-09968: scumnt: unable to lock file SVR4 Error: 11: Resource temporarily unavailable Fri Sep 13 14:29:19 2002 ORA-1102 signalled during: alter database mount... Fri Sep 13 14:35:20 2002 Shutting down instance (abort) Problem Explanation: ==================== A database is started in EXCLUSIVE mode by default. Therefore, the ORA-01102 error is misleading and may have occurred due to one of the following reasons: - there is still an "sgadef.dbf" file in the "ORACLE_HOME/dbs" directory - the processes for Oracle (pmon, smon, lgwr and dbwr) still exist - shared memory segments and semaphores still exist even though the database has been shutdown - there is a "ORACLE_HOME/dbs/lk" file Search Words: ============= ORA-1102, crash, immediate, abort, fail, fails, migration Solution Description: ===================== Verify that the database was shutdown cleanly by doing the following: 1. Verify that there is not a "sgadef.dbf" file in the directory "ORACLE_HOME/dbs". % ls $ORACLE_HOME/dbs/sgadef.dbf If this file does exist, remove it. % rm $ORACLE_HOME/dbs/sgadef.dbf 2. Verify that there are no background processes owned by "oracle" % ps -ef | grep ora_ | grep $ORACLE_SID If background processes exist, remove them by using the Unix command "kill". For example: % kill -9 3. Verify that no shared memory segments and semaphores that are owned by "oracle" still exist % ipcs -b If there are shared memory segments and semaphores owned by "oracle", remove the shared memory segments % ipcrm -m and remove the semaphores % ipcrm -s NOTE: The example shown above assumes that you only have one database on this machine. If you have more than one database, you will need to shutdown all other databases before proceeding with Step 4. 4. Verify that the "$ORACLE_HOME/dbs/lk" file does not exist 5. Startup the instance Solution Explanation: ===================== The "lk" and "sgadef.dbf" files are used for locking shared memory. It seems that even though no memory is allocated, Oracle thinks memory is still locked. By removing the "sgadef" and "lk" files you remove any knowledge oracle has of shared memory that is in use. Now the database can start. . ----- Note: ----- Note:1013221.6 Subject: RECOVERING FROM A LOST DATAFILE IN A ROLLBACK TABLESPACE Type: PROBLEM Status: PUBLISHED Content Type: TEXT/PLAIN Creation Date: 16-OCT-1995 Last Revision Date: 18-JUN-2002 Solution 1: --------------- Error scenario: 1. set transaction use rollback segment rb1; 2. INSERTS into's... 3. SHUTDOWN ABORT; (simulate Media errors) 4. Delete file rb1.ora (Tablespace RB1 with segment rb1 ); 5. Restore a backup of the file Recover: 1. comment out INIT.ORA ROLLBACK_SEGMENT parameter , so ORACLE does not try to find the incorrect segment rb1 2. STARTUP MOUNT 3. ALTER DATABASE DATAFILE 'rb1.ora' OFFLINE; 4. ALTER DATABASE OPEN # now we are in business 5. CREATE ROLLBACK SEGMENT rbtemp TABLESPACE SYSTEM; # We need Temporary RBS for further steps; 6. ALTER ROLLBACK SEGMENT rbtemp ONLINE; 7. RECOVER TABLESPACE RB1; 8. ALTER TABLESPACE RB1 ONLINE; 9. ALTER ROLLBACK SEGMENT rb1 ONLINE; 10. ALTER ROLLBACK SEGMENT rbtemp OFFLINE; 11. DROP ROLLBACK SEGMENT rbtemp; Result: Successfully rollback uncommitted Transactions, no suspect instance. Solution 2: --------------- INTRODUCTION ------------ Rollback segments can be monitored through the data dictionary view, dba_rollback_segs. There is a status column that describes what state the rollback segment is currently in. Normal states are either online or offline. Occasionally, the status of "needs recovery" will appear. When a rollback segment is in this state, bringing the rollback segment offline or online either through the alter rollback segment command or removing it FROM the rollback_segments parameter in the init.ora usually has no effect. UNDERSTANDING ------------- A rollback segment falls into this status of needs recovery whenever Oracle tries to roll back an uncommitted transaction in its transaction table and fails. Here are some examples of why a transaction may need to rollback: 1-A user may do a dml transaction and decides to issue rollback 2-A shutdown abort occurs and the database needs to do an instance recovery in which case, Oracle has to roll back all uncommitted transactions. When a rollback of a transaction occurs, undo must be applied to the data block the modified row/s are in. If for whatever reason, that data block is unavailable, the undo cannot be applied. The result is a 'corrupted' rollback segment with the status of needs recovery. What could be some reasons a datablock is unaccessible for undo? 1-If a tablespace or a datafile is offline or missing. 2-If the object the datablock belongs to is corrupted. 3-If the datablock that is corrupt is actually in the rollback segment itself rather than the object. HOW TO RESOLVE IT ----------------- 1-MAKE sure that all tablespaces are online and all datafiles are online. This can be checked through v$datafile, under the status column. For tablespaces associated with the datafiles, look in dba_tablespaces. If that still does not resolve the problem then 2-PUT the following in the init.ora- event = "10015 trace name context forever, level 10" Setting this event will generate a trace file that will reveal the necessary information about the transaction Oracle is trying to roll back and most importantly, what object Oracle is trying to apply the undo to. 3-SHUTDOWN the database (if normal does not work, immediate, if that does not work, abort) and bring it back up. Note: An ora-1545 may be encountered, or other errors. If the database cannot startup, contact customer support at this point. 4-CHECK in the directory that is specified by the user_dump_dest parameter (in the init.ora or show parameter command) for a trace file that was generated at startup time. 5-IN the trace file, there should be a message similar to- error recovery tx(#,#) object #. TX(#,#) refers to transaction information. The object # is the same as the object_id in sys.dba_objects. 6-USE the following query to find out what object Oracle is trying to perform recovery on. SELECT owner, object_name, object_type, status FROM dba_objects WHERE object_id = ; 7-THIS object must be dropped so the undo can be released. An export or relying on a backup may be necessary to restore the object after the corrupted rollback segment goes away. 8-AFTER dropping the object, put the rollback segment back in the init.ora parameter rollback_segments, removed the event, and shutdown and startup the database. In most cases, the above steps will resolve the problematic rollback segment. If this still does not resolve the problem, it may be likely that the corruption is in the actual rollback segment. At this point, if the problem has not been resolved, please contact customer support. Solution 3: --------------- Recovery FROM the loss of a Rollback segment datafile containing active transactions How do I recover the datafile containing rollback segments having active transactions and if the backup is done with RMAN without using catalog. I have tried the case study FROM the Oracle recovery handbook,but when i tried to open the database after offlining the Rollback segment file I got the following errors ORA-00604: error occurred at recursive SQL level 2 ORA-00376: file 2 cannot be read at this time ORA-01110:data file 2: '/orabackup/CCD1prod/oradata/rbs01CCD1prod.dbf' the status of the datafile was "Recover". Anyhow shutting down and starup mounting the database allows for the database or the datafile recovery, but this was done through SVRMGRL. Here is whats happening. simulate the loss of datafile by removing FROM the os and shut down abort the database. mount the database so RMAN can restore the file, at this point offlining the file succeeds but you cannot open the database. so the question is can we offline a rollback segment datafile containing active transactions and open the database ? How to perform recovery in such case using an RMAN backup without using the catalog. I appreciate for any insight and tips into this issue. Madhukar FROM: Oracle, Tom Villane 01-May-02 21:04 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi, The only supported way to recover FROM the loss of a rollback segment datafile containing a rollback segment with a potentially active data dictionary transaction is to restore the datafile FROM backup and roll forward to a point in time prior to the loss of the datafile (assuming archivelog mode). Tom Villane Oracle Support Metalink Analyst FROM: Madhukar Yedulapuram 02-May-02 06:46 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi Tom, What does Rollforward upto a time prior to the loss of the datafile got to do with the recovery, are you suggesting this so that active transaction is not lost,is it possible ? Because during the recovery the rollforward is followed by rollback and all the active transactions FROM the rollback segment's transaction table will be rolled back isnt it ? My question is if I have a active transaction in a rollback segment and the file containing that rollback segment is lost and the database crashed or did a shutdown abort can we open the database after offlining the datafile and commenting out the rollback_segments parameter in the init.ora parameter, I tried to do it and got the errors which I mentioned earlier. So in this case I have to do offline recovery only or what ? Thanks, madhukar FROM: Oracle, Tom Villane 02-May-02 16:24 Subject: Re : Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi, You won't be able to open the database if you lose a rollback segment datafile that contains an active transaction. You will have to: Restore a good backup of the file RECOVER DATAFILE '' ALTER DATABASE DATAFILE '' ONLINE; The only way you would be able to open the database is if the status of the rollback were OFFLINE, any other status requires that you recover as noted before. As recovering FROM rollback corruption needs to be done properly, you may want to log an iTAR if you have additional questions. Regards Tom Villane Oracle Support Metalink Analyst FROM: Madhukar Yedulapuram 03-May-02 07:22 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi Tom, Thank you for the reply.you said that the only way the database can be opened is if the status of the rollback segment was offline,but what happens to an active transaction which was using this rollback segment, once the database is opened and the media recovery performed on the datafile,the database will show values which were part of an active transaction and not committed,isnt this the logical corruption? madhukar FROM: Madhukar Yedulapuram 05-May-02 08:14 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Tom, Can I get some reponse to my questions. Thank You, Madhukar FROM: Oracle, Tom Villane 07-May-02 13:53 Subject: Re : Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi, Sorry for the confusion, I should not have said "rolling forward to a point in time..." in my previous reply. No, there won't be corruption or inconsistency. The redo logs will contain the information for both committed and uncommitted transactions. Since this includes changes made to rollback segment blocks, it follows that rollback data is also (indirectly) recorded in the redo log. To recover FROM a loss of Datafiles in the SYSTEM tablespace or datafiles with active rollback segments. You must perform closed database recovery. -Shutdown the database -Restore the file FROM backup -Recover the datafile -Open the database. References: Oracle8i Backup and Recovery Guide, chapter 6 under "Losing Datafiles in ARCHIVELOG Mode ". Regards Tom Villane Oracle Support Metalink Analyst FROM: Madhukar Yedulapuram 07-May-02 22:23 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi Tom, After offlining the rollback segment containing active transaction you can open the database and do the recovery and after that any active transactions should be rolled back and the data should not show up, but I performed the following test and Oracle is showing logical corruption by showing data which was never committed. SVRMGR> create tablespace test_rbs datafile '/orabackup/CCD1prod/oradata/test_rbs01.dbf' size 10M 2> default storage (initial 1M next 1M minextents 1 maxextents 1024); Statement processed. SVRMGR> create rollback segment test_rbs tablespace test_rbs; Statement processed. SVRMGR> create table case5 (c1 number) tablespace tools; Statement processed. SVRMGR> set transaction use rollback segment test_rbs; ORA-01598: rollback segment 'TEST_RBS' is not online SVRMGR> alter rollback segment test_rbs online; Statement processed. SVRMGR> set transaction use rollback segment test_rbs; Statement processed. SVRMGR> insert into case5 values (5); 1 row processed. SVRMGR> alter rollback segment test_rbs offline; Statement processed. SVRMGR> shutdown abort ORACLE instance shut down. SVRMGR> startup mount ORACLE instance started. Total System Global Area 145981600 bytes Fixed Size 73888 bytes Variable Size 98705408 bytes Database Buffers 26214400 bytes Redo Buffers 20987904 bytes Database mounted. SVRMGR> alter database datafile '/orabackup/CCD1prod/oradata/test_rbs01.dbf' offline; Statement processed. SVRMGR> alter database open; Statement processed. SVRMGR> recover tablespace test_rbs; Media recovery complete. SVRMGR> alter tablespace test_rbs online; Statement processed. SVRMGR> SELECT * FROM case5; C1 ---------- 5 1 row SELECTed. SVRMGR> alter rollback segment test_rbs online; Statement processed. SVRMGR> SELECT * FROM case5; C1 ---------- 5 1 row SELECTed. SVRMGR> drop rollback segment test_rbs; drop rollback segment test_rbs * ORA-01545: rollback segment 'TEST_RBS' specified not available SVRMGR> SELECT segment_name,status FROM dba_rollback_segs; SEGMENT_NAME STATUS ------------------------------ ---------------- SYSTEM ONLINE R0 OFFLINE R01 OFFLINE R02 OFFLINE R03 OFFLINE R04 OFFLINE R05 OFFLINE R06 OFFLINE R07 OFFLINE R08 OFFLINE R09 OFFLINE R10 OFFLINE R11 OFFLINE R12 OFFLINE BIG_RB OFFLINE TEST_RBS ONLINE 16 rows SELECTed. SVRMGR> drop rollback segment test_rbs; drop rollback segment test_rbs * ORA-01545: rollback segment 'TEST_RBS' specified not available Here I have to bring the rollback segment offline to dropt it. Can this be explained or is this a bug,because this caused logical corruption. FROM: Oracle, Tom Villane 10-May-02 13:19 Subject: Re : Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi, What you are showing is expected and normal, and not corruption. At the time that you issue the "alter rollback segment test_rbs online;" Oracle does an implicit commit becuase any "ALTER" statement is considered DDL and Oracle issues an implicit COMMIT before and after any data definition language (DDL)statement. Regards Tom Villane Oracle Support Metalink Analyst -------------------------------------------------------------------------------- FROM: Madhukar Yedulapuram 14-May-02 20:12 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi Tom, So what you are saying is the moment I say Alter rollback segment RBS# online,oracle will issue an implicit commit,but if you look at my test just after performing the tablespace recovery (had only one datafile in the RBS tablespace which was offlined before opening the database and doing the recovery), I brought the tablespace online and did a SELECT FROM the table which was having the active transaction in one of the rollback segments,so this statement has issued an implicit commit and I could see the data which was never actually committed,doesnt this contradict the Oracle's stance that only that data will be shown which shown which is committed, I think this statement is true for Intance and Crash recovery,not for media recovery as the case in point proves,but still if you say Oracle issues an implicit commit,then the stance of oracle is consistent. madhukar FROM: Oracle, Tom Villane 15-May-02 18:30 Subject: Re : Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi, A slight correction to what I posted, I should have said the implicit commit happened when the rollback segment was altered offline. Whether it's an implicit commit (before and after a DDL statement like CREATE, DROP, RENAME, ALTER) or if the user did the commit, or if the user exits the application (forces a commit). All of the above are considered commits and the data will be saved. Regards Tom Villane Oracle Support Metalink Analyst FROM: Madhukar Yedulapuram 16-May-02 23:17 Subject: Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi Tom, Thank You very much,so the moment i brought the RBS offline,the transaction was committed and the data saved in the table,is that what you are saying. So the data was committed even before performing the recovery,so recovery is essentially not applying anything in this case. madhukar FROM: Oracle, Tom Villane 17-May-02 12:18 Subject: Re : Re : Recovery FROM the loss of a Rollback segment datafile containing active transactions Hi, Yes, that is what happened. Regards Tom Villane Oracle Support Metalink Analyst ----- Note: ----- After backup you increase a datafile. ------------------------------------------ problem 2: "the backed up datafile size is smaller, and Oracle won't accept it for recovery." isn't a problem because we most certainly will accept that file. As a test you can do this (i just did) o create a small 1m tablespace with a datafile. o alter it and begin backup. o copy the datafile o alter it and end backup. o alter the datafile and "autoextend on next 1m" it. o create a table with initial 2m initial extent. This will grow the datafile. o offline the tablespace o copy the 1m original file back. o try to online it -- it'll tell you the file that needs recovery (its already accepted the smaller file at this point) o alter database recover datafile 'that file'; o alter the tablespace online again -- all is well. As for the questions: 1) There is such a command -- "alter database create datafile". Here is an example I just ran through: tkyte@TKYTE816> alter tablespace t begin backup; Tablespace altered. I copied the single datafile that is in T at this point tkyte@TKYTE816> alter tablespace t end backup; Tablespace altered. tkyte@TKYTE816> alter tablespace t add datafile 'c:\temp\t2.dbf' size 1m; Tablespace altered. So, I added a datafile AFTER the backup... tkyte@TKYTE816> alter tablespace t offline; Tablespace altered. At this point, I went out and erased the two datafiles associated with T. I moved the copy of the one datafile in place... tkyte@TKYTE816> alter tablespace t online; alter tablespace t online * ERROR at line 1: ORA-01113: file 9 needs media recovery ORA-01110: data file 9: 'C:\TEMP\T.DBF' So, it sees the copy is out of sync... tkyte@TKYTE816> recover tablespace t; ORA-00283: recovery session canceled due to errors ORA-01157: cannot identify/lock data file 10 - see DBWR trace file ORA-01110: data file 10: 'C:\TEMP\T2.DBF' and now it tells of the missing datafile -- all we need do at this point is: tkyte@TKYTE816> alter database create datafile 'c:\temp\t2.dbf'; Database altered. tkyte@TKYTE816> recover tablespace t; Media recovery complete. tkyte@TKYTE816> alter tablespace t online; Tablespace altered. and we are back in business.... ----- Note: ----- Setting Trace Events -------------------- database level via init.ora EVENT="604 TRACE NAME ERRORSTACK FOREVER" EVENT="10210 TRACE NAME CONTEXT FOREVER, LEVEL 10" session level ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME BLOCKDUMP LEVEL 67109037'; ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME CONTROLF LEVEL 10'; system trace dump file ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME SYSTEMSTATE LEVEL 10'; ----- Note: ----- DROP TEMP DATAFILE If your database does not start because it cannot find file(s) belonging to the TEMP tablespace, you can easily recover. Example: SQL>startup mount SQL>alter database open; ora-01157 cannot identify datafile 4 - file not found ora-01110 data file 4 '/oradata/temp/temp.dbf' SQL>alter database datafile '/oradata/temp/temp.dbf' offline drop; SQL>alter database open; SQL>drop tablespace temp including contents; SQL>create tablespace temp datafile '.... ----- Note: ----- Strange processes=.. and database does not start ------------------------------------------------ Does the PROCESSES initialization parameter of init.ora depend on some other parameter ? We were getting the error as maximum no of process (50) exceeded..... The value was initially set to 50, so when the value was....changed to 200, and the database was restarted, it gave an error of "end-of-file on communication channel" The value was reduced to 150 & 100 and the same error was encountered.... when it was set back to 50, the database started.... Can anyone clear ? check out ur semaphore settings in /etc/system. try increasing seminfo_semmns ----- Note: ----- ORA-00600 I work with ORACLE DB ver.8.0.5 and recieved an error in alert.log ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [12700], [3383], [41957137], [44], [], [], [], [] oerr ora 600 00600, 00000, "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" Cause: This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition. Action: Report as a bug - the first argument is the internal error number Number [12700] indicates "invalid NLS parameter value (%s)" Cause: An invalid or unknown NLS configuration parameter was specified. ----- Note: ----- segment has reached it's max_extents ------------------------------------ oracle later than 7.3.x Version 7.3 and later: You can set the MAXEXTENTS storage parameter value to UNLIMITED for any object. Rollback Segment ================ ALTER ROLLBACK SEGMENT rollback_segment STORAGE ( MAXEXTENTS UNLIMITED); Temporary Segment ================= ALTER TABLESPACE tablespace DEFAULT STORAGE ( MAXEXTENTS UNLIMITED); Table Segment ============= ALTER TABLE MANIIN_ASIAKAS STORAGE ( MAXEXTENTS UNLIMITED); ALTER TABLE MANIIN_ASIAKAS STORAGE ( NEXT 5M ); Index Segment ============= ALTER INDEX index STORAGE ( MAXEXTENTS UNLIMITED); Table Partition Segment ======================= ALTER TABLE table MODIFY PARTITION partition STORAGE (MAXEXTENTS UNLIMITED); ----- Note: ----- max logs -------- Problem Description ------------------- In the "alert.log", you find the following warning messages: kccrsz: denied expansion of controlfile section 9 by 65535 record(s) the number of records is already at maximum value (65535) krcpwnc: following controlfile record written over: RECID #520891 Recno 53663 Record timestamp ... kccrsz: denied expansion of controlfile section 9 by 65535 record(s) the number of records is already at maximum value (65535) krcpwnc: following controlfile record written over: RECID #520892 Recno 53664 Record timestamp The database is still running. The CONTROL_FILE_RECORD_KEEP_TIME init parameter is set to 7. If you display the records used in the LOG HISTORY section 9 of the controlfile: SQL> SELECT * FROM v$controlfile_record_section WHERE type='LOG HISTORY' ; TYPE RECORDS_TOTAL RECORDS_USED FIRST_INDEX LAST_INDEX LAST_RECID ------------- ------------- ------------ ----------- ---------- ---------- LOG HISTORY 65535 65535 33864 33863 520892 The number of RECORDS_USED has reached the maximum allowed in RECORDS_TOTAL. Solution Description -------------------- Set the CONTROL_FILE_RECORD_KEEP_TIME to 0: * Insert the parameter CONTROL_FILE_RECORD_KEEP_TIME = 0 IN "INIT.ORA" -OR- * Set it momentarily if you cannot shut the database down now: SQL> alter system set control_file_record_keep_time=0; Explanation ----------- The default value for * the CONTROL_FILE_RECORD_KEEP_TIME is 7 days. SELECT value FROM v$parameter WHERE name='control_file_record_keep_time'; VALUE ----- 7 * the MAXLOGHISTORY database parameter has already reached the maximum of 65535 and it cannot be increased anymore. SQL> alter database backup controlfile to trace; => in the trace file, MAXLOGHISTORY is 65535 The MAXLOGHISTORY increases dynamically when the CONTROL_FILE_RECORD_KEEP_TIME is set to a value different FROM 0, but does not exceed 65535. Once reached, the message appears in the alert.log warning you that a controlfile record is written over. ----- Note: ----- ORA-470 ORA-00470 ORA-470 maxloghistory --------------------- Problem Description: ==================== Instance cannot be started because of ORA-470. LGWR has also died creating a trace file with an ORA-204 error. It is possible that the maxloghistory limit of 65535 as specified in the controlfile has been reached. Diagnostic Required: ==================== The following information should be requested for diagnostics: 1. LGWR trace file produced 2. Dump of the control file - using the command: ALTER SESSION SET EVENTS 'immediate trace name controlf level 10' 3. Controlfile contents, using the command: ALTER DATABASE BACKUP CONTROLFILE TO TRACE; Diagnostic Analysis: ==================== The following observations will indicate that we have the maxloghistory limit of 65535: 1. The Lgwr trace file should show the following stack trace: - in 8.0.3 and 8.0.4, OSD skgfdisp returns ORA-27069, stack: kcrfds -> kcrrlh -> krcpwnc -> kccroc -> kccfrd -> kccrbl -> kccrbp - in 8.0.5 kccrbl causes SEGV before the call to skgfdisp with wrong block number. stack: kcrfds -> kcrrlh -> krcpwnc -> kccwnc -> kccfrd -> kccrbl 2. FROM the 'dump of the controlfile': ... ... numerous lines omittted ... LOG FILE HISTORY RECORDS: (blkno = 0x13, size = 36, max = 65535, in-use = 65535, last-recid= 188706) ... the max value of 65535 reconfirms that the limit has been reached. 3. Further confirmation can be seen FROM the controlfile trace: CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS NOARCHIVELOG MAXLOGFILES 16 MAXLOGMEMBERS 2 MAXDATAFILES 50 MAXINSTANCES 1 MAXLOGHISTORY 65535 ... Diagnostic Solution: =================== 1. Set control_file_record_keep_time = 0 in the init.ora. This parameter specifies the minimum age of a log history record in days before it can be reused. With the parameter set to 0, reusable sections never expand and records are reused immediately as required. [NOTE:1063567.6] gives a good description on the use of this parameter. 2. Mount the database and retrieve details of online redo log files for use in step 6. Because the recovery will need to roll forward through current online redo logs, a list of online log details is required to indicate which redo log is current. This can be obtained using the following command: startup mount SELECT * FROM v$logfile; 3. Open the database. This is a very important step. Although the startup will fail, it is a very important step before recreating the controlfile in step 5 and hense, enabling crash recovery to repair any incomplete log switch. Without this step it may be impossible to recover the database. alter database open 4. Shutdown the database, if it did not already crash in step 3. 5. Using the backup controlfile trace, recreate the controlfile with a smaller maxloghistory value. The MAXLOGHISTORY section of the current control file cannot be extended beyond 65536 entries. The value should reflect the amount of log history that you wish to maintain. An ORA-219 may be returned when the size of the controlfile, based on the values of the MAX- parameters, is higher then the maximum allowable size. [NOTE:1012929.6] gives a good step-by-step guide to recreating the control file. 6. Recover the database. The database will automatically be mounted due to the recreation of the controlfile in step 5 : Recover database using backup controlfile; At the recovery prompt apply the online logs in sequence by typing the unquoted full path and file name of the online redo log to apply, as noted in step 2. After applying the current redo log, you will receive the message 'Media Recovery Complete'. 7. Once media recovery is complete, open the database as follows: alter database open resetlogs; Note: keep recurring "Control file resized from" > /dbms/tdbaplay/playroca/admin/dump/udump/playroca_ora_1548438.trc > Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production > With the Partitioning, OLAP and Data Mining options > ORACLE_HOME = /dbms/tdbaplay/ora10g/home > System name: AIX > Node name: pl003 > Release: 3 > Version: 5 > Machine: 00CB560D4C00 > Instance name: playroca > Redo thread mounted by this instance: 1 > Oracle process number: 28 > Unix process pid: 1548438, image: oracle@pl003 (TNS V1-V3) > > *** 2008-02-21 12:51:57.587 > *** ACTION NAME:(0000010 FINISHED67) 2008-02-21 12:51:57.583 > *** SERVICE NAME:(SYS$USERS) 2008-02-21 12:51:57.583 > *** SESSION ID:(518.643) 2008-02-21 12:51:57.583 > Control file resized from 454 to 470 blocks > kccrsd_append: rectype = 28, lbn = 227, recs = 1128 ----- Note: ----- Compatible init.ora change: --------------------------- Database files have the COMPATIBLE version in the file header. If you set the parameter to a higher value, all the headers will be updated at next database startup. This means that if you shutdown your database, downgrade the COMPATIBLE parameter, and try to restart your database, you'll receive an error message something like: ORA-00201: control file version 7.3.2.0.0 incompatible with ORACLE version 7.0.12.0.0 ORA-00202: control file: '/usr2/oracle/dbs/V73A/ctrl1V73A.ctl' In the above case, database was running with COMPATIBLE 7.3.2.0. I commented out the parameter in init.ora, that is; kernel uses default 7.0.12.0 and returns an error before mounting since kernel cannot read the controlfile header. - You may only change the value of COMPATIBLE after a COLD Backup. - You may only change the value of COMPATIBLE if the database has been shutdown in NORMAL/IMMEDIATE mode. This parameter allows you to use a new release, while at the same time guaranteeing backward compatibility with an earlier release (in case it becomes necessary to revert to the earlier release). This parameter specifies the release with which Oracle7 Server must maintain compatibility. Some features of the current release may be restricted. For example, if you are running release 7.2.2.0 with compatibility set to 7.1.0.0 in order to guarantee compatibility, you will not be able to use 7.2 features. When using the standby database and feature, this parameter must have the same value on the primary and standby databases, and the value must be 7.3.0.0.0 or higher. This parameter allows you to immediately take advantage of the maintenance improvements of a new release in your production systems without testing the new functionality in your environment. The default value is the earliest release with which compatibility can be guaranteed. Ie: It is not possible to set COMPATIBLE to 7.3 on an Oracle8 database. ----------------- Hi Tom, Just installed DB9.0.1, I tried to modify parameter in init.ora file: compatible=9.0.0(default) to 8.1.0. After I restarted the 901 DB, I got error below when I login to sqlplus: ERROR: ORA-01033: ORACLE initialization or shutdown in progress Anything wrong with that? If I change back, everything is ok. The database could not start up. If you start the database manually, from the command line -- you would discover this. For example: idle> startup pfile=initora920.ora ORACLE instance started. Total System Global Area 143725064 bytes Fixed Size 451080 bytes Variable Size 109051904 bytes Database Buffers 33554432 bytes Redo Buffers 667648 bytes Database mounted. ORA-00402: database changes by release 9.2.0.0.0 cannot be used by release 8.1.0.0.0 ORA-00405: compatibility type "Locally Managed SYSTEM tablespace" ..... Generally, compatible cannot be set DOWN as you are already using new features many times that are not compatible with the older release. You would have had to of created the database with 8.1 file formats (compatible set to 8.1 from the very beginning) ------------------------------ ----- Note: ----- ORA-27044: unable to write the header block of file: ---------------------------------------------------- Problem Description: ==================== When you manually switch redo logs, or when the log buffer causes the redo threads to switch, you see errors similar to the following in your alert log: ... Fri Apr 24 13:42:00 1998 Thread 1 advanced to log sequence 170 Current log# 4 seq# 170 mem# 0: /.../rdlACPT04.rdl Fri Apr 24 13:42:04 1998 Errors in file /.../acpt_arch_15973.trc: ORA-202: controlfile: '/.../ctlACPT01.dbf' ORA-27044: unable to write the header block of file SVR4 Error: 48: Operation not supported Additional information: 3 Fri Apr 24 13:42:04 1998 kccexpd: controlfile resize from 356 to 368 block(s) denied by OS ... Note: The particular SVR4 error observed may differ in your case and is irrelevant here. ORA-00202: "controlfile: '%s'" Cause: This message reports the name file involved in other messages. Action: See associated error messages for a description of the problem. ORA-27044: "unable to write the header block of file" Cause: write system call failed, additional information indicates which function encountered the error Action: check errno Solution Description: ===================== To workaround this problem you can: 1. Use a database blocksize smaller than 16k. This may not be practical in all cases, and to change the db_block_size of a database you must rebuild the database. - OR - 2. Set the init.ora parameter CONTROL_FILE_RECORD_KEEP_TIME equal to zero. This can be done by adding the following line to your init.ora file: CONTROL_FILE_RECORD_KEEP_TIME = 0 The database must be shut down and restarted to have the changed init.ora file read. Explanation: ============ This is [BUG:663726] , which is fixed in release 8.0.6. The write of a 16K buffer to a control file seems to fail during an implicit resize operation on the controlfile that came as a result of adding log history records (V$LOG_HISTORY) when archiving an online redo log after a log switch. Starting with Oracle8 the control file can grow to a much larger size than it was able to in Oracle7. Bug 663726 is only reproducible when the control file needs to grow AND when the db_block_size = 16k. This has been tested on instances with a smaller database block size and the problem has not been able to be reproduced. Records in some sections in the control file are circularly reusable while records in other sections are never reused. CONTROL_FILE_RECORD_KEEP_TIME applies to reusable sections. It specifies the minimum age in days that a record must have before it can be reused. In the event a new record needs to be added to a reusable section and the oldest record has not aged enough, the record section expands. If CONTROL_FILE_RECORD_KEEP_TIME is set to 0, then reusable sections never expand and records are reused as needed. ----- Note: ----- ORA-04031 error shared_pool: ---------------------------- ORA-4031 ORA-04031 DIAGNOSING AND RESOLVING ORA-04031 ERROR For most applications, shared pool size is critical to Oracle perfoRMANce. The shared pool holds both the d ata dictionary cache and the fully parsed or compiled representations of PL/SQL blocks and SQL statements. When any attempt to allocate a large piece of contiguous memory in the shared pool fails Oracle first flushes all objects that are not currently in use from the pool and the resulting free memory chunks are merged. If there is still not a single chunk large enough to satisfy the request ORA-04031 is returned. The message that you will get when this error appears is the following: Error: ORA 4031 Text: unable to allocate %s bytes of shared memory (%s,%s,%s) The ORA-04031 error is usually due to fragmentation in the library cache or shared pool reserved space. Before of increasing the shared pool size consider to tune the application to use shared sql and tune SHARED_POOL_SIZE, SHARED_POOL_RESERVED_SIZE, and SHARED_POOL_RESERVED_MIN_ALLOC. First determine if the ORA-04031 was a result of fragmentation in the library cache or in the shared pool reserved space by issuing the following query: SELECT free_space, avg_free_size, used_space, avg_used_size, request_failures, last_failure_size FROM v$shared_pool_reserved; The ORA-04031 is a result of lack of contiguous space in the shared pool reserved space if: REQUEST_FAILURES is > 0 and LAST_FAILURE_SIZE is > SHARED_POOL_RESERVED_MIN_ALLOC. To resolve this consider increasing SHARED_POOL_RESERVED_MIN_ALLOC to lower the number of objects being cached into the shared pool reserved space and increase SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE to increase the available memory in the shared pool reserved space. The ORA-04031 is a result of lack of contiguous space in the library cache if: REQUEST_FAILURES is > 0 and LAST_FAILURE_SIZE is < SHARED_POOL_RESERVED_MIN_ALLOC or REQUEST_FAILURES is 0 and LAST_FAILURE_SIZE is < SHARED_POOL_RESERVED_MIN_ALLOC The first step would be to consider lowering SHARED_POOL_RESERVED_MIN_ALLOC to put more objects into the shared pool reserved space and increase SHARED_POOL_SIZE. This view keeps information of every SQL statement and PL/SQL block executed in the database. The following SQL can show you statements with literal values or candidates to include bind variables: SELECT substr(sql_text,1,40) "SQL", count(*) , sum(executions) "TotExecs" FROM v$sqlarea WHERE executions < 5 GROUP BY substr(sql_text,1,40) HAVING count(*) > 30 ORDER BY 2; ----- Note: ----- ORA-4030 Out of memory: ----------------------- Possibly no memory left in Oracle, or the OS does not grant more memory. Also inspect the size of any swap file. The errors is also reported if execute permissions are not in place on some procedure. ----- Note: ----- wrong permissions on oracle: ---------------------------- Hi, I am under very confusing situation. I'm running database (8.1.7) My oracle is installed under ownership of userid "oracle" when i login with unix id "TEST" and give oracle_sid,oracle_home,PATH variables and then do sqlplus sys after logging in when i give "select file#,error from v$datafile_header;" for some file# i get error as "CAN NOT READ HEADER" but when i login through other unix id and do the same thing. I'm not getting any error.. This seems very very confusing, Could you tell me the reason behind this?? Thank & Regards, Atul Followup: sounds like you did not run the root.sh during the install and the permissions on the oracle binaries are wrong. what does ls -l $ORACLE_HOME/bin/oracle look like. it should look like this: $ ls -l $ORACLE_HOME/bin/oracle -rwsr-s--x 1 ora920 ora920 51766646 Mar 31 13:03 /usr/oracle/ora920/bin/oracle with the "s" bits set. rwsr-s--x 1 oracle dba 494456 Dec 7 1999 lsnrctl regardless of who I log in as, when you have a setuid program as the oracle binary is, it'll be running "as the owner" tell me, what does ipcs -a show you, who is the owner of the shared memory segments associated with the SGA. If that is not Oracle -- you are "getting confused" somewhere for the s bit would ensure that Oracle was the owner. Some connection troubleshooting: -------------------------------- ----- Note: ----- ORA-12545: ---------- This one is probaly due to the fact the IP or HOSTNAME in tnsnames is wrong. ORA-12514: ---------- This one is probaly due to the fact the SERVICE_NAME in tnsnames is wrong or should be fully qualified with domain name. ORA-12154: ---------- This one is probaly due to the fact the alias you have used in the logon dialogbox is wrong. fully qualified with domain name. ORA-12535: ---------- The TNS-12535 or ORA-12535 error is normally a timeout error associated with Firewalls or slow Networks. + It can also be an incorrect listener.ora parameter setting for the CONNECT_TIMEOUT_ value specified. + In essence, the ORA-12535/TNS-12535 is a timing issue between the client and server. ORA-12505: ---------- TNS:listener does not currently know of SID given in connect descriptor Note 1: ------- Symptom: When trying to connect to Oracle the following error is generated: ORA-12224: TNS: listener could not resolve SID given in connection description. Cause: The SID specified in the connection was not found in the listener’s tables. This error will be returned if the database instance has not registered with the listener. Possible Remedy: Check to make sure that the SID is correct. The SIDs that are currently registered with the listener can be obtained by typing: LSNRCTL SERVICES These SIDs correspond to SID_NAMEs in TNSNAMES.ORA or DB_NAME in the initialisation file. Note 2: ------- ORA-12505: TNS:listener could not resolve SID given in connect descriptor You are trying to connect to a database, but the SID is not known. Although it is possible that a tnsping command succeeds, there might still a problem with the SID parameter of the connection string. eg. C:>tnsping ora920 TNS Ping Utility for 32-bit Windows: Version 9.2.0.7.0 - Production Copyright (c) 1997 Oracle Corporation. All rights reserved. Used parameter files: c:\oracle\ora920\network\admin\sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = DEV01)(PORT = 2491))) (CONNECT_DATA = (SID = UNKNOWN) (SERVER = DEDICATED))) OK (20 msec) As one can see, this is the connection information stored in a tnsnames.ora file: ORA920.EU.DBMOTIVE.COM = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = DEV01)(PORT = 2491)) ) (CONNECT_DATA = (SID = UNKNOWN) (SERVER = DEDICATED) ) ) However, the SID UNKNOWN is not known by the listener at the database server side. In order to test the known services by a listener, we can issue following command at the database server side: C:>lsnrctl services LSNRCTL for 32-bit Windows: Version 10.1.0.2.0 - Production Copyright (c) 1991, 2004, Oracle. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=DEV01)(PORT=1521))) Services Summary... Service "ORA10G.eu.dbmotive.com" has 1 instance(s). Instance "ORA10G", status UNKNOWN, has 1 handler(s) for this service... Handler(s): "DEDICATED" established:0 refused:0 LOCAL SERVER Service "ORA920.eu.dbmotive.com" has 2 instance(s). Instance "ORA920", status UNKNOWN, has 1 handler(s) for this service... Handler(s): "DEDICATED" established:0 refused:0 LOCAL SERVER Instance "ORA920", status READY, has 1 handler(s) for this service... Handler(s): "DEDICATED" established:2 refused:0 state:ready LOCAL SERVER The command completed successfully Know services are ORA10G and ORA920. Changing the SID in our tnsnames.ora to a known service by the listener (ORA920) solved the problem. ----- Note: ----- ORA-12560 --------- Note 1: ------- Oracle classify this as a ‘generic protocol adapter error’. In my experience it indicates that Oracle client does not know what instance to connect to or what TNS alias to use. Set the correct ORACLE_HOME ans ORACLE_SID variables. Note 2: ------- Doc ID: Note:73399.1 Subject: WINNT: ORA-12560 DB Start via SVRMGRL or SQL*PLUS ORACLE_SID is set correctly Type: BULLETIN Status: PUBLISHED Content Type: TEXT/PLAIN Creation Date: 28-JUL-1999 Last Revision Date: 14-JAN-2004 PURPOSE To assist in resolving ORA-12560 errors on Oracle8i. SCOPE & APPLICATION Support Analysts and customers. RELATED DOCUMENTS PR:1070749.6 NOTE:1016454.102 TNS 12560 DB CREATE VIA INSTALLATION OR CONFIGURATION ASSISTANT FAILS BUG:948671 ORADIM SUCCSSFULLY CREATES AN UNUSABLE SID WITH NON-ALPHANUMERIC CHARACTER BUG:892253 ORA-12560 CREATING DATABASE WITH DB CONFIGURATION ASSISTANT IF SID HAS NON-ALPHA If you encounter an ORA-12560 error when you try to start Server Manager or SQL*Plus locally on your Windows NT server, you should first check the ORACLE_SID value. Make sure the SID is correctly set, either in the Windows NT registry or in your environment (with a set command). Also, you must verify that the service is running. See the entries above for more details. If you have verified that ORACLE_SID is properly set, and the service is running, yet you still get an ORA-12560, then it is possible that you have created an instance with a non-alphanumeric character. The Getting Started Guide for Oracle8i on Windows NT documents that SID names can contain only alphanumerics, however if you attempt to create a SID with an underscore or a dash on Oracle8i you are not prevented from doing so. The service will be created and started successfully, but attempts to connect will fail with an ORA-12560. You must delete the instance and recreate it with no special characters - only alphanumerics are allowed in the SID name. See BUG#948671, which was logged against 8.1.5 on Windows NT for this issue. Note 3: ------- Doc ID : Note:119008.1 Content Type: TEXT/PLAIN Subject: ORA-12560 Connecting to the Server on Unix - Troubleshooting Creation Date: 04-SEP-2000 Type: PROBLEM Last Revision Date: 20-MAR-2003 Status: PUBLISHED PURPOSE ------- This note describes some of the possible reasons for ORA-12560 errors connecting to server on Unix Box. The list below shows some of the causes, the symptoms and the action to take. It is possible you will hit a cause not described here, in that case the information above should allow it to be identified. SCOPE & APPLICATION ------------------- Support Analysts and customers alike. ORA-12560 CONNECTING TO THE SERVER ON UNIX - TROUBLESHOOTING ------------------------------------------------------------ ORA-12560: TNS:protocol adapter error Cause: A generic protocol adapter error occurred. Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and re execute the operation. Turn off tracing when the operation is complete. F This is a high-level error just reporting an error occurred in the actual transport layer. Look at the next error down the stack and process that. 1. ORA-12500 ORA-12560 MAKING MULTIPLE CONNECTIONS TO DATABASE Problem: Trying to connect to the database via listener and the ORA-12500 are prompted. You may see in the listener.log ORA-12500 and ORA-12560: ORA-12500: TNS:listener failed to start a dedicated server process Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment maybe set up incorrectly. Action: Turn on tracing at the ADMIN level and re execute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. If error persists, contact Worldwide Customer Support. In many cases the error ORA-12500 is caused due to leak of resources in the Unix Box, if you are enable to connect to database and randomly you get the error your operating system is reached the maximum values for some resources. Otherwise, if you get the error in first connection the problem may be in the configuration of the system. Solution: Finding the resource which is been reached is difficult, the note 2064862.102 indicates some suggestion to solve the problems. 2. ORA-12538/ORA-12560 connecting to the database via SQL*Net Problem: Trying to connect to database via SQL*Net the error the error ORA-12538 is prompted. In the trace file you can see: nscall: error exit nioqper: error from nscall nioqper: nr err code: 0 nioqper: ns main err code: 12538 nioqper: ns (2) err code: 12560 nioqper: nt main err code: 508 nioqper: nt (2) err code: 0 nioqper: nt OS err code: 0 Solution: - Check the protocol used in the TNSNAMES.ORA by the connection string - Ensure that the TNSNAMES.ORA you check is the one that is actually being used by Oracle. Define the TNS_ADMIN environment variable to point to the TNSNAMES directory. - Using the $ORACLE_HOME/bin/adapters command, ensure the protocol is installed. Run the command without parameters to check if the protocol is installed, then run the command with parameters to see whether a particular tool/application contains the protocol symbols e.g.: 1. $ORACLE_HOME/bin/adapters 2. $ORACLE_HOME/bin/adapters $ORACLE_HOME/bin/oracle $ORACLE_HOME/bin/adapters $ORACLE_HOME/bin/sqlplus Explanation: If the protocol is not installed every connection attempting to use it will fail with ORA-12538 because the executable doesn't contain the required protocol symbol/s. Error ORA-12538 may also be caused by an issue with the '$ORACLE_HOME/bin/relink all' command. 'Relink All' does not relink the sqlplus executable. If you receive error ORA-12538 when making a sqlplus connection, it may be for this reason. To relink sqlplus manually: $ su - oracle $ cd $ORACLE_HOME/sqlplus/lib $ make -f ins_sqlplus.mk install $ ls -l $ORACLE_HOME/bin/sqlplus --> should show a current date/time stamp 3. ORA-12546 ORA-12560 connecting locally to the database Problem: Trying to connect to database locally with a different account to the software owner, the error the error ORA-12546 is prompted. In the trace file you can see: nioqper: error from nscall nioqper: nr err code: 0 nioqper: ns main err code: 12546 nioqper: ns (2) err code: 12560 nioqper: nt main err code: 516 nioqper: nt (2) err code: 13 nioqper: nt OS err code: 0 Solution: Make sure the permissions of oracle executable are correct, this should be: 52224 -rwsr-sr-x 1 oracle dba 53431665 Aug 10 11:07 oracle Explanation: The problem occurs due to an incorrect setting on the oracle executable. 4. ORA-12541 ORA-12560 TRYING TO CONNECT TO A DATABASE Problem: You are trying to connect to a database using SQL*Net and receive the following error ORA-12541 ORA-12560 after change the TCP/IP port in the listener.ora and you are using PARAMETER USE_CKPFILE_LISTENER in listener.ora. The following error struct appears in the SQLNET.LOG: nr err code: 12203 TNS-12203: TNS:unable to connect to destination ns main err code: 12541 TNS-12541: TNS:no listener ns secondary err code: 12560 nt main err code: 511 TNS-00511: No listener nt secondary err code: 239 nt OS err code: 0 Solution: Check [NOTE:1061927.6] to resolve the problem. Explanation: If TCP protocol is listed in the Listener.ora's ADDRESS_LIST section and the parameter USE_CKPFILE_LISTENER = TRUE, the Listener ignores the TCP port number defined in the ADDRESS section and listens on a random port. RELATED DOCUMENTS ----------------- Note:39774.1 LOG & TRACE Facilities on NET . Note:45878.1 SQL*Net Common Errors & Diagnostic Worksheet Net8i Admin/Ch.11 Troubleshooting Net8 / Resolving the Most Common Error Messages ----- Note: ----- ORA-12637 Packet received failed. A process was unable to receive a packet from another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. Note 1: Just edit the file sqlnet.ora and search for the string SQLNET.AUTHENTICATION_SERVICES. When it exists it’s set to = (TNS), change this to = (NONE). When it doesn’t exist, add the string SQLNET.AUTHENTICATION_SERVICES = (NONE) Note 2: What does SQLNET.AUTHENTICATION_SERVICES do? SQLNET.AUTHENTICATION_SERVICES Purpose Use the parameter SQLNET.AUTHENTICATION_SERVICES to enable one or more authentication services. If authentication has been installed, it is recommended that this parameter be set to either none or to one of the authentication methods. Default None Values Authentication Methods Available with Oracle Net Services: none for no authentication methods. A valid username and password can be used to access the database. all for all authentication methods nts for Windows NT native authentication Authentication Methods Available with Oracle Advanced Security: kerberos5 for Kerberos authentication cybersafe for Cybersafe authentication radius for RADIUS authentication dcegssapi for DCE GSSAPI authentication See Also: Oracle Advanced Security Administrator's Guide Example SQLNET.AUTHENTICATION_SERVICES=(kerberos5, cybersafe) Note 3: ORA-12637 for members of one NT group, using OPS$ login Being "identified externally", users can work fine until the user is added to a "wwwauthor" NT group to allow them to publish documents on Microsoft IIS (intranet) -- then they get ORA-12637 starting the Oracle c/s application (document management system). The environment is: Oracle 9.2.0.1.0 on Windows 2000 Advanced Server w. SP4, Windows 2003 domain controllers in W2K compatible mode, client workstations with W2K and Win XP. Any hint will be appreciated. Problem solved. Specific NT group (wwwauthor) which caused problems had existed already with specific permissions, then it was dropped and created again with exactly the same name (but, of course, with different internal ID). This situation have been identified as causing some kind of mess. A completely new group with different name has been created. Note 4: ORA-12637 packet receive failure I added a second instance to the Oracle server. Since then, on the server and all clients, I get ORA-12637 packet receive failure when I try to connect to this database. Why is this? Hello Try commenting out the SQLNET.CRYPTO_SEED and SQLNET.AUTHENTICATION_SERVICES in the server's SQLNET.ORA and on the client sqlnet file if they exist. Please also verify that the server's LISTENER.ORA file contains the following parameter: CONNECT_TIMEOUT_LISTENER=0 Note 5: Workaround is to turn off prespawned server processes in "listener.ora". In the "listener.ora", comment out or delete the prespawn parameters, ie: SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = prd) (ORACLE_HOME = /raid/app/oracle/product/7.3.4) # (PRESPAWN_MAX = 99) # (PRESPAWN_LIST = # (PRESPAWN_DESC = (PROTOCOL = TCP) (POOL_SIZE = 1) (TIMEOUT = 30)) # ) ) ) Note 6: Problem Description ------------------- Connections to Oracle 9.2 using a Cybersafe authenticated user fails on Solaris 2.6 with ORA-12637 and a core dump is generated. Solution Description -------------------- 1) Shutdown Oracle, the listener and any clients. 2) In $ORACLE_HOME/lib take a backup copy of the file sysliblist 3) Edit sysliblist. Move the -lthread entry to the beginning. So change from, -lnsl -lsocket -lgen -ldl -lsched -lthread To, -lthread -lnsl -lsocket -lgen -ldl -lsched 4) Do $ORACLE_HOME/bin/relink all Note 7: fact: Oracle Server - Personal Edition 8.1 fact: MS Windows symptom: Starting Server Manager (Svrmgrl) Fails symptom: ORA-12637: Packet Receive Failed cause: Oracle's installer will set the authentication to (NTS) by default. However, if the Windows machine is not in a Domain where there is a Windows Domain Controller, it will not be able to contact the KDC (Key Distribtion Centre) needed for Authentication. fix: Comment out SQLNET.AUTHENTICATION_SERVICES=(NTS) in sqlnet.ora ----- Note: ----- ORA-02058: dba_2pc_pending: Lists all in-doubt distributed transactions. The view is empty until populated by an in-doubt transaction. After the transaction is resolved, the view is purged. SQL> SELECT LOCAL_TRAN_ID, GLOBAL_TRAN_ID, STATE, MIXED, HOST, COMMIT# 2 FROM DBA_2PC_PENDING 3 / LOCAL_TRAN_ID GLOBAL_TRAN_ID ---------------------- ---------------------------------------------------------- 6.31.5950 1145324612.10D447310B5FCE408A296417959EBEEC00000000 SQL> select STATE, MIXED, HOST, COMMIT# 2 FROM DBA_2PC_PENDING 3 / STATE MIX HOST ---------------- --- ------------------------------------------------------------ forced rollback no REBV\PGSS-TST-TCM SQL> select * from dba_2pc_neighbors; LOCAL_TRAN_ID IN_ DATABASE ---------------------- --- -------------------------------------------------- 6.31.5950 in O SQL> select state, tran_comment, advice from dba_2pc_pending; STATE TRAN_COMMENT ---------------- ------------------------------------------------------------ prepared SQL> rollback force '6.31.5950'; Rollback complete. SQL> commit; Doc ID: Note:290405.1 Subject: ORA-30019 When Executing Dbms_transaction.Purge_lost_db_entry Type: PROBLEM Status: MODERATED Content Type: TEXT/X-HTML Creation Date: 11-NOV-2004 Last Revision Date: 16-NOV-2004 The information in this document applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.5 This problem can occur on any platform. Errors ORA-30019 Illegal rollback Segment operation in Automatic Undo mode Symptoms Attempting to clean up the pending transaction using DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY, getting ora-30019: ORA-30019: Illegal rollback Segment operation in Automatic Undo mode Changes AUTO UNDO MANAGEMENT is running Cause DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY is not supported in AUTO UNDO MANAGEMENT This is due to fact that "set transaction use rollback segment.." cannot be done in AUM. Fix 1.) alter session set "_smu_debug_mode" = 4; 2.) execute DBMS_TRANSACTION.PURGE_LOST_DB_ENTRY('local_tran_id'); ----- Note: ----- ORA-600 [12850] Doc ID : Note:1064436.6 Content Type: TEXT/PLAIN Subject: ORA-00600 [12850], AND ORA-00600 [15265]: WHEN SELECT OR DESCRIBE ON TABLE Creation Date: 14-JAN-1999 Type: PROBLEM Last Revision Date: 29-FEB-2000 Status: PUBLISHED Problem Description: --------------------- You are doing a describe or select on a table and receive: ORA-600 [12850]: Meaning: 12850 occurs when it can't find the user who owns the object from the dictionary. If you try to delete the table, you receive: ORA-600 [15625]: Meaning: The arguement 15625 is occuring because some index entry for the table is not found in obj$. Problem Explanation: -------------------- The data dictionary is corrupt. You cannot drop the tables in question because the data dictionary doesn't know they exist. Search Words: ------------- ORA-600 [12850] ORA-600 [15625] describe delete table Solution Description: --------------------- You need to rebuild the database. Solution Explanation: --------------------- Since the table(s) cannot be accessed or dropped because of the data dictionary corruption, rebuilding the database is the only option. ----- Note: ----- ORA-1092 ORA-01092 ------------------------------------------------------------------------------------------- Doc ID : Note:222132.1 Content Type: TEXT/PLAIN Subject: ORA-01599 and ORA-01092 while starting database Creation Date: 03-DEC-2002 Type: PROBLEM Last Revision Date: 07-AUG-2003 Status: PUBLISHED PURPOSE ------- The purpose of this Note is to fix errors ORA-01599 & ORA-01092 when recieved at startup. SCOPE & APPLICATION ------------------- All DBAs, Support Analyst. Symptom(s) ~~~~~~~~~~ Starting the database gives errors similar to: ORA-01599: failed to acquire rollback segment (20), cache space is full (currently has (19) entries) ORA-01092: ORACLE instance terminated Change(s) ~~~~~~~~~~ Increased shared_pool_size parameter. Increased processes and/or sessions parameters. Cause ~~~~~~~ Low value for max_rollback_segments The above changes changed the value for max_rollback_segments internally. Fix ~~~~ The value for max_rollback_segments which is to be calculated as follows: max_rollback_segments = transactions/transactions_per_rollback_segment or 30 whichever is greater. transactions = session * 1.1; sessions = (processes * 1.1) + 5; The default value for transactions_per_rollback_segment = 5; 1. Use these calculations and find out the value for max_rollback_segments. 2. Set it to this value or 30 whichever is greater. 3. Startup database after this correct setting. Reference info ~~~~~~~~~~~~~~ [BUG:2233336] - RDBMS ERRORS AT STARTUP CAN CAUSE ODMA TO OMIT CLEANUP ACTIONS [NOTE:30764.1] - Init.ora Parameter "MAX_ROLLBACK_SEGMENTS" Reference Note -------------------------------------------------------------------------------------------- Doc ID : Note:1038418.6 Content Type: TEXT/PLAIN Subject: ORA-01092 STARTING UP ORACLE RDBMS DATABASE Creation Date: 17-NOV-1997 Type: PROBLEM Last Revision Date: 06-JUL-1999 Status: PUBLISHED Problem Summary: ================ ORA-01092 starting up Oracle RDBMS database. Problem Description: ==================== When you startup your Oracle RDBMS database, you receive the following error: ORA-01092: ORACLE instance terminated. Disconnection forced. Problem Explanation: ==================== Oracle cannot write to the alert_.log file because the ownership and/or permissions on the BACKGROUND_DUMP_DEST directory are incorrect. Solution Summary: ================= Modify the ownership and permissions of directory BACKGROUND_DUMP_DEST. Solution Description: ===================== To allow oracle to write to the BACKGROUND_DUMP_DEST directory (contains alert_.log), modify the ownership of directory BACKGROUND_DUMP_DEST so that the oracle user (software owner) is the owner and make the permissions on directory BACKGROUND_DUMP_DEST 755. Follow these steps: 1. Determine the location of the BACKGROUND_DUMP_DEST parameter defined in the init.ora or config.ora files. 2. Login as root. 3. Change directory to the location of BACKGROUND_DUMP_DEST. 4. Change the owner of all the files and the directory to the software owner. For example: % chown oracle * 5. Change the permissions on the directory to 755. % chmod 755 . Solution Explanation: ===================== Changing the ownership and permissions of the BACKGROUND_DUMP_DEST directory, enables oracle to write to the alert_.log file. --------------------------------------------------------------------------- Doc ID : Note:273413.1 Content Type: TEXT/X-HTML Subject: Database Does not Start, Ora-00604 Ora-25153 Ora-00604 Ora-1092 Creation Date: 19-MAY-2004 Type: PROBLEM Last Revision Date: 04-OCT-2004 Status: MODERATED The information in this article applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 10.1.0.4 This problem can occur on any platform. Errors ORA-1092 Oracle instance terminated. ORA-25153 Temporary Tablespace is Empty ORA-604 error occurred at recursive SQL level Symptoms The database is not opening and in the alert.log the following errors are reported: ORA-00604: error occurred at recursive SQL level 1 ORA-25153: Temporary Tablespace is Empty Error 604 happened during db open, shutting down database USER: terminating instance due to error 604 Instance terminated by USER, pid = xxxxx ORA-1092 signalled during: alter database open... You might find SQL in the trace file like: select distinct d.p_obj#,d.p_timestamp from sys.dependency$ d, obj$ o where d.p_obj#>=:1 and d.d_obj#=o.obj# and o.status!=5 Cause In the case where there's locally managed temp tablespace in the database,after controlfile is re-created using the statement generated by "alter database backup controlfile to trace", the database can't be opened again because it complains that temp tablespace is empty. However no tempfiles can be added to the temp tablespace, nor can the temp tablespace be dropped because the database is not yet open. The query failed because of inadequate sort space(memory + disk) Fix We can increase the sort_area_size and sort_area_retained_size to a very high value so that the query completes. Then DB will open and we can take care of the TEMP tablespace If the error still persists after increasing the sort_area_size and sort_area_retained_size to a high vale, then the only option remains is to restore and recover. ------------------------------------------------------------------------------- Displayed below are the messages of the selected thread. Thread Status: Active From: Ronald Shaffer 17-Mar-05 19:23 Subject: Deleted OUTLN and now I get ORA-1092 and ORA-18008 RDBMS Version: 10G Operating System and Version: RedHat ES 3 Error Number (if applicable): ORA-1092 and ORA-18008 Product (i.e. SQL*Loader, Import, etc.): Product Version: Deleted OUTLN and now I get ORA-1092 and ORA-18008 One of our DBAs dropped the OUTLN user in 10G and now the instance will not start. We get an ORA-18008 specifying the schema is missing and an ORA-1092 when it attempts to OPEN. Startup mount is as far as we can get. Any experience with this issue out there? Thanks... From: Fairlie Rego 23-Mar-05 01:26 Subject: Re : Deleted OUTLN and now I get ORA-1092 and ORA-18008 Hi Ronald, You are hitting bug 3786479 AFTER DROPPING THE OUTLN USER/SCHEMA, DB WILL NO LONGER OPEN.ORA-18008 http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=BUG&p_id=3786479 If this is still an issue file a Tar and get a backport. Regards, Fairlie Rego ---------------------------------------------------------------------------------- Displayed below are the messages of the selected thread. Thread Status: Closed From: Henry Lau 06-Mar-03 10:38 Subject: ORA-01092 while alter datbase open RDBMS Version: 9.0.1.3 Operating System and Version: Linux Redhat 7.1 Error Number (if applicable): ORA-01092 Product (i.e. SQL*Loader, Import, etc.): ORACLE DATABASE Product Version: 9.0.1.3 ORA-01092 while alter datbase open Hi, Since our undotbs is very large and we try to follow the Doc ID: 157278.1, we are trying to change the undotbs to a new one We try to 1. Create UNDO tablespace undotb2 datafile $ORACLE_HOME/oradata/undotb2.dbf size 300M 2. ALTER SYSTEM SET undo_tablespace=undotb2; 3. Change undo = undotb2; 4. Restart the database; 5. alter tablespace undotbs offline; 6. when we restart the database, it shows the following error. SQL> startup mount pfile=$ORACLE_HOME/admin/TEST/pfile/init.ora ORACLE instance started. Total System Global Area 386688540 bytes Fixed Size 280092 bytes Variable Size 318767104 bytes Database Buffers 67108864 bytes Redo Buffers 532480 bytes Database mounted. SQL> alter database nomount; alter database nomount * ERROR at line 1: ORA-02231: missing or invalid option to ALTER DATABASE SQL> alter database open; alter database open * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced I have checked the Log file as follow: SQL> /u01/oracle/product/9.0.1/admin/TEST/udump/ora_29151.trc Oracle9i Release 9.0.1.3.0 - Production JServer Release 9.0.1.3.0 - Production ORACLE_HOME = /u01/oracle/product/9.0.1 System name: Linux Node name: utxrho01.unitex.com.hk Release: 2.4.2-2smp Version: #1 SMP Sun Apr 8 20:21:34 EDT 2001 Machine: i686 Instance name: TEST Redo thread mounted by this instance: 1 Oracle process number: 9 Unix process pid: 29151, image: oracle@utxrho01.unitex.com.hk (TNS V1-V3) *** SESSION ID:(8.3) 2003-03-06 17:25:38.615 Evaluating checkpoint for thread 1 sequence 8 block 2 ORA-00376: file 2 cannot be read at this time ORA-01110: data file 2: '/u01/oracle/product/9.0.1/oradata/TEST/undotbs01.dbf' ~ ~ ~ ~ Please help to check what the problem is ?? Thank you !! Regards, Henry From: Oracle, Pravin Sheth 07-Mar-03 09:31 Subject: Re : ORA-01092 while alter datbase open Hi Henry, What you are seeing is bug 2360088, which is fixed in Oracle 9.2.0.2. I suggest that you log an iSR (formerly iTAR) for a quicker solution for the problem. Regards Pravin ----------------------------------------------------------------------------------- ----- Note: ----- ORA-600 [qerfxFetch_01] Note 1: ------- Doc ID: Note:255881.1 Subject: ORA-600 [qerfxFetch_01] Type: REFERENCE Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 10-NOV-2003 Last Revision Date: 12-NOV-2004 This note contains information that has not yet been reviewed by the PAA Internals group or DDR. As such, the contents are not necessarily accurate and care should be taken when dealing with customers who have encountered this error. If you are going to use the information held in this note then please take whatever steps are needed to in order to confirm that the information is accurate. Until the article has been set to EXTERNAL, we do not guarantee the contents. Thanks. PAA Internals Group (Note - this section will be deleted as the note moves to publication) Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article represents a partially published OERI note. It has been published because the ORA-600 error has been reported in at least one confirmed bug. Therefore, the SUGGESTIONS section of this article may help in terms of identifying the cause of the error. This specific ORA-600 error may be considered for full publication at a later date. If/when fully published, additional information will be available here on the nature of this error. PURPOSE: This article discusses the internal error "ORA-600 [qerfxFetch_01]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [qerfxFetch_01] VERSIONS: versions 9.2 DESCRIPTION: During database operations, user interrupts need to be handled correctly. ORA-600 [qerfxFetch_01] is raised when an interrupt has been trapped but has not been handled correctly. FUNCTIONALITY: Fixed table row source. IMPACT: NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 2306106 See Note 2306106.8 OERI:[qerfxFetch_01] possible - affects OEM Fixed: 9.2.0.2, 10.1.0.2 INTERNAL ONLY SECTION - NOT FOR PUBLICATION OR DISTRIBUTION TO CUSTOMERS ======================================================================== Ensure that this note comes out on top in Metalink when searched ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 qerfxFetch_01 Note 2: ------- Doc ID : Note:2306106.8 Content Type: TEXT/X-HTML Subject: Support Description of Bug 2306106 Creation Date: 13-AUG-2003 Type: PATCH Last Revision Date: 14-AUG-2003 Status: PUBLISHED Click here for details of sections in this note. Bug 2306106 OERI:[qerfxFetch_01] possible - affects OEM This note gives a brief overview of bug 2306106. Affects: Product (Component) Oracle Server (RDBMS) Range of versions believed to be affected Versions >= 9.2 but < 10G Versions confirmed as being affected 9.2.0.1 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.2.0.2 (Server Patch Set) 10G Production Base Release Symptoms: Error may occur Internal Error may occur (ORA-600) ORA-600 [qerfxFetch_01] Related To: (None Specified) Description ORA-600 [qerfxFetch_01] possible - affects OEM Note 3: ------- Bug 2306106 is fixed in the 9.2.0.2 patchset. This bug is not published and thus cannot be viewed externally in MetaLink. All it says on this bug is 'ORA-600 [qerfxFetch_01] possible - affects OEM'. ----- Note: ----- Undo corruption: ================ Note 1: ------- Doc ID : Note:2431450.8 Content Type: TEXT/X-HTML Subject: Support Description of Bug 2431450 Creation Date: 08-AUG-2003 Type: PATCH Last Revision Date: 05-JAN-2004 Status: PUBLISHED Click here for details of sections in this note. Bug 2431450 SMU Undo corruption possible on instance crash This note gives a brief overview of bug 2431450. Affects: Product (Component) (Rdbms) Range of versions believed to be affected Versions >= 9 but < 10G Versions confirmed as being affected 9.0.1.4 9.2.0.3 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.0.1.5 iAS Patch Set 9.2.0.4 (Server Patch Set) 10g Production Base Release Symptoms: Corruption (Physical) Internal Error may occur (ORA-600) ORA-600 [kteuPropTime-2] / ORA-600 [4191] Related To: System Managed Undo Description SMU (System Managed Undo) Undo corruption possible on instance crash. This can result in subsequent ORA-600 errors due to the undo corruption. Note 2: ------- Doc ID : Note:233864.1 Content Type: TEXT/X-HTML Subject: ORA-600 [kteuproptime-2] Creation Date: 28-MAR-2003 Type: REFERENCE Last Revision Date: 07-APR-2005 Status: PUBLISHED Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article discusses the internal error "ORA-600 [kteuproptime-2]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [kteuproptime-2] VERSIONS: versions 9.0 to 9.2 DESCRIPTION: Oracle has encountered an error propagating Extent Commit Times in the Undo Segment Header / Extent Map Blocks, for System Managed Undo Segments The extent being referenced is not valid. FUNCTIONALITY: UNDO EXTENTS IMPACT: INSTANCE FAILURE POSSIBLE PHYSICAL CORRUPTION SUGGESTIONS: If instance is down and fails to restart due to this error then set the following parameter, which will gather additional information to assist support in identifing the cause: # Dump Undo Segment Headers during transaction recovery event="10015 trace name context forever, level 10" Restart the instance and submit the trace files and alert.log to Oracle Support Services for further analysis. Do not set any other undo/rollback_segment parameters without direction from Support. Known Issues: Bug# 2431450 See Note 2431450.8 SMU Undo corruption possible on instance crash Fixed: 9.2.0.4, 10.1.0.2 Note 3: ------- Hi, apply patchset 9.2.0.2, bug 2431450 is fixed in 9.2.0.2 that made SMU (System Managed Undo) Undo corruption possible on instance crash. It's a very rare scenario : This will only cause a problem if there was an instance crash after a transaction committed but before it propogated the extent commit times to all its extents AND there was a shrink of extents before the transaction could be recovered. But still, this bug was not published (not for any particular reason except it was found internal). Greetings, Note 4: ------- From: Oracle, Ken Robinson 21-Feb-03 17:44 Subject: Re : ORA-600 kteuPropTime-2 Forgot to mention the second bug for this....bug 2689239. Regards, Ken Robinson Oracle Server EE Analyst ORA-600 [4191] possible on shrink of system managed undo segment. Note 5: ------- BUGBUSTER - System-managed undo segment corruption Affects Versions: 9.2.0.1.0, 9.2.0.2.0, 9.2.0.3.0 Fixed in: Patch 2431450, 9.2.0.4.0 BUG# (if recognised) 2431450 This info. correct on: 31-AUG-2003 Symptoms Oracle instance crashes and details of the ORA-00600 error are written to the alert.log ORA-00600: internal error code, arguments: [kteuPropTime-2], [], [], [] Followed by Fatal internal error happened while SMON was doing active transaction recovery. Then SMON: terminating instance due to error 600 Instance terminated by SMON, pid = 22972 This occurs as Oracle encounters an error when propagating Extent Commit Times in the Undo Segment Header Extent Map Blocks. It could be because SMON is over-enthusiastic in shrinking extents in SMU segments. As a result, extent commit times do not get written to all the extents and SMON causes the instance to crash, leaving one or more of the undo segments corrupt. When opening the database following the crash, Oracle tries to perform crash recovery and encounters problems recovering committed transactions stored in the corrupt undo segments. This leads to more ORA-00600 errors and a further instance crash. The net result is that the database cannot be opened: "Error 600 happened during db open, shutting down database" Workaround Until the corrupt undo segment can be identified and offlined then unfortunately the database will not open. Identify the corrupt undo segment by setting the following parameters in the init.ora file: _smu_debug_mode=1 event="10015 trace name context forever, level 10" (set event 10511) event="10511 trace name context forever, level 2" _smu_debug_mode simply collects diagnostic information for support purposes. Event 10015 is the undo segment recovery tracing event. Use this to identify corrupted rollback/undo segments when a database cannot be started. With these parameters set, an attempt to open the database will still cause a crash, but Oracle will write vital information about the corrupt rollback/undo segments to a trace file in user_dump_dest. This is an extract from such a trace file, revealing that undo segment number 6 (_SYSSMU6$) is corrupt. Notice that the information stored in the segment header about the number of extents was inconsistent with the extent map. Recovering rollback segment _SYSSMU6$ UNDO SEG (BEFORE RECOVERY): usn = 6 Extent Control Header ----------------------------------------------------------------- Extent Header:: spare1: 0 spare2: 0 #extents: 7 #blocks: 1934 last map 0x00805f89 #maps: 1 offset: 4080 Highwater:: 0x0080005b ext#: 0 blk#: 1 ext size: 7 #blocks in seg. hdr's freelists: 0 #blocks below: 0 mapblk 0x00000000 offset: 0 Unlocked Map Header:: next 0x00805f89 #extents: 5 obj#: 0 flag: 0x40000000 Extent Map ----------------------------------------------------------------- 0x0080005a length: 7 0x00800061 length: 8 0x0081ac89 length: 1024 0x00805589 length: 256 0x00805a89 length: 256 Retention Table ----------------------------------------------------------- Extent Number:0 Commit Time: 1060617115 Extent Number:1 Commit Time: 1060611728 Extent Number:2 Commit Time: 1060611728 Extent Number:3 Commit Time: 1060611728 Extent Number:4 Commit Time: 1060611728 Comment out parameters undo_management and undo_tablespace and set the undocumented _corrupted_rollback_segments parameter to tell Oracle to ignore any corruptions and force the database open: _corrupted_rollback_segments=(_SYSSMU6$) This time, Oracle will start and open OK, which will allow you to check the status of the undo segments by querying DBA_ROLLBACK_SEGS. select segment_id, segment_name, tablespace_name, status from dba_rollback_segs where owner='PUBLIC'; SEGMENT_ID SEGMENT_NAME TABLESPACE_NAME STATUS ---------- ------------ --------------- ---------------- 1 _SYSSMU1$ UNDOTS OFFLINE 2 _SYSSMU2$ UNDOTS OFFLINE 3 _SYSSMU3$ UNDOTS OFFLINE 4 _SYSSMU4$ UNDOTS OFFLINE 5 _SYSSMU5$ UNDOTS OFFLINE 6 _SYSSMU6$ UNDOTS NEEDS RECOVERY 7 _SYSSMU7$ UNDOTS OFFLINE 8 _SYSSMU8$ UNDOTS OFFLINE 9 _SYSSMU9$ UNDOTS OFFLINE 10 _SYSSMU10$ UNDOTS OFFLINE SMON will complain every 5 minutes by writing entries to the alert.log as long as there are undo segments in need of recovery SMON: about to recover undo segment 6 SMON: mark undo segment 6 as needs recovery At this point, you must either download and apply patch 2431450 or create private rollback segments. Note 6: ------- Repair UNDO log corruption Don Burleson In rare cases (usually DBA error) the Oracle UNDO tablespace can become corrupted. This manifests with this error: ORA-00376: file xx cannot be read at this time In cases of UNDO log corruption, you must: • Change the undo_management parameter from “AUTO” to “MANUAL” • Create a new UNDO tablespace • Drop the old UNDO tablespace Dropping the corrupt UNDO tablespace can be tricky and you may get the message: ORA-00376: file string cannot be read at this time To drop a corrupt UNDO tablespace: 1 – Identify the bad segment: select segment_name, status from dba_rollback_segs where tablespace_name='undotbs_corrupt' and status = ‘NEEDS RECOVERY’; SEGMENT_NAME STATUS ------------------------------ ---------------- _SYSSMU22$ NEEDS RECOVERY 2. Bounce the instance with the hidden parameter “_offline_rollback_segments”, specifying the bad segment name: _OFFLINE_ROLLBACK_SEGMENTS=_SYSSMU22$ 3. Bounce database, nuke the corrupt segment and tablespace: SQL> drop rollback segment "_SYSSMU22$"; Rollback segment dropped. SQL > drop tablespace undotbs including contents and datafiles; Tablespace dropped. Note 7: ------- Old stuff: Sometimes there can be trouble with an undo segment. Actually there might be something with a normal object: PUT the following in the init.ora- event = "10015 trace name context forever, level 10" Setting this event will generate a trace file that will reveal the necessary information about the transaction Oracle is trying to rollback and most importantly, what object Oracle is trying to apply the undo to. USE the following query to find out what object Oracle is trying to perform recovery on. select owner, object_name, object_type, status from dba_objects where object_id = ; THIS object must be dropped so the undo can be released. An export or relying on a backup may be necessary to restore the object after the corrupted rollback segment goes away. ----- Note: ----- Subject: Ora600-[Kcbbxsv_7] And Database Instance Crashed By Dbwr Process Doc ID: 443679.1 Type: PROBLEM Modified Date : 20-MAY-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 This problem can occur on any platform. Symptoms DBWR process terminated the DB instance with following error: ORA-00600: internal error code, arguments: [kcbbxsv_7], [0], [0] And the failing functions from the trace file are: "kcbbxsv kcbb_coalesce kcbbwlru" Cause This issue has been discussed in internal Bug: 4639623Abstract: ORA-600 [KCBBXSV_7] IN DBWR. Details from the Bug: Inside the function "kcbchg1_main", if flashback database is on, then it generates before image(if not previously generated since the barrier) for all blocks changed, including blocks intemporary segment. For a temporary buffer, the code erroneously checks if the buffer is dirtybefore generating flashback data, before the buffer is marked as dirty. As per the Bug: 1. The block is a temp block residing in a datafile, not tempfile. 2. The buffer is a current buffer, and is dirty, and has "redo_since_read" bit set. Solution The Bug: 4639623 has been fixed in version: 11.1.0 (11g) and this fix has been included in 10.1.0.5 (for 10gR1) and 10.2.0.2 (for 10gR2) patchsets. Check Metalink for Patch availability for your RDBMS and OS versions. References ----- Note: ----- Subject: ORA-600 [KEWUCMB_1], [0], [2] Unable to Extend Undo Segment Doc ID: 406614.1 Type: PROBLEM Modified Date : 30-APR-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.2 This problem can occur on any platform. Symptoms An undo segment fails to extend, yielding: ORA-00600: internal error code, arguments: [kewucmb_1], [0], [2], [], [], [], [], [] ORA-13509: error encountered during updates to a AWR table ORA-30036: unable to extend segment by ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1' in undo tablespace '' Cause This is due to unpublished bug 4440918. Abstract: ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KEWUCMB_1], [0], [2], [], [], [], [] Solution Unpublished bug 4440918 is fixed in 11g, but is backportable. A workaround is to set STATISTICS_LEVEL=BASIC to disable automatic database statistics collection. Alternatively, use MetaLink to determine if one-off Patch 4440918 is available for a specific platform. Otherwise, contact Oracle Support to request a backport. ----- Note: ----- XXX ----- Note: ----- Subject: Ora-7445 [KGHADJUST] Pmon Process Terminated And Instance Crashed Doc ID: 421947.1 Type: PROBLEM Modified Date : 12-OCT-2007 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.2 This problem can occur on any platform. Symptoms The following error(s) occurred in the alert log. ORA-00600: internal error code, arguments: [17147] ORA-10387: parallel query server interrupt (normal) ORA-07445: exception encountered: core dump [kqrpre1()+2780] ORA-07445: exception encountered: core dump [kghadjust()+120] Stack trace for the error ORA-07445 [kghadjust()+120] is similar to: kghadjust kghupr_flg kghupr kglophup kglHandleUnpin Cause This is unpublished Bug:4927533 - INSTANCE CRASHED WITH ORA-7445 [KGHADJUST], The bug is fixed in 11g. A workaround is avaliable. Solution Workaround: set _bloom_filter_enabled=FALSE. Setting the parameter _bloom_filter_enabled=FALSE may have a preformance impact, re-gather statistics on the object to resolve the performance issue. One-off patches may be available depending on your current release and operating system. To obtain a patch from MetaLink: 1) Click on 'Patches and Updates' 2) Click on 'Simple Search' 3) Enter patch number: 4927533 4) Select your O/S 5) Click Go. References Bug 5469910 - Abstract: INSTANCE CRASHED WITH ORA-7445 [KGHADJUST] ----- Note: ----- ORA-01653 ORA-1653 Note 1: ------- Doc ID : Note:151994.1 Content Type: TEXT/PLAIN Subject: Overview Of ORA-01653: Unable To Extend Table %s.%s By %s In Tablespace %s Creation Date: 12-JUL-2001 Type: TROUBLESHOOTING Last Revision Date: 15-JUN-2004 Status: PUBLISHED PURPOSE ------- This bulletin is an overview of ORA-1653 error message for tablespace dictionary managed. SCOPE& APPLICATION ------------------ It is for users requiring further information on ORA-01653 error message. When looking to resolve the error by using any of the solutions suggested, please consult the DBA for assistance. Error: ORA-01653 Text: unable to extend table %s.%s by %s in tablespace %s ------------------------------------------------------------------------------- Cause: Failed to allocate an extent for table segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. Explanation: ------------ This error does not necessarily indicate whether or not you have enough space in the tablespace, it merely indicates that Oracle could not find a large enough area of free contiguous space in which to fit the next extent. Diagnostic Steps: ----------------- 1. In order to see the free space available for a particular tablespace, you must use the view DBA_FREE_SPACE. Within this view, each record represents one fragment of space. How the view DBA_FREE_SPACE can be used to determine the space available in the database is described in: [NOTE:121259.1] Using DBA_FREE_SPACE 2. The DBA_TABLES view describes the size of next extent (NEXT_EXTENT) and the percentage increase (PCT_INCREASE) for all tables in the database. The "next_extent" size is the size of extent that is trying to be allocated (and for which you have the error). When the extent is allocated : next_extent = next_extent * (1 + (pct_increase/100)) Algorythm to allocate extent for segment is described in the Concept Guide Chapter : Data Blocks, Extents, and Segments - How Extents Are Allocated 3. Look to see if any users have the tablespace in question as their temporary tablespace. This can be checked by looking at DBA_USERS (TEMPORARY_TABLESPACE). Possible solutions: ------------------- - Manually Coalesce Adjacent Free Extents ALTER TABLESPACE COALESCE; The extents must be adjacent to each other for this to work. - Add a Datafile: ALTER TABLESPACE ADD DATAFILE '' SIZE ; - Resize the Datafile: ALTER DATABASE DATAFILE '' RESIZE ; - Enable autoextend: ALTER DATABASE DATAFILE '' AUTOEXTEND ON MAXSIZE UNLIMITED; - Defragment the Tablespace: - Lower "next_extent" and/or "pct_increase" size: ALTER STORAGE ( next pctincrease ); - If the tablespace is being used as a temporary tablespace, temporary segments may be still holding the space. References: ----------- [NOTE:1025288.6] How to Diagnose and Resolve ORA-01650, ORA-01652, ORA-01653, ORA-01654, ORA-01688 : Unable to Extend < OBJECT > by %S in Tablespace [NOTE:1020090.6] Script to Report on Space in Tablespaces [NOTE:1020182.6] Script to Detect Tablespace Fragmentation [NOTE:1012431.6] Overview of Database Fragmentation [NOTE:121259.1] Using DBA_FREE_SPACE [NOTE:61997.1] SMON - Temporary Segment Cleanup and Free Space Coalescing Note 2: ------- Doc ID : Note:1025288.6 Content Type: TEXT/PLAIN Subject: How to Diagnose and Resolve ORA-01650,ORA-01652,ORA-01653,ORA-01654,ORA-01688 : Unable to Extend < OBJECT > by %S in Tablespace %S Creation Date: 02-JAN-1997 Type: TROUBLESHOOTING Last Revision Date: 10-JUN-2004 Status: PUBLISHED PURPOSE ------- This document can be used to diagnose and resolve space management errors - ORA-1650, ORA-1652, ORA-1653, ORA-1654 and ORA-1688. SCOPE & APPLICATION ------------------- You are working with the database and have encountered one of the following errors: ORA-01650: unable to extend rollback segment %s by %s in tablespace %s Cause: Failed to allocate extent for the rollback segment in tablespace. Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace. ORA-01652: unable to extend temp segment by %s in tablespace %s Cause: Failed to allocate an extent for temp segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated or create the object in other tablespace. ORA-01653: unable to extend table %s.%s by %s in tablespace %s Cause: Failed to allocate extent for table segment in tablespace. Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace. ORA-01654: unable to extend index %s.%s by %s in tablespace %s Cause: Failed to allocate extent for index segment in tablespace. Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the specified tablespace. ORA-01688: unable to extend table %s.%s partition %s by %s in tablespace %s Cause: Failed to allocate an extent for table segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. How to Solve the Following Errors About UNABLE TO EXTEND -------------------------------------------------------- An "unable to extend" error is raised when there is insufficient contiguous space available to extend the object. A. In order to address the UNABLE TO EXTEND issue, you need to get the following information: 1. The largest contiguous space available for the tablespace SELECT max(bytes) FROM dba_free_space WHERE tablespace_name = ''; The above query returns the largest available contiguous chunk of space. Please note that if the tablespace you are concerned with is of type TEMPORARY, then please refer to [NOTE:188610.1] . If this query is done immediately after the failure, it will show that the largest contiguous space in the tablespace is smaller than the next extent the object was trying to allocate. 2. => "next_extent" for the object => "pct_increase" for the object => The name of the tablespace in which the object resides Use the "next_extent" size with "pct_increase" in the following formula to determine the size of extent that is trying to be allocated. extent size = next_extent * (1 + (pct_increase/100) next_extent = 512000 pct_increase = 50 => extent size = 512000 * (1 + (50/100)) = 512000 * 1.5 = 768000 ORA-01650 Rollback Segment ========================== SELECT next_extent, pct_increase, tablespace_name FROM dba_rollback_segs WHERE segment_name = ''; Note: pct_increase is only needed for early versions of Oracle, by default in later versions pct_increase for a rollback segment is 0. ORA-01652 Temporary Segment =========================== SELECT next_extent, pct_increase, tablespace_name FROM dba_tablespaces WHERE tablespace_name = ''; Temporary segments take the default storage clause of the tablespace in which they are created. If this error is caused by a query, then try and ensure that the query is tuned to perform its sorts as efficiently as possible. To find the owner of a sort, please refer to [NOTE:1069041.6] ORA-01653 Table Segment ======================= SELECT next_extent, pct_increase , tablespace_name FROM dba_tables WHERE table_name = '' AND owner = ''; ORA-01654 Index Segment ======================= SELECT next_extent, pct_increase, tablespace_name FROM dba_indexes WHERE index_name = '' AND owner = ''; ORA-01688 Table Partition ========================= SELECT next_extent, pct_increase, tablespace_name FROM dba_tab_partitions WHERE partition_name='' AND table_owner = ''; B. Possible Solutions There are several options for solving errors due to failure to extend: a. Manually Coalesce Adjacent Free Extents --------------------------------------- ALTER TABLESPACE COALESCE; The extents must be adjacent to each other for this to work. b. Add a Datafile -------------- ALTER TABLESPACE ADD DATAFILE '' SIZE ; c. Lower "next_extent" and/or "pct_increase" size ---------------------------------------------- For non-temporary and non-partitioned segment problem: ALTER STORAGE ( next pctincrease ); For non-temporary and partitioned segment problem: ALTER TABLE MODIFY PARTITION STORAGE ( next pctincrease ); For a temporary segment problem: ALTER TABLESPACE DEFAULT STORAGE (initial next pctincrease ); d. Resize the Datafile ------------------- ALTER DATABASE DATAFILE '' RESIZE ; e. Defragment the Tablespace ------------------------- If you would like more information on fragmentation, the following documents are available from Oracle WorldWide Support . (this is not a comprehensive list) [NOTE:1020182.6] Script to Detect Tablespace Fragmentation [NOTE:1012431.6] Overview of Database Fragmentation [NOTE:30910.1] Recreating Database Objects Related Documents: ================== [NOTE:15284.1] Understanding and Resolving ORA-01547 Overview Of ORA-01653 Unable To Extend Table %s.%s By %s In Tablespace %s: Overview Of ORA-01654 Unable To Extend Index %s.%s By %s In Tablespace %s: [NOTE:188610.1] DBA_FREE_SPACE Does not Show Information about Temporary Tablespaces [NOTE:1069041.6] How to Find Creator of a SORT or TEMPORARY SEGMENT or Users Performing Sorts for Oracle8 and 9 Search Words: ============= ORA-1650 ORA-1652 ORA-1653 ORA-1654 ORA-1688 ORA-01650 ORA-01652 ORA-01653 ORA-01654 ORA-01688 1650 1652 1653 1654 1688 ----- Note: ----- Doc ID : Note:201342.1 Content Type: TEXT/X-HTML Subject: Top Internal Errors - Oracle Server Release 9.2.0 Creation Date: 27-JUN-2002 Type: BULLETIN Last Revision Date: 24-MAY-2004 Status: PUBLISHED Top Internal Errors - Oracle Server Release 9.2.0 Additional information or documentation on ORA-600 errors not listed here may be available from the ORA-600 Lookup tool : > > Oracle9i Release 2 (9.2) Support Status and Alerts ORA-600 [KSLAWE:!PWQ] Possible bugs: Fixed in: > BACKGROUND PROCESS GOT OERI:KSLAWE:!PWQ AND INSTANCE CRASHES 9.2.0.6, 10G References: > ALERT: ORA-600[KSLAWE:!PWQ] RAISED IN V92040 OR V92050 ON SUN 64BIT ORACLE ORA-600 [ksmals] Possible bugs: Fixed in: > ORA-7445 & HEAP CORRUPTION WHEN RUNNING APPS PROGRAM THAT DOES HEAVY INSERTS 9.2.0.4 References: > ORA-600 [ksmals] ORA-600 [4000] Possible bugs: Fixed in: > STARTUP after an ORA-701 fails with OERI[4000] 9.2.0.5, 10G > OERI:4506 / OERI:4000 possible against transported tablespace 8.1.7.4, 9.0.1.4, 9.2.0.1 References: > ORA-600 [4000] "trying to get dba of undo segment header block from usn" ORA-600 [4454] Possible bugs: Fixed in: > OERI:4411/OERI:4454 on long running job 8.1.7.3, 9.0.1.3, 9.2.0.1 References: > ORA-600 [4454] ORA-600 [kcbgcur_9] Possible bugs: Fixed in: > OERI:kcbgcur_9 on direct load into AUTO space managed segment 9.2.0.4, 10G > Direct path load may fail with OERI:kcbgcur_9 / OERI:ktfduedel2 9.2.0.4, 10G > OERI:KCBGCUR_9 possible from SMON dropping a rollback segment in locally managed tablespace 9.0.1.4, 9.2.0.1 > OERI:KCBGCUR_9 possible during TEMP space operations 9.0.1.3, 9.2.0.1 > OERI:KCBGCUR_9 possible from ONLINE REBUILD INDEX with concurrent DML 8.1.7.3, 9.0.1.3, 9.2.0.1 > OERI:kcbgcur_9 from CLOB TO CHAR or BLOB TO RAW conversion 9.2.0.2, 10G References: > ORA-600 [kcbgcur_9] "Block class pinning violation" ORA-600 [qerrmOFBu1], [1003] Possible bugs: Fixed in: > SQL*PLUS CRASH IN TTC LOGGING INTO ORACLE 7.3.4 DATABASE References: > ORA-600 [qerrmOFBu1] - "Error during remote row fetch operation > ALERT: Connections from Oracle 9.2 to Oracle7 are Not Supported ORA-600 [ktsgsp5] or ORA-600 [kdddgb2] Possible bugs: Fixed in: > ORA-600 [KDDDGB2] [435816] [2753588] & PROBABLE INDEX CORRUPTION 9.2.0.2 References: > ORA-600 [kdddgb2] > ORA-600 [ktsgsp5] > ALERT: Corruption / Internal Errors possible after Upgrading to 9.2.0.1 ----- Note: ----- ADJUST SCN: =========== Note 1 Adjust SCN: ------------------ Doc ID: Note:30681.1 Subject: EVENT: ADJUST_SCN - Quick Reference Type: REFERENCE Status: PUBLISHED Content Type: TEXT/PLAIN Creation Date: 20-OCT-1997 Last Revision Date: 04-AUG-2000 Language: USAENG ADJUST_SCN Event ~~~~~~~~~~~~~~~~ *** WARNING *** This event should only ever be used under the guidance of an experienced Oracle analyst. If an SCN is ahead of the current database SCN, this indicates some form of database corruption. The database should be rebuilt after bumping the SCN. **************** The ADJUST_SCN event is useful in some recovery situations where the current SCN needs to be incremented by a large value to ensure it is ahead of the highest SCN in the database. This is typically required if either: a. An ORA-600 [2662] error is signalled against database blocks or b. ORA-1555 errors keep occuring after forcing the database open or ORA-604 / ORA-1555 errors occur during database open. (Note: If startup reports ORA-704 & ORA-1555 errors together then the ADJUST_SCN event cannot be used to bump the SCN as the error is occuring during bootstrap. Repeated startup/shutdown attempts may help if the SCN mismatch is small) or c. If a database has been forced open used _ALLOW_RESETLOGS_CORRUPTION (See ) The ADJUST_SCN event acts as described below. **NOTE: You can check that the ADJUST_SCN event has fired as it should write a message to the alert log in the form "Debugging event used to advance scn to %s". If this message is NOT present in the alert log the event has probably not fired. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If the database will NOT open: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Take a backup. You can use event 10015 to trigger an ADJUST_SCN on database open: startup mount; alter session set events '10015 trace name adjust_scn level 1'; (NB: You can only use IMMEDIATE here on an OPEN database. If the database is only mounted use the 10015 trigger to adjust SCN, otherwise you get ORA 600 [2251], [65535], [4294967295] ) alter database open; If you get an ORA 600:2256 shutdown, use a higher level and reopen. Do *NOT* set this event in init.ora or the instance will crash as soon as SMON or PMON try to do any clean up. Always use it with the "alter session" command. ~~~~~~~~~~~~~~~~~~~~~~~~~~ If the database *IS* OPEN: ~~~~~~~~~~~~~~~~~~~~~~~~~~ You can increase the SCN thus: alter session set events 'IMMEDIATE trace name ADJUST_SCN level 1'; LEVEL: Level 1 is usually sufficient - it raises the SCN to 1 billion (1024*1024*1024) Level 2 raises it to 2 billion etc... If you try to raise the SCN to a level LESS THAN or EQUAL to its current setting you will get - See below. Ie: The event steps the SCN to known levels. You cannot use the same level twice. Calculating a Level from 600 errors: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To get a LEVEL for ADJUST_SCN: a) Determine the TARGET scn: ora-600 [2662] See Use TARGET >= blocks SCN ora-600 [2256] See Use TARGET >= Current SCN b) Multiply the TARGET wrap number by 4. This will give you the level to use in the adjust_scn to get the correct wrap number. c) Next, add the following value to the level to get the desired base value as well : Add to Level Base ~~~~~~~~~~~~ ~~~~~~~~~~~~ 0 0 1 1073741824 2 2147483648 3 3221225472 Note 2: Adjust SCN ------------------ Subject: OERR: 600 2662 Block SCN is ahead of Current SCN Creation Date: 21-OCT-1997 ORA-00600 ORA-600 ORA-600 [2662] [a] [b] [c] [d] [e] Versions: 7.0.16 - 8.0.5 Source: kcrf.h =========================================================================== Meaning: There are 3 forms of this error. 4/5 argument forms - The SCN found on a block (dependant SCN) was ahead of the current SCN. See below for this 1 Argument (before 7.2.3): Oracle is in the process of writing a block to a log file. If the calculated block checksum is less than or equal to 1 (0 and 1 are reserved) ORA-600 [2662] is returned. This is a problem generating an offline immediate log marker (kcrfwg). *NOT DOCUMENTED HERE* --------------------------------------------------------------------------- Argument Description: Until version 7.2.3 this internal error can be logged for two separate reasons, which we will refer to as type I and type II. The two types can be distinguished by the number of arguments: Type I has four or five arguments after the [2662]. Type II has one argument after the [2662]. From 7.2.3 onwards type II no longer exists. Type I ~~~~~~ a. Current SCN WRAP b. Current SCN BASE c. dependant SCN WRAP d. dependant SCN BASE e. Where present this is the DBA where the dependant SCN came from. From kcrf.h: If the SCN comes from the recent or current SCN then a dba of zero is saved. If it comes from undo$ because the undo segment is not available then the undo segment number is saved, which looks like a block from file 0. If the SCN is for a media recovery redo (i.e. block number == 0 in change vector), then the dba is for block 0 of the relevant datafile. If it is from another database for distribute xact then dba is DBAINF(). If it comes from a TX lock then the dba is really usn<<16+slot. Type II ~~~~~~~ a. checksum -> log block checksum - zero if none (thread # in old format) --------------------------------------------------------------------------- Diagnosis: ~~~~~~~~~~ In addition to different basic types from above, there are different situations and coherences where ORA-600 [2662] type 'I' can be raised. For diagnosis we can split up startup-issues and no-startup-issues. Usually the startup-issues are more critical. Getting started: ~~~~~~~~~~~~~~~~ (1) is the error raised during normal database operations (i.e. when the database is up) or during startup of the database? (2) what is the SCN difference [d]-[b] ( subtract argument 'b' from arg 'd')? (3) is there a fifth argument [e] ? If so convert the dba to file# block# Is it a data dictionary object? (file#=1) If so find out object name with the help of reference dictionary from second database (4) What is the current SQL statement? (see trace) Which table is refered to? Does the table match the object you found in step before? Be careful at this point: there may be no relationship between DBA in [e] and real source of problem (blockdump). Deeper analysis: ~~~~~~~~~~~~~~~~ - investigate trace file this will be a user trace file normally but could be an smon trace too - search for: 'buffer' ("buffer dba" in Oracle7 dumps, "buffer tsn" in Oracle8 dumps) this will bring you to a blockdump which usually represents the 'real' source of OERI:2662 WARNING: There may be more than one buffer pinned to the process so ensure you check out all pinned buffers. -> does the blockdump match the dba from e.? -> what kind of blockdump is it? (a) rollbacksegment header (b) datablock (c) other SEE BELOW for EXAMPLES which demonstrate the sort of output you may see in trace files and the things to check. Check list and possible causes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - If Parallel Server check both nodes are using the same lock manager instance & point at the same control files. - If not Parallel Server check that 2 instances haven't mounted the same database (Is there a second PMON process around ?? - shut down any other instances to be sure) Possible causes: - doing an open resetlogs with _ALLOW_RESETLOGS_CORRUPTION enabled - a hardware problem, like a faulty controller, resulting in a failed write to the control file or the redo logs - restoring parts of the database from backup and not doing the appropriate recovery - restoring a control file and not doing a RECOVER DATABASE USING BACKUP CONTROLFILE - having _DISABLE_LOGGING set during crash recovery - problems with the DLM in a parallel server environment - a bug Solutions: - if the SCNs in the error are very close: Attempting a startup several times will bump up the dscn every time we open the database even if open fails. The database will open when dscn=scn. - ** You can bump the SCN on open using See [NOTE:30681.1] Be aware that you should really rebuild the database if you use this option. - Once this has occurred you would normally want to rebuild the database via exp/rebuild/imp as there is no guarantee that some other blocks are not ahead of time. Articles: ~~~~~~~~~ Solutions: [NOTE:30681.1] Details of the ADJUST_SCN Event [NOTE:1070079.6] alter system checkpoint Possible Causes: [NOTE:1021243.6] CHECK INIT.ORA SETTING _DISABLE_LOGGING [NOTE:74903.1] How to Force the Database Open (_ALLOW_RESETLOGS_CORRUPTION) [NOTE:41399.1] Forcing the database open with `_ALLOW_RESETLOGS_CORRUPTION` [NOTE:851959.9] OERI:2662 DURING CREATE SNAPSHOT AT MASTER SITE Known Bugs: ~~~~~~~~~~~ Fixed In. Bug No. Description ---------+------------+---------------------------------------------------- 7.0.14 BUG:153638 7.1.5 BUG:229873 7.1.3 Bug:195115 Miscalculation of SCN on startup for distributed TX ? 7.1.6.2.7 Bug:297197 Port specific Solaris OPS problem 7.3 Bug:336196 Port specific IBM SP AIX problem -> dlm issue 7.3.4.5 Bug:851959 OERI:2662 possible from distributed OPS select --------------------------------------------------------------------------- --------------------------------------------------------------------------- Examples: ~~~~~~~~ Below are some examples of this type of error and the information you will see in the trace files. ~~~~~~~~~~ CASE (a) ~~~~~~~~~~ blockdump should look like this: *** buffer dba: 0x05000002 inc: 0x00000001 seq: 0x0001a9c6 ver: 1 type: 1=KTU UNDO HEADER Extent Control Header ----------------------------------------------------------------- Extent Control:: inc#: 716918 tsn: 4 object#: 0 *** -> interpret: dba: 0x05000002 -> 83886082 (0x05000002) = 5,2 XXX tsn: 4 -> this is rollback segment 4 tsn: 4 -> this rollback segment is in tablespace 4 ORA-00600: Interner Fehlercode, Argumente: [2662], [0], [71183], [0], [71195], [83886082], [], [] -> [e] > 0 and represents dba from block which is in trace -> [d]-[b] = 71195 - 71183 = 12 -> convert [b] to hex: 71195 = 0x1161B so this value can be found in blockdump: *** TRN TBL:: index state cflags wrap# uel scn dba ------------------------------------------------------------------ ... 0x4e 9 0x00 0x00d6 0xffff 0x0000.0001161b 0x00000000 ... *** -> possible cause so in this case the CURRENT SCN is LOWER than the SCN on this transaction ie: The current SCN looks like it has decreased !! This could happen if the database is opened with the _allow_resetlogs_corruption parameter -> If some recovery steps have just been performed review these steps as the mismatch may be due to open resetlogs with _allow_resetlogs_corruption enabled or similar. See for information on this parameter. ------------------------------------------------------------------ ~~~~~~~~~~ CASE (b) ~~~~~~~~~~ blockdump looks like this: *** buffer dba: 0x0100012f inc: 0x00000815 seq: 0x00000d48 ver: 1 type: 6=trans data Block header dump: dba: 0x0100012f Object id on Block? Y seg/obj: 0xe csc: 0x00.5fed6 itc: 2 flg: O typ: 1 - DATA fsl: 0 fnx: 0x0 Itl Xid Uba Flag Lck Scn/Fsc 0x01 0x0000.00b.0000036c 0x0100261c.0138.04 --U- 1 fsc 0x0000.0005fed7 0x02 0x0000.00a.0000037b 0x0100261d.0138.01 --U- 1 fsc 0x0000.0005fed4 data_block_dump =============== ... *** interpret: dba: 0x0100012f -> 8,10 ==> 16777519 (0x0100012f) = 1,303 (0x1 0x12f) *** SVRMGR> SELECT SEGMENT_NAME, SEGMENT_TYPE FROM DBA_EXTENTS 2> WHERE FILE_ID = 1 AND 303 BETWEEN BLOCK_ID AND 3> BLOCK_ID + BLOCKS - 1; SEGMENT_NAME SEGMENT_TYPE ---------------------------------------------------------- ----------------- UNDO$ TABLE 1 row selected. *** -> current sql-statement (trace): *** update undo$ set name=:2,file#=:3,block#=:4,status$=:5,user#=:6, undosqn=:7,xactsqn=:8,scnbas=:9,scnwrp=:10,inst#=:11 where us#=:1 ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [2662], [0], [392916], [0], [392919], [0], [], [] *** -> e. = 0 info not available -> d-b = 392919 - 392916 = 3 -> dba from blockdump matches the object from current sql statement -> convert b. to hex: = 0x5FED7 so this value can be found in blockdump -> see ITL slot 0x01! --------------------------------------------------------------------------- --------------------------------------------------------------------------- --------------------------------------------------------------------------- Some more internals: ~~~~~~~~~~~~~~~~~~~~ I will try to give another example in oder to answer question if current SCN is decreased or dependant SCN increase. hypothesis: current SCN decreased Evidence: reproduced ORA-600 [2662] by aborting tx and using _allow_resetlog_corruption while open resetlogs. check database SCN before! Prerequisits: _allow_resetlogs_corruption = true in init.ora shutdown/startup db *** BEGIN TESTCASE SVRMGR> drop table tx; Statement processed. SVRMGR> create table tx (scn# number); Statement processed. SVRMGR> insert into tx values( userenv('COMMITSCN') ); 1 row processed. SVRMGR> select * from tx; SCN# ---------- 392942 1 row selected. ************ another session ************** SQL> connect scott/tiger Connected. SQL> update emp set sal=sal+1; 13 rows processed. SQL> -- no commit here ******************************************* SVRMGR> insert into tx values( userenv('COMMITSCN') ); 1 row processed. SVRMGR> select * from tx; SCN# ---------- 392942 392943 2 rows selected. -- so current SCN will be 392943 SVRMGR> shutdown abort ORACLE instance shut down. -- this breaks tx SVRMGR> startup mount pfile=e:\jv734\initj734.ora ORACLE instance started. Total System Global Area 11018952 bytes Fixed Size 35760 bytes Variable Size 7698200 bytes Database Buffers 3276800 bytes Redo Buffers 8192 bytes Database mounted. SVRMGR> recover database until cancel; ORA-00279: Change 392925 generated at 10/26/99 17:13:03 needed for thread 1 ORA-00289: Suggestion : e:\jv734\arch\arch_2.arc ORA-00280: Change 392925 for thread 1 is in sequence #2 Specify log: {=suggested | filename | AUTO | CANCEL} cancel Media recovery cancelled. SVRMGR> alter database open resetlogs; alter database open resetlogs * ORA-00600: internal error code, arguments: [2662], [0], [392928], [0], [392931], [0], [], [] *** END TESTCASE because we know current SCN before (392943) we see, that current SCN has decreased after solving the problem with: shutdown abort/startup -> works SVRMGR> drop table tx; Statement processed. SVRMGR> create table tx (scn# number); Statement processed. SVRMGR> insert into tx values( userenv('COMMITSCN') ); 1 row processed. SVRMGR> select * from tx; SCN# ---------- 392943 1 row selected. so we have exactly reached the current SCN from before 'shutdown abort' So current SCN was bumpt up from 392928 to 392942. Note 3: Adjust SCN ------------------ Doc ID : Note:28929.1 Content Type: TEXT/X-HTML Subject: ORA-600 [2662] "Block SCN is ahead of Current SCN" Creation Date: 21-OCT-1997 Type: REFERENCE Last Revision Date: 15-OCT-2004 Status: PUBLISHED This note contains information that was not reviewed by DDR. As such, the contents are not necessarily accurate and care should be taken when dealing with customers who have encountered this error. Thanks. PAA Internals Group Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article discusses the internal error "ORA-600 [2662]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [2662] [a] [b] [c] [d] [e] VERSIONS: versions 6.0 to 10.1 DESCRIPTION: A data block SCN is ahead of the current SCN. The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in a UGA variable. If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error. ARGUMENTS: Arg [a] Current SCN WRAP Arg [b] Current SCN BASE Arg [c] dependent SCN WRAP Arg [d] dependent SCN BASE Arg [e] Where present this is the DBA where the dependent SCN came from. FUNCTIONALITY: File and IO buffer management for redo logs IMPACT: INSTANCE FAILURE POSSIBLE PHYSICAL CORRUPTION SUGGESTIONS: There are different situations where ORA-600 [2662] can be raised. It can be raised on startup or duing database operation. If not using Parallel Server, check that 2 instances have not mounted the same database. Check for SMON traces and have the alert.log and trace files ready to send to support. Check the SCN difference [argument d]-[argument b]. If the SCNs in the error are very close, then try to shutdown and startup the instance several times. In some situations, the SCN increment during startup may permit the database to open. Keep track of the number of times you attempted a startup. If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 2899477 See Note 2899477.8 Minimise risk of a false OERI[2662] Fixed: 9.2.0.5, 10.1.0.2 Bug# 2764106 See Note 2764106.8 False OERI[2662] possible on SELECT which can crash the instance Fixed: 9.2.0.5, 10.1.0.2 Bug# 2054025 See Note 2054025.8 OERI:2662 possible on new TEMPORARY index block Fixed: 9.0.1.3, 9.2.0.1 Bug# 851959 See Note 851959.8 OERI:2662 possible from distributed OPS select Fixed: 7.3.4.5 Bug# 647927 P See Note 647927.8 Digital Unix ONLY: OERI:2662 could occur under heavy load Fixed: 8.0.4.2, 8.0.5.0 INTERNAL ONLY SECTION - NOT FOR PUBLICATION OR DISTRIBUTION TO CUSTOMERS ======================================================================== There were 2 forms of this error until 7.2.3: Type I: 4/5 argument forms - The SCN found on a block (dependent SCN) is ahead of the current SCN. See below for this Type II: 1 Argument (before 7.2.3 only): Oracle is in the process of writing a block to a log file. If the calculated block checksum is less than or equal to 1 (0 and 1 are reserved) ORA-600 [2662] is returned. This is a problem generating an offline immediate log marker (kcrfwg). *NOT DOCUMENTED HERE* Type I ~~~~~~ a. Current SCN WRAP b. Current SCN BASE c. dependent SCN WRAP d. dependent SCN BASE e. Where present this is the DBA where the dependent SCN came from. From kcrf.h: If the SCN comes from the recent or current SCN then a dba of zero is saved. If it comes from undo$ because the undo segment is not available then the undo segment number is saved, which looks like a block from file 0. If the SCN is for a media recovery redo (i.e. block number == 0 in change vector), then the dba is for block 0 of the relevant datafile. If it is from another database for a distributed transaction then dba is DBAINF(). If it comes from a TX lock then the dba is really usn<<16+slot. Type II ~~~~~~~ a. checksum -> log block checksum - zero if none (thread # in old format) --------------------------------------------------------------------------- Diagnosis: ~~~~~~~~~~ In addition to different basic types from above, there are different situations where ORA-600 [2662] type I can be raised. Getting started: ~~~~~~~~~~~~~~~~ (1) is the error raised during normal database operations (i.e. when the database is up) or during startup of the database? (2) what is the SCN difference [d]-[b] ( subtract argument 'b' from arg 'd')? (3) is there a fifth argument [e] ? If so convert the dba to file# block# Is it a data dictionary object? (file#=1) If so find out object name with the help of reference dictionary from second database (4) What is the current SQL statement? (see trace) Which table is refered to? Does the table match the object you found in previous step? Be careful at this point: there may be no relationship between DBA in [e] and the real source of problem (blockdump). Deeper analysis: ~~~~~~~~~~~~~~~~ (1) investigate trace file: this will be a user trace file normally but could be an smon trace too (2) search for: 'buffer' ("buffer dba" in Oracle7 dumps, "buffer tsn" in Oracle8/Oracle9 dumps) this will bring you to a blockdump which usually represents the 'real' source of OERI:2662 WARNING: There may be more than one buffer pinned to the process so ensure you check out all pinned buffers. -> does the blockdump match the dba from e.? -> what kind of blockdump is it? (a) rollback segment header (b) datablock (c) other Check list and possible causes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If Parallel Server check both nodes are using the same lock manager instance & point at the same control files. Possible causes: (1) doing an open resetlogs with _ALLOW_RESETLOGS_CORRUPTION enabled (2) a hardware problem, like a faulty controller, resulting in a failed write to the control file or the redo logs (3) restoring parts of the database from backup and not doing the appropriate recovery (4) restoring a control file and not doing a RECOVER DATABASE USING BACKUP CONTROLFILE (5) having _DISABLE_LOGGING set during crash recovery (6) problems with the DLM in a parallel server environment (7) a bug Solutions: (1) if the SCNs in the error are very close, attempting a startup several times will bump up the dscn every time we open the database even if open fails. The database will open when dscn=scn. (2)You can bump the SCN either on open or while the database is open using (see Note 30681.1 ). Be aware that you should rebuild the database if you use this option. Once this has occurred you would normally want to rebuild the database via exp/rebuild/imp as there is no guarantee that some other blocks are not ahead of time. Articles: ~~~~~~~~~ Solutions: Note 30681.1 Details of the ADJUST_SCN Event Note 1070079.6 Alter System Checkpoint Possible Causes: Note 1021243.6 CHECK INIT.ORA SETTING _DISABLE_LOGGING Note 41399.1 Forcing the database open with `_ALLOW_RESETLOGS_CORRUPTION` Note 851959.9 OERI:2662 DURING CREATE SNAPSHOT AT MASTER SITE Known Bugs: ~~~~~~~~~~~ Fixed In. Bug No. Description ---------+------------+---------------------------------------------------- 7.1.5 Bug 229873 7.1.3 Bug 195115 Miscalculation of SCN on startup for distributed TX ? 7.1.6.2.7 Bug 297197 Port specific Solaris OPS problem 7.3 Bug 336196 Port specific IBM SP AIX problem -> dlm issue 7.3.4.5 Bug 851959 OERI:2662 possible from distributed OPS select Not fixed Bug 2216823 OERI:2662 reported when reusing tempfile with restored DB 8.1.7.4 Bug 2177050 OERI:729 space leak possible (with tags "define var info"/"oactoid info") can corrupt UGA and cause OERI:2662 --------------------------------------------------------------------------- Ensure that this note comes out on top in Metalink when searched ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 2662 in file header does not match given name You are certain that the file is good and that it belongs to that database. Solution: Check the file's properties in Windows Explorer and verify that it is not a "Hidden" file. Explanation: If you have set the "Show All Files' option under Explorer, View, Options, you are able to see 'hidden' files that other users and/or applications cannot. If any or all datafiles are marked as 'hidden' files, Oracle does not see them when it tries to recreate the controlfile. You must change the properties of the file by right-clicking on the file in Windows Explorer and then deselecting the check box marked "Hidden" under the General tab. You should then be able to create the controlfile. References: Note 1084048.6 ORA-01503, ORA-01161: on Create Controlfile. Note 2: ======= This message may result, if the db_name in the init.ora does not match with the set "db_name" given while creating the controlfile. Also, remove any old controlfiles present in the specified directory. Thanks, Note 3: ======= We ran into a similar problem when trying to create a new instance with datafiles from another database. The error comes in the create control file statement. Oracle uses REUSE as the default option when you do the alter database backup controlfile to trace. If you delete REUSE then the new database name you will change all the header information in all the database datafiles and you will be able to start up the instance. Hope this helps. Note 4: ======= Try this command "CREATE CONTROLFILE SET DATABASE..." instead of "CREATE CONTROLFILE REUSE DATABASE..." I think it would be better. ----- Note: ----- ORA-01031 ========= ORA-1031 ORA-01031 Note 1: ------- The 'OSDBA' and 'OSOPER' groups are chosen at installation time and usually both default to the group 'dba'. These groups are compiled into the 'oracle' executable and so are the same for all databases running from a given ORACLE_HOME directory. The actual groups being used for OSDBA and OSOPER can be checked thus: cd $ORACLE_HOME/rdbms/lib cat config.[cs] The line '#define SS_DBA_GRP "group"' should name the chosen OSDBA group. The line '#define SS_OPER_GRP "group"' should name the chosen OSOPER group. Note 2: ------- Bookmark Fixed font Go to End Doc ID: Note:69642.1 Content Type: TEXT/PLAIN Subject: UNIX: Checklist for Resolving Connect AS SYSDBA Issues Creation Date: 20-APR-1999 Type: TROUBLESHOOTING Last Revision Date: 31-DEC-2004 Status: PUBLISHED Introduction: ~~~~~~~~~~~~~ This bulletin lists the documented causes of getting ---> prompted for a password when trying to CONNECT as SYSDBA ---> errors such as ORA-01031, ORA-01034, ORA-06401, ORA-03113,ORA-09925, ORA-09817, ORA-12705, ORA-12547 a) SQLNET.ORA Checks: --------------------- 1. The "sqlnet.ora" can be found in the following locations (listed by search order): $TNS_ADMIN/sqlnet.ora $HOME/sqlnet.ora $ORACLE_HOME/network/admin/sqlnet.ora Depending upon your operating system, it may also be located in: /var/opt/oracle/sqlnet.ora /etc/sqlnet.ora A corrupted "sqlnet.ora" file, or one with security options set, will cause a 'connect internal' request to prompt for a password. To determine if this is the problem, locate the "sqlnet.ora" that is being used. The one being used will be the first one found according to the search order listed above. Next, move the file so that it will not be found by this search: % mv sqlnet.ora sqlnet.ora_save Try to connect internal again. If it still fails, search for other "sqlnet.ora" files according to the search order listed above and repeat using the move command until you are sure there are no other "sqlnet.ora" files being used. If this does not resolve the issue, use the move command to put all the "sqlnet.ora" files back where they were before you made the change: % mv sqlnet.ora_save sqlnet.ora If moving the "sqlnet.ora" resolves the issue, then verify the contents of the file: a) SQLNET.AUTHENTICATION_SERVICES If you are not using database links, comment this line out or try setting it to: SQLNET.AUTHENTICATION_SERVICES = (BEQ,NONE) b) SQLNET.CRYPTO_SEED This should not be set in a "sqlnet.ora" file on UNIX. If it is, comment the line out. (This setting is added to the "sqlnet.ora" if it is built by one of Oracle's network cofiguration products shipped with client products) c) AUTOMATIC_IPC If this is set to "ON" it can force a "TWO_TASK" connection. Try setting this to "OFF": AUTOMATIC_IPC = OFF 2. Set the permissions correctly in the "TNS_ADMIN" files. The environment variable TNS_ADMIN defines the directory where the "sqlnet.ora", "tnsnames.ora", and "listener.ora" files reside. These files must contain the correct permissions, which are set when "root.sh" runs during installation. As root, run "root.sh" or edit the permissions on the "sqlnet.ora", "tnsnames.ora", and "listener.ora" files by hand as follows: $ cd $TNS_ADMIN $ chmod 644 sqlnet.ora tnsnames.ora listener.ora $ ls -l sqlnet.ora tnsnames.ora listener.ora -rw-r--r-- 1 oracle dba 1628 Jul 12 15:25 listener.ora -rw-r--r-- 1 oracle dba 586 Jun 1 12:07 sqlnet.ora -rw-r--r-- 1 oracle dba 82274 Jul 12 15:23 tnsnames.ora b) Software and Operating System Issues: ---------------------------------------- 1. Be sure $ORACLE_HOME is set to the correct directory and does not have any typing mistakes: % cd $ORACLE_HOME % pwd If this returns a location other than your "ORACLE_HOME" or is invalid, you will need to reset the value of this environment variable: sh or ksh: ---------- $ ORACLE_HOME= $ export ORACLE_HOME Example: $ ORACLE_HOME=/u01/app/oracle/product/7.3.3 $ export ORACLE_HOME csh: ---- % setenv ORACLE_HOME Example: % setenv ORACLE_HOME /u01/app/oracle/product/7.3.3 If your "ORACLE_HOME" contains a link or the instance was started with the "ORACLE_HOME" set to another value, the instance may try to start using the memory location that another instance is using. An example of this might be: You have "ORACLE_HOME" set to "/u01/app/oracle/product/7.3.3" and start the instance. Then you do something like: % ln -s /u01/app/oracle/product/7.3.3 /u01/app/oracle/7.3.3 % setenv ORACLE_HOME /u01/app/oracle/7.3.3 % svrmgrl SVRMGR> connect internal If this prompts for a password then most likely the combination of your "ORACLE_HOME" and "ORACLE_SID" hash to the same shared memory address of another running instance. Otherwise you may be able to connect internal but you will receive an ORA-01034 "Oracle not available" error. In most cases using a link as part of your "ORACLE_HOME" is fine as long as you are consistent. Oracle recommends that links not be used as part of the "ORACLE_HOME", but their use is supported. 2. Check that $ORACLE_SID is set to the correct SID, (including capitalization), and does not have any typos: % echo $ORACLE_SID Refer to Note:1048876.6 for more information. 3. Ensure $TWO_TASK is not set. To check if "TWO_TASK" is set, do the following: sh, ksh or on HP/UX only csh: ----------------------------- env |grep -i two - or - echo $TWO_TASK csh: ---- setenv |grep -i two If any lines are returned such as: TWO_TASK= - or - TWO_TASK=PROD You will need to unset the environment variable "TWO_TASK": sh or ksh: ---------- unset TWO_TASK csh: ---- unsetenv TWO_TASK Example : $ TWO_TASK=V817 $ export TWO_TASK $ sqlplus /nolog SQL*Plus: Release 8.1.7.0.0 - Production on Fri Dec 31 10:12:25 2004 (c) Copyright 2000 Oracle Corporation. All rights reserved. SQL> conn / as sysdba ERROR: ORA-01031: insufficient privileges $ unset TWO_TASK $ sqlplus /nolog SQL> conn / as sysdba Connected. If you are running Oracle release 8.0.4, and upon starting "svrmgrl" you receive an ORA-06401 "NETCMN: invalid driver designator" error, you should also unset two_task. The login connect string may be getting its value from the TWO_TASK environment variable if this is set for the user. 4. Check the permissions on the Oracle executable: % cd $ORACLE_HOME/bin % ls -l oracle ('ls -n oracle' should work as well) The permissions should be rwsr-s--x, or 6751. If the permissions are incorrect, do the following as the "oracle" software owner: % chmod 6751 oracle If you receive an ORA-03113 "end-of-file on communication" error followed by a prompt for a password, then you may also need to check the ownership and permissions on the dump directories. These directories must belong to Oracle, group dba, (or the appropriates names for your installation). This error may occur while creating a database. Permissions should be: 755 (drwxr-xr-x) Also, the alert.log must not be greater than 2 Gigabytes in size. When you start up "nomount" an Oracle pseudo process will try to write the "alert.log" file in "udump". When Oracle cannot do this (either because of permissions or because of the "alert.log" being greater than 2 Gigabytes in size), it will issue the ORA-03113 error. 5. "osdba" group checks: a. Make sure the operating system user issuing the CONNECT INTERNAL belongs to the "osdba" group as defined in the "$ORACLE_HOME/rdbms/lib/config.s" or "$ORACLE_HOME/rdbms/lib/config.c". Typically this is set to "dba". To verify the operating system groups the user belongs to, do the following: % id uid=1030(oracle) gid=1030(dba) The "gid" here is "dba" so the "config.s" or "config.c" may contain an entry such as: /* 0x0008 15 */ .ascii "dba\0" If these do not match, you either need to add the operating system user to the group as it is seen in the "config" file, or modify the "config" file and relink the "oracle" binary. Refer to entry [NOTE:50507.1] section 3 for more details. b. Be sure you are not logged in as the "root" user and that the environment variables "USER", "USERNAME", and "LOGNAME" are not set to "root". The "root" user is a special case and cannot connect to Oracle as the "internal" user unless the effective group is changed to the "osdba" group, which is typically "dba". To do this, either modify the "/etc/password" file (not recommended) or use the "newgrp" command: # newgrp dba "newgrp" always opens a new shell, so you cannot issue "newgrp" from within a shell script. Keep this in mind if you plan on executing scripts as the "root" user. c. Verify that the "osdba" group is only listed once in the "/etc/group" file: % grep dba /etc/group dba::1010: dba::1100: If more than one line starting with the "osdba" group is returned, you need to remove the ones that are not correct. It is not possible to have more than one group use a group name. d. Check that the oracle user uid and gid are matching with /etc/passwd and /etc/group : $ id uid=500(oracle) gid=235(dba) $ grep oracle /etc/passwd oracle:x:500:235:oracle:/home/oracle:/bin/bash ^^^ $ grep dba /etc/group dba:x:253:oracle ^^^ The mismatch also causes an ORA-1031 error. 6. Verify that the file system is not mounted no set uid: % mount /u07 on /dev/md/dsk/d7 nosuid/read/write If the filesytem is mounted "nosuid", as seen in this example, you will need to unmount the filesystem and mount it without the "nosuid" option. Consult your operating system documentation or your operating system vendor for instruction on modifying mount options. 7. Please read the following warning before you attempt to use the information in this step: ****************************************************************** * * * WARNING: If you remove segments that belong to a running * * instance you will crash the instance, and this may * * cause database corruption. * * * * Please call Oracle Support Services for assistance * * if you have any doubts about removing shared memory * * segments. * * * ****************************************************************** If an instance crashed or was killed off using "kill" there may be shared memory segments hanging around that belong to the down instance. If there are no other instances running on the machine you can issue: % ipcs -b T ID KEY MODE OWNER GROUP SEGSZ Shared Memory: m 0 0x50000ffe --rw-r--r-- root root 68 m 1601 0x0eedcdb8 --rw-r----- oracle dba 4530176 In this case the "ID" of "1601" is owned by "oracle" and if there are no other instances running in most cases this can safely be removed: % ipcrm -m 1601 If your SGA is split into multiple segments you will have to remove all segments associated with the instance. If there are other instances running, and you are not sure which memory segments belong to the failed instance, you can do the following: a. Shut down all the instances on the machine and remove whatever shared memory still exists that is owned by the software owner. b. Reboot the machine. c. If your Oracle software is release 7.3.3 or newer, you can connect into each instance that is up and identify the shared memory owned by that instance: % svrmgrl SVRMGR> connect internal SVRMGR> oradebug ipc In Oracle8: ----------- Area #0 `Fixed Size', containing Subareas 0-0 Total size 000000000000b8c0, Minimum Subarea size 00000000 Subarea Shmid Size Stable Addr 0 7205 000000000000c000 80000000 In Oracle7: ----------- -------------- Shared memory -------------- Seg Id Address Size 2016 80000000 4308992 Total: # of segments = 1, size = 4308992 Note the "Shmid" for Oracle8 and "Seg Id" for Oracle7 for each running instance. By process of elimination find the segments that do not belong to an instance and remove them. 8. If you are prompted for a password and then receive error ORA-09925 "unable to create audit trail file" or error ORA-09817 "write to audit file failed", along with "SVR4 Error: 28: No space left on device", do the following: Check your "pfile". It is typically in the "$ORACLE_HOME/dbs" directory and will be named "init.ora, where "" is the value of "ORACLE_SID" in your environment. If the "init.ora" file has the "ifile" parameter set, you will also have to check the included file as well. You are looking for the parameter "audit_file_dest". If "audit_file_dest" is set, change to that directory; otherwise change to the "$ORACLE_HOME/rdbms/audit" directory, as this is the default location for audit files. If the directory does not exist, create it. Ensure that you have enough space to create the audit file. The audit file is generally 600 bytes in size. If it does exist, verify you can write to the directory: % touch afile If it could not create the called "afile", you need to change the permissions on your audit directory: % chmod 751 9. If connect internal prompts you for a password and then you receive an ORA-12705 "invalid or unknown NLS parameter value specified" error, you need to verify the settings for "ORA_NLS", "ORA_NLS32", "ORA_NLS33" or "NLS_LANG". You will need to consult your Installation and Configuration Guide for the proper settings for these environment variables. 10. If you have installed Oracle software and are trying to connect with Server Manager to create or start the database, and receive a TNS-12571 "packet writer failure" error, please refer to Note:1064635.6 11. If in SVRMGRL (Server Manager line mode), you are running the "startup.sql" script and receive the following error: ld:so.1: oracle_home/bin/svrmgrl fatal relocation error symbol not found kgffiop RDBMS v7.3.2 is installed. RDBMS v8.0.4 is a separate "oracle_home", and you are attempting to have it coexist. This is due to the wrong version of the client shared library "libclntsh.so.1" being used at runtime. Verify environment variable settings. You need to ensure that "ORACLE_HOME" and "LD_LIBRARY_PATH" are set correctly. For C-shell, type: % setenv LD_LIBRARY_PATH $ORACLE_HOME/lib % setenv ORACLE_HOME /u01/app/oracle/product/8.0.4 For Bourne or Korn shell, type: $ LD_LIBRARY_PATH=$ORACLE_HOME/lib $ export LD_LIBRARY_PATH $ ORACLE_HOME=/u01/app/oracle/product/8.0.4 $ export ORACLE_HOME 12. Ensure that the disk the instance resides on has not reached 100% capacity. % df -k If it has reached 100% capacity, this may be the cause of 'connect internal' prompting for a password. Additional disk space will need to be made available before 'connect internal' will work. For additional information refer to Note:97849.1 13. Delete process.dat and regid.dat files in $ORACLE_HOME/otrace/admin directory. Oracle Trace is enabled by default on 7.3.2 and 7.3.3 (depends on platform) This can caused high disk space usage by these files and cause a number of apparently mysterious side effects. See Note:45482.1 for more details. 14. When you get ora-1031 "Insufficient privileges" on connect internal after you supply a valid password and you have multiple instances running from the same ORACLE_HOME, be sure that if an instance has REMOTE_LOGIN_PASSWORDFILE set to exclusive that the file $ORACLE_HOME/dbs/orapw does exist, otherwise it defaults to the use of the file orapw that consequently causes access problems for any other database that has the parameter set to shared. Set the parameter REMOTE_LOGIN_PASSWORDFILE to shared for all instances that share the common password file and create an exclusive orapw password files for any instances that have this set to exclusive. 15. Check permissions on /etc/passwd file (Unix only). If Oracle cannot open the password file, connect internal fails with ORA-1031, since Oracle is not able to verify if the user trying to connect is indeed in the dba group. Example: -------- # chmod 711 /etc/passwd # ls -ltr passwd -rwx--x--x 1 root sys 901 Sep 21 14:26 passwd $ sqlplus '/ as sysdba' SQL*Plus: Release 9.2.0.1.0 - Production on Sat Sep 21 16:21:18 2002 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. ERROR: ORA-01031: insufficient privileges Trussing sqlplus will show also the problem: 25338: munmap(0xFF210000, 8192) = 0 25338: lwp_mutex_wakeup(0xFF3E0778) = 0 25338: lwp_mutex_lock(0xFF3E0778) = 0 25338: time() = 1032582594 25338: open("/etc/passwd", O_RDONLY) Err#13 EACCES 25338: getrlimit(RLIMIT_NOFILE, 0xFFBE8B28) = 0 c) Operating System Specific checks: ------------------------------------ 1. On OpenVMS, check that the privileges have been granted at the Operating System level: $ SET DEFAULT SYS$SYSTEM: $ RUN AUTHORIZE If the list returned by AUTHORIZE does not contain ORA__DBA, or ORA_DBA, then you do not have the correct OS privileges to issue a connect internal. If ORA__DBA was added AFTER ORA_DBA, then ORA_DBA needs to be removed and granted again to be updated. Please refer to Note:1010852.6 for more details. 2. On Windows NT, check if DBA_AUTHORIZATION is set to BYPASS in the registry. 3. On Windows NT, if you are able to connect internally but then startup fails for some reason, successive connect internal attempts might prompt for a password. You may also receive errors such as: ORA-12705: invalid or unknown NLS parameter value specified ORA-01012: not logged on LCC-00161: Oracle error (possible syntax error) ORA-01031: insufficient privileges Refer to entry Note:1027964.6 for suggestions on how to resolve this problem 4. If you are using Multi-Threaded Server (MTS), make sure you are using a dedicated server connection. A dedicated server connection is required to start up or shutdown the database. Unless the database alias in the "TNSNAMES.ORA" file includes a parameter to make a dedicated server connection, it will make a shared connection to a dispatcher. See Note:1058680.6 for more details. 5. On Solaris, if the file "/etc/.name_service_door" has incorrect permissions, Oracle cannot read the file. You will receive a message that "The Oracle user cannot access "/etc/.name_service_door" (permission denied). This file is a flavor of IPC specific to Solaris which Oracle software is using This can also cause connect internal problems. See entry Note:1066589.6 6. You are on Digital Unix, running SVRMGRL (Server Manager line mode), and you receive an ORA-12547 "TNS:lost contact" error and a password prompt. This problem occurs when using Parallel Server and the True Cluster software together. If Parallel Server is not linked in, svrmgrl works as expected. Oracle V8.0.5 requires an Operating System patch which previous versions of Oracle did not require. The above patch allows svrmgrl to communicate with the TCR software. You can determine if the patch is applied by running: % nm /usr/ccs/lib/libssn.a | grep adjust If this returns nothing, then you need to: 1. Obtain the patch for TCR 1.5 from Digital. This patch is for the MC SCN and adds the symbol "adjustSequenceNumber" to the library /usr/ccs/lib/libssn.a. 2. Apply the patch. 3. Relink Oracle Another possibility is that you need to raise the value of kernel parameter per-proc-stack-size when increased from its default value of 2097152 to 83886080 resolved this problem. 7. You are on version 6.2 of the Silicon Graphics UNIX (IRIX) operating system and you have recently installed RDBMS release 8.0.3. If you are logged on as "oracle/dba" and an attempt to log in to Server Manager using "connect/internal" prompts you for a password, you should refer to entry Note:1040607.6 8. On AIX 4.3.3 after applying ML5 or higher you can not longer connect as internal or if on 9.X '/ as sysdba' does not work as well. This is a known AIX bug and it occurs on all RS6000 ports including SP2. There is two workarounds and one solution. They are as follows: 1) Use mkpasswd command to remove the index. This is valid until a new user is added to "/etc/passwd" or modified: # mkpasswd -v -d 2) Touch the "/etc/passwd" file. If the "/etc/passwd" file is newer than the index it will not use the password file index: # touch /etc/passwd 3) Obtain APAR IY22458 from IBM. Any questions about this APAR should be directed to IBM. d) Additional Information: -------------------------- 1. In the "Oracle7 Administrator's Reference for UNIX", there is a note that states: If REMOTE_OS_AUTHENT is set to true, users who are members of the dba group on the remote machine are able to connect as INTERNAL without a password. However, if you are connecting remotely, that is connecting via anything except the bequeath adapter, you will be prompted for a password regardless of the value of "REMOTE_OS_AUTHENT". Refer to bug 644988 References: ~~~~~~~~~~~ [NOTE:1048876.6] UNIX: Connect internal prompts for password after install [NOTE:1064635.6] ORA-12571: PACKET WRITER FAILURE WHEN STARTING SVRMGR [NOTE:1010852.6] OPENVMS: ORA-01031: WHEN ISSUING "CONNECT INTERNAL" IN SQL*DBA OR SERVER MANAGER [NOTE:1027964.6] LCC-00161 AND ORA-01031 ON STARTUP [NOTE:1058680.6] ORA-00106 or ORA-01031 ERROR when trying to STARTUP or SHUTDOWN DATABASE [NOTE:1066589.6] UNIX: Connect Internal asks for password when TWO_TASK is set [NOTE:1040607.6] SGI: ORA-01012 ORA-01031: WHEN USING SRVMGR AFTER 8.0.3 INSTALL [NOTE:97849.1] Connect internal Requires Password [NOTE:50507.1] SYSDBA and SYSOPER Privileges in Oracle8 and Oracle7 [NOTE:18089.1] UNIX: Connect INTERNAL / AS SYSBDA Privilege on Oracle 7/8 [BUG:644988] REMOTE_OS_AUTHENT=TRUE: NOT ALLOWING USERS TO CONNECT INTERNAL WITHOUT PASSWORD Search Words: ~~~~~~~~~~~~~ svrmgrm sqldba sqlplus sqlnet remote_login_passwordfile Note 3: ------- ORA-01031: insufficient privileges Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. Action: Ask the database administrator to perform the operation or grant the required privileges. Note 4: ------- ORA-01031: insufficient privileges In most cases, the user receiving this error lacks a privilege to create an object (such as a table, view, procedure and the like). Grant the required privilege like so: grant create table to user_lacking_privilege; Startup If someone receives this error while trying to startup the instance, the logged on user must belong to the ora_dba group on Windows or dba group on Unix. Note 5: ------- I am not sure it is the same, but I got this error today in windows when sql_authentication in sqlnet.ora was NONE. Changing it to NTS solved the problem. ----- Note: ----- ORA-00600: internal error code, arguments: [17059]: =================================================== Note 1: ------- Doc ID : Note:138554.1 Content Type: TEXT/PLAIN Subject: ORA-600 [17059] Creation Date: 02-APR-2001 Type: REFERENCE Last Revision Date: 09-DEC-2004 Status: PUBLISHED Note: For additional ORA-600 related information please read [NOTE:146580.1] PURPOSE: This article discusses the internal error "ORA-600 [17059]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [17059] [a] VERSIONS: versions 7.1 to 10.1 DESCRIPTION: While building a table to hold the list of child cursor dependencies relating to a given parent cursor, we exceed the maximum possible size of the table. ARGUMENTS: Arg [a] Object containing the table FUNCTIONALITY: Kernel Generic Library cache manager IMPACT: PROCESS FAILURE NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: One symptom of this error is that the session will appear to hang for a period of time prior to this error being reported. If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Issuing this SQL as SYS (SYSDBA) may help show any problem objects in the dictionary: select do.obj#, po.obj# , p_timestamp, po.stime , decode(sign(po.stime-p_timestamp),0,'SAME','*DIFFER*') X from sys.obj$ do, sys.dependency$ d, sys.obj$ po where P_OBJ#=po.obj#(+) and D_OBJ#=do.obj# and do.status=1 /*dependent is valid*/ and po.status=1 /*parent is valid*/ and po.stime!=p_timestamp /*parent timestamp not match*/ order by 2,1 ; Normally the above select would return no rows. If any rows are returned the listed dependent objects may need recompiling. Known Issues: Bug# 3555003 See [NOTE:3555003.8] View compilation hangs / OERI:17059 after DBMS_APPLY_ADM.SET_DML_HANDLER Fixed: 9.2.0.6 Bug# 2707304 See [NOTE:2707304.8] OERI:17059 / OERI:kqlupd2 / PLS-907 after adding partitions to Partitioned IOT Fixed: 9.2.0.3, 10.1.0.2 Bug# 2636685 See [NOTE:2636685.8] Hang / OERI:[17059] after adding a list value to a partition Fixed: 9.2.0.3, 10.1.0.2 Bug# 2626347 See [NOTE:2626347.8] OERI:17059 accessing view after ADD / SPLIT PARTITION Fixed: 9.2.0.3, 10.1.0.2 Bug# 2306331 See [NOTE:2306331.8] Hang / OERI[17059] on view after SET_KEY or SET_DML_INVOKATION on base table Fixed: 9.2.0.2 Bug# 1115424 See [NOTE:1115424.8] Cursor authorization and dependency lists too long - can impact shared pool / OERI:17059 Fixed: 8.0.6.2, 8.1.6.2, 8.1.7.0 Bug# 631335 See [NOTE:631335.8] OERI:17059 from extensive re-user of a cursor Fixed: 8.0.4.2, 8.0.5.0, 8.1.5.0 Bug# 558160 See [NOTE:558160.8] OERI:17059 from granting privileges multiple times Fixed: 8.0.3.2, 8.0.4.0, 8.1.5.0 Note 2: ------- Doc ID : Note:234457.1 Content Type: TEXT/X-HTML Subject: ORA-600 [17059] Error When Compiling A Package Creation Date: 19-FEB-2003 Type: PROBLEM Last Revision Date: 24-AUG-2004 Status: PUBLISHED fact: fact: Oracle Server - Enterprise Edition fact: Partitioned Tables / Indexes symptom: ORA-600 [17059] Error When Compiling A Package symptom: When Compiling a Package symptom: The Package Accesses a Partitioned Table symptom: ORA-00600: internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s] symptom: internal error code, arguments: [17059], [352251864] symptom: Calling Location kglgob symptom: Calling Location kgldpo symptom: Calling Location kgldon symptom: Calling Location pkldon symptom: Calling Location pkloud symptom: Calling Location - phnnrl_name_resolve_by_loading cause: This is due to > fixed in 10i, and occurs when accessing a partitioned table via a dblink within the package, where DDL (such as adding/dropping partitions) is performed on the table. fix: This is fixed in 9.0.1.4, 9.2.0.2 & 10i. One-off patches are available for 8.1.7.4. A workaround is to flush the shared pool. Note 3: ------- Doc ID : Note:239796.1 Content Type: TEXT/PLAIN Subject: ORA-600 [17059] when querying dba_tablespaces, dba_indexes, dba_ind_partitions etc Creation Date: 28-MAY-2003 Type: PROBLEM Last Revision Date: 13-AUG-2004 Status: PUBLISHED Problem: ~~~~~~~~ The information in this article applies to: Internal Error ORA-600 [17059] when querying Data dictionary views like dba_tablespaces, dba_indexes, dba_ind_partitions etc Symptom(s) ~~~~~~~~~~ While querying Data dictionary views like dba_tablespaces, dba_indexes, dba_ind_partitions etc, getting internal error ORA-600 [17059] Change(s) ~~~~~~~~~~ You probably altered some objects or executed some cat*.sql scripts. Cause ~~~~~~~ Some SYS objects are INVALID. Fix ~~~~ Connect SYS run $ORACLE_HOME/rdbms/admin/utlrp.sql and make sure all the objects are valid. ----- Note: ----- ORA-00600: internal error code, arguments: [17003] ================================================== ORA-600 ORA-00600 Note 1: ------- The information in this article applies to: Oracle Forms - Version: 9.0.2.7 to 9.0.2.12 Oracle Server - Enterprise Edition - Version: 9.2 This problem can occur on any platform. Errors ORA 600 "internal error code, arguments: [%s],[%s],[%s], [%s], [%s], Symptoms The following error occurs when compiling a form or library ( fmb / pll ) against RDBMS 9.2 PL/SQL ERROR 0 at line 0, column 0 ORA-00600: internal error code, arguments: [17003], [0x11360BC], [275], [1], [], [], [], [] The error reproduces everytime. Triggers / local program units in the form / library contain calls to stored database procedures and / or functions. The error does not occur when compiling against RDBMS 9.0.1 or lower. Cause This is a known bug / issue. The compilation error occurs when the form contains a call to a stored database function / procedure which has two DATE IN variables receiving DEFAULT values such as SYSDATE. Reference: Abstract: INTERNAL ERROR [1401] WHEN COMPILE FUNCTION WITH 2 DEFAULT DATE VARIABLES ON 9.2 Fix The bug is fixed in Oracle Forms 10g (9.0.4). There is no backport fix available for Forms 9i (9.0.2) To work-around, modify the offending calls to the stored database procedure/ functions so that DEFAULT parameter values are not passed directly . For example, pass the DEFAULT value SYSDATE indirectly to the stored database procedure/ function by first assigning it to a local variable in the form. Note 2: ------- Doc ID : Note:138537.1 Content Type: TEXT/PLAIN Subject: ORA-600 [17003] Creation Date: 02-APR-2001 Type: REFERENCE Last Revision Date: 15-OCT-2004 Status: PUBLISHED Note: For additional ORA-600 related information please read [NOTE:146580.1] PURPOSE: This article discusses the internal error "ORA-600 [17003]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [17003] [a] [b] [c] VERSIONS: versions 7.0 to 10.1 DESCRIPTION: The error indicates that we have tried to lock a library cache object by using the dependency number to identify the target object and have found that no such dependency exists. Under this situation we will raise an ORA-600 [17003] if the dependency number that we are using exceeds the number of entries in the dependency table or the dependency entry is not marked as invalidated. ARGUMENTS: Arg [a] Library Cache Object Handle Arg [b] Dependency number Arg [c] 1 or 2 (indicates where the error was raised internally) FUNCTIONALITY: Kernel Generic Library cache manager IMPACT: PROCESS MEMORY FAILURE NO UNDERLYING DATA CORRUPTION. SUGGESTIONS: A common condition where this error is seen is problematic upgrades. If a patchset has recently been applied, please confirm that there were no errors associated with this upgrade. Specifically, there are some XDB related bugs which can lead to this error being reported. Known Issues: Bug# 2611590 See [NOTE:2611590.8] OERI:[17003] running XDBRELOD.SQL Fixed: 9.2.0.3, 10.1.0.2 Bug# 3073414 XDB may not work after applying a 9.2 patch set Fixed: 9.2.0.5 ----- Note: ----- ORA-00600: internal error code, arguments: [qmxiUnpPacked2], [121], [], [], [], [], [], [] ========================================================================================== Note 1. ------- Doc ID: Note:222876.1 Content Type: TEXT/PLAIN Subject: ORA-600 [qmxiUnpPacked2] Creation Date: 09-DEC-2002 Type: REFERENCE Last Revision Date: 15-OCT-2004 Status: PUBLISHED Note: For additional ORA-600 related information please read [NOTE:146580.1] PURPOSE: This article discusses the internal error "ORA-600 [qmxiUnpPacked2]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [qmxiUnpPacked2] [a] VERSIONS: versions 9.2 to 10.1 DESCRIPTION: When unpickling an XOB or an array of XOBs an unexpected datatype was found. Generally due to XMLType data that has not been successfully upgraded from a previous version. ARGUMENTS: Arg [a] Type of XOB FUNCTIONALITY: Qernel xMl support Xob to/from Image IMPACT: PROCESS FAILURE NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: Please review the following article on Metalink : [NOTE:235423.1] How to resolve ORA-600 [qmxiUnpPacked2] during upgrade If you still encounter the error having tried the suggestions in the above article, or the article isn't applicible to your environment then ensure that the upgrade to current version was completed succesfully without error. If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 2607128 See [NOTE:2607128.8] OERI:[qmxiUnpPacked2] if CATPATCH.SQL/XDBPATCH.SQL fails Fixed: 9.2.0.3 Bug# 2734234 CONSOLIDATION BUG FOR ORA-600 [QMXIUNPPACKED2] DURING CATPATCH.SQL 9.2.0.2 Note 2. ------- Doc ID: Note:235423.1 Content Type: TEXT/X-HTML Subject: How to resolve ORA-600 [qmxiUnpPacked2] during upgrade Creation Date: 14-APR-2003 Type: HOWTO Last Revision Date: 18-MAR-2005 Status: PUBLISHED The information in this article applies to: Oracle 9.2.0.2 Multiple Platforms, 64-bit Symptom(s) ~~~~~~~~~~ ORA-600 [qmxiUnpPacked2] [] Cause ~~~~~ If the error is seen after applying 9.2.0.2 on a 9.2.0.1 database or if using DBCA in 9.2.0.2 to create a new database (which is using the 9.2.0.1 seed database) then it is very likely that either shared_pool_size or java_pool_size was too small when catpatch.sql was executed. Error is generally seen as ORA-600: internal error code, arguments: [qmxiUnpPacked2], [121] There are 3 options to proceed from here:- Fix ~~~~ Option 1 ======== If your shared_pool_size and java_pool_size are less than 150Mb the do the following :- 1/ Set your shared_pool_size and java_pool_size to 150Mb each. In some case you may need to use larger pool sizes. 2/ Get the xdbpatch.sql script from Note 237305.1 3/ Copy xdbpatch.sql to $ORACLE_HOME/rdbms/admin/xdbpatch.sql having taken a backup of the original file first 4/ Restart the instance with: startup migrate; 5/ spool catpatch @?/rdbms/admin/catpatch.sql Option 2 ======== If you already have shared_pool_size and java_pool_size set at greater than 150Mb then the problem may be caused by the shared memory allocated during the JVM upgrade is not released properly. In which case do the following :- 1/ Set your shared_pool_size and java_pool_size to 150Mb each. In some case you may need to use larger pool sizes. 2/ Get the xdbpatch.sql script from Note 237305.1 3/ Edit the xdbpatch.sql script and add the following as the first line in the script:- alter system flush shared_pool; 3/ Copy xdbpatch.sql to $ORACLE_HOME/rdbms/admin/xdbpatch.sql having taken a backup of the original file first 3/ Restart the instance with: startup migrate; 4/ spool catpatch @?/rdbms/admin/catpatch.sql Option 3 ======== If XDB is NOT in use and there are NO registered XML Schemas an alternative is to drop, and maybe re-install XDB :- 1/ To drop the XDB subsystem connect as sys and run @?/rdbms/admin/catnoqm.sql 2/ You can then run catpatch.sql to perform the upgrade startup migrate; @?/rdbms/admin/catpatch.sql 3/ Once complete you may chose to re-install the XDB subsystem, if so connect as sys and run catqm.sql @?/rdbms/admin/catqm.sql If the error is seen during normal database operation, ensure that upgrade to current version was completed succesfully without error. Once this is confirmed attempt to reproduce the error, if successful forward ALERT.LOG, trace files and full error stack to Oracle Support Services for further analysis. References ~~~~~~~~~~~ Bug 2734234 CONSOLIDATION BUG FOR ORA-600 [QMXIUNPPACKED2] DURING CATPATCH.SQL 9.2.0.2 Note 237305.1 Modified xdbpatch.sql ----- Note: ----- ORA-00600: internal error code, arguments: [kcbget_37], [1], [], [], [], [], [], [] ==================================================================================== ORA-600 ORA-00600 ORA-00600: internal error code, arguments: [kcbso1_1], [], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [kcbget_37], [1], [], [], [], [], [], [] Doc ID: Note:2652771.8 Subject: Support Description of Bug 2652771 Type: PATCH Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 13-AUG-2003 Last Revision Date: 14-AUG-2003 Click here for details of sections in this note. Bug 2652771 AIX: OERI[1100] / OERI[KCBGET_37] SGA corruption This note gives a brief overview of bug 2652771. Affects: Product (Component) Oracle Server (RDBMS) Range of versions believed to be affected Versions < 10G Versions confirmed as being affected 8.1.7.4 9.2.0.2 Platforms affected Aix 64bit 5L Aix 64bit 433 Fixed: This issue is fixed in 9.2.0.3 (Server Patch Set) Symptoms: Memory Corruption Internal Error may occur (ORA-600) ORA-600 [1100] / ORA-600 [kcbget_37] Known Issues: Bug# 2652771 P See [NOTE:2652771.8] AIX: OERI[1100] / OERI[KCBGET_37] SGA corruption Fixed: 9.2.0.3 ----- Note: ----- ORA-00600: internal error code, arguments: [kcbzwb_4], [], [], [], [], [], [], [] ================================================================================= Doc ID: Note:4036717.8 Subject: Bug 4036717 - Truncate table in exception handler can causes OERI:kcbzwb_4 Type: PATCH Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 25-FEB-2005 Last Revision Date: 09-MAR-2005 Click here for details of sections in this note. Bug 4036717 Truncate table in exception handler can causes OERI:kcbzwb_4 This note gives a brief overview of bug 4036717. Affects: Product (Component) PL/SQL (Plsql) Range of versions believed to be affected Versions < 10.2 Versions confirmed as being affected 10.1.0.3 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.2.0.7 (Server Patch Set) 10.1.0.4 (Server Patch Set) 10g Release 2 (future version) Symptoms: Related To: Internal Error May Occur (ORA-600) ORA-600 [kcbzwb_4] PL/SQL Truncate Description Truncate table in exception handler can cause OERI:kcbzwb_4 with the fix for bug 3768052 installed. Workaround: Turn off or deinstall the fix for bug 3768052. Note that the procedure containing the affected transactional commands will have to be recompiled after backing out the bug fix. Doc ID: Note:4036717.8 Subject: Bug 4036717 - Truncate table in exception handler can causes OERI:kcbzwb_4 Type: PATCH Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 25-FEB-2005 Last Revision Date: 09-MAR-2005 Click here for details of sections in this note. Bug 4036717 Truncate table in exception handler can causes OERI:kcbzwb_4 This note gives a brief overview of bug 4036717. Affects: Product (Component) PL/SQL (Plsql) Range of versions believed to be affected Versions < 10.2 Versions confirmed as being affected 10.1.0.3 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.2.0.7 (Server Patch Set) 10.1.0.4 (Server Patch Set) 10g Release 2 (future version) Symptoms: Related To: Internal Error May Occur (ORA-600) ORA-600 [kcbzwb_4] PL/SQL Truncate Description Truncate table in exception handler can cause OERI:kcbzwb_4 with the fix for bug 3768052 installed. Workaround: Turn off or deinstall the fix for bug 3768052. Note that the procedure containing the affected transactional commands will have to be recompiled after backing out the bug fix. ----- Note: ----- ORA-00600: internal error code, arguments: [kcbgtcr_6], [], [], [], [], [], [], [] ================================================================================== Doc ID: Note:248874.1 Subject: ORA-600 [kcbgtcr_6] Type: REFERENCE Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 18-SEP-2003 Last Revision Date: 25-MAR-2004 This note contains information that has not yet been reviewed by DDR. As such, the contents are not necessarily accurate and care should be taken when dealing with customers who have encountered this error. Thanks. PAA Internals Group Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article discusses the internal error "ORA-600 [kcbgtcr_6]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [kcbgtcr_6] [a] VERSIONS: versions 8.0 to 10.1 DESCRIPTION: Two buffers have been found in the buffer cache that are both current and for the same DBA (Data Block Address). We should not have two 'current' buffers for the same DBA in the cache, if this is the case then this error is raised. ARGUMENTS: Arg [a] Buffer class Note that for Oracle release 9.2 and earlier there are no additional arguments reported with this error. FUNCTIONALITY: Kernel Cache Buffer management IMPACT: PROCESS FAILURE POSSIBLE INSTANCE FAILURE NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: Retry the operation. Does the error still occur after an instance bounce? If using 64bit AIX then ensure that minimum version in use is 9.2.0.3 or patch for Bug 2652771 has been applied. If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug 2652771 Shared data structures corrupted around latch code on 64bit AIX ports. Fixed 9.2.0.3 backports available for older versions (8.1.7) from Metalink. ORA-600 [kcbgtcr_6] Versions: 8.0.5 - 10.1 Source: kcb.c Meaning: We have two 'CURRENT' buffers for the same DBA. Argument Description: None --------------------------------------------------------------------------- Explanation: We have identified two 'CURRENT' buffers for the same DBA in the cache, this is incorrect, and this error will be raised. --------------------------------------------------------------------------- Diagnosis: Check the trace file, this will show the buffers i.e :- BH (0x70000003ffe9800) file#: 39 rdba: 0x09c131e6 (39/78310) class 1 ba: 0x70000003fcf0000 set: 6 dbwrid: 0 obj: 11450 objn: 11450 hash: [70000000efa9b00,70000004d53a870] lru: [70000000efa9b68,700000006fb8d68] ckptq: [NULL] fileq: [NULL] st: XCURRENT md: NULL rsop: 0x0 tch: 1 LRBA: [0x0.0.0] HSCN: [0xffff.ffffffff] HSUB: [255] RRBA: [0x0.0.0] BH (0x70000000efa9b00) file#: 39 rdba: 0x09c131e6 (39/78310) class 1 ba: 0x70000000e4f6000 set: 6 dbwrid: 0 obj: 11450 objn: 11450 hash: [70000004d53a870,70000003ffe9800] lru: [700000012fbaf68,70000003ffe9868] ckptq: [NULL] fileq: [NULL] st: XCURRENT md: NULL rsop: 0x0 tch: 2 LRBA: [0x0.0.0] HSCN: [0xffff.ffffffff] HSUB: [255] RRBA: [0x0.0.0] Here it is clear that we have two current buffers for the dba. Most likely cause for this is 64bit AIX Bug 2652771. If this isn't the case check the error reproduces consistently after bouncing the instance? Via SQLplus? What level of concurrency to reproduce? Is a testcase available? Check OS memory for errors. --------------------------------------------------------------------------- Known Bugs: Bug 2652771 Shared data structures corrupted around latch code on 64bit AIX ports. - Fixed 9.2.0.3, backports available for older versions. ----- Note: ----- ORA-00600: internal error code, arguments: [1100], [0x7000002FDF83F40], [0x7000002FDF83F40], [], [], [], [], [] =============================================================================================================== Doc ID: Note:138123.1 Subject: ORA-600 [1100] Type: REFERENCE Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 28-MAR-2001 Last Revision Date: 08-FEB-2005 Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article discusses the internal error "ORA-600 [1100]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [1100] [a] [b] [c] [d] [e] VERSIONS: versions 6.0 to 9.2 DESCRIPTION: This error relates to the management of standard double-linked (forward and backward) lists. Generally, if the list is damaged an attempt to repair the links is performed. Additional information will accompany this internal error. A dump of the link and often a core dump will coincide with this error. This is a problem with a linked list structure in memory. FUNCTIONALITY: GENERIC LINKED LISTS IMPACT: PROCESS FAILURE POSSIBLE INSTANCE FAILURE IF DETECTED BY PMON PROCESS No underlying data corruption. SUGGESTIONS: Known Issues: Bug# 3724548 See Note 3724548.8 OERI[kglhdunp2_2] / OERI[1100] under high load Fixed: 9.2.0.6, 10.1.0.4, 10.2 Bug# 3691672 + See Note 3691672.8 OERI[17067]/ OERI[26599] / dump (kgllkdl) from JavaVM / OERI:1100 from PMON Fixed: 10.1.0.4, 10.2 Bug# 2652771 P See Note 2652771.8 AIX: OERI[1100] / OERI[KCBGET_37] SGA corruption Fixed: 9.2.0.3 Bug# 1951929 See Note 1951929.8 ORA-7445 in KQRGCU/kqrpfr/kqrpre possible Fixed: 8.1.7.3, 9.0.1.2, 9.2.0.1 Bug# 959593 See Note 959593.8 CTRL-C During a truncate crashes the instance Fixed: 8.1.6.3, 8.1.7.0 INTERNAL ONLY SECTION - NOT FOR PUBLICATION OR DISTRIBUTION TO CUSTOMERS No internal information at the present time. Ensure that this note comes out on top in Metalink when searched ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 ora-600 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 1100 Note 2: ------- Doc ID: Note:3724548.8 Subject: Bug 3724548 - OERI[kglhdunp2_2] / OERI[1100] under high load Type: PATCH Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 24-SEP-2004 Last Revision Date: 13-JAN-2005 Click here for details of sections in this note. Bug 3724548 OERI[kglhdunp2_2] / OERI[1100] under high load This note gives a brief overview of bug 3724548. Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions < 10.2 Versions confirmed as being affected 9.2.0.4 9.2.0.5 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.2.0.6 (Server Patch Set) 10.1.0.4 (Server Patch Set) 10g Release 2 (future version) Symptoms: Related To: Memory Corruption Internal Error May Occur (ORA-600) ORA-600 [kglhdunp2_2] ORA-600 [1100] (None Specified) Description When an instance is under high load it is possible for sessions to get ORA-600[KGLHDUNP2_2] and ORA-600 [1100] errors. This can also show as a corrupt linked list in the SGA. The full bug text (if published) can be seen at (This link will not work for UNPUBLISHED bugs) You can search for any interim patches for this bug here (This link will Error if no interim patches exist) ----- Note: ----- Compilation problems DBI DBD: ============================= We upgraded Oracle from 8.1.6 to 9.2.0.5 and I tried to rebuild the DBD::Oracle module but it threw errors like: . gcc: unrecognized option `-q64' ld: 0711-736 ERROR: Input file /lib/crt0_64.o: XCOFF64 object files are not allowed in 32-bit mode. collect2: ld returned 8 exit status make: 1254-004 The error code from the last command is 1. Stop. After some digging I found out that this is because the machine is AIX 5.2 running under 32-bit and it is looking at the oracle's lib directory which has 64 bit libraries. So after running "perl Makefile.PL", I edited the Makefile 1. changing the references to Oracle's ../lib to ../lib32, 2. changing change crt0_64.o to crt0_r.o. 3. Remove the -q32 and/or -q64 options from the list of libraries to link with. Now when I ran "make" it went smoothly, so did make test and make install. I ran my own simple perl testfile which connects to the Oracle and gets some info and it works fine. Now I have an application which can be customised to call perl scripts and when I call this test script from that application it fails with: install_driver(Oracle) failed: Can't load '/usr/local/perl/lib/site_perl/5.8.5/a ix/auto/DBD/Oracle/Oracle.so' for module DBD::Oracle: 0509-022 Cannot load mod ule /usr/local/perl/lib/site_perl/5.8.5/aix/auto/DBD/Oracle/Oracle.so. 0509-150 Dependent module /u00/oracle/product/9.2.0/lib/libclntsh.a(sh r.o) could not be loaded. 0509-103 The module has an invalid magic number. 0509-022 Cannot load module /u00/oracle/product/9.2.0/lib/libclntsh.a. 0509-150 Dependent module /u00/oracle/product/9.2.0/lib/libclntsh.a co uld not be loaded. at /usr/local/perl/lib/5.8.5/aix/DynaLoader.pm line 230. at (eval 3) line 3 Compilation failed in require at (eval 3) line 3. Perhaps a required shared library or dll isn't installed where expected at /opt/dscmdevc/src/udps/test_oracle_dbd.pl line 45 whats happening here is that the application sets its own LIBPATH to include oracle's lib(instead of lib32) in the beginning and that makes perl look at the wrong place for the file - libclntsh.a .Unfortunately it will take too long for the application developers to change this in their application and I am looking for a quick solution. The test script is something like: use Env; use strict; use lib qw( /opt/harvest/common/perl/lib ) ; #use lib qw( $ORACLE_HOME/lib32 ) ; use DBI; my $connect_string="dbi:Oracle:"; my $datasource="d1ach2"; $ENV{'LIBPATH'} = "${ORACLE_HOME}/lib32:$ENV{'LIBPATH'}" ; . . my $dbh = DBI->connect($connect_string, $dbuser, $dbpwd) or die "Can't connect to $datasource: $DBI::errstr"; . . Adding 'use lib' or using'$ENV{LIBPATH}' to change the LIBPATH is not working because I need to make this work in this perl script and the "use DBI" is run (or whatever the term is) in the compile-phase before the LIBPATH is set in the run-phase. I have a work around for it: write a wrapper ksh script which exports the LIBPATH and then calls the perl script which works fine but I was wondering if there is a way to set the libpath or do something else inside the current perl script so that it knows where to look for the right library files inspite of the wrong LIBPATH? Or did I miss something when I changed the Makefile and did not install everything right? Is there anyway I check this? (the make install didnot throw any errors) Any help or thoughts on this would be much appreciated. Thanks! Rachana. note 12: -------- P550:/ # find . -name "libclnt*" -print ./apps/oracle/product/9.2/lib/libclntst9.a ./apps/oracle/product/9.2/lib/libclntsh.a ./apps/oracle/product/9.2/lib32/libclntst9.a ./apps/oracle/product/9.2/lib32/libclntsh.a ./apps/oracle/oui/bin/aix/libclntsh.so.9.0 P550:/ # ----- Note: ----- Listener problem: IBM/AIX RISC System/6000 Error: 13: Permission denied ------------------------------------------------------------------------ When starting listener start listener TNS-12546: TNS:permission denied TNS-12560: TNS:protocol adapter error TNS-00516: Permission denied IBM/AIX RISC System/6000 Error: 13: Permission denied Note 1: 'TNS-12531: TNS:cannot allocate memory' may be misleading, it seems to be a permission problem (see also IBM/AIX RISC System/6000 Error: 13: Permission denied). A possible reason is: Oracle (more specific the listener) is unable to read /etc/hosts, because of permission problems. So host resolution is not possible. .. .. The problem really was in permissions of /etc/hosts on the node2. It was -rw-r----- (640). Now it is -rw-rw-r-- (664) and everything goes ok. Thank you! BUGS WITH REGARDS TO PRO*COBOL ON 9i: ----- Note: ----- Listener problem: IBM/AIX RISC System/6000 Error: 79: Connection refused ------------------------------------------------------------------------ d0planon@zb121l01:/data/oracle/d0planon/admin/home/$ lsnrctl LSNRCTL for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production on 12-OCT-2007 08:29:14 Copyright (c) 1991, 2006, Oracle. All rights reserved. Welcome to LSNRCTL, type "help" for information. LSNRCTL> status Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521)) TNS-12541: TNS:no listener TNS-12560: TNS:protocol adapter error TNS-00511: No listener IBM/AIX RISC System/6000 Error: 79: Connection refused Answer 1: Check if the oracle user can read /etc/hosts Answer 2: Maybe there are multiple instances of the listener, so if you try the following LSNRCTL> status You might have a correct response. ----- Note: ----- 64BIT PRO*COBOL IS NOT THERE EVNN AFTER UPGRDING TO 9.2.0.3 ON AIX-5L BOX -------------------------------------------------------------------------- Bookmark Fixed font Go to End Monitor Bug Bug No. 2859282 Filed 19-MAR-2003 Updated 01-NOV-2003 Product Precompilers Product Version 9.2.0.3 Platform AIX5L Based Systems (64-bit) Platform Version 5.* Database Version 9.2.0.3 Affects Platforms Port-Specific Severity Severe Loss of Service Status Closed, Duplicate Bug Base Bug 2440385 Fixed in Product Version No Data Problem statement: 64BIT PRO*COBOL IS NOT THERE EVNN AFTER UPGRDING TO 9.2.0.3 ON AIX-5L BOX *** 03/19/03 10:13 am *** 2889686.996 . ========================= PROBLEM: . 1. Clear description of the problem encountered: . cst. has upgraded from 9.2.0.2 to 9.2.0.3 on a AIX 5L 64-Bit Box and is not seeing the 64-bit Procob executable. Actually the same problem existed when upgraded from 9.2.0.1 to 9.2.0.2, but the one-off patch has been provided in the Bug#2440385 to resolve the issue. As per the Bug, problem has been fixed in 9.2.0.3. But My Cst. is facing the same problem on 9.2.0.3 also. . This is what the Cst. says ============================ This is the original bug # 2440385. The fix provides 64 bit versions of Pro*Cobol.There are two versions of the patch for the bug: one is for the 9.2.0.1 RDBMS and the other is for 9.2.0.2. So the last time I hit this issue, I applied the 9.2.0.2 RDBMS patch to the 9.2.0.1 install. The 9.2.0.2 patch also experienced the relinking problem on rtsora just like the 9.2.0.1 install did. I ignored the error to complete the patch application. Then I used the patch for the 2440385 bug to get 64 bit procob/rtsora executables (the patch actually provides executables rather than performing a successful relinking) to get the Pro*Cobol 1.8.77 precompiler to work with the MicroFocus Server Express 2.0.11 (64 bit) without encountering "bad magic number" error. . The current install that I am performing I've downloaded the Oracle 9.2.0.3 Pro*Cobol capability fix either so the rtsora relinking fails as well. Thus I don't have a working Pro*Cobol precompiler to allow me to generate our Cobol programs against the database. . 2. Pertinent configuration information (MTS/OPS/distributed/etc) . 3. Indication of the frequency and predictability of the problem . 4. Sequence of events leading to the problem . 5. Technical impact on the customer. Include persistent after effects. . ========================= DIAGNOSTIC ANALYSIS: . One-off patch should be provided on top of 9.2.0.3 as provided on top of 9.2.0.2/9.2.0.1 . ========================= WORKAROUND: . . ========================= RELATED BUGS: . 2440385 . ========================= REPRODUCIBILITY: . 1. State if the problem is reproducible; indicate where and predictability . 2. List the versions in which the problem has reproduced . 9.2.0.3 . 3. List any versions in which the problem has not reproduced Further notes on PRO*COBOL: =========================== Note 1: ======= 9201,9202,9203,9204,9205 32 bit cobol: procob32 or procob18_32. 64 bit cobol: procob or procob18 PATCHES: 1. Patch 2663624: (Cobol patch for 9202 AIX 5L) ----------------------------------------------- PSE FOR BUG2440385 ON 9.2.0.2 FOR AIX5L PORT 212 Patchset Exception: 2663624 / Base Bug 2440385 #------------------------------------------------------------------------- # # DATE: November 26, 2002 # ----------------------- # Platform Patch for : AIX Based Systems (Oracle 64bit) for 5L # Product Version # : 9.2.0.2 # Product Patched : RDBMS # # Bugs Fixed by this patch: # ------------------------- # 2440385 : PLEASE PROVIDE THE PATCH FOR SUPPORTING 64BIT PRO*COBOL # # Patch Installation Instructions: # -------------------------------- # To apply the patch, unzip the PSE container file; # # % unzip p2440385_9202_AIX64-5L.zip # # Set your current directory to the directory where the patch # is located: # # % cd 2663624 # # Ensure that the directory containing the opatch script appears in # your $PATH; then enter the following command: # # % opatch apply 2. Patch 2440385: ----------------- Results for Platform : AIX5L Based Systems (64-bit) Patch Description Release Updated Size 2440385 Pro*COBOL: PATCH FOR SUPPORTING 64BIT PRO*COBOL 9.2.0.3 27-APR-2003 34M 2440385 Pro*COBOL: PATCH FOR SUPPORTING 64BIT PRO*COBOL 9.2.0.2 26-NOV-2002 17M 2440385 Pro*COBOL: PATCH FOR SUPPORTING 64BIT PRO*COBOL 9.2.0.1 01-OCT-2002 17M 3. Patch 3501955 9205: ---------------------- Also includes 2440385. Provide the patch for supporting 64-bit Pro*COBOL. Note 2: ======= Problem precompiling Cobol program under Oracle 9i...... Hi, we recently upgraded to 9i. However, we still have 32 bit Cobol, so we're using the procob18_32 precompiler to compile our programs. Some of my compiles have worked successfully. However, I'm receiving the follow error in one of my compiles: 1834 183400 01 IB0-STATUS PIC 9. 7SA 350 1834 ...................................^ PCC-S-0018: Expected "PICTURE clause", but found "9" at line 1834 in file What's strange is that if I compile the program against the same DB using procob instead of procob18_32, it compiles cleanly. I noticed in my compile that failed using procob18_32, it had the following message: System default option values taken from: /u01/app/oracle/product/9.2.0.4/precomp /admin/pcccob.cfg Yet, when I used procob, it had this message: System default option values taken from: /u01/app/oracle/product/9.2.0.4/precomp /admin/pcbcfg.cfg .. .. Hi, I started using procob32 instead of procob18_32, and that resolved my problem. Thanks for any help you may have already started to provide. Note 3: ======= Doc ID: Note:257934.1 Content Type: TEXT/X-HTML Subject: Pro*COBOL Application Fails in Runtime When Using Customized old Make Files With Signal 11 (MF Errror 114) Creation Date: 20-NOV-2003 Type: PROBLEM Last Revision Date: 04-APR-2005 Status: MODERATED The information in this article applies to: Precompilers - Version: 9.2.0.4 This problem can occur on any platform. Symptoms After upgrading from Oracle server and Pro*COBOL 9.2.0.3.0 to 9.2.0.4.0 application are failing with cobol runtime error 114 when using 32-bit builds. Platform is AIX 4.3.3 which does not support 64-bit builds with Micro Focus Server Express 2.0.11. Execution error : file 'sample1' error code: 114, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 11) Changes Upgraded from 9.2.0.3.0 to 9.2.0.4.0. Cause The customized old make files for building 32-bit applications invoked the 64-bit precompilers procob or procob18 instead of procob32 or procob18_32. Fix Use the Oracle Supplied make templates or change the customized old make files for 32-bit application builds $ORACLE_HOME/precomp/demo/procob2/demo_procob_32.mk, $ORACLE_HOME/precomp/demo/procob/demo_procob_32.mk and $ORACLE_HOME/precomp/demo/procob/demo_procob18_32.mk invoke the wrong precompiler. To fix the problem add the following to $ORACLE_HOME/precomp/demo/procob2/demo_procob_32.mk: PROCOB=procob32 Using $ORACLE_HOME/precomp/demo/procob/demo_procob_32.mk: PROCOB_32=procob32 Using $ORACLE_HOME/precomp/demo/procob/demo_procob18_32.mk PROCOB18_32=procob18_32 The change can be added to the bottom of the make file. References Bug 3220095 - Procobol App Fails114 Attempt To Access Item Beyond Bounds Of Memory (Signal 11) Note 4: ======= Displayed below are the messages of the selected thread. Thread Status: Closed From: Jean-Daniel DUMAS 23-Nov-04 16:39 Subject: PROCOB18_32 Problem at execution ORA-00933 PROCOB18_32 Problem at execution ORA-00933 We try to migrate from Oracle 8.1.7.4 to Oracle 9.2.0.5. We've got problems with a lot of procobol programs using host table variables in PL SQL blocks like: EXEC SQL EXECUTE BEGIN FOR nIndice IN 1..:WI-NB-APPELS-TFO009S LOOP UPDATE tmp_edition_erreur SET mon_nb_dec = :WTI-S2-MON-NB-DEC (nIndice) WHERE mon_cod = :WTC-S2-MON-COD (nIndice) AND run_id = :WC-O-RUN-ID; END LOOP; END; END-EXEC At execution, we've got "ORA-00933 SQL command not properly ended". The problem seems to appear only if the host table variable is used inside a SELECT,UPDATE or DELETE command. For the INSERT VALUES command, it seems that we've got no problem. A workaround consists to assign host table variables into oracle table variables and replace inside SQL command host table variables by oracle table variables. But, as we've got a lot a program like this, we don't enjoy to do this. Have somebody another idea ? jddumas@eram.fr From: Oracle, Amit Joshi 05-Jan-05 06:26 Subject: Re : PROCOB18_32 Problem at execution ORA-00933 Hi Please refer to bug 3802067 on Metalink. From the details provided , it seems you are hitting the same. Best Regards Amit Joshi Note 5: ======= Re: Server Express 64bit and Oracle 9i problem (114) on AIX 5.2 Hi Wayne (and Panos) Apologies if you're aware of some of this already, but I just wanted to clarify the steps involved in creating and executing a Pro*COBOL application with Micro Focus Server Express on UNIX. When installing Pro*COBOL on UNIX (as part of the main Oracle installation), you need to have your COBOL environment setup, in order for the installer to relink a COBOL RTS containing the Oracle support libraries (rtsora/rtsora32/rtsora64). The 64-bit edition of Oracle 9i on AIX 5.x creates rtsora -- the 64-bit version of the run-time -- and rtsora32 -- the 32-bit version of the run-time. It's imperative that you use the correct edition of Server Express, i.e. 32-bit or 64-bit -- note well, that these are separate products on this platform -- for the mode in which you wish to use Oracle. In addition, you need to ensure that LIBPATH is set to point to the correct Oracle 'lib' directory -- $ORACLE_HOME/lib32 for 32-bit, or $ORACLE_HOME/lib for 64-bit If you wish to recreate those executables, say if you've updated your COBOL environment since installing Oracle, then from looking at the makefiles -- ins_precomp.mk and env_precomp.mk -- then the effective commands to use to re-link the run-time correctly are as follows (logged in under your Oracle user ID) : either mode: export PATH=$COBDIR/bin:$ORACLE_HOME/bin:$PATH 32-bit : export LIBPATH=$COBDIR/lib:$ORACLE_HOME/lib32:$LIBPATH cd $ORACLE_HOME/precomp/lib make LIBDIR=lib32 -f ins_precomp.mk EXE=rtsora32 rtsora32 64-bit: export LIBPATH=$COBDIR/lib:$ORACLE_HOME/lib:$LIBPATH cd $ORACLE_HOME/precomp/lib make -f ins_precomp.mk rtsora Regarding precompiling your application, Oracle provide two versions of Pro*COBOL. Again, you need to use the correct one depending on whether you're creating a 32-bit or 64-bit application, as the precompiler will generate different code. If invoking Pro*COBOL directly, you need to use : 32-bit : procob32 / procob18_32 , e.g. procob32 myapp.pco cob -it myapp.cob rtsora32 myapp.int or 64-bit : procob / procob18 , e.g. procob myapp.pco cob -it myapp.cob rtsora myapp.int If you're using Server Express 2.2 SP1 or later, you can also compile using the Cobsql preprocessor, which will invoke the correct version of Pro*COBOL under the covers, allowing for a single precompile-compile step, e.g. cob -ik myapp.pco -C "p(cobsql) csqlt==oracle8 endp" This method also aids debugging, as you will see the original source code while animating, rather than the output from the precompiler. See the Server Express Database Access manual. Prior to SX 2.2 SP1, Cobsql only supported the creation of 32-bit applications. I hope this helps -- if you're still having problems, please let me know. Regards, SimonT. Re: Re: Server Express 64bit and Oracle 9i problem (114) on AIX 5.2 Hi Simon (and anyone else) Thanks for that. We still seem to be getting a very unusual error with our c ompiles in or makes. A bit of background: we are "upgrading" from Oracle8i, SAS6, Solaris, MF COB OL 4.5 to AIX 5L, Oracle9i, SAS8 and MF Server Express COBOL. When we attempt to compile our COBOL it works fine. However if the COBOL has embedded Oracle SQL our procomp makes try to access ADA. We do not use ADA. I thought this must have been included by accident; but can find no flag or install option for it. So can you give us any clues as to why we are suffer ing an ADA plague :-)) Wayne Re: Server Express 64bit and Oracle 9i problem (114) on AIX 5.2 Hi Wayne. On the surface, it appears as if you're not picking up the correct Pro*COBOL binary. If you invoke 'procob' from the command line, you should see something along the lines of : Pro*COBOL: Release 9.2.0.4.0 - Production on Mon Apr 19 13:38:07 2004 followed by a list of Pro*COBOL options. Do you see this, or do you see a different banner (say, Pro*ADA, or Pro*Fortran)? Assuming you see something other than a Pro*COBOL banner, then if you invoke 'whence procob', does it show procob as being picked up from your Oracle bin directory (/home/oracle/9.2.0/bin/procob in my case) ? If you're either not seeing the correct Pro*COBOL banner, or it's not located in the correct directory, I'd suggest rebuilding the procob and procob32 binaries. Logged in under your Oracle user ID, with the Oracle environment set up : cd $ORACLE_HOME/precomp/lib make -f ins_precomp.mk procob32 procob and then try your compilation process again. Regards, SimonT. Re: Re: Server Express 64bit and Oracle 9i problem (114) on AIX 5.2 Hi Simon Firstly, thanks for all your help, it was greatly appreciated. We have the solution to our problem: The problem is resolved by modifying the line in the job from: make -f $SRC_DIR/procob.mk COBS="$SRC_DIR/PFEM025A.cob SYSDATE.cob CNTLGET. cob" EXE=$SRC_DIR/PFEM025A to make -f $SRC_DIR/procob.mk build COBS="$SRC_DIR/PFEM025A.cob SYSDATE.cob CN TLGET.cob" EXE=$SRC_DIR/PFEM025A It appears this (build keyword) is not a requirement for the job to run on S olaris but is for AIX. All is working fine. Cheers Wayne Note 6: ======= Doc ID: Note:2440385.8 Content Type: TEXT/X-HTML Subject: Support Description of Bug 2440385 Creation Date: 08-AUG-2003 Type: PATCH Last Revision Date: 15-AUG-2003 Status: PUBLISHED Click here for details of sections in this note. Bug 2440385 AIX: Support for 64 bit ProCobol This note gives a brief overview of bug 2440385. Affects: Product (Component) Precompilers (Pro*COBOL) Range of versions believed to be affected Versions >= 7 but < 10G Versions confirmed as being affected 9.2.0.3 Platforms affected Aix 64bit 5L Fixed: This issue is fixed in 9.2.0.4 (Server Patch Set) Symptoms: (None Specified) Related To: Pro* Precompiler Description Add support for 64 bit ProCobol The full bug text (if published) can be seen at Bug 2440385 This link will not work for UNPUBLISHED bugs. Note 7: ======= Displayed below are the messages of the selected thread. Thread Status: Closed From: Cathy Agada 18-Sep-03 21:40 Subject: How do I relink rtsora for 64 bit processing How do I relink rtsora for 64 bit processing I have the following error while relinking "rtsora" on AIX 5L/64bit platform on oracle 9.2.0.3 (I believe my patch is up-to-date). Our Micro Focus compiler version is 2.0.11 $>make -f ins_precomp.mk relink EXENAME=rtsora /bin/make -f ins_precomp.mk LIBDIR=lib32 EXE=/app/oracle/product/9.2.0/precomp/lib/rtsora rtsora32 Linking /app/oracle/product/9.2.0/precomp/lib/rtsora cob64: bad magic number: /app/oracle/product/9.2.0/precomp/lib32/cobsqlintf.o make: 1254-004 The error code from the last command is 1. Stop. make: 1254-004 The error code from the last command is 2. My environment variable is as follows: COBDIR=/usr/lpp/cobol LD_LIBRARY_PATH=$ORACLE_HOME/lib:/app/oracle/product/9.2.0/network/lib SHLIB_PATH=$ORACLE_HOME/lib64:/app/oracle/product/9.2.0/lib32 I added 'define=bit64' on precomp config file. Any ideas on what could be wrong. Thanks. From: Oracle, Amit Chitnis 19-Sep-03 05:26 Subject: Re : How do I relink rtsora for 64 bit processing Cathy, Support for 64 bit Pro*Cobol 9.2.0.3 on AIX 5.1 was provided through one off patch for bug 2440385 You will need to download and apply the patch for bug 2440385. ==OR== You can dowload and apply the latest 9.2.0.4 patchset where the bug is fixed. Thanks, Amit Chitnis. Note 8: ======= Doc ID: Note:215279.1 Content Type: TEXT/X-HTML Subject: Building Pro*COBOL Programs Fails With "cob64: bad magic number:" Creation Date: 08-APR-2003 Type: PROBLEM Last Revision Date: 15-APR-2003 Status: PUBLISHED fact: Pro*COBOL 9.2.0.2 fact: Pro*COBOL 9.2.0.1 fact: AIX-Based Systems (64-bit) symptom: Building Pro*COBOL programs fails symptom: cob64: bad magic number: %s symptom: /oracle/product/9.2.0/precomp/lib32/cobsqlintf.o cause: Bug 2440385 AIX: Support for 64 bit ProCobol fix: This is fixed in Pro*COBOL 9.2.0.3 One-Off patch for Pro*COBOL 9.2.0.2 has been provided in Metalink Patch Number 2440385 Reference: How to Download a Patch from Oracle Note 9: ======= If you wish to recreate those executables, say if you've updated your COBOL environment since installing Oracle, then from looking at the makefiles -- ins_precomp.mk and env_precomp.mk -- then the effective commands to use to re-link the run-time correctly are as follows (logged in under your Oracle user ID) : either mode: export PATH=$COBDIR/bin:$ORACLE_HOME/bin:$PATH 32-bit : export LIBPATH=$COBDIR/lib:$ORACLE_HOME/lib32:$LIBPATH cd $ORACLE_HOME/precomp/lib make LIBDIR=lib32 -f ins_precomp.mk EXE=rtsora32 rtsora32 64-bit: export LIBPATH=$COBDIR/lib:$ORACLE_HOME/lib:$LIBPATH cd $ORACLE_HOME/precomp/lib make -f ins_precomp.mk rtsora Note 10: ======== On 9.2.0.5, try to get the pro cobol patch for 9203. Then just copy the procobol files to the cobol directory. ----- Note: ----- ORA-12170: ========== Connection Timeout. Doc ID: Note:274303.1 Content Type: TEXT/X-HTML Subject: Description of parameter SQLNET.INBOUND_CONNECT_TIMEOUT Creation Date: 26-MAY-2004 Type: BULLETIN Last Revision Date: 10-FEB-2005 Status: MODERATED *** This article is being delivered in Draft form and may contain errors. Please use the MetaLink "Feedback" button to advise Oracle of any issues related to this article. *** PURPOSE ------- To specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information. Description of parameter SQLNET.INBOUND_CONNECT_TIMEOUT ------------------------------------------------------- This parameter has been introduced in 9i version. This has to be configured in sqlnet.ora file. Use the SQLNET.INBOUND_CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information. If the client fails to establish a connection and complete authentication in the time specified, then the database server terminates the connection. In addition, the database server logs the IP address of the client and an ORA-12170: TNS:Connect timeout occurred error message to the sqlnet.log file. The client receives either an ORA-12547: TNS:lost contact or an ORA-12637: Packet receive failed error message. Without this parameter, a client connection to the database server can stay open indefinitely without authentication. Connections without authentication can introduce possible denial-of-service attacks, whereby malicious clients attempt to flood database servers with connect requests that consume resources. To protect both the database server and the listener, Oracle Corporation recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying values for these parameters, consider the following recommendations: *Set both parameters to an initial low value. *Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter. For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed. By default is set to None Example SQLNET.INBOUND_CONNECT_TIMEOUT=3 RELATED DOCUMENTS ----------------- Oracle9i Net Services Reference Guide, Release 2 (9.2), Part Number A96581-02 SQLNET.EXPIRE_TIME: ------------------- Purpose: Determines time interval to send a probe to verify the session is alive See Also: Oracle Advanced Security Administrator's Guide Default: None Minimum Value: 0 minutes Recommended Value: 10 minutes Example: sqlnet.expire_time=10 sqlnet.expire_time Enables dead connection detection, that is, after the specifed time (in minutes) the server checks if the client is still connected. If not, the server process exits. This parameter must be set on the server PROBLEM: Long query (20 minutes) returns ORA-01013 after about a minute. SOLUTION: The SQLNET.ORA parameter SQLNET.EXPIRE_TIME was set to a one(1). The parameter was changed to... SQLNET.EXPIRE_TIME=2147483647 This allowed the query to complete. This is documented in the Oracle Troubleshooting manual on page 324. The manual part number is A54757.01. Keywords: SQLNET.EXPIRE_TIME,SQLNET.ORA,ORA-01013 sqlnet.expire_time should be set on the server. The server sends keep alive traffic over connections that have already been established. You won't need to change your firewall. sqlnet.expire_time is actually intended to test connections in order to allow oracle to clean up resources from connection that abnormally terminated. The architecture to do that means that the server will send a probe packet to the client. That probe packet is viewed by the most firewalls as traffic on the line. That will in short reset the idle timers on the firewall. If you happen to have the disconnects from idle timers then it may help. It was not intended for that feature but it is a byproduct of the design. ----- Note: ----- Tracing SQLNET: =============== Note 1: ------- Doc ID: Note:219968.1 Subject: SQL*Net, Net8, Oracle Net Services - Tracing and Logging at a Glance Type: BULLETIN Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 20-NOV-2002 Last Revision Date: 26-AUG-2003 TITLE ----- SQL*Net, Net8, Oracle Net Services - Tracing and Logging at a Glance. PURPOSE ------- The purpose of Oracle Net tracing and logging is to provide detailed information to track and diagnose Oracle Net problems such as connectivity issues, abnormal disconnection and connection delay. Tracing provides varying degrees of information that describe connection-specific internal operations during Oracle Net usage. Logging reports summary, status and error messages. Oracle Net Services is the replacement name for the Oracle Networking product formerly known as SQL*Net (Oracle7 [v2.x]) and Net8 (Oracle8/8i [v8.0/8.1]). For consistency, the term Oracle Net is used thoughout this article and refers to all Oracle Net product versions. SCOPE & APPLICATION ------------------- The aim of this document is to overview SQL*Net, Net8, Oracle Net Services tracing and logging facilities. The intended audience includes novice Oracle users and DBAs alike. Although only basic information on how to enable and disable tracing and logging features is described, the document also serves as a quick reference. The document provides the reader with the minimum information necessary to generate trace and log files with a view to forwarding them to Oracle Support Services (OSS) for further diagnosis. The article does not intend to describe trace/log file contents or explain how to interpret them. LOG & TRACE PARAMETER OVERVIEW ------------------------------ The following is an overview of Oracle Net trace and log parameters. TRACE_LEVEL_[CLIENT|SERVER|LISTENER] = [0-16|USER|ADMIN|SUPPORT|OFF] TRACE_FILE_[CLIENT|SERVER|LISTENER] = TRACE_DIRECTORY_[CLIENT|SERVER|LISTENER] = TRACE_UNIQUE_[CLIENT|SERVER|LISTENER] = [ON|TRUE|OFF|FALSE] TRACE_TIMESTAMP_[CLIENT|SERVER|LISTENER] = [ON|TRUE|OFF|FALSE] #Oracle8i+ TRACE_FILELEN_[CLIENT|SERVER|LISTENER] = #Oracle8i+ TRACE_FILENO_[CLIENT|SERVER|LISTENER] = #Oracle8i+ LOG_FILE_[CLIENT|SERVER|LISTENER] = LOG_DIRECTORY_[CLIENT|SERVER|LISTENER] = LOGGING_LISTENER = [ON|OFF] TNSPING.TRACE_LEVEL = [0-16|USER|ADMIN|SUPPORT|OFF] TNSPING.TRACE_DIRECTORY = NAMES.TRACE_LEVEL = [0-16|USER|ADMIN|SUPPORT|OFF] NAMES.TRACE_FILE = NAMES.TRACE_DIRECTORY = NAMES.TRACE_UNIQUE = [ON|OFF] NAMES.LOG_FILE = NAMES.LOG_DIRECTORY = NAMES.LOG_UNIQUE = [ON|OFF] NAMESCTL.TRACE_LEVEL = [0-16|USER|ADMIN|SUPPORT|OFF] NAMESCTL.TRACE_FILE = NAMESCTL.TRACE_DIRECTORY = NAMESCTL.TRACE_UNIQUE = [ON|OFF] Note: With the exception of parameters suffixed with LISTENER, all other parameter suffixes and prefixes [CLIENT|NAMES|NAMESCTL|SERVER|TNSPING] are fixed and cannot be changed. For parameters suffixed with LISTENER, the suffix name should be the actual Listener name. For example, if the Listener name is PROD_LSNR, an example trace parameter name would be TRACE_LEVEL_PROD_LSNR=OFF. CONFIGURATION FILES ------------------- Files required to enable Oracle Net tracing and logging features include: Oracle Net Listener LISTENER.ORA LISTENER.TRC Oracle Net - Client SQLNET.ORA on client SQLNET.TRC Oracle Net - Server SQLNET.ORA on server SQLNET.TRC TNSPING Utility SQLNET.ORA on client/Server TNSPING.TRC Oracle Name Server NAMES.ORA NAMES.TRC Oracle NAMESCTL SQLNET.ORA on server Oracle Connection Manager CMAN.ORA CONSIDERATIONS WHEN USING LOGGING/TRACING ----------------------------------------- 1. Verify which Oracle Net configuration files are in use. By default, Oracle Net configuration files are sought and resolved from the following locations: TNS_ADMIN environment variable (incl. Windows Registry Key) /etc or /var/opt/oracle (Unix) $ORACLE_HOME/network/admin (Unix) %ORACLE_HOME%/Network/Admin or %ORACLE_HOME%/Net80/Admin (Windows) Note: User-specific Oracle Net parameters may also reside in $HOME/sqlnet.ora file. An Oracle Net server installation is also a client. 2. Oracle Net tracing and logging can consume vast quantities of disk space. Monitor for sufficient disk space when tracing is enabled. On some Unix operating systems, /tmp is used for swap space. Although generally writable by all users, this is not an ideal location for trace/log file generation. 3. Oracle Net tracing should only be enabled for the duration of the issue at hand. Oracle Net tracing should always be disabled after problem resolution. 4. Large trace/log files place an overhead on the processes that generate them. In the absence of issues, the disabling of tracing and/or logging will improve Oracle Net overall efficiency. Alternatively, regularly truncating log files will also improve efficiency. 5. Ensure that the target trace/log directory is writable by the connecting user, Oracle software owner and/or user that starts the Net Listener. LOG & TRACE PARAMETERS ---------------------- This section provides a detailed description of each trace and log parameter. TRACE LEVELS TRACE_LEVEL_[CLIENT|SERVER|LISTENER] = [0-16|USER|ADMIN|SUPPORT|OFF] Determines the degree to which Oracle Net tracing is provided. Configuration file is SQLNET.ORA, LISTENER.ORA. Level 0 is disabled - level 16 is the most verbose tracing level. Listener tracing requires the Net Listener to be reloaded or restarted after adding trace parameters to LISTENER.ORA. Oracle Net (client/server) tracing takes immediate effect after tracing parameters are added to SQLNET.ORA. By default, the trace level is OFF. OFF (equivalent to 0) disabled - provides no tracing. USER (equivalent to 4) traces to identify user-induced error conditions. ADMIN (equivalent to 6) traces to identify installation-specific problems. SUPPORT (equivalent to 16) trace information required by OSS for troubleshooting. TRACE FILE NAME TRACE_FILE_[CLIENT|SERVER|LISTENER] = Determines the trace file name. Any valid operating system file name. Configuration file is SQLNET.ORA, LISTENER.ORA. Trace file is automatically appended with '.TRC'. Default trace file name is SQLNET.TRC, LISTENER.TRC. TRACE DIRECTORY TRACE_DIRECTORY_[CLIENT|SERVER|LISTENER] = Determines the directory in which trace files are written. Any valid operating system directory name. Configuration file is SQLNET.ORA, LISTENER.ORA. Directory should be writable by the connecting user and/or Oracle software owner. Default trace directory is $ORACLE_HOME/network/trace. UNIQUE TRACE FILES TRACE_UNIQUE_[CLIENT|SERVER|LISTENER] = [ON|TRUE|OFF|FALSE] Allows generation of unique trace files per connection. Trace file names are automatically appended with '_.TRC'. Configuration file is SQLNET.ORA, LISTENER.ORA. Unique tracing is ideal for sporadic issues/errors that occur infrequently or randomly. Default value is OFF TRACE TIMING TRACE_TIMESTAMP_[CLIENT|SERVER|LISTENER] = [ON|TRUE|OFF|FALSE] A timestamp in the form of [DD-MON-YY 24HH:MI;SS] is recorded against each operation traced by the trace file. Configuration file is SQLNET.ORA, LISTENER.ORA Suitable for hanging or slow connection issues. Available from Oracle8i onwards. Default value is is OFF. MAXIMUM TRACE FILE LENGTH TRACE_FILELEN_[CLIENT|SERVER|LISTENER] = Determines the maximum trace file size in Kilobytes (Kb). Configuration file is SQLNET.ORA, LISTENER.ORA. Available from Oracle8i onwards. Default value is UNLIMITED. TRACE FILE CYCLING TRACE_FILENO_[CLIENT|SERVER|LISTENER] = Determines the maximum number of trace files through which to perform cyclic tracing. Configuration file is SQLNET.ORA, LISTENER.ORA. Suitable when disk space is limited or when tracing is required to be enabled for long periods. Available from Oracle8i onwards. Default value is 1 (file). LOG FILE NAME LOG_FILE_[CLIENT|SERVER|LISTENER] = Determines the log file name. May be any valid operating system file name. Configuration file is SQLNET.ORA, LISTENER.ORA. Log file is automatically appended with '.LOG'. Default log file name is SQLNET.LOG, LISTENER.LOG. LOG DIRECTORY LOG_DIRECTORY_[CLIENT|SERVER|LISTENER] = Determines the directory in which log files are written. Any valid operating system directory name. Configuration file is SQLNET.ORA, LISTENER.ORA. Directory should be writable by the connecting user or Oracle software owner. Default directory is $ORACLE_HOME/network/log. DISABLING LOGGING LOGGING_LISTENER = [ON|OFF] Disables Listener logging facility. Configuration file is LISTENER.ORA. Default value is ON. ORACLE NET TRACE/LOG EXAMPLES ----------------------------- CLIENT (SQLNET.ORA) trace_level_client = 16 trace_file_client = cli trace_directory_client = /u01/app/oracle/product/9.0.1/network/trace trace_unique_client = on trace_timestamp_client = on trace_filelen_client = 100 trace_fileno_client = 2 log_file_client = cli log_directory_client = /u01/app/oracle/product/9.0.1/network/log tnsping.trace_directory = /u01/app/oracle/product/9.0.1/network/trace tnsping.trace_level = admin SERVER (SQLNET.ORA) trace_level_server = 16 trace_file_server = svr trace_directory_server = /u01/app/oracle/product/9.0.1/network/trace trace_unique_server = on trace_timestamp_server = on trace_filelen_server = 100 trace_fileno_server = 2 log_file_server = svr log_directory_server = /u01/app/oracle/product/9.0.1/network/log namesctl.trace_level = 16 namesctl.trace_file = namesctl namesctl.trace_directory = /u01/app/oracle/product/9.0.1/network/trace namesctl.trace_unique = on LISTENER (LISTENER.ORA) trace_level_listener = 16 trace_file_listener = listener trace_directory_listener = /u01/app/oracle/product/9.0.1/network/trace trace_timestamp_listener = on trace_filelen_listener = 100 trace_fileno_listener = 2 logging_listener = off log_directory_listener = /u01/app/oracle/product/9.0.1/network/log log_file_listener=listener NAMESERVER TRACE (NAMES.ORA) names.trace_level = 16 names.trace_file = names names.trace_directory = /u01/app/oracle/product/9.0.1/network/trace names.trace_unique = off CONNECTION MANAGER TRACE (CMAN.ORA) tracing = yes RELATED DOCUMENTS ----------------- Note 16658.1 (7) Tracing SQL*Net/Net8 Note 111916.1 SQLNET.ORA Logging and Tracing Parameters Note 39774.1 Log & Trace Facilities on Net v2 Note 73988.1 How to Get Cyclic SQL*Net Trace Files when Disk Space is Limited Note 1011114.6 SQL*Net V2 Tracing Note 1030488.6 Net8 Tracing Note 2: ------- Doc ID: Note:39774.1 Subject: LOG & TRACE Facilities on NET v2. Type: FAQ Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 25-JUL-1996 Last Revision Date: 31-JAN-2002 LOG AND TRACE FACILITIES ON SQL*NET V2 ====================================== This article describes the log and trace facilities that can be used to examine application connections that use SQL*Net. This article is based on usage of SQL*NET v2.3. It explains how to invoke the trace facility and how to use the log and trace information to diagnose and resolve operating problems. Following topics are covered below: o What the log facility is o What the trace facility is o How to invoke the trace facility o Logging and tracing parameters o Sample log output o Sample trace output Note: Information in this section is generic to all operating system environments. You may require further information from the Oracle operating system-specific documentation for some details of your specific operating environment. ________________________________________ 1. What is the Log Facility? ============================ All errors encountered in SQL*Net are logged to a log file for evaluation by a network or database administrator. The log file provides additional information for an administrator when the error on the screen is inadequate to understand the failure. The log file, by way of the error stack, shows the state of the TNS software at various layers. The properties of the log file are: o Error information is appended to the log file when an error occurs. o Generally, a log file can only be replaced or erased by an administrator, although client log files can be deleted by the user whose application created them. (Note that in general it is bad practice to delete these files while the program using them is still actively logging.) o Logging of errors for the client, server, and listener cannot be disabled. This is an essential feature that ensures all errors are recorded. o The Navigator and Connection Manager components of the MultiProtocol Interchange may have logging turned on or off. If on, logging includes connection statistics. o The Names server may have logging turned on or off. If on, a Names server's operational events are written to a specified logfile. You set logging parameters using the Oracle Network Manager. ________________________________________ 2. What is the Trace Facility? ============================== The trace facility allows a network or database administrator to obtain more information on the internal operations of the components of a TNS network than is provided in a log file. Tracing an operation produces a detailed sequence of statements that describe the events as they are executed. All trace output is directed to trace output files which can be evaluated after the failure to identify the events that lead up to an error. The trace facility is typically invoked during the occurrence of an abnormal condition, when the log file does not provide a clear indication of the cause. Attention: The trace facility uses a large amount of disk space and may have a significant impact upon system performance. Therefore, you are cautioned to turn the trace facility ON only as part of a diagnostic procedure and to turn it OFF promptly when it is no longer necessary. Components that can be traced using the trace facility are: o Network listener o SQL*Net version 2 components - SQL*Net client - SQL*Net server o MultiProtocol Interchange components - the Connection Manager and pumps - the Navigator o Oracle Names - Names server - Names Control Utility The trace facility can be used to identify the following types of problems: - Difficulties in establishing connections - Abnormal termination of established connections - Fatal errors occurring during the operation of TNS network components ________________________________________ 3. What is the Difference between Logging and Tracing? ====================================================== While logging provides the state of the TNS components at the time of an error, tracing provides a description of all software events as they occur, and therefore provides additional information about events prior to an error. There are three levels of diagnostics, each providing more information than the previous level. The three levels are: 1. The reported error from Oracle7 or tools; this is the single error that is commonly returned to the user. 2. The log file containing the state of TNS at the time of the error. This can often uncover low level errors in interaction with the underlying protocols. 3. The trace file containing English statements describing what the TNS software has done from the time the trace session was initiated until the failure is recreated. When an error occurs, a simple error message is displayed and a log file is generated. Optionally, a trace file can be generated for more information. (Remember, however, that using the trace facility has an impact on your system performance.) In the following example, the user failed to use Oracle Network Manager to create a configuration file, and misspelled the word "PORT" as "POT" in the connect descriptor. It is not important that you understand in detail the contents of each of these results; this example is intended only to provide a comparison. Reported Error (On the screen in SQL*Forms): ERROR: ORA-12533: Unable to open message file (SQL-02113) Logged Error (In the log file, SQLNET.LOG): **************************************************************** Fatal OSN connect error 12533, connecting to: (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala) (USER=ginger)))(ADDRESS_LIST=(ADDRESS=(PROTOCOL=ipc) (KEY=bad_port))(ADDRESS=(PROTOCOL=tcp)(HOST=lala)(POT=1521)))) VERSION INFORMATION: TNS for SunOS: Version 2.0.14.0.0 - Developer's Release Oracle Bequeath NT Protocol Adapter for SunOS: Version 2.0.14.0.0 - Developer's Release Unix Domain Socket IPC NT Protocol Adaptor for SunOS: Version 2.0.14.0.0 - Developer's Release TCP/IP NT Protocol Adapter for SunOS: Version 2.0.14.0.0 - Developer's Release Time: 07-MAY-93 17:38:50 Tracing to file: /home/ginger/trace_admin.trc Tns error struct: nr err code: 12206 TNS-12206: TNS:received a TNS error while doing navigation ns main err code: 12533 TNS-12533: TNS:illegal ADDRESS parameters ns secondary err code: 12560 nt main err code: 503 TNS-00503: Illegal ADDRESS parameters nt secondary err code: 0 nt OS err code: 0 Example of Trace of Error ------------------------- The trace file, SQLNET.TRC at the USER level, contains the following information: --- TRACE CONFIGURATION INFORMATION FOLLOWS --- New trace stream is "/private1/oracle/trace_user.trc" New trace level is 4 --- TRACE CONFIGURATION INFORMATION ENDS --- --- PARAMETER SOURCE INFORMATION FOLLOWS --- Attempted load of system pfile source /private1/oracle/network/admin/sqlnet.ora Parameter source was not loaded Error stack follows: NL-00405: cannot open parameter file Attempted load of local pfile source /home/ginger/.sqlnet.ora Parameter source loaded successfully -> PARAMETER TABLE LOAD RESULTS FOLLOW <- Some parameters may not have been loaded See dump for parameters which loaded OK -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <- TRACE_DIRECTORY_CLIENT = /private1/oracle trace_level_client = USER TRACE_FILE_CLIENT = trace_user --- PARAMETER SOURCE INFORMATION ENDS --- --- LOG CONFIGURATION INFORMATION FOLLOWS --- Attempted open of log stream "/tmp_mnt/home/ginger/sqlnet.log" Successful stream open --- LOG CONFIGURATION INFORMATION ENDS --- Unable to get data from navigation file tnsnav.ora local names file is /home/ginger/.tnsnames.ora system names file is /etc/tnsnames.ora -- failure, error stack follows -- NL-00427: bad list -- NOTE: FILE CONTAINS ERRORS, SOME NAMES MAY BE MISSING Calling address: (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala)(USER=ginger))) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=ipc)(KEY=bad_port))(ADDRESS=(PROTOCOL=tcp)(HOST Getting local community information Looking for local addresses setup by nrigla No addresses in the preferred address list TNSNAV.ORA is not present. No local communities entry. Getting local address information Address list being processed... No community information so all addresses are "local" Resolving address to use to call destination or next hop Processing address list... No community entries so iterate over address list This a local community access Got routable address information Making call with following address information: (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=ipc)(KEY=bad_port))) Calling with outgoing connect data (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala)(USER=ginger))) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=lala)(POT=1521)))) (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=ipc)(KEY=bad_port))) KEY = bad_port connecting... opening transport... -- sd=8, op=1, resnt[0]=511, resnt[1]=2, resnt[2]=0 -- unable to open transport -- nsres: id=0, op=1, ns=12541, ns2=12560; nt[0]=511, nt[1]=2, nt[2]=0 connect attempt failed Call failed... Call made to destination Processing address list so continuing Getting local community information Looking for local addresses setup by nrigla No addresses in the preferred address list TNSNAV.ORA is not present. No local communities entry. Getting local address information Address list being processed... No community information so all addresses are "local" Resolving address to use to call destination or next hop Processing address list... No community entries so iterate over address list This a local community access Got routable address information Making call with following address information: (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=tcp)(HOST=lala)(POT=1521))) Calling with outgoing connect data (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala)(USER=ginger))) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=lala)(POT=521)))) (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=tcp)(HOST=lala)(POT=1521))) -- failed to recognize: POT -- nsres: id=0, op=13, ns=12533, ns2=12560; nt[0]=503, nt[1]=0, nt[2]=0 Call failed... Exiting NRICALL with following termination result -1 -- error from nricall -- nr err code: 12206 -- ns main err code: 12533 -- ns (2) err code: 12560 -- nt main err code: 503 -- nt (2) err code: 0 -- nt OS err code: 0 -- Couldn't connect, returning 12533 In the trace file, note that unexpected events are preceded with an -- stamp. These events may represent serious errors, minor errors, or merely unexpected results from an internal operation. More serious and probably fatal errors are stamped with the -- prefix. In this example trace file, you can see that the root problem, the misspelling of "PORT," is indicated by the trace line: -- failed to recognize: POT Most tracing is very similar to this. If you have a basic understanding of the events the components will perform, you can identify the probable cause of an error in the text of the trace. ________________________________________ 4. Log File Names ================= Log files produced by different components have unique names. The default file names are: SQLNET.LOG Contains client and/or server information LISTENER.LOG Contains listener information INTCHG.LOG Contains Connection Manager and pump information NAVGATR.LOG Contains Navigator information NAMES.LOG Contains Names server information You can control the name of the log file. For each component, any valid string can be used to create a log file name. The parameters are of the form: LOG_FILE_component = string For example: LOG_FILE_LISTENER = TEST Some platforms have restrictions on the properties of a file name. See your Oracle operating system specific manuals for platform specific restrictions. _____________________________________ 5. Using Log Files ================== Follow these steps to track an error using a log file: 1. Browse the log file for the most recent error that matches the error number you have received from the application. This is almost always the last entry in the log file. Notice that an entry or error stack in the log file is usually many lines in length. In the example earlier in this chapter, the error number was 12207. 2. Starting at the bottom, look up to the first non-zero entry in the error report. This is usually the actual cause. In the example earlier in this chapter, the last non-zero entry is the "ns" error 12560. 3. Look up the first non-zero entry in later chapters of this book for its recommended cause and action. (For example, you would find the "ns" error 12560 under ORA-12560.) To understand the notation used in the error report, see the previous chapter, "Interpreting Error Messages." 4. If that error does not provide the desired information, move up the error stack to the second to last error and so on. 5. If the cause of the error is still not clear, turn on tracing and re-execute the statement that produced the error message. The use of the trace facility is described in detail later in this chapter. Be sure to turn tracing off after you have re-executed the command. ________________________________________ 6. Using the Trace Facility =========================== The steps used to invoke tracing are outlined here. Each step is fully described in subsequent sections. 1. Choose the component to be traced from the list: o Client o Server o Listener o Connection Manager and pump (cmanager) o Navigator (navigator) o Names server o Names Control Utility 2. Save existing trace file if you need to retain information on it. By default most trace files will overwrite an existing ones. TRACE_UNIQUE parameter needs to be included in appropriate config. files if unique trace files are required. This appends Process Id to each file. For Example: For Names server tracing, NAMES.TRACE_UNIQUE=ON needs to be set in NAMES. ORA file. For Names Control Utility, NAMESCTL.TRACING_UNIQUE=TRUE needs to be in SQLNET.ORA. TRACE_UNIQUE_CLIENT=ON in SQLNET.ORA for Client Tracing. 3. For any component, you can invoke the trace facility by editing the component configuration file that corresponds to the component traced. The component config. files are SQLNET.ORA, LISTENER.ORA, INTCHG.ORA, and NAMES. ORA. 4. Execute or start the component to be traced. If the trace component configuration files are modified while the component is running, the modified trace parameters will take effect the next time the component is invoked or restarted. Specifically for each component: CLIENT: Set the trace parameters in the client-side SQLNET.ORA and invoke a client application, such as SQL*Plus, a Pro*C application, or any application that uses the Oracle network products. SERVER: Set the trace parameters in the server-side SQLNET.ORA. The next process started by the listener will have tracing enabled. The trace parameters must be created or edited manually. LISTENER: Set the trace parameters in the LISTENER.ORA CONNECTION MANAGER: Set the trace parameters in INTCHG.ORA and start the Connection Manager from the Interchange Control Utility or command line. The pumps are started automatically with the Connection Manager, and their trace files are controlled by the trace parameters for the Connection Manager. NAVIGATOR:Again, set the trace parameters in INTCHG.ORA and start the Navigator NAMES SERVER: Trace parameters needs to be set in NAMES.ORA and start the Names server. NAMES CONTROL UTILITY: Set the trace parameters in SQLNET.ORA and start the Names Control Utility 5. Be sure to turn tracing off when you do not need it for a specific diagnostic purpose. ________________________________________ 7. Setting Trace Parameters =========================== The trace parameters are defined in the same configuration files as the log parameters. Table below shows the configuration files for different network components and the default names of the trace files they generate. -------------------------------------------------------- | Trace Parameters | Configuration | | | Corresponding to | File | Output Files | |-------------------|-----------------|------------------| | | | | | Client | SQLNET.ORA | SQLNET.TRC | | Server | | SQLNET.TRC | | TNSPING Utility | | TNSPING.TRC | | Names Control | | | | Utility | | NAMESCTL.TRC | |-------------------|-----------------|------------------| | Listener | LISTENER.ORA | LISTENER.TRC | |-------------------|-----------------|------------------| | Interchange | INTCHG.ORA | | | Connection | | | | Manager | | CMG.TRC | | Pumps | | PMP.TRC | | Navigator | | NAV.TRC | |-------------------|-----------------|------------------| | Names server | NAMES.ORA | NAMES.TRC | |___________________|_________________|__________________| The configuration files for each component are located on the computer running that component. The trace characteristics for two or more components of an Interchange are controlled by different parameters in the same configuration file. For example, there are separate sets of parameters for the Connection Manager and the Navigator that determine which components will be traced, and at what level. Similarly, if there are multiple listeners on a single computer, each listener is controlled by parameters that include the unique listener name in the LISTENER.ORA file. For each component, the configuration files contain the following information: o A valid trace level to be used (Default is OFF) o The trace file name (optional) o The trace file directory (optional) ________________________________________ 7a. Valid SQLNET.ORA Diagnostic Parameters ========================================== The SQLNET.ORA caters for: o Client Logging & Tracing o Server Logging & Tracing o TNSPING utility o NAMESCTL program ------------------------------------------------------------------------------ | | | | | PARAMETERS | VALUES | Example (DOS client, UNIX server) | | | | | |------------------------|----------------|------------------------------------| |Parameters for Client | |===================== | |------------------------------------------------------------------------------| | | | | | TRACE_LEVEL_CLIENT | OFF/USER/ADMIN | TRACE_LEVEL_CLIENT=USER | | | | | | TRACE_FILE_CLIENT | string | TRACE_FILE_CLIENT=CLIENT | | | | | | TRACE_DIRECTORY_CLIENT | valid directory| TRACE_DIRECTORY_CLIENT=c:\NET\ADMIN| | | | | | TRACE_UNIQUE_CLIENT | OFF/ON | TRACE_UNIQUE_CLIENT=ON | | | | | | LOG_FILE_CLIENT | string | LOG_FILE_CLIENT=CLIENT | | | | | | LOG_DIRECTORY_CLIENT | valid directory| LOG_DIRECTORY_CLIENT=c:\NET\ADMIN | |------------------------------------------------------------------------------| |Parameters for Server | |===================== | |------------------------------------------------------------------------------| | | | | | TRACE_LEVEL_SERVER | OFF/USER/ADMIN | TRACE_LEVEL_SERVER=ADMIN | | | | | | TRACE_FILE_SERVER | string | TRACE_FILE_SERVER=unixsrv_2345.trc | | | | | | TRACE_DIRECTORY_SERVER | valid directory| TRACE_DIRECTORY_SERVER=/tmp/trace | | | | | | LOG_FILE_SERVER | string | LOG_FILE_SERVER=unixsrv.log | | | | | | LOG_DIRECTORY_SERVER | valid directory| LOG_DIRECTORY_SERVER=/tmp/trace | |------------------------------------------------------------------------------| ---(SQLNET.ORA Cont.)--------------------------------------------------------- | | | | | PARAMETERS | VALUES | Example (DOS client, UNIX server) | | | | | |------------------------|----------------|------------------------------------| | |Parameters for TNSPING | |====================== | |------------------------------------------------------------------------------| | | | | | TNSPING.TRACE_LEVEL | OFF/USER/ADMIN | TNSPING.TRACE_LEVEL=user | | | | | | TNSPING.TRACE_DIRECTORY| directory |TNSPING.TRACE_DIRECTORY= | | | | /oracle7/network/trace | | | | | |------------------------------------------------------------------------------| |Parameters for Names Control Utility | |==================================== | |------------------------------------------------------------------------------| | | | | | NAMESCTL.TRACE_LEVEL | OFF/USER/ADMIN |NAMESCTL.TRACE_LEVEL=user | | | | | | NAMESCTL.TRACE_FILE | file |NAMESCTL.TRACE_FILE=nc_south.trc | | | | | | NAMESCTL.TRACE_DIRECTORY| directory |NAMESCTL.TRACE_DIRECTORY=/o7/net/trace| | | | | | NAMESCTL.TRACE_UNIQUE | TRUE/FALSE |NAMESCTL.TRACE_UNIQUE=TRUE or ON/OFF| | | | | ------------------------------------------------------------------------------ Note: You control log and trace parameters for the client through Oracle Network Manager. You control log and trace parameters for the server by manually adding the desired parameters to the SQLNET.ORA file. Parameters for Names Control Utility & TNSPING Utility need to be added manually to SQLNET.ORA file. You cannot create them using Oracle Network Manager. ________________________________________ 7b. Valid LISTENER.ORA Diagnostic Parameters ============================================ The following table shows the valid LISTENER.ORA parameters used in logging and tracing of the listener. ------------------------------------------------------------------------------ | | | | | PARAMETERS | VALUES | Example (DOS client, UNIX server) | | | | | |------------------------|----------------|------------------------------------| | | | | |TRACE_LEVEL_LISTENER | USER | TRACE_LEVEL_LISTENER=OFF | | | | | |TRACE_FILE_LISTENER | string | TRACE_FILE_LISTENER=LISTENER | | | | | |TRACE_DIRECTORY_LISTENER| valid directory| TRACE_DIRECTORY_LISTENER=$ORA_SQLNETV2 | | | | | |LOG_FILE_LISTENER | string | LOG_FILE_LISTENER=LISTENER | | | | | |LOG_DIRECTORY_LISTENER | valid directory| LOG_DIRECTORY_LISTENER=$ORA_ERRORS | | | | | ------------------------------------------------------------------------------ ________________________________________ 7c. Valid INTCHG.ORA Diagnostic Parameters ========================================== The following table shows the valid INTCHG.ORA parameters used in logging and tracing of the Interchange. ---------------------------------------------------------------------------------- | | | | | PARAMETERS | VALUES | Example (DOS client, UNIX server) | | | (default)| | |------------------------|--------------------|------------------------------------| | | | | |TRACE_LEVEL_CMANAGER | OFF|USER|ADMIN | TRACE_LEVEL_CMANAGER=USER | | | | | |TRACE_FILE_CMANAGER | string (CMG.TRC) | TRACE_FILE_CMANAGER=CMANAGER | | | | | |TRACE_DIRECTORY_CMANAGER| valid directory | TRACE_DIRECTORY_CMANAGER=C:\ADMIN | | | | | |LOG_FILE_CMANAGER | string (INTCHG.LOG)| LOG_FILE_CMANAGER=CMANAGER | | | | | |LOG_DIRECTORY_CMANAGER | valid directory | LOG_DIRECTORY_CMANAGER=C:\ADMIN | | | | | |LOGGING_CMANAGER | OFF/ON | LOGGING_CMANAGER=ON | | | | | |LOG_INTERVAL_CMANAGER | Any no of minutes | LOG_INTERVAL_CMANAGER=60 | | | (60 minutes)| | |TRACE_LEVEL_NAVIGATOR | OFF/USER/ADMIN | TRACE_LEVEL_NAVIGATOR=ADMIN | | | | | |TRACE_FILE_NAVIGATOR | string (NAV.TRC)| TRACE_FILE_NAVIGATOR=NAVIGATOR | | | | | |TRACE_DIRECTORY_NAVIGATOR| valid directory | TRACE_DIRECTORY_NAVIGATOR=C:\ADMIN | | | | | |LOG_FILE_NAVIGATOR |string (NAVGATR.LOG)| LOG_FILE_NAVIGATOR=NAVIGATOR | | | | | |LOG_DIRECTORY_NAVIGATOR | valid directory | LOG_DIRECTORY_NAVIGATOR=C:\ADMIN | | | | | |LOGGING_NAVIGATOR | OFF/ON | LOGGING_NAVIGATOR=OFF | | | | | |LOG_LEVEL_NAVIGATOR | ERRORS|ALL (ERRORS)| LOG_LEVEL_NAVIGATOR=ERRORS | | | | | ---------------------------------------------------------------------------------- Note: The pump component shares the trace parameters of the Connection Manager, but it generates a separate trace file with the unchangeable default name PMPpid.TRC. ________________________________________ 7d. Valid NAMES.ORA Diagnostic Parameters ========================================= The following table shows the valid NAMES.ORA parameters used in logging and tracing of the Names server. ------------------------------------------------------------------------------ | | | | | PARAMETERS | VALUES | Example (DOS client, UNIX server) | | | (default)| | |------------------------|----------------|------------------------------------| | | | | | NAMES.TRACE_LEVEL | OFF/USER/ADMIN | NAMES.TRACE_LEVEL=ADMIN | | | | | | NAMES.TRACE_FILE | file(names.trc)| NAMES.TRACE_FILE=nsrv3.trc | | | | | | NAMES.TRACE_DIRECTORY | directory | NAMES.TRACE_DIRECTORY=/o7/net/trace| | | | | | NAMES.TRACE_UNIQUE | TRUE/FALSE | NAMES.TRACE_UNIQUE=TRUE or ON/OFF | | | | | | NAMES.LOG_FILE | file(names.log)| NAMES.LOG_FILE=nsrv1.log | | | | | | NAMES.LOG_DIRECTORY | directory | NAMES.LOG_DIRECTORY= /o7/net/log | | | | | ------------------------------------------------------------------------------ ________________________________________ 8. Example of a Trace File =========================== In the following example, the SQLNET.ORA file includes the following line: TRACE_LEVEL_CLIENT = ADMIN The following trace file is the result of a connection attempt that failed because the hostname is invalid. The trace output is a combination of debugging aids for Oracle specialists and English information for network administrators. Several key events can be seen by analyzing this output from beginning to end: (A) The client describes the outgoing data in the connect descriptor used to contact the server. (B) An event is received (connection request). (C) A connection is established over the available transport (in this case TCP/IP). (D) The connection is refused by the application, which is the listener. (E) The trace file shows the problem, as follows: -- ***hostname lookup failure! *** (F) Error 12545 is reported back to the client. If you look up Error 12545 in Chapter 3 of this Manual, you will find the following description: ORA-12545 TNS:Name lookup failure Cause: A protocol specific ADDRESS parameter cannot be resolved. Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect value is the node name. ++++++ NOTE: TRACE FILE EXTRACT +++++++ --- TRACE CONFIGURATION INFORMATION FOLLOWS --- New trace stream is "/private1/oracle/trace_admin.trc" New trace level is 6 --- TRACE CONFIGURATION INFORMATION ENDS --- ++++++ NOTE: Loading Parameter files now. +++++++ --- PARAMETER SOURCE INFORMATION FOLLOWS --- Attempted load of system pfile source /private1/oracle/network/admin/sqlnet.ora Parameter source was not loaded Error stack follows: NL-00405: cannot open parameter file Attempted load of local pfile source /home/ginger/.sqlnet.ora Parameter source loaded successfully -> PARAMETER TABLE LOAD RESULTS FOLLOW <- Some parameters may not have been loaded See dump for parameters which loaded OK -> PARAMETER TABLE HAS THE FOLLOWING CONTENTS <- TRACE_DIRECTORY_CLIENT = /private1/oracle trace_level_client = ADMIN TRACE_FILE_CLIENT = trace_admin --- PARAMETER SOURCE INFORMATION ENDS --- ++++++ NOTE: Reading Parameter files. +++++++ --- LOG CONFIGURATION INFORMATION FOLLOWS --- Attempted open of log stream "/private1/oracle/sqlnet.log" Successful stream open --- LOG CONFIGURATION INFORMATION ENDS --- Unable to get data from navigation file tnsnav.ora local names file is /home/ginger/.tnsnames.ora system names file is /etc/tnsnames.ora initial retry timeout for all servers is 500 csecs max request retries per server is 2 default zone is [root] Using nncin2a() to build connect descriptor for (possibly remote) database. initial load of /home/ginger/.tnsnames.ora -- failure, error stack follows -- NL-00405: cannot open parameter file -- NOTE: FILE CONTAINS ERRORS, SOME NAMES MAY BE MISSING initial load of /etc/tnsnames.ora -- failure, error stack follows -- NL-00427: bad list -- NOTE: FILE CONTAINS ERRORS, SOME NAMES MAY BE MISSING Inserting IPC address into connect descriptor returned from nncin2a(). ++++++ NOTE: Looking for Routing Information. +++++++ Calling address: (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala) (USER=ginger)))(ADDRESS_LIST=(ADDRESS=(PROTOCOL=ipc (KEY=bad_host))(ADDRESS=(PROTOCOL=tcp)(HOST=lavender) (PORT=1521)))) Getting local community information Looking for local addresses setup by nrigla No addresses in the preferred address list TNSNAV.ORA is not present. No local communities entry. Getting local address information Address list being processed... No community information so all addresses are "local" Resolving address to use to call destination or next hop Processing address list... No community entries so iterate over address list This a local community access Got routable address information ++++++ NOTE: Calling first address (IPC). +++++++ Making call with following address information: (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=ipc)(KEY=bad_host))) Calling with outgoing connect data (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala) (USER=ginger)))(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp) (HOST=lavender)(PORT=1521)))) (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=ipc)(KEY=bad_host))) KEY = bad_host connecting... opening transport... -- sd=8, op=1, resnt[0]=511, resnt[1]=2, resnt[2]=0 -- unable to open transport -- nsres: id=0, op=1, ns=12541, ns2=12560; nt[0]=511, nt[1]=2, nt[2]=0 connect attempt failed Call failed... Call made to destination Processing address list so continuing ++++++ NOTE: Looking for Routing Information. +++++++ Getting local community information Looking for local addresses setup by nrigla No addresses in the preferred address list TNSNAV.ORA is not present. No local communities entry. Getting local address information Address list being processed... No community information so all addresses are "local" Resolving address to use to call destination or next hop Processing address list... No community entries so iterate over address list This a local community access Got routable address information ++++++ NOTE: Calling second address (TCP/IP). +++++++ Making call with following address information: (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=tcp) (HOST=lavender)(PORT=1521))) Calling with outgoing connect data (DESCRIPTION=(CONNECT_DATA=(SID=trace)(CID=(PROGRAM=)(HOST=lala) (USER=ginger)))(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp) (HOST=lavender) (PORT=1521)))) (DESCRIPTION=(EMPTY=0)(ADDRESS=(PROTOCOL=tcp) (HOST=lavender)(PORT=1521))) port resolved to 1521 looking up IP addr for host: lavender -- *** hostname lookup failure! *** -- nsres: id=0, op=13, ns=12545, ns2=12560; nt[0]=515, nt[1]=0, nt[2]=0 Call failed... Exiting NRICALL with following termination result -1 -- error from nricall -- nr err code: 12206 -- ns main err code: 12545 -- ns (2) err code: 12560 -- nt main err code: 515 -- nt (2) err code: 0 -- nt OS err code: 0 -- Couldn't connect, returning 12545 Most tracing is very similar to this. If you have a basic understanding of the events the components will perform, you can identify the probable cause of an error in the text of the trace. ----- Note: ----- ORA-01595: error freeing extent (2) of rollback segment (9)): ============================================================= Note 1: ORA-01595, 00000, "error freeing extent (%s) of rollback segment (%s))" Cause: Some error occurred while freeing inactive rollback segment extents. Action: Investigate the accompanying error. Note 2: Two factors are necessary for this to happen. A rollback segment has extended beyond OPTIMAL. There are two or more transactions sharing the rollback segment at the time of the shrink. What happens is that the first process gets to the end of an extent, notices the need to shrink and begins the recursive transaction to do so. But the next transaction blunders past the end of that extent before the recursive transaction has been committed. The preferred solution is to have sufficient rollback segments to eliminate the sharing of rollback segments between processes. Look in V$RESOURCE_LIMIT for the high-water-mark of transactions. That is the number of rollback segments you need. The alternative solution is to raise OPTIMAL to reduce the risk of the error. Note 3: This error is harmless. You can try (and probably should) set optimal to null and maxextents to unlimited (which might minimize the frequency of these errors). These errors happen sometimes when oracle is shrinking the rollback segments upto the optimal size. The undo data for shrinking is also kept in the rollback segments. So when it attempts to shrink the same rollback segment where its trying to write the undo, it throws this warning. Its not a failure per se .. since oracle will retry and succeed. ----- Note: ----- OUI-10022: oraInventory cannot be used because it is in an invalid state ======================================================================== Note 1: ------- If there are other products installed through the OUI, create a copy of = the oraInst.loc file (depending on the UNIX system, possibly in /etc or /var/opt/oracle). Modify the inventory_loc parameter to point to a different location for = the OUI to create the oraInventory directory. Run the installer using the -invPtrLoc parameter (eg: runInstaller -invPtrLoc /PATH/oraInst.loc). This will retain the existing oraInventory directory and create a new = one for use by the new product. ----- Note: ----- Failure to extend rollback segment because of 30036 condition ============================================================== Not a serious problem. Do some undo tuning. ----- Note: ----- ORA-02049 ORA-2049 In a distributed transaction, a process is waiting for a lock to get released. Note 1: ------- Error: ORA 2049 Text: timeout: distributed transaction waiting for lock ------------------------------------------------------------------------------- Cause: Exceeded seconds waiting for lock. Action: treat as a deadlock *** Important: The notes below are for experienced users - See Note 22080.1 Explanation: Ignore the "Action" above - this is non-sense. Basically ORA 2049 is signalled if: a) you are waiting on another sessions TX enqueue (Eg: usually you are waiting for a row lock) AND b) you are performing a distributed operation. Eg: You are using a DB link for something, even if it is only a select AND c) You wait for longer than 'distributed_lock_timeout' The use of a DB Link opens you up to distributed rules of operation even if you only READ from it. You can either increase the timeout OR handle the ORA 2049 as a 'try again' exception that is not fatal. This mechanism exists to prevent deadlock so any handling of 'TRY AGAIN' should include an escape clause to prevent deadlock. Example: Session 1 Session 2 ~~~~~~~~~ ~~~~~~~~~ update t2@LINK set b=4 where b=3; select * from dual@LINK; update t2 set b=4 where b=3; ^^ ORA 2049 OR EVEN update t2 set b=4 where b=3; select * from dual@LINK; update t2 set b=4 where b=3; ^^ ORA 2049 Note 2: ------- Subject: ORA-2049 IN ANY DISTRIBUTED ENVIRONMENT Doc ID: 1029942.6 Type: PROBLEM Modified Date : 10-FEB-2009 Status: PUBLISHED Problem Summary: ================ ORA-2049 IN ANY DISTRIBUTED ENVIRONMENT Problem Description: ==================== You receive the following error in any distributed environment: multi-master replication, snapshots, distributed database or even a remote update and receive the following error: 02049, 00000, "timeout: distributed transaction waiting for lock" // *Cause: exceeded init.ora distributed_lock_timeout seconds waiting for lock Problem Explanation: ==================== This errors occurs because the replicated transaction could not acquire the proper DML lock at the remote site to execute the deferred remote procedure call. Search Words: ============= ORA-02049 dbms_defer_sys.execute dbms_defer_sys.push Solution Description: ===================== The following lists covers some possible causes for this and steps to take to resolve: 1) The remote site may be down. Do a 'ping' test to verify that the remote site(s) are available to send the TXN to. At the OS prompt: Ex. ping remotehostname The remote site may have been down while the attempt to push the TXN occurred. Check the sys.dba_jobs view for any broken jobs, BROKEN=Y and re-execute the job manually. Ex. sqlplus repadmin/repadmin sql> exec dbms_job.run(1); 2) Increase the DISTRIBUTED_LOCK_TIMEOUT in init.ora databases involved in the environment. The default value is 60 (seconds). Increase the value to 300 (seconds) and restart all of the replicated instances. 300 seconds is a common value in a distributed environment. Depending on the network speed the value for DISTRIBUTED_LOCK_TIMEOUT may need to be increased higher. See also Note 1018919.102 ORA-2049 DISTRIBUTED_LOCK_TIMEOUT IN ORACLE8I This note discusses the parameter being obsoleted, and its '_' alternative. 3) Check the remote databases for any EXCLUSIVE locks held on the table(s) involved. Query the V$LOCK view. Is the customer doing an ANALYZE TABLE TABLENAME COMPUTE STATISTICS or SELECT FOR UPDATE on the table? In 7.3 ANALYZE will put an exclusive lock on the object and prevent the transaction from completing. Check the object for TM locks from querying V$LOCK. Make sure there are no exclusive locks and then attempt to re-execute the transaction from the remote database as shown in step 1. In 10.2 an 'analyze table compute statistics' does not lock the table in exclusive mode. All it does is take out a row level exclusive lock, and this doesn't block distributed updates, inserts, or deletes. There are no TM mode 6 locks for this operation. Solution Explanation: ===================== It is not always enough to just increase the DISTRIBUTED_LOCK_TIMEOUT parameter. If increasing it is not helping, then you need to resolve issues at the remote site. There may be some locks on the tables Oracle needs to update. Reference: ========== DISTRIBUTED_LOCK_TIMEOUT in Oracle® Database Reference 10g Release 2 (10.2) Part Number B14237-02 DISTRIBUTED_LOCK_TIMEOUT in Oracle® Database Reference 11g Release 1 (11.1) Part Number B28320-01 Note 3: ------- Support and Historical Notes for "DISTRIBUTED_LOCK_TIMEOUT" This parameter was hidden in 8i and 9.0 and then made available again in 9.2 onwards. The parameter defines the number of seconds that a distributed transaction waits for a lock. If a session waits longer than this for the lock then ORA-2049 is signalled. Note that this timeout applies even to local lock waits if the session is in a distributed transaction. See Note 19332.1 for a simple example. This parameter can be useful to set a time-limit on statements. The session only needs to be using a DBLINK for this behaviour (timeouts) to be enabled. Articles: Overview of Init.Ora Parameter Reference notes Note 68462.1 Note 4: ------- ----- Note: ----- ORA-06502: PL/SQL: numeric or value error: character string buffer too small ============================================================================ Note 1: Hi, I am having a strange problem with an ORA-06502 error I am getting and don't understand why. I would expect this error to be quite easy to fix, it would suggest that a variable is not large enough to cope with a value being assigned to it. But I'm fairly sure that isn't the problem. Anyway I have a stored procedure similar to the following: PROCEDURE myproc(a_user IN VARCHAR2, p_1 OUT .%TYPE, p_2 OUT .%TYPE) IS BEGIN SELECT my_first_column, my_second_column INTO p_1, p_2 FROM my_table WHERE user_id = a_user; END; / The procedure is larger than this, but using error_position variables I have tracked it down to one SQL statement. But I don't understand why I'm getting the ORA-06502, because the variables I am selecting into are defined as the same types as the columns I'm selecting. The variable I am selecting into is in fact a VARCHAR2(4), but if I replace the sql statement with p_1 := 'AB'; it still fails. It succeeds if I do p_1 := 'A'; Has anyone seen this before or anything similar that they might be able to help me with please? Thanks, mtae. -- Answer 1: It is the code from which you are calling it that has the problem, e.g. DECLARE v1 varchar2(1); v2 varchar2(1); BEGIN my_proc ('USER',v1,v2); END; / -- Answer 2 try this: PROCEDURE myproc(a_user IN VARCHAR2, p_1 OUT varchar2, p_2 OUT varchar2) IS v_1 .%TYPE; v_2 .%TYPE; BEGIN SELECT my_first_column, my_second_column INTO v_1, v_2 FROM my_table WHERE user_id = a_user; p_1 := v_1; p_2 := v_2; END; / Comment from mtae Date: 07/28/2004 04:24AM PDT Author Comment It was the size of the variable that was being used as the actual parameter being passed in. Feeling very silly, but thanks, sometimes you can look at a problem too long. ----- Note: ----- ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], [] ===================================================================================================== thread: see this error every time I shutdown a 10gR3 grid control database on 10.2.0.3 RDBMS, even though all opmn and OMS processes are down. So far, I have not seen any problems, apart from the annoying shutdown warning. Note 365103.1 seems to indicate it can be ignored: Cause This is due to unpublished Bug 4483084 'ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE]' This is a bug in that an ORA-600 error is reported when it is found that something is still going on during shutdown. It does not indicate any damage or a problem in the system. Solution At the time of writing, it is likely that the fix will be to report a more meaningful external error, although this has not been finalised. The error is harmless so it is unlikely that this will be backported to 10.2. The error can be safely ignored as it does not indicate a problem with the database. thread: ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [],[], [], [], [], [], [] 14-DEC-06 05:15:35 GMT Hi, There is no patch available for the bug 4483084. You need to Ignore this error, as there is absolutely no impact to the database due to this error. Thanks, Ram ----- Note: ----- ORA-12518 Tns: Listener could not hand off: ------------------------------------------- >>>> thread 1: Q: ORA-12518 Tns: Listener could not hand off client conenction Posted: May 31, 2007 2:02 AM Reply Dear exeprts, Plz tell me how can I resolve ORA-12518 Tns: Listener could not hand off client conenction. ORA-12518: TNS:listener could not hand off client connection A: Your server is probably running out of memory and need to swap memory to disk. One cause can be an Oracle process consuming too much memory. A possible workaround is to set following parameter in the listener.ora and restart the listener: DIRECT_HANDOFF_TTC_LISTENER=OFF You might need to increase the value of large_pool_size. Regards. >>>> thread 2: Q: Hi All, I'm using oracle 10g in window XP system. Java programmers will be accessing the database. Frequently they will get "ORA-12518: TNS:listener could not hand off" error and through sqlplus also i'll get this error. But, after sometime it works fine. I checked tnsnames.ora and listner.ora files entry. they seems to be ok. i have used system name itself for HOST flag instead of IP address. But still i'm getting this error. Can anybody tell me what might be the problem? Thanks, A: From Oracle's error messages docco, we see -------- TNS-12518 TNS:listener could not hand off client connection Cause: The process of handing off a client connection to another process failed. Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If the problem persists, contact Oracle Support Services. -------- So what does the listener trace indicate? A: Did you by any chance upgrade with SP2? If so, you could be running into firewall problems - 1521 is open, the initial contact made, but the handoff to a random (blocked!) port fails... -- Regards, Frank van Bortel >>>> thread 3: Q: I install Oracle9i and Oracle8i on Win2000 Server. I used Listener of 9i. My database based on Oracle8i. I found this error:ORA-12518: TNS:listener could not hand off client connectionwhen I logged on database. If I restarted database and listener it run but a few minutes it failed. Can u help me??? A: Are you usting MTS? First start the listener and then the database ( both the databases). Now check the status of listener. if nothing works, try DIRECT_HANDOFF_TTC_ = OFF in listener.ora. >>>> thread 4 Q: This weekend I installed Oracle Enterprise 10g release 2 on Windows 2003 server. The server is a Xeon dual processor 2.5MHz each with 3GB RAM and 300GB harddisk on RAID 1. The installation was fine, I then installed our application on it, that went smoothly as well. I had 3 users logged in to test the installation and everything was ok. Today morning we had 100 users trying to login and some got access, but majority got the ORA error above and have no access. I checked the tnsnames.ora file and sqlnet.ora file, service on the database all looks ok. I also restarted the listener service on the server, but I still get this error message. I've also increased no of sessions to 1000. Has anyone ever come across a issue like this in Oracle 10g. Regards A: I think I've resolved the problem, majority of my users are away on easter break so when they return I will know whether this tweak has paid off or not. Basically my SGA settings were quite high, so 60% of RAM was being used by SGA and 40% by Windows. I basically reduced the total SGA to 800 MB and i've had no connection problems, ever since. >>>> thread 5 ORA-12518: TNS:listener could not hand off client connection Your server is probably running out of memory and need to swap memory to disk. One cause can be an Oracle process consuming too much memory. A possible workaround is to set following parameter in the listener.ora and restart the listener: DIRECT_HANDOFF_TTC_LISTENER=OFF Should you be working with Multi threaded server connections, you might need to increase the value of large_pool_size. ----- Note: ----- Private strand flush not complete: ---------------------------------- -- thread: Q: I just upgraded to Oracle 10g release 2 and I keep getting this error in my alert log Thread 1 cannot allocate new log, sequence 509 Private strand flush not complete Current log# 2 seq# 508 mem# 0: /usr/local/o1_mf_2_2cx5wnw5_.log Current log# 2 seq# 508 mem# 1: /usr/local/o1_mf_2_2cx5wrjk_.log What causes the "private strand flush not complete" message? A: This is not a bug, it's the expected behavior in 10gr2. The "private strand flush not complete" is a "noise" error, and can be disregarded because it relates to internal cache redo file management. Oracle Metalink note 372557.1 says that a "strand" is a new 10gr2 term for redo latches. It notes that a strand is a new mechanism to assign redo latches to multiple processes, and it's related to the log_parallelism parameter. The note says that the number of strands depends on the cpu_count. When you switch redo logs you will see this alert log message since all private strands have to be flushed to the current redo log. -- thread: Q: HI, I'm using the Oracle 10g R2 in a server with Red Hat ES 4.0, and i received the following message in alert log "Private strand flush not complete", somebody knows this error? The part of log, where I found this error is: Fri Feb 10 10:30:52 2006 Thread 1 advanced to log sequence 5415 Current log# 8 seq# 5415 mem# 0: /db/oradata/bioprd/redo081.log Current log# 8 seq# 5415 mem# 1: /u02/oradata/bioprd/redo082.log Fri Feb 10 10:31:21 2006 Thread 1 cannot allocate new log, sequence 5416 Private strand flush not complete Current log# 8 seq# 5415 mem# 0: /db/oradata/bioprd/redo081.log Current log# 8 seq# 5415 mem# 1: /u02/oradata/bioprd/redo082.log Thread 1 advanced to log sequence 5416 Current log# 13 seq# 5416 mem# 0: /db/oradata/bioprd/redo131.log Current log# 13 seq# 5416 mem# 1: /u02/oradata/bioprd/redo132.log Thanks, A: Hi, Note:372557.1 has brief explanation of this message. Best Regards, -- thread: Q: Hi, I`m having such info in alert_logfile... maybee some ideas or info... Private strand flush not complete What could this posible mean ?? Thu Feb 9 22:03:44 2006 Thread 1 cannot allocate new log, sequence 387 Private strand flush not complete Current log# 2 seq# 386 mem# 0: /path/redo02.log Thread 1 advanced to log sequence 387 Current log# 3 seq# 387 mem# 0: /path/redo03.log Thanks A: see http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref4478 regards log file switch (private strand flush incomplete) User sessions trying to generate redo, wait on this event when LGWR waits for DBWR to complete flushing redo from IMU buffers into the log buffer; when DBWR is complete LGWR can then finish writing the current log, and then switch log files. Wait Time: 1 second Parameters: None Error message :Thread 1 cannot allocate new log ----------------------------------------------- Note 1: ------- Q: Hi Iam getting error message "Thread 1 cannot allocate new log", sequence40994 can any one help me out , how to overcome this problem. Give me a solution. regards A: Perhaps this will provide some guidance. Rick Sometimes, you can see in your alert.log file, the following corresponding messages: Thread 1 advanced to log sequence 248 Current log# 2 seq# 248 mem# 0: /prod1/oradata/logs/redologs02.log Thread 1 cannot allocate new log, sequence 249 Checkpoint not complete This message indicates that Oracle wants to reuse a redo log file, but the corresponding checkpoint associated is not terminated. In this case, Oracle must wait until the checkpoint is completely realized. This situation may be encountered particularly when the transactional activity is important. This situation may also be checked by tracing two statistics in the BSTAT/ESTAT report.txt file. The two statistics are: - Background checkpoint started. - Background checkpoint completed. These two statistics must not be different more than once. If this is not true, your database hangs on checkpoints. LGWR is unable to continue writing the next transactions until the checkpoints complete. Three reasons may explain this difference: - A frequency of checkpoints which is too high. - A checkpoints are starting but not completing - A DBWR which writes too slowly. The number of checkpoints completed and started as indicated by these statistics should be weighed against the duration of the bstat/estat report. Keep in mind the goal of only one log switch per hour, which ideally should equate to one checkpoint per hour as well. The way to resolve incomplete checkpoints is through tuning checkpoints and logs: 1) Give the checkpoint process more time to cycle through the logs - add more redo log groups - increase the size of the redo logs 2) Reduce the frequency of checkpoints - increase LOG_CHECKPOINT_INTERVAL - increase size of online redo logs 3) Improve the efficiency of checkpoints enabling the CKPT process with CHECKPOINT_PROCESS=TRUE 4) Set LOG_CHECKPOINT_TIMEOUT = 0. This disables the checkpointing based on time interval. 5) Another means of solving this error is for DBWR to quickly write the dirty buffers on disk. The parameter linked to this task is: DB_BLOCK_CHECKPOINT_BATCH. DB_BLOCK_CHECKPOINT_BATCH specifies the number of blocks which are dedicated inside the batch size for writing checkpoints. When you want to accelerate the checkpoints, it is necessary to increase this value. Note 2: ------- Q: Hi All, Lets generate a good discussion thread for this database performance issue. Sometimes this message is found in the alert log generated. Thread 1 advanced to log sequence xxx Current log# 2 seq# 248 mem# 0: /df/sdfds Thread 1 cannot allocate new log, sequence xxx Checkpoint not complete I would appreciate a discussion on the following 1. What are the basic reasons for this warning 2. What is the preventive measure to be taken / Methods to detect its occurance 3. What are the post occurance measures/solutions for this. Regards A: Increase size of your redo logs. A: Amongst other reasons, this happens when redo logs are not sized properly. A checkpoint could not be completed because a new log is trying to be allocated while it is still in use (or hasn't been archived yet). This can happen if you are running very long transactions that are producing large amounts of redo (which you did not anticipate) and the redo logs are too small to handle it. If you are not archiving, increasing the size of your logfiles should help (each log group should have at least 2 members on separate disks). Also, be aware of what type of hardware you are using. Typically, raid-5 is slower for writes than raid-1. If you are archiving and have increased the size of the redo logs, also try adding an additional arch process. I have read plenty of conflicting documentation on how to resolve this problem. One of the "solutions" is to increase the size of your logbuffer. I have not found this to be helpful (for my particular databases). In the future, make sure to monitor the ratio of redo log entries to requests (it should be around 5000 to 1). If it slips below this ratio, you may want to consider adding addtional members to your log groups and increasing their size. A: Configuring redo logs is an art and you may never archieve 100% of the time that there is no waiting for available log files. But in my opinion, the best bet for your situation is to add one (or more) redo log instead of increase the size of the redo logs. Because even if your redo logs are huge, but if your disk controller is slow, a large transaction (for example, data loading) may use up all three redo logs before the first redo log completes the archive and becomes available, thus Oracle will halt until the archive is completed. ----- Note: ----- tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10): ----------------------------------------------------------------- -- thread 1: Q: tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1) tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1) Most repords speak of a harmless message. Some reports refer to a bug affecting Oracle versions op to 10.2.0.2 ----- Note: ----- ORA-600 12333 ------------- thread 1: ORA-600[12333] is reported with three additional numeric values when arequest is being received from a network packet and the request code inthe packet is not recognized. The three additional values report theinvalid request values received. The error may have a number of different root causes. For example, anetwork error may have caused bad data to be received, or the clientapplication may have sent wrong data, or the data in the network buffermay have been overwritten. Since there are many potential causes of thiserror, it is essential to have a reproducible testcase to correctlydiagnose the underlying cause. If operating system network logs areavailable, it is advisable to check them for evidence of networkfailures which may indicate network transmission problems. thread 2: We just found out that it was related to Block option DML RETURNINGVALUE in Forms4.5 We set it to NO, and the problem was solved Thanks anyway thread 3: From: Oracle, Kalpana Malligere 05-Oct-99 22:09 Subject: Re : ORA-00600: internal error code, arguments: [12333], [0], [3], [81], [], [], [] Hello, An ORA-600 12333 occurs because there has been a client/server protocol violation. There can be many reasons for this: Network errors, network hardware problems, etc. Where do you see or when do you get this error? Do you have any idea what was going on at the time of this error? Which process received it, i.e., was it a background or user process? Were you running sql*loader? Does this error have any adverse impact on the application or database? We cannot generally progress unless there is reproducible test case or reproducible environment. There are many bugs logged for this error which are closed as 'could not reproduce'. In one such bug, the developer indicated that "The problem does not normally have any bad side effects." So suggest you try to isolate what is causing it as much as possible. The error can be due to underlying network problems as well. It is not indicative of a problem with the database itself. ----- Note: ----- Common Errors on Spatial. In the following sections, we list some common errors that you may encounter while location-enabling your application (starting with some of the frequently encountered errors). We also suggest the corrective actions for each error. Note that this list is not exhaustive. For other errors not listed here, you should refer to Oracle Spatial User's Guide and Oracle Technical Support for assistance. ORA-13226: Interface Not Supported Without a Spatial Index This error happens when you are using a spatial operator that cannot be evaluated without the use of the spatial index. This could happen if either there is no index on the column that you are using or the optimizer does not choose the index-based evaluation. Action: If there is no spatial index on the columns in the spatial operator, create an index. Otherwise, if the optimizer is not choosing the spatial index, then you should specify explicit hints such as INDEX or ORDERED to ensure that the spatial index is used. Refer to Chapter 8 for more details. ORA-13203: Failed to Read USER_SDO_GEOM_METADATA View This error occurs if the table you are trying to index does not have any metadata in the USER_SDO_GEOM_METADATA view. ----- Note: ----- SMON: Parallel transaction recovery tried: ------------------------------------------ Note 1: ------- Q: I was inserting 2.000.000 records in a table and the connection has been killed. in my alert file I found the following message : "SMON: Parallel transaction recovery tried" here the content of the smon log file: Redo thread mounted by this instance: 1 Oracle process number: 6 Windows thread id: 2816, image: ORACLE.EXE *** 2006-06-29 21:33:05.484 *** SESSION ID:(5.1) 2006-06-29 21:33:05.453 *** 2006-06-29 21:33:05.484 SMON: Restarting fast_start parallel rollback *** 2006-06-30 02:50:54.695 SMON: Parallel transaction recovery tried A: Hi, This is an expected message when cleanup is occuring and you have fast_start_parallel_rollback set to cleanup rollback segments after a failed transaction Note 2: ------- You get this message if SMON failed to generate the slave servers necessary to perform a parallel rollback of a transaction. Check the value for the parameter, FAST_START_PARALLEL_ROLLBACK (default is LOW). LOW limits the number of rollback processes to 2 * CPU_COUNT. HIGH limits the number of rollback processes to 4 * CPU_COUNT. You may want to set the value of this parameter to FALSE. Received on Wed Mar 10 2004 - 23:58:40 CST Note 3: ------- Q: SMON: Parallel transaction recovery tried We found above message in alert_sid.log file. A: No need to worry about it. it is information message ... SMON start recovery in parrallel but failed and done in serial mode. Note 4: ------- The system monitor process (SMON) performs recovery, if necessary, at instance startup. SMON is also responsible for cleaning up temporary segments that are no longer in use and for coalescing contiguous free extents within dictionary managed tablespaces. If any terminated transactions were skipped during instance recovery because of file-read or offline errors, SMON recovers them when the tablespace or file is brought back online. SMON checks regularly to see whether it is needed. Other processes can call SMON if they detect a need for it. With Real Application Clusters, the SMON process of one instance can perform instance recovery for a failed CPU or instance. ----- Note: ----- KGX Atomic Operation: ===================== Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the Partitioning, OLAP and Data Mining options ORACLE_HOME = /dbms/tdbaaccp/ora10g/home System name: AIX Node name: pl003 Release: 3 Version: 5 Machine: 00CB560D4C00 Instance name: accptrid Redo thread mounted by this instance: 1 Oracle process number: 16 Unix process pid: 2547914, image: oracle@pl003 (TNS V1-V3) *** 2008-03-20 07:22:28.571 *** SERVICE NAME:(SYS$USERS) 2008-03-20 07:22:28.570 *** SESSION ID:(161.698) 2008-03-20 07:22:28.570 KGX cleanup... KGX Atomic Operation Log 700000036eb4350 Mutex 70000003f9adcf8(161, 0) idn 0 oper EXAM Cursor Parent uid 161 efd 5 whr 26 slp 0 oper=DEFAULT pt1=700000039ce1c30 pt2=700000039ce1e18 pt3=700000039ce2338 pt4=0 u41=0 stt=0 Note 1: ------- Q: Hi there, Oracle has started using mutexes and it is said that they are more efficient as compared to latches. Questions 1)What is mutex?I know mutex are mutual exclusions and they are the concept of multiple threads.What I want to know that how this concept is implemented in Oracledatabase? 2) How they are better than latches?both are used for low level locking so how one is better than the other? Any input is welcome. Thanks and regards Aman.... A: 1) Simply put mutexes are memory structures. They are used to serialize the access to shared structures. IMHO their most important characteristics are two. First, they can be taken in shared or exclusive mode. Second, getting a mutex can be done in wait or no-wait mode. 2) The main advantages over latches are that mutexes requires less memory and are faster to get and release. A: In Oracle, latches and mutexes are different things and managed using different modules. KSL* modules for latches and KGX* for mutexes. As Chris said, general mutex operatins require less CPU instructions than latch operations (as they aren't as sophisticated as latches and don't maintain get/miss counts as latches do). But the main scalability benefit comes from that there's a mutex structure in each child cursor handle and the mutex itself acts as cursor pin structure. So if you have a cursor open (or cached in session cursor cache) you don't need to get the library cache latch (which was previously needed for changing cursor pin status), but you can modify the cursor's mutex refcount directly (with help of pointers in open cursor state area in sessions UGA). Therefore you have much higher scalability when pinning/unpinning cursors (no library cache latching needed, virtually no false contention) and no separate pin structures need to be allocated/maintained. Few notes: 1) library cache latching is still needed for parsing etc, the mutexes address only the pinning issue in library cache 2) mutexes are currently used for library cache cursors (not other objects like PL/SQL stored procs, table defs etc) 3) As mutexes are a generic mechanism (not library cache specific) they're used in V$SQLSTATS underlying structures too 4) When mutexes are enabled, you won't see cursor pins from X$KGLPN anymore (as X$KGLPN is a fixed table based on the KGL pin array - which wouldn't be used for cursors anymore) ----- Note: ----- ktsmgtur(): TUR was not tuned for ... secs: =========================================== [pl101][tdbaprod][/dbms/tdbaprod/prodrman/admin/dump/bdump] cat prodrman_mmnl_1011950.trc /dbms/tdbaprod/prodrman/admin/dump/bdump/prodrman_mmnl_1011950.trc Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the Partitioning, OLAP and Data Mining options ORACLE_HOME = /dbms/tdbaprod/ora10g/home System name: AIX Node name: pl101 Release: 3 Version: 5 Machine: 00CB85FF4C00 Instance name: prodrman Redo thread mounted by this instance: 1 Oracle process number: 12 Unix process pid: 1011950, image: oracle@pl101 (MMNL) *** 2008-03-25 06:58:08.841 *** SERVICE NAME:(SYS$BACKGROUND) 2008-03-25 06:58:08.811 *** SESSION ID:(105.1) 2008-03-25 06:58:08.811 ktsmgtur(): TUR was not tuned for 361 secs What does this mean? Note 1: ------- Tur is a pathchecker, and if a SAN connection is lost, TUR will complain. ----- Note: ----- tkcrrpa: (WARN) Failed initial attempt to send ARCH message: ============================================================ > *** SERVICE NAME:() 2008-03-22 14:56:43.590 > *** SESSION ID:(221.1) 2008-03-22 14:56:43.590 > Maximum redo generation record size = 132096 bytes > Maximum redo generation change vector size = 98708 bytes > tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10) > tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x10) No good answer yet. ----- Note: ----- Weird errors 1: =============== In a trace file of an Oracle 10.2.0.3 db on AIX 5.3 we can find: >>>> DATABASE CALLED PRODTRID: > OS pid = 3907726 > loadavg : 1.12 1.09 1.13 > swap info: free_mem = 49.16M rsv = 24.00M > alloc = 2078.75M avail = 6144.00M swap_free = 4065.25M > F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD > 240001 A tdbaprod 3907726 1 0 60 20 1cfff7400 90692 06:00:39 - 0:00 ora_m000_prodtrid > open: Permission denied > 3907726: ora_m000_prodtrid > 0x00000001000f81e0 sskgpwwait(??, ??, ??, ??, ??) + ?? > 0x00000001000f5c54 skgpwwait(??, ??, ??, ??, ??) + 0x94 > 0x000000010010ba00 ksliwat(??, ??, ??, ??, ??, ??, ??, ??) + 0x640 > 0x0000000100116744 kslwaitns_timed(??, ??, ??, ??, ??, ??, ??, ??) + 0x24 > 0x0000000100170374 kskthbwt(0x0, 0x7000000, 0x0, 0x0, 0x15ab3c, 0x28284288, 0xfffffff, 0x7000000) + 0x214 > 0x0000000100116884 kslwait(??, ??, ??, ??, ??, ??) + 0x84 > 0x00000001002c8fb0 ksvrdp() + 0x550 > 0x00000001041c8c34 opirip(??, ??, ??) + 0x554 > 0x0000000102ab4ba8 opidrv(??, ??, ??) + 0x448 > 0x000000010409df30 sou2o(??, ??, ??, ??) + 0x90 > 0x0000000100000870 opimai_real(??, ??) + 0x150 > 0x00000001000006d8 main(??, ??) + 0x98 > 0x0000000100000360 __start() + 0x90 > *** 2008-04-01 06:01:43.294 At other instances we find: >>>> DATABASE CALLED PRODRMAN 06:01:41 - Check for changes since lastscan in file: /dbms/tdbaprod/prodrman/admin/dump/bdump/prodrman_cjq0_1003754.trc Warning: Errors detected in file /dbms/tdbaprod/prodrman/admin/dump/bdump/prodrman_cjq0_1003754.trc > OS pid = 3997922 > loadavg : 1.00 1.09 1.17 > swap info: free_mem = 62.76M rsv = 24.00M > alloc = 2087.91M avail = 6144.00M swap_free = 4056.09M > F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD > 240001 A tdbaprod 3997922 1 4 62 20 1322c8400 91516 05:43:28 - 0:00 ora_j000_prodrman > open: Permission denied > 3997922: ora_j000_prodrman > 0x00000001000f81e0 sskgpwwait(??, ??, ??, ??, ??) + ?? > 0x00000001000f5c54 skgpwwait(??, ??, ??, ??, ??) + 0x94 > 0x000000010010ba00 ksliwat(??, ??, ??, ??, ??, ??, ??, ??) + 0x640 > 0x0000000100116744 kslwaitns_timed(??, ??, ??, ??, ??, ??, ??, ??) + 0x24 > 0x0000000100170374 kskthbwt(0x0, 0x0, 0x7000000, 0x7000000, 0x15ab10, 0x1, 0xfffffff, 0x7000000) + 0x214 > 0x0000000100116884 kslwait(??, ??, ??, ??, ??, ??) + 0x84 > 0x00000001021d4fcc kkjsexe() + 0x32c > 0x00000001021d5d58 kkjrdp() + 0x478 > 0x00000001041c8bd0 opirip(??, ??, ??) + 0x4f0 > 0x0000000102ab4ba8 opidrv(??, ??, ??) + 0x448 > 0x000000010409df30 sou2o(??, ??, ??, ??) + 0x90 > 0x0000000100000870 opimai_real(??, ??) + 0x150 > 0x00000001000006d8 main(??, ??) + 0x98 > 0x0000000100000360 __start() + 0x90 > *** 2008-04-01 05:46:23.170 05:46:20 - Check for changes since lastscan in file: /dbms/tdbaprod/prodrman/admin/dump/bdump/prodrman_cjq0_1003754.trc Warning: Errors detected in file /dbms/tdbaprod/prodrman/admin/dump/bdump/prodrman_cjq0_1003754.trc > /dbms/tdbaprod/prodrman/admin/dump/bdump/prodrman_cjq0_1003754.trc > Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production > With the Partitioning, OLAP and Data Mining options > ORACLE_HOME = /dbms/tdbaprod/ora10g/home > System name: AIX > Node name: pl101 > Release: 3 > Version: 5 > Machine: 00CB85FF4C00 > Instance name: prodrman > Redo thread mounted by this instance: 1 > Oracle process number: 10 > Unix process pid: 1003754, image: oracle@pl101 (CJQ0) > > *** 2008-04-01 05:46:17.709 > *** SERVICE NAME:(SYS$BACKGROUND) 2008-04-01 05:44:28.394 > *** SESSION ID:(107.1) 2008-04-01 05:44:28.394 > Waited for process J000 to initialize for 60 seconds > *** 2008-04-01 05:46:17.709 > Dumping diagnostic information for J000: >>>> DATABASE CALLED ACCPROSS 06:01:26 - Check for changes since lastscan in file: /dbms/tdbaaccp/accpross/admin/dump/bdump/accpross_cjq0_1970272.trc Warning: Errors detected in file /dbms/tdbaaccp/accpross/admin/dump/bdump/accpross_cjq0_1970272.trc > /dbms/tdbaaccp/accpross/admin/dump/bdump/accpross_cjq0_1970272.trc > Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production > With the Partitioning, OLAP and Data Mining options > ORACLE_HOME = /dbms/tdbaaccp/ora10g/home > System name: AIX > Node name: pl003 > Release: 3 > Version: 5 > Machine: 00CB560D4C00 > Instance name: accpross > Redo thread mounted by this instance: 1 > Oracle process number: 10 > Unix process pid: 1970272, image: oracle@pl003 (CJQ0) > > *** 2008-04-01 06:01:21.210 > *** SERVICE NAME:(SYS$BACKGROUND) 2008-04-01 06:00:48.099 > *** SESSION ID:(217.1) 2008-04-01 06:00:48.099 > Waited for process J001 to initialize for 60 seconds > *** 2008-04-01 06:01:21.210 > Dumping diagnostic information for J001: > OS pid = 3645448 > loadavg : 1.28 1.18 1.16 > swap info: free_mem = 107.12M rsv = 24.00M > alloc = 3749.61M avail = 6144.00M swap_free = 2394.39M > F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD > 240001 A tdbaaccp 3645448 1 8 64 20 7566c510 91844 05:59:48 - 0:00 ora_j001_accpross > open: Permission denied > 3645448: ora_j001_accpross > 0x00000001000f81e0 sskgpwwait(??, ??, ??, ??, ??) + ?? > 0x00000001000f5c54 skgpwwait(??, ??, ??, ??, ??) + 0x94 > 0x000000010010ba00 ksliwat(??, ??, ??, ??, ??, ??, ??, ??) + 0x640 > 0x0000000100116744 kslwaitns_timed(??, ??, ??, ??, ??, ??, ??, ??) + 0x24 > 0x0000000100170374 kskthbwt(0x0, 0x0, 0x7000000, 0x7000000, 0x16656c, 0x1, 0xfffffff, 0x7000000) + 0x214 > 0x0000000100116884 kslwait(??, ??, ??, ??, ??, ??) + 0x84 > 0x00000001021d4fcc kkjsexe() + 0x32c > 0x00000001021d5d58 kkjrdp() + 0x478 > 0x00000001041c8bd0 opirip(??, ??, ??) + 0x4f0 > 0x0000000102ab4ba8 opidrv(??, ??, ??) + 0x448 > 0x000000010409df30 sou2o(??, ??, ??, ??) + 0x90 > 0x0000000100000870 opimai_real(??, ??) + 0x150 > 0x00000001000006d8 main(??, ??) + 0x98 > 0x0000000100000360 __start() + 0x90 > *** 2008-04-01 06:01:26.792 >>>> DATABASE CALLED PRODROSS 05:15:00 - Check for changes since lastscan in file: /dbms/tdbaprod/prodross/admin/dump/bdump/prodross_cjq0_2068516.trc Warning: Errors detected in file /dbms/tdbaprod/prodross/admin/dump/bdump/prodross_cjq0_2068516.trc > /dbms/tdbaprod/prodross/admin/dump/bdump/prodross_cjq0_2068516.trc > Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production > With the Partitioning, OLAP and Data Mining options > ORACLE_HOME = /dbms/tdbaprod/ora10g/home > System name: AIX > Node name: pl101 > Release: 3 > Version: 5 > Machine: 00CB85FF4C00 > Instance name: prodross > Redo thread mounted by this instance: 1 > Oracle process number: 10 > Unix process pid: 2068516, image: oracle@pl101 (CJQ0) > > *** 2008-04-01 05:13:52.362 > *** SERVICE NAME:(SYS$BACKGROUND) 2008-04-01 05:11:46.862 > *** SESSION ID:(217.1) 2008-04-01 05:11:46.861 > Waited for process J000 to initialize for 60 seconds > *** 2008-04-01 05:13:52.362 > Dumping diagnostic information for J000: > OS pid = 1855710 > loadavg : 1.08 1.15 1.20 > swap info: free_mem = 63.91M rsv = 24.00M > alloc = 2110.61M avail = 6144.00M swap_free = 4033.39M > F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD > 240001 A tdbaprod 1855710 1 4 66 22 1cb2f5400 92672 05:10:46 - 0:00 ora_j000_prodross > open: Permission denied > 1855710: ora_j000_prodross > 0x00000001000f81e0 sskgpwwait(??, ??, ??, ??, ??) + ?? > 0x00000001000f5c54 skgpwwait(??, ??, ??, ??, ??) + 0x94 > 0x000000010010ba00 ksliwat(??, ??, ??, ??, ??, ??, ??, ??) + 0x640 > 0x0000000100116744 kslwaitns_timed(??, ??, ??, ??, ??, ??, ??, ??) + 0x24 > 0x0000000100170374 kskthbwt(0x0, 0x0, 0x7000000, 0x7000000, 0x15aab2, 0x1, 0xfffffff, 0x7000000) + 0x214 > 0x0000000100116884 kslwait(??, ??, ??, ??, ??, ??) + 0x84 > 0x00000001021d4fcc kkjsexe() + 0x32c > 0x00000001021d5d58 kkjrdp() + 0x478 > 0x00000001041c8bd0 opirip(??, ??, ??) + 0x4f0 > 0x0000000102ab4ba8 opidrv(??, ??, ??) + 0x448 > 0x000000010409df30 sou2o(??, ??, ??, ??) + 0x90 > 0x0000000100000870 opimai_real(??, ??) + 0x150 > 0x00000001000006d8 main(??, ??) + 0x98 > 0x0000000100000360 __start() + 0x90 > *** 2008-04-01 05:13:59.017 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodroca/admin/dump/bdump/prodroca_cjq0_757946.trc Warning: Errors detected in file /dbms/tdbaprod/prodroca/admin/dump/bdump/prodroca_cjq0_757946.trc > OS pid = 1867996 > loadavg : 1.00 1.09 1.17 > swap info: free_mem = 66.71M rsv = 24.00M > alloc = 2087.91M avail = 6144.00M swap_free = 4056.09M > F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD > 240001 A tdbaprod 1867996 1 3 65 22 1078c5400 92656 05:44:06 - 0:00 ora_j000_prodroca > open: Permission denied > 1867996: ora_j000_prodroca > 0x00000001000f81e0 sskgpwwait(??, ??, ??, ??, ??) + ?? > 0x00000001000f5c54 skgpwwait(??, ??, ??, ??, ??) + 0x94 > 0x000000010010ba00 ksliwat(??, ??, ??, ??, ??, ??, ??, ??) + 0x640 > 0x0000000100116744 kslwaitns_timed(??, ??, ??, ??, ??, ??, ??, ??) + 0x24 > 0x0000000100170374 kskthbwt(0x0, 0x0, 0x7000000, 0x7000000, 0x15ab10, 0x1, 0xfffffff, 0x7000000) + 0x214 > 0x0000000100116884 kslwait(??, ??, ??, ??, ??, ??) + 0x84 > 0x00000001021d4fcc kkjsexe() + 0x32c > 0x00000001021d5d58 kkjrdp() + 0x478 > 0x00000001041c8bd0 opirip(??, ??, ??) + 0x4f0 > 0x0000000102ab4ba8 opidrv(??, ??, ??) + 0x448 > 0x000000010409df30 sou2o(??, ??, ??, ??) + 0x90 > 0x0000000100000870 opimai_real(??, ??) + 0x150 > 0x00000001000006d8 main(??, ??) + 0x98 > 0x0000000100000360 __start() + 0x90 > *** 2008-04-01 05:46:23.398 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodtrid/admin/dump/bdump/prodtrid_mmon_921794.trc Warning: Errors detected in file /dbms/tdbaprod/prodtrid/admin/dump/bdump/prodtrid_mmon_921794.trc > /dbms/tdbaprod/prodtrid/admin/dump/bdump/prodtrid_mmon_921794.trc > Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production > With the Partitioning, OLAP and Data Mining options > ORACLE_HOME = /dbms/tdbaprod/ora10g/home > System name: AIX > Node name: pl101 > Release: 3 > Version: 5 > Machine: 00CB85FF4C00 > Instance name: prodtrid > Redo thread mounted by this instance: 1 > Oracle process number: 11 > Unix process pid: 921794, image: oracle@pl101 (MMON) > > *** 2008-04-01 06:01:39.797 > *** SERVICE NAME:(SYS$BACKGROUND) 2008-04-01 06:01:39.385 > *** SESSION ID:(106.1) 2008-04-01 06:01:39.385 > Waited for process m000 to initialize for 60 seconds > *** 2008-04-01 06:01:39.797 > Dumping diagnostic information for m000: 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodrman/admin/dump/bdump/alert_prodrman.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodrman/admin/dump/udump/sbtio.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodroca/admin/dump/bdump/alert_prodroca.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodroca/admin/dump/udump/sbtio.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodross/admin/dump/bdump/alert_prodross.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodross/admin/dump/udump/sbtio.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodslot/admin/dump/bdump/alert_prodslot.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodslot/admin/dump/udump/sbtio.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodtrid/admin/dump/bdump/alert_prodtrid.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/prodtrid/admin/dump/udump/sbtio.log 06:01:42 - Check for changes since lastscan in file: /dbms/tdbaprod/ora10g/home/network/log/listener.log File /dbms/tdbaprod/ora10g/home/network/log/listener.log is changed, but no errors detected Note 1: ------- Q: Hi, we're running oracle 10 on AIX 5.3 TL04. We're experiencing some troubles with paging space. We've got 7 GB real mem and 10 GB paging space, and smoetimes the paging space occupation increases and it "freezes" the server (no telnet nor console connection). We've seen oracle has shown this error: CODE *** 2007-06-18 11:16:49.696 Dump diagnostics for process q002 pid 786600 which did not start after 120 seconds: (spawn_time:x10BF1F175 now:x10BF3CB36 diff:x1D9C1) *** 2007-06-18 11:16:54.668 Dumping diagnostic information for q002: OS pid = 786600 loadavg : 0.07 0.27 0.28 swap info: free_mem = 9.56M rsv = 40.00M alloc = 4397.23M avail = 10240.00M swap_free = 5842.77M skgpgpstack: fgets() timed out after 60 seconds skgpgpstack: pclose() timed out after 60 seconds ERROR: process 786600 is not alive *** 2007-06-18 11:19:41.152 *** 2007-06-18 11:27:36.403 Process startup failed, error stack: ORA-27300: OS system dependent operation:fork failed with status: 12 ORA-27301: OS failure message: Not enough space ORA-27302: failure occurred at: skgpspawn3 So we think it's oracle's fault, but we're not sure. We're AIX guys, not oracle, so we're not sure about this. Can anyone confirm if this is caused by oracle? A: Looks like a bug. We are running on a Windows 2003 Server Standard edition. I had the same problem. Server was not responding anymore after the following errors: ORA-27300: OS system dependent operation:spcdr:9261:4200 failed with status: 997 ORA-27301: OS failure message: Overlapped I/O operation is in progress. ORA-27302: failure occurred at: skgpspawn And later: O/S-Error: (OS 1450) Insufficient system resources exist to complete the requested service. We are running the latest patchset 10.2.0.2 because of a big problem in 10.2.0.1 (wrong parsing causes client memory problems. Procobol., plsql developer ect crash because oracle made mistakes skipping the parse process, goto direct execute and return corrupted data to the client. Tomorrow I will rise a level 1 TAR indicating we had a crach. Server is now running normaly. A: Oracle finally admit there was a bug: BUG 5607984 - ORACLE DOES NOT CLOSE TCP CONNECTIONS. REMAINS IN CLOSE_WAIT STATE. [On Windows 32-bit]. The patch 10 (patch number 5639232) is supposed to solve the problem for 10.2.0.2.0. We applied it monday morning and everything is fine up to now. This bug is also supposed to be solved in the 10.2.0.3.0 patchset that is availlable on the Metalink site. Note 2: ------- Q: question: ----------------------------------------------------------- my bdump received two error message traces this morning. One of the trace displays a lot of detail, mainly as: *** SESSION ID:(822.1) 2007-02-11 00:35:06.147 Waited for process J000 to initialize for 60 seconds *** 2007-02-11 00:35:20.276 Dumping diagnostic information for J000: OS pid = 811172 loadavg : 0.55 0.42 0.44 swap info: free_mem = 3.77M rsv = 24.50M alloc = 2418.36M avail = 6272.00M swap_free = 3853.64M F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 240001 A oracle 811172 1 0 60 20 5bf12400 86396 00:34:32 - 0:00 ora_j000_BAAN open: The file access permissions do not allow the specified action. Then whole bunch of the pointers and something like this "0x0000000100055800 kghbshrt(??, ??, ??, ??, ??, ??) + 0x80" how do I find out what really went wrong? This error occured after I did an export pump of the DB, about 10 minutes later. This is first time I sae such and the export pump has been for a year. My system is Oracle 10g R2 on AIX 5.3L Note 3: ------- At least here you have an explanation about the Oracle processes: pmon The process monitor performs process recovery when a user process fails. PMON is responsible for cleaning up the cache and freeing resources that the process was using. PMON also checks on the dispatcher processes (described later in this table) and server processes and restarts them if they have failed. mman Used for internal database tasks. dbw0 The database writer writes modified blocks from the database buffer cache to the datafiles. Oracle Database allows a maximum of 20 database writer processes (DBW0-DBW9 and DBWa-DBWj). The initialization parameter DB_WRITER_PROCESSES specifies the number of DBWn processes. The database selects an appropriate default setting for this initialization parameter (or might adjust a user specified setting) based upon the number of CPUs and the number of processor groups. lgwr The log writer process writes redo log entries to disk. Redo log entries are generated in the redo log buffer of the system global area (SGA), and LGWR writes the redo log entries sequentially into a redo log file. If the database has a multiplexed redo log, LGWR writes the redo log entries to a group of redo log files. ckpt At specific times, all modified database buffers in the system global area are written to the datafiles by DBWn. This event is called a checkpoint. The checkpoint process is responsible for signalling DBWn at checkpoints and updating all the datafiles and control files of the database to indicate the most recent checkpoint. smon The system monitor performs recovery when a failed instance starts up again. In a Real Application Clusters database, the SMON process of one instance can perform instance recovery for other instances that have failed. SMON also cleans up temporary segments that are no longer in use and recovers dead transactions skipped during system failure and instance recovery because of file-read or offline errors. These transactions are eventually recovered by SMON when the tablespace or file is brought back online. reco The recoverer process is used to resolve distributed transactions that are pending due to a network or system failure in a distributed database. At timed intervals, the local RECO attempts to connect to remote databases and automatically complete the commit or rollback of the local portion of any pending distributed transactions. cjq0 Job Queue Coordinator (CJQ0) Job queue processes are used for batch processing. The CJQ0 process dynamically spawns job queue slave processes (J000...J999) to run the jobs. d000 Dispatchers are optional background processes, present only when the shared server configuration is used. s000 Dunno. qmnc Queue monitor background process A queue monitor process which monitors the message queues. Used by Oracle Streams Advanced Queuing. mmon Performs various manageability-related background tasks. mmnl Performs frequent and light-weight manageability-related tasks, such as session history capture and metrics computation. j000 A job queue slave. (See cjq0) Addition: --------- Sep 13, 2006 Oracle Background Processes, incl. 10gR2 ------------------- --New in 10gR2 ------------------- PSP0 (new in 10gR2) - Process SPawner - to create and manage other Oracle processes. NOTE: There is no documentation currently in the Oracle Documentation set on this process. LNS1(new in 10gR2) - a network server process used in a Data Guard (primary) database. Further explaination From "What's New in Oracle Data Guard?" in the Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) "During asynchronous redo transmission, the network server (LNSn) process transmits redo data out of the online redo log files on the primary database and no longer interacts directly with the log writer process. This change in behavior allows the log writer (LGWR) process to write redo data to the current online redo log file and continue processing the next request without waiting for inter-process communication or network I/O to complete." ------------------- --New in 10gR1 ------------------- MMAN - Memory MANager - it serves as SGA Memory Broker and coordinates the sizing of the memory components, which keeps track of the sizes of the components and pending resize operations. Used by Automatic Shared Memory Management feature. RVWR -Recovery Writer - which is responsible for writing flashback logs which stores pre-image(s) of data blocks. It is used by Flashback database feature in 10g, which provides a way to quickly revert an entire Oracle database to the state it was in at a past point in time. - This is different from traditional point in time recovery. - One can use Flashback Database to back out changes that: - Have resulted in logical data corruptions. - Are a result of user error. - This feature is not applicable for recovering the database in case of media failure. - The time required for flashbacking a database to a specific time in past is DIRECTLY PROPORTIONAL to the number of changes made and not on the size of the database. Jnnn - Job queue processes which are spawned as needed by CJQ0 to complete scheduled jobs. This is not a new process. CTWR - Change Tracking Writer (CTWR) which works with the new block changed tracking features in 10g for fast RMAN incremental backups. MMNL - Memory Monitor Light process - which works with the Automatic Workload Repository new features (AWR) to write out full statistics buffers to disk as needed. MMON - Memory MONitor (MMON) process - is associated with the Automatic Workload Repository new features used for automatic problem detection and self-tuning. MMON writes out the required statistics for AWR on a scheduled basis. M000 - MMON background slave (m000) processes. CJQn - Job Queue monitoring process - which is initiated with the job_queue_processes parameter. This is not new. RBAL - It is the ASM related process that performs rebalancing of disk resources controlled by ASM. ARBx - These processes are managed by the RBAL process and are used to do the actual rebalancing of ASM controlled disk resources. The number of ARBx processes invoked is directly influenced by the asm_power_limit parameter. ASMB - is used to provide information to and from the Cluster Synchronization Services used by ASM to manage the disk resources. It is also used to update statistics and provide a heartbeat mechanism. Changes about Queue Monitor Processes The QMON processes are optional background processes for Oracle Streams Advanced Queueing (AQ) which monitor and maintain all the system and user owned AQ objects. These optional processes, like the job_queue processes, does not cause the instance to fail on process failure. They provide the mechanism for message expiration, retry, and delay, maintain queue statistics, remove processed messages from the queue table and maintain the dequeue IOT. QMNx - Pre-10g QMON Architecture The number of queue monitor processes is controlled via the dynamic initialisation parameter AQ_TM_PROCESSES. If this parameter is set to a non-zero value X, Oracle creates that number of QMNX processes starting from ora_qmn0_ (where is the identifier of the database) up to ora_qmnX_ ; if the parameter is not specified or is set to 0, then QMON processes are not created. There can be a maximum of 10 QMON processes running on a single instance. For example the parameter can be set in the init.ora as follows aq_tm_processes=1 or set dynamically via alter system set aq_tm_processes=1; QMNC & Qnnn - 10g QMON Architecture Beginning with release 10.1, the architecture of the QMON processes has been changed to an automatically controlled coordinator slave architecture. The Queue Monitor Coordinator, ora_qmnc_, dynamically spawns slaves named, ora_qXXX_, depending on the system load up to a maximum of 10 in total. For version 10.01.XX.XX onwards it is no longer necessary to set AQ_TM_PROCESSES when Oracle Streams AQ or Streams is used. However, if you do specify a value, then that value is taken into account. However, the number of qXXX processes can be different from what was specified by AQ_TM_PROCESSES. If AQ_TM_PROCESSES is not specified in versions 10.1 and above, QMNC only runs when you have AQ objects in your database. ----- Note: ----- ORA-00600: internal error code, arguments: [13080], [], [], [], [], [], [], []: ================================================================================ When running statement ALTER TABLE ENABLE CONSTAINT this ORA-00600 error appears. ----- Note: ----- WARNING: inbound connection timed out (ORA-3136): ================================================= Note 1: Q: WARNING: inbound connection timed out (ORA-3136) this error appearing in Alert log . Please explain following:--------------- 1.How to overcome this error? 2.Is there any adverse effect in long run? 3.Is it require to SHUTDOWN the DATABASE to solve it. A: A good dicussion at freelist.ora http://www.freelists.org/archives/oracle-l/08-2005/msg01627.html In 10gR2, SQLNET.INBOUND_CONNECT_TIMEOUT the parameters were set to have a default of 60 (seconds). Set the parameters SQLNET.INBOUND_CONNECT_TIMEOUT and INBOUND_CONNECT_TIMEOUT_listenername to 0 (indefinite). A: What the error is telling you is that a connection attempt was made, but the session authentication was not provided before SQLNET.INBOUND_CONNECT_TIMEOUT seconds. As far as adverse effects in the long run, you have a user or process that is unable to connect to the database. So someone is unhappy about the database/application. Before setting SQLNET.INBOUND_CONNECT_TIMEOUT, verify that there is not a firewall or Network Address Translation (NAT) between the client and server. Those are common cause for ORA-3136. Q: Subject: WARNING: inbound connection timed out (ORA-3136) I have been getting like 50 of these error message a day in my alert_log the past couple of days. Anybody know what they mean? WARNING: inbound connection timed out (ORA-3136) A: Yep this is annoying, especially if you have alert log monitors :(. I had these when I first went to 10G... make these changes to get rid of them: Listener.ora: INBOUND_CONNECT_TIMEOUT_=0 .. for every listener Sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT=0 Then the errors stop... Note 2: SQLNET.INBOUND_CONNECT_TIMEOUT Purpose Use the SQLNET.INBOUND_CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information. If the client fails to establish a connection and complete authentication in the time specified, then the database server terminates the connection. In addition, the database server logs the IP address of the client and an ORA-12170: TNS:Connect timeout occurred error message to the sqlnet.log file. The client receives either an ORA-12547: TNS:lost contact or an ORA-12637: Packet receive failed error message. . Without this parameter, a client connection to the database server can stay open indefinitely without authentication. Connections without authentication can introduce possible denial-of-service attacks, whereby malicious clients attempt to flood database servers with connect requests that consume resources. To protect both the database server and the listener, Oracle Corporation recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying values for these parameters, consider the following recommendations: Set both parameters to an initial low value. Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter. For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed. ----- Note: ----- AUTO SGA: Not free: =================== Q: Hi, We have 10gr2 on windows server 2003 standard edition. The below errors are generated in mman trace files every now and then. AUTO SGA: Not free 0x2DFE78A8, 4, 1, 0 AUTO SGA: Not free 0x2DFE78A8, 4, 1, 0 AUTO SGA: Not free 0x2DFE795C, 4, 1, 0 AUTO SGA: Not free 0x2DFE7A10, 4, 1, 0 AUTO SGA: Not free 0x2DFE7AC4, 4, 1, 0 AUTO SGA: Not free 0x2DFE7B78, 4, 1, 0 AUTO SGA: Not free 0x2DFE7C2C, 4, 1, 0 AUTO SGA: Not free 0x2DFE7CE0, 4, 1, 0 AUTO SGA: Not free 0x2DFE7D94, 4, 1, 0 AUTO SGA: Not free 0x2DFF2708, 4, 1, 0 metalink doesnt give much info either.( BUG : 5201883 for your reference ) did anybody happened to have come across this issue and probably resolved it. Any comments are appreciated. A: This can be safely ignored.Since ASMM(Automatic Shared Memory Management) is enabled at instance level, you might be hitting this bug. Check Metalink note: 394026.1 Adding the Metalink note. A: As stated in the bug description, either 1) ignore the messages and delete generated trace files periodically and/or 2) wait for patchset 10.2.0.4 ----- Note: ----- ORA-06512: ========== Error: ORA-06512: at line Cause: This error message indicates the line number in the PLSQL code that the error resulted. Action: For example, if you had the following PLSQL code: declare v_number number(2); begin v_number := 100; end; You would receive the following error message: ORA-06502 nummeric or value error. number precision too large ORA=06512 at line 4 So it tells you at which line the error is. ----- Note: ----- ORA-06512: at "SYS.DBMS_CDC_UTILITY": ===================================== Errormessage in trace file: > /dbms/tdbaplay/playroca/admin/dump/udump/playroca_ora_1667142.trc > Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production > With the Partitioning, OLAP and Data Mining options > ORACLE_HOME = /dbms/tdbaplay/ora10g/home > System name: AIX > Node name: pl003 > Release: 3 > Version: 5 > Machine: 00CB560D4C00 > Instance name: playroca > Redo thread mounted by this instance: 1 > Oracle process number: 27 > Unix process pid: 1667142, image: oracleplayroca@pl003 > > *** SERVICE NAME:(SYS$USERS) 2008-05-28 12:40:22.399 > *** SESSION ID:(530.27892) 2008-05-28 12:40:22.399 > oracle.jdbc.driver.OracleSQLException: ORA-01405: fetched column value is NULL > ORA-06512: at "SYS.DBMS_CDC_UTILITY", line 226 > ORA-06512: at line 1 > at oracle.jdbc.driver.T2SConnection.check_error(T2SConnection.java:153) > at oracle.jdbc.driver.T2SCallableStatement.checkError(T2SCallableStatement.java:92) > at oracle.jdbc.driver.T2SCallableStatement.executeForRows(T2SCallableStatement.java:449) > at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1294) > at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3514) > at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3620) > at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:5261) > at oracle.CDC.SubscriptionWindow.qccsero(SubscriptionWindow.java:759) > at oracle.CDC.SubscriptionWindow.extendWindow(SubscriptionWindow.java:337) > at oracle.CDC.SubscribeApi.extendWindow(SubscribeApi.java:428) ----- Note: ----- TNS-12519: TNS:no appropriate service handler found: ==================================================== Note 1: ------- >> Hi all, >> >> we have an Oracle 10 (version details below) on Linux (RHEL 4). When >> connecting via JDBC we get intermittend ORA-12519 (reflected as >> TNS-12519 in listener.log). sqlldr also has a problem, although at >> the moment I can't exactly determine whether it's the same (I'm >> guessing it is because the happen about the same time). >> >> Research on the web revealed that a too low value for "processes" >> might be the reason. (The other possible cause I found was non >> matching versions of DB and client but this is not the case here.) >> So we increased DB param "parallel_max_servers" to 200. Since the >> error still showed up we went up to 400. It's been quiet since the >> last change of this parameter on Tuesday but some minutes ago I got >> an email notification that the error occurred again. >> >> I rather not want to increase the value by trial and error since we >> have only 36 sessions on the database right now and there seems to be >> a discrepancy between parameter "processes" (at 150 now, the value is >> derived from "parallel_max_servers") and the actual # of processes. >> Also the system is not much utilized and there's enough free >> resources (CPU wise and memory wise). So I'd like to first find out >> what is causing this error before I take further measures. >> >> I checked the alert log but there were no significant entries. I >> checked job scheduling to check whether there might be a job that >> eats up connections, but no. I guess switching on some trace might >> be helpful but at the moment I don't have an idea which one would be >> appropriate. Any ideas? Thanks for any insights! >> > > I fought this battle earlier this month. > The problem is that the more recent version listeners "count" > the incominng connection requests. When the count would exceed the > processes value the ORA-12519 error is raised. The problem is that > the listener does not really count the disconnetions. I learns > of them only periodically. If/when you have many, many short lived > connections you can see this error. I had found this article which basically states the same: http://forums.oracle.com/forums/thread.jspa?threadID=360226&tstart=0 Note 2: ------- This is an issue your DBA needs to address, it is not due to your client application -- Here is a Metalink note I found - for further information you will need to contact support. Article-ID: Note 240710.1 Title: Intermittent TNS-12516 or TNS-12519 Errors Connecting Via Net Symptom(s) ~~~~~~~~~~ Client connections may intermittently fail with either of the following errors: TNS-12516 TNS:listener could not find instance with matching protocol stack TNS-12519 TNS:no appropriate service handler found Additionally, a TNS-12520 error may appear in the listener log. TNS:listener could not find available handler for requested type of server The output of the lsnrctl services command may show that the service handler is in a "blocked" state. e.g. '"DEDICATED" established:1 refused:0 state:blocked' Change(s) ~~~~~~~~~~ None necessarily. Perhaps increase in load. Cause ~~~~~~~ By way of instance registration, PMON is responsible for updating the listener with information about a particular instance such as load and dispatcher information. Maximum load for dedicated connections is determined by the PROCESSES parameter. The frequency at which PMON provides SERVICE_UPDATE information varies according to the workload of the instance. The maximum interval between these service updates is 10 minutes. The listener counts the number of connections it has established to the instance but does not immediately get information about connections that have terminated. Only when PMON updates the listener via SERVICE_UPDATE is the listener informed of current load. Since this can take as long as 10 minutes, there can be a difference between the current instance load according to the listener and the actual instance load. When the listener believes the current number of connections has reached maximum load, it may set the state of the service handler for an instance to "blocked" and begin refusing incoming client connections with either of the following errors: TNS-12516 TNS:listener could not find instance with matching protocol stack TNS-12519 TNS:no appropriate service handler found Additionally, a TNS-12520 error may appear in the listener log. The output of lsnrctl service may show that the service handler is "blocked". e.g. '"DEDICATED" established:1 refused:0 state:blocked' Fix ~~~~ Increase the value for PROCESSES. Note 3: ------- Q: Hi all, I installed 10g Release 2 on Windows 2003 ... My application working fine .... recently i got an error .. TNS-12519: TNS:no appropriate service handler found i checked my listener it is working fine... but after some time connection start working... What was the issue? Regards Mani A: It could be a system load issue. If the problem happens again, try executing "lsnrctl services". If you see something like the following : Service "test10" has 1 instance(s). Instance "test10", status READY, has 1 handler(s) for this service... Handler(s): "DEDICATED" established:0 refused:0 state:blocked LOCAL SERVER then you may want to increase PROCESSES initialization parameter. ----- Note: ----- Good article on ORA-7445 Subject: Introduction to 600/7445 Internal Error Analysis Doc ID: 390293.1 Type: TROUBLESHOOTING Modified Date : 13-OCT-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 10.2.0.2 Information in this document applies to any platform. Purpose The purpose of this troubleshooting article is to provide an insight into key areas of internal 600/7445 trace files to assist in deriving to a known bug or to highlight what might be needed by ORACLE Support to progress an issue further. Whilst the article can be used to some extent on 11g it is primarily written for versions V10204 will be considered at a future date but is beyond the scope of what can be reported here. The nature of Internal errors means no one approach can guarantee getting to a solution but again the intention is to provide an indication on notes that support make available to customers and a simple workflow process that assists for a vast majority of SRs. A simple example is illustrated to generate a known bug that is harmless to the database when generated, that said it should ONLY be used on a TEST database as it's not encouraged to willingly raise such errors in 'LIVE' environments. This example will then be used to highlight various sections and how each section can be useful for general 600/7445 analysis and again to provide the best chance of identifying a known bugfix should one be available. The article also makes links to a number of others for completeness including Note 232963.1 should a testcase be required as is the ideal case for all internal errors but understandably is not always possible dependent on the problem area. Tests were made on SUN but the bug is not platform specific, it may however show slightly different messages within the alert log and for Windows based platforms some tools/notes might not be applicable. However this does not distract from the primary aim of how a trace file can be analyzed. An Internal Error whether ORA-00600 or ORA-07445 can fall into many categories :- Issue reproducible and testcase can be provided Issue reproducible but no simple testcase perhaps due to code being oracle SQL, 3rd party SQL Issue not reproducible but persistent and formulates to some pattern e.g. once a day Issue not reproducible and random pattern to occurrences By definition if an issue is not reproducible at will in a customer environment a testcase may be very difficult to obtain but should always be attempted where possible. These are a simplified subset, depending on root cause there can be many 600/7445 errors. Typically the argument(s) of the error when unique should mean each are different problems but if occurring on same timestamp or one always soon follows another there might be some relationship and this will be for support to determine. Last Review Date September 5, 2006 Instructions for the Reader A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting. Troubleshooting Details Worked Example ------------------ A real life example will follow and a working methodology will then be provided. Conclusions will then be made at the end of the analysis and some standard questions will be commented on that should always be appropriate to analysis of Internal errors and perhaps any SR raised into support. The bug number identified will be reported in a later section so as to show the workflow/analysis methodology used without knowing the solution in advance. This article is only suitable for 1 error is raised but all are reported to be within the same tracefile. There will be cases where >1 error and >1 trace exist but this is beyond the scope of this 'Introduction'. Various sections of the trace are now reported based on this example, not all 600/7445 traces will allow for each section to be reviewed. Again this is a very simple example and of often combinations of traces will need to be understood which is beyond the scope of this article. Section 1 : Trace header information ------------------------------------- xxxx/xxxx_ora_24779.trc Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production With the Partitioning, OLAP and Data Mining options ORACLE_HOME = xxxxxx System name: SunOS Node name: xxxxxx Release: 5.8 Version: Generic_117350-38 Machine: sun4u Instance name: xxxxx Redo thread mounted by this instance: 1 Oracle process number: 15 Unix process pid: 24779, image: oracle@xxxxx (TNS V1-V3) This section gives general information on the machine/instance and version of RDBMS where the internal error has been seen, whilst important its certainly does not really contain much to narrow bug searches as this info is customer/machine specific where as a bug itself should really hold information generic to all customers. Section 2 : The 600 or 7445 internal error ------------------------------------------ *** SESSION ID:(143.5) 2006-07-18 10:45:03.004 Exception signal: 11 (SIGSEGV), code: 1 (Address not mapped to object), addr: 0xffffffff7b280000, PC: [0xffffffff7b700b58, memcpy()+1196] *** 2006-07-18 10:45:03.008 ksedmp: internal or fatal error ORA-07445: exception encountered: core dump [memcpy()+1196] [SIGSEGV] [Address not mapped to object] [0xFFFFFFFF7B280000] [] [] This article is not written to show the differences between ORA-00600/ORA-07445 errors in any detail. The basic difference between these two errors, is that an ORA-600 is a trapped error condition in the Oracle code that should not occur, whereasan ORA-7445 is an untrapped error condition detected by the operating system. Section 3 : Current SQL statement --------------------------------- Current SQL statement for this session: update a sET col11 = (select avg(b.col22) keep (dense_rank first order by (col22)) FROM b where b.col21= a.col12); Not all internal issues will show a current SQL statement and there is no simple reason why this is the case. If this does happen it is recommended to try and use all other sections to narrow the search space down. When present in an internal (600/7445) trace file it should always be locatable using a search in the trace file of 'Current SQL' and should be the first hit found. In addition there maybe a 'PLSQL Call Stack' that pinpoints the schema.object and line number for an internal issue. Section 4 : Call Stack Trace ----------------------------- The call stack within the trace file is seen as follows :- ----- Call Stack Trace ----- calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- ksedmp()+744 CALL ksedst() 000000840 ? FFFFFFFF7FFE7D5C ? 000000000 ? FFFFFFFF7FFE4850 ? FFFFFFFF7FFE35B8 ? FFFFFFFF7FFE3FB8 ? ssexhd()+1000 CALL ksedmp() 000106000 ? 106324A04 ? 106324000 ? 000106324 ? 000106000 ? 106324A04 ? sigacthandler()+44 PTR_CALL 0000000000000000 000380007 ? FFFFFFFF7FFEB9A0 ? 000000067 ? 000380000 ? 00000000B ? 106324A00 ? _memcpy()+592 PTR_CALL 0000000000000000 00000000B ? FFFFFFFF7FFEB9A0 ? FFFFFFFF7FFEB6C0 ? FFFFFFFFFFFFFFFF ? 000000004 ? 000000000 ? ksxb1bqb()+36 FRM_LESS __1cY__nis_writeCol FFFFFFFF7B2F0000 ? dStartFile6FpcpnNdi FFFFFFFF7B35EE90 ? rectory_obj__i_()+3 FFFFFFFFFFFE6DA0 ? 75 FFFFFFFFFFFFFFFF ? 000000004 ? 000000000 ? kxhrPack()+1088 CALL ksxb1bqb() FFFFFFFF7B0F7220 ? FFFFFFFF7B354BBF ? FFFFFFFFFFFF1070 ? FFFFFFFF7B2E5D60 ? FFFFFFFF7B0F7220 ? 000001FF0 ? qescaInsert()+280 CALL kxhrPack() 000000080 ? FFFFFFFF7B34A5E8 ? The stack function is the first column on each line, and so reads: ksedmp ssexhd sigacthandler memcpy ksxb1bqb ..... For clarity the full stack trace is summarised to :- Function List (to Full stack) (to Summary stack) ksedmp ssexhd sigacthandler memcpy ksxb1bqb kxhrPack qescaInsert subsr3 evaopn2 upderh upduaw kdusru kauupd updrow qerupRowProcedure qerupFetch updaul updThreePhaseExe updexe opiexe kpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o opimai_real main start There is no automated tool for customers to get into this form. Note 211909.1 reports a further example of ORA-7445 stack analysis. The call stack can be very powerful to narrow a problem down to known issues but if used incorrectly will generate many hits totally unrelated to the problem being encountered. As the functions and their purpose are ORACLE proprietry this article can only give pointers towards good practice and these include :- a) Ignore function names that are before the 600/7445 error so for this worked example searches on 'ksedmp','ssexhd' or 'sigacthandler' will not benefit. The top most routines are for error handling, so this is why the failing function 'memcpy()' is not at the top of the stack, and why the top most functions can be ignored. b) Ignore calls towards the end of the call stack c) Try a number of different searches based on the failing function from the 600/7445 and 4-5 functions after In this case a useful Metalink search would be : memcpy ksxb1bqb kxhrPack qescaInsert subsr3 Section 5 : Session Information ------------------------------- SO: 392b5a188, type: 4, owner: 392a5a5b8, flag: INIT/-/-/0x00 (session) sid: 143 trans: 3912d2f78, creator: 392a5a5b8, flag: (41) USR/- BSY/-/-/-/-/- DID: 0001-000F-0000000F, short-term DID: 0000-0000-00000000 txn branch: 0 oct: 6, prv: 0, sql: 38d8c05b0, psql: 38d8c0b20, user: 173/SCOTT O/S info: user: xxxxxx, term: pts/21, ospid: 24482, machine: xxxxxx program: sqlplus@xxxxxx (TNS V1-V3) application name: SQL*Plus, hash value=3669949024 last wait for 'SQL*Net message from client' blocking sess=0x0 seq=282 wait_time=830 seconds since wait started=1 A 600/7445 trace should always have a 'Call stack Trace' whether it contains function names or not, after this follows 'PROCESS STATE' information and in this we can search on keyword 'session'. The first hit should take us to the section of the trace file that shows where the error came from and the session/user affected (above they have been blanked to xxxxxx). In many cases we will see user, terminal and machine information that can often be useful for any issue that needs to be reproduced for further investigation. On many occasions an internal error will be reported in alert logs and the DBA will not necessarily have been informed by any users of the database/application that they encountered a problem. This section can often also show 3rd party sessions e.g. TOAD/PLSQL or even where the client is another ORACLE product e.g. FORMS/APPS and even if just a client process e.g. EXP/RMAN. This can be another powerful method of narrowing a problem down, in the case of a problem coming from 3rd party software it is important to determine wherever possible if an issue can be reproduced in SQLPLUS. Section 6 : Explain Plan Information ------------------------------------- ============ Plan Table ============ ---------------------------------------+-----------------------------------+ | Id | Operation | Name | Rows | Bytes | Cost | Time | ---------------------------------------+-----------------------------------+ | 0 | UPDATE STATEMENT | | | | 3 | | | 1 | UPDATE | A | | | | | | 2 | TABLE ACCESS FULL | A | 2 | 52 | 3 | 00:00:01 | | 3 | SORT AGGREGATE | | 1 | 26 | | | | 4 | TABLE ACCESS FULL | B | 1 | 26 | 3 | 00:00:01 | ---------------------------------------+-----------------------------------+ This section can be found in the 600/7445 trace (when present) using the case sensitive search 'Explain plan' and will be the first hit unless the SQL for example contained the same string. In this section the 'Plan Table' for the failing SQL will be reported and especially for CBO related internal errors might give a pointer to finding a workaround. For this worked example nothing really can be used but we might for example see the plan using a 'hash join' and if so a possible w/a to try would be hash_join_enabled=false. Caution should be used here, permanent workarounds should only be set in place if matching to a known bug and the implications are understood. Section 7 : Current Cursor Information -------------------------------------- Current cursor: 4, pgadep: 0 Open cursors(pls, sys, hwm, max): 11(3, 7, 50, 50) NULL 6 SYNTAX 0 PARSE 0 BOUND 5 FETCH 0 ROW 0 Cached frame pages(total, free): 4k(61, 58), 8k(10, 10), 16k(1, 1), 32k(0, 0) pgactx: 38d2c9e98 ctxcbk: 38d2c9b30 ctxqbc: 0 ctxrws: 38e751110 This can be found using the case sensitive search in the trace file of 'Current cur', this section will either tie up with the current SQL statement reported in the 600/7445 or when there is no SQL statement reported it 'might' assist in further analysis. Once the current cursor is known the information on this can be found using the search 'Cursor#X' where X is the value shown e.g in this case 4. However this is >=10.2 specific and so it should be noted that prior to 10.2 use the search 'Cursor X '. Cursor#4(ffffffff7b231828) state=BOUND curiob=ffffffff7b2456f8 curflg=4c fl2=0 par=0 ses=392b5a188 sqltxt(38d8c05b0)=update a sET col11 = (select avg(b.col22) keep (dense_rank first order by (col22)) FROM b where b.col21= a.col12) hash=e2ef469857c74a273b881c20276493b5 parent=38eabc4b8 maxchild=01 plk=38f664f50 ppn=nll If a SQL statement is using BIND variables it is the cursor information that often proves useful at isolating the values used in the SQL which again can be the key to reproducing a problem if data specific. ORA-00600/ORA-07445 Analysis : General Guidlines ------------------------------------------------ Now that the sections have been explained we need to ensure we use as systematic a procedure as possible to determine if a known issue/bug exists. It should be clear that a 600/7445 trace contains far more information but if the above sections together with what follows cannot conclude to a known issue it is recommended that a SR is raised to support. Three useful documents types can assist here :- OERI notes ---------- An 'OERI' article is a document provided where possible to customers that provides a brief meaning of the error/impact and known bugs relating to the 600/7445. The quickest way to find this information from Metalink is to search as : a) 7445 <1st argument> oeri or b) 600 <1st argument> oeri So if the internal error was 600[12333] the search is:600 12333 oeri So for this article and worked example the search would be : 7445 memcpy oeri Equally the 600/7445 tool as per Note 153788.1 can be used and if the trace file is submitted into this tool an OERI note will be reported where published. If the testcase is attempted on a WINDOWS platform the error reported in the alert and trace may not be the same and the tool might not return any hits. Finding a suitable example for all platforms is beyond the scope of this document. So for the latter search we should find Note 310531.1, it should be noted that not all bugs associated with an error will be tagged but ideally they would be. It should also be clear from the notes seen in this type of search that ORA-600[x]/7445[y] does not mean only one bug can attribute to the Internal error. BUG.8 notes ----------- If the OERI or if a search gets a hit to a bug there maybe a link to a note where the Metalink Noteid is .8 For this worked example Note 5162852.8 exists, also to illustrate their purpose we can take for example Note 4451759.8 These articles are automatically generated when a bug becomes fixed and will typicaly include :- --Product affected --Range of releases the bug/error is believe appropriate to --Known affected version(s) --Fixed version Together with the 'symptoms' of the bug and where possible workarounds. This information is also in the bug itself but the note provides this into a much clearer form. Patch Set : List of Bugfixes by Problem Type Articles ----------------------------------------------------- When a PSR is released ORACLE ensures there is an article that summarises all the bugfixes made into that PSR, this articles allows a quick search to customers to see if there is an ORA-600/ORA-7445 error of the same type in the PSR. As mentioned earlier in the OERI section just because there is a fix for the same type, it does not guarantee that the problem is the same. For example if one of these PSR notes mentions ORA-00600[729] it means that the fix relates to one specifc way this error can be encountered, it does not stop 600[729] occurring for other reasons and even with the latest PSR applied to a given RDBMS release the internal error could occur due to a new unknown bug. These documents can be found in Metalink using a search with keywords like :- patch set bug fixes problem type So if we are looking to see what fixes are made into the V92070 PSR we would use the six keywords : 9.2.0.7 patch set bug fixes problem type Metalink will produce many hits but then the internet browsers search function can be used to search on the string '9.2.0.7' to quickly isolate the note which in this case is Note 308894.1 It is recommended to search always on the highest PSR available for the version you are running on since the note will then also contain links to the previous PSRs. ORA-00600/ORA-07445 Analysis : Keyword Searches ----------------------------------------------- This is the stage of the article where we need to use the research gathered from trace files and known Metalink notes to see if we can use the Metalink knowledge base to determine if the internal error is a known bug. It was commented that Section4 of a trace file can be very powerful here but again it is impossible to provide one unique way to search the knowledge bases. Instead we will use the worked example and will give some recommendations for 'bad' and 'good' search practices. Bad Searches Practices ---------------------- a) Using first few calls of stack trace e.g ksedmp ssexhd sigacthandler memcpy b) Use of Metalink 'Advanced Search' and using the 'using any of the words' option The reason this is a poor search method is that it is likely too many hits will be returned especially if keywords like 600/7445 are used. The default search functionality is an AND base search where all keywords must be present and this provides for better searches and fewer unrelated hits. c) Using all of the stack trace. As explained above a default Metalink search will find hits that contain all the keywords and using the whole stack allows a real risk of getting zero hits returned. Good Searches Practices ------------------------ It should be noted that more than one search might actually be needed to get a feeling for what bugs/notes are relevant to the customers issue. The scope of what can be searched will depend on if a problem is reproducible. a) Isolating a good section of the 'Call Stack' from Section4 b) If SQL is known then look at SQL to see if there is something special on the SQL e.g for this worked example we know dense_rank is being used and this is not common SQL c) If a problem is reproducible and an explain plan is available look at the plan to see if there is something that can be changed at session level. An example was reported in Section6 and if a parameter is seen to make a query work this parameter can then become a very useful keyword for determining if a known bug exists. d) Using the RDBMS version as keyword can sometimes show if any bugs exist that contain a oneoff fix for the same internal error argument but caution is needed as it is not a guarantee that the bug will cover the same cause. With this information in mind the two searches :- memcpy ksxb1bqb kxhrPack qescaInsert subsr3 memcpy dense_rank both get very few bug hits and is quickly identified. ORA-00600/ORA-07445 Analysis : Key Questions ----------------------------------------------------- If trying to research an Internal error before raising a SR to ORACLE Support the following questions will help avoid further questions from analysts. These questions are asked in the Metalink template when raising a SR and if answered as clearly as possible this can greatly assist in getting to a solution. Is the error reproducible? If an issue is reproducible where possible it should also be tested from SQLPLUS (ref Section 5). It is possible that a known bug/new bug might only occur on JDBC based clients for example and time needs to be spent understanding the minimum configuration needed to reproduce a problem. If an issue is indeed reproducible in a controlled manner a testcase for the majority of issues should be possible and if a SR or pre-analysis is not matched to a known bug very rarely can a problem be fixed from a trace file alone. For this reason please be aware of Note 232963.1 Has this worked before? If functionality that was working has just stopped it would tend to suggest either some issue of data within one or more objects or some more significant change. If a 600/7445 is seen within Development particularly on higher PSRs/releases it could well be that you have found a new bug. Again depending on reproducibility a testcase ideally would be required. Has any new change been made recently e.g new code/new PSR or DB version/higher DB load? Rarely do 600/7445 errors just start to occur due to a database being open for a certain amount of time. Even a small change of init/spfile parameters can influence how the database operates so if any change is known it is better to mention asap no matter how small. What is frequency of the error, when did it start? On many occasions a 600/7445 will be seen as a oneoff and not to be seen again. If pre-analysis cannot be matched to a known issue and if in any doubt about an error a SR should always be raised. It is however necessary to be aware that if the error is a oneoff or sporadic there is a tradeoff between impact of error and further analysis, as covered below. On other occasions we might see the error on the hour or some consistent period of time, in these cases root cause might be some job that runs or linked to an ORACLE process that gets invoked at certain times. Finding some pattern can sometimes be vital to solving an issue and knowing when an issue truly started is very important to analysis. What is the known visible impact? Of course any 600/7445 [or any issue for all product support] should be raised as a SR to ORACLE if there is any concern. Sometimes an Internal errors impact is very clear in that we might see an error in a controlled manner only when a session logsoff the database or the database closes down. It is equally possible that a database may seem to be running stable with no users reporting problems and only by proactively looking at the alert can errors be seen. In all cases if a SR is raised to Support we will need to try and assess the impact of a given error and to make a confirmation asap if linked to something serious within the database eg corruption. In many cases of analysis there soon becomes a tradeoff between seeing the error in the alert and the further diagnostics needed to try and get to the root cause. For this reason if an error is a oneoff or very infrequent and determined not to visibly affect users a decision may need to be made on how far to go especially if running on a desupported release or not on the latest PSR. The above questions relate to Support asking this information from the customer, one of the key questions asked by customers to Support is :- 'Why am I being asked to go to the latest PSR when a bug has not been identified?' The primary answers for this are twofold :- a) Note 209768.1 explains the backport policy for new bugs. So if Support could not match analysis to a known issue, a new bug can be filed. Sometimes Development can release 'diagnostics patches' to better analyze new issue but it's recommended to use it on latest patchset. Also if on older PSRs it is far more likely for the customer to be running with >1 'oneoff' fix placing the customer into a configuration that is probably not seen with many other customers. b) Perhaps more importantly each PSR contains many fixes and can solve many issues without Support being able to determine why. For this reason the latest PSR is seen as a statistically faster option to solve a problem when an error cannot be matched to a known bug. Of course if considering the latest PSR appropriate backups and testing need to be made in advance. Summary and Conclusions --------------------------- The article can be summarised into key sections :- 1. Most importantly always raise a SR if anything is unclear 2. Consider the ORA600/7445 tool : Note 153788.1 3. Make use of the key articles surrounding internal errors ie OERI notes and BUGTAGS 4. Understand basic trace information to be able to use Metalink better for 'efficient' searching 5. If a SR is to be be raised provide as much information as possible based on the Metalink template questions as these will often be vital to solving the SR. In conclusion 600/7445 errors are not hopefully a common event to be seen by DBA's and analysis of these errors is not something that would be expected by themselves. However it is often of interest to many customers as to what is looked at within support and how we make a formal analysis. Therefore the articles purpose is to highlight some of these processes with the hope that some self analysis can be made and to assist customer/support interaction on these issues. References Note 146580.1 - What is an ORA-600 Internal Error? Note 146581.1 - How to deal with ORA-600 Internal Errors Note 153788.1 - Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool Note 154170.1 - How to find the offending SQL from a trace file Note 211909.1 - Customer Introduction to ORA-7445 Errors Note 232963.1 - How to Build a Testcase for Oracle Data Server Support to Reproduce ORA-600 and ORA-7445 Errors ----- Note: ----- Good article on ORA-7445 Subject: Customer Introduction to ORA-7445 Errors Doc ID: 211909.1 Type: BULLETIN Modified Date : 10-OCT-2008 Status: PUBLISHED Purpose The purpose of this note is to provide an introduction to ORA-7445 errors, and to suggest the next step in diagnosing the error. The note is written with a UNIX bias, although the concepts are generic. Scope & Application To be used by the DBA when reporting ORA-7445 errors to Oracle Support Services. What is an ORA-7445 error? An ORA-7445 error is raised by an Oracle server process when it has received a fatal signal from the operating system. The error may be raised in either a foreground or background process. The process will normally write an error to the alert log write a trace file in either user_dump_dest or background_dump_dest create a core dump in core_dump_dest There are many 'illegal' operations that the operating system can trap. A common example is a process writing to an invalid memory location, and so to protect the system the offending process will be sent a fatal signal. Typically, the signals seen are SIGBUS (signal 10, bus error) and SIGSEGV (signal 11, segmentation violation). There are other UNIX signals and exceptions that may happen, however, they are likely caused by OS problems rather than an Oracle problem. Examples of other signals are: SIGINT, SIGKILL, SIGSYS. A complete list is available in Note 1038055.6. An ORA-7445 is a generic error, and can occur from anywhere in the Oracle code. The precise location of the error is identified by the trace file it produces. What Does an ORA-7445 Error Look Like? The appearance of an ORA-7445 error varies slightly from platform to platform. The two general forms are illustrated here. Example 1 ORA-07445: exception encountered: core dump [run_some_SQL()+268] [SIGBUS] [Invalid address alignment] [] [] [] Example 2 ORA-07445: exception encountered: core dump [10] [2122262800] [261978112] [] [] [] Example 1 tells us: The error occurred in function run_some_SQL() The process received signal SIGBUS Some additional information pertinent to the signal Example 2 is less descriptive, although is exactly the same: The failing function is not given The process received signal 10 Some additional information, which is not useful at this time What Information Should be Collected? The following should always be collected. The alert log, stretching back to at least the previous instance startup prior to the error. Ensure the startup init.ora parameters are included. All ORA-7445 and ORA-600 trace files since the last instance startup This is to establish if the ORA-7445 being investigated is related to or a symptom of another error. (If a lot of trace files exist only collect the first 3 to 5 - Oracle Support will be able to tell from the alert.log if more trace files are required.) In some cases, a trace file is not generated. If this happens, the core dump should be located and a stack trace taken from that using an operating system debugger, as discussed in Note 1812.1. This information should be uploaded at the time an SR is created. Self Service Diagnosis and Initial Interrogation of the Trace File Metalink now offers an ORA-7445 search tool Note 208922.1, analogous to the ORA-600 lookup tool Note 153788.1. To use this tool effectively, customers will need to isolate The failing function, if given in the ORA-7445 error message, or The stack trace from the Oracle trace file The following snippet shows key information taken from a trace file. *** 2002-05-08 23:35:18.224 <---timestamp *** SESSION ID:(194.14075) 2002-05-08 23:35:18.202 Exception signal: 10 (SIGBUS), code: 1 (Invalid address alignment), addr: 0x41e7, PC: kjrfnd()+44 *** 2002-05-08 23:35:19.404 ksedmp: internal or fatal error ORA-07445: exception encountered: core dump [kjrfnd()+44] [SIGBUS] [Invalid address alignment] [16871] [] [] <----the errror Current SQL statement for this session: <---the current SQL statement DELETE FROM MY_TABLE WHERE COL1 < :b1 ----- PL/SQL Call Stack ----- object line object handle number name e560c680 35 anonymous block e560c680 290 anonymous block ----- Call Stack Trace ----- <----Stack trace starts here calling call entry argument values in hex location type point (? means dubious value) -------------------- -------- -------------------- ---------------------------- ksedmp()+168 CALL ksedst()+0 540 ? 0 ? FFBE4F98 ? FFBE4A3C ? FFBE4A20 ? 0 ? ssexhd()+380 CALL ksedmp()+0 3 ? 0 ? 1 ? FFBE56B8 ? 1 ? 6 ? sigacthandler()+40 PTR_CALL 00000000 A ? FFBE5F10 ? 19FE000 ? 19FE000 ? 0 ? 0 ? kjrfnd()+44 PTR_CALL 00000000 A ? FFBE5F10 ? FFBE5C58 ? kjrref()+176 CALL kjrfnd()+0 4177 ? F6A7F020 ? 0 ? 41DF ? kjuocl()+732 CALL kjrref()+0 FFBE63AC ? 19FA400 ? kjusuc()+1260 CALL kjuocl()+0 FFBE6218 ? EB5FB9A8 ? EB5FB9A8 ? 5 ? 5 ? 0 ? ksipget()+832 CALL kjusuc()+0 19FA400 ? FFBE63AC ? 0 ? E2A2ED40 ? 19FA400 ? 8 ? ksqcmi()+3356 CALL ksipget()+0 10020 ? FFBE6648 ? EE15430C ? 0 ? 0 ? 0 ? ksqgtl()+944 CALL ksqcmi()+0 FFBE65A8 ? 1 ? EDEB4C90 ? EE1542D4 ? 1 ? 0 ? <... lots of stuff deleted here ...> sou2o()+20 CALL opidrv()+0 3C ? FFBEF784 ? 19F8000 ? 2F6C6F67 ? 0 ? 0 ? main()+160 CALL sou2o()+0 FFBEFA80 ? 3C ? 4 ? FFBEFA70 ? 1746CF4 ? 1A06318 ? _start()+220 CALL main()+0 0 ? FFBEFC2C ? 1A1D478 ? 19F8000 ? 0 ? 0 ? <----Stack trace ends here ----- Argument/Register Address Dump ----- The ORA-7445 error message and 'Current SQL statement' are self explanatory. The stack is the first column on each line, and reads: ksedmp <- ssexhd <- sigacthandler <- kjrfnd <- kjrref ..... The topmost routines are for error handling; this is why the failing function (kjrfnd()) is not at the top of the stack. For the purposes of the of the ORA-7445 tool, customers can simply cut and paste from the trace file, starting with the first line of the stack trace (in this case 'ksedmp....'). Customers should paste the first 15-20 lines, or until the line "Argument/Register Dump", whichever is shorter. When the third argument is “Object specific hardware error”, this indicates that the error was caused by the lack of some operating system resource, usually memory or swap space. In this case, please check your operating systems errorlog file for any accompanying error message, eg.: Linux: /var/log/messages, Solaris, HP Tru64: /var/adm/messages, HP-UX: /var/adm/syslog/syslog.log, AIX: /bin/errpt Apr 7 15:30:00 aemhrsPD1 genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow stack for pid 15415 (cron). Does The Problem Reproduce ? The time to resolution of an ORA-7745 error can be shortened considerably if the customer is able to reproduce the error at will, or better still, provide a reproducable testcase. The first step is to identify the SQL being run at the time of the error. Note 154170.1 discusses how to extract currently running SQL from trace files. It is important to remember that the currently running SQL maybe the victim of some previous problem, and may not reproduce the error when run in isolation. Often, it is useful to build up a pattern of when the error occurs. For example does the error only occur for certain bind variables in the current SQL? does the error always occur around a particular time of day? is the error timing related to other activity on the database, such as a backup or high load? is the error always from a given application, or user? when did the error first start to occur? What changed around this time? are there any other errors (especially ORA-7445 or ORA-600 errors) around the same time? Related Documents Note 153788.1 Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool Note 154170.1 How to find the offending SQL from a trace file Note 1812.1 TECH: Getting a Stack Trace from a CORE file Note 268451.1 ORA-7445: exception encountered: core dump [...] [SIGBUS] [Object specific hardware error] ----- Note: ----- Subject: Bug 1785175 - OERI:kcbgcur_9 from CLOB TO CHAR or BLOB TO RAW conversion Doc ID: 1785175.8 Type: PATCH Modified Date : 24-SEP-2008 Status: PUBLISHED Bug 1785175 OERI:kcbgcur_9 from CLOB TO CHAR or BLOB TO RAW conversion This note gives a brief overview of bug 1785175. The content was last updated on: 08-AUG-2003 Click here for details of each of the sections below. Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions >= 9.0 but < 10.1.0.2 Versions confirmed as being affected 9.2.0.1 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.2.0.2 (Server Patch Set) 10.1.0.2 (Base Release) Symptoms: Related To: Internal Error May Occur (ORA-600) ORA-600 [kcbgcur_9] Datatypes (LOBs/CLOB/BLOB/BFILE) Description Perfoming implicit or explicit CLOBTOCHAR or BLOBTORAW data type conversion may fail with ORA-600 [kcbgcur_9] Eg: update char_tab set a = to_char(to_clob('b')); Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice. References Bug 1785175 (This link will only work for PUBLISHED bugs) Note 245840.1 Information on the sections in this article ----- Note: ----- ORA-00600 ORA-600 [kole_t2u] Subject: ORA-600 [kole_t2u] With Multibyte Character Sets, While Appending To LOB In A Loop Doc ID: 739282.1 Type: PROBLEM Modified Date : 11-NOV-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.3 This problem can occur on any platform. Symptoms Following error can occure : ORA-600: internal error code, arguments: [kole_t2u], [34], [], [], [], [], [], [] with multibyte character sets, while appending to lob in a loop. Even after applying a patch for the Bug 4562807, encountered same ORA-600 [kole_t2u] error . Call stack functions : -------------------------- kole_t2u koklwrite kkxlwra kkxlcwra pevm_icd_call_commo pfrinstr_ICAL pfrrun_no_tool pfrrun plsql_run pricar pricbr prient2 prient kkxrpc kporpc opiodr ttcpip opitsk Cause The error is due to the published Bug 6407486 Abstract : ORA-600 [KOLE_T2U] USING A BLOB TABLE. Solution This Bug 6407486 has been fixed in the 10.2.0.5 and 11.2(11g) RDBMS version. There is no workaround available for this bug. Apply the one off patch for this bug. Check if there is a one off backport fix for your operating system, see Patch 6407486. ----- Note: ----- Doc ID: Note:293515.1 Subject: ORA-1578 ORA-26040 in a LOB segment - Script to solve the errors Type: PROBLEM Status: PUBLISHED Content Type: TEXT/X-HTML Creation Date: 09-DEC-2004 Last Revision Date: 25-FEB-2005 Purpose ============ - The purpose of this article is to provide a script to solve errors ORA-1578 / ORA-26040 when a lob block is accessed by a sql statement. - Note that the data inside the corrupted lob blocks is not salvageable. This procedure will update the lob column with an empty lob to avoid errors ORA-1578 / ORA-26040. - After applying this solution dbverify would still produce error DBV-200 until block marked as corrupted is reused and reformatted. Symptoms =========== - ORA-1578 and ORA-26040 are produced when accesing a lob column in a table: ORA-1578 : ORACLE data block corrupted (file # %s, block # %s) ORA-26040: Data block was loaded using the NOLOGGING option - dbverify for the datafile that produces the errors fails with: DBV-00200: Block, dba , already marked corrupted Example: dbv file=/oracle/oradata/data.dbf blocksize=8192 DBV-00200: Block, dba 54528484, already marked corrupted ..... The dba can be used to get the relative file number and block number: Relative File number: SQL> select dbms_utility.data_block_address_file(54528484) from dual; DBMS_UTILITY.DATA_BLOCK_ADDRESS_FILE(54528484) ---------------------------------------------- 13 Block Number: SQL> select dbms_utility.data_block_address_block(54528484) from dual; DBMS_UTILITY.DATA_BLOCK_ADDRESS_BLOCK(54528484) ----------------------------------------------- 2532 Cause ========== - LOB segment has been defined as NOLOGGING - LOB Blocks were marked as corrupted by Oracle after a datafile restore / recovery. Identify the table referencing the lob segment - Example ========================================================= Error example when accessing the lob column by a sql statement: ORA-01578 : ORACLE data block corrupted (file #13 block # 2532) ORA-01110 : datafile 13: '/oracle/oradata/data.dbf' ORA-26040 : Data block was loaded using the NOLOGGING option. 1. Query dba_extents to find out the lob segment name select owner, segment_name, segment_type from dba_extents where file_id = 13 and 2532 between block_id and block_id + blocks - 1; In our example it returned: owner=SCOTT segment_name=SYS_LOB0000029815C00006$$ segment_type=LOBSEGMENT 2. Query dba_lobs to identify the table_name and lob column name: select table_name, column_name from dba_lobs where segment_name = 'SYS_LOB0000029815C00006$$' and owner = 'SCOTT'; In our example it returned: table_name = EMP column_name = EMPLOYEE_ID_LOB Fix ====== 1. Identify the table rowid's referencing the corrupted lob segment blocks by running the following plsq script: rem ********************* Script begins here ******************** create table corrupted_data (corrupted_rowid rowid); set concat # declare error_1578 exception; pragma exception_init(error_1578,-1578); n number; begin for cursor_lob in (select rowid r, &&lob_column from &table_owner.&table_with_lob) loop begin n:=dbms_lob.instr(cursor_lob.&&lob_column,hextoraw('8899')) ; exception when error_1578 then insert into corrupted_data values (cursor_lob.r); commit; end; end loop; end; / undefine lob_column rem ********************* Script ends here ******************** When prompted by variable values and following our example: Enter value for lob_column: EMPLOYEE_ID_LOB Enter value for table_owner: SCOTT Enter value for table_with_lob: EMP 2. Update the lob column with empty lob to avoid ORA-1578 and ORA-26040: SQL> set concat # SQL> update &table_owner.&table_with_lob set &lob_column = empty_blob() where rowid in (select corrupted_rowid from corrupted_data); if &lob_column is a CLOB datatype, replace empty_blob by empty_clob. Reference ============== Note 290161.1 - The Gains and Pains of Nologging Operations ----- Note: ----- ORA-600 [12333] DURING INSERT VIA BPEL PM DATABASE ADAPTER Doc ID: 356359.1 Type: PROBLEM Modified Date : 03-JUN-2008 Status: MODERATED Applies to: Oracle(R) BPEL Process Manager - Version: 10.1.2.0 This problem can occur on any platform. Symptoms In a BPEL 10.1.2 patch 2 installation that uses Oracle 9i as dehydration store, once the pay load gets to certain size, the BPEL engine fails to insert audit trails and an error as follows is shown on the domain log: <2006-01-16 17:26:52,771> Error while invoking bean "cube delivery": Cannot insert invoke message. The process domain was unable to insert the invocation data for message "b4a41f5b4b2e7ff8:186c730:108d370d576:-7ff8", operation "initiate" in the datastore. The exception reported is: No more data to read from socket Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid. sql statement: INSERT INTO invoke_message_bin( message_guid, domain_ref, bin_csize, bin_usize, bin ) VALUES ( ?, ?, ?, ?, ? ) <2006-01-16 17:26:52,959> < default.collaxa.cube> At the same time, it is generated an internal error in the Alert Log file: ORA-00600: internal error code, arguments: [12333], [6], [197], [20], [], [], [] , [] The failing statement is: INSERT INTO invoke_message_bin( message_guid, domain_ref, bin_csize, bin_usize, bin ) VALUES ( :1, :2, :3, :4, :5 ) The stack trace is: ksedmp kgeriv kgesiv ksesic3 opitsk opiino opiodr opidrv Cause The cause of this problem has been identified and verified in an unpublished Bug:2452068. Solution You can upgrade to an Oracle 10g as dehydration store. OR Workaround Switch to OCI driver using the following steps. These steps are only good for the Developer edition. The steps need to be verified against the Mid-Tier edition ( This note will be updated once that is done). 0. Make sure an Oracle database or Oracle Sql client is installed on the same box where they run the BPEL PM 1. Set the following two environment variable on your SHELL environment where you start the BPEL PM. Please modify the syntax to fit your SHELL environment. ORACLE_HOME= export ORACLE_HOME LD_LIBRARY_PATH=$ORACLE_HOME/lib export LD_LIBRARY_PATH 2. Check the ORACLE_HOME/network/admin/tnsnames.ora. Identify the entry for the bpel dehydration store. If there is no such entrance, create one. Then note the instance name. Example: bpel = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = stacx56.us.oracle.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orcl) ) ) 3. Modify /integration/orabpel/system/appserver/oc4j/j2ee/home/config/data-sources.xml Change the jdbc url of the BPELServerDataSource to use oci driver Specifically, from url="jdbc:oracle:thin:orabpel/orabpel@localhost:1521:orcl" to url="jdbc:oracle:oci:orabpel/orabpel@bpel" The '@bpel' matches the 'bpel' in the tnsnames.ora. This may be different from the 'sid' which is 'orcl' in this case. 4. At the same SHELL terminal where you did #1, run startorabpel.sh References Bug 3877092 - ORA-600 [12333] THROUGH JDBC THIN CLIENT INSERTING INTO BLOB Note 315843.1 - ORA-600 Error When Inserting Into Blob Using Stream 9.2 ----- Note: ----- Subject: ORA-600 [qerixgetkey:optdesc] Doc ID: 285911.1 Type: REFERENCE Modified Date : 12-DEC-2008 Status: PUBLISHED Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article represents a partially published OERI note. It has been published because the ORA-600 error has been reported in at least one confirmed bug. Therefore, the SUGGESTIONS section of this article may help in terms of identifying the cause of the error. This specific ORA-600 error may be considered for full publication at a later date. If/when fully published, additional information will be available here on the nature of this error. SUGGESTIONS: If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 5897486 See Note 5897486.8 Wrong results / OERI from CONNECT BY with function based index Fixed: 11.2 Bug# 2670788 See Note 2670788.8 OERI[qerixgetkey:optdesc] / dump from SELECT using AND-EQUAL with DESC index Fixed: 9.2.0.6, 10.1.0.2 ----- Note: ----- Subject: ORA-600 [15709] Doc ID: 138457.1 Type: REFERENCE Modified Date : 12-DEC-2008 Status: PUBLISHED Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article discusses the internal error "ORA-600 [15709]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR: ORA-600 [15709] [a] [b] [c] VERSIONS: versions 7.1 to 10.1 DESCRIPTION: This error is raised when there are problems with parallel query processing while creating and shutting down query slave (server) processes. ARGUMENTS: The number of additional arguments vary between one and three depending on exactly which area of the code raises the internal error. FUNCTIONALITY: eXecute Fast (parallel) Process and buffer queue manager IMPACT: PROCESS FAILURE NON CORRUPTIVE - No underlying data corruption. SUGGESTIONS: Increase the parallel_max_servers parameter in init.ora and retry the operation. If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 6954722 See Note 6954722.8 OERI[15709] in SMON in RAC / instance crash Fixed: 10.2.0.5, 11.1.0.7, 11.2 Bug# 3256025 See Note 3256025.8 OERI[15709] cleaning up dead PQ slaves Fixed: 9.2.0.5, 10.1.0.2 Bug# 2362461 See Note 2362461.8 OERI:[15709] possible due to PQ slave cleanup race condition Fixed: 9.2.0.2, 10.1.0.2 Bug# 1615171 See Note 1615171.8 OERI:15709 possible on rollback of PDML which takes > 32 minutes Fixed: 8.1.7.3, 9.0.1.0 ----- Note: ----- Subject: RAC Instance Crashed With ORA-00600 [kjbrasr:pkey], [209735] Doc ID: 401627.1 Type: PROBLEM Modified Date : 30-APR-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.2 This problem can occur on any platform. SymptomsGot the following error several times in a 4 node RAC environment and caused instance to crash. ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [kjbrasr:pkey], [209735], [], [], [], [], [], [] The call stack from the trace file: ksedst ksedmp ksfdmp kgerinv kgeasnmierr kjbrasr kjbmpocr kjmxmpm kjmpmsgi kjmsm ksbrdp opirip Cannot Cannot Cannot opidrv sou2o opimai_real Cause The cause of the problem is due to the unpublished Bug 5106909.The bug is fixed in 11g. Bug 5106909 Status: 80,Development to Q/A Fixed In Ver: 11.1. Abstract: RAC: AFTER OBJECT MISMATCH WAIT FOR ASYNC FLUSH SolutionApply oneoff patch on top of 10.2.0.2 to fix this bug. You can download the patch from metalink: Patch 5106909 OR Workaround is to disable DRM (Dynamic Resource Mastering) To disable DRM, set _gc_affinity_time=0 _gc_undo_affinity=FALSE ----- Note: ----- ORA-600 [kgkprrpicknext1] Note 1: ------- Subject: ORA-600 [kgkprrpicknext1] Doc ID: 605616.1 Type: REFERENCE Modified Date : 09-JUL-2008 Status: PUBLISHED Note: For additional ORA-600 related information please read Note 146580.1 PURPOSE: This article represents a partially published OERI note. It has been published because the ORA-600 error has been reported in at least one confirmed bug. Therefore, the SUGGESTIONS section of this article may help in terms of identifying the cause of the error. This specific ORA-600 error may be considered for full publication at a later date. If/when fully published, additional information will be available here on the nature of this error. SUGGESTIONS: If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 6651027 See Note 6651027.8 OERI:kgkprrpicknext1 / dumps from DBRM Fixed: 10.2.0.4, 11.1.0.7, 11.2 Note 2: ------- Subject: Bug 6651027 - OERI:kgkprrpicknext1 / dumps from DBRM Doc ID: 6651027.8 Type: PATCH Modified Date : 24-SEP-2008 Status: PUBLISHED Bug 6651027 OERI:kgkprrpicknext1 / dumps from DBRM This note gives a brief overview of bug 6651027. The content was last updated on: 02-JUL-2008 Click here for details of each of the sections below. Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions < 11.2 Versions confirmed as being affected 11.1.0.6 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 11.2 (Future Release) 10.2.0.4 (Server Patch Set) 11.1.0.7 (Server Patch Set) Symptoms: Related To: Process May Dump (ORA-7445) / Abend / Abort Internal Error May Occur (ORA-600) ORA-600 [kgkprrpicknext1] (None Specified) Description ORA-600 [kgkprrpicknext1] / a dump can occur in DBRM whenever a runnable session is selected to run but internal data structures have a mismatch in state. Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice. References Bug 6651027 (This link will only work for PUBLISHED bugs) Note 245840.1 Information on the sections in this article ----- Note: ----- ----- Note: ----- This is an add-to list of NON CORRUPTIVE ORA-07445 and ORA-00600 errors with reference to Oracle Metalink Note number that you can use for further research: ORA-00600: internal error code, arguments: [504], [0x200433CC], [160], [7], [shared pool], [1], [0], [0x20043494] Note:28104.1 ORA-600 [kqludp2] "Unable to lock or pin dependent object" Note:264061.1 Ora-00600 [733], [1902261712], [Pga Heap], [], Note:338757.1 ORA-600 [4400] Note:138822.1 ORA-00600: internal error code, arguments: [kcbgtcr_4], [89427], [89247], [1152], [1], [], [], [] Note:138990.1 ORA-07445: exception encountered: core dump [kpogup()+508] [SIGSEGV] [Address not mapped to object] [0x16E] [] [] Note:278302.1 ORA-07445: exception encountered: core dump [eoc_ub1_array_hash] [SIGSEGV] [Address not mapped to object] [3815194624] [] [] Opened a TAR --> ORACLE response: process failure-rollback ONLY ORA-600 [kcbgcur_2] Note:138981.1 ORA-00600 [12209] Note:138325.1 #################################################################################################### SECTION 3: List of most Oracle RDBMS ORA- messages: #################################################################################################### Oracle® Database Error Messages 10g Release 2 ORA-00000 to ORA-00832 ORA-00000: normal, successful completion Cause: Normal exit. Action: None. ORA-00001: unique constraint (string.string) violated Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level. Action: Either remove the unique restriction or do not insert the key. ORA-00017: session requested to set trace event Cause: The current session was requested to set a trace event by another session. Action: This is used internally; no action is required. ORA-00018: maximum number of sessions exceeded Cause: All session state objects are in use. Action: Increase the value of the SESSIONS initialization parameter. ORA-00019: maximum number of session licenses exceeded Cause: All licenses are in use. Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter. ORA-00020: maximum number of processes (string) exceeded Cause: All process state objects are in use. Action: Increase the value of the PROCESSES initialization parameter. ORA-00021: session attached to some other process; cannot switch session Cause: The user session is currently used by others. Action: Do not switch to a session attached to some other process. ORA-00022: invalid session ID; access denied Cause: Either the session specified does not exist or the caller does not have the privilege to access it. Action: Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege. ORA-00023: session references process private memory; cannot detach session Cause: An attempt was made to detach the current session when it contains references to process private memory. Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session"s database links and/or cursors. Detaching a session with operating system privileges is always disallowed. ORA-00024: logins from more than one process not allowed in single-process mode Cause: Trying to login more than once from different processes for ORACLE started in single-process mode. Action: Logoff from the other process. ORA-00025: failed to allocate string Cause: Out of memory. Action: Restart with larger sga heap. ORA-00026: missing or invalid session ID Cause: Missing or invalid session ID string for ALTER SYSTEM KILL SESSION. Action: Retry with a valid session ID. ORA-00027: cannot kill current session Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current session. Action: None. ORA-00028: your session has been killed Cause: A privileged user has killed your session and you are no longer logged on to the database. Action: Login again if you wish to continue working. ORA-00029: session is not a user session Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.). Action: Retry with a user session ID. ORA-00030: User session ID does not exist. Cause: The user session ID no longer exists, probably because the session was logged out. Action: Use a valid session ID. ORA-00031: session marked for kill Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done. Action: No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner. ORA-00032: invalid session migration password Cause: The session migration password specified in a session creation call was invalid (probably too long). Action: Retry with a valid password (less than 30 chars). ORA-00033: current session has empty migration password Cause: An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed. Action: Create the session with a non-empty migration password. ORA-00034: cannot string in current PL/SQL session Cause: An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by "alter session disable commit in procedure") Action: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session. ORA-00036: maximum number of recursive SQL levels (string) exceeded Cause: An attempt was made to go more than the specified number of recursive SQL levels. Action: Remove the recursive SQL, possibly a recursive trigger. ORA-00037: cannot switch to a session belonging to a different server group Cause: An attempt was made to switch to a session in a different server group. This is not allowed. Action: Make sure the server switches to a session that belongs to its server group. ORA-00038: Cannot create session: server group belongs to another user Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user. Action: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user login in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner. ORA-00040: active time limit exceeded - call aborted Cause: The Resource Manager SWITCH_TIME limit was exceeded. Action: Reduce the complexity of the update or query, or contact your database administrator for more information. ORA-00041: active time limit exceeded - session terminated Cause: The Resource Manager SWITCH_TIME limit was exceeded. Action: Reduce the complexity of the update or query, or contact your database administrator for more information. ORA-00042: Unknown Service name string Cause: An attempt was made to use an invalid application service. Action: Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package. ORA-00050: operating system error occurred while obtaining an enqueue Cause: Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low. Action: Look up the operating system error in your system documentation and perform the needed action. ORA-00051: timeout occurred while waiting for a resource Cause: Usually due to a dead instance. Action: Check for any dead, unrecovered instances and recover them. ORA-00052: maximum number of enqueue resources (string) exceeded Cause: Ran out of enqueue resources. Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter. ORA-00053: maximum number of enqueues exceeded Cause: Ran out of enqueue state objects. Action: Increase the value of the ENQUEUES initialization parameter. ORA-00054: resource busy and acquire with NOWAIT specified Cause: Resource interested is busy. Action: Retry if necessary. ORA-00055: maximum number of DML locks exceeded Cause: Ran out of DML lock state objects. Action: Increase the value of the DML_LOCKS initialization parameter and warm start. ORA-00056: DDL lock on object "string.string" is already held in an incompatible mode Cause: An attempt was made to acquire a DDL lock that is already locked. Action: This happens if you attempt to drop a table that has parse locks on it. ORA-00057: maximum number of temporary table locks exceeded Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts. Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start. ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string) Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database. Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value. ORA-00059: maximum number of DB_FILES exceeded Cause: The value of the DB_FILES initialization parameter was exceeded. Action: Increase the value of the DB_FILES parameter and warm start. ORA-00060: deadlock detected while waiting for resource Cause: Transactions deadlocked one another while waiting for resources. Action: Look at the trace file to see the transactions and resources involved. Retry if necessary. ORA-00061: another instance has a different DML_LOCKS setting Cause: The shared instance being started is using DML locks, and the running instances are not, or vice-versa. Action: Ensure that all instances" INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero. ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0 Cause: The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX). Action: Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement. ORA-00063: maximum number of log files exceeded string Cause: The number of log files specificied exceeded the maximum number of log files supported in this release. Action: Re-create the control file with the highest number of log files no greater than the maximum supported in this release. ORA-00064: object is too large to allocate on this O/S (string,string) Cause: An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system. Action: Reduce the value of the initialization parameter. ORA-00065: initialization of FIXED_DATE failed Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss. Action: Make sure the initialization parameter is in the correct date format. ORA-00067: invalid value string for parameter string; must be at least string Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message. ORA-00068: invalid value string for parameter string, must be between string and string Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message. ORA-00069: cannot acquire lock -- table locks disabled for string Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ... ADD (...), and so on. Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command. ORA-00070: command string is not valid Cause: An invalid debugger command was specified. Action: Type HELP to see the list of available commands. ORA-00071: process number must be between 1 and string Cause: An invalid process number was specified. Action: Specify a valid process number. ORA-00072: process "string" is not active Cause: An invalid process was specified. Action: Specify a valid process. ORA-00073: command string takes between string and string argument(s) Cause: An incorrect number of arguments was specified. Action: Specify the correct number of arguments. Type HELP to see the list of commands and their syntax. ORA-00074: no process has been specified Cause: No debug process has been specified. Action: Specify a valid process. ORA-00075: process "string" not found in this instance Cause: The specified process was not logged on to the current instance. Action: Specify a valid process. ORA-00076: dump string not found Cause: An attempt was made to invoke a dump that does not exist. Action: Type DUMPLIST to see the list of available dumps. ORA-00077: dump string is not valid Cause: An attempt was made to invoke an invalid dump. Action: Try another dump. ORA-00078: cannot dump variables by name Cause: An attempt was made to dump a variable by name on a system that does not support this feature. Action: Try the PEEK command. ORA-00079: variable string not found Cause: An attempt was made to dump a variable that does not exist. Action: Use a valid variable name. ORA-00080: invalid global area specified by level string Cause: An attempt was made to dump an invalid global area. Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use to dump global area as well as bytes for every pointer; must be a multiple of 4. ORA-00081: address range [string, string) is not readable Cause: An attempt was made to read/write an invalid memory address range. Action: Try another address or length. ORA-00082: memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring Cause: An invalid length was specified for the POKE command. Action: Use a valid length (either 1, 2, 4, or possibly 8). ORA-00083: warning: possibly corrupt SGA mapped Cause: Even though there may be SGA corruptions, the SGA was mapped. Action: Use the DUMPSGA command to dump the SGA. ORA-00084: global area must be PGA, SGA, or UGA Cause: An attempt was made to dump an invalid global area. Action: Specify either PGA, SGA, or UGA. ORA-00085: current call does not exist Cause: An invalid attempt was made to dump the current call heap. Action: Wait until the process starts a call. ORA-00086: user call does not exist Cause: An invalid attempt was made to dump the user call heap. Action: Wait until the process starts a call. ORA-00087: command cannot be executed on remote instance Cause: Cluster database command issued for non cluster database ORADEBUG command. Action: Issue the command without the cluster database syntax. ORA-00088: command cannot be executed by shared server Cause: Debug command issued on shared server. Action: Reissue the command using a dedicated server. ORA-00089: invalid instance number in ORADEBUG command Cause: An invalid instance number was specified in a cluster database ORADEBUG command. Action: Reissue the command with valid instance numbers. ORA-00090: failed to allocate memory for cluster database ORADEBUG command Cause: Could not allocate memory needed to execute cluster database oradebug. Action: Reissue the command on each instance with single-instance oradebug. ORA-00091: LARGE_POOL_SIZE must be at least string Cause: The value of LARGE_POOL_SIZE is below the minimum size. Action: Increase the value of LARGE_POOL_SIZE past the minimum size. ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC. Action: Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC. ORA-00093: %s must be between string and string Cause: The parameter value is not in a valid range. Action: Modify the parameter value to be within the specified range. ORA-00094: %s requires an integer value Cause: The parameter value is not an integer. Action: Modify the parameter value to be an integer. ORA-00096: invalid value string for parameter string, must be from among string Cause: The value for the initialization parameter is invalid. Action: Choose a value as indicated by the message. ORA-00097: use of Oracle SQL feature not in SQL92 string Level Cause: Usage of Oracle"s SQL extensions. Action: none ORA-00100: no data found Cause: An application made reference to unknown or inaccessible data. Action: Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100. ORA-00101: invalid specification for system parameter DISPATCHERS Cause: The syntax for the DISPATCHERS parameter is incorrect. Action: Refer to the manual for correct syntax. ORA-00102: network protocol string cannot be used by dispatchers Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers. Action: Refer to the manual on network protocols supported by the dispatchers. ORA-00103: invalid network protocol; reserved for use by dispatchers Cause: The network specified in the SQL*Net connect string is reserved for use by the dispatchers. Action: Specify other network protocols in the connection string. ORA-00104: deadlock detected; all public servers blocked waiting for resources Cause: All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources. Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS. ORA-00105: too many dispatcher configurations Cause: Too many dispatcher configurations have been specified. No more can be added. Action: Consolidate the dispatcher configurations if possible. ORA-00106: cannot startup/shutdown database when connected to a dispatcher Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher. Action: Re-connect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string. ORA-00107: failed to connect to ORACLE listener process Cause: Most likely due to the fact that ORACLE listener has not been started. Action: Start ORACLE listener if it has not been started. Or else contact your ORACLE representative. ORA-00108: failed to set up dispatcher to accept connection asynchronously Cause: Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations. Action: Contact your ORACLE representative. ORA-00109: invalid value for attribute string: string Cause: The value specified for the attribute was incorrect. Action: Refer to the manual for the proper values. ORA-00110: invalid value string for attribute string, must be between string and string Cause: The value specified for the attribute was incorrect. Action: Specify a value within the range allowed. ORA-00111: invalid attribute string Cause: The specified attribute was not recognized. Action: Refer to the manual for the proper keyword to use to specify a dispatcher attribute. ORA-00112: value of string is null Cause: The attribute was specified with no value. Action: Specify a non-null value. ORA-00113: protocol name string is too long Cause: A protocol name specified in the DISPATCHERS system parameter is too long. Action: Use a valid protocol name for the DISPATCHERS value. ORA-00114: missing value for system parameter SERVICE_NAMES Cause: No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter. Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified. ORA-00115: connection refused; dispatcher connection table is full Cause: A connection request was refused by a dispatcher because the dispatcher cannot support any more connections. Action: Connect to a different dispatcher, or use a dedicated server. ORA-00116: SERVICE_NAMES name is too long Cause: A service name specified in the SERVICE_NAMES system parameter is too long. Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars). ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified. Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers. ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified. Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers. ORA-00119: invalid specification for system parameter string Cause: The syntax for the specified parameter is incorrect. Action: Refer to the Oracle Reference Manual for the correct syntax. ORA-00122: cannot initialize network configuration Cause: ORACLE could not initialize SQL*Net version 2. Action: Check the error stack for detailed information. ORA-00123: idle public server terminating Cause: Too many idle servers were waiting on the common queue. Action: This error is used internally, no action is required. ORA-00125: connection refused; invalid presentation Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported. Action: Correct the PRESENTATION specified in the TNS address. ORA-00126: connection refused; invalid duplicity Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported. Action: Correct the DUPLICITY specified in the TNS address. ORA-00127: dispatcher string does not exist Cause: There is currently no dispatcher running with the specified name. Action: Retry with a name of the form "D###" denoting an existing dispatcher process. ORA-00128: this command requires a dispatcher name Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] "dispatcher name" ORA-00129: listener address validation failed "string" Cause: An error was encountered while validating the listener address. Action: Resolve error or contact your ORACLE representative. ORA-00130: invalid listener address "string" Cause: The listener address specification is not valid. Action: Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct. ORA-00131: network protocol does not support registration "string" Cause: The specified protocol does not support async notification. Action: Refer to the manual for information on supported network protocols. ORA-00132: syntax error or unresolved network name "string" Cause: Listener address has syntax error or cannot be resolved. Action: If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct. ORA-00133: value of string is too long Cause: The value specified for the attribute was too long. Action: Use shorter names and keywords or remove unneeded blanks. ORA-00134: invalid DISPATCHERS specification #string Cause: The syntax for the n-th DISPATCHERS specification was incorrect. Action: Refer to the Oracle Reference Manual for the correct syntax. ORA-00150: duplicate transaction ID Cause: Attempted to start a new transaction with an ID already in use by an existing transaction. Action: Check your application. ORA-00151: invalid transaction ID Cause: The specified transaction ID does not correspond to an existing valid transaction. Action: Check your application. ORA-00152: current session does not match requested session Cause: The current session is not the same as the session that was passed into a upixado() call. Action: Check your application. ORA-00153: internal error in XA library Cause: The XA library could not access thread-specific pointers. Action: Contact customer support. ORA-00154: protocol error in transaction monitor Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended. Action: Contact the transaction monitor customer support. ORA-00155: cannot perform work outside of global transaction Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction. Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work. ORA-00160: global transaction length string is greater than maximum (string) Cause: An external global transaction ID with a too large length field was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00161: transaction branch length string is illegal (maximum allowed string) Cause: An external transaction branch ID with a length either too large or 0 was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00162: external dbid length string is greater than maximum (string) Cause: An external database name with too large a length field was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00163: internal database name length string is greater than maximum (string) Cause: An internal database name with a too large length field was passed in. Action: Report the problem to your external transaction coordinator vendor. ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction. Action: Roll back or commit the current distributed transaction first. ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation. Action: none ORA-00166: remote/local nesting level is too deep Cause: Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table. Action: Rearrange the query or co-locate the functions with the tables. ORA-00200: control file could not be created Cause: It was not possible to create the control file. Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again. ORA-00201: control file version string incompatible with ORACLE version string Cause: The control file was created by incompatible software. Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release. ORA-00202: control file: "string" Cause: This message reports the name file involved in other messages. Action: See associated error messages for a description of the problem. ORA-00203: using the wrong control files Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file. Action: Check that the correct control files were specified. ORA-00204: error in reading (block string, # blocks string) of control file Cause: A disk I/O failure was detected on reading the control file. Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk. ORA-00205: error in identifying control file, check alert log for more info Cause: The system could not find a control file of the specified name and size. Action: Check that ALL control files are online and that they are the same files that the system created at cold start time. ORA-00206: error in writing (block string, # blocks string) of control file Cause: A disk I/O failure was detected on writing the control file. Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk. ORA-00207: control files are not for the same database Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name. Action: Check that the control file is for the correct database and is not an old version. ORA-00208: number of control file names exceeds limit of string Cause: An attempt was made to use more control files than Oracle supports. Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files. ORA-00209: control file blocksize mismatch, check alert log for more info Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter. Action: Look at the alert log for more information. ORA-00210: cannot open the specified control file Cause: Cannot open the control file. Action: Check to make sure the control file exists and is not locked by some other program. ORA-00211: control file does not match previous control files Cause: A control file was specified that belongs to another database. Action: Find and install the correct control file. ORA-00212: block size string below minimum required size of string bytes Cause: The block size specified was too small. Space for the system overhead is required. Action: Specify a larger block size and retry the operation. ORA-00213: cannot reuse control file; old file size string, string required Cause: To reuse a control file, it must be the same size as the one previously used. Action: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement. ORA-00214: control file "string" version string inconsistent with file "string" version string Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used. Action: Use a consistant set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period. ORA-00215: must be at least one control file Cause: No control file is specified or the control file specified does not exist. Action: Specify at least one valid control file and retry the operation. ORA-00216: control file could not be resized for migration from 8.0.2 Cause: The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed. Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file. ORA-00217: control file could not be resized for new record types Cause: The control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed. Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file. ORA-00218: block size string of control file "string" does not match DB_BLOCK_SIZE (string) Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database. Action: Restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value. ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks) Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value. Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. ORA-00220: control file not mounted by first instance, check alert log for more info Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file. Action: Find and install the correct control file. ORA-00221: error on write to control file Cause: An error occurred when writing to one or more of the control files. Action: See accompanying messages. ORA-00222: operation would reuse name of a currently mounted control file Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file. Action: Retry the operation with a different filename. ORA-00223: convert file is invalid or incorrect version Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued. Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set. ORA-00224: control file resize attempted with illegal record type (string) Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter. Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16). ORA-00225: expected size string of control file differs from actual size string Cause: The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted. Action: Restore a good copy of the control file. ORA-00226: operation disallowed while alternate control file open Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access. Action: Retry the operation after calling cfileUseCurrent. ORA-00227: corrupt block detected in control file: (block string, # blocks string) Cause: A block header corruption or checksum error was detected on reading the control file. Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command. ORA-00228: length of alternate control file name exceeds maximum of string Cause: The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system. Action: Retry the operation with a shorter filename. ORA-00229: operation disallowed: already hold snapshot control file enqueue Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue. Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue. ORA-00230: operation disallowed: snapshot control file enqueue unavailable Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue. Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates. ORA-00231: snapshot control file has not been named Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified. Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName. ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time). ORA-00233: copy control file is corrupt or unreadable Cause: The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy. Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy. ORA-00234: error in identifying or opening snapshot or copy control file Cause: A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy. Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively. ORA-00235: control file fixed table inconsistent due to concurrent update Cause: Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information. Action: Retry the operation. ORA-00236: snapshot operation disallowed: mounted control file is a backup Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file. Action: Mount a current control file and retry the operation. ORA-00237: snapshot operation disallowed: control file newly created Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. Action: Mount a current control file and retry the operation. ORA-00238: operation would reuse a filename that is part of the database Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database. Action: Retry the operation with a different filename. ORA-00250: archiver not started Cause: An attempt was made to stop automatic archiving, but the archiver process was not running. Action: No action required. ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command. Action: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command. ORA-00252: log string of thread string is empty, cannot archive Cause: A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that instance death during a log switch left the log empty. Action: Empty logs do not need to be archived. Do not attempt to archive the redo log file. ORA-00253: character limit string exceeded by archive destination string string Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long. Action: Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message. ORA-00254: error in archive control string "string" Cause: The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter. Action: Check the archive string used to make sure it refers to a valid online device. ORA-00255: error archiving log string of thread string, sequence # string Cause: An error occurred during archiving. Action: Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo. ORA-00256: cannot translate archive destination string string Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated. Action: Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string. ORA-00257: archiver error. Connect internal only, until freed. Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file. Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving. ORA-00258: manual archiving in NOARCHIVELOG mode must identify log Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename. Action: Specify log by filename, by group number or by thread and sequence number. ORA-00259: log string of open instance string (thread string) is the current log, cannot archive Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries. Action: Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread. ORA-00260: cannot find online log sequence string for thread string Cause: The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs. Action: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number. ORA-00261: log string of thread string is being archived or modified Cause: The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log. Action: Wait for the current operation to complete and try again. ORA-00262: current log string of closed thread string cannot switch Cause: The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused. Action: Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed. ORA-00263: there are no logs that need archiving for thread string Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving. Action: No action required. ORA-00264: no recovery required Cause: An attempt was made to perform media recovery on files that do not // need any type of recovery. Action: Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames. ORA-00265: instance recovery required, cannot set ARCHIVELOG mode Cause: The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles. Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option. ORA-00266: name of archived log file needed Cause: During media recovery, the name of an archived redo log file was requested, but no name was entered. Action: Mount the correct redo log file and enter its name when it is requested. ORA-00267: name of archived log file not needed Cause: During media recovery, the name of an archived redo log file was entered, but no name was requested. Action: Continue media recovery, but do not enter a new log name. ORA-00268: specified log file does not exist "string" Cause: The given redo log file does not exist. Action: Check the spelling and capitalization of the filename and retry the command. ORA-00269: specified log file is part of thread string not string Cause: The given redo log file is not part of the given thread Action: Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error. ORA-00270: error creating archive log string Cause: An error was encountered when either creating or opening the destination file for archiving. Action: Check that the archive destination is valid and that there is sufficient space on the destination device. ORA-00271: there are no logs that need archiving Cause: An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived. Action: No action required. ORA-00272: error writing archive log string Cause: An I/O error occurred while archiving a redo log file. Action: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device. ORA-00273: media recovery of direct load data that was not logged Cause: A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt. Action: The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error. ORA-00274: illegal recovery option string Cause: An illegal option was specified for a recovery command. Action: Correct the syntax and retry the command. ORA-00275: media recovery has already been started Cause: An attempt was made to start a second media recovery operation in the same session. Action: Complete or cancel the first media recovery session or start another session to perform media recovery. ORA-00276: CHANGE keyword specified but no change number given Cause: The CHANGE keyword was specified on the command line, but no change number was given. Action: Retry the command using a valid change number after the CHANGE keyword. ORA-00277: illegal option to the UNTIL recovery flag string Cause: Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword. Action: Correct the syntax. ORA-00278: log file "string" no longer needed for this recovery Cause: The specified redo log file is no longer needed for the current recovery. Action: No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future. ORA-00279: change string generated at string needed for thread string Cause: The requested log is required to proceed with recovery. Action: Please supply the requested log with "ALTER DATABASE RECOVER LOGFILE " or cancel recovery with "ALTER DATABASE RECOVER CANCEL". ORA-00280: change string for thread string is in sequence #string Cause: This message helps to locate the redo log file with the specified change number requested by other messages. Action: Use the information provided in this message to specify the required archived redo log files for other errors. ORA-00281: media recovery may not be performed using dispatcher Cause: An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method. Action: Connect to the instance via a dedicated server process to perform media recovery. ORA-00282: UPI string call not supported, use ALTER DATABASE RECOVER Cause: The given UPI call is no longer supported. Action: Use the ALTER DATABASE RECOVER command for all recovery actions. ORA-00283: recovery session canceled due to errors Cause: An error during recovery was determined to be fatal enough to end the current recovery session. Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action. ORA-00284: recovery session still in progress Cause: An error during recovery was determined to be minor enough to allow the current recovery session to continue. Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action. ORA-00285: TIME not given as a string constant Cause: UNTIL TIME was not followed by a string constant for the time. Action: Enter the time enclosed in single quotation marks. ORA-00286: no members available, or no member contains valid data Cause: None of the members of a redo log file group are available, or the available members do not contain complete data. Action: If a member is temporarily offline, attempt to make it available. Make sure that the correct filenames are being used, especially if the redo log file is being accessed from a remote location. ORA-00287: specified change number string not found in thread string Cause: The given change number does not appear in any of the online redo logs for the given thread. Action: Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs. ORA-00288: to continue recovery type ALTER DATABASE RECOVER CONTINUE Cause: During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors. Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume. ORA-00289: suggestion : string Cause: This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived. Action: Consider using this filename for the next log needed for recovery. ORA-00290: operating system archival error occurred. See error below Cause: While attempting to archive to a redo log file, the server encountered an unexpected operating system error. Action: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation. ORA-00291: numeric value required for PARALLEL option Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism. Action: Re-enter the command with a numeric argument specifying the degree of parallelism desired. ORA-00292: parallel recovery feature not installed Cause: A parallel recovery was requested when the parallel recovery option is not installed. Action: Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file. ORA-00293: control file out of sync with redo log Cause: The redo log file and control file are out of sync because a non-current controle file was specified when the instance was started. Action: Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause. ORA-00294: invalid archivelog format specifier "string" Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T. Action: Correct the initialization file and re-start the instance. ORA-00295: datafile/tempfile number string is invalid, must be between 1 and string Cause: An invalid file number was specified. Action: Specify a valid datafile or tempfile number and retry the operation. ORA-00296: maximum number of files (string) exceeded for RECOVER DATAFILE LIST Cause: The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than recovery manager needs to recover to satisfy the user"s RECOVER command. Action: Re-start the instance with a higher value for DB_FILES. ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START Cause: The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START. Action: Contact customer support ORA-00298: Missing or invalid attribute value Cause: A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT Action: Correct the syntax and retry the command. ORA-00299: must use file-level media recovery on data file string Cause: The control file does not contain an entry for this file, so block media recovery cannot be done. Action: Restore the data file and perform file-level media recovery. ORA-00300: illegal redo log block size string specified - exceeds limit of string Cause: The specified block size of the redo log is greater than the maximum block size for the operating system. Action: Create the redo log on a device with a smaller block size ORA-00301: error in adding log file "string" - file cannot be created Cause: The creation of the redo log file failed Action: Check: 1) there is enough storage space on the device 2) the name of the file is valid 3) the device is online 4) an IO error occurred Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size. ORA-00302: limit of string logs exceeded Cause: The maximum number of redo log files has been exceeded. Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES if the compatibility is lower than 10.2.0. Otherwise, allocate more storage space for the control file. ORA-00303: cannot process Parallel Redo Cause: A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo. Action: Use a later release that supports Parallel Redo. to process this log. ORA-00304: requested INSTANCE_NUMBER is busy Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use. Action: Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number c) wait for instance recovery to complete on the instance with this number. ORA-00305: log string of thread string inconsistent; belongs to another database Cause: The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database. Action: Specify the correct redo log file, then retry the operation. ORA-00306: limit of string instances in this database Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances. Action: You cannot start more than the lower of a) port-specific limit as to the number of instances b) the number of instances specified at create-database time ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range. Action: Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation. ORA-00308: cannot open archived log "string" Cause: The system cannot access a required archived redo log file. Action: Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session. ORA-00309: log belongs to wrong database Cause: The system cannot access the archived redo log because it belongs to another database. Action: Specify the correct redo log file, then retry the operation. ORA-00310: archived log contains sequence string; sequence string required Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified Action: Specify the correct redo log file; then retry the operation. ORA-00311: cannot read header from archived log Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. ORA-00312: online log string thread string: "string" Cause: This message reports the filename for details of another message. Action: Other messages will accompany this message. See the associated messages for the appropriate action to take. ORA-00313: open failed for members of log group string of thread string Cause: The online log cannot be opened. May not be able to find file. Action: See accompanying errors and make log available. ORA-00314: log string of thread string, expected sequence# string doesn"t match string Cause: The online log is corrupted or is an old version. Action: Find and install correct version of log or reset logs. ORA-00315: log string of thread string, wrong thread # string in header Cause: The online log is corrupted or is an old version. Action: Find and install correct version of log or reset logs. ORA-00316: log string of thread string, type string in header is not log file Cause: The online log is corrupted or is an old version. Action: Find and install correct version of log or reset logs. ORA-00317: file type string in header is not log file Cause: This is not an archived log file. Action: Find the correct file and try again. ORA-00318: log string of thread string, expected file size string doesn"t match string Cause: On header read the file size indicated in the control file did not match the file size contained in the log file. Action: Restore correct file or reset logs. ORA-00319: log string of thread string has incorrect log reset status Cause: Check of log file header at database open found that an online log has log reset data that is different from the control file. The log is probably an incorrectly restored backup. Action: Restore correct file or reset logs. ORA-00320: cannot read file header from log string of thread string Cause: The file is not available. Action: Restore the log file. ORA-00321: log string of thread string, cannot update log file header Cause: Cannot write to the log file. Action: Restore the access to the file. ORA-00322: log string of thread string is not current copy Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup. Action: Restore correct file or reset logs. ORA-00323: Current log of thread string not useable and all others need archiving Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used. Action: Archive the logs for the thread then retry open. ORA-00324: log file "string" translated name "string" too long, string characters exceeds string limit Cause: the translated name for a log file is too long. Action: Choose a untranslated name that yields a shorter translated name. ORA-00325: archived log for thread string, wrong thread # string in header Cause: The archived log is corrupted or for another thread. Can not use the log for applying redo. Action: Find correct archived log. ORA-00326: log begins at change string, need earlier change string Cause: The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo. Action: Find correct archived log. ORA-00327: log string of thread string, physical size string less than needed string Cause: A log file has shrunk in size. This is likely to have been caused by operator or operating system error. Action: Restore the log file from backup. If backup is not available, drop this log and re-create. If the database was shut down cleanly, no further action should be required; otherwise incomplete recovery may be required. ORA-00328: archived log ends at change string, need later change string Cause: The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo. Action: Find correct archived log. ORA-00329: archived log begins at change string, need change string Cause: The archived log is not the correct log. An earlier log is needed. Action: Restore the correct log file. ORA-00330: archived log ends at change string, need change string Cause: The archived log is not the correct log. A later log is needed. Action: Restore the correct log file. ORA-00331: log version string incompatible with ORACLE version string Cause: The log was written by incompatible version of Oracle. Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software. ORA-00332: archived log is too small - may be incompletely archived Cause: The log is smaller than the space allocated in it. May be the result of a shutdown abort while it was being written by the archiver. Action: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived. ORA-00333: redo log read error block string count string Cause: An IO error occurred while reading the log described in the accompanying error. Action: Restore accessibility to file, or get another copy of the file. ORA-00334: archived log: "string" Cause: Reporting filename for details of another error Action: See associated error messages ORA-00335: online log string: No log with this number, log does not exist Cause: Reporting filename for details of another error Action: See associated error messages ORA-00336: log file size string blocks is less than minimum string blocks Cause: The log file size as specified in create database is too small. Action: Increase the log file size. ORA-00337: log file "string" does not exist and no size specified Cause: An attempt to add a log found neither an existing file nor a size for creating the file. Action: Specify a size for the log file. ORA-00338: log string of thread string is more recent than control file Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough. Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery. ORA-00339: archived log does not contain any redo Cause: The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log. Action: Restore the correct log file. ORA-00340: IO error processing online log string of thread string Cause: An IO error occurred on the named online log. Action: Restore accessibility to file, or restore file from backup. ORA-00341: log string of thread string, wrong log # string in header Cause: The internal information in an online log file does not match the control file. Action: Restore correct file or reset logs. ORA-00342: archived log does not have expected resetlogs SCN string Cause: Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo. Action: Supply the correct log file. ORA-00343: too many errors, log member closed Cause: The maximum number of errors on this log member has been exceeded. Action: Correct the underlying problem by referring to the other error messages found with this one. ORA-00344: unable to re-create online log "string" Cause: An I/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command. Action: Correct the file/device as indicated by accompanying errors. ORA-00345: redo log write error block string count string Cause: An IO error has occurred while writing the log Action: Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery. ORA-00346: log member marked as STALE Cause: A log file member no longer is complete. Action: Correct the underlying problem by referring to the other error messages found with this one. ORA-00347: log string of thread string, expected block size string doesn"t match string Cause: On header read the blocksize indicated in the control file did not match the blocksize contained in the log file. Action: Restore correct file or reset logs. ORA-00348: single-process redo failure. Must abort instance Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation. Action: Shutdown abort and warmstart the database. ORA-00349: failure obtaining block size for "string" Cause: The operating system was unable to determine the blocksize for the given filename. Action: Consult the accompanying error message, and correct the device or specify another filename. ORA-00350: log string of instance string (thread string) needs to be archived Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled. Action: Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files. ORA-00351: recover-to time invalid Cause: The time specified in a recover-until statement must be after January 1st 1988. Action: Specify a time after January 1st 1988. ORA-00352: all logs for thread string need to be archived - cannot enable Cause: Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread. Action: Archive a log for the thread or disable media recovery. ORA-00353: log corruption near block string change string time string Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption. Action: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time. ORA-00354: corrupt redo log block header Cause: The block header on the redo block indicated by the accompanying error, is not reasonable. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. ORA-00355: change numbers out of order Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. ORA-00356: inconsistent lengths in change description Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. ORA-00357: too many members specified for log file, the maximum is string Cause: An add logfile or add logfile member command would result in a log with too many members. The number of members is set when the database is created. Action: Use fewer log file members. ORA-00358: Too many file members specified, the maximum is string Cause: A create or alter statement specified too many members in a parenthesised file list. Action: Specify a number of file members that is within the port-defined limit. ORA-00359: logfile group string does not exist Cause: An add logfile member or drop logfile request specified a logfile group number that does not exist. Action: Check the configuration of the log files and reissue the command. ORA-00360: not a logfile member: string Cause: A filename was given to drop logfile member that is not a part of the database, or which is a data file. Action: Supply a valid logfile member name. ORA-00361: cannot remove last log member string for group string Cause: An attempt has been made to remove the last member of a log file group. Action: If desired, delete the entire log, by using DROP LOGFILE. ORA-00362: member is required to form a valid logfile in group string Cause: A request to drop a logfile member was denied because it would remove data required to form a complete logfile. Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE; ORA-00363: log is not the archived version Cause: d by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command. Action: Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included. ORA-00364: cannot write header to new log member Cause: An i/o error occurred when attempting to write the header to a log member that is being added to an existing group. Action: See accompanying errors. Fix problem or use another file. ORA-00365: the specified log is not the correct next log Cause: The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database. Action: Find the log that was generated by this copy of the database and give that filename to recovery. ORA-00366: log string of thread string, checksum error in the file header Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted Action: Find and install correct version of log or reset logs. ORA-00367: checksum error in log file header Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted Action: Find the correct file and try again. ORA-00368: checksum error in redo log block Cause: The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents. Action: Restore correct file or reset logs. ORA-00369: Current log of thread string not useable and other log being cleared Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used. Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise reissue the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs. ORA-00370: potential deadlock during kcbchange operation Cause: Error code used internally by software. Should never be reported Action: Treat as internal error. See error 600. ORA-00371: not enough shared pool memory, should be atleast string bytes Cause: Init.ora parameter shared_pool_size is too small Action: Increase the parameter value ORA-00372: file string cannot be modified at this time Cause: attempting to modify the contents of a file that cannot be modified. The file is most likely part of a read only tablespace but may be in the process of going offline, or the database may be in the process of closing. Action: check the status of the file and its tablespace ORA-00373: online log version string incompatible with ORACLE version string Cause: The online log was written by incompatible version of Oracle. Can occur when the log file was created by either a new or older version of Oracle. Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software. ORA-00374: parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string] Cause: invalid value for db_block_size parameter Action: adjust parameter and restart ORA-00375: unable to get default db_block_size Cause: the system was unable to determine the default db_block_size Action: see accompanying system specific error. As a workaround, specify the blocksize in the INIT.ORA file. ORA-00376: file string cannot be read at this time Cause: attempting to read from a file that is not readable. Most likely the file is offline. Action: Check the state of the file. Bring it online ORA-00377: Frequent backups of file string causing write operation to stall Cause: Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete. Action: Increase the interval between begin hot-backup commands for this file. ORA-00378: buffer pools cannot be created as specified Cause: Either the number of buffers or the number of lru latches is too small to satisfy the specified buffer pool configuration. Action: Either increase the number of buffers and/or number of lru latches or configure smaller buffer pools. ORA-00379: no free buffers available in buffer pool string for block size stringK Cause: All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available. Action: Increase the number of buffers in the specified pool for the specified block size ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard block size Cause: User specified the parameter db_nk_cache_size (where n is one of 2,4,8,16,32), while the standard block size for this database is equal to n Kbytes. This is illegal. Action: Specify the standard block size cache using db_cache_size (DEFAULT pool) (and db_recycle_cache_size, db_keep_cache_size if additional buffer pools are required). Do NOT use the corresponding db_nk_cache_size parameter for the standard block size. ORA-00381: cannot use both new and old parameters for buffer cache size specification Cause: User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32), db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_recycle }. This is illegal. Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don"t specify both. If old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes. Cache advisory can only be enabled with the new cache parameters. ORA-00382: %s not a valid block size, valid range [string..string] Cause: User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16, 32}, but nk is not a valid block size for this platform. Action: Remove corresponding parameter from the "init.ora" file and restart the instance. ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce db_K_cache_size to zero while there were still online tablespaces with blocksize K. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set db_cache_size to zero. Action: Offline any tablespaces with the corresponding blocksize and then perform the operation again. ORA-00384: Insufficient memory to grow cache Cause: The system could not allocate sufficient memory to grow the cache to the specified size. Action: Attempt a smaller increase in the value of the parameter. ORA-00385: cannot enable Very Large Memory with new buffer cache parameters Cause: User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32) } AND use_indirect_data_buffers is set to TRUE. This is illegal. Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2) parameters. ORA-00386: use_indirect_data_buffers not supported Cause: The system could not allocate sufficient memory to grow the cache to the specified size. Action: Attempt a smaller increase in the value of the parameter. ORA-00390: log string of thread string is being cleared, cannot become current log Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log. ORA-00391: All threads must switch to new log format at the same time Cause: An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time. Action: Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database. ORA-00392: log string of thread string is being cleared, operation not allowed Cause: An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing. Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log. ORA-00393: log string of thread string is needed for recovery of offline datafiles Cause: Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared the tablespaces containing the files will have to be dropped. Action: Archive the log then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command. ORA-00394: online log reused while attempting to archive it Cause: It has been detected that an online log that is being archived has been reused Action: Cannot archive the logfile anymore since it has been overwritten ORA-00395: online logs for the clone database must be renamed Cause: A clone database open forces logfile renaming to avoid overwriting the primary logfiles Action: Rename the logfiles manually or using the log_file_name_convert initialization parameter ORA-00396: error string required fallback to single-pass recovery Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error. Action: Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process. ORA-00397: instance recovery process terminated with error Cause: The foreground process doing instance recovery died. Action: Check the foreground trace file for the cause of recovery failure. ORA-00398: abort thread recovery due to reconfiguration Cause: Global enqueue service reconfiguration occurred during instance/crash recovery. Action: This is used internally, no action is required. ORA-00399: corrupt change description in redo log Cause: A change vector in the redo log failed validation checks. Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. ORA-00400: invalid release value string for parameter string Cause: The release level given for the specified init parameter is invalid. Action: Correct the parameter value in the parameter file and retry. ORA-00401: the value for parameter string is not supported by this release Cause: The value specified cannot be supported by this release of the software. Action: Choose an appropriate value, or remove the parameter value to use the default value. ORA-00402: database changes by release string cannot be used by release string Cause: Changes have been made to the database that require a newer software release or that violate the compatibility parameters. Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the init file. ORA-00403: %s (string) is not the same as other instances (string) Cause: Another instance has set the compatible or compatible no recovery parameters differently than this instance. Action: Change the parameters of the current instance to match other instances already running. ORA-00404: Convert file not found: "string" Cause: The file used for converting the database from V7 to V8 could not be found. Action: Verify that the migration process has been started on this database and that the convert filename is accessable. ORA-00405: compatibility type "string" Cause: Reporting a type associated with another error. Action: See accompanying error ORA-00406: COMPATIBLE parameter needs to be string or greater Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter. Action: Shutdown and startup with a higher compatibility setting. ORA-00407: rolling upgrade from release string.string to string.string is not allowed Cause: Another instance executing software at a different point release already has the database mounted. Action: Shutdown all instances then startup with the new software. ORA-00408: parameter string is set to TRUE Cause: Reporting the parameter that resulted in the compatibility error. Action: Shutdown and startup with a higher compatibility setting. ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT Cause: This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value. Action: Shutdown and startup with the specified compatibility setting. ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance Cause: ORACLE feature is not licensed. Action: Contact ORACLE for assistance. ORA-00438: %s Option not installed Cause: The specified option is not installed. Action: Purchase and install the option. ORA-00439: feature not enabled: string Cause: The specified feature is not enabled. Action: Do not attempt to use this feature. ORA-00443: background process "string" did not start Cause: The specified process did not start. Action: Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory. ORA-00444: background process "string" failed while starting Cause: Usually due to a bad (or non-existent) background process image. Action: Get a good background process image. ORA-00445: background process "string" did not start after string seconds Cause: The specified process did not start after the specified time. Action: Ensure that the background did not die and leave a trace file. ORA-00446: background process started when not expected Cause: The background process specified started up AFTER the RDBMS was already running. Action: If nobody at your site started the process, then this is an internal error. ORA-00447: fatal error in background process Cause: One of the background processes died unexpectedly. Action: Warm start the system. ORA-00448: normal completion of background process Cause: One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit. Action: Warm start the system. ORA-00449: background process "string" unexpectedly terminated with error string Cause: A foreground process needing service from a background process has discovered the process died. Action: Consult the error code, and the trace file for the process. ORA-00450: background process "string" did not start Cause: The specified process did not start. Action: Consult the error code, and the trace file for the process. ORA-00451: foreground process died unexpectedly Cause: The foreground process for the new connection did not start. Action: Reconnect to Oracle. ORA-00452: foreground process unexpectedly terminated with error string Cause: The foreground process for the new connection did not start. Action: Reconnect to Oracle. ORA-00453: backgroud process "string" is dead Cause: The background process that was being messaged was dead or its incarnation was invalid. Action: Restart the background process. ORA-00469: CKPT process terminated with error Cause: The checkpoint process died Action: Warm start instance ORA-00470: LGWR process terminated with error Cause: The log writer process died Action: Warm start instance ORA-00471: DBWR process terminated with error Cause: The database writer process died Action: Warm start instance ORA-00472: PMON process terminated with error Cause: The process cleanup process died Action: Warm start instance ORA-00473: ARCH process terminated with error Cause: The archive process died Action: Warm start instance ORA-00474: SMON process terminated with error Cause: The system cleanup process died Action: Warm start instance ORA-00475: TRWR process terminated with error Cause: The system tracing process died Action: Warm start instance ORA-00476: RECO process terminated with error Cause: The distributed transaction (two-phase commit) recovery process died. Action: Warm start instance ORA-00477: SNP* process terminated with error Cause: A materialized view refresh process died Action: PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle support. ORA-00478: SMON process terminated due to error string Cause: SMON was unable to service the requests due to error in cleanup of resources Action: Warm start instance ORA-00479: RVWR process terminated with error string Cause: The RVWR process died Action: Warm start instance ORA-00480: LCK* process terminated with error Cause: A system lock process died Action: Warm start instance ORA-00481: LMON process terminated with error Cause: The global enqueue service monitor process died Action: Warm start instance ORA-00482: LMD* process terminated with error Cause: A global enqueue service daemon process died Action: Warm start instance ORA-00483: During shutdown a process abnormally terminated Cause: One of the background processes did not exit normally at or near the time of shutdown. Action: Use shutdown abort. ORA-00484: LMS* process terminated with error Cause: A global cache service process died Action: Warm start instance ORA-00485: DIAG process terminated with error string Cause: A global diagnostic process died Action: Wait for process to restart ORA-00486: ASMB process terminated with error Cause: An ASM background process died. Action: Warm start instance. Also check that ASM Instance is running. ORA-00487: CTWR process terminated with error Cause: The change tracking process died Action: Warm start instance ORA-00488: RBAL process terminated with error Cause: The ASM rebalance coordinator process died. Action: Warm start instance. ORA-00489: ARB* process terminated with error Cause: An ASM rebalance worker process died. Action: Wait for process to restart. ORA-00490: PSP process terminated with error Cause: The process spawner died Action: Warm start instance ORA-00566: cannot request processor group - NUMA not enabled Cause: Cannot start process in a requested processor group when the NUMA feature is disabled. Action: Start the process without requesting a NUMA processor group. ORA-00567: Requested processor group string is too large (maximum string) Cause: The process could not be started in the requested processor group. Action: Start the process in another processor group. ORA-00568: Maximum number of interrupt handlers exceeded Cause: User specified too many ^c handlers Action: Remove some old handlers. ORA-00569: Failed to acquire global enqueue. Cause: A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention. Action: Check for and resolve prior errors on all instances in the cluster. If there is shared pool resource contention, increase the SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization parameters. ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: This is the generic internal error number for Oracle program exceptions. This indicates that a process has encountered an exceptional condition. Action: Report as a bug - the first argument is the internal error number ORA-00601: cleanup lock conflict Cause: PMON process runs into lock conflict trying to recovery processes Action: This is trapped internally, no action necessary ORA-00602: internal programming exception Cause: Internal programming exception Action: Report as bug ORA-00603: ORACLE server session terminated by fatal error Cause: An ORACLE server session is in an unrecoverable state. Action: Login to ORACLE again so a new server session will be created ORA-00604: error occurred at recursive SQL level string Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables). Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support. ORA-00606: Internal error code Cause: A call to deferred upi functions was made in non deferred mode Action: Report as a bug. ORA-00607: Internal error occurred while making a change to a data block Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block. Action: call Oracle Support ORA-00608: testing error [string] [string] [string] [string] [string] Cause: Internal error reserved for testing. Action: call Oracle Support ORA-00609: could not attach to incoming connection Cause: Oracle process could not answer incoming connection Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support. ORA-00610: Internal error code Cause: Oracle process started too late Action: This error should never be seen by the customer. Contact Oraclce Support ORA-00701: object necessary for warmstarting database cannot be altered Cause: Attempt to alter or drop a database object (table, cluster, or index) which are needed for warmstarting the database. Action: None. ORA-00702: bootstrap verison "string" inconsistent with version "string" Cause: The reading version of the boostrap is incompatible with the current bootstrap version. Action: Restore a version of the software that is compatible with this bootstrap version. ORA-00703: maximum number of row cache instance locks exceeded Cause: There are not enough row cache enqueues. Action: Increase the row cache enqueue parameter and warm start the system. ORA-00704: bootstrap process failure Cause: Failure in processing bootstrap data - see accompanying error. Action: Contact your customer support representative. ORA-00705: inconsistent state during start up; shut down the instance, then restart it Cause: A previous attempt to start an instance was terminated. Action: Shut down the instance completely, then restart it. ORA-00706: error changing format of file "string" Cause: An attempt to change the block0 format of the specified file failed because the file is read-only or offline. Action: Make the file read-write or bring the file online and set the BLK0_FMTCHG event. ORA-00710: new tablespace name is the same as the old tablespace name Cause: An attempt to rename a tablespace failed because the new name is the same as the old name. Action: No action required. ORA-00711: new tablespace name is invalid Cause: An attempt to rename a tablespace failed because the new name is invalid. Action: Choose a valid new name and retry the command. ORA-00712: cannot rename system tablespace Cause: An attempt to rename the system tablespace failed. Action: No action required. ORA-00720: ALTER DATABASE RESET COMPATIBILITY command has been de-supported Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i. Action: No action required. ORA-00721: changes by release string cannot be used by release string Cause: An attempt to import a tablespace failed because the tablespace contains changes that require a newer software release or that violate the compatibility parameters. Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file. ORA-00722: Feature "string" Cause: Reporting name of the feature for details of another error. Action: See associated error message. ORA-00723: Initialization parameter COMPATIBLE must be explicitly set Cause: Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user. Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used. ORA-00724: ALTER DATABASE CONVERT command has been de-supported Cause: ALTER DATABASE CONVERT command has been de-supported since Oracle 10i. Action: No action required. ORA-00740: datafile size of (string) blocks exceeds maximum file size Cause: The user specified datafile size exceeded maximum file size. Action: Please check REFERENCE for maximum size. Reduce the size and retry. ORA-00741: logfile size of (string) blocks exceeds maximum logfile size Cause: The user specified logfile size exceeded maximum logfile size. Action: Please check REFERENCE for maximum size. Reduce the size and retry. ORA-00750: database has been previously mounted and dismounted Cause: The instance has already mounted and dismounted the database, which is only allowed once in its lifetime. Action: Shut down the database. ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM Cause: The specified value of sga_max_size is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc. Action: Set sga_max_size to the recommended value or reduce the values of any SGA component size parameters you have specified. ORA-00821: Specified value of sga_target stringM is too small, needs to be at least stringM Cause: The specified value of sga_target is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc. Action: Set sga_target to the recommended value or reduce the values of any SGA component size parameters you have specified. ORA-00822: MMAN process terminated with error Cause: The Memory Management process died. Action: Warm start instance ORA-00823: Specified value of sga_target greater than sga_max_size Cause: The specified value of sga_target is greater than sga_max_size. Action: Increase sga_max_size to match up with sga_target or decrease sga_target to match up with sga_maxsize. ORA-00824: cannot set sga_target due to existing internal settings, see alert log for more information Cause: Unable to set sga_target due to current parameter settings. Action: See alert log for more information. ORA-00825: cannot set db_block_buffers if sga_target set Cause: sga_target set with db_block_buffers set. Action: Do not set sga_target or use new cache parameters and do not use db_block_buffers which is a old cache parameter. ORA-00826: cannot set sga_target for an ASM instance Cause: sga_target set for an ASM instance. Action: Do not set sga_target. ORA-00827: could not shrink sga_target to specified value Cause: Attempted to shrink the SGA to the specified value but did not succeed because the SGA components could not be shrunk as they were already at their minimum sizes. Action: Do not set sga_target to a value below the current value without first shrinking the individual SGA components. ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings Cause: Unable to set shared_pool_reserved_size to specified value if sga_target set, either because the specified value is too small, or because it is too large for the current internal size of shared pool. More details can be found in the alert log. Action: If possible, do not set shared_pool_reserved_size without setting shared_pool_size if sga_target set. Examine the alert log for information about current internal size of shared pool, and valid range of values for shared_pool_reserved_size. ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA enabled which cannot be done because auto-tune SGA cannot work with statistics_level set to BASIC. Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again. ORA-00832: no streams pool created and cannot automatically create one Cause: A database feature which needs STREAMS SGA was being used, however, the streams_pool_size parameter was not defined and the value of db_cache_size was too small to permit an automatic transfer of SGA to the streams pool from the buffer cache. Action: Please set the parameter streams_pool_size or set sga_target. ORA-00910 to ORA-01497ORA-00910: specified length too long for its datatype Cause: for datatypes CHAR and RAW, the length specified was > 2000; otherwise, the length specified was > 4000. Action: use a shorter length or switch to a datatype permitting a longer length such as a VARCHAR2, LONG CHAR, or LONG RAW ORA-00911: invalid character Cause: identifiers may not start with any ASCII character other than letters and numbers. $#_ are also allowed after the first character. Identifiers enclosed by doublequotes may contain any character other than a doublequote. Alternative quotes (q"#...#") cannot use spaces, tabs, or carriage returns as delimiters. For all other contexts, consult the SQL Language Reference Manual. Action: none ORA-00912: input parameter too long Cause: one of your input strings was too long Action: shorten the input parameter length ORA-00953: missing or invalid index name Cause: An index name of the form [ . ] is expected but not present. If OIDINDEX clause, index name must be Action: Enter an appropriate index name. ORA-00956: missing or invalid auditing option Cause: AUDIT or NOAUDIT statement contains an invalid auditing option. Action: Use a valid option. ORA-00960: ambiguous column naming in select list Cause: A column name in the order-by list matches more than one select list columns. Action: Remove duplicate column naming in select list. ORA-00962: too many group-by / order-by expressions Cause: The group-by or order-by column list contain more than 1000 expressions. Action: Use 1000 or less expressions in the group-by or order-by list. ORA-00964: table name not in FROM list Cause: The table name referred in the select list is not specified in the from list. Action: Make sure the name is correctly specified and matches one of the names in the from list. ORA-00965: column aliases not allowed for "*" Cause: The statement is trying to alias the * expression in the select list which is not legal. Action: Remove the alias. ORA-00972: identifier is too long Cause: An identifier with more than 30 characters was specified. Action: Specify at most 30 characters. ORA-00976: LEVEL, PRIOR, or ROWNUM not allowed here Cause: LEVEL, PRIOR, or ROWNUM is being specified at illegal location. Action: Remove LEVEL, PRIOR, or ROWNUM. ORA-00977: duplicate auditing option Cause: AUDIT or NOAUDIT statement specifies an option more than once Action: Either use ALL with no other auditing options or make sure no option is listed more than once. ORA-00981: cannot mix table and system auditing options Cause: Table and system-wide auditing options were specified in the same AUDIT or NOAUDIT statement. Action: You must issue table and system options in separate statements. ORA-00983: cannot audit or noaudit SYS user actions Cause: An attempt was made to AUDIT or NOAUDIT SYS user actions. Action: Execute the statement again with a valid user. ORA-00991: only MAC privileges may be granted to procedures Cause: Object privileges or non-MAC system privileges were granted to the procedure. Action: Only grant MAC privileges using the PROCEDURE clause. ORA-01002: fetch out of sequence Cause: This error means that a fetch has been attempted from a cursor which is no longer valid. Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including: 1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned. 2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error. 3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement. Action: 1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch. 2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE. 3) Reexecute the statement after rebinding, then attempt to fetch again. ORA-01010: invalid OCI operation Cause: One of the following: 1) You attempted an invalid OCI operation. 2) You are using an Oracle client application linked with version 7.1 (or higher) libraries, the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a version 7.0 (or lower) Oracle Server. 3) You are connected to a version 7.1 (or higher) Oracle Server, the initialization parameter DBLINK_ENCRYPT_LOGIN is set to TRUE, and you attempted to use a database link pointing to a version 7.0 (or lower) Oracle Server. 4) You are connected to a version 9.0.2(or higher) Oracle Server and you attempted to use a database link pointing to a version 9.0.1(or lower) Oracle Server for distributed autonomous transaction. Action: For the above causes: 1) Do not use the invalid OCI operation. 2) If you do not wish to use encrypted connect passwords in your distributed database, set ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords, you must upgrade all Oracle Servers to version 7.1 (or higher). 3) If you do not wish to use encrypted database links in your distributed database, set DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, you must upgrade all Oracle Servers to version 7.1 (or higher). 4) Do not attempt distributed autonomous transaction on version 9.0.1(or lower) Oracle Server. ORA-01016: This function can be called only after a fetch Cause: Cursor in an invalid state. Action: Make sure that the oci/upi function is called after fetch. ORA-01019: unable to allocate memory in the user side Cause: The user side memory allocator returned error. Action: Increase the processes heap size or switch to the old set of calls. ORA-01022: database operation not supported in this configuration Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating ORACLE servers. Action: You may need to upgrade one or more of your ORACLE servers or re-link your user side application with new libraries. Report the problem to Worldwide Customer Support. ORA-01023: Cursor context not found (Invalid cursor number) Cause: The cursor number is not a valid open cursor. Action: Make sure that the cursor is open. ORA-01025: UPI parameter out of range Cause: An integer parameter to a upi function is out of range. Action: This usually indicates an error in a tool built on top of the oracle dbms. Report the error to your customer support representative. ORA-01026: multiple buffers of size > 4000 in the bind list Cause: More than one long buffer in the bind list. Action: Change the buffer size to be less than 4000 for the bind variable bound to a normal column. ORA-01027: bind variables not allowed for data definition operations Cause: An attempt was made to use a bind variable in a SQL data definition operation. Action: Such bind variables are not allowed. ORA-01028: internal two task error Cause: Received send long message but don"t have the cursor context. Action: Report as a bug. ORA-01029: internal two task error Cause: Received a request to send the long again when there is no long Action: Report as a bug ORA-01030: SELECT ... INTO variable does not exist Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement. Action: If it is not possible to correct the statement, call customer support. ORA-01031: insufficient privileges Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges. When Trusted Oracle is configure in DBMS MAC, this error may occur if the user was granted the necessary privilege at a higher label than the current login. Action: Ask the database administrator to perform the operation or grant the required privileges. For Trusted Oracle users getting this error although granted the the appropriate privilege at a higher label, ask the database administrator to regrant the privilege at the appropriate label. ORA-01032: no such userid Cause: This is an internal error message related to Export/Import. Action: Contact customer support. ORA-01033: ORACLE initialization or shutdown in progress Cause: An attempt was made to log on while Oracle is being started up or shutdown. Action: Wait a few minutes. Then retry the operation. ORA-01034: ORACLE not available Cause: Oracle was not started up. Possible causes include the following: - The SGA requires more space than was allocated for it. - The operating-system variable pointing to the instance is improperly defined. Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform specific Oracle documentation. ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on. Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege. ORA-01036: illegal variable name/number Cause: Unable to find bind context on user side Action: Make sure that the variable being bound is in the sql statement. ORA-01037: maximum cursor memory exceeded Cause: Attempting to process a complex sql statement which consumed all available memory of the cursor. Action: Simplify the complex sql statement. ORA-01038: cannot write database file version string with ORACLE version string Cause: Attempting to write datafile headers in an old format. The new format can not be used until after the database has been verified as being compatible with this software version. Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation. ORA-01039: insufficient privileges on underlying objects of the view Cause: Attempting to explain plan on other people"s view without the necessary privileges on the underlying objects of the view. Action: Get necessary privileges or do not perform the offending operation. ORA-01040: invalid character in password; logon denied Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range. Action: Resubmit password with valid characters. ORA-01041: internal error. hostdef extension doesn"t exist Cause: Pointer to hstdef extension in hstdef is null. Action: Report as a bug ORA-01042: detaching a session with open cursors not allowed Cause: An attempt was made to detach a seesio n which had open cursors. Action: Close all the cursors before detaching the session. ORA-01043: user side memory corruption [string], [string], [string], [string] Cause: The application code corrupted some of the usr memory used by oracle Action: Make sure that the application code is not overwriting memory. ORA-01044: size string of buffer bound to variable exceeds maximum string Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as: (element_size)*(number of elements) Action: Reduce buffer size. ORA-01045: user string lacks CREATE SESSION privilege; logon denied Cause: A connect was attempted to a userid which does not have create session privilege. Action: Grant the user CREATE SESSION privilege. ORA-01048: Couldn"t find the specified procedure in the given context Cause: The procedure user specified in deferred RPC doesn"t exist. Action: Check to make sure that the procedure exists and is visible to the replication process. ORA-01049: Bind by name is not spupportted in streamed RPC Cause: A newer version of server is talking with this version requesting an operation not supported in this version. Action: none ORA-01051: deferred rpc buffer format invalid Cause: The deferred rpc data in sys.def$_call is corrupted. Action: Contact your customer support representive. ORA-01052: required destination LOG_ARCHIVE_DUPLEX_DEST is not specified Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to two. Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to one. ORA-01058: internal New Upi interface error Cause: Attempt to delete non existant hstdef extension. Action: Report as a bug. ORA-01059: parse expected before a bind or execute Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed. Action: Ensure the statement is parsed before a bind or execute. ORA-01060: array binds or executes not allowed Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor. Action: Bind a single cursor or execute the PL/SQL block once. ORA-01061: cannot start up a V8 server using a V7 client application Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server. Action: Use a client application linked with V8 (or higher) libraries.60 ORA-01062: unable to allocate memory for define buffer Cause: Exceeded the maximum buffer size for current plaform Action: Use piecewise fetch with a smaller buffer size ORA-01070: Using an old version of Oracle for the server Cause: Using pre 7.0.10.1 version of oracle for server Action: Upgrade server to post 7.0.10.1 version ORA-01071: cannot perform operation without starting up ORACLE Cause: Obvious Action: none ORA-01072: cannot stop ORACLE; ORACLE not running Cause: Obvious Action: none ORA-01073: fatal connection error: unrecognized call type Cause: An illegal internal operation was attempted. Action: Contact your customer support representative. ORA-01074: cannot shut down ORACLE; inside a login session - log off first Cause: Obvious Action: none ORA-01075: you are currently logged on Cause: Attempt to login while logged in. Action: none ORA-01076: multiple logons per process not yet supported Cause: Obvious Action: none ORA-01077: background process initialization failure Cause: Failure during initialization of ORACLE background processes. Action: Further diagnostic information should be in the error stack or in the trace file. ORA-01078: failure in processing system parameters Cause: Failure during processing of INIT.ORA parameters during system startup. Action: Further diagnostic information should be in the error stack. ORA-01079: ORACLE database was not properly created, operation aborted Cause: There was an error when the database or control file was created. Action: s to recreate the database or a new control file. ORA-01080: error in shutting down ORACLE Cause: Failure during system shutdown. Action: Further diagnostic information should be in the error stack. ORA-01081: cannot start already-running ORACLE - shut it down first Cause: Obvious Action: none ORA-01082: "row_locking = always" requires the transaction processing option Cause: "row_locking = always" is specified in INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option. Action: Remove it from INIT.ORA file or set it to "default" or "intent". ORA-01083: value of parameter "string" is inconsistent with that of other instances Cause: The value of the given parameter is required to be the same for all instances in the cluster database configuration. ROW_LOCKING and SERIALIZABLE are 2 examples. Action: Change the value of the parameter in INIT.ORA file to match that of other cluster database instances. ORA-01084: invalid argument in OCI call Cause: The failing OCI call contains an argument with an invalid value. Action: Use valid argument values. For more information, see the Programmer"s Guide to the Oracle Call Interfaces and the appropriate programming language supplement. ORA-01085: preceding errors in deferred rpc to "string.string.string" Cause: Errors were encountered when the named procedure was executed as a deferred remoted procedure call. Action: Correct the cause of the preceding errors. ORA-01086: savepoint "string" never established Cause: Trying to roll back to a save point that was never established. Action: none ORA-01088: cannot shut down ORACLE while active processes exist Cause: Users are still logged into the instance. Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE. ORA-01089: immediate shutdown in progress - no operations are permitted Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running ORACLE instance, so your operations have been terminated. Action: Wait for the instance to be restarted, or contact your DBA. ORA-01090: shutdown in progress - connection is not permitted Cause: The SHUTDOWN command was used to shut down a running ORACLE instance, so you cannot connect to ORACLE. Action: Wait for the instance to be restarted, or contact your DBA. ORA-01091: failure during startup force Cause: Unable to destroy the old SGA. Action: Manually remove the old SGA and reissue the STARTUP command ORA-01092: ORACLE instance terminated. Disconnection forced Cause: The instance this process was connected to was terminated abnormally, probably via a shutdown abort. This process was forced to disconnect from the instance. Action: Examine the alert log for more details. When the instance has been restarted, retry action. ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected Cause: There is at least one more session other than the current one logged into the instance. ALTER DATABASE CLOSE is not permitted. Action: Find the other sessions and log them out and resubmit the command ORA-01095: DML statement processed zero rows Cause: During a call to OTEX, an update, delete, or insert statement being executed processed zero rows. The execution of statements by OTEX was halted at this point. Action: none ORA-01096: program version (string) incompatible with instance (string) Cause: A program is trying to connect to an instance using a different version of code than the database was started with. This is not allowed. Action: Either relink the program with the same version as the database or restart the database using the old version of code. ORA-01097: cannot shutdown while in a transaction - commit or rollback first Cause: Obvious Action: none ORA-01099: cannot mount database in SHARED mode if started in single process mode Cause: Obvious Action: none ORA-01100: database already mounted Cause: A database is already mounted in this instance. Action: none ORA-01101: database being created currently mounted by some other instance Cause: Some other instance has the database of same name currently mounted and you are trying to create it. Action: Either change the database name or shutdown the other instance. ORA-01102: cannot mount database in EXCLUSIVE mode Cause: Some other instance has the database mounted exclusive or shared. Action: Shutdown other instance or mount in a compatible mode. ORA-01103: database name "string" in control file is not "string" Cause: The database name in the control file does not match your database name. Action: Either find the correct control file or change your database name. ORA-01104: number of control files (string) does not equal string Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance. Action: Check to make sure that all control files are listed. ORA-01105: mount is incompatible with mounts by other instances Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why. Action: See accompanying errors. ORA-01106: database must be closed before dismounting Cause: Obvious Action: none ORA-01107: database must be mounted for media recovery Cause: An attempt to perform media recovery was made but the database is not mounted. Action: Mount the database. ORA-01108: file string is in backup or media recovery Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery. Action: Complete or cancel the media recovery session or backup. ORA-01109: database not open Cause: A command was attempted that requires the database to be open. Action: Open the database and try the command again ORA-01110: data file string: "string" Cause: Reporting file name for details of another error Action: See associated error message ORA-01111: name for data file string is unknown - rename to correct file Cause: The data file was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created. Action: Rename the MISSING file to the name of the real file. ORA-01112: media recovery not started Cause: An attempt to continue media recovery is being made but media recovery was not started. Action: None. ORA-01113: file string needs media recovery Cause: An attempt was made to online or open a database with a file that is in need of media recovery. Action: First apply media recovery to the file. ORA-01114: IO error writing block to file string (block # string) Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time. Action: Restore access to the device or remove unnecessary files to free up space. ORA-01115: IO error reading block from file string (block # string) Cause: Device on which the file resides is probably offline Action: Restore access to the device ORA-01116: error in opening database file string Cause: Usually the file is not accessible. Action: Restore the database file. ORA-01117: adding file "string" with illegal block size: string; limit is string Cause: An attempt was made to add a database file with a block size that is greater than the maximum block size allowed. Action: Retry the DDL command with a smaller block size. ORA-01118: cannot add any more database files: limit of string exceeded Cause: There is no more room in the control file for adding database files. Action: Resize the control file or drop other tablespaces. ORA-01119: error in creating database file "string" Cause: Usually due to not having enough space on the device. Action: none ORA-01120: cannot remove online database file string Cause: Attempting to drop a datafile when it is online Action: Take file offline before dropping. ORA-01121: cannot rename database file string - file is in use or recovery Cause: Attempted to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered. Action: Close database in all instances and end all recovery sessions. ORA-01122: database file string failed verification check Cause: The information in this file is inconsistent with information from the control file. See accompanying message for reason. Action: Make certain that the db files and control files are the correct files for this database. ORA-01123: cannot start online backup; media recovery not enabled Cause: An attempt to start backup of an on-line tablespace failed because media recovery is not enabled. Action: Enable media recovery and retry this operation. ORA-01124: cannot recover data file string - file is in use or recovery Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is curently doing media recovery on the file. Action: Do not do media recovery. ORA-01125: cannot disable media recovery - file string has online backup set Cause: An attempt to disable media recovery found that an online backup is still in progress. Action: End the backup of the offending tablespace and retry this command. ORA-01126: database must be mounted in this instance and not open in any instance Cause: Obvious Action: none ORA-01127: database name "string" exceeds size limit of string characters Cause: Obvious Action: none ORA-01128: cannot start online backup - file string is offline Cause: An attempt to start an online backup found that one of the files is offline. Action: Bring the offending files online and retry this command or do a cold backup. ORA-01129: user"s default or temporary tablespace does not exist Cause: The user"s default or temporary tablespace was dropped. Action: Reassign the default or temporary tablespace. ORA-01135: file string accessed for DML/query is offline Cause: Attempted to access a data file that is offline Action: Bring the data file back online ORA-01136: specified size of file string (string blocks) is less than original size of string blocks Cause: A file size was specified in the AS clause of ALTER DATABASE CREATE DATAFILE, and the size was smaller the the size needed Action: Create the file with a larger size. ORA-01137: data file string is still in the middle of going offline Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline. Action: Wait a bit and try to online the file again. ORA-01138: database must either be open in this instance or not at all Cause: The requested operation can not be done when the database is mounted but not open in this instance, and another instance has the database open. Action: Execute the operation in an open instance, open the datbase in this instance, or close the database in the other instances. ORA-01139: RESETLOGS option only valid after an incomplete database recovery Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session. Action: Retry the ALTER DATABASE OPEN without specifying RESETLOGS ORA-01140: cannot end online backup - all files are offline or readonly Cause: All the files were found to be offline or readonly when attempting to end an online backup. Action: None. Online backup does not need to be ended for this tablespace. ORA-01141: error renaming data file string - new file "string" not found Cause: An attempt to change a data file"s name in the control file failed because no file was found with the new name. Action: Make sure that the data file has been properly renamed by the operating system and retry. ORA-01142: cannot end online backup - none of the files are in backup Cause: None of the files were found to be in online backup when attempting to end an online backup. Action: None. Online backup does not need to be ended for this tablespace. ORA-01143: cannot disable media recovery - file string needs media recovery Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled. Action: Recover the offending file or drop the tablespace it belongs to and retry this command. ORA-01144: File size (string blocks) exceeds maximum of string blocks Cause: Specified file size is larger than maximum allowable size value. Action: Specify a smaller size. ORA-01145: offline immediate disallowed unless media recovery enabled Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVELOG mode. Action: Take tablespace offline normally or shutdown abort. Reconsider your backup strategy. You could do this if you were archiving your logs. ORA-01146: cannot start online backup - file string is already in backup Cause: When starting an online backup it was noticed that an online backup was already started for one of the data files. Action: End the first backup before beginning another. ORA-01147: SYSTEM tablespace file string is offline Cause: A file belonging to the SYSTEM tablespace has been marked offline by the DBA. The database cannot be started until all SYSTEM tablespace files are online and openable. Action: Bring the file online. ORA-01148: cannot refresh file size for datafile string Cause: An operating system or device error occurred when retrieving the file"s size. The device on which the file resides may have been offline. Action: Restore access to the device. ORA-01149: cannot shutdown - file string has online backup set Cause: An attempt to shutdown normally found that an online backup is still in progress. Action: End the backup of the offending tablespace and retry this command. ORA-01150: cannot prevent writes - file string has online backup set Cause: An attempt to make a tablespace read only or offline normal found that an online backup is still in progress. It will be necessary to write the file header to end the backup, but that would not be allowed if this command succeeded. Action: End the backup of the offending tablespace and retry this command. ORA-01151: use media recovery to recover block, restore backup if needed Cause: Error 1172 occurred. Action: This is additional information for error 1172. ORA-01152: file string was not restored from a sufficiently old backup Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the database consistent. This file is still in the future of the last log applied. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery. Action: Either apply more logs until the database is consistent or restore the database file from an older backup and repeat recovery. ORA-01153: an incompatible media recovery is active Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs Action: Complete or cancel the other media recovery session or RMAN backup ORA-01154: database busy. Open, close, mount, and dismount not allowed now Cause: Some operation is in progress that expects the opened/mounted state of this instance to remain the same. Action: Wait for the operation to complete then retry. If attempting to do a shutdown, SHUTDOWN ABORT will work. If this is a shutdown of a standby database that is operating in NO DATA LOSS mode, you must shutdown the primary database first. ORA-01155: the database is being opened, closed, mounted or dismounted Cause: The requested operation needs the instance to be in a particular state but the state is being changed. Action: Wait for the open, close, mount, or dismount to complete then retry the operation. If necessary, a SHUTDOWN ABORT will always work. ORA-01156: recovery in progress may need access to files Cause: Either media recovery or instance recovery is in progress. It may need the files this operation is being applied to. Action: Wait for recovery to complete. ORA-01157: cannot identify/lock data file string - see DBWR trace file Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However the first instance to open the database will need to access all online data files. Accompanying error from the operating system describes why the file could not be identified. Action: Have operating system make file available to database. Then either open the database or do ALTER SYSTEM CHECK DATAFILES. ORA-01158: database string already mounted Cause: Another instance has a database by this name mounted. Action: Find which instance is still running. Perhaps you have not lost the control files after all. ORA-01159: file is not from same database as previous files - wrong database id Cause: Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified. Action: Please double check the list of files provided to the CREATE ORA-01160: file is not a string Cause: The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated. Action: Please double check the mentioned file. ORA-01161: database name string in file header does not match given name of string Cause: The database name given at the command line does not match the database name found in the file header. Action: Chance are good that the database name specified at the command line is incorrect. Resolve the descepency, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option. ORA-01162: block size string in file header does not match configured block sizes Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the INIT.ORA file. Action: Configure the appropriate cache for this block size using one of the various (db_2k_cache_size, db_4k_cache_size, db_8k_cache_size, db_16k_cache_size, db_32K_cache_size) parameters. ORA-01163: SIZE clause indicates string (blocks), but should match header string Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header. Action: Specify the correct filename and size ( in bytes ). ORA-01164: MAXLOGFILES may not exceed string Cause: MAXLOGFILES specified on the command line too large. Action: Resubmit the command with a smaller MAXLOGFILES ORA-01165: MAXDATAFILES may not exceed string Cause: MAXDATAFILES specified on the command line too large. Action: Resubmit the command with a smaller MAXDATAFILES ORA-01166: file number string is larger than string (string) Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES. Action: Increase the maximum specified on the command line. ORA-01167: two files are the same file/group number or the same file Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file spec. This message will also appear if the same control file appears more than once in the control_files parameter in the init.ora file. If this happens, check for additional error messages. Action: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the control_files parameter in the init.ora file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list. ORA-01168: physical block size string does not match size string of other members Cause: The file is located on a device with a different physical block size than the other members in the group Action: Use a physical device with matching block size. ORA-01169: DATAFILE number 1 not found. Must be present Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command. Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE command. ORA-01170: file not found "string" Cause: ALL datafiles and, if NORESETLOGS, ALL logfiles MUST be accessible by the process for CREATE CONTROLFILE. Action: The file specified probably contains a typing error. Double check command and the existance of all files and then resubmit. ORA-01171: datafile string going offline due to error advancing checkpoint Cause: The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block. Action: See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online. ORA-01172: recovery of thread string stuck at block string of file string Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. Action: Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem then restore the file from a backup and recover it. ORA-01173: data dictionary indicates missing data file from system tablespace Cause: Either the database has been recovered to a point in time in the future of the control file or a datafile from the system tablespace was omitted from the create control file command previously issued. Action: For the former problem you need to recover the database from a more recent control file. For the latter problem, simply recreate the control file checking to be sure that you include all the datafiles in the system tablespace. ORA-01174: DB_FILES is string buts needs to be string to be compatible Cause: The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open. Action: Change the value of the DB_FILES parameter to be compatible ORA-01175: data dictionary has more than the string files allowed by the instance Cause: The data dictionary is found to have more files than that which can be supported by this instance. Action: Shutdown the instance and restart with a larger number of db_files ORA-01176: data dictionary has more than the string files allowed by the controlfie Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more datafiles than that supported by the control file. Action: Recreate the control file with a larger MAXDATAFILES. ORA-01177: data file does not match dictionary - probably old incarnation Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile. Action: Do a CREATE CONTROLFILE with the correct file or none at all. ORA-01178: file string created before last CREATE CONTROLFILE, cannot recreate Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed at the last CREATE CONTROLFILE command. The information needed to recreate the file was lost with the control file that existed when the file was added to the database. Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. ORA-01179: file string does not exist Cause: During datafile recovery, a file was listed which was not part for the database. Action: Recheck the datafile name. Remember to use double quotes at the SQLDBA command line and remember that the file name is translated in the environment of the SQLDBA. ORA-01180: can not create datafile 1 Cause: Attempting to create datafile 1 using ALTER DATABASE CREATE DATAFILE. Action: Recover file from a backup or recreate database. ORA-01181: file string created before last known RESETLOGS, cannot recreate Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that existed before the last known RESETLOGS. Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created. ORA-01182: cannot create database file string - file is in use or recovery Cause: Attempted to use ALTER DATABASE CREATE DATAFILE to recreate a datafile that is online in an open instance or is being recovered. Action: Close database in all instances and end all recovery sessions ORA-01183: cannot mount database in SHARED mode Cause: Some other instance has the database mounted exclusive. Action: Shutdown other instance then mount shared. ORA-01184: logfile group string already exists Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is already in use. Action: Specify a different logfile number, or let the database choose an unused value. ORA-01185: logfile group number string is invalid Cause: An ALTER DATABASE ADD LOGFILE command specified a log number for the new log which is too large. Action: Specify a correct logfile number. ORA-01186: file string failed verification tests Cause: The data file did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01187: cannot read from file string because it failed verification tests Cause: The data file did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01188: Block size string in header does not match physical block size string Cause: A log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the log. Action: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE. ORA-01189: file is from a different RESETLOGS than previous files Cause: In a CREATE CONTROLFILE command either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS. Action: If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command. ORA-01190: control file or data file string is from before the last RESETLOGS Cause: Attempting to use a data file when the log reset information in the file does not match the control file. Either the data file or the control file is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS. Action: Restore file from a more recent backup. ORA-01191: file string is already offline - cannot do a normal offline Cause: When attempting to do a normal tablespace offline it was discovered that one of the files in the tablespace was already offline. Action: Either bring the datafile online first, or use another tablespace offline option. ORA-01192: must have at least one enabled thread Cause: You must specify at least two logfiles from at least one thread at the create contolfile command line. Action: Find the missing logfiles and resubmit the command with the newly found logfiles included in the command line. ORA-01193: file string is not the same file seen at start of recovery Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery. Action: Ensure the correct file is available, then retry recovery. ORA-01194: file string needs more recovery to be consistent Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery. Action: Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery. ORA-01195: online backup of file string needs more recovery to be consistent Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended. Action: Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery. ORA-01196: file string is inconsistent due to a failed media recovery session Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file. Action: Either apply more logs until the file is consistent or restore the backup again and repeat recovery. ORA-01197: thread string only contains one log Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs. Action: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE. ORA-01198: must specify size for log file if RESETLOGS Cause: File sizes must be given for all logfiles if doing a CREATE CONTROLFILE with the RESETLOGS option. Action: Resubmit the command with the appropriate logfile size. ORA-01199: file string is not in online backup mode Cause: Attempting to end an online backup for a file that is not in online backup. Action: Do not enter command since it is not needed. ORA-01200: actual file size of string is smaller than correct size of string blocks Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy. Action: Restore a good copy of the data file and do recovery as needed. ORA-01201: file string header failed to write correctly Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made. Action: The file probably will require recovery. Further error messages will indicate what is needed. ORA-01202: wrong incarnation of this file - wrong creation time Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped. Action: Restore a current copy of the data file and do recovery as needed. ORA-01203: wrong incarnation of this file - wrong creation SCN Cause: The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped. Action: Restore a current copy of the data file and do recovery as needed. ORA-01204: file number is string rather than string - wrong file Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database. Action: Restore a copy of the correct data file and do recovery as needed. ORA-01205: not a data file - type number in header is string Cause: The file type in the header is not correct for a data file. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted. Action: Restore a copy of the correct data file and do recovery as needed. ORA-01206: file is not part of this database - wrong database id Cause: The database ID in the file header does not match the database id in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected. Action: Restore a copy of the correct data file and do recovery as needed. ORA-01207: file is more recent than control file - old control file Cause: The control file change sequence number in the data file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough. Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery. ORA-01208: data file is an old version - not accessing current version Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01209: data file is from before the last RESETLOGS Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use. Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES. ORA-01210: data file header is media corrupt Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistancy of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database. Action: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery. ORA-01211: Oracle7 data file is not from migration to Oracle8 Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8. Action: Have operating system make correct data file available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run. ORA-01212: MAXLOGMEMBERS may not exceed string Cause: MAXLOGMEMBERS specified on the command line too large. Action: Resubmit the command with a smaller MAXLOGMEMBERS ORA-01213: MAXINSTANCES may not exceed string Cause: MAXINSTANCES specified on the command line too large. Action: Resubmit the command with a smaller MAXINSTANCES ORA-01214: MAXLOGHISTORY may not exceed string Cause: MAXLOGHISTORY specified on the command line too large. Action: Resubmit the command with a smaller MAXLOGHISTORY ORA-01215: enabled thread string is missing after CREATE CONTROLFILE Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database. Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads. ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread). Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be recreated after the database is open. ORA-01217: logfile member belongs to a different logfile group Cause: A member of a multiple-member logfile group specified in a CREATE CONTROLFILE is not part of the same group as previous members. Action: Group together the correct members for the CREATE CONTROLFILE command. ORA-01218: logfile member is not from the same point-in-time Cause: A member of a multiple-member logfile group is from a different point in time. One of the members specified may be an older (backup) copy of the log. Action: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command. ORA-01219: database not open: queries allowed on fixed tables/views only Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened. Action: Re-phrase the query to include only fixed objects, or open the database. ORA-01220: file based sort illegal before database is open Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open. Action: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory. ORA-01221: data file string is not the same file to a background process Cause: When the database writer opens the data file, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all. Action: Look in the DBWR trace file for the error it recieved when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process. ORA-01222: MAXINSTANCES of string requires MAXLOGFILES be at least string, not string Cause: Attemping to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs. Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES. ORA-01223: RESETLOGS must be specified to set a new database name Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS. Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE. ORA-01224: group number in header string does not match GROUP string Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong. Action: Omit the GROUP option or give the correct one. ORA-01225: thread number string is greater than MAXINSTANCES string Cause: The log is for a thread greater than the MAXINSTANCES argument. Action: Increase the value for MAXINSTANCES and resubmit the command. ORA-01226: file header of log member is inconsistent with other members Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log. Action: Find the correct log member or omit this member from the command. ORA-01227: log string is inconsistent with other logs Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistancy. All log files listed in the command must be the current versions of the online logs. Action: Find the correct online logs or use the RESETLOGS option. ORA-01228: SET DATABASE option required to install seed database Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database. Action: Resubmit command with the SET DATABASE and RESETLOGS options. ORA-01229: data file string is inconsistent with logs Cause: The data file in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs. Action: Find the correct online logs or use the RESETLOGS option. ORA-01230: cannot make read only - file string is offline Cause: An attempt to make a tablespace read only found that one of its files is offline. Action: Bring the file online and retry this command. ORA-01231: cannot make read write - file string is offline Cause: An attempt to make a tablespace read write found that one of its files is offline. Action: Bring the file online and retry this command. ORA-01232: cannot start online backup - file string is being made read-only Cause: An attempt to start an online backup found that one of the files is in transition to read-only mode. Action: Wait for the transition to complete and then retry the command, if this is an ALTER DATABASE BEGIN BACKUP command, or take the backup without any begin or end commands, if this is an ALTER TABLESPACE BEGIN BACKUP command. ORA-01233: file string is read only - cannot recover using backup control file Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read only files do not normally need to be recovered, but recovery with a backup control file must recover all online files. Action: If the file really is read only, take it offline before the recovery, and bring the read only tablespace online after the database is open. If the file does need recovery use a control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one. ORA-01234: cannot end backup of file string - file is in use or recovery Cause: Attempted to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online. Action: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation. ORA-01235: END BACKUP failed for string file(s) and succeeded for string Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded. Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful. ORA-01236: Error string occurred during initialization of file header access Cause: The indicated error occurred while doing initialization processing of file headers. Action: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm. ORA-01237: cannot extend datafile string Cause: An operating system error occurred during the resize. Action: Fix the cause of the operating system error and retry the command. ORA-01238: cannot shrink datafile string Cause: An operating system error occurred during the resize. Action: The error is ignored, operation continues normally. ORA-01239: database must be in ARCHIVELOG mode to use external cache Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this can not be allowed. Action: Change database to be in ARCHIVELOG mode or do not use an external cache. ORA-01240: too many data files to add in one command Cause: The command specifies adding more data files than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large. Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands. ORA-01241: an external cache has died Cause: The external cache may have been restarted. Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all data files through consistent external caches. ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure. Action: Restore accessibility to the file mentioned in the error stack and restart the instance. ORA-01243: system tablespace file suffered media failure Cause: A system tablespace file was detected as inaccessible due to media failure. Action: Restore accessibility to the file mentioned in the error stack and restart the instance. ORA-01244: unnamed datafile(s) added to control file by media recovery Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files. Action: Rename the files to valid file names and resume recovery. If necessary the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option. ORA-01245: offline file string will be lost if RESETLOGS is done Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option. Action: Either bring the file online and recover it, or take it offline with the FOR DROP option. ORA-01246: recovering files through TSPITR of tablespace string Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery. Action: Restore more recent backups and recover them. ORA-01247: database recovery through TSPITR of tablespace string Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done. Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery. ORA-01248: file string was created in the future of incomplete recovery Cause: Attempting to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed. Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE. ORA-01249: archiving not allowed in a clone database Cause: Attempting to archive an online redo log or enable archiving for a clone database. Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed then recreate database as not a clone. ORA-01250: Error string occurred during termination of file header access Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error. Action: The indicated error should be corrected. ORA-01251: Unknown File Header Version read for file number string Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file. Action: Have the operating system make the correct file available to the database, or recover the file. ORA-01252: cannot prevent writes - file string in recovery manager backup Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read-only, then the file header cannot be updated when the backup is complete. Action: Wait for the Recovery Manager backup to complete and retry this command. ORA-01253: cannot start online backup - file string in recovery manager backup Cause: The specified file is being backed up by Recovery Manager. Action: Wait for the Recovery Manager proxy backup to complete before starting another backup. ORA-01254: cannot end online backup - file string in recovery manager backup Cause: The specified file is being backed up by Recovery Manager. Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be initiated or terminated manually. ORA-01255: cannot shutdown - file string in recovery manager backup Cause: An attempt to shutdown normally found that a Recovery Manager backup is still in progress. Action: Wait for the Recovery Manager proxy backup to complete and retry this command. ORA-01256: error in locking database file string Cause: The file is in use by another database instance. Action: Determine which database instance legitimately owns the file. ORA-01257: cannot reuse database file string, unknown file size Cause: The size of the raw partion cannot be determined Action: Add the datafile/logfile by specifying the size parameter. ORA-01258: unable to delete temporary file string Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database. Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file. ORA-01259: unable to delete datafile string Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace. Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file. ORA-01260: warning: END BACKUP succeeded but some files found not to be in backup mode Cause: END BACKUP completed successfully for all files that were in online backup mode. However one or more modifiable files were found not to be in online backup mode. Backup of those files (if it was done) can be invalid and, if restored, can result in an inconsistent database. Action: Check the alert log for a list of the files that were found not to be in backup mode. If there is a possibility that those files have been modified during online backup, then replace their backups with new ones. ORA-01261: Parameter string destination string cannot be translated Cause: The value for the specified parameter contained a destination string that could not be translated. Action: Use a valid destination string in the specified parameter. ORA-01262: Stat failed on a file destination directory Cause: Unable to get information about an Oracle managed files destination directory. Action: Check the permissions on the directory or use a different directory name. ORA-01263: Name given for file destination directory is invalid Cause: The name given for an Oracle managed files destination does not correspond to a directory. Action: Use a different name. ORA-01264: Unable to create string file name Cause: Unable to create an Oracle managed file name. Action: , if possible, and retry the command. ORA-01265: Unable to delete string string Cause: An error prevented the file from being deleted. Action: See the subsequent error messsages that describe the operating system error that prevented the file from being deleted. If possible, fix the problem and manually delete the file. ORA-01266: Unable to create unique file name Cause: Unable to create a unique file name for an Oracle managed file. Oracle tried several names but each file name was already in use in the default destination directory for the file type. Action: Retry the operation. If that fails, also, it may be necessary to change the default destination directory for the file type and then retry. ORA-01267: Failure getting date/time Cause: Could not get date/time when trying to create unique file name. Action: Internal error - contact Oracle Customer Support. ORA-01268: invalid TEMPFILE clause for alter of permanent TABLESPACE Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace. Action: Retry with a DATAFILE clause. ORA-01269: Destination parameter string is too long Cause: The value for DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n or DB_RECOVERY_FILE_DEST parameter was too long. Action: Replace the destination value for the specified parameter with a shorter character string. ORA-01270: %s operation is not allowed if STANDBY_PRESERVES_NAMES is true Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true. Action: Set STANDBY_PRESERVES_NAMES false if the operation must be performed. ORA-01271: Unable to create new file name for file string Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file. Action: Use the ALTER DATABASE CREATE DATAFILE command with a new unique name and then resume the standby database recovery. ORA-01272: REUSE only allowed when a file name is provided. Cause: The REUSE parameter was specified in a command without a file name. Action: Either supply a file name or remove the REUSE parameter. ORA-01273: STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher Cause: Automated standby file management was disabled, so an added file Action: Restart the instance with COMPATIBLE set to the correct release. ORA-01274: cannot add datafile "string" - file could not be created Cause: Automated standby file management was disabled, so an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The control file file entry for the file is "UNNAMEDnnnnn". Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file, or set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery. ORA-01275: Operation string is not allowed if standby file management is automatic. Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO. Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be performed. ORA-01276: Cannot add file string. File has an Oracle Managed Files file name. Cause: An attempt was made to add to the database a datafile, log file, control file, snapshot control file, backup control file, datafile copy, control file copy or backuppiece with an Oracle Managed Files file name. Action: Retry the operation with a new file name. ORA-01277: file "string" already exists Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS "filename" command specified a file name which is already in use. Action: Either specify a different file name, or add the REUSE parameter to the command to overwrite the existing file. ORA-01278: error creating file "string" Cause: An operating system error occurred while attempting to create a trace file specified in the command ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS "filename". Action: Check the error stack for more detailed information. ORA-01279: db_files too large Cause: db_files has been set too high to be supported by the system. Action: Decrease the number of db_files. ORA-01280: Fatal LogMiner Error. Cause: An internal error has occurred inside LogMiner. Action: none ORA-01281: SCN range specified is invalid Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid. Action: Specify a valid SCN range. ORA-01282: date range specified is invalid Cause: startTime may be greater than endTime. startTime or endTime may be greater than year 2110. startTime may be less than year 1988. Action: Specify a valid date range. ORA-01283: Options specified is invalid Cause: The specified options parameter is invalid for the procedure. Action: Specify valid Options parameter. ORA-01284: file string cannot be opened Cause: The file or directory may not exist or may be inaccessible. Pathname exceeds 256 characters. Action: Ensure that the file and the directory exist and are accessible. ORA-01285: error reading file string Cause: The file or directory may not exist or is inaccessible. Action: Specify valid file or directory. Make sure that file and directory are accessible. ORA-01286: start interval required Cause: Options were supplied which require a starting time or starting SCN Action: Specify a starting interval (time or SCN). ORA-01287: file string is from a different database incarnation Cause: The logfile is produced by a different incarnation of the database. Action: Add a logfile that is produced by the same incarnation. ORA-01289: cannot add duplicate logfile string Cause: The logfile specified has already been added to the list of logfiles. Action: Specify a different logfile. ORA-01290: cannot remove unlisted logfile string Cause: The user attempted to remove a logfile that is not present in the list. Action: Specify a valid logfile. ORA-01291: missing logfile Cause: Not all logfiles corresponding to the time or scn range specified have been added to the list. Action: Check the v$logmnr_logs view to determine the missing scn range, and add the relevant logfiles. ORA-01292: no log file has been specified for the current LogMiner session Cause: No logfile has been specified for the LogMiner session. Action: Specify atleast one log file. ORA-01293: mounted database required for specified LogMiner options Cause: Options were specified which required the database to be mounted Action: Specify different options or mount the database. ORA-01294: error occurred while processing information in dictionary file string, possible corruption Cause: The dictionary file is corrupt. Action: Get a new dictionary file. ORA-01295: DB_ID mismatch between dictionary string and logfiles Cause: The dictionary file is produced by a database that is different from that produced the logfiles. Action: Specify a compatible dictionary file. ORA-01296: character set mismatch between dictionary string and logfiles Cause: The character set of the database that produced the dictionary file is different from the charatcter set of the database that produced the logfiles. Action: Specify a dictionary file with the same character set. ORA-01297: redo version mismatch between dictionary string and logfiles Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles. Action: none ORA-01298: conflicting dictionary option Cause: More than one dictionary source was specified or DDL_DICT_TRACKING was specified with DICT_FROM_ONLINE_CATALOG. Action: none ORA-01299: dictionary string corresponds to a different database incarnation Cause: The dictionary file was extracted from a different incarnation of the database. Action: Specify a dictionary file extracted from the correct database incarnation. ORA-01300: writable database required for specified LogMiner options Cause: Options were specified which required the database to be writable. Action: Specify different options or open the database for write access. ORA-01301: error writing to file during flat file build Cause: Error writing to file during flat file build Action: none ORA-01302: dictionary build options missing or incorrect Cause: Missing dictionary build options or incorrectly specified options Action: Specify either a build to redo log or to flat file. If build to flat file, specify filename and directory. ORA-01303: subordinate process error: number. Check alert and trace logs Cause: A process subordinate to this Logminer process has exited with this error status. Action: Search for this error in the alert log and trace files for additional information. ORA-01304: subordinate process error. Check alert and trace logs Cause: A process subordinate to this Logminer process has exited with an error condition. Action: Look in the alert log and trace files for additional information. ORA-01306: dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view. ORA-01307: no LogMiner session is currently active Cause: A select was issued from v$logmnr_contents without first invoking the dbms_logmnr.start_logmnr() procedure. Otherwise, dbms_logmnr.end_logmnr() was called without a prior call to dbms_logmnr.start_logmnr() or dbms_logmnr.add_logfile() Action: Invoke the dbms_logmnr.start_logmnr() procedure before issuing a select from the v$logmnr_contents view. ORA-01308: initialization parameter utl_file_dir is not set Cause: utl_file_dir is not set in the initialization file. Action: Set utl_file_dir to the appropriate directory. ORA-01309: invalid session Cause: The specified Logminer session ID or session handle is invalid. Action: Use a valid Logminer session ID or session handle. ORA-01310: requested return type not supported by the lcr_mine function Cause: The return type requested by the user is not supported by lcr_mine" Action: Pick a return type supported by the lcr_mine function" ORA-01311: Illegal invocation of the mine_value function Cause: An attempt was made to use mine_value function on a column other than redo_value or undo_value columns of SYS.X$LOGMNR_CONTENTS or SYS.V$LOGMNR_CONTENTS fixed table/view. Action: Rewrite the SQL statement with a legal invocation of mine_value ORA-01312: Specified table/column does not exist Cause: The table/column specified in the lcr_mine call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly. Action: Create a LogMiner session at a start SCN at which the table definition is available. ORA-01313: LogMiner dictionary column type different from specified type Cause: The return type specified for the column in lcr_mine call is different from the actual type of the column. Action: Rewrite the lcr_mine invocation with the right return type. ORA-01314: Name of the column to be mined should be a string literal Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal. Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in "a.b.c.d". ORA-01315: Log file has been added or removed during select Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view. Action: Re-issue the SQL select statement on the v$logmnr_logs view. ORA-01316: Already attached to a Logminer session Cause: A Logminer attach session was issued while already attached to a Logminer session. Action: Detach from the current Logminer session and attach to the requested session. ORA-01317: Not attached to a Logminer session Cause: A command or procedure was issued which requires an attached Logminer session. Action: Attach to a Logminer session before issuing the command or procedure. ORA-01319: Invalid Logminer session attribute Cause: A session attribute was supplied which is invalid. Action: Re-issue with valid session attribute. ORA-01320: Invalid Logminer dictionar attribute Cause: A Logminer dictionary attribute was supplied which is invalid. Action: Re-issue with valid dictionary attribute. ORA-01322: No such table Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table(). Action: Re-issue with valid table name. ORA-01323: Invalid state Cause: A Logminer routine was called from the wrong state. Action: none ORA-01324: cannot add file string due to DB_ID mismatch Cause: The logfile is produced by a different database than other logfiles already added to the list. Action: Specify a logfile produced by the same database. ORA-01325: archive log mode must be enabled to build into the logstream Cause: Database does not have archivelog mode enabled. Action: Mount the database, then issue commands to enable archivelog mode. startup pfile=init.ora mount alter database archivelog alter database open ORA-01326: compatability of 9.0 or greater required to build into the logstream Cause: Compatibility mode set to some value less than 9.0 Action: Ensure that init.ora parameter establishing a compatability of 9.0 or greater is set. For example: compatible=9.0.0.0.0 ORA-01327: failed to exclusively lock system dictionary as required by build Cause: Other users are performing DDL operations. Action: none ORA-01328: only one build operation may occur at one time Cause: Another processes is simultaneously attempting to run build(); Action: Wait until the other processes completes. ORA-01329: unable to truncate required build table Cause: The table may be missing, or locked by another user. Action: none ORA-01332: internal Logminer Dictionary error Cause: Unexpected error condition Action: Check trace and/or alert logs ORA-01333: failed to establish Logminer Dictionary Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictiony. Or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary. Action: If build() was not employed prior to this mining session the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have beed added. The following query, run on the system which build() was run, can be helpful in identifying the requried files. select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log; Minimally a set of files beginning with one which has DICTIONARY_BEGIN = "YES" and all following log files through one marked DICTIONARY_END = "YES" must be added. ORA-01334: invalid or missing logminer dictionary processes context Cause: Unexpected internal error condition Action: none ORA-01336: specified dictionary file cannot be opened Cause: The dictionary file or directory does not exist or is inaccessible. Action: Make sure that the dictionary file and directory exist and are accessible. ORA-01337: log file has a different compatibility version Cause: The logfile has a different compatibility version then the rest of the logfile in the session" Action: Make sure that the logfile has the same compatibility version as the rest of the logfiles in the session. ORA-01338: Other process is attached to LogMiner session Cause: Can not do this when other process is attached to LogMiner session. Action: none ORA-01340: NLS error Cause: Could not load NLS package. Action: none ORA-01341: LogMiner out-of-memory Cause: The LogMiner session requires more system resources than is currently available. Action: Allocate more SGA for LogMiner. ORA-01342: LogMiner can not resume session due to inability of staging checkpointed data Cause: Logmnr can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery. Action: Specify a bigger max_sga for the given LogMiner session and try again. ORA-01343: LogMiner encountered corruption in the logstream Cause: Log file is missing a range of scn values. Action: Verify the contiguity of the scn range reprented by the log files added to LogMiner. ORA-01344: LogMiner coordinator already attached Cause: A coordinator process is already attached to the specified logminer context. Action: Detach from the active coordinator session and retry the attach. ORA-01345: must be a LogMiner coordinator process Cause: A LogMiner client attempted to perform a privileged operation. Action: Issue the operation from the coordinator process. ORA-01346: LogMiner processed redo beyond specified reset log scn Cause: LogMiner has detected a new branch with resetlogs scn information prior to redo already mined. Action: Contact your customer support representative. ORA-01347: Supplemental log data no longer found Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data. Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session. ORA-01350: must specify a tablespace name Cause: Invocation failed to specify a valid tablespace Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of a valid tablespace. ORA-01351: tablespace given for Logminer dictionary does not exist Cause: The tablespace name given as a parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist. Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace. ORA-01352: tablespace given for Logminer spill does not exist Cause: The tablespace name given as the parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist. Action: Check spelling of the tablespace name. If spelling is correct verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE does not create a tablespace. ORA-01353: existing Logminer session Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while a Logminer session(s) was active. Action: First cause all Logminer sessions to be closed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of using Oracle features such as Data Guard SQL Apply or Streams which use Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE. ORA-01354: Supplemental log data must be added to run this command Cause: An attempt was made to perform an operation that required that supplemental log data be enabled. Action: Execute a command such as ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and then reissue the command that failed with this error. ORA-01355: logminer tablespace change in progress Cause: The tables used by logminer are in the process of being moved to another tablespace. Action: Wait until the move is complete and try again. ORA-01356: active logminer sessions found Cause: Logminer sessions are currently active. Action: End all logminer sessions and retry. ORA-01361: global name mismatch Cause: The database global name where the log file was generated did not match the user-specified global name of the Streams Capture process. Action: Start a new capture process and ensure that the user-specified global name matches that of the database that generated the log file. ORA-01370: Specified restart SCN is too old Cause: specified restart scn is too old, logmnr could not find a proper checkpoint. Action: Specify a bigger restart SCN to try again ORA-01371: Complete LogMiner dictionary not found Cause: One or more log files containing the LogMiner dictionary was not found. Action: Add into LogMiner all log files containing the dictionary. ORA-01372: Insufficient processes for specified LogMiner operation Cause: The number of processes requested by the caller can not be allocated Action: Increase number of parallel servers allocated to the instance ORA-01373: insufficient memory for staging persistent LogMiner session Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session. Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart instance. ORA-01374: _log_parallelism_max greater than 1 not supported in this release Cause: LogMiner does not mine redo records generated with _log_parallelism_max set to a value greater than 1. Action: none ORA-01375: Corrupt logfile string recovered Cause: A corrupt logfile has been recovered by RFS Action: None. Logical Standby should automatically restart. If logfile is still corrupt, may need to manually copy and reregister the logfile on the standby. ORA-01409: NOSORT option may not be used; rows are not in ascending order Cause: Creation of index with NOSORT option when rows were not ascending. For non-unique indexes the rowid is considered part of the index key. Therefore, if you create an index nosort and two of the rows in the table have the same key and are stored in ascending order, but get split accross two extents where the dba of the first block in the second extent is less than the dba of the last block in the first extent, then the create index nosort may fail. Action: Create the index without the NOSORT option, or ensure table is stored in one extent. ORA-01411: cannot store the length of column in the indicator Cause: Tried to fetch a column of size more than 64K and couldn"t store the length of the column in the given indicator of size 2 bytes. Action: Use the new bind type with call backs to fetch the long column. ORA-01412: zero length not allowed for this datatype Cause: The length for type 97 is 0 Action: Specify the correct length. ORA-01413: illegal value in packed decimal number buffer Cause: The user buffer bound by the user as packed decimal number contained an illegal value. Action: Use a legal value. ORA-01414: invalid array length when trying to bind array Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length. Action: Sepcify a valid length. ORA-01415: too many distinct aggregate functions Cause: The query contains more distinct aggregates than can be processed. The current limit is 255. Action: Reduce the number of distinct aggregate functions in the query. ORA-01417: a table may be outer joined to at most one other table Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed Action: Check that this is really what you want, then join b and c first in a view. ORA-01422: exact fetch returns more than requested number of rows Cause: The number specified in exact fetch is less than the rows returned. Action: Rewrite the query or change number of rows requested ORA-01424: missing or illegal character following the escape character Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, "%", or "_". Action: Remove the escape character or specify the missing character. ORA-01425: escape character must be character string of length 1 Cause: Given escape character for LIKE is not a character string of length 1. Action: Change it to a character string of length 1. ORA-01426: numeric overflow Cause: Evaluation of an value expression causes an overflow/underflow. Action: Reduce the operands. ORA-01429: Index-Organized Table: no data segment to store overflow row-pieces Cause: No overflow segment defined. Action: Add overflow segment. ORA-01438: value larger than specified precision allowed for this column Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column. Action: Enter a value that complies with the numeric column"s precision, or use the MODIFY option with the ALTER TABLE command to expand the precision. ORA-01451: column to be modified to NULL cannot be modified to NULL Cause: the column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint. Action: if a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint. ORA-01453: SET TRANSACTION must be first statement of transaction Cause: self-evident Action: commit (or rollback) transaction, and re-execute ORA-01456: may not perform insert/delete/update operation inside a READ ONLY transaction Cause: A non-DDL insert/delete/update or select for update operation was attempted Action: commit (or rollback) transaction, and re-execute ORA-01463: cannot modify column datatype with current constraint(s) Cause: An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa. Action: Remove the constraint(s) or do not perform the offending operation. ORA-01466: unable to read data - table definition has changed Cause: Query parsed after tbl (or index) change, and executed w/old snapshot Action: commit (or rollback) transaction, and re-execute ORA-01469: PRIOR can only be followed by a column name Cause: Attempting to specify "PRIOR " where is not a column name. Action: Only a column name can follow PRIOR. Replace with a column name. ORA-01470: In-list iteration does not support mixed operators Cause: Constants of different types are specified in an in-list. Action: Use constants of same type for in-lists. ORA-01478: array bind may not include any LONG columns Cause: User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes. Action: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead. ORA-01479: last character in the buffer is not Null Cause: A bind variable of type 97 does not contain null at the last position Action: Make the last character null ORA-01480: trailing null missing from STR bind value Cause: A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer. Action: Terminate the string with a null character ORA-01481: invalid number format model Cause: The user is attempting to either convert a number to a string via TO_CHAR or a string to a number via TO_NUMBER and has supplied an invalid number format model parameter. Action: Consult your manual. ORA-01482: unsupported character set Cause: The character set used to perform the operation, such as the CONVERT function, is not a supported character set. Action: Use one of the supported character sets. ORA-01483: invalid length for DATE or NUMBER bind variable Cause: A bind variable of type DATE or NUMBER is too long. Action: Consult your manual for the maximum allowable length. ORA-01484: arrays can only be bound to PL/SQL statements Cause: You tried to bind an array to a non-PL/SQL statement. Action: none ORA-01485: compile bind length different from execute bind length Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length (given in the bind call). The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array. Action: none ORA-01486: size of array element is too large Cause: You tried to bind a data value which was either too large for the datatype (for example, NUMBER) or was greater than 4000 bytes (for example, VARCHAR or LONG). Action: none ORA-01487: packed decimal number too large for supplied buffer Cause: An impossible request for decimal to oracle number conversion was made Action: This conversion cannot be performed ORA-01488: invalid nibble or byte in the input data Cause: An impossible request for decimal to oracle number conversion was made Action: This conversion cannot be performed ORA-01489: result of string concatenation is too long Cause: String concatenation result is more than the maximum size. Action: Make sure that the result is less than the maximum size. ORA-01490: invalid ANALYZE command Cause: Incorrect syntax specified Action: Retry the command ORA-01491: CASCADE option not valid Cause: The CASCADE option is only valid for tables or clusters. Action: Do not specify CASCADE ORA-01492: LIST option not valid Cause: The LIST option is only valid for tables or clusters. Action: Do not specify LIST ORA-01493: invalid SAMPLE size specified Cause: The specified SAMPLE size is out of range Action: Specify a value within the proper range. ORA-01494: invalid SIZE specified Cause: The specified histogram SIZE value was out of range. Action: Specify a value within the proper range. ORA-01495: specified chain row table not found Cause: The specified table either does not exist or user does not have the proper privleges. Action: Specify the correct table to use. ORA-01496: specified chain row table form incorrect Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. ORA-01497: illegal option for ANALYZE CLUSTER Cause: The FOR COLUMNS clause may not be used with ANALYZE CLUSTER. Action: Retry with a legal syntax. ORA-01500 to ORA-02098ORA-01500: failure in getting date/time Cause: During create database or alter tablespace, there was a failure in getting the date and time. Action: Contact your customer support representative. ORA-01501: CREATE DATABASE failed Cause: An error occurred during create database Action: See accompanying errors. ORA-01502: index "string.string" or partition of such index is in unusable state Cause: 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 Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition ORA-01503: CREATE CONTROLFILE failed Cause: An error occurred during CREATE CONTROLFILE Action: See accompanying errors. ORA-01504: database name "string" does not match parameter db_name "string" Cause: The name in a database create or mount does not match the name given in the INIT.ORA parameter db_name. Action: correct or omit one of the two names. ORA-01505: error in adding log files Cause: During create or alter database, error(s) occurred when adding new log files. Action: Check error stack for detailed error information. ORA-01506: missing or illegal database name Cause: No db_name INIT.ORA aprameter was specified. Action: The database name must be given in the db_name INIT.ORA parameter. ORA-01507: database not mounted Cause: A command was attempted that requires the database to be mounted. Action: If you are using the ALTER DATABASE statement via the SQLDBA startup command, specify the MOUNT option to startup; 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. If you are doing a FLASHBACK DATABASE, you must first mount the desired database. ORA-01508: cannot create database; error in file "string" at line string Cause: CREATE DATABASE was unable to process the specified file. Action: Check the offending line in the specified file. ORA-01509: specified name "string" does not match actual "string" Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database. Action: Correct the database name spelling or DISMOUNT the mounted database. ORA-01510: error in deleting log files Cause: During ALTER DATABASE, an error occurred while dropping log files. Action: Check the error stack for detailed error information. ORA-01511: error in renaming log/data files Cause: An error occurred during the ALTER DATABASE RENAME FILE command. Action: Check the error stack for detailed error information. ORA-01512: error renaming log file string - new file string not found Cause: An attempt to change a log file"s name in the control file failed because no file was found with the new name. Action: Make sure that the log file has been properly renamed by the operating system and retry. ORA-01513: invalid current time returned by operating system Cause: The operating system returned a time that was not between 1988 and 2121. Action: Correct the time kept by the operating system. ORA-01514: error in log specification: no such log Cause: A log file name, or list of member names, did not correspond to an existing log. Action: Specify an existing log file. ORA-01515: error dropping log group string: no such log Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database control file. Action: Specify the name of an existing log file. ORA-01516: nonexistent log file, datafile, or tempfile "string" Cause: 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 (e.g., resize, autoextend, online/offline, etc.); 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. Action: 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. ORA-01517: log member: "string" Cause: Used to print member names Action: See top level error for information ORA-01518: CREATE DATABASE must specify more than one log file Cause: Only one log file was specified in the CREATE DATABASE statement. Action: Specify at least two log files. ORA-01519: error while processing file "string" near line string Cause: CREATE DATABASE encountered a problem while processing specified file. The specified file is bad. Action: Retry your system installation procedure or contact your customer support representative. ORA-01520: number of data files to add (string) exceeds limit of string Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database. Action: Use fewer files or re-create the database with a larger value of MAXDATAFILES. ORA-01521: error in adding data files Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding data files. Action: Check the error stack for detailed error information. ORA-01522: file "string" to be renamed does not exist Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file. Action: Specify the correct file name. ORA-01523: cannot rename data file to "string" - file already part of database Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file. Action: Rename the file to a name not already being used as part of the database. ORA-01524: cannot create data file as "string" - file already part of database Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file. Action: Create the file as a name not already being used as part of the database. ORA-01525: error in renaming data files Cause: An error occurred when renaming files as part of ALTER TABLESPACE. Action: Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack. ORA-01526: error in opening file "string" Cause: CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error. Action: Retry your system installation procedure or contact your customer support representative. ORA-01527: error while reading file Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error. Action: Retry your system installation procedure or contact your customer support representative. ORA-01528: EOF while processing SQL statement Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The sql.bsq file is bad. Action: Retry your system installation procedure or contact your customer support representative. ORA-01529: error closing file "string" Cause: CREATE DATABASE was not able to close the specified file. Action: Retry your system installation procedure or contact your customer support representative. ORA-01530: a database already mounted by the instance Cause: 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. Action: If you wish to mount the database, shutdown the instance and then startup the instance and retry the operation. ORA-01531: a database already open by the instance Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database. Action: If you wish to open a new database on the instance, first shutdown the instance and then startup the instance and retry the operation. ORA-01532: cannot create database; instance being started elsewhere Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance. Action: Make sure no one else is simultaneously altering the instance. If no one is, contact your customer support representative; otherwise, retry the operation. ORA-01533: cannot rename file "string"; file does not belong to tablespace Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace. Action: Specify the correct file name or the correct tablespace name. ORA-01534: rollback segment "string" doesn"t exist Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown. Action: Use the correct rollback segment name. ORA-01535: rollback segment "string" already exists Cause: Specified rollback segment already exists. Action: Use a different name. ORA-01536: space quota exceeded for tablespace "string" Cause: 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. Action: 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. ORA-01537: cannot add file "string" - file already part of database Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database. Action: Use a different file name. ORA-01538: failed to acquire any rollback segment Cause: Failed to acquire any rollback segment during startup in shared mode Action: Startup in exclusive mode to create one more public segment or specify available private segments in the INIT.ORA parameter rollback_segments_required, then startup in shared mode ORA-01539: tablespace "string" is not online Cause: Failed to either make a tablespace read only or offline because it is not online. A tblespace must be online before it can become read only or offline normal. Action: 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. ORA-01540: tablespace "string" is not offline Cause: Failed to bring a tablespace online because it is not offline Action: Check the status of the tablespace ORA-01541: system tablespace cannot be brought offline; shut down if necessary Cause: Tried to bring system tablespace offline Action: Shutdown if necessary to do recovery ORA-01542: tablespace "string" is offline, cannot allocate space in it Cause: Tried to allocate space in an offline tablespace Action: Bring the tablespace online or create the object in other tablespace ORA-01543: tablespace "string" already exists Cause: Tried to create a tablespace which already exists Action: Use a different name for the new tablespace ORA-01544: cannot drop system rollback segment Cause: Tried to drop system rollback segment Action: None ORA-01545: rollback segment "string" specified not available Cause: Either: 1) An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace. 2) An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance. 3) An attempt was made to drop a rollback segment that is currently online. 4) An attempt was made to alter a rollback segment that is currently online to use unlimited extents. 5) An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file. Action: Either: 1) Make the rollback segment available; for example, bring an offline tablespace online. 2) Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment. 3) Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions. 4) Same as 3). 5) Remove the name from the _corrupted_rollback_segments parameter. ORA-01546: tablespace contains active rollback segment "string" Cause: Tried to make a tablespace that contains active rollback segment(s) offline or read only Action: Shutdown instances that use the active rollback segments in the tablespace and then make the tablespace offline or read only ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below Cause: 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. Action: Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria. ORA-01548: active rollback segment "string" found, terminate dropping tablespace Cause: Tried to drop a tablespace that contains active rollback segment(s) Action: Shutdown instances that use the active rollback segments in the tablespace and then drop the tablespace ORA-01549: tablespace not empty, use INCLUDING CONTENTS option Cause: Tried to drop a non-empty tablespace Action: To drop all the objects in the tablespace, use the INCLUDING CONTENTS option ORA-01550: cannot drop system tablespace Cause: Tried to drop system tablespace Action: None ORA-01551: extended rollback segment, pinned blocks released Cause: Doing recursive extent of rollback segment, trapped internally by the system Action: None ORA-01552: cannot use system rollback segment for non-system tablespace "string" Cause: Tried 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. Action: Create one or more private/public segment(s), shutdown and then startup again. May need to modify the INIT.ORA parameter rollback_segments to acquire private rollback segment. If this is a clone database being used for tablspace point in time recovery then this operation is not allowed. If the non-system tablespace has AUTO segment space management, then create an undo tablespace. ORA-01553: MAXEXTENTS must be no smaller than the string extents currently allocated Cause: The number of extents allocated is greater than the MAXEXTENTS specified. Action: Specify a larger MAXEXTENTS value. ORA-01554: out of transaction slots in transaction tables Cause: Too many concurrent transactions Action: Shutdown the system, modify the INIT.ORA parameters transactions, rollback_segments or rollback_segments_required, then startup again ORA-01555: snapshot too old: rollback segment number string with name "string" too small Cause: rollback records needed by a reader for consistent read are overwritten by other writers Action: If in Automatic Undo Management mode, increase undo_retention setting. Otherwise, use larger rollback segments ORA-01556: MINEXTENTS for rollback segment must be greater than 1 Cause: Specified MINEXTENTS of less than 2 for rollback segment Action: Specify larger MINEXTENTS ORA-01557: rollback segment extents must be at least string blocks Cause: Specified extent of less than minimum size for rollback segment Action: Specify larger extents ORA-01558: out of transaction ID"s in rollback segment string Cause: All the available transaction id"s have been used Action: Shutdown the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction id"s. ORA-01559: MAXEXTENTS for rollback segment must be greater than 1 Cause: Specified MAXEXTENTS of less than 2 for rollback segment Action: Specify larger MAXEXTENTS ORA-01560: LIKE pattern contains partial or illegal character Cause: like pattern is not formed correctly Action: make sure like pattern is specified correctly ORA-01561: failed to remove all objects in the tablespace specified Cause: Failed to remove all objects when dropping a tablespace Action: Retry the drop tablespace until all objects are dropped ORA-01562: failed to extend rollback segment number string Cause: Failure occurred when trying to extend rollback segment Action: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintainence. Use the alter rollback segment offline command to take the rollback segment offline. ORA-01563: rollback segment is PUBLIC, need to use the keyword PUBLIC Cause: Did not use the keyword PUBLIC to identified public rollback segment Action: Use the keyword PUBLIC when identifying public rollback segment ORA-01564: rollback segment is not PUBLIC Cause: The rollback segment segment identified is not public Action: Do not use the keyword PUBLIC when identifying private rollback segment ORA-01565: error in identifying file "string" Cause: An error occurred while trying to identify a file. Action: Check the error stack for detailed information. ORA-01566: file specified more than once in ALTER DATABASE Cause: The list of files supplied to the command contained at least one duplicate. Action: Remove the duplicate file specification and retry. ORA-01567: dropping log string would leave less than 2 log files for instance string (thread string) Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread. Action: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it. ORA-01568: cannot set space quota on PUBLIC Cause: Trying to set space quota on a tablespace for PUBLIC. Action: If trying to grant system-wide or tablespace-wide space priviledges to all users, use GRANT RESOURCE [ON ] TO PUBLIC. ORA-01569: data file too small for system dictionary tables Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables. Action: Recreate the database by specifying a larger file or more files. ORA-01570: MINEXTENTS must be no larger than the string extents currently allocated Cause: The number of extents allocated is smaller than the MINEXTENTS specified. Action: Specify a smaller MINEXTENTS value. ORA-01571: redo version string incompatible with ORACLE version string Cause: This software version can not 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. Action: Shutdown and startup using the compatible software. Do any required media recovery, and open the database. Shutdown and then startup using current software. If the file is going to be dropped then take it offline with the DROP option to skip this check. ORA-01572: rollback segment "string" cannot be brought online, string extents exceeded Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing. Action: Drop and recreate the rollback segment. ORA-01573: shutting down instance, no further change allowed Cause: Some process tries to make changes while the db is being shutdown Action: None ORA-01574: maximum number of concurrent transactions exceeded Cause: the limit on the number of concurrent transactions has been hit Action: shutdown the system, increase the INIT.ORA parameter "transactions" , and then restart the system. ORA-01575: timeout waiting for space management resource Cause: failed to acquire necessary resource to do space management. Action: Retry the operation. ORA-01576: The instance string is not enabled Cause: The thread associated with instance is not enabled. Action: Enable the thread associated with the instance using ALTER DATABASE ENABLE INSTANCE command. ORA-01577: cannot add log file "string" - file already part of database Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database. Action: Use a different file name. ORA-01578: ORACLE data block corrupted (file # string, block # string) Cause: The data block indicated was corrupted, mostly due to software errors. Action: Try to restore the segment containing the block indicated. This may involve dropping the segment and recreating it. If there is a trace file, report the errors in it to your ORACLE representative. ORA-01579: write error occurred during recovery Cause: A write error occurred during recovery Action: Consult trace files for the nature of the write error, and correct error. ORA-01580: error creating control backup file string Cause: An operating system error occurred while attempting to create a control file backup. Action: Check the error stack for more detailed information ORA-01581: attempt to use rollback segment (string) new extent (string) which is being allocated Cause: Undo generated to extend a rollback segment run out of current undo block space and is attempting to write into the new extent which has not been completely allocated. Action: The rollback segment extending will be rollbacked by the system, no more extension will be possible untill the next extent is freed up by rolling back or committing other transactions. ORA-01582: unable to open control file for backup Cause: An operating system error occurred while attempting to open a control file for backup. Action: Check the error stack for more detailed information ORA-01583: unable to get block size of control file to be backed up Cause: An operating system error occurred while attempting to get the block size of a control file for backup. Action: Check the error stack for more detailed information ORA-01584: unable to get file size of control file to be backed up Cause: An operating system error occurred while attempting to get the file size of a control file for backup. Action: Check the error stack for more detailed information ORA-01585: error identifying backup file string Cause: An operating system error occurred when attempting to identify the file to be used for control file backup. Action: Check the error stack for more detailed information ORA-01586: database must be mounted EXCLUSIVE and not open for this operation Cause: Attempting to DROP DATABASE when the database is not mounted EXCLUSIVE. Action: Mount the database in EXCLUSIVE mode. ORA-01588: must use RESETLOGS option for database open Cause: An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup, or a FLASHBACK DATABASE was done. Action: Use the RESETLOGS option when opening the database. ORA-01589: must use RESETLOGS or NORESETLOGS option for database open Cause: 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. Action: Specify the appropriate option. ORA-01590: number of segment free list (string) exceeds maximum of string Cause: storage parameter FREELIST GROUPS is too large. Action: Reduce storage parameters FREELIST GROUPS ORA-01591: lock held by in-doubt distributed transaction string Cause: Trying to access resource that is locked by a dead two-phase commit transaction that is in prepared state. Action: DBA 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, DBA should contact DBA at commit point if known or 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. ORA-01592: error converting Version 7 rollback segment (string) to Oracle 8 format Cause: Look at the accompanying internal error; Version 7 database may not have shutdown cleanly. Action: Investigate the internal error; may have to reload the Version 7 database (from backup) and shutdown the database cleanly. ORA-01593: rollback segment optimal size (string blks) is smaller than the computed initial size (string blks) Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment. Action: Specify a larger OPTIMAL size. ORA-01594: attempt to wrap into rollback segment (string) extent (string) which is being freed Cause: Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and/or too many extents to free Action: The rollback segment shrinking will be rollbacked by the system; increase the optimal size of the rollback segment. ORA-01595: error freeing extent (string) of rollback segment (string)) Cause: Some error occurred while freeing inactive rollback segment extents. Action: Investigate the accompanying error. ORA-01596: cannot specify system in string parameter Cause: The system rollback segment is specified in the INIT.ORA parameter referred to in the error message Action: change the INIT.ORA parameter ORA-01597: cannot alter system rollback segment online or offline Cause: Tried to online or offline the system rollback segment Action: None ORA-01598: rollback segment "string" is not online Cause: Could have been taken offline before by DBA or cleaned up by SMON. Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make sure the rollback segment is actually online. ORA-01599: failed to acquire rollback segment (string), cache space is full Cause: the amount statically allocated is not enough based on max_rollback_segments parameter. Action: For now take another rollback segment offline or increase the parameter max_rollback_segments ORA-01600: at most one "string" in clause "string" of string Cause: The INIT.ORA parameter was mis-specified. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01601: illegal bucket size in clause "string" of string Cause: The bucket size was invalid for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01603: illegal grouping size in clause "string" of string Cause: The grouping size was invalid for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01604: illegal number range in clause "string" of string Cause: The number range was invalid for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01605: missing numbers in clause "string" of string Cause: The numbers were missing for this parameter. Action: Correct the INIT.ORA parameter and restart the instance. ORA-01606: gc_files_to_locks not identical to that of another mounted instance Cause: The gc_files_to_locks parameters were different on two instances. Action: Modify the INIT.ORA parameter gc_files_to_locks and restart. ORA-01607: cannot add logfile to the specified instance Cause: The limit on the number of instances supported by the control file has been reached. Action: Use an instance name supported by the control file, or resize the thread record and/or checkpoint progress record secions of the control file. ORA-01608: cannot bring rollback segment "string" online, its status is (string) Cause: Could have been brought online before by DBA or left as a result of process crash. Action: Check the status of rollback segment in undo$ or dba_rollback_segs ORA-01609: log string is the current log for thread string - cannot drop members Cause: A member of the current log for a thread cannot be dropped. Action: 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. ORA-01610: recovery using the BACKUP CONTROLFILE option must be done Cause: Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was recreated 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. Action: Perform recovery using the BACKUP CONTROFILE option. ORA-01611: thread number string is invalid - must be between 1 and string Cause: A thread number in a command is greater than the number of threads supported by the control file. Action: Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the control file. ORA-01612: instance string (thread string) is already enabled Cause: An attempt was made to enable a thread that is already enabled. Action: Either use this thread or enable another thread. ORA-01613: instance string (thread string) only has string logs - at least 2 logs required to enable. Cause: The thread cannot be enabled because it only has two online log files associated with it. Action: Add logs to the thread or pick another thread to enable ORA-01614: instance string (thread string) is busy - cannot enable Cause: 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. Action: Wait and try again, or find another thread to enable. ORA-01615: instance string (thread string) is mounted - cannot disable Cause: Some instance, possibly this one, has allocated the thread for its use. The thread can not be disabled while in use. Action: Shut the instance down cleany using the thread. ORA-01616: instance string (thread string) is open - cannot disable Cause: 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. Action: 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. ORA-01617: cannot mount: string is not a valid thread number Cause: The INIT.ORA parameter "thread" is not between 1 and the number of threads allowed by the control file. Action: Shut down the instance, change the INIT.ORA parameter and startup, or resize the thread record and/or checkpoint progress record sections of the control file. ORA-01618: redo thread string is not enabled - cannot mount Cause: The INIT.ORA parameter "thread" requests a thread that is not enabled. A thread must be enabled before it can be mounted. Action: Shutdown the instance, change the INIT.ORA parameter and startup mounting a different thread. If the database is open in another instance then the thread may be enabled. ORA-01619: thread string is mounted by another instance Cause: The INIT.ORA parameter "thread" requests a thread that has been mounted by another instance. Only one instance may use a thread. Action: Shutdown the instance, change the INIT.ORA parameter and startup mounting a different thread. ORA-01620: no public threads are available for mounting Cause: The INIT.ORA parameter "thread" is zero, its default value. There are no threads which have been publicly enabled, and not mounted. Action: Shutdown the instance, change the INIT.ORA 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. ORA-01621: cannot rename member of current log if database is open Cause: 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. Action: Wait until the log is not current, or mount the database exclusively. ORA-01622: thread number must be specified - default not specific Cause: 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. Action: Explicitly specify the thread number either in the INIT.ORA parameter "thread", or in the add command. ORA-01623: log string is current log for instance string (thread string) - cannot drop Cause: 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. Action: 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. ORA-01624: log string needed for crash recovery of instance string (thread string) Cause: A log cannot be dropped or cleared until the thread"s checkpoint has advanced out of the log. Action: 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. ORA-01625: rollback segment "string" does not belong to this instance Cause: Trying to shrink or take a rollback segment offline that does not belong to this instance. Action: none ORA-01626: rollback segment number "string" cannot handle more transactions Cause: Too many transactions in this segment. Action: Choose a different rollback segment, or reduce the number of concurrent transactions. ORA-01627: rollback segment number "string" is not online Cause: Could have been taken offline before by DBA or cleaned up by SMON. Action: Check the status of rollback segment in undo$ or dba_rollback_segs to make sure the rollback segment is actually online. ORA-01628: max # extents (string) reached for rollback segment string Cause: An attempt was made to extend a rollback segment that was already at the MAXEXTENTS value. Action: If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, raise this value. ORA-01629: max # extents (string) reached saving undo for tablespace string Cause: Save undo for the offline tablespace at max extents Action: Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied . ORA-01630: max # extents (string) reached in temp segment in tablespace string Cause: A temp segment tried to extend past max extents. Action: If maxextents for the tablespace is less than the the system maximum, you can raise that. Otherwise, raise pctincrease for the tablespace ORA-01631: max # extents (string) reached in table string.string Cause: A table tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-01632: max # extents (string) reached in index string.string Cause: An index tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01633: Real Application Clusters Option needed for this operation Cause: System doesn"t have Real Application Clusters configured Action: Obtain Real Application Clusters option ORA-01634: rollback segment number "string" is about to go offline Cause: The rollback segment specified was marked to go offline by DBA. Action: Bring the rollback segment online first. ORA-01635: rollback segment #string specified not available Cause: (same as 1545) Action: (same as 1545) ORA-01636: rollback segment "string" is already online Cause: The instance is trying to online an already online RS Action: none ORA-01637: rollback segment "string" is being used by another instance (#string) Cause: The instance is trying to online a RS already in use by another instance Action: none ORA-01638: parameter string does not allow ORACLE version string to mount cluster database Cause: The recovery compatible parameter is set too low to allow this software version to mount in cluster database mode. Action: 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. ORA-01639: instance string has no thread assigned to it Cause: There is no mapping from instance to thread for this instance in the control file. Action: Make sure that this instance has a thread assigned to it by adding logfiles to this instance or by starting the instance with an existing thread which will automatically create a mapping. ORA-01640: cannot make tablespace read only with active transactions Cause: Attempting 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. Action: 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. ORA-01641: tablespace "string" is not online - cannot add data file Cause: Attempting to add a datafile to a tablespace that has been set to read only or offline. Action: Make the tablespace online and read write then add the datafile. ORA-01642: begin backup not needed for read only tablespace "string" Cause: Attempting to begin or end a backup for a tablespace that has been set to read only. Action: Take the backup without any begin or end commands. The files are not being modified so the backup will be consistent. ORA-01643: system tablespace can not be made read only Cause: Attempting to set the system tablespace to read only. The system tablespace must remain read write for database operation. Action: Leave system tablespace read write. ORA-01644: tablespace "string" is already read only Cause: Attempting to make tablespace read only that is already read only. Action: Leave tablespace read only, or make read write then make read only again. ORA-01645: previous attempt to make read write is half complete Cause: A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be useable after a resetlogs if its files are offline. Action: Repeat the command to make the tablespace read write. ORA-01646: tablespace "string" is not read only - cannot make read write Cause: Attempting to make a tablespace read write that is not read only. It may be either online or offline. Action: Leave tablespace read write. ORA-01647: tablespace "string" is read only, cannot allocate space in it Cause: Tried to allocate space in a read only tablespace Action: Create the object in another tablespace ORA-01648: log string is the current log of disabled instance string (thread string) Cause: 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 can not be cleared or archived. Action: Complete the thread enable by issuing the enable command again. ORA-01649: operation not allowed with a backup control file Cause: An attempt is being made to perform a command that does not make sense when the control file is a restored backup. Action: Wait until after the database has been opened and try again. ORA-01650: unable to extend rollback segment string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for a rollback segment in the tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01651: unable to extend save undo segment by string for tablespace string Cause: Failed to allocate an extent of the required number of blocks for saving undo entries for the indicated offline tablespace. Action: Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied. ORA-01652: unable to extend temp segment by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for a temporary segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01653: unable to extend table string.string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for a table segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01654: unable to extend index string.string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01655: unable to extend cluster string.string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for a cluster segment in tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01656: max # extents (string) reached in cluster string.string Cause: A cluster tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-01657: invalid SHRINK option value Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-01658: unable to create INITIAL extent for segment in tablespace string Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created. Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL ORA-01659: unable to allocate MINEXTENTS beyond string in tablespace string Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created. Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE ORA-01660: tablespace "string" is already permanent Cause: Attempting to make tablespace permanent that is already permanent. Action: Leave tablespace permanent. ORA-01661: tablespace "string" is already temporary Cause: Attempting to make tablespace temporary that is already temporary. Action: Leave tablespace permanent. ORA-01662: tablespace "string" is non-empty and cannot be made temporary Cause: Tried to convert a non-empty tablespace to a temporary tablespace Action: To drop all the objects in the tablespace. ORA-01663: the contents of tablespace "string" is constantly changing Cause: The contents of the tablespace is always changing between PERMANENT and TEMPORARY. Action: To decide what the tablespace contents should be and stay with it. ORA-01664: Transaction which has expanded the Sort Segment has aborted Cause: Internal Error. Action: Contact Oracle Support. ORA-01665: control file is not a standby control file Cause: Attempting to mount, recover or activate a standby database without a standby control file. Action: Create a standby control file before attempting to use the database as a standby database. ORA-01666: control file is for a standby database Cause: Attempting to mount, recover, or open a standby database without the appropriate command option to designate a standby database. Action: Use the standby option or appropriate commands, or mount with the primary control file. ORA-01667: cannot add any more tablespaces: limit of string exceeded Cause: There is no more room in the control file for adding tablespaces. Action: Resize the control file or drop other tablespaces. ORA-01668: standby database requires DROP option for offline of data file Cause: Attempting 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. Action: Specify the DROP option or leave the file online. ORA-01669: standby database control file not consistent Cause: Attempting to activate a standby database with a control file that has not been recovered to the same point as the data files. Most likely the control file was just copied from the primary database and has not been used for recovery. Action: Recover the standby database until all the files are consistent. ORA-01670: new datafile string needed for standby database recovery Cause: Standby database recovery noticed that a file was added to the primary database, but is not available on the standby. Action: 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. ORA-01671: control file is a backup, cannot make a standby control file Cause: The currently mounted control file is a backup control file, and attempting to create a control file for a standby database. Action: Complete any needed recovery and open the database with the resetlogs option. ORA-01672: control file may be missing files or have extra ones Cause: Attempting 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. Action: Open the database, then retry the operation. ORA-01673: data file string has not been identified Cause: This data file 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 can not create a standby control file. Action: 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. ORA-01674: data file string is an old incarnation rather than current file Cause: 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. Action: Rebuild the control file using CREATE CONTROLFILE, and give the correct file. ORA-01675: max_commit_propagation_delay inconsistent with other instances Cause: The max_commit_propagation_delay INIT.ORA parameter is inconsistent with those in other instances. Action: Make sure all instances have the same max_commit_propagation_delay. ORA-01676: standby file name convert of "string" exceeds maximum length of string Cause: 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. Action: Change initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name. ORA-01677: standby file name convert parameters differ from other instance Cause: 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. Action: Change initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match other instances. ORA-01678: parameter string must be pairs of pattern and replacement strings Cause: The initialization parameter does not have 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. Action: Specify even number of strings for the parameter, or omit the parameter. ORA-01679: database must be mounted EXCLUSIVE and not open to activate Cause: An attempt to activate a standby database was made when the database was not mounted EXCLUSIVE or was already open. Action: Mount the database EXCLUSIVE and retry the ACTIVATE command. ORA-01680: unable to extend LOB segment by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for a LOB segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01681: max # extents (string) reached in LOB segment in tablespace string Cause: A LOB segment tried to extend past max extents. Action: If maxextents for the tablespace is less than the the system maximum, you can raise that. Otherwise, raise pctincrease for the tablespace ORA-01682: read-only DB cannot allocate temporary space in tablespace string Cause: Temporary space (usually for sorting) could not be allocated in either main storage or a tempfile. 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. Action: 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. ORA-01683: unable to extend index string.string partition string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for index segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01684: max # extents (string) reached in table string.string partition string Cause: A table tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-01685: max # extents (string) reached in index string.string partition string Cause: An index tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01686: max # files (string) reached for the tablespace string Cause: The number of files for a given tablespace has reached its maximum value Action: Resize existing files in the tablespace, or partition the objects among multiple tablespaces, or move some objects to a different tablespace. ORA-01687: specified logging attribute for tablespace "string" is same as the existing Cause: Attempting to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute Action: Change the specified logging attribute ORA-01688: unable to extend table string.string partition string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for table segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01689: syntax error in clause "string" of string Cause: There was a syntax in the INIT.ORA parameter. Action: Fix the syntax error and restart the instance. ORA-01690: sort area size too small Cause: sort area size too small to fit two records in memory Action: increase sort_area_size ORA-01691: unable to extend lob segment string.string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01692: unable to extend lob segment string.string partition string by string in tablespace string Cause: Failed to allocate an extent of the required number of blocks for LOB segment in the tablespace indicated. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-01693: max # extents (string) reached in lob segment string.string Cause: A LOB segment tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01694: max # extents (string) reached in lob segment string.string partition string Cause: A LOB segment tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-01695: error converting rollback segment string to version 8.0.2 Cause: Version 8.0.1 database may not have shutdown cleanly Action: May have to reload the 8.0.1 database and shutdown cleanly ORA-01696: control file is not a clone control file Cause: Attempting 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. Action: Mount without the clone option or use a backup control file and shutdown the other instances before mounting as a clone. ORA-01697: control file is for a clone database Cause: Attempting to mount a clone database without the appropriate command option to designate a clone database. Action: Use the clone option or appropriate commands, or mount with the primary control file. ORA-01698: a clone database may only have SYSTEM rollback segment online Cause: Attempting to online a rollback segment in a clone database. Action: Do not use this command. ORA-01699: tablespace "string" is being imported for point in time recovery Cause: Attempting to online a tablespace or begin another point in time import while a point in time import is already in progress Action: Wait until the import complets ORA-01704: string literal too long Cause: The string literal is longer than 4000 characters. Action: Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables. ORA-01715: UNIQUE may not be used with a cluster index Cause: An attempt was made to create a cluster index with the UNIQUE attribute. Action: Remove UNIQUE from the CREATE INDEX statement. ORA-01716: NOSORT may not be used with a cluster index Cause: An attempt was made to create a cluster index using the NOSORT option. Action: Remove NOSORT from the CREATE INDEX statement. ORA-01718: BY ACCESS | SESSION clause not allowed for NOAUDIT Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement. Action: Remove BY ACCESS | SESSION. ORA-01719: outer join operator (+) not allowed in operand of OR or IN Cause: An outer join appears in an or clause. Action: 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)). ORA-01720: grant option does not exist for "string.string" Cause: A grant was being performed on a view and the grant option was not present for an underlying object. Action: Obtain the grant option on all underlying objects of the view. ORA-01721: USERENV(COMMITSCN) invoked more than once in a transaction Cause: The USERENV("COMMITSCN") function can only be used once in a transaction. Action: Re-write the transactioin to use USERENV("COMMITSCN") only once ORA-01724: floating point precision is out of range (1 to 126) Cause: Self-evident. Action: Self-evident. ORA-01725: USERENV("COMMITSCN") not allowed here Cause: 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. Action: Correct the use of the function. ORA-01734: illegal parameters - EXTENT MIN higher than EXTENT MAX Cause: A wrong value is specified for the parameter. Action: Correct the parameter and reissue the statement. ORA-01742: comment not terminated properly Cause: The indicated comment or hint begun with the /* token did not have the terminating */. Action: Properly terminate the comment or hint with a */. ORA-01743: only pure functions can be indexed Cause: The indexed function uses SYSDATE or the user environment. Action: 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. ORA-01751: Invalid dump undo option Cause: An invalid option is specified in the ALTER DUMP UNDO command. Action: Correct and reissue the command. ORA-01752: cannot delete from view without exactly one key-preserved table Cause: The deleted table either had no key perserved 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. Action: Redefine the view or delete it from the underlying base tables. ORA-01754: a table may contain only one column of type LONG Cause: 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. Action: Remove the LONG column currently in the table by using the ALTER TABLE command. ORA-01755: Must specify an extent number or block number Cause: Expecting an extent or block number but something else was specified. Action: Correct the error and reissue the command. ORA-01757: Must specify an object number Cause: Expecting an object number but something else was specified. Action: Correct the error and reissue the command. ORA-01761: DML operation does not map to a unique table in the join Cause: 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. Action: Change the join specification. ORA-01763: update or delete involves outer joined table Cause: 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. Action: Change the join specification. ORA-01764: new update value of join is not guaranteed to be unique Cause: 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. Action: Change the join specification. ORA-01769: duplicate CLUSTER option specifications Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option. Action: Remove the extra CLUSTER option. ORA-01771: illegal option for a clustered table Cause: 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. These options may only be specified for the cluster itself. Action: Remove the illegal option(s). ORA-01772: Must specify a value for LEVEL Cause: Expecting the value of LEVEL but something else was specified. Action: Correct the error and reissue the command. ORA-01774: Dump undo option specified more than once Cause: The same option for ALTER DUMP UNDO was specified twice. Action: Remove the redundant options and reissue the command. ORA-01776: cannot modify more than one base table through a join view Cause: Columns belonging to more than one underlying table were either inserted into or updated. Action: Phrase the statement as two or more separate statements. ORA-01779: cannot modify a column which maps to a non key-preserved table Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table. Action: Modify the underlying base tables directly. ORA-01781: UNRECOVERABLE cannot be specified without AS SELECT Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause. Action: Do not specify UNRECOVERABLE. ORA-01782: UNRECOVERABLE cannot be specified for a cluster or clustered table Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE. Action: Do not specify UNRECOVERABLE. ORA-01783: only one RECOVERABLE or UNRECOVERABLE clause may be specified Cause: 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. Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement. ORA-01784: RECOVERABLE cannot be specified with database media recovery disabled Cause: 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. Action: Do not specify RECOVERABLE, or restart the database with media recovery enabled. ORA-01792: maximum number of columns in a table or view is 1000 Cause: 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. Action: 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: 1) If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns; 2) Reduce the number of columns in the command and resubmit. ORA-01799: a column may not be outer-joined to a subquery Cause: (+) () is not allowed. Action: Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case. ORA-01804: failure to initialize timezone information Cause: The timezone information file was not properly read. Action: Please contact Oracle Customer Support. ORA-01841: (full) year must be between -4713 and +9999, and not be 0 Cause: Illegal year entered Action: Input year in the specified range ORA-01854: julian date must be between 1 and 5373484 Cause: An invalid Julian date was entered. Action: Enter a valid Julian date between 1 and 5373484. ORA-01858: a non-numeric character was found where a numeric was expected Cause: 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. Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation. ORA-01859: a non-alphabetic character was found where an alphabetic was expected Cause: 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. Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation. ORA-01861: literal does not match format string Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading whitespace). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra whitespace. Action: Correct the format string to match the literal. ORA-01862: the numeric value does not match the length of the format item Cause: 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. Action: Correct the input date or turn off the FX or FM format specifier in the format string. ORA-01863: the year is not supported for the current calendar Cause: The year is not supported for the current calendar. Action: Please check the documentation to find out what years are supported for the current calendar. ORA-01864: the date is out of range for the current calendar Cause: Your calendar doesn"t extend to the specified date. Action: Specify a date which is legal for this calendar. ORA-01865: not a valid era Cause: Era input does not match a known era. Action: Provide a valid era on input. ORA-01866: the datetime class is invalid Cause: This is an internal error. Action: Please contact Oracle Worldwide Support. ORA-01867: the interval is invalid Cause: The character string you specified is not a valid interval. Action: Please specify a valid interval. ORA-01868: the leading precision of the interval is too small Cause: The leading precision of the interval is too small to store the specified interval. Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision. ORA-01870: the intervals or datetimes are not mutually comparable Cause: The intervals or datetimes are not mutually comparable. Action: Specify a pair of intervals or datetimes that are mutually comparable. ORA-01871: the number of seconds must be less than 60 Cause: The number of seconds specified was greater than 59. Action: Specify a value for seconds that is 59 or smaller. ORA-01873: the leading precision of the interval is too small Cause: The leading precision of the interval is too small to store the specified interval. Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision. ORA-01874: time zone hour must be between -12 and 14 Cause: The time zone hour specified was not in the valid range. Action: Specify a time zone hour between -12 and 14. ORA-01875: time zone minute must be between -59 and 59 Cause: The time zone minute specified was not in the valid range. Action: Specify a time zone minute between -59 and 59. ORA-01876: year must be at least -4713 Cause: The specified year was not in range. Action: Specify a year that is greater than or equal to -4713. ORA-01877: string is too long for internal buffer Cause: This is an internal error. Action: Please contact Oracle Worldwide Support. ORA-01878: specified field not found in datetime or interval Cause: The specified field was not found in the datetime or interval. Action: Make sure that the specified field is in the datetime or interval. ORA-01879: the hh25 field must be between 0 and 24 Cause: The specified hh25 field was not in the valid range. Action: Specify an hh25 field between 0 and 24. ORA-01880: the fractional seconds must be between 0 and 999999999 Cause: The specified fractional seconds were not in the valid range. Action: Specify a value for fractional seconds between 0 and 999999999. ORA-01881: timezone region id number is invalid Cause: The region id referenced an invalid region. Action: Please contact Oracle Customer Support. ORA-01882: timezone region string not found Cause: The specified region name was not found. Action: Please contact Oracle Customer Support. ORA-01883: overlap was disabled during a region transition Cause: The region was changing state and the overlap flag was disabled. Action: Please contact Oracle Customer Support. ORA-01890: NLS error detected Cause: An NLS error was detected. Action: Look for additional error messages and take appropriate action. If there are no additional errors, call Oracle Worldwide Support. ORA-01891: Datetime/Interval internal error Cause: Internal error. Action: Please contact Oracle Worldwide Support. ORA-01898: too many precision specifiers Cause: While trying to truncate or round dates, extra data was found in the date format picture Action: Check the syntax of the date format picture and retry. ORA-01900: LOGFILE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01901: ROLLBACK keyword expected Cause: keyword missing Action: supply missing keyword ORA-01902: SEGMENT keyword expected Cause: keyword missing Action: supply missing keyword ORA-01903: EVENTS keyword expected Cause: keyword missing Action: supply missing keyword ORA-01904: DATAFILE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01905: STORAGE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01906: BACKUP keyword expected Cause: keyword missing Action: supply missing keyword ORA-01907: TABLESPACE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01908: EXISTS keyword expected Cause: keyword missing Action: supply missing keyword ORA-01909: REUSE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01910: TABLES keyword expected Cause: keyword missing Action: supply missing keyword ORA-01911: CONTENTS keyword expected Cause: keyword missing Action: supply missing keyword ORA-01912: ROW keyword expected Cause: keyword missing Action: supply missing keyword ORA-01913: EXCLUSIVE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01914: invalid auditing option for sequence numbers Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option that is not legal for sequence numbers. Action: The following options may not be used for sequence numbers and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, EXECUTE ORA-01915: invalid auditing option for views Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is not legal for views. Action: The following options may not be used for views and should be removed: ALTER, INDEX, REFERENCES, EXECUTE ORA-01916: keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected Cause: An expected keyword was not used for datafile/tempfile clause Action: Use correct syntax. ORA-01917: user or role "string" does not exist Cause: There is not a user or role by that name. Action: Re-specify the name. ORA-01918: user "string" does not exist Cause: User does not exist in the system. Action: Verify the user name is correct. ORA-01919: role "string" does not exist Cause: Role by that name does not exist. Action: Verify you are using the correct role name. ORA-01920: user name "string" conflicts with another user or role name Cause: There is already a user or role with that name. Action: Specify a different user name. ORA-01921: role name "string" conflicts with another user or role name Cause: There is already a user or role with that name. Action: Specify a different role name. ORA-01922: CASCADE must be specified to drop "string" Cause: Cascade is required to remove this user from the system. The user own"s object which will need to be dropped. Action: Specify cascade. ORA-01923: CASCADE aborted, objects locked by another user Cause: Cannot drop the user"s objects; someone has them locked. Action: Use the lock monitor to determine who has the objects locked. ORA-01924: role "string" not granted or does not exist Cause: Set role can only be performed with roles granted directly to your account. (e.g. a sub-role cannot be enabled) Action: Don"t try to set the role. ORA-01925: maximum of string enabled roles exceeded Cause: The INIT.ORA parameter "max_enabled_roles" has been exceeded. Action: Increase max_enabled_roles and warm start the database. ORA-01926: cannot GRANT to a role WITH GRANT OPTION Cause: Role cannot have a privilege with the grant option. Action: Perform the grant without the grant option. ORA-01927: cannot REVOKE privileges you did not grant Cause: You can only revoke privileges you granted. Action: Don"t revoke these privileges. ORA-01928: GRANT option not granted for all privileges Cause: In order to grant a privilege, you must first have the privilege with the grant option. Action: Obtain the privilege with the grant option and try again. ORA-01929: no privileges to GRANT Cause: "ALL" was specified but the user doesn"t have any privileges with the grant option. Action: Don"t grant privileges on that object. ORA-01930: auditing the object is not supported Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited. Action: Don"t attempt to AUDIT the object. ORA-01931: cannot grant string to a role Cause: UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER privilege cannot be granted to a role. Action: Grant privilege directly to the user. ORA-01932: ADMIN option not granted for role "string" Cause: The operation requires the admin option on the role. Action: Obtain the grant option and re-try. ORA-01933: cannot create a stored object using privileges from a role Cause: An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles. Action: Grant the privileges required to the user directly. ORA-01934: circular role grant detected Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself. Action: Do not perform the grant. ORA-01935: missing user or role name Cause: A user or role name was expected. Action: Specify a user or role name. ORA-01936: cannot specify owner when creating users or roles Cause: Users and roles do not have owners. Action: Don"t specify an owner. ORA-01937: missing or invalid role name Cause: A valid role name was expected. Action: Specify a valid role name. ORA-01938: IDENTIFIED BY must be specified for CREATE USER Cause: Cannot create a user without specifying a password or "IDENTIFIED EXTERNALLY". Action: Specify one of the password clauses. ORA-01939: only the ADMIN OPTION can be specified Cause: System privileges and Roles can only be granted with the admin option. The grant option cannot be used with these privileges. Action: Specify the admin option. ORA-01940: cannot drop a user that is currently connected Cause: Attempt was made to drop a user that is currently logged in. Action: Make sure user is logged off, then repeat command. ORA-01941: SEQUENCE keyword expected Cause: keyword missing Action: supply missing keyword ORA-01942: IDENTIFIED BY and EXTERNALLY cannot both be specified Cause: A user cannot be specified to have and not have a password. Action: Specify only one of the options. ORA-01943: IDENTIFIED BY already specified Cause: The identified clause has been given twice. Action: Use only one identified by clause. ORA-01944: IDENTIFIED EXTERNALLY already specified Cause: The identified externaly clause has been given twice. Action: Use only one identified clause. ORA-01945: DEFAULT ROLE[S] already specified Cause: The default roles clause has been given twice. Action: Use only on default role clause. ORA-01946: DEFAULT TABLESPACE already specified Cause: The default tablespace clause has been given twice. Action: Use only one default tablespace clause. ORA-01947: TEMPORARY TABLESPACE already specified Cause: The temporary tablespace clause has been given twice. Action: Use only one temporary tablespace clause. ORA-01948: identifier"s name length (string) exceeds maximum (string) Cause: A name has been specified that is too long. For example, dbms_session.is_role_enabled() specifies a role name that is too long. Action: Change the application or command to use a correct identifier. ORA-01949: ROLE keyword expected Cause: The role keyword is required here. Action: Specify the role keyword. ORA-01950: no privileges on tablespace "string" Cause: User does not have privileges to allocate an extent in the specified tablespace. Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace. ORA-01951: ROLE "string" not granted to "string" Cause: The role you tried to revoke was not granted to the user. Action: Don"t try to revoke a privilege which is not granted. ORA-01952: system privileges not granted to "string" Cause: A system privilege you tried to revoke was not granted to the user. Action: Make sure the privileges you are trying to revoke are granted. ORA-01953: command no longer valid, see ALTER USER Cause: The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality Action: Use the alter user command instead. ORA-01954: DEFAULT ROLE clause not valid for CREATE USER Cause: Default roles cannot be specified for create user. Action: Grant and alter the user"s default roles after creating the user. ORA-01955: DEFAULT ROLE "string" not granted to user Cause: 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. Action: Grant the role to the user. ORA-01956: invalid command when OS_ROLES are being used Cause: This command cannot be used when the INIT.ORA parameter OS_ROLES is TRUE. Action: Grant the role to the user in the operating system. ORA-01967: invalid option for CREATE CONTROLFILE Cause: An invalid CREATE CONTROLFILE option is present. Action: Specify only valid CREATE CONTROLFILE options. ORA-01968: Only specify RESETLOGS or NORESETLOGS once Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. ORA-01969: You must specify RESETLOGS or NORESETLOGS Cause: Missing a RESETLOGS or a NORESETLOGS Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once. ORA-01970: You must specify a database name for CREATE CONTROLFILE Cause: Missing a database name Action: Retype CREATE CONTROLFILE command with the DATABASE keyword. ORA-01973: Missing change number Cause: Keyword "CHANGE" found but change number not specified. Action: Fix command line and resubmit ORA-01974: Illegal archive option Cause: Not a valid option to the "ALTER SYSTEM ARCHIVE" command Action: none ORA-01977: Missing thread number Cause: Keyword "THREAD" found but thread number not specified. Action: Fix command line and resubmit ORA-01978: Missing sequence number Cause: Keyword "SEQUENCE" found but sequence number not specified. Action: Fix command line and resubmit ORA-01979: missing or invalid password for role "string" Cause: An attempt was made to enable a role without giving Action: Use the "identified by" clause in set role to specify the correct password. ORA-01980: error during OS ROLE initialization Cause: An OS error occurred while loading a users OS ROLES. Action: Check the OS error. ORA-01981: CASCADE CONSTRAINTS must be specified to perform this revoke Cause: During this revoke some foreign key contraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified. Action: Remove the constraints or specify CASCADE CONSTRAINTS. ORA-01982: invalid auditing option for tables Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables. Action: The following options may not be used for tables and should be removed: REFERENCES, EXECUTE ORA-01983: invalid auditing option for DEFAULT Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT. Action: The following options may not be used for DEFAULT and should be removed: REFERENCES ORA-01984: invalid auditing option for procedures/packages/functions Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions. Action: The following options may not be used for procedures, packages, and functions and should be removed: all but EXECUTE ORA-01985: cannot create user as LICENSE_MAX_USERS parameter exceeded Cause: Maximum users in the database license limit exceeded. Action: Increase license limit. ORA-01986: OPTIMIZER_GOAL is obsolete Cause: An obsolete parameter, OPTIMIZER_GOAL, was referenced. Action: Use the OPTIMIZER_MODE parameter. ORA-01987: client os username is too long Cause: A client"s os username is too long for the os logon to succeed. Action: Use a shorter os username. ORA-01988: remote os logon is not allowed Cause: Remote os login attempted when not allowed. Action: Use a local client, or use the remote_os_authent system parameter to turn on remote os logon. ORA-01989: role "string" not authorized by operating system Cause: The os role does not exist, is not granted to you, or you did not provide the correct password. Action: Re-attempt the SET ROLE with a valid os role and password, if necessary. ORA-01994: GRANT failed: password file missing or disabled Cause: The operation failed either because the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the password file was missing. Action: Create the password file using the orapwd tool and set the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE. ORA-01999: password file cannot be updated in SHARED mode Cause: The operation failed because the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE was set to SHARED. Action: Set the INIT.ORA parameter to EXCLUSIVE. ORA-02001: user SYS is not permitted to create indexes with freelist groups Cause: user tried to create an index while running with sys authorization. Action: none ORA-02004: security violation Cause: This error code is never returned to a user. It is used as a value for column, audit_trail.returncode, to signal that a security violation occurred. Action: None. ORA-02007: can"t use ALLOCATE or DEALLOCATE options with REBUILD Cause: Allocate or deallocate storage and rebuild index are not compatible. Action: Choose one or the other. ORA-02009: the size specified for a file must not be zero Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification. Action: Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause. ORA-02020: too many database links in use Cause: The current session has exceeded the INIT.ORA open_links maximum. Action: 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. ORA-02021: DDL operations are not allowed on a remote database Cause: An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname ...". Action: To alter the remote database structure, you must connect to the remote database with the appropriate privileges. ORA-02022: remote statement has unoptimized view with remote object Cause: The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database. Action: Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote. ORA-02024: database link not found Cause: Database link to be dropped is not found in dictionary Action: Correct the database link name ORA-02025: all tables in the SQL statement must be at the remote database Cause: The user"s SQL statement references tables from multiple databases. The remote database is not Oracle V7 or above, and can perform updates only if it can reference all tables in the SQL statement. Action: none ORA-02026: missing LINK keyword Cause: keyword missing Action: supply missing keyword ORA-02027: multi-row UPDATE of LONG column is not supported Cause: 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. Action: You may only update a single row with such a bind variable. ORA-02028: fetching an exact number of rows is not supported by the server Cause: The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side. Action: Connect to a valid server or do not use an exact fetch. ORA-02029: missing FILE keyword Cause: keyword missing Action: supply missing keyword ORA-02030: can only select from fixed tables/views Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table/view. Action: You may only select rows from fixed tables/views. ORA-02031: no ROWID for fixed tables or for external-organized tables Cause: An attempt is being made to access rowid from a fixed table or from a external-organized table. Action: Do not access ROWID from a fixed table or from a external-organized table. ORA-02032: clustered tables cannot be used before the cluster index is built Cause: User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created. Action: Create the cluster index. ORA-02033: a cluster index for this cluster already exists Cause: A cluster index already exists for the cluster. Action: None. ORA-02034: speed bind not permitted Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system. Action: none ORA-02035: illegal bundled operation combination Cause: User requested that the UPI bundled execution call perform an an illegal combination of operations. Action: See documentation for legal operation combinations. ORA-02036: too many variables to describe with automatic cursor open Cause: User requested that the UPI bundled execution call perform automatic cursor open and close on a describe operation. There were too many select-list items or bind variables to do this. Action: open and close cursor explicitly ORA-02037: uninitialized speed bind storage Cause: User attempted a UPI bundled execution call containing a standalone execute operation without first performing a UPI bundled execution call containing a bind operation. Action: perform a UPI bundled execution call with bind before performing a bundled execution call with execute ORA-02038: define is not allowed for array type Cause: User attempted to define a select list variable of type "array". Arrays may only serve as host bind variables. Action: none ORA-02039: bind by value is not allowed for array type Cause: User attempted to bind an array host variable by value. Arrays may only be bound by reference. Action: none ORA-02040: remote database string does not support two-phase commit Cause: the database was potentially updated but does not support prepare to commit (as determined by its logon transaction traits). The transaction was rolled back. Action: Do not attempt to update the remote database unless it is the only database updated in one transaction. ORA-02041: client database did not begin a transaction Cause: internal error Action: contact support ORA-02042: too many distributed transactions Cause: the distributed transaction table was full because too many distributed transactions were active. Action: Run fewer transactions. If you are sure you don"t have too many concurrent distributed transactions, this indicates an internal error and support should be notified. Instance shutdown/restart would be a work-around. ORA-02043: must end current transaction before executing string Cause: a transaction is in progress and one of the following commands commands is issued: COMMIT FORCE, ROLLBACK FORCE, or ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode. Action: COMMIT or ROLLBACK the current transaction and resubmit command. ORA-02044: transaction manager login denied: transaction in progress Cause: a remote transaction manager tried to log in while a distributed transaction is in progress. Action: end the current transaction (this is a protocol error from a remote transaction manager) ORA-02045: too many local sessions participating in global transaction Cause: too many sessions at this site for this transaction. Action: use an existing link so another session need not be created. ORA-02046: distributed transaction already begun Cause: internal error or error in external transaction manager. A server session received a begin_tran RPC before finishing with a previous distributed tran. Action: none ORA-02047: cannot join the distributed transaction in progress Cause: Either a transaction is in progress against a remote database that does not fully support two phase commit, and an update is attempted on another database, or updates are pending and and an attempt is made to update a different database that does not fully support two phase commit. Action: complete the current transaction and then resubmit the update request. ORA-02048: attempt to begin distributed transaction without logging on Cause: client program must issue a distributed transaction login. Action: contact support. ORA-02049: timeout: distributed transaction waiting for lock Cause: exceeded INIT.ORA distributed_lock_timeout seconds waiting for lock. Action: treat as a deadlock ORA-02050: transaction string rolled back, some remote DBs may be in-doubt Cause: network or remote failure in 2PC. Action: Notify operations; remote DBs will automatically re-sync when the failure is repaired. ORA-02051: another session in same transaction failed Cause: a session at the same site with same global transaction ID failed. Action: none necessary, transaction automatically recovered. ORA-02052: remote transaction failure at string Cause: error in remote transaction at given DBLINK Action: retry ORA-02053: transaction string committed, some remote DBs may be in-doubt Cause: network or remote failure in 2PC. Action: Notify operations; remote DBs will automatically re-sync when the failure is repaired. ORA-02054: transaction string in-doubt Cause: network or remote failure in 2PC. Action: Notify operations; DBs will automatically re-sync when the failure is repaired. Monitor pending_trans$ for final outcome. ORA-02055: distributed update operation failed; rollback required Cause: a failure during distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent, the transaction must roll back to a savepoint or entirely Action: rollback to a savepoint or rollback transaction and resubmit ORA-02056: 2PC: string: bad two-phase command number string from string Cause: two-phase commit protocol error. Action: recovery of transaction attempted. Monitor pending_trans$ table to ensure correct resolution. Contact support. ORA-02057: 2PC: string: bad two-phase recovery state number string from string Cause: internal error in two-phase recovery protocol Action: contact support ORA-02058: no prepared transaction found with ID string Cause: no transaction with local_tran_id or global_tran_id found in the pending_trans$ table in prepared state. Action: check the pending_trans$ table. ORA-02059: ORA-2PC-CRASH-TEST-string in commit comment Cause: This is a special comment used to test the two phase commit. Action: Don"t use this special comment (%s a number 1-10) ORA-02060: select for update specified a join of distributed tables Cause: tables in a join with the for update clause must reside at the same DB. Action: none ORA-02061: lock table specified list of distributed tables Cause: tables in a lock table statement must reside at the same DB. Action: issue multiple lock table commands. ORA-02062: distributed recovery received DBID string, expected string Cause: a database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different DB mounted. Action: restore link definition or remote database. ORA-02063: preceding stringstring from stringstring Cause: an Oracle error was received from a remote database link. Action: refer to the preceding error message(s) ORA-02064: distributed operation not supported Cause: One of the following unsupported operations was attempted: 1. array execute of a remote update with a subquery that references a dblink, or 2. an update of a long column with bind variable and an update of a second column with a subquery that both references a dblink and a bind variable, or 3. a commit is issued in a coordinated session from an RPC procedure call with OUT parameters or function call. Action: simplify remote update statement ORA-02065: illegal option for ALTER SYSTEM Cause: The option specified for ALTER SYSTEM is not supported Action: refer to the user manual for option supported ORA-02066: missing or invalid DISPATCHERS text Cause: A character string literal was expected, but not found, following ALTER SYSTEM SET DISPATCHERS Action: place the string literal containing the dispatcher"s specification after ALTER SYSTEM SET DISPATCHERS ORA-02067: transaction or savepoint rollback required Cause: 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. Action: rollback to a previous savepoint or rollback the transaction and resubmit. ORA-02068: following severe error from stringstring Cause: A severe error (disconnect, fatal Oracle error) received from the indicated database link. See following error text. Action: Contact the remote system administrator. ORA-02069: global_names parameter must be set to TRUE for this operation Cause: 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 Action: Issue alter session set global_names = true if possible ORA-02070: database stringstring does not support string in this context Cause: The remote database does not support the named capability in the context in which it is used. Action: Simplify the SQL statement. ORA-02071: error initializing capabilities for remote database string Cause: Could not load a remote-specified capability table. Action: Contact support for the remote SQL*Connect product. ORA-02072: distributed database network protocol mismatch Cause: This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example. Action: Upgrade the older release. ORA-02073: sequence numbers not supported in remote updates Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables. Action: none ORA-02074: cannot string in a distributed transaction Cause: A commit or rollback was attempted from session other than the parent of a distributed transaction. Action: Only commit or rollback from the parent session. ORA-02075: another instance changed state of transaction string Cause: A commit force or rollback force was issued from a session in another instance. Action: Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction. ORA-02076: sequence not co-located with updated table or long column Cause: all referenced sequences must be co-located with the table with the long column. Action: none ORA-02077: selects of long columns must be from co-located tables Cause: if a select returns long columns from multiple tables, all the tables must be co-located Action: none ORA-02079: no new sessions may join a committing distributed transaction Cause: 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. Action: Contact support. ORA-02080: database link is in use Cause: a transaction is active or a cursor is open on the database link given in the alter session close database link command. Action: commit or rollback, and close all cursors ORA-02081: database link is not open Cause: dblink given is not currently open. Action: none ORA-02082: a loopback database link must have a connection qualifier Cause: attempt to create a database link with the same name as the current database. Action: a loopback database link needs a trailing qualifier, e.g. MYDB.DEV.US.ORACLE.COM@INST1 - the "@INST1" is the qualifier ORA-02083: database name has illegal character "string" Cause: supplied database name can contain only A-Z, 0-9, "_", "#", "$" "." and "@" characters. Action: none ORA-02084: database name is missing a component Cause: supplied database name cannot contain a leading ".", trailing "." or "@", or two "." or "@" in a row. Action: none ORA-02085: database link string connects to string Cause: a database link connected to a database with a different name. The connection is rejected. Action: create a database link with the same name as the database it connects to, or set global_names=false. ORA-02086: database (link) name is too long Cause: database/database link name can have at most 128 characters. Action: none ORA-02087: object locked by another process in same transaction Cause: 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. Action: 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, simply use the same session to access the object. ORA-02088: distributed database option not installed Cause: Remote and distributed updates and transactions are a separately priced option in ORACLE V7. Action: none ORA-02089: COMMIT is not allowed in a subordinate session Cause: COMMIT was issued in a session that is not the two-phase commit global coordinator. Action: Issue commit at the global coordinator only. ORA-02090: network error: attempted callback+passthru Cause: internal error. Action: none ORA-02091: transaction rolled back Cause: Also see error 2092. If the transaction is aborted at a remote site then you will only see 2091; if aborted at host then you will see 2092 and 2091. Action: Add rollback segment and retry the transaction. ORA-02092: out of transaction table slots for distributed transaction Cause: 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. Action: Add a rollback segment and retry the transaction. ORA-02093: TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string) Cause: Value of parameter specified is greater than allowed on this port. Action: Use default or reduce it to less than max. ORA-02094: replication option not installed Cause: The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable. Action: 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. ORA-02095: specified initialization parameter cannot be modified Cause: The specified initialization parameter is not modifiable Action: none ORA-02096: specified initialization parameter is not modifiable with this option Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command. Action: Check the DBA guide for information about under what scope the parameter may be modified ORA-02097: parameter cannot be modified because specified value is invalid Cause: Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter. Action: Check the DBA guide for range of acceptable values for this parameter. ORA-02098: error parsing index-table reference (:I) Cause: An incorrect index-table (:I) syntax was encountered. Action: This syntax is for oracle internal use only. ORA-02140 to ORA-04099ORA-02140: invalid tablespace name Cause: An identifier does not follow ALTER TABLESPACE. Action: Specify a tablespace name following ALTER TABLESPACE. ORA-02141: invalid OFFLINE option Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE. Action: The user must either specify no option following OFFLINE or one of the options NORMAL or IMMEDIATE. ORA-02142: missing or invalid ALTER TABLESPACE option Cause: A valid option was not present. Action: Use one of the valid options: add, rename, default, online, offline, read only, read write, begin, end, no, force, retention guarantee and retention noguarantee. ORA-02143: invalid STORAGE option Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause. Action: Specify only valid options. ORA-02144: no option specified for ALTER CLUSTER Cause: No ALTER CLUSTER options are specified. Action: Specify one or more of the following options: pctfree, pctused, size, storage. ORA-02145: missing STORAGE option Cause: No STORAGE options were specified following STORAGE ( Action: Specify one or more STORAGE option between the parentheses. ORA-02146: SHARED specified multiple times Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times. Action: Only specify the SHARED option once. ORA-02147: conflicting SHARED/EXCLUSIVE options Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement. Action: Specify SHARED or EXCLUSIVE, but not both. ORA-02148: EXCLUSIVE specified multiple times Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times. Action: Only specify the EXCLUSIVE option once. ORA-02149: Specified partition does not exist Cause: Partition not found for the object. Action: Retry with correct partition name. ORA-02150: invalid new tablespace name Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO statement was invalid. Action: Retry with a valid new tablespace name. ORA-02151: invalid tablespace name: string Cause: Oracle cannot create a tablespace whose name starts with "_$deleted$". Action: Try a different tablespace name. ORA-02152: Invalid ALTER TABLESPACE ... RENAME option Cause: An option other than DATAFILE or TO follows by ALTER TABLESPACE ... RENAME. Action: The user must specify either DATAFILE or TO following ALTER TABLESPACE ... RENAME. ORA-02153: invalid VALUES password string Cause: An encoded password string does not follow the VALUES clause. Action: Place a proper encoded password string after the VALUES clause. ORA-02154: a tablespace with the name "string" is found Cause: An attempt to rename a tablespace to a new name failed because the new name is already used by some other tablespace. Action: Retry with a different new name. ORA-02155: invalid DEFAULT tablespace identifier Cause: An identifier does not follow DEFAULT TABLESPACE. Action: Place a tablespace name after DEFAULT TABLESPACE. ORA-02156: invalid TEMPORARY tablespace identifier Cause: An identifier does not follow TEMPORARY TABLESPACE. Action: Place a tablespace name after TEMPORARY TABLESPACE. ORA-02157: no options specified for ALTER USER Cause: No options were specified. Action: Specify at least one ALTER USER option. ORA-02158: invalid CREATE INDEX option Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified. Action: Choose one of the valid CREATE INDEX options. ORA-02159: installed DLM does not support releasable locking mode Cause: The parameter file specified gc_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available. Action: Specify configuration parameters that do not require the additional function. ORA-02160: index-organized table can not contain columns of type LONG Cause: A column of type LONG defined for index-organized table. Action: Do not use columns of type LONG in index-organized tables. ORA-02161: invalid value for MAXLOGFILES Cause: A number does not follow MAXLOGFILES. Action: Specify a number after MAXLOGFILES. ORA-02162: invalid value for MAXDATAFILES Cause: A number does not follow MAXDATAFILES. Action: Specify a number after MAXDATAFILES. ORA-02163: invalid value for FREELIST GROUPS Cause: A number does not follow FREELIST GROUPS. Action: Specify a number after FREELIST GROUPS. ORA-02164: DATAFILE clause specified more than once Cause: The CREATE DATABASE command contains more than one DATAFILE clause. Action: Specify at most one DATAFILE clause. ORA-02165: invalid option for CREATE DATABASE Cause: An invalid CREATE DATABASE option is present. Action: Specify only valid CREATE DATABASE options. ORA-02166: ARCHIVELOG and NOARCHIVELOG specified Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement. Action: Specify at most one of these two options. ORA-02167: LOGFILE clause specified more than once Cause: The CREATE DATABASE command contains more than one LOGFILE clause. Action: Specify at most one LOGFILE clause. ORA-02168: invalid value for FREELISTS Cause: A number does not follow FREELISTS Action: Specify a number after FREELISTS ORA-02169: FREELISTS storage option not allowed Cause: The user attempted to specify the FREELISTS storage option. This option may only be specified during create table or create index. Action: Remove these options and retry the statement. ORA-02170: FREELIST GROUPS storage option not allowed Cause: The user attempted to specify the FREELIST GROUPS storage option. This option may only be specified during create table and when allow_freelist_groups INIT.ORA is specified. Action: Remove this option and retry the statement or set the allow_freelist_groups INIT.ORA parameter. ORA-02171: invalid value for MAXLOGHISTORY Cause: A number does not follow MAXLOGHISTORY Action: Specify a number after MAXLOGHISTORY ORA-02172: The PUBLIC keyword is not appropriate for a disable thread Cause: The PUBLIC keyword was specified for a disable. Action: Remove the keyword and resubmit. ORA-02173: invalid option for DROP TABLESPACE Cause: Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS. Action: Place nothing or only INCLUDING CONTENTS after the tablespace name. ORA-02174: Missing required thread number Cause: Must specify thread number after THREAD keyword Action: none ORA-02175: invalid rollback segment name Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT. Action: Place the segment name following ROLLBACK SEGMENT. ORA-02176: invalid option for CREATE ROLLBACK SEGMENT Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement. Action: Specify one of the valid options: TABLESPACE and STORAGE. ORA-02177: Missing required group number Cause: Must specify group number after GROUP keyword Action: none ORA-02178: correct syntax is: SET TRANSACTION READ { ONLY | WRITE } Cause: There is a syntax error in the user"s statement. Action: Correct the syntax as indicated. ORA-02179: valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED } Cause: There is a syntax error in the user"s statement. Action: Correct the syntax as indicated. ORA-02180: invalid option for CREATE TABLESPACE Cause: An invalid option appeared. Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE, FORCE, RETENTION. ORA-02181: invalid option to ROLLBACK WORK Cause: A token other than TO follows ROLLBACK [WORK]. Action: Place nothing or TO SAVEPOINT after ROLLBACK [WORK]. ORA-02182: savepoint name expected Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT]. Action: Place a savepoint name following TO [SAVEPOINT]. ORA-02183: valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED } Cause: There is a syntax error in the user"s statement. Action: Correct the syntax as indicated. ORA-02184: resource quotas are not allowed in REVOKE Cause: In a revoke statement, a resource quota was specified. Action: Specify resource privilege without the quota. ORA-02185: a token other than WORK follows COMMIT Cause: A token other than WORK follows COMMIT. Action: Place either nothing or WORK after COMMIT. ORA-02186: tablespace resource privilege may not appear with other privileges Cause: An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked. Action: Use a separate grant or revoke statement for the resource quota privilege. ORA-02187: invalid quota specification Cause: In a grant or revoke statement, the user attempted to grant a tablespace quota above the upper limit. Action: Grant a smaller tablespace quota. ORA-02188: Cannot enable instance publicly Cause: An attempt was made to publicly enable a thread associated with an instance. Action: Leave out the PUBLIC keyword. ORA-02189: ON required Cause: In a grant or revoke statement, the user specified a tablespace quota but did not follow it with the ON clause. Action: Specify the tablespace on which the quota is to be applied with the ON clause. ORA-02190: keyword TABLES expected Cause: The keyword TABLES is expected following DROP CLUSTER INCLUDING. Action: Place TABLES after INCLUDING. ORA-02191: correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT Cause: There is a syntax error in the user"s statement. Action: Correct the syntax as indicated. ORA-02192: PCTINCREASE not allowed for rollback segment storage clauses Cause: pctincrease was specified in a create or alter rollback segment Action: reissue statement without the pctincrease clause ORA-02194: event specification syntax error string (minor error string) near "string" Cause: There is a syntax error in an event specification. Action: Fix the error. ORA-02195: Attempt to create string object in a string tablespace Cause: The object type is inconsistent with a tablespace contents. Action: Create an object in a different tablespace, or change the user defaults. ORA-02196: PERMANENT/TEMPORARY option already specified Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once. Action: none ORA-02197: file list already specified Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified. Action: Merge the DATAFILE/TEMPFILE clauses into a single clause. ORA-02198: ONLINE/OFFLINE option already specified Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once. Action: Specify at most one of ONLINE or OFFLINE. ORA-02199: missing DATAFILE/TEMPFILE clause Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause. Action: Specify a DATAFILE/TEMPFILE clause. ORA-02200: WITH GRANT OPTION not allowed for PUBLIC Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION. Action: Remove the WITH GRANT OPTION clause. ORA-02201: sequence not allowed here Cause: An attempt was made to reference a sequence in a from-list. Action: A sequence can only be referenced in a select-list. ORA-02202: no more tables permitted in this cluster Cause: An attempt was made to create a table in a cluster which already contains 32 tables. Action: Up to 32 tables may be stored per cluster. ORA-02203: INITIAL storage options not allowed Cause: The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. These options may only be specified when the object is created. Action: Remove these options and retry the statement. ORA-02204: ALTER, INDEX and EXECUTE not allowed for views Cause: An attempt was made to grant or revoke an invalid privilege on a view. Action: Do not attempt to grant or revoke any of ALTER, INDEX, or EXECUTE privileges on views. ORA-02205: only SELECT and ALTER privileges are valid for sequences Cause: An attempt was made to grant or revoke an invalid privilege on a sequence. Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE, REFERENCES or EXECUTE privilege on sequences. ORA-02206: duplicate INITRANS option specification Cause: INITRANS is specified more than once. Action: Specify INITRANS at most once. ORA-02207: invalid INITRANS option value Cause: The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value. Action: Choose a valid INITRANS value. ORA-02208: duplicate MAXTRANS option specification Cause: MAXTRANS is specified more than once. Action: Specify MAXTRANS at most once. ORA-02209: invalid MAXTRANS option value Cause: The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value. Action: Choose a valid MAXTRANS value. ORA-02210: no options specified for ALTER TABLE Cause: No ALTER TABLE option was specified. Action: Specify at least one alter table option. ORA-02211: invalid value for PCTFREE or PCTUSED Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100. Action: Choose an appropriate value for the option. ORA-02212: duplicate PCTFREE option specification Cause: PCTFREE option specified more than once. Action: Specify PCTFREE at most once. ORA-02213: duplicate PCTUSED option specification Cause: PCTUSED option specified more than once. Action: Specify PCTUSED at most once. ORA-02214: duplicate BACKUP option specification Cause: The BACKUP option to ALTER TABLE is specified more than once. Action: Specify the option at most once. ORA-02215: duplicate tablespace name clause Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement. Action: Specify at most one TABLESPACE clause. ORA-02216: tablespace name expected Cause: A tablespace name is not present where required by the syntax for one of the following statements: CREATE/DROP TABLESPACE, CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT. Action: Specify a tablespace name where required by the syntax. ORA-02217: duplicate storage option specification Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once. Action: Specify all storage options at most once. ORA-02218: invalid INITIAL storage option value Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-02219: invalid NEXT storage option value Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-02220: invalid MINEXTENTS storage option value Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS. Action: Specify an appropriate value. ORA-02221: invalid MAXEXTENTS storage option value Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS. Action: Specify an appropriate value. ORA-02222: invalid PCTINCREASE storage option value Cause: The specified value must be a positive integer. Action: Specify an appropriate value. ORA-02223: invalid OPTIMAL storage option value Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-02224: EXECUTE privilege not allowed for tables Cause: An attempt was made to grant or revoke an invalid privilege on a table. Action: Do not attempt to grant or revoke EXECUTE privilege on tables. ORA-02225: only EXECUTE and DEBUG privileges are valid for procedures Cause: An attempt was made to grant or revoke an invalid privilege on a procedure, function or package. Action: Do not attempt to grant or revoke any privilege besides EXECUTE or DEBUG on procedures, functions or packages. ORA-02226: invalid MAXEXTENTS value (max allowed: string) Cause: The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment. Action: Specify a smaller value. ORA-02227: invalid cluster name Cause: A cluster name of the form [ . ] is expected but not present. Action: Enter an appropriate cluster name. ORA-02228: duplicate SIZE specification Cause: The SIZE option is specified more than once. Action: Specify the SIZE option at most once. ORA-02229: invalid SIZE option value Cause: The specified value must be an integer number of bytes. Action: Specify an appropriate value. ORA-02230: invalid ALTER CLUSTER option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement. Action: Specify only legal options. ORA-02231: missing or invalid option to ALTER DATABASE Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement. Action: Specify only legal options. ORA-02232: invalid MOUNT mode Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement. Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT. ORA-02233: invalid CLOSE mode Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement. Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE. ORA-02234: changes to this table are already logged Cause: the log table to be added is a duplicate of another Action: Don"t add this change log to the system; check that the replication product"s system tables are consistent ORA-02235: this table logs changes to another table already Cause: the table to be altered is already a change log for another table Action: Don"t log changes to the specified base table to this table; check that the replication product"s system tables are consistent ORA-02236: invalid file name Cause: A character string literal was not used in the filename list of a LOGFILE, DATAFILE, or RENAME clause. Action: Use correct syntax. ORA-02237: invalid file size Cause: A non-integer value was specified in the SIZE or RESIZE clause. Action: Use correct syntax. ORA-02238: filename lists have different numbers of files Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the the number of existing filenames does not equal the number of new filenames. Action: Make sure there is a new filename to correspond to each existing filename. ORA-02239: there are objects which reference this sequence Cause: the sequence to be dropped is still referenced Action: Make sure the sequence name is correct, or drop the referencing constraint/object ORA-02240: invalid value for OBJNO or TABNO Cause: A number does not follow either OBJNO or TABNO. Action: Specify a number after OBJNO or TABNO. ORA-02241: must of form EXTENTS (FILE BLOCK SIZE , ...) Cause: bad extent storage clause Action: respecify ORA-02242: no options specified for ALTER INDEX Cause: No options specified. Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE. ORA-02243: invalid ALTER INDEX or ALTER MATERIALIZED VIEW option Cause: An option other than INITRANS, MAXTRANS,or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER MATERIALIZED VIEW statement. Action: Specify only legal options. ORA-02244: invalid ALTER ROLLBACK SEGMENT option Cause: The STORAGE option is expected but not found. Action: Specify the STORAGE option. ORA-02245: invalid ROLLBACK SEGMENT name Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT. Action: Place a rollback segment name following SEGMENT. ORA-02246: missing EVENTS text Cause: A character string literal was expected, but not found, following ALTER SESSION SET EVENTS. Action: Place the string literal containing the events text after EVENTS. ORA-02247: no option specified for ALTER SESSION Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION. Action: Place the SET EVENTS option after ALTER SESSION. ORA-02248: invalid option for ALTER SESSION Cause: Obvious. Action: see SQL Language Manual for legal options. ORA-02249: missing or invalid value for MAXLOGMEMBERS Cause: A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the port-specific maximum number of log file members. Action: Specify a valid number after MAXLOGMEMBERS. ORA-02250: missing or invalid constraint name Cause: The constraint name is missing or invalid. Action: Specify a valid identifier name for the constraint name. ORA-02251: subquery not allowed here Cause: Subquery is not allowed here in the statement. Action: Remove the subquery from the statement. ORA-02252: check constraint condition not properly ended Cause: The specified search condition for the check constraint is not properly ended. Action: End the condition properly. ORA-02253: constraint specification not allowed here Cause: Constraint specification is not allowed here in the statement. Action: Remove the constraint specification from the statement. ORA-02254: DEFAULT not allowed here Cause: Default value expression is not allowed for the column here in the statement. Action: Remove the default value expression from the statement. ORA-02255: obsolete 7.1.5 Cause: Was that defaults must not conflict with not null constraints Action: none ORA-02256: number of referencing columns must match referenced columns Cause: The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list. Action: Make sure that the referencing columns match the referenced columns. ORA-02257: maximum number of columns exceeded Cause: The number of columns in the key list exceeds the maximum number. Action: Reduce the number columns in the list. ORA-02258: duplicate or conflicting NULL and/or NOT NULL specifications Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02259: duplicate UNIQUE/PRIMARY KEY specifications Cause: Self-evident. Action: Remove the duplicate specification. ORA-02260: table can have only one primary key Cause: Self-evident. Action: Remove the extra primary key. ORA-02261: such unique or primary key already exists in the table Cause: Self-evident. Action: Remove the extra key. ORA-02262: ORA-string occurs while type-checking column default value expression Cause: New column datatype causes type-checking error for existing column default value expression. Action: Remove the default value expression or don"t alter the column datatype. ORA-02263: need to specify the datatype for this column Cause: The required datatype for the column is missing. Action: Specify the required datatype. ORA-02264: name already used by an existing constraint Cause: The specified constraint name has to be unique. Action: Specify a unique constraint name for the constraint. ORA-02265: cannot derive the datatype of the referencing column Cause: The datatype of the referenced column is not defined as yet. Action: Make sure that the datatype of the referenced column is defined before referencing it. ORA-02266: unique/primary keys in table referenced by enabled foreign keys Cause: An attempt was made to truncate a table with unique or primary keys referenced by foreign keys enabled in another table. Other operations not allowed are dropping/truncating a partition of a partitioned table or an ALTER TABLE EXCHANGE PARTITION. Action: Before performing the above operations the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; ORA-02267: column type incompatible with referenced column type Cause: The datatype of the referencing column is incompatible with the Action: Select a compatible datatype for the referencing column. ORA-02268: referenced table does not have a primary key Cause: The referenced table does not have a primary key. Action: Specify explicitly the referenced table unique key. ORA-02269: key column cannot be of LONG datatype Cause: Self-evident. Action: Change the datatype of the column, or remove the column from the key. ORA-02270: no matching unique or primary key for this column-list Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a column-list for which there is no matching unique or primary key constraint in the referenced table. Action: Find the correct column names using the ALL_CONS_COLUMNS catalog view ORA-02271: table does not have such constraint Cause: Self-evident. Action: Make sure the specified constraint name is correct. ORA-02272: constrained column cannot be of LONG datatype Cause: Self-evident. Action: Change the datatype of the column, or remove the constraint on the column. ORA-02273: this unique/primary key is referenced by some foreign keys Cause: Self-evident. Action: Remove all references to the key before the key is to be dropped. ORA-02274: duplicate referential constraint specifications Cause: Self-evident. Action: Remove the duplicate specification. ORA-02275: such a referential constraint already exists in the table Cause: Self-evident. Action: Remove the extra constraint. ORA-02276: default value type incompatible with column type Cause: The type of the evaluated default expression is incompatible with the datatype of the column. Action: Change the type of the column, or modify the default expression. ORA-02277: invalid sequence name Cause: The specified sequence name is not a valid identifier name. Action: Specify a valid identifier name for the sequence name. ORA-02278: duplicate or conflicting MAXVALUE/NOMAXVALUE specifications Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02279: duplicate or conflicting MINVALUE/NOMINVALUE specifications Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02280: duplicate or conflicting CYCLE/NOCYCLE specifications Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02281: duplicate or conflicting CACHE/NOCACHE specifications Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02282: duplicate or conflicting ORDER/NOORDER specifications Cause: Self-evident. Action: Remove the duplicate or conflicting specification. ORA-02283: cannot alter starting sequence number Cause: Self-evident. Action: Don"t alter it. ORA-02284: duplicate INCREMENT BY specifications Cause: Self-evident. Action: Remove the duplicate specification. ORA-02285: duplicate START WITH specifications Cause: Self-evident. Action: Remove the duplicate specification. ORA-02286: no options specified for ALTER SEQUENCE Cause: Self-evident. Action: The statement is meaningless without any options. ORA-02287: sequence number not allowed here Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate here in the statement. Action: Remove the sequence number. ORA-02288: invalid OPEN mode Cause: A token other than RESETLOGS appears following ALTER DATABASE OPEN. Action: Either nothing or RESETLOGS should be placed following OPEN. ORA-02289: sequence does not exist Cause: The specified sequence does not exist, or the user does not have the required privilege to perform this operation. Action: Make sure the sequence name is correct, and that you have the right to perform the desired operation on this sequence. ORA-02290: check constraint (string.string) violated Cause: The values being inserted do not satisfy the named check constraint. Action: do not insert values that violate the constraint. ORA-02291: integrity constraint (string.string) violated - parent key not found Cause: A foreign key value has no matching primary key value. Action: Delete the foreign key or add a matching primary key. ORA-02292: integrity constraint (string.string) violated - child record found Cause: attempted to delete a parent key value that had a foreign key dependency. Action: delete dependencies first then parent or disable constraint. ORA-02293: cannot validate (string.string) - check constraint violated Cause: an alter table operation tried to validate a check constraint to a populated table that had nocomplying values. Action: Obvious ORA-02294: cannot enable (string.string) - constraint changed during validation Cause: While one DDL statement was attempting to enable this constraint, another DDL changed this same constraint. Action: Try again, with only one DDL changing the constraint this time. ORA-02295: found more than one enable/disable clause for constraint Cause: a create or alter table specified more than one enable and/or disable clause for a given constraint. Action: only one enable or disable may be specified for a given constraint. ORA-02296: cannot enable (string.string) - null values found Cause: an alter table enable constraint failed because the table contains values that do not satisfy the constraint. Action: Obvious ORA-02297: cannot disable constraint (string.string) - dependencies exist Cause: an alter table disable constraint failed becuase the table has foriegn keys that are dpendent on this constraint. Action: Either disable the foreign key constraints or use disable cascade ORA-02298: cannot validate (string.string) - parent keys not found Cause: an alter table validating constraint failed because the table has orphaned child records. Action: Obvious ORA-02299: cannot validate (string.string) - duplicate keys found Cause: an alter table validating constraint failed because the table has duplicate key values. Action: Obvious ORA-02300: invalid value for OIDGENERATORS Cause: A number was not specified for the value of OIDGENERATORS. Action: Specify a number for OIDGENERATORS. ORA-02301: maximum number of OIDGENERATORS is 255 Cause: A number greater than 255 was specified for the value of OIDGENERATORS. Action: Make sure the number specified for OIDGENERATORS does not exceed 255. ORA-02302: invalid or missing type name Cause: An invalid or missing type name was entered in a statement. Action: Enter a valid type name in the statement and retry the operation. ORA-02303: cannot drop or replace a type with type or table dependents Cause: An attempt was made to drop or replace a type that has dependents. There could be a substitutable column of a supertype of the type being dropped. Action: Drop all type(s) and table(s) depending on the type, then retry the operation using the VALIDATE option, or use the FORCE option. ORA-02304: invalid object identifier literal Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either: - not a string of 32 hexadecimal characters - an object identifier that already identifies an existing object - an object identifier different from the original object identifier already assigned to the type Action: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation. ORA-02305: only EXECUTE, DEBUG, and UNDER privileges are valid for types Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE, DEBUG, or UNDER) on a type. Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on types. ORA-02306: cannot create a type that already has valid dependent(s) Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist). Action: Drop the dependents first before creating the type, or do not create the type. ORA-02307: cannot alter with REPLACE option a type that is not valid Cause: An attempt was made to ALTER with REPLACE option a type that is not valid. Action: Use the CREATE OR REPLACE TYPE command to modify the type. ORA-02308: invalid option string for object type column Cause: An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column. Action: Remove the invalid option from column specification and retry the operation. ORA-02309: atomic NULL violation Cause: An attempt was made to acess the attributes of a NULL object instance. Action: Ensure that the object instance is non-NULL before accessing. ORA-02310: exceeded maximum number of allowable columns in table Cause: The attributes in the object type column exceeded the maximum number of columns allowed in a table. Action: Specify fewer attributes for the object type and retry the operation. ORA-02311: cannot alter with COMPILE option a valid type with type or table dependents Cause: An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents. Action: No need to perform this operation. ORA-02313: object type contains non-queryable type string attribute Cause: The specified object type contains a nested attribute whose type is non-queryable. Action: Use an object type with queryable attribute types. ORA-02314: illegal use of type constructor Cause: The statement contains an illegal use of a type constructor. Action: Refer to the SQL Reference manual for the correct statement syntax. ORA-02315: incorrect number of arguments for default constructor Cause: The number of arguments specified for the default constructor doesn"t match the number of attributes of the object type. Action: Specify the correct number of arguments for the default constructor and retry the operation. ORA-02320: failure in creating storage table for nested table column string Cause: An error occurred while creating the storage table for the specified nested table column. Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support. ORA-02322: failure in accessing storage table of the nested table column Cause: An error occured while performing DML on the storage table of the nested table column. Action: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Support. ORA-02324: more than one column in the SELECT list of THE subquery Cause: More than one column was selected in the THE subquery. Action: Specify only one column in the SELECT list of the THE subquery and retry the operation. ORA-02327: cannot create index on expression with datatype string Cause: An attempt was made to create an index on a non-indexable expression. Action: Change the column datatype or do not create the index on an expression whose datatype is one of VARRAY, nested table, object, LOB, or REF. ORA-02329: column of datatype string cannot be unique or a primary key Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF. Action: Change the column datatype or remove the constraint. Then retry the operation. ORA-02330: datatype specification not allowed Cause: An attempt was made to specify the data type in the column constraint specification of an object table. Action: Remove data type specification and retry the operation. ORA-02331: cannot create constraint on column of datatype string Cause: An attempt was made to create a constraint on a column posessing a non-constrainable datatype -- VARRAY, nested table, object, LOB, FILE, or REF. Action: Change the column datatype, or remove the constraint. ORA-02332: cannot create index on attributes of this column Cause: An attempt was made to create an index on an attributes of an object type column. Action: Do not specify the index on the attribute. ORA-02333: cannot create constraints on attributes of this column Cause: An attempt was made to create a constraint on an attribute of an object type column. Action: Remove the constraint or change the object type. ORA-02334: cannot infer type for column Cause: A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column. Action: Declare a datatype for the column. ORA-02335: invalid datatype for cluster column Cause: An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE. Action: Remove the CLUSTER column or change the datatype of the column. ORA-02336: column attribute cannot be accessed Cause: An attempt was made to extract an attribute of an object type column. Action: Change the object type for the column and retry the operation. ORA-02337: not an object type column Cause: An attempt was made to use dotted notation on a non-ADT column; that is, "a.b.c" where "a" is not an object type. Action: Either change the column type to an object type or do not perform this operation. ORA-02338: missing or invalid column constraint specification Cause: A column constraint was not specified. Action: Remove the column specification or specify a column constraint. Then retry the operation. ORA-02339: invalid column specification Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column. Action: Remove the PACKED or UNPACKED keyword in the column specification and retry the operation. ORA-02340: invalid column specification Cause: An attempt was made to specify an UNPACKED column within a packed table. Action: Remove the UNPACKED keyword in the column specification. ORA-02342: replacement type has compilation errors Cause: The use of the ALTER...REPLACE statement on a valid type caused a compilation error. Action: Use the ALTER...REPLACE statement to replace the type with a valid type which does not cause compilation errors. ORA-02344: cannot revoke execute on a type with table dependents Cause: An attempt was made to revoke execute on a type that has dependents. Action: Drop all table(s) depending on the type, then retry the operation, or use the FORCE option. ORA-02345: cannot create a view with column based on CURSOR operator Cause: A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement. Action: Remove the CURSOR operator and replace it with the CAST operator. ORA-02347: cannot grant privileges on columns of an object table Cause: An attempt was made to grant privileges on the columns of an object table. Action: none ORA-02348: cannot create VARRAY column with embedded LOB Cause: An attempt was made to create a column of a VARRAY type which has an embedded LOB attribute. The LOB could be an attribute of a subtype of the declared type of VARRAY"s element. Action: Remove offending attribute from type. If it is a subtype attribute then declare the VARRAY column NOT SUBSTITUTABLE. ORA-02349: invalid user-defined type - type is incomplete Cause: An attempt was made to use an incomplete type definition as a column or table datatype. Action: Complete the type definition and retry the operation. ORA-02351: internal error: string Cause: An unexpected error condition was detected. Action: Call Oracle Customer Support. ORA-02352: file truncated error Cause: A truncated file was used for the load operation. Action: Verify unload operation completed successfully. ORA-02353: files not from the same unload operation Cause: Files used for the load operation were not from the same unload operation. Action: Verify the files used are from the same unload operation. ORA-02354: error in exporting/importing data string Cause: An error has occurred in a stream export or import operation. This message will be followed by another message giving more details about this error. Action: See export/import documentation for an explanation of the second error message. ORA-02355: error opening file: string Cause: An attempt to open the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved. ORA-02356: The database is out of space. The load cannot continue Cause: The load was discontinued due to space exhaustion in the database. Action: Add space for the specified table. ORA-02357: no valid dump files Cause: None of the dump files for the operation were valid. A minimum of one valid dump file is expected. Action: Check that the dump files exist and are openable. ORA-02358: internal error fetching attribute string Cause: An attempt to fetch information about an internal object failed. Action: Contact Oracle Support Services. ORA-02359: internal error setting attribute string Cause: An attempt to set information about an internal object failed. Action: Contact Oracle Support Services. ORA-02360: fatal error during data export/import initialization Cause: An unexpected error occurred during initialization for data export/import. Action: Contact Oracle Support Services. ORA-02361: error while attempting to allocate number bytes of memory Cause: d by insufficient memory. Action: Reconnect to the instance and retry the operation. ORA-02362: error closing file: string Cause: An attempt to close the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved. ORA-02363: error reading from file: string Cause: An attempt to read from the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved. ORA-02364: error writing to file: string Cause: An attempt to write to the specified file for data export/import failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if ORA-02365: error seeking in file: string Cause: An attempt to seek to the specified position in file failed. Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if ORA-02366: The following index(es) on table string were processed: Cause: The table had some indexes which were loaded if there were no errors. Action: none. ORA-02367: file truncated error in string Cause: A truncated or incomplete file was used for the load operation. Action: Verify unload operation completed successfully. ORA-02368: file string is not valid for this load operation Cause: The specified file could not be used for this load because the internal header and/or table metadata of this file were not consistent with those of the first file listed in the DUMPFILE clause. Action: Verify all the files listed in the DUMPFILE clause are from the same unload operation. ORA-02371: Loader must be at least version string.string.string.string.string for direct path Cause: The loader being used is incompatible with this version of the kernel. Action: Upgrade your loader to at least the specified version or use the conventional path. ORA-02372: data for row: string Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error. Action: None. This is only an informational message. ORA-02373: Error parsing insert statement for table string. Cause: self-evident. Action: Check the error given below this one. ORA-02374: conversion error loading table string.string Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row. Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported. ORA-02375: conversion error loading table string.string partition string Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row. Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported. ORA-02376: invalid or redundant resource Cause: a create, or alter profile command which names a resource not yet defined, or try to specify same resource twice. Action: define resource first ORA-02377: invalid resource limit Cause: specifying limit of 0 Action: specify limit > 0 ORA-02379: profile string already exists Cause: Try to create a profile which already exist Action: none ORA-02380: profile string does not exist Cause: Try to assign a user to a non-existant profile Action: none ORA-02381: cannot drop PUBLIC_DEFAULT profile Cause: Try to drop PUBLIC_DEFAULT profile Action: none ORA-02383: illegal cost factor Cause: Negative or UNLIMITED cost for this resourc Action: none ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user prfile. Action: End one or more concurrent sessions or ask the database administrator to increase the SESSION_PER_USER limit of the user profile. ORA-02396: exceeded maximum idle time, please connect again Cause: as stated Action: none ORA-02397: exceeded PRIVATE_SGA limit, you are being logged off Cause: Only when using TP monitor Action: expand limit ORA-02398: exceeded procedure space usage Cause: Stored procedured used up too much space in SYSTEM Tablespace Action: Use less stored procedure ORA-02399: exceeded maximum connect time, you are being logged off Cause: As stated Action: none ORA-02401: cannot EXPLAIN view owned by another user Cause: The view specified in the SQL statement belongs to another user and cannot be explained. Action: Create a view with the same definition that belongs to current user. ORA-02402: PLAN_TABLE not found Cause: The table used by EXPLAIN to store row source information does not exist in the current schema. Action: Create a plan table in the current schema or use the INTO clause of the statement to put the results of the explain command in an existing plan table. ORA-02403: plan table does not have correct format Cause: The explicit plan table does not have the appropriate field definitions. Action: Redefine the plan table to have the appropriate field definitions. ORA-02404: specified plan table not found Cause: The specified plan table does cannot be found. Action: Create the specified plan table or use an existing plan table. ORA-02405: invalid sql plan object provided Cause: The user provided a NULL, empty, or malformed object of type SQL_PLAN_TABLE_TYPE Action: Provide a new, properly formed object to the function ORA-02420: missing schema authorization clause Cause: the AUTHORIZATION clause is missing from a create schema statement. Action: Preceed the schema authorization identifier with the AUTHORIZATION keyword. ORA-02421: missing or invalid schema authorization identifier Cause: the schema name is missing or is incorrect in an authorization clause of a create schema statement. Action: If the name is present, it must be the same as the current schema. ORA-02422: missing or invalid schema element Cause: A statement other than a create table, create view, or grant privilege appears in a create schema statement. Action: Self-evident. ORA-02423: schema name does not match schema authorization identifier Cause: a table definition with a schema name prepended to the table name does not match the schema name provided in the authorization clause of a create schema statement. Action: make sure the schema names match. ORA-02424: potential circular view references or unknown referenced tables Cause: the create schema statement contains views that depend on other views in the containing create schema statement or they contain references to unknown tables. Action: create the dependent views in a separate create schema statement and make sure all referenced tables are either defined in the create schema statement or exist outside the statement. ORA-02425: create table failed Cause: a create table statement failed in the create schema statement. Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message. ORA-02426: privilege grant failed Cause: a grant privilege statement failed inthe create schema statement. Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message. ORA-02427: create view failed Cause: a create view statement failed in the create schema statement. Action: the cause for failure will be presented below this error message. Follow appropriate action(s) as suggested by the subsequent error message. ORA-02428: could not add foreign key reference Cause: could not add a foreign key reference because of error in declaration. Either referenced table does not exist or table does not have an unique key. Action: make sure referenced table exists and/or has unique key ORA-02429: cannot drop index used for enforcement of unique/primary key Cause: user attempted to drop an index that is being used as the enforcement mechanism for unique or primary key. Action: drop the constraint instead of the index. ORA-02430: cannot enable constraint (string) - no such constraint Cause: the named constraint does not exist for this table. Action: Obvious ORA-02431: cannot disable constraint (string) - no such constraint Cause: the named constraint does not exist for this table. Action: Obvious ORA-02432: cannot enable primary key - primary key not defined for table Cause: Attempted to enable a primary key that is not defined for the table. Action: Need to add a primary key definition for the table. ORA-02433: cannot disable primary key - primary key not defined for table Cause: Attempted to disable a primary key tht is not defined for the table. Action: None ORA-02434: cannot enable unique(string) - unique key not defined for table Cause: attempted to enable a unique key that is not defined for the table. Action: None ORA-02435: cannot disable unique(string) - unique key not defined for table Cause: attempted to disable a unique key that is not deined for the table. Action: None ORA-02436: date or system variable wrongly specified in CHECK constraint Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century. Action: Completely specify the date constant or system variable. Setting the event 10149 allows constraints like "a1 > "10-MAY-96"", which a bug permitted to be created before version 8. ORA-02437: cannot validate (string.string) - primary key violated Cause: attempted to validate a primary key with duplicate values or null values. Action: remove the duplicates and null values before enabling a primary key. ORA-02438: Column check constraint cannot reference other columns Cause: attempted to define a column check constraint that references another column. Action: define it as a table check constriant. ORA-02439: Unique index on a deferrable constraint is not allowed Cause: attempted to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns. Action: Drop the index on the constraint columns or make the constraint not deferrable. ORA-02440: Create as select with referential constraints not allowed Cause: create table foo (... ref. con. ...) as select ...; Action: Create the table as select, then alter the table to add the constraints afterwards. ORA-02441: Cannot drop nonexistent primary key Cause: alter table drop primary key - primary key does not exist. Action: None ORA-02442: Cannot drop nonexistent unique key Cause: alter table drop unique () - unique specification does not exist. Action: make sure column list for unique constraint is correct. ORA-02443: Cannot drop constraint - nonexistent constraint Cause: alter table drop constraint Action: make sure you supply correct constraint name. ORA-02444: Cannot resolve referenced object in referential constraints Cause: attempted to define foreign key referencing an object which cannot be resolved to a base table reference Action: referential constraints can only be defined on objects which can be resolve to base table reference ORA-02445: Exceptions table not found Cause: the explicity or implicity declared exceptions table does not exist. Action: Create the table then issue the enable command again. ORA-02446: CREATE TABLE ... AS SELECT failed - check constraint violated Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement when some rows violated one or more CHECK constraints. Action: Do not select rows that violate constraints. ORA-02447: cannot defer a constraint that is not deferrable Cause: An attempt was made to defer a nondeferrable constraint Action: Drop the constraint and create a new one that is deferrable ORA-02448: constraint does not exist Cause: The named constraint does not exist Action: Stop trying to do something with a nonexistant constraint ORA-02449: unique/primary keys in table referenced by foreign keys Cause: An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table. Action: Before performing the above operations the table, drop the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; ORA-02450: Invalid hash option - missing keyword IS Cause: Missing IS keyword. Action: Specify HASH IS option. ORA-02451: duplicate HASHKEYS specification Cause: The HASHKEYS option is specified more than once. Action: Only specify the HASHKEYS option once. ORA-02452: invalid HASHKEYS option value Cause: The specified HASHKEYS option must be an integer value. Action: Specify an appropriate value. ORA-02453: duplicate HASH IS specification Cause: The HASH IS option is specified more than once. Action: only specify the HASH IS option once. ORA-02454: Number of hash keys per block (string) exceeds maximum of string Cause: The SIZE argument is too small. Action: Increase the SIZE argument. ORA-02455: The number of cluster key column must be 1 Cause: When specifing the HASH IS option, the number of key columns must be 1. Action: Either do not specify the HASH IS option or reduce the number of key columns. ORA-02456: The HASH IS column specification must be NUMBER(*,0) Cause: The column specification must specify an integer. Action: Specify the column definition as type NUMBER(precision, 0). ORA-02457: The HASH IS option must specify a valid column Cause: The HASH IS column name is not specified in the cluster definition. Action: Specify a valid column name. ORA-02458: HASHKEYS must be specified for a HASH CLUSTER Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER. Action: Specify the HASHKEYS option. ORA-02459: Hashkey value must be a positive integer Cause: The value of the hash key was not a positive number. Action: Specify a positive integer. ORA-02460: Inappropriate index operation on a hash cluster Cause: An attempt to create a cluster index was issued on a hash cluster. Action: Do not attempt to create such an index. ORA-02461: Inappropriate use of the INDEX option Cause: This option is only valid for non hash clusters. Action: Do not specify this option. ORA-02462: Duplicate INDEX option specified Cause: The INDEX option is specified more than once. Action: Only specify the INDEX option once. ORA-02463: Duplicate HASH IS option specified Cause: The HASH IS option is specified more than once. Action: Only specify the HASH IS option once. ORA-02464: Cluster definition can not be both HASH and INDEX Cause: The cluster can either be a hash or indexed cluster - not both. Action: Remove either the HASH IS or INDEX options. ORA-02465: Inappropriate use of the HASH IS option Cause: This option is only valid for clusters Action: Do not specify this option ORA-02466: The SIZE and INITRANS options cannot be altered for HASH CLUSTERS. Cause: An attempt was made to change the SIZE and INITRANS options after the hash cluster was created. Action: Do not specify this option. ORA-02467: Column referenced in expression not found in cluster definition Cause: A column in the hash is expression was not present in cluster definition. Action: Recreate the cluster and correct the error in hash expression. ORA-02468: Constant or system variable wrongly specified in expression Cause: A constant or system variable was specified in the hash expression. Action: Recreate the cluster and correct the error in hash expression. ORA-02469: Hash expression does not return an Oracle Number. Cause: Result of evaluating hash expression is not an Oracle Number. Action: Recreate the cluster and correct the error in hash expression. ORA-02470: TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression. Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions. Action: Recreate the cluster and correct the error in hash expression. ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expre\ssion. Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expression\s. Action: Recreate the cluster and remove the offending keywords. ORA-02472: PL/SQL functions not allowed in hash expressions Cause: A PL/SQL function was used in the hash expression. Action: Recreate the cluster and remove the PL/SQL function. ORA-02473: Error while evaluating the cluster"s hash expression. Cause: An error occurred while evaluating the clusters hash expression. Action: Correct the query and retry. ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string) Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed. Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause. ORA-02475: maximum cluster chain block count of string has been exceeded Cause: The number of blocks in a cluster chain exceeds the maximum number allowed. Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key. ORA-02476: can not create index due to parallel direct load on table Cause: A parallel direct load is occurring to the specified table. Action: Retry statement after load is complete. ORA-02477: can not perform parallel direct load on object string Cause: A parallel direct load is not possible because an index is is being created on the table. Action: Retry load after index creation is complete. ORA-02478: merge into base segment would overflow MAXEXTENTS limit Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger ORA-02479: error while translating file name for parallel load Cause: An invalid file name was specified to load data into. Action: Specify a valid database file. ORA-02481: Too many processes specified for events (max string) Cause: Too many processes specified than allowed per event. Action: Enter fewer processes by using ranges or wildcards if possible. ORA-02482: Syntax error in event specification (string) Cause: Illegal event string Action: Enter a legal event string ORA-02483: Syntax error in process specification (string) Cause: Illegal process string Action: Enter a legal process string ORA-02484: Invalid _trace_buffers parameter specification (string) Cause: Bad process or size in _trace_buffers INIT.ORA parameter. Action: none ORA-02485: Invalid _trace_options parameter specification (string) Cause: Bad syntax for _trace_options INIT.ORA parameter. Action: none ORA-02486: Error in writing trace file string Cause: Error occurred in creating/writing the file. Action: Check file name and make sure it is constructed properly. Also, check permissions for directories. ORA-02487: Error in converting trace data Cause: Incompatible binary trace data was specified. Action: Check the format of the input data. ORA-02488: Error encountered when accessing file [string] for trace conversion Cause: An attempt was made to open or access the trace file during a trace conversion. Action: Check the permissions for both input and output files. Also, check the file compatibility for the trace conversion. ORA-02490: missing required file size in RESIZE clause Cause: No value was specified for the RESIZE clause. Action: Use correct syntax. ORA-02491: missing required keyword ON or OFF in AUTOEXTEND clause Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause. Action: Use correct syntax. ORA-02492: missing required file block increment size in NEXT clause Cause: No value was specified for the NEXT clause. Action: Use correct syntax. ORA-02493: invalid file increment size in NEXT clause Cause: A non-integer value was used for the NEXT clause of the DATAFILE list. Action: Use correct syntax. ORA-02494: invalid or missing maximum file size in MAXSIZE clause Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value. Action: Use correct syntax. ORA-02495: cannot resize file string, tablespace string is read only Cause: An attempt was made to resize a data file in a tablespace that is read only. Action: Change the tablespace to read/write and retry the resize operation. ORA-02700: osnoraenv: error translating ORACLE_SID Cause: Two-task driver could not find the value of ORACLE_SID in the environment. Action: Make sure that the ORACLE_SID environment variable has been properly set and exported. ORA-02701: osnoraenv: error translating oracle image name Cause: ORACLE_HOME environment variable not set. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. ORA-02702: osnoraenv: error translating orapop image name Cause: ORACLE_HOME environment variable not set. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. ORA-02703: osnpopipe: pipe creation failed Cause: The pipe driver failed to create pipes for communications with the orapop process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. ORA-02704: osndopop: fork failed Cause: The two-task driver could not fork orapop. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02705: osnpol: polling of communication channel failed Cause: The pipe driver failed while polling the communications channel. Action: Contact your customer support representative. ORA-02706: osnshs: host name too long Cause: The length of your host-string specified by the TWO_TASK environment variable exceeds the ORACLE system-imposed limit. Action: Contact your customer support representative. ORA-02707: osnacx: cannot allocate context area Cause: The invoked Unix two-task driver could not allocate heap space for the context area. Action: Contact your customer support representative. ORA-02708: osnrntab: connect to host failed, unknown ORACLE_SID Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied. Action: First, check whether you have read access to oratab, and see if the desired sid is there. Add an entry to oratab for the desired sid, if necessary. ORA-02709: osnpop: pipe creation failed Cause: The pipe driver failed to create pipes for two-task communications with the oracle shadow process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. ORA-02710: osnpop: fork failed Cause: The pipe driver could not fork the oracle shadow process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02711: osnpvalid: write to validation channel failed Cause: The pipe driver failed to write to the orapop process. Action: Contact your customer support representative. ORA-02712: osnpop: malloc failed Cause: The pipe driver failed to allocate enough heap space for its context area buffers. Action: Contact your customer support representative. ORA-02713: osnprd: message receive failure Cause: The pipe driver failed to read a message from the communications channel. Action: Contact your customer support representative. ORA-02714: osnpwr: message send failure Cause: The pipe driver failed to write a message to the communications channel. Action: Contact your customer support representative. ORA-02715: osnpgetbrkmsg: message from host had incorrect message type Cause: The pipe driver received a message having an unrecognizable message type. Action: Contact your customer support representative. ORA-02716: osnpgetdatmsg: message from host had incorrect message type Cause: The Pipe driver received a message having an unrecognizable message type. Action: Contact your customer support representative. ORA-02717: osnpfs: incorrect number of bytes written Cause: The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver. Action: Contact your customer support representative. ORA-02718: osnprs: reset protocol error Cause: The two-task driver could not reset the connection. Action: Contact your customer support representative. ORA-02719: osnfop: fork failed Cause: The fast driver could not fork the oracle shadow process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-02720: osnfop: shmat failed Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer. Action: Try invoking the Fast driver later, or use the default attach address. ORA-02721: osnseminit: cannot create semaphore set Cause: The Fast driver failed to get a semaphore set. Action: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and check with your system administrator. ORA-02722: osnpui: cannot send break message to orapop Cause: The Pipe driver could not send a break message to orapop. Action: Contact your customer support representative. ORA-02723: osnpui: cannot send break signal Cause: The Pipe driver could not send a break message to the ORACLE shadow process. Action: Contact your customer support representative. ORA-02724: osnpbr: cannot send break message to orapop Cause: The Pipe driver could not send a break message to orapop. Action: Contact your customer support representative. ORA-02725: osnpbr: cannot send break signal Cause: The Pipe driver could not send a break message to the ORACLE shadow process. Action: Kill system call failed. Check errno and contact customer support. ORA-02726: osnpop: access error on oracle executable Cause: The Pipe driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. ORA-02727: osnpop: access error on orapop executable Cause: The Pipe driver could not access the orapop executable. Action: Check the permissions on the orapop executable and each component of the ORACLE_HOME/bin path. ORA-02728: osnfop: access error on oracle executable Cause: The Fast driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. ORA-02729: osncon: driver not in osntab Cause: The driver you have specified is not supported. Action: Check with your database administrator which drivers are supported. ORA-02730: osnrnf: cannot find user logon directory Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file. Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your uid and home directory are correct in the /etc/passwd file. ORA-02731: osnrnf: malloc of buffer failed Cause: The specified driver could not find enough heap space to malloc a buffer. Action: Contact your customer support representative. ORA-02732: osnrnf: cannot find a matching database alias Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet. Action: Create the alias in a file called .sqlnet in your home directory for personal use or ask your system administrator to create the alias in /etc/sqlnet for system-wide use. ORA-02733: osnsnf: database string too long Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the ORACLE system-imposed limit. Action: Contact your customer support representative. ORA-02734: osnftt: cannot reset shared memory permission Cause: The Fast driver was unable to reset shared memory permissions. Action: Contact your customer support representative. ORA-02735: osnfpm: cannot create shared memory segment Cause: The Fast driver failed to create a shared memory segment for two-task communication. Action: Check whether the system-imposed limit on shared memory identifiers has already been reached for your system. ORA-02736: osnfpm: illegal default shared memory address Cause: The Fast driver failed to establish a default shared memory address. Action: Contact your customer support representative. ORA-02737: osnpcl: cannot tell orapop to exit Cause: The Pipe driver failed to send orapop the command to exit. Action: Contact your customer support representative. ORA-02738: osnpwrtbrkmsg: incorrect number of bytes written Cause: The pipe driver apparently sent an imcomplete break message. Action: Contact your customer support representative. ORA-02739: osncon: host alias is too long Cause: The alias used for a sqlnet host is longer than 161 characters. Action: Use a shorter alias. ORA-02750: osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf Cause: The Fast driver failed to create a shared memory file for two-task communication. Action: Check the permissions on the directory ?/dbs ORA-02751: osnfsmmap: cannot map shared memory file Cause: The Fast driver failed to map a shared memory file for two-task communication. Action: Contact your customer support representative. ORA-02752: osnfsmmap: illegal shared memory address Cause: The Fast driver failed to attach shared memory at the expected location. Action: Contact your customer support representative. ORA-02753: osnfsmmap: cannot close shared memory file Cause: The Fast driver cannot close the shared memory file. Action: Contact your customer support representative. ORA-02754: osnfsmmap: cannot change shared memory inheritence Cause: The Fast driver could not alter the inheritence attributes of the shared memory. Action: Contact your customer support representative. ORA-02755: osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf Cause: The Fast driver failed to create a file for shared memory. Action: Check the permissions on the directory ?/dbs ORA-02756: osnfsmnam: name translation failure Cause: The Fast driver encountered an error translating the shared memory filename ?/dbs/ftt_.dbf. Action: Contact your customer support representative. ORA-02757: osnfop: fork_and_bind failed Cause: The Fast driver failed to fork a process onto the desired cluster and node number. Action: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If these seem valid, contact customer support. ORA-02758: Allocation of internal array failed Cause: The package was unable to allocate memory for an array because the system ran out of memory. Action: Either reclaim memory by killing other processes or reboot the machine with more memory. ORA-02759: Not enough request descriptors available Cause: All of the package"s request descriptors are in use performing other requests. Action: Either wait until enough requests are done, or shut the package down and re-initialize it with more request descriptors. ORA-02760: Client close of file failed. Cause: The client was unable to close a file after forking the servers. Action: This is a system problem - contact your System Administrator. ORA-02761: File number to be canceled is negative. Cause: The file number contained with the sfiov structure is less than zero. Action: This may be a programming error. If it is not, contact ORACLE support. ORA-02762: file number to be cancelled is greater than the maximum. Cause: The file number contained with the sfiov structure is greater than the maximum. Action: This may be a programming error. If it is not, contact ORACLE support. ORA-02763: Unable to cancel at least one request Cause: No requests were found that could be cancelled. Action: This error can occur if all the requests dealing with that file number have already been filled. ORA-02764: Invalid package mode Cause: The mode of the package can only be parallel or duplex. Action: See sfa.h for the correct values. ORA-02765: Invalid maximum number of servers Cause: The number of servers given was less than or equal to zero. Action: Use a number greater than zero. ORA-02766: Invalid maximum of request descriptors Cause: The number of request descriptors was less than or equal to zero. Action: Use a number greater than zero. ORA-02767: Less than one request descriptor was allocated per server Cause: The package requires that the number of request descriptors be greater than or equal to the number of servers used. Action: Use a higher number ORA-02768: Maximum number of files is invalid Cause: The maximum number of files to be used by the package was less than or equal to zero. Action: Use a positive number. ORA-02769: Setting of handler for SIGTERM failed Cause: The package was unable to set up handling by the server for the termination signal. This is an internal error. Action: Contact ORACLE support. ORA-02770: Total number of blocks is invalid Cause: The total number of blocks to be allocated for use by the package was not greater than zero. Action: Use a positive number. ORA-02771: Illegal request time out value Cause: The number was not a positive number. Action: Use a positive number. ORA-02772: Invalid maximum server idle time Cause: The time given was not a positive number. Action: Use a positive number. ORA-02773: Invalid maximum client wait time Cause: The time given was not a positive number. Action: Use a positive number. ORA-02774: Invalid request list latch time out value Cause: The time given was not a positive number. Action: Use a positive number. ORA-02775: Invalid request done signal Cause: The signal number was not a positive number. Action: Use a positive number. ORA-02776: Value for request done signal exceeds maximum Cause: The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system. Action: none ORA-02777: Stat failed on log directory Cause: The package was unable to get information about the directory in which the log files are to reside. Action: Check the permissions on the directory or use a different directory name. ORA-02778: Name given for the log directory is invalid Cause: The name given for the directory in which the logs are to be kept does not correspond to a directory. Action: Use a different name. ORA-02779: Stat failed on core dump directory Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception. Action: Check the permissions on the directory or use a different directory name. ORA-02780: Name given for the core dump directory is invalid Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory. Action: Use a different name. ORA-02781: Invalid value given for the timing wanted flag Cause: The value given was not TRUE or FALSE. Action: none ORA-02782: Both read and write functions were not specified Cause: To ensure that the functions act symmetrically, pointers to both the read and write functions must be given. Action: Either specify both functions or specify neither. The package will supply its own functions. ORA-02783: Both post and wait functions were not specified Cause: To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given. Action: Either specify both functions or specify neither. The package will supply its own functions. ORA-02784: Invalid shared memory ID specified Cause: The ID of the segment specified for use as the shared buffer region was invalid. Action: Use a different ID, or let the package specify its own. ORA-02785: Invalid shared memory buffer size Cause: The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero. Action: Use a positive number. ORA-02786: Size needed for shared region is greater than segment size Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment. Action: Use a larger size segment or let the package allocate its own. ORA-02787: Unable to allocate memory for segment list Cause: The package cannot allocate memory for an internal segment list because the system has run out of memory. The "additional information" field is the amount of memory that the package attempted to allocate. Action: none ORA-02788: Unable to find kernel process pointer in async process array Cause: Internal error - Contact ORACLE support. Action: none ORA-02789: Maximum number of files reached Cause: The maximum number of files that can be used for asynchronous I/O has been reached. Action: Shut down the servers and re-initialize the package with a higher number. ORA-02790: File name is too long Cause: The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The "additional information" field is the maximum length. Action: Use a shorter name. ORA-02791: Unable to open file for use with asynchronous I/O Cause: The package could not open file for some reason. Action: Check the file name. ORA-02792: Unable to fstat() a file being used for asynchronous I/O. Cause: The fstat(2) call on a file being used for asynchronous I/O failed. Action: Check the file name. ORA-02793: Close of asynchronous I/O failed. Cause: The client was unable to close a file being used for asynchronous I/O. Action: Contact ORACLE support - this should not happen. ORA-02794: Client unable to get key for shared memory Cause: The client was unable to get a key so that it obtain shared memory for use with shared memory. Action: Contact ORACLE support - this is an internal error. ORA-02795: Request list is empty Cause: The client was signalled by a server that it was done with a request but the "done" list was empty. Action: Internal error - contact ORACLE support. ORA-02796: Done request is not in correct state Cause: A request is not in the right state. Action: Internal error - contact ORACLE support. ORA-02797: No requests available Cause: No free request descriptors are available. Action: Wait until some requests are filled and then retry the request, or shutdown the servers and initialize the package with a higher number of requests. ORA-02798: Invalid number of requests Cause: The number of operations sent to either sfard() or sfawrite() is less than zero. Action: This is a user programming error. ORA-02799: Unable to arm signal handler Cause: The arming of a signal handler for the "done" signal failed. Action: Internal error - contact ORACLE support. ORA-02800: Requests timed out Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time. Action: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with sfainit(). If the server processes are dying due to unexpected signals, this is an internal error, and ORACLE support should be contacted. ORA-02801: Operations timed out Cause: Some asynchronous operations timed out in kernel mode. Action: Internal error - contact ORACLE support. ORA-02802: No idle servers available in parallel mode Cause: Internal error. Action: Contact ORACLE support. ORA-02803: Retrieval of current time failed Cause: Internal error. Action: Contact ORACLE support. ORA-02804: Allocation of memory failed for log file name Cause: The client was unable to allocated a buffer for the name of the log file. Action: Contact your System Administrator. ORA-02805: Unable to set handler for SIGTPA Cause: Internal error. Action: Contact ORACLE support. ORA-02806: Unable to set handler for SIGALRM Cause: Internal error. Action: Contact ORACLE support. ORA-02807: Allocation of memory for I/O vectors failed. Cause: The client was unable to allocate memory for the array of I/O vectors that the servers are to use. Action: Contact your System Administrator. ORA-02808: Allocation of memory of open files array failed. Cause: The client was unable to allocate memory for an array of flags that the servers are to use. Action: Contact your System Administrator. ORA-02809: Jump buffer not valid Cause: Internal error. Action: Contact ORACLE support. ORA-02813: Unable to make temporary file name in order to get key Cause: Internal error. Action: Contact ORACLE support. ORA-02814: Unable to get shared memory Cause: Shmget(2) failed. Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support. ORA-02815: Unable to attach shared memory Cause: Shmat(2) failed. Action: Check the UNIX number. If you are unsure about what it means, contact ORACLE customer support. ORA-02816: Unable to kill a process Cause: A server did not die after being sent a kill signal. Action: The process may be a runaway - contact ORACLE customer support. ORA-02817: Read failed Cause: A server could not read a requested amount of data. Action: Check the call to sfard(). An incorrect file descriptor may have been sent to sfard(). The number in the "additional information" field is the starting block number of the data segment being read in. ORA-02818: Less than the number of blocks requested was read in Cause: A server could not read in the request amount of data. The first number in the "additional information" field is the block number being read in. The second is the actual number of bytes that was read in. Action: This is a programming error. ORA-02819: Write failed Cause: A server was unable to perform a write. The number in the "additional information" field is the starting block number of the data segment being written out. The first number in the "additional information" field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up. Action: Check the UNIX error number. ORA-02820: Unable to write the requested number of blocks Cause: A server could not write the requested amount of data out to disk. The disk may have run out of space. Action: Check the UNIX error number. ORA-02821: Unable to read the requested number of blocks. Cause: A server could not read the number of blocks that was requested. The end of the file may have been read. Action: Check the file on disk. ORA-02822: Invalid block offset Cause: A server was unable to seek to the designated block. Action: Check the UNIX error number. ORA-02823: Buffer is not aligned. Cause: The buffer on which an I/O is being done is not on the correct boundary. Action: Check the calling program. ORA-02824: Request free list is empty Cause: The list from which the package allocates request descriptors is empty because all of the descriptors is in use. Action: Wait until some become free, or initialize the package with a higher number of request descriptors. ORA-02825: Request on free list was not free Cause: Internal error. Action: Contact ORACLE support. ORA-02826: Illegal block size Cause: A negative number was given for the I/O block size to be used by the asynchronous I/O package. Action: This is a programming error - use either a positive number or zero to get the default value. ORA-02827: Invalid file number Cause: The file number upon which an operation is to done is either less than zero or greater than the maximum number of files than can be open. Action: This is a programming error. Since the calling program should not touch this number, this is a programming error. ORA-02828: Segment free list is empty Cause: No segments are available to allocated. Action: Free some segments or shut down the package and re-initialize it with a higher number of segments. ORA-02829: No segment of the proper size is available Cause: No segment of the proper size is ready for use by the caller. Action: Free some segments and try again. ORA-02830: Segment could not be split - no free segments available Cause: A segment that is larger than that desired could not be split because no free segment was available. Action: Free some segments and try again. ORA-02831: Segment deallocation failed - empty segment list Cause: The caller attempted to deallocate a segment but the "in use" list was empty. This is a programming error. Action: Check the calling program. ORA-02832: Segment deallocation failed - segment not on list Cause: The caller attempted to deallocate a segment that was not on the "in use" list. This is a programming error. Action: Check the calling program. ORA-02833: Server was unable to close file Cause: A server was unable to close a file being used for asynchronous I/O. Action: See the UNIX error number for more information. ORA-02834: Server unable to open file Cause: The server was unable to open a file for use with asynchronous I/O. Action: Check the UNIX error number for more information. ORA-02835: Server unable to send signal to client Cause: Internal error. Action: Contact ORACLE support. ORA-02836: Unable to create temporary key file Cause: Internal error. Action: Contact ORACLE support. ORA-02837: Unable to unlink temporary file Cause: Internal error. Action: Contact ORACLE support. ORA-02838: Unable to arm signal handler for the alarm signal Cause: The arming of a signal handler for the alarmsignal failed. Action: Internal error - contact ORACLE support. ORA-02839: Sync of blocks to disk failed. Cause: The server was unable to flush its writes out to disk. Action: Check the UNIX error number. ORA-02840: Open of log file by client failed Cause: The client process was unable to open its log file. Action: Check the UNIX error number for more information. ORA-02841: Server died on start up Cause: A server exited during its initialization process. Action: Check the servers" logs for more information. ORA-02842: Client unable to fork a server Cause: The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn. Action: Either reduce the number of servers that are to be used, or reconfigure the operating system so that it can handle more processes. ORA-02843: Invalid value for kernel flag Cause: An illegal value was given for the kernel flag in the information structure. Only TRUE and FALSE are permitted. Action: This is a programming error - check the calling routine. ORA-02844: Invalid value for the leave open flag Cause: A value was given for the flag that determines whether a file is to be left open after the client checks it to see if the servers can use it. Only TRUE and FALSE are supported. Action: This is a programming error - check the calling routine. ORA-02845: Invalid value for the timing wanted flag Cause: A value was given for the flag that indicates that operations are to be timed out. Only TRUE and FALSE are supported. Action: This is a programming error - check the calling routine. ORA-02846: Unkillable server Cause: A server would not respond to the termination signal. The first number is the number of the server. The second is its UNIX process number. This is an internal problem. Action: This is an operating system problem. ORA-02847: Server did not terminate when posted Cause: A server did not respond to a posted request to shutdown. The first number is the number of the server. The second is its UNIX process number. This is an internal problem. Action: Contact ORACLE support. ORA-02848: Asynchronous I/O package is not running Cause: An operation using the asynchronous I/O package was attempted without first initializing the package using sfainit(). Action: Call sfainit() before using the package. ORA-02849: Read failed because of an error Cause: A server could not read the requested amount of data from disk. Action: Check the UNIX error number. ORA-02850: File is closed Cause: A file upon which an asynchronous I/O operation is to be performed has already been closed by the package. Action: This is a programming error. ORA-02851: Request list is empty when it should not be Cause: This is an internal problem. Action: Contact ORACLE support. ORA-02852: Invalid critical-section time out value Cause: The time given was not a positive number. Action: Use a positive number. ORA-02853: Invalid server list latch time out value Cause: The time given was not a positive number. Action: Use a positive number. ORA-02854: Invalid number of request buffers Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than 0. Action: Use a number that is greater than or equal to 0. ORA-02855: Number of requests is less than the number of slaves Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than the number specified for the number of slaves, "db_slaves." Action: Specify a number that is greater than that given for "db_slaves" Alternatively, specify 0. The kernel will supply the appropriate number. ORA-02875: smpini: Unable to get shared memory for PGA Cause: Stated in errno. Action: Resolve the problem. ORA-02876: smpini: Unable to attach to shared memory for PGA Cause: Stated in errno. Action: Resolve the problem. ORA-02877: smpini: Unable to initialize memory protection Cause: The adspcinit program has not been executed. Action: Execute the adscpinit program as shown in your Installation and Users" Guide. If the problem persists, try rebooting your computer. ORA-02878: sou2o: Variable smpdidini overwritten Cause: The variable smpdidini was overwritten, probably by client code. Action: Verify client code, e.g. Pro*C, for illegal memory access. If the problem occurs outside Single Task operation, contact your customer support representative. ORA-02879: sou2o: Could not gain access to protected memory Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02880: smpini: Could not register PGA for protection Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02881: sou2o: Could not revoke access to protected memory Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02882: sou2o: Could not register SGA for protection Cause: This is an internal error, note error code in errno. Action: Report to your customer support representative. Restarting your application or your computer may cure the problem. ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature Cause: The environment variable EXTSHM was set before starting oracle. Action: Unset the environment variable EXTSHM and startup oracle. ORA-03001: unimplemented feature Cause: This feature is not implemented. Action: None. ORA-03002: operator not implemented Cause: This is an internal error. Action: Contact your customer support representative. ORA-03007: obsolete feature Cause: User attempted to use a feature which is no longer supported. Action: None. ORA-03008: parameter COMPATIBLE >= string needed for string Cause: An attempt was made to use a feature for a later Oracle version, than the setting of the initialization parameter, COMPATIBLE. Action: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options. ORA-03112: a server linked as single-task cannot use SQL*Net Cause: A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement. Action: Do not use SQL*Net connect strings in a single-task environment. ORA-03113: end-of-file on communication channel Cause: The connection between Client and Server process was broken. Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time. ORA-03119: two-task detected inconsistent datatype specification Cause: There was both a datatype, and an anonymous datatype declaration found. Action: Correct the specification. ORA-03122: attempt to close ORACLE-side window on user side Cause: This is an internal error. Action: Contact your customer support representative. ORA-03123: operation would block Cause: This is a status code that indicates that the operation cannot complete now. Action: None; this is not an error. The operation should be retried again for completion. ORA-03124: two-task internal error Cause: Internal error. Action: Contact your customer support representative. ORA-03125: client-server protocol violation Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code. Action: Contact your customer support representative. ORA-03126: network driver does not support non-blocking operations Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations. Action: Use default blocking operations or use a driver supporting non-blocking operations. ORA-03127: no new operations allowed until the active operation ends Cause: An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched. Action: Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been inserted or fetched. ORA-03128: connection is in blocking mode Cause: The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode. Action: If non-blocking mode is required use appropriate OCI calls to change the mode. ORA-03129: the next piece to be inserted is required Cause: The application performed a piecewise bind on a column. Action: Provide the next piece of this bind variable. ORA-03130: the buffer for the next piece to be fetched is required Cause: The application performed a piecewise define on the column. Action: Provide the next buffer for the next piece to be retrieved. ORA-03131: an invalid buffer was provided for the next piece Cause: The application either provided the length of the buffer for the next piece to be zero or provided a null pointer. Action: Verify if the buffer pointer for the next piece is null or if the length is zero. ORA-03132: two-task default value overflow Cause: The default value specified for a record field was too large. Action: Change the default value to fit the field size. ORA-03134: Connections to this server version are no longer supported. Cause: An attempt was made to connect to an Oracle server of older version. Action: Please refer to documentation for more details. ORA-03135: connection lost contact Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection. Action: 1) Check if the server session was terminated. 2) Check if the timeout parameters are set properly in sqlnet.ora. ORA-03136: inbound connection timed out Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2) Configure SQL*NET with a proper inbound connect timeout value if necessary. ORA-03200: the segment type specification is invalid Cause: segment type is not TABLE, INDEX, or CLUSTER Action: use a correct segment type ORA-03201: the group number specification is invalid Cause: the freelist group number was either negative or larger than the the number of freelist groups in the segment Action: use a correct group number ORA-03202: the scan limit specification is invalid Cause: the scan limit did not have a positive integer value the number of freelist groups in the segment Action: use a correct scan limit ORA-03203: concurrent update activity makes space analysis impossible Cause: high volume of user updates interfere with the space analysis Action: retry the command or lock the underlying objects ORA-03204: the segment type specification should indicate partitioning Cause: partition name is specified for the space analysis, but the object type does not indicate parttitioning Action: specify PARTITION in the segment type, if the object is partitioned, otherwise, omit the partition name ORA-03205: partition name is required when partitioned type is specified Cause: partition name is not specified for the space analysis, but the object type indicates parttitioning Action: specify partition name, if the object is partitioned, otherwise, specify a non-partitioned type ORA-03206: maximum file size of (string) blocks in AUTOEXTEND clause is out of range Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed. Action: Reduce the size and retry. ORA-03207: subpartitioned type must be specified for composite object Cause: partition type is specified for the space analysis, but the object type indicates composite partitioning Action: specify subpartition name and subpartition type ORA-03208: partitioned type must be specified for a non-composite object Cause: subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning Action: specify partition name and partition type ORA-03209: DBMS_ADMIN_PACKAGE invalid file/block specification Cause: The value of file number or block number is outside of limits or inconsistent Action: Fix the file number/block number value ORA-03210: DBMS_ADMIN_PACKAGE invalid option specification Cause: The value of one of the option parameters is incorrect Action: Fix the option value ORA-03211: The segment does not exist or is not in a valid state Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation does not exist or is not in a state appropriate for this operation Action: Fix the segment specification, or put the segment in the appropriate state. ORA-03212: Temporary Segment cannot be created in locally-managed tablespace Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent tablespace of kind locally-managed Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace ORA-03213: Invalid Lob Segment Name for DBMS_SPACE package Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist. Action: Fix the Segment Specification ORA-03214: File Size specified is smaller than minimum required Cause: File Size specified for add/resize datafile/tempfile does not allow for the minimum required of one allocation unit. Action: Increase the specification for file size ORA-03215: File Size specified for resize is too small Cause: File Size specified for resize datafile/tempfile causes bitmap control structures to overlap Action: Increase the specification for file size ORA-03216: Tablespace/Segment Verification cannot proceed Cause: Corruptions detected during verification whch cannot be dealt with Action: Do manual verification ORA-03217: invalid option for alter of TEMPORARY TABLESPACE Cause: invalid option for alter of temporary tablespace was specified Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE, TEMPFILE OFFLINE ORA-03218: invalid option for CREATE/ALTER TABLESPACE Cause: invalid option for create/alter tablespace of type locally-managed Action: Specify one of the valid options. ORA-03219: Tablespace "string" is dictionary-managed, offline or temporary Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary Action: Reissue operation for a different tablespace, mount the tablespace or do not issue it at all, since it does not apply for the given tablespace ORA-03220: DBMS_ADMIN_PACKAGE required parameter is NULL or missing Cause: Some of the procedures was called with missing or NULL parameters Action: Specify the missing parameter ORA-03221: Temporary tablespaces and temporary segments must have standard block size Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size. Action: (1) If creating a temporary tablespace, do not specify a block size different from the standard block size. (2) If altering an existing permanent tablespace to a temporary tablespace, ensure that it is of standard block size. (3) Ensure that the user"s temporary tablespace is a tablespace having the standard block size. ORA-03222: average row size and row count must be greater than zero Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information. Action: Check the row size parameter in dbms_space.create_table_cost(). For explain plan, make sure statistics have been computed for all source tables in the CREATE TABLE AS SELECT statement. ORA-03230: segment only contains string blocks of unused space above high water mark Cause: Attempt to preserve too many blocks. Action: reduce the KEEP amount. ORA-03231: the INITIAL extent may not be deallocated Cause: Attempt to deallocate space from the segment which was truncated prior to the 7.3 release. Action: increase the KEEP amount, or truncate the segment, and reissue the command. ORA-03233: unable to extend table string.string subpartition string by string in tablespace string Cause: Failed to allocate an extent for table subpartition segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-03234: unable to extend index string.string subpartition string by string in tablespace string Cause: Failed to allocate an extent for index subpartition segment in tablespace. Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-03235: max # extents (string) reached in table string.string subpartition string Cause: A table subpartition tried to extend past maxextents Action: If maxextents is less than the system maximum, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params ORA-03236: max # extents (string) reached in index string.string subpartition string Cause: An index subpartition tried to extend past maxextents Action: If maxextents is less than the system max, raise it. Otherwise, you must recreate with larger initial, next or pctincrease params. ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (string) Cause: Too large a size for an initial extent due to freelist group specification Action: Reduce number of freelist groups specified for segment ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated. Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated. ORA-03239: maxextents (string) reached in LOB segment string.string subpartition string Cause: A LOB subpartition segment tried to extend past maxextents. Action: If maxextents is less than the system maximum, raise it. Otherwise, recreate the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters. ORA-03240: User"s temporary tablespace same as tablespace being migrated Cause: Users default temporary tablespace must be different from the tablespace being migrated. Action: alter users default temporary tablespace to be different. ORA-03241: Invalid unit size Cause: User specified an invalid unit size for the tablespace Action: Specify the correct unit size. To estimate unit size please refer to Oracle Server Administrator"s Guide. ORA-03242: Tablespace migration retried 500 times Cause: For migration to complete, temporary segments should not be present in the tablespace at the time of migration. Action: Avoid migrating the tablespace when there is heavy temporary segment creation going on as with object drops. ORA-03243: destination dba overlaps with existing control information Cause: Cannot overlap control information during relocation Action: Please chose another destination address ORA-03244: No free space found to place the control information Cause: During migration of tablespace found no place to put the control information. If during bitmaps relocation, found no space at the specified destination. Action: If during migration, add more space to the tablespace and retry migration. If during bitmaps relocation, specify a destination address where there is enough free space. ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate Cause: Tablespace was not dictionary managed or online or permanent. Action: Make sure the tablespace is online, permanent and dictionary managed ORA-03246: Invalid block number specified Cause: Control information cannot be placed at the specified dba either because the block number specified is beyond the file end or the file is not large enough to accomodate the control information at that location Action: specify a correct block number ORA-03247: Invalid block number specified Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive Action: Choose another destination dba. ORA-03248: Too much of segment creation activity during migration Cause: Temporary segments were attempted to be created during migration Action: The error is signalled after retrying migration for 500 times. Run migration when there is less of segment creation activity is going on. ORA-03249: Uniform size for auto segment space managed tablespace should have atleast string blocks Cause: For the given blocksize, uniform size specified is insufficient Action: Specify larger extent size and retry ORA-03250: Cannot mark this segment corrupt Cause: This segment cannot be marked corrupt because it contains data dictionary objects Action: Check the segment information and reissue the command. ORA-03251: Cannot issue this command on SYSTEM tablespace Cause: It is not permitted to migrate SYSTEM tablespace from locally managed format to dictionary managed format or relocate bitmaps. Action: Check the tablespace name and procedure name ORA-03252: initial extent size not enough for LOB segment Cause: Fatblock size of LOB segment is too big to fit into the initial extent. Action: Specify a smaller fatblock size or create the LOB segment in other tablespaces with bigger initial extent size. ORA-03254: unable to execute the sql in read only database Cause: Unable to create a consistent snapshot of the object in a read only database. Transaction recovery must be performed before opening the database read only. Action: Open the database read write, allow dead transaction recovery to complete and then open the database read only. ORA-03261: the tablespace string has only one file Cause: Dropping file from ts which has a single file extent. Action: Cannot make a tablespace fileless ORA-03262: the file is non-empty Cause: Trying to drop a non-empty datafile Action: Cannot drop a non empty datafile ORA-03263: cannot drop the first file of tablespace string Cause: Trying to drop the first datafile with which ts is created Action: Cannot drop the first datafile with which ts is created ORA-03264: cannot drop offline datafile of locally managed tablespace Cause: Trying to drop offline datafile in lmts Action: Try to drop file afetr making it online ORA-03274: both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified Cause: The DEALLOCATE option and the ALLOCATE option are specified in the same command. Action: Choose one of the options or issue two separate commands. ORA-03275: duplicate DEALLOCATE option specification Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once. Action: Specify the option at most once. ORA-03276: duplicate ALLOCATE EXTENT option specification Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once. Action: Specify the option at most once. ORA-03277: invalid SIZE specified Cause: The specified value must be an integer. Action: Choose an appropriate integer value. ORA-03278: duplicate ALLOCATE EXTENT option specification Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once. Action: Specify each option at most once. ORA-03279: invalid INSTANCE specified Cause: The specified value is not recognized as a valid instance name. Action: Use a valid name. ORA-03280: invalid DATAFILE filename specified Cause: A character string literal is expected, but not found. Action: Specify filenames using character string literals. ORA-03281: invalid ALLOCATE EXTENT option Cause: An option other than DATAFILE, SIZE or INSTANCE was specified. Action: Remove invalid option and retry the command. ORA-03282: missing ALLOCATE EXTENT option Cause: No ALLOCATE EXTENT options were specified. Action: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE. ORA-03283: specified datafile string does not exist Cause: The datafile does not exist Action: Retry the option with the correct datafile ORA-03284: datafile string is not a member of tablespace string Cause: The specified datafile does not belong to the tablespace that the object resides in. Action: Retry the option with the correct datafile. ORA-03286: ALLOCATE EXTENT not valid for HASH CLUSTERS Cause: The cluster is a hash cluster, and can not use the allcoate extent option. Action: none ORA-03287: invalid FREELIST GROUP specified Cause: The specified FREELIST GROUP number is invalid Action: Choose a number between 1 and # freelist groups for this object ORA-03288: both FREELIST GROUP and INSTANCE parameters may not be specified Cause: Both FREELIST GROUP and INSTANCE were specified in clause Action: Remove one of the two parameters ORA-03289: partition name and segment type do not match Cause: Partition name and segment type specified for space analysis do not match Action: Specify type PARTITION if the object is partitioned, specify SUBPARTITION if the object is composite ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword Cause: Invalid object specification given. Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE ORA-03291: Invalid truncate option - missing STORAGE keyword Cause: Expected STORAGE keyword Action: Either specify DROP STORAGE or REUSE STORAGE ORA-03292: Table to be truncated is part of a cluster Cause: The table being truncated is a member of a cluster. Action: Either use TRUNCATE CLUSTER or DROP TABLE ORA-03293: Cluster to be truncated is a HASH CLUSTER Cause: Only INDEX CLUSTERS can be truncated. Action: Drop and recreate the HASH CLUSTER instead of using truncate. ORA-03296: cannot resize datafile - file string not found Cause: The specified datafile is not available for resizing. Action: Ensure that the datafile name is valid, and if so, ensure the file is accessible. ORA-03297: file contains used data beyond requested RESIZE value Cause: Some portion of the file in the region to be trimmed is currently in use by a database object Action: Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed. ORA-03298: cannot shrink datafile - file string is under hot backup Cause: Attempt to shrink a datafile while it is under hot backup. This is not allowed. Action: Retry shrinking the file after the hot backup completes. ORA-03299: cannot create dictionary table string Cause: A dictionary table is created upon the first execution of the command "alter database datafile autoextend on" for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace. Action: See action for next error message in error stack. ORA-04000: the sum of PCTUSED and PCTFREE cannot exceed 100 Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100 Action: create the table/cluster specifying values whose sum is <= 100 ORA-04001: sequence parameter string must be an integer Cause: %s (a sequence parameter) specified was not an integer Action: create the sequence, giving the specified parameter an integer value ORA-04002: INCREMENT must be a non-zero integer Cause: a sequence increment was specified to be zero Action: specify the increment to be a non-zero value ORA-04003: sequence parameter string exceeds maximum size allowed (string digits) Cause: %s (a sequencer parameter) had too many digits Action: specify the parameter with the allowed number of digits ORA-04004: MINVALUE must be less than MAXVALUE Cause: MINVALUE was specified to be greater than or equal to MAXVALUE Action: specify a MINVALUE that is less than MAXVALUE ORA-04005: INCREMENT must be less than MAXVALUE minus MINVALUE Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE Action: specify an INCREMENT that is < MAXVALUE-MINVALUE ORA-04006: START WITH cannot be less than MINVALUE Cause: the given starting value is less than MINVALUE Action: make sure that the starting value is >= MINVALUE ORA-04007: MINVALUE cannot be made to exceed the current value Cause: the given MINVALUE would be greater than the current value Action: always make sure that MINVALUE is <= the current value ORA-04008: START WITH cannot be more than MAXVALUE Cause: the starting value would be larger than MAXVALUE Action: make sure that the starting value is less than MAXVALUE ORA-04009: MAXVALUE cannot be made to be less than the current value Cause: the current value exceeds the given MAXVALUE Action: make sure that the new MAXVALUE is larger than the current value ORA-04010: the number of values to CACHE must be greater than 1 Cause: the value in the CACHE clause was one Action: specify NOCACHE, or a value larger than one ORA-04011: sequence string must range between string and string Cause: the value specified for one of the sequence parameters exceeds limits Action: specify parameter within these limits ORA-04012: object is not a sequence Cause: the object specified cannot have sequence ddl"s performed on it Action: re-enter the statement being careful with the spelling of the name ORA-04013: number to CACHE must be less than one cycle Cause: number to CACHE given is larger than values in a cycle Action: enlarge the cycle, or cache fewer values ORA-04014: descending sequences that CYCLE must specify MINVALUE Cause: sequences that cycle must have their wrap-wrap specified Action: re-create the sequence, specifying its wrap-value ORA-04015: ascending sequences that CYCLE must specify MAXVALUE Cause: sequences that cycle must have their wrap-wrap specified Action: re-create the sequence, specifying its wrap-value ORA-04016: sequence string no longer exists Cause: sequence was dropped while processing its next value. Action: re-create the sequence ORA-04017: invalid value string (length = string) for parameter max_dump_file_size Cause: neither did the string supplied for max_dump_file_size parameter match the "UNLIMITED" string value nor did it represent a base 10 integer. Action: reassign a proper value to this parameter. ORA-04020: deadlock detected while trying to lock object stringstringstringstringstring Cause: While trying to lock a library object, a deadlock is detected. Action: Retry the operation later. ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring Cause: While waiting to lock a library object, a timeout is occurred. Action: Retry the operation later. ORA-04022: nowait requested, but had to wait to lock dictionary object Cause: Had to wait to lock a library object during a nowait request. Action: Retry the operation later. ORA-04027: self-deadlock during automatic validation for object string.string Cause: An attempt was made to validate an invalidated object but it failed because of a self-deadlock. Action: , e.g. compile the invalidated object separately. ORA-04028: cannot generate diana for object stringstringstringstringstring Cause: Cannot generate diana for an object because of lock conflict. Action: Please report this error to your support representative. ORA-04029: error ORA-string occurred when querying stringstringstring Cause: The table or view being queried might be missing. The error number indicates the error. Action: Fix the error. ORA-04030: out of process memory when trying to allocate string bytes (string,string) Cause: Operating system process private memory has been exhausted Action: none ORA-04031: unable to allocate string bytes of shared memory ("string","string","string","string") Cause: More shared memory is needed than was allocated in the shared pool. Action: If the shared pool is out of memory, either use the dbms_shared_pool package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the INIT.ORA parameters "shared_pool_reserved_size" and "shared_pool_size". If the large pool is out of memory, increase the INIT.ORA parameter "large_pool_size". ORA-04032: pga_aggregate_target must be set before switching to auto mode Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is not specified Action: before setting workarea_size_policy, set pga_aggregate_target to a value representing the total private memory available to the instance. This total is generally the total physical memory available in the system minus what is needed for the SGA minus what is needed for the operating system (e.g. 500MB) ORA-04033: Insufficient memory to grow pool Cause: The system had insufficient memory to grow the pool to the specified size. Action: Specify a smaller value to grow the pool. ORA-04034: unable to shrink pool to specified size Cause: The pool could not shrink to the specified size as it could not free memory. Action: Specify a larger value to which to shrink the pool to. ORA-04041: package specification must be created first before creating package body Cause: Attempt to create a package body before creating its package specification. Action: Create the package specification first before creating the package body. ORA-04042: procedure, function, package, or package body does not exist Cause: Attempt to access a procedure, function, package, or package body that does not exist. Action: Make sure the name is correct. ORA-04043: object string does not exist Cause: An object name was specified that was not recognized by the system. There are several possible causes: - An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist. - An attempt was made to rename an index or a cluster, or some other object that cannot be renamed. Action: Check the spelling of the named object and rerun the code. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.) ORA-04044: procedure, function, package, or type is not allowed here Cause: A procedure, function, or package was specified in an inappropriate place in a statement. Action: Make sure the name is correct or remove it. ORA-04045: errors during recompilation/revalidation of string.string Cause: This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation/revalidation of the object. Action: Check the following errors for more information, and make the necessary corrections to the object. ORA-04046: results of compilation are too large to support Cause: Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store. Action: Reduce the size of the store procedure by splitting it into smaller stored procedures. ORA-04047: object specified is incompatible with the flag specified Cause: The object type implied by the flag does not match the type of object specified. Action: Specify the correct object, or use the appropriate flag ORA-04050: invalid or missing procedure, function, or package name Cause: The required procedure, function, or package name is invalid or missing. Action: Specify a valid name. ORA-04051: user string cannot use database link string.string Cause: During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC. Action: Change your database link structure so that all indirect remote accesses are done from the same userid that originates the request. ORA-04052: error occurred when looking up remote object stringstringstringstringstring Cause: An error has occurred when trying to look up a remote object. Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database. ORA-04053: error occurred when validating remote object stringstringstringstringstring Cause: An error has occurred when trying to validate a remote object. Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database. ORA-04054: database link string does not exist Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link. Action: Either use a different database link or create the database link. ORA-04055: Aborted: "string" formed a non-REF mutually-dependent cycle with "string". Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2); Action: Break the cycle (possibly by adding a REF or by using another type). ORA-04060: insufficient privileges to execute string Cause: Attempt to execute a stored procedure without sufficient privileges. Action: Get necessary privileges. ORA-04061: existing state of string has been invalidated Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped. Action: Try again; this error should have caused the existing state of all packages to be re-initialized. ORA-04062: %s of string has been changed Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp/signature of the procedure. Action: Recompile the caller in order to pick up the new timestamp. ORA-04063: %s has errors Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view"s defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types. Action: Fix the errors and/or create referenced objects as necessary. ORA-04064: not executed, invalidated string Cause: Attempt to execute a stored procedure that has been invalidated. Action: Recompile it. ORA-04065: not executed, altered or dropped string Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure. Action: Recompile its dependents. ORA-04066: non-executable object, string Cause: Attempt to execute a non-procedure. Action: Make sure that a correct name is given. ORA-04067: not executed, string does not exist Cause: Attempt to execute a non-existent stored procedure. Action: Make sure that a correct name is given. ORA-04068: existing state of packagesstringstringstring has been discarded Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure. Action: Try again after proper re-initialization of any application"s state. ORA-04069: cannot drop or replace a library with table dependents Cause: An attempt was made to drop or replace a library that has dependents. There could be a table which depends on type which depends on the library being dropped. Action: Drop all table(s) depending on the type, then retry. ORA-04070: invalid trigger name Cause: An invalid trigger name was specified. Action: Verify that trigger name is not a reserved keyword. ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause. Action: Specify either BEFORE, AFTER or INSTEAD OF. ORA-04072: invalid trigger type Cause: An invalid trigger type was given. Action: Specify either INSERT, UPDATE or DELETE. ORA-04073: column list not valid for this trigger type Cause: A column list was specified for a non-update trigger type. Action: Remove the column list. ORA-04074: invalid REFERENCING name Cause: An invalid name was given in the referencing clause. Action: Verify the referencing name is not a reserved word. ORA-04075: invalid trigger action Cause: An statement was given for the trigger action. Action: Re-specify the trigger action. ORA-04076: invalid NEW or OLD specification Cause: An invalid NEW or OLD specification was given for a column. Action: Re-specify the column using the correct NEW or OLD specification. ORA-04077: WHEN clause cannot be used with table level triggers Cause: The when clause can only be specified for row level triggers. Action: Remove the when clause or specify for each row. ORA-04078: OLD and NEW values cannot be identical Cause: The referencing clause specifies identical values for NEW and OLD. Action: Re-specify either the OLD or NEW referencing value. ORA-04079: invalid trigger specification Cause: The create TRIGGER statement is invalid. Action: Check the statement for correct syntax. ORA-04080: trigger "string" does not exist Cause: The TRIGGER name is invalid. Action: Check the trigger name. ORA-04081: trigger "string" already exists Cause: The TRIGGER name or type already exists. Action: Use a different trigger name or drop the trigger which is of the same name. ORA-04082: NEW or OLD references not allowed in table level triggers Cause: The trigger is accessing "new" or "old" values in a table trigger. Action: Remove any new or old references. ORA-04083: invalid trigger variable "string" Cause: The variable referenced in the trigger body is invalid. Action: See the manual for valid trigger variable types. ORA-04084: cannot change NEW values for this trigger type Cause: New trigger variables can only be changed in before row insert or update triggers. Action: Change the trigger type or remove the variable reference. ORA-04085: cannot change the value of an OLD reference variable Cause: Old values can only be read and not changed. Action: Do not attempt to change an old variable. ORA-04086: trigger description too long, move comments into triggering code Cause: The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the pl/sql code executed for the trigger. Action: If the trigger description contains a large comment, move that ORA-04087: cannot change the value of ROWID reference variable Cause: Rowid"s can only be read and not changed. Action: Do not attempt to change an rowid value. ORA-04088: error during execution of trigger "string.string" Cause: A runtime error occurred during execution of a trigger. Action: Check the triggers which were involved in the operation. ORA-04089: cannot create triggers on objects owned by SYS Cause: An attempt was made to create a trigger on an object owned by SYS. Action: Do not create triggers on objects owned by SYS. ORA-04090: "string" specifies same table, event and trigger time as "string" Cause: Trigger is of duplicate event and trigger time. Action: Combine the triggering information into one trigger which is fired at the given time. ORA-04091: table string.string is mutating, trigger/function may not see it Cause: A trigger (or a user defined plsql function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it. Action: Rewrite the trigger (or function) so it does not read that table. ORA-04092: cannot string in a trigger Cause: A trigger attempted to commit or rollback. Action: Rewrite the trigger so it does not commit or rollback. ORA-04093: references to columns of type LONG are not allowed in triggers Cause: A trigger attempted to reference a long column in the triggering table. Action: Do not reference the long column. ORA-04094: table string.string is constraining, trigger may not modify it Cause: A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement. Action: none ORA-04095: trigger "string" already exists on another table, cannot replace it Cause: Cannot replace a trigger which already exists on a different table than the one being replaced. Action: Drop the trigger with the same name and re-create it. ORA-04096: trigger "string" has a WHEN clause which is too large, limit 2K Cause: A trigger"s "when" clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size. Action: Use a smaller "when" clause. Note, the trigger body could be used to perform the same limiting action as the "when" clause. ORA-04097: DDL conflict while trying to drop or alter a trigger Cause: An attempt was made to concurrently perform two DDL operations on a trigger or trigger table. Action: Investigate the new state of the trigger and retry the DDL operation, if still appropriate. ORA-04098: trigger "string.string" is invalid and failed re-validation Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger. Action: Options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger. ORA-04099: trigger "string" is valid but not stored in compiled form Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release. Action: Alter compile the trigger to create the trigger in stored form. Also, you may want to review that a proper upgrade was done. ORA-04930 to ORA-07499 ORA-04930: open sequence number failed or initial state is valid Cause: Either Shared Sequence Number OS component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly. Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the OS command ps -ef|grep . Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by isuing the ipcs -b OS command. If there are shared memory segments or processes still on the system, use svrmgrl to shutdown the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the cnxshow command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital"s customer support organization. ORA-04931: unable to set initial sequence number value Cause: A call to the SSN failed to set the sequence number to its initial value, possibly caused by an MC hardware problem. Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital"s customer support organization. If it is, contact Oracle support. ORA-04932: increment or adjust of sequence number failed Cause: A call to the SSN failed to increment the sequence number. Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital"s customer support organization. If it is, contact Oracle support. ORA-04933: initial service identifier is non-zero Cause: A valid service identifier existed before the sequence number service was opened. Action: Verify that the instance is completely shut down. ORA-04934: unable to obtain the current sequence number Cause: A call to the SSN failed to return its current value. Either there are many errors occurring on the MC hardware, or the sequence number has become invalid and cannot be validated. Action: Verify that the MC hardware is functioning properly. If it is, contact Oracle Support. ORA-04935: unable to get/convert SCN recovery lock Cause: A process has timed out trying to get or convert the SCN recovery lock. Another process probably has the lock in EX or SHR mode, but is not releasing it. Action: Contact Oracle Support. ORA-04940: unsupported optimization of Oracle binary, check alert log for more info Cause: ORACLE binary has been optimized with unsupported options or a required option has not been used. Action: Check the documentation for a list of supported and required flags for the optimizing utility that you used to optimize ORACLE. Shutdown the instance, optimize ORACLE again with supported combination of options and restart the instance. ORA-04941: required operating system patch needs to be applied Cause: The operating system could not return the start time of a process. Action: Check that the operating system kernel has been patched to return process start time. Apply the required operating system patch and restart the instance. ORA-06000: NETASY: port open failure Cause: Autologin unable to open port Action: Check log file for OS-specific error code ORA-06001: NETASY: port set-up failure Cause: Autologin unable to change port attributes Action: Check log file for OS-specific error code ORA-06002: NETASY: port read failure Cause: Autologin unable to read from port Action: Check log file for OS-specific error code ORA-06003: NETASY: port write failure Cause: Autologin unable to write to port Action: Check log file for OS-specific error code ORA-06004: NETASY: dialogue file open failure Cause: Autologin unable to open dialogue file Action: Check connect string for accuracy/typos ORA-06005: NETASY: dialogue file read failure Cause: Autologin unable to read dialogue file Action: Check log file for OS-specific error code ORA-06006: NETASY: dialogue execute failure Cause: Expected response never received Action: None ORA-06007: NETASY: bad dialogue format Cause: Dialogue file contains syntax error Action: Correct the dialogue file ORA-06009: NETASY: dialogue filename too long Cause: Full file spec for dialogue file exceeds 64 bytes Action: Amend connect string accordingly ORA-06010: NETASY: dialogue file too long Cause: Dialogue file exceeds 768 bytes in length Action: Simplify dialogue (e.g. remove comments, redundant white space), or split into two and link with "more" command ORA-06011: NETASY: dialogue too long Cause: One of two: 1. Dialogue contains more than 24 exchange blocks 2. Dialogue send string exceeds 84 bytes in length Action: Simplify dialogue or split into two and link with "more" command ORA-06017: NETASY: message receive failure Cause: Async driver gets I/O error while doing network read operation Action: Check log file for OS-specific error code and contact your customer support representative. ORA-06018: NETASY: message send failure Cause: Async driver gets I/O error while doing network write operation Action: Check log file for OS-specific error code and contact your customer support representative. ORA-06019: NETASY: invalid login (connect) string Cause: Syntax error in login string. Action: Resubmit with correct string. ORA-06020: NETASY: initialisation failure Cause: Async driver unable to complete initialisation Action: Check log file for OS-specific error code ORA-06021: NETASY: connect failed Cause: Async driver unable to establish connection with partner Action: Check log file for OS-specific error code ORA-06022: NETASY: channel open failure Cause: no free channel [should never happen] Action: Contact your customer support representative. ORA-06023: NETASY: port open failure Cause: Async driver unable to open port Action: Check log file for OS-specific error code ORA-06024: NETASY: VTM error Cause: Virtual Terminal Manager unable to read/write to port Action: Check log file for OS-specific error code ORA-06025: NETASY: Configuration error Cause: Async driver genned for server-only, but client service requested Action: Contact your customer support representative. ORA-06026: NETASY: port close failure Cause: Async driver unable to close port Action: Check log file for OS-specific error code ORA-06027: NETASY: channel close failure Cause: Async driver unable to close channel Action: Check log file for OS-specific error code ORA-06028: NETASY: unable to intialise for logging Cause: Async driver unable to initialise for logging I/O Action: Contact your customer support representative. ORA-06029: NETASY: port assignment failure Cause: Async driver unable to assign port to channel [should never happen] Action: Contact your customer support representative. ORA-06030: NETDNT: connect failed, unrecognized node name Cause: Node name specified in host string is unknown (probably misspelled) Action: Retry with correct node name ORA-06031: NETDNT: connect failed, unrecognized object name Cause: Host string contains reference to object (which doesn"t exist): @d:- => object is ORDN; when is VMS, the object is ORDN.COM when is UNIX, the object is ORDN @d:::"task=" => object is ; when is VMS, the object is .COM when is UNIX, the object is Action: Retry with correct object name or create the required object on host node ORA-06032: NETDNT: connect failed, access control data rejected Cause: Host string contains invalid username/password Action: Retry with correct username/password ORA-06033: NETDNT: connect failed, partner rejected connection Cause: Connection with partner was made but was rejected. Action: Contact your network administrator. ORA-06034: NETDNT: connect failed, partner exited unexpectedly Cause: Connection with host node was made but partner aborted Action: Make sure object (see 06031, above) is working (for VMS run the command file and make sure that the ORACLE server process starts up); sometimes happens when the network/node is under stress - in this case a retry often works. ORA-06035: NETDNT: connect failed, insufficient resources Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use. Action: Contact your network administrator. ORA-06037: NETDNT: connect failed, node unreachable Cause: Host node is down. Action: Contact your network administrator. ORA-06039: NETDNT: connect failed Cause: Connect failed for unexpected reason (see OSD error). Action: Contact your customer support representative. ORA-06040: NETDNT: invalid login (connect) string Cause: Syntax error in login string. Action: Resubmit with correct string. ORA-06041: NETDNT: disconnect failed Cause: Driver gets error while doing network close operation Action: Contact your customer support representative. ORA-06042: NETDNT: message receive failure Cause: Driver gets I/O error while doing network read operation Action: Contact your customer support representative. ORA-06043: NETDNT: message send failure Cause: Driver gets I/O error while doing network write operation Action: Contact your customer support representative. ORA-06044: NETDNT: connect failed, byte count quota exceeded Cause: Connect failed because of insufficient byte count quota. Action: Increase byte count quota. ORA-06102: NETTCP: cannot allocate context area Cause: Insufficient dynamic memory available for connection context area. Action: Contact your customer support representative. ORA-06105: NETTCP: remote host is unknown Cause: Host name specified in the login (connect) string is unknown. Action: Check spelling; make sure name is in the TCP/IP HOST file. ORA-06106: NETTCP: socket creation failure Cause: Process open file quota probably exceeded. Action: Contact your customer support representative. ORA-06107: NETTCP: ORACLE network server not found Cause: No entry in SERVICES file for ORACLE server. Action: Add ("orasrv") entry to the TCP/IP SERVICES file. ORA-06108: NETTCP: connect to host failed Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check the latter by targeting it with Telnet). Action: Start the SQL*Net TCP/IP server process on the remote host. ORA-06109: NETTCP: message receive failure Cause: I/O error occurred while attempting network read operation. Action: Contact your customer support representative. ORA-06110: NETTCP: message send failure Cause: I/O error occurred while attempting network write operation. Action: Contact your customer support representative. ORA-06111: NETTCP: disconnect failure Cause: Error occurred while closing a socket. Action: Contact your customer support representative. ORA-06112: NETTCP: invalid buffer size Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096). Action: Re-submit with valid buffer size. ORA-06113: NETTCP: Too many connections Cause: The maximum no. of concurrently open connections has been reached. Action: Exit an application with an open connection which is no longer required. ORA-06114: NETTCP: SID lookup failure Cause: From the remote host"s SQL*Net TCP/IP server: the database SID, specified in the login (connect) string, was not recognized. Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net TCP/IP server). ORA-06115: NETTCP: unable to create ORACLE logicals Cause: The host"s SQL*Net TCP/IP server was unable to create the necessary logicals required by the ORACLE server process. See the SQL*Net TCP/IP server log file for more details. Action: Contact your system administrator. ORA-06116: NETTCP: unable to create ORASRV process Cause: The host"s SQL*Net TCP/IP server was unable to create the ORACLE server process. See the SQL*Net TCP/IP server log file for more details. Action: Contact your system administrator. ORA-06117: NETTCP: unable to create ORASRV: quota exceeded Cause: The host"s SQL*Net TCP/IP server was unable to create the ORACLE server process because of quota depletion. Action: Increase quota allocations to the SQL*Net TCP/IP server process. ORA-06118: NETTCP: unable to complete handshake with ORASRV Cause: The ORACLE server process was started but failed to complete its initialization. Action: Contact your customer support representative. ORA-06119: NETTCP: spurious client request Cause: The host"s SQL*Net TCP/IP server was unable to recognize this connection request. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06120: NETTCP: network driver not loaded Cause: The TCP/IP network driver is not loaded. Action: Check that the TCP/IP driver is loaded correctly. ORA-06121: NETTCP: access failure Cause: The host"s SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06122: NETTCP: setup failure Cause: The host"s SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06123: NETTCP: cannot set KEEPALIVE Cause: The host"s SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06124: NETTCP: timeout waiting for ORASRV Cause: The ORACLE server process was started but failed to respond after N secs. Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = which will come into effect the next time the SQL*Net TCP/IP server is started. ORA-06125: NETTCP: ORASRV exited unexpectedly Cause: The ORACLE server process was started but exited unexpectedly. Possible causes: 1. Insufficient quotas to run ORASRV 2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_.OUT Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative. ORA-06126: NETTCP: ORASRV unable to open network connection Cause: The ORACLE server process was started but was unable to open the socket passed to it by TCPSRV. Action: Contact your customer support representative. ORA-06127: NETTCP: unable to change username Cause: The host"s SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host OS). Action: Create new user account on host. ORA-06128: NETTCP: unable to create mailbox Cause: The host"s SQL*Net TCP/IP server was unable to create a mailbox (needed for IPC communication with the ORACLE server process). See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06129: NETTCP: unable to transfer socket ownership to ORASRV Cause: The host"s SQL*Net TCP/IP server was unable to transfer the network communication handle to the ORACLE server process. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06130: NETTCP: host access denied Cause: The host"s SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host"s CONFIG.ORA. Action: To grant access, add appropriate entry to the host"s VNT. ORA-06131: NETTCP: user access denied Cause: The host"s SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege - as determined by the contents of the Username Mapping Table (UMT), a component of the host"s CONFIG.ORA. Action: To grant access, add appropriate entry to the host"s UMT. ORA-06132: NETTCP: access denied, wrong password Cause: The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password. Action: To grant access, get passwords in sync. ORA-06133: NETTCP: file not found Cause: The host"s SQL*Net TCP/IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request. Action: Check CONFIG.ORA for spelling; make correct entry. ORA-06134: NETTCP: file access privilege violation Cause: The host"s SQL*Net TCP/IP server did not have READ/ EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request. Action: Change protection on SID mapping file. ORA-06135: NETTCP: connection rejected; server is stopping Cause: The host"s SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping. Action: Re-start SQL*Net TCP/IP server. ORA-06136: NETTCP: error during connection handshake Cause: Network I/O failure occurred while communicating with the host"s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06137: NETTCP: error during connection handshake Cause: Network I/O failure occurred while communicating with the host"s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06138: NETTCP: error during connection handshake Cause: Network I/O failure occurred while communicating with the host"s SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06140: NETTCP: no such user Cause: A proxy login connect attempt failed because the client username has no counterpart on the host. Action: none ORA-06141: NETTCP: no privilege for user Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account. Action: Change account protection; change server privilges. ORA-06142: NETTCP: error getting user information Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account. See the SQL*Net TCP/IP server log file for more details. Action: Contact your customer support representative. ORA-06143: NETTCP: maximum connections exceeded Cause: The connect failed because the maximum conncurrent connections supported by the host"s SQL*Net TCP/IP server has already been reached. Action: Wait for a short period and re-try. ORA-06144: NETTCP: SID (database) is unavailable Cause: The database administrator on the host has varied the SID offline. Action: Wait for it to be varied back on-line. ORA-06145: NETTCP: unable to start ORASRV: images not installed Cause: The host"s SQL*Net TCP/IP server was unable to start the ORACLE server process because the ORACLE protected images were not installed. Action: Install the images. ORA-06250: NETNTT: cannot allocate send and receive buffers Cause: Two-task driver could not allocate data buffers. Action: There is insufficient memory to run your program. Kill off other processes to free up memory. ORA-06251: NETNTT: cannot translate address file name Cause: ORACLE_HOME environment variable not set. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. ORA-06252: NETNTT: cannot open address file Cause: The NTT two-task driver could not open a file containing address information. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running. ORA-06253: NETNTT: cannot read arguments from address file Cause: The NTT two-task driver could not read addressing information from its addressing file. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running. ORA-06254: NETNTT: cannot share connection to cube Cause: The NTT two-task driver could not share a connection to the cube. Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running. ORA-06255: NETNTT: cannot read pid of remote process Cause: An error occurred while reading the NTT communications link. Action: Contact your customer support representative. ORA-06256: NETNTT: remote fork failed Cause: The Oracle listener process on the cube could not fork off a shadow process. Action: The instance you are trying to connect to probably doesn"t have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance. ORA-06257: NETNTT: cannot send command line to shadow process Cause: An error occurred while writing the NTT communications link. Action: Contact your customer support representative. ORA-06258: NETNTT: cannot allocate context area Cause: Two-task driver could not allocate data buffers. Action: There is insufficient memory to run your program. Kill off other processes to free up memory. ORA-06259: NETNTT: cannot read from remote process Cause: An error occurred while reading the NTT communications link. Action: Contact your customer support representative. ORA-06260: NETNTT: cannot write to remote process Cause: An error occurred while writing the NTT communications linke. Action: Contact your customer support representative. ORA-06261: NETNTT: nrange() failed Cause: The call to "nrange()" failed while attempting to establish a connection. Action: Contact your customer support representative. ORA-06262: NETNTT: nfconn() failed Cause: The call to "nfconn()" failed while attempting to establish a connection. Action: Contact your customer support representative. ORA-06263: NETNTT: out of memory in pi_connect Cause: Two-task driver could not allocate data buffers. Action: There is insufficient memory to run your program. Kill off other processes to free up memory. ORA-06264: NETNTT: data protocol error Cause: The NTT two-task driver received an unexpected message type." Action: Contact your customer support representative. ORA-06265: NETNTT: break protocol error Cause: The NTT two-task driver received an unexpected message type." Action: Contact your customer support representative. ORA-06266: NETNTT: bad write length Cause: The NTT two-task driver failed on an internal consistency check. Action: Contact your customer support representative. ORA-06267: NETNTT: bad state Cause: The NTT two-task driver failed on an internal consistency check. Action: Contact your customer support representative. ORA-06268: NETNTT: cannot read /etc/oratab Cause: The NTT two-task driver could not read configuration information from /etc/oratab. Action: Make sure /etc/oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory. ORA-06300: IPA: Disconnect failure Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues. Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl. Otherwise contact your customer support representative. ORA-06301: IPA: Cannot allocate driver context Cause: The memory pool is exhausted. Action: Check the circumstances and try to allocate less memory in your program or adjust the init parameters in your INIT.ORA file and retry. ORA-06302: IPA: Cannot connect to remote host Cause: found. Action: Check sequentially for the above causes and eliminate the actual ORA-06303: IPA: Message send error Cause: The SQL*Net IPA driver could not write the message into the message queue. Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl. ORA-06304: IPA: Message receive error Cause: The SQL*Net IPA driver could not read a message from the message queue. Action: Make sure that the message queue exists and is accessible. If necessary rerun ipactl. ORA-06305: IPA: Illegal message type Cause: The communication between user and ORACLE is out of synchronization. This message should not normally be issued. Action: Contact your customer support representative. ORA-06306: IPA: Message write length error Cause: The IPA driver tried to write a message in the queue that was too big for the queue. Action: Contact your customer support representative. ORA-06307: IPA: Cannot reset connection Cause: A fatal error occurred during the resetting of the connection. Action: Contact your customer support representative. ORA-06308: IPA: No more connections available Cause: You have exhausted all your connections. Action: Try again when some of the current users have logged off. ORA-06309: IPA: No message queue available Cause: The SQL*Net IPA servers have not been started. Action: Run ipactl. ORA-06310: IPA: Environment variable(s) not set Cause: Environment variable(s) not set correctly. Action: Check and correct. ORA-06311: IPA: Maximum number of servers reached Cause: Maximum number of servers reached. Action: Shutdown and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start up enough servers to support database links. ORA-06312: IPA: Incorrect outgoing service name supplied Cause: Incorrect outgoing service name supplied. Action: Check and correct the service name. ORA-06313: IPA: Shared memory failed to initialise Cause: The shared memory has not been set up correctly. Action: Contact your system manager. ORA-06314: IPA: Event set up failure Cause: Fatal interprocess communication error. Action: Contact your system manager. ORA-06315: IPA: Invalid connect string Cause: The connect string is malformed. Action: Check and correct. ORA-06316: IPA: Invalid database SID Cause: The SID is unknown at the remote side. Action: Either the database does not exist, is not running, or there are no reserved servers for that SID. ORA-06317: IPA: Local maximum number of users exceeded Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side. Action: Wait for free connections to become available. If the problem persists, contact your system manager. ORA-06318: IPA: Local maximum number of connections exceeded Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side. Action: Wait for free connections to become available. If the problem persists, contact your system manager. ORA-06319: IPA: Remote maximum number of users exceeded Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side. Action: Wait for free connections to become available. If the problem persists, contact your system manager. ORA-06320: IPA: Remote maximum number of connections exceeded Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side. Action: Wait for free connections to become available. If the problem persists, contact your system manager. ORA-06321: IPA: Cannot reach the remote side Cause: There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect. Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied. ORA-06322: IPA: Fatal shared memory error Cause: An internal error has occurred in the shared memory handling. Action: Contact customer support. ORA-06323: IPA: Cause event error Cause: Fatal interprocess communication error. Action: Contact your system manager. ORA-06400: NETCMN: No default host string specified Cause: There was no default host string specified in the configuration and the user didn"t specify any explicit connect string. Action: Either reconfigure the system specifying a default connect string or use an explicit connect string. ORA-06401: NETCMN: invalid driver designator Cause: The login (connect) string contains an invalid driver designator. Action: Correct the string and re-submit. ORA-06402: NETCMN: error receiving break message Cause: Error occurred while attempting to read a break message. Action: Contact your customer support representative. ORA-06403: Unable to allocate memory. Cause: System unable to allocate needed virtual memory. Action: Configure more memory, reduce load, or simply try again. ORA-06404: NETCMN: invalid login (connect) string Cause: Syntax error in login string. Action: Correct string and re-submit. ORA-06405: NETCMN: reset protocol error Cause: Unable to reset out of break state. Action: Contact your customer support representative. ORA-06406: NETCMN: error sending break message Cause: Error occurred while attempting to send a break message. Action: Contact your customer support representative. ORA-06407: NETCMN: unable to set up break handling environment Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages. Action: Contact your customer support representative. ORA-06408: NETCMN: incorrect message format Cause: Message from partner contains bad header. Action: Contact your customer support representative. ORA-06413: Connection not open. Cause: Unable to establish connection. Action: Use diagnostic procedures to ascertain exact problem. ORA-06416: NETCMN: error on test Cause: Error occurred while testing I/O status of the network connection. Action: Contact your customer support representative. ORA-06419: NETCMN: server can not start oracle Cause: The remote server was unable to start an ORACLE process on behalf of the client. Action: Make sure permissions on the remote ORACLE program are correctly set. Contact your system administrator. ORA-06420: NETCMN: SID lookup failure Cause: From the remote host"s server: the database SID, specified in the login (connect) string, was not recognized. Action: Add the appropriate SID entry to the CONFIG.ORA or oratab file on the remote host (restarting the remote server may be needed). ORA-06421: NETCMN: Error detected in the read-in data Cause: Error found during recomputation of checksum or CRC. Action: Possible hardware failures of communication nodes. Contact system administrator immediately. ORA-06422: NETCMN: Error in sending data Cause: Unable to transmit data to remote host. Action: Try reconnect to remote host, and contact your system administrator. ORA-06423: NETCMN: Error in receiving data Cause: Unable to receive data from remote host. Action: Try reconnect to remote host, and contact your system administrator. ORA-06430: ssaio: Seals do not match Cause: A function was called with an invalid argument. Action: Contact your Oracle Customer Support Representative. ORA-06431: ssaio: Invalid Block number Cause: The file block number is out of range of the file. The additional information returns the block number. Action: Verify that the block number is correct. Run dbfsize and check if the block number is in that range. Contact your Oracle Customer Support Representative. ORA-06432: ssaio: Buffer Not Aligned Cause: The I/O buffer was not aligned on a 2K boundary. Action: Contact your Oracle Customer Support Representative. ORA-06433: ssaio: LSEEK error, unable to seek to requested block. Cause: The additional information returns the block number Action: Look up the additional information returned in your operating system reference manual. Verify that the block number is correct. ORA-06434: ssaio: read error, unable to read requested block from database file. Cause: The read system call returned an error. Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual. ORA-06435: ssaio: write error, unable to write requested block to database file. Cause: The write system call returned an error. Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual. ORA-06436: ssaio: asynchronous I/O failed due to incorrect parameters. Cause: The Asynchronous I/O system call returned an error. Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual. ORA-06437: ssaio: the asynchronous write was unable to write to the database file. Cause: The Asynchronous I/O system call returned an error. Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual. ORA-06438: ssaio: the asynchronous read was unable to read from the database file. Cause: The Asynchronous I/O system call returned an error. Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual. ORA-06439: ssaio: the asynchronous write returned incorrect number of bytes Cause: This write call may have been truncated. The additional information returns the block number and number of bytes. Action: Verify that the block number and the number of bytes written are correct. ORA-06440: ssaio: the asynchronous read returned incorrect number of bytes Cause: This read call may have been truncated. The additional information returns the block number and number of bytes. Action: Verify that the block number and the number of bytes read are correct. ORA-06441: ssvwatev: Incorrect parameter passed to function call Cause: Either the ORACLE process id, or wait time or event ID is invalid. Action: The additional information indicates the process id, time and event id. ORA-06442: ssvwatev: Failed with unexpected error number. Cause: Some system problems may exists on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06443: ssvpstev: Incorrect parameter passed to function call Cause: An invalid event ID is passed in to this routine. Action: The additional information indicates the event id. ORA-06444: ssvpstev: Failed with unexpected error number. Cause: Some system problems may exist on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06445: ssvpstevrg: Incorrect parameters passed to function call Cause: An invalid event id, or the low and high event ID do not exist. Action: The additional information indicates the error number. It also contains the event id, low boundary and high boundary. ORA-06446: ssvpstevrg: Failed with unexpected error number. Cause: Some system problems may exist on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06447: ssvpstp: Incorrect parameter passed to function call Cause: Invalid oracle process ID is passed in to this routine. Action: The additional information indicates the process id. ORA-06448: ssvpstp: Failed with unexpected error number. Cause: Some system problems may exists on your system, please check error logs. Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual. ORA-06449: The list IO or the sysvendor is not installed. Cause: ORACLE tries to use the sysvendor interface (INIT.ORA parameter use_sysvendor=true) but the UNIX kernel does not have the ORACLE sysvendor interface linked in. Action: Set use_sysvendor=false in INIT.ORA, if you don"t want to use this interface or link the UNIX kernel with this interface so that ORACLE can use it. ORA-06500: PL/SQL: storage error Cause: PL/SQL was unable to allocate additional storage. This message normally appears with an ORA-4030 or ORA-4031 error which gives additional information. Sometimes this error can be caused by runaway programs. Action: 1) Ensure there are no issues or bugs in your PL/SQL program which are causing excessive amounts of memory to be used. 2) Programmatically cause unused objects to be freed (e.g. by setting them to NULL). 3) Increase the amount of shared or process memory (as appropriate) available to you. ORA-06503: PL/SQL: Function returned without value Cause: A call to PL/SQL function completed, but no RETURN statement was executed. Action: Rewrite PL/SQL function, making sure that it always returns a value of a proper type. ORA-06504: PL/SQL: Return types of Result Set variables or query do not match Cause: Number and/or types of columns in a query does not match declared return type of a result set variable, or declared types of two Result Set variables do not match. Action: Change the program statement or declaration. Verify what query the variable actually refers to during execution. ORA-06505: PL/SQL: variable requires more than 32767 bytes of contiguous memory Cause: A PL/SQL variable was declared with a constraint which required more than 32767 bytes of memory. PL/SQL does not currently support allocations of contiguous memory greater than 32767 bytes. Action: Consider reducing the constraint in the variable declaration. If that is not possible, try changing the database or national character set to such, that requires less memory for the same constraint. Note: changing the character set will impact execution of all PL/SQL code. ORA-06510: PL/SQL: unhandled user-defined exception Cause: A user-defined exception was raised by PL/SQL code, but not handled. Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA. ORA-06511: PL/SQL: cursor already open Cause: An attempt was made to open a cursor that was already open. Action: Close cursor first before reopening. ORA-06512: at stringline string Cause: Backtrace message as the stack is unwound by unhandled exceptions. Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA. ORA-06513: PL/SQL: index for PL/SQL table out of range for host language array Cause: An attempt is being made to copy a PL/SQL table to a host language array. But an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, etc. If an table entry has not been assigned then the corresponding element in the host language array is set to null. Action: Increase size of host language array, or decrease size of PL/SQL table. Also make sure that you don"t use index values less than 1. ORA-06514: PL/SQL: The remote call cannot be handled by the server Cause: The remote call has parameters that are cursor variables or lob variables. This cannot be handled by stored procedures on your server. Action: Avoid using cursor variables or lob variables as parameters for stored procedures on this server or upgrade your server to a version that supports this. ORA-06515: PL/SQL: unhandled exception string Cause: An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors. Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA. ORA-06516: PL/SQL: the Probe packages do not exist or are invalid Cause: A Probe operation, probably an attempt to initialize the ORACLE server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid. Action: DBA should load the Probe packages. This can be done by running the pbload.sql script supplied with the RDBMS. ORA-06517: PL/SQL: Probe error - string Cause: An error occurred while passing a Probe operation to the server for execution. Action: Refer to the entry for the embedded error message. ORA-06518: PL/SQL: Probe version string incompatible with version string Cause: The current version of Probe is incompatible with the version on the ORACLE server. Action: Refer to the documentation to ensure that this degree of compatibility is supported. ORA-06519: active autonomous transaction detected and rolled back Cause: Before returning from an autonomous PL/SQL block, all autonomous transactions started within the block must be completed (either committed or rolled back). If not, the active autonomous transaction is implicitly rolled back and this error is raised. Action: Ensure that before returning from an autonomous PL/SQL block, any active autonomous transactions are explicitly committed or rolled back. ----------------------------------------------------------------------- 06520 through 06529 reserved for Foreign function errors ORA-06520: PL/SQL: Error loading external library Cause: An error was detected by PL/SQL trying to load the external library dynamically. Action: Check the stacked error (if any) for more details. ORA-06521: PL/SQL: Error mapping function Cause: An error was detected by PL/SQL trying to map the mentioned function dynamically. Action: Check the stacked error (if any) for more details. ORA-06522: %s Cause: ORA-06520 or ORA-065211 could stack this error with a system specific error string. Action: This error string should give the cause for errors ORA-06520 or ORA-065211 ORA-06523: Maximum number of arguments exceeded Cause: There is an upper limit on the number of arguments that one can pass to the external function. Action: Check the port specific documentation on how to calculate the upper limit. ORA-06524: Unsupported option : string Cause: The option specified is an unsupported feature for external procedures. Action: Correct the syntax in the external specification ORA-06525: Length Mismatch for CHAR or RAW data Cause: The length specified in the length variable has an illegal value. This can happen if you have requested requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the orlvstr or orlraw. Action: Correct the external procedure code and set the length variable correctly. ORA-06526: Unable to load PL/SQL library Cause: PL/SQL was unable to instantiate the library referenced by this referenced in the EXTERNAL syntax. This is a serious error and should normally not happen. Action: Report this problem to customer support. ORA-06527: External procedure SQLLIB error: string Cause: An error occurred in sqllib during execution of a Pro* external procedure. Action: The message text indicates the actual SQLLIB error that occurred. Consult the Oracle Error Messages and Codes manual for a complete description of the error message and follow the appropriate action. ORA-06528: Error executing PL/SQL profiler Cause: An error occurred in during execution of a PL/SQL profiler procedure. Action: Check the stacked errors for more details. ORA-06529: Version mismatch - PL/SQL profiler Cause: The PL/SQL profiler package (dbmspb.sql, prvtpbp.plb) does not match the version of the code in the server implementing the profiler. Action: Run the package profload.sql in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler packages ORA-06530: Reference to uninitialized composite Cause: An object, LOB, or other composite was referenced as a left hand side without having been initialized. Action: Initialize the composite with an appropriate constructor or whole-object assignment. ORA-06531: Reference to uninitialized collection Cause: An element or member function of a nested table or varray was referenced (where an initialized collection is needed) without the collection having been initialized. Action: Initialize the collection with an appropriate constructor or whole-object assignment. ORA-06532: Subscript outside of limit Cause: A subscript was greater than the limit of a varray or non-positive for a varray or nested table. Action: Check the program logic and increase the varray limit if necessary. ORA-06533: Subscript beyond count Cause: An in-limit subscript was greater than the count of a varray or too large for a nested table. Action: Check the program logic and explicitly extend if necessary. ORA-06534: Cannot access Serially Reusable package string Cause: The program attempted to access a Serially Reusable package in PL/SQL called from SQL context (trigger or otherwise). Such an access is currently unsupported. Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in PL/SQL called from sql context (trigger or otherwise). ORA-06535: statement string in string is NULL or 0 length Cause: The program attempted to use a dynamic statement string that was either NULL or 0 length. Action: Check the program logic and ensure that the dynamic statement string is properly initialized. ORA-06536: IN bind variable bound to an OUT position Cause: The program attempted to bind an IN bind variable to a statement that was expecting an OUT bind variable at that position. Action: Make sure that an OUT or IN OUT bind mode is specified for the bind argument. ORA-06537: OUT bind variable bound to an IN position Cause: The program attempted to bind an OUT bind variable to a statement that was expecting an IN bind variable at that position. Action: Make sure that an IN or IN OUT bind mode is specified for the bind argument. ORA-06538: statement violates string RESTRICT_REFERENCES pragma Cause: The program attempted to execute a dynamic statement which does not meet the purity level specified (in the pragma RESTRICT_REFERENCES directive) for the module executing the statement. Action: Ensure that the dynamic statement meets the purity level specified for the module executing the statement. ORA-06539: target of OPEN must be a query Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query. Action: Ensure that the OPEN cursor operation is done on a dynamic query statement. -------------------------------------------------------- 06540 through 06549 reserved for pl/sql error handling ORA-06540: PL/SQL: compilation error Cause: A pl/sql compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages. Action: See accompanying PLS-nnnnn error messages. ORA-06541: PL/SQL: compilation error - compilation aborted Cause: A pl/sql compilation error occurred and the compilation was aborted; but the compilation unit was written out to the backing store. However, unlike ora-06545, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages. Action: See accompanying PLS-nnnnn error messages. ORA-06544: PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: A pl/sql internal error occurred. Action: Report as a bug; the first argument is the internal error nuber. ORA-06545: PL/SQL: compilation error - compilation aborted Cause: A pl/sql compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ora-06541, the user will always see this error along with the accompaning PLS-nnnnn error messages. Action: See accompanying PLS-nnnnn error messages. ORA-06546: DDL statement is executed in an illegal context Cause: DDL statement is executed dynamically in illegal PL/SQL context. - Dynamic OPEN cursor for a DDL in PL/SQL - Bind variable"s used in USING clause to EXECUTE IMMEDIATE a DDL - Define variable"s used in INTO clause to EXECUTE IMMEDIATE a DDL Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement. ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or DELETE statements Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only. Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use USING clause instead. ORA-06548: no more rows needed Cause: The caller of a pipelined function does not need more rows to be produced by the pipelined function. Action: Catch the NO_DATA_NEEDED exception is an exception handling block. ORA-06549: PL/SQL: failed to dynamically open shared object (DLL): string Cause: One possible cause might be there are too many DLLs open at the same time. Action: -------------------------------------------------------- ORA-06550: line string, column string: string Cause: Usually a PL/SQL compilation error. Action: none ORA-06554: package DBMS_STANDARD must be created before using PL/SQL Cause: The DBMS specific extensions to PL/SQL"s package "STANDARD" are in package "DBMS_STANDARD". This package must be created before using PL/SQL. Action: Create package "DBMS_STANDARD". The source for this PL/SQL stored package is provided with the distribution. ORA-06555: this name is currently reserved for use by user SYS Cause: You tried to create a package named "STANDARD", "DBMS_STANDARD" or "DEBUG_IO". These are currently reserved for use by user SYS. Action: Choose another name for your package. ORA-06556: the pipe is empty, cannot fulfill the unpack_message request Cause: There are no more items in the pipe. Action: Check that the sender and receiver agree on the number and types of items placed on the pipe. ORA-06557: null values are not allowed for any parameters to pipe icd"s Cause: Internal error from the dbms_pipe package. Action: none ORA-06558: buffer in dbms_pipe package is full. No more items allowed Cause: The pipe buffer size has been exceeded. Action: none ORA-06559: wrong datatype requested, string, actual datatype is string Cause: The sender put different datatype on the pipe than that being requested (package "dbms_pipe"). The numbers are: 6 - number, 9 - char, 12 - date. Action: Check that the sender and receiver agree on the number and types of items placed on the pipe. ORA-06560: pos, string, is negative or larger than the buffer size, string Cause: Internal error from the dbms_pipe package. Action: none ORA-06561: given statement is not supported by package DBMS_SQL Cause: Attempting to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL. Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported. ORA-06562: type of out argument must match type of column or bind variable Cause: Attempting to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the type of the given out argument where to place the value is different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN (for defining a column) or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL. Action: Pass in an out argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable. ORA-06563: top level procedure/function specified, cannot have subparts Cause: The name to be resolved was specified with three parts (a.b.c) but the a.b part resolves to a top level procedure or function (which don"t have nested procedures). This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure. Action: Specify a procedure/function within a package, or a top level procedure/function. ORA-06564: object string does not exist Cause: The named object could not be found. Either it does not exist or you do not have permission to access it. Action: Create the object or get permission to access it. ORA-06565: cannot execute string from within stored procedure Cause: The named procedure cannot be executed from within a stored procedure, function or package. This function can only be used from pl/sql anonymous blocks. Action: Remove the procedure from the calling stored procedure. ORA-06566: invalid number of rows specified Cause: An invalid number of rows was specified in a call to the procedure DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows. Action: Specify a number that matches that for previously defined columns. ORA-06567: invalid number of values specified Cause: An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. In order to execute a given parsed statement in a given cursor, the same number of values must have been bound for all bind variables, so when EXECUTE is called, the latest calls to BIND_VARIABLE must must have specified the same number of values to be bound for all bind variables. Action: Make sure that the same number of values have been bound for all of the bind variables. ORA-06568: obsolete ICD procedure called Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an eralier release of RDBMS. Action: Make sure that all PL/SQL programs have been upgraded to the latest release of the RDBMS. This can be accomplished by following upgrade instructions in the README file, or by running the catproc.sql script supplied with the RDBMS. ORA-06569: Collection bound by bind_array contains no elements Cause: A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present then at execute time there will be no value for this bind and the statement is meaningless. Action: Fill the collection with the elements you want to bind and try the bind call again. ORA-06570: shared pool object does not exist, cannot be pinned Cause: The specified shared pool shared cursor could not be found, therefore it cannot be pinned. Action: Remove the procedure from the calling stored procedure. ORA-06571: Function string does not guarantee not to update database Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL/SQL function that does not contain a pragma that prevents the database from being updated. * A SQL statement references a stand-alone, PL/SQL function that contains an instruction to update the database. Action: If the referenced function is a packaged, PL/SQL function: Recreate the PL/SQL function with the required pragma; be certain to include the "Write No Database State" (WNDS) argument in the argument list of the pragma. If the referenced function is a stand-alone, PL/SQL function: Do not use the function. ORA-06572: Function string has out arguments Cause: A SQL statement references either a packaged, or a stand-alone, PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter. Action: Recreate the PL/SQL function without the OUT parameter in the argument list. ORA-06573: Function string modifies package state, cannot be used here Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL/SQL function that does not contain a pragma containing the "Write no Package State" (WNPS). * A SQL statement references a stand-alone, PL/SQL function that modifies a package state. A stand-alone, PL/SQL function referenced by a SQL statement cannot modify a package state. Action: If the function is a packaged, PL/SQL function: Recreate the function and include a pragma containing the "Write no Package State" (WNPS). If the function is a stand-alone, PL/SQL function: Delete the function from the SQL statement. ORA-06574: Function string references package state, cannot execute remotely Cause: There are two possible causes for this message: * A remote, packaged function or a remote-mapped, local, packaged function that does not contain a pragma with the "Write no Package State" (WNPS) and "Read no Package State" (RNPS) arguments references a package state. * A remote, stand-alone function or a remote-mapped, local, stand-alone function contains a reference to a package state (reads or writes a package variable). Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state. Action: If the function is a packaged function: Recreate the function and include a pragma containing the "Write no Package State" (WNPS) and "Read no Package State" (RNPS) arguments. If the function is a stand-alone function: Do not call the function. ORA-06575: Package or function string is in an invalid state Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors. Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object. ORA-06576: not a valid function or procedure name Cause: Could not find a function (if an INTO clause was present) or a procedure (if the statement did not have an INTO clause) to call. Action: Change the statement to invoke a function or procedure ORA-06577: output parameter not a bind variable Cause: The argument corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement must be a bind variable. Action: Change the argument to a bind variable ORA-06578: output parameter cannot be a duplicate bind Cause: The bind variable corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement cannot be a duplicate bind variable. Action: Change the bind variable to be unique ORA-06579: Bind variable not big enough to hold the output value Cause: The bind variable specified by the user is not large enough to hold the output returned by the function or a procedure. Action: Specify a bind variable of larger size. ORA-06580: Hash Join ran out of memory while keeping large rows in memory Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised. Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increaed. ORA-06592: CASE not found while executing CASE statement Cause: A CASE statement must either list all possible cases or have an else clause. Action: Add all missing cases or an else clause. ORA-06593: %s is not supported with natively compiled PL/SQL modules Cause: Specified feature is not yet supported for natively compiled PL/SQL modules yet. Action: Recompile the relevant PL/SQL modules in non-native mode by setting the parameter plsql_compiler_flags to INTERPRETED. ORA-06595: REF CURSOR parameters are not supported in forwarded RPC calls Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR parameter. Action: Either call the remote function directly (i.e., not by way of forwarding), or move the remote function to a database where it can be called directly. ORA-06596: unsupported LOB operation in RPC call Cause: An attempt was made to perform certain LOB operations (for example, deep copying of a temporary or abstract LOB on the client-side) while performing an RPC. This is not currently supported. Action: Perform the LOB operation in question before starting the RPC; or perform those LOB operations which are not actually executed on the client-side, on the server-side. ORA-06600: LU6.2 Driver: SNA software is not loaded Cause: The SNA software is not running. Action: Start the SNA software and try again. ORA-06601: LU6.2 Driver: Invalid database ID string Cause: The database string in the connect was invalid. Action: Provide a valid database string, as defined in documentation. ORA-06602: LU6.2 Driver: Error allocating context area Cause: Context area failure. Action: Contact your local service representative. ORA-06603: LU6.2 Driver: Error allocating memory Cause: Operating system refused request for memory. Action: Contact you local service representative. ORA-06604: LU6.2 Driver: Unable to allocate session with remote LU Cause: Allocate system call failed. Action: Ensure that the SNA software is running and that sessions are free. If this is the case, then check your SNA configuration data for errors. You may have entered an incorrect parameter. ORA-06605: LU6.2 Driver: Unexpected line turnaround Cause: SNA software switched from send to receive unexpectedly. Action: Check the SNA configuration data, particularly parameters associated with a session. ORA-06606: LU6.2 Driver: Unexpected response from SNA Cause: A parameter in an SNA call returned an unexpected value. Action: Attempt to reproduce problem, debug and record the value of the "what" data parameter at the time of error. Then contact your service representative. ORA-06607: LU6.2 Driver: Reset occurred in send state Cause: A reset was issued whilst in send state. Action: Check the SNA LOG data, if relevent, for further information. ORA-06608: LU6.2 Driver: Reset occurred in receive state Cause: A reset was received from the partner whilst in receive state. This may be because the partner deallocated. Action: Check the SNA LOG data, if relevent, for further information. ORA-06610: LU6.2 Driver: Failed during deallocation Cause: LU6.2 driver was unable to deallocate gracefully. Action: Check the reason for deallocation. Consult the SNA LOG data. ORA-06616: LU6.2 Driver: Attach to LU failed Cause: The SQL*Net LU6.2 driver was unable to attach to the LU specified in the connect string, or was unable to attach to the default LU. Action: Check that the LU name specified in the connect string, or the default LU name if no LU was specified, is correctly configured and operational. ORA-06622: LU6.2 Driver: Unable to attach to SNA Cause: The SQL*Net LU6.2 driver could not attach to the SNA software on your machine. The most likely cause is that the SNA software is not operational. Action: Check the status of the SNA software, ensure that it is operational and then try again. ORA-06700: TLI Driver: incorrect message type from host Cause: TLI received a message with an unrecognizable message type. Action: Contact your customer support representative. ORA-06701: TLI Driver: incorrect number of bytes written Cause: TLI sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes supplied to the driver. Action: Contact your customer support representative. ORA-06702: TLI Driver: cannot allocate context area Cause: TLI could not allocate heap space for the context area. Action: Contact your customer support representative. ORA-06703: TLI Driver: send break message failed Cause: TLI failed to send a break message across the connection. Action: Contact your customer support representative. ORA-06704: TLI Driver: receive break message failed Cause: TLI failed to receive an expected break message. Action: Contact your customer support representative. ORA-06705: TLI Driver: remote node is unknown Cause: TLI could not find your remote host information. Action: Make sure you specified the hostname correctly on the command line. (Also, check your capitalization and spelling.) ORA-06706: TLI Driver: service not found Cause: TLI could not find service information for the specified service name. Action: If you specified the service name on the command line or with the environment variable TLI_SERVER, make sure you specified it correctly. If the service name is not in the SERVICES file for your protocol, ask your system adminstrator to add it. ORA-06707: TLI Driver: connection failed Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server due to an error encountered by the remote server, which has supplied a string describing the remote error. Action: See the SQL*Net TCP/IP User"s Guide section "orasrv Messages" for the specific cause and action. ORA-06708: TLI Driver: message receive failure Cause: TLI encountered an error receiving a message from the communication channel. Action: Contact your customer support representative. ORA-06709: TLI Driver: message send failure Cause: TLI encountered an error sending a message across the communication channel. Action: Contact your customer support representative. ORA-06710: TLI Driver: send interrupt break message failed Cause: TLI failed to send a break message while handling an interrupt signal from the user. Action: Contact your customer support representative. ORA-06711: TLI Driver: error on bind Cause: TLI failed to assign a network address to the communication channel. Action: Contact your customer support representative. ORA-06712: TLI Driver: error on accept Cause: TLI failed to accept a connection request from the client. Action: Contact your customer support representative. ORA-06713: TLI Driver: error on connect Cause: TLI failed to connect the client to the remote server. The network line to the remote host may be down. Action: Use other network login programs to make sure that the remote host is accessible. ORA-06720: TLI Driver: SID lookup failure Cause: The database SID supplied in the database login string was not recognized by the remote host. Action: Ask your system administrator to add the appropriate SID entry to oratab on the remote host. ORA-06721: TLI Driver: spurious client req Cause: The remote TLI server received an undefined request. Action: Contact your customer support representative. ORA-06722: TLI Driver: connection setup failure Cause: The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message. Action: Contact your customer support representative. ORA-06730: TLI Driver: unable to open clone device Cause: TLI failed to open the Streams clone device associated with the transport provider. Action: Contact your customer support representative. ORA-06731: TLI Driver: cannot alloc t_call Cause: TLI cannot allocate space for the client"s connection information. Action: Contact your customer support representative. ORA-06732: TLI Driver: cannot alloc t_discon Cause: TLI cannot allocate space for the client"s disconnection information. Action: Contact your customer support representative. ORA-06733: TLI Driver: failed to receive disconnect Cause: TLI failed to receive an expected disconnection message during connection release. Action: Contact your customer support representative. ORA-06734: TLI Driver: cannot connect Cause: TLI failed to connect the client to the remote server. Action: Check that the remote TLI server is running. ORA-06735: TLI Driver: client failed to close error conn Cause: TLI failed to properly close a connection after an error was received. Action: Contact your customer support representative. ORA-06736: TLI Driver: server not running Cause: TLI timed out while attempting to connect to the remote TLI server. Action: Check that the remote TLI server is running with the status utility for the transport provider you are using. If it is not, ask your system adminstrator to start it. ORA-06737: TLI Driver: connection failed Cause: TLI could not establish a connection to the remote TLI server. Action: Check that the remote TLI server is running with the status utility for the transport provider you are using. ORA-06741: TLI Driver: unable to open protocol device Cause: The TLI server failed to open the Streams device associated with the transport provider. Action: Contact your customer support representative. ORA-06742: TLI Driver: cannot alloc t_bind Cause: The TLI server cannot allocate space for its requested network address. Action: Contact your customer support representative. ORA-06743: TLI Driver: cannot alloc t_bind Cause: The TLI server cannot allocate space for its actual network address. Action: Contact your customer support representative. ORA-06744: TLI Driver: listener cannot bind Cause: The TLI server failed to assign the correct network address on which to listen for connections. Action: Contact your customer support representative. ORA-06745: TLI Driver: listener already running Cause: The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running. Action: Ensure that the TLI server is not already running. If it is not running and this error message recurs, contact your customer support representative. ORA-06746: TLI Driver: cannot alloc t_call Cause: TLI cannot allocate space for the TLI server"s connection information. Action: Contact your customer support representative. ORA-06747: TLI Driver: error in listen Cause: The TLI server encountered an error while listening for connection requests. Action: Contact your customer support representative. ORA-06748: TLI Driver: cannot allocate t_discon Cause: TLI cannot allocate space for the TLI server"s disconnection information. Action: Contact your customer support representative. ORA-06749: TLI Driver: option not allowed across network Cause: The requested TLI server command must be issued from the same host on which the server is running. Action: Log in to the remote host and try again. ORA-06750: TLI Driver: sync failed Cause: The ORACLE process started by the TLI server was unable to synchronize its inherited connection. Action: Contact your customer support representative. ORA-06751: TLI Driver: bound addresses unequal Cause: The osn check server address failed. The bound server address was not the same as the requested binding address. Action: Contact your customer support representative. ORA-06752: TLI: error in signal setup Cause: A call to sigaction() returned with a system error. Action: Contact your customer support representative. ORA-06753: TLI Driver: name-to-address mapping failed Cause: For SVR4, the netdir_getbyname() call failed for some unknown reason. Action: Contact your custumer service representative. ORA-06754: TLI Driver: unable to get local host address Cause: The name of the remote host to connect to was not specified, and the name of the local host cannot be retrieved from the HOSTS file. Action: Contact your system administrator. ORA-06755: TLI Driver: cannot close transport endpoint Cause: The TLI server was unable to close a connection after passing it to an ORACLE process. Action: Contact your customer support representative. ORA-06756: TLI Driver: cannot open oratab Cause: The TLI server could not open the file used to define the locations of remotely accessible databases. Action: Ask your system administrator to check that the file exists and has the correct permissions. ORA-06757: TLI Driver: server got bad command Cause: The TLI server received an invalid command. Action: Contact your customer support representative. ORA-06760: TLI Driver: timeout reading orderly release Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06761: TLI Driver: error sending orderly release Cause: TLI encountered an error sending a disconnect message closing the communication channel. Action: Contact your customer support representative. ORA-06762: TLI Driver: error reading orderly release Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06763: TLI Driver: error sending disconnect Cause: TLI encountered an error sending a disconnect message closing the communication channel. Action: Contact your customer support representative. ORA-06764: TLI Driver: error reading disconnect Cause: TLI was not able to retreive an expected disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06765: TLI Driver: error awaiting orderly release Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel. Action: Contact your customer support representative. ORA-06766: TLI Driver: close failed during release Cause: TLI failed to close the communication channel after receiving a disconnect message. Action: Contact your customer support representative. ORA-06767: TLI Driver: alloc failed during release Cause: TLI cannot allocate space for disconnection information while closing the communication channel. Action: Contact your customer support representative. ORA-06770: TLI Driver: error sending version Cause: TLI encountered an error while sending its version information during connection establishment. Action: Contact your customer support representative. ORA-06771: TLI Driver: error reading version Cause: TLI encountered an error while awaiting the expected version information during connection establishment. Action: Contact your customer support representative. ORA-06772: TLI Driver: error sending command Cause: TLI encountered an error while sending a command message during connection establishment. Action: Contact your customer support representative. ORA-06773: TLI Driver: error reading command Cause: TLI encountered an error while awaiting the expected command message during connection establishment. Action: Contact your customer support representative. ORA-06774: TLI Driver: error sending break mode Cause: TLI encountered an error while sending break-mode message during connection establishment. Action: Contact your customer support representative. ORA-06775: TLI Driver: error reading break mode Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment. Action: Contact your customer support representative. ORA-06776: TLI Driver: error sending parms Cause: TLI encountered an error while sending the connection parameters during connection establishment. Action: Contact your customer support representative. ORA-06777: TLI Driver: error reading parms Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment. Action: Contact your customer support representative. ORA-06778: TLI Driver: error sending ccode Cause: TLI encountered an error while sending the completion status message during connection establishment. Action: Contact your customer support representative. ORA-06779: TLI Driver: error reading ccode Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment. Action: Contact your customer support representative. ORA-06780: TLI Driver: recv error code failed Cause: TLI encountered an error while awaiting an expected error message during connection establishment. Action: Contact your customer support representative. ORA-06781: TLI Driver: error reading negotation string Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment. Action: Contact your customer support representative. ORA-06790: TLI Driver: poll failed Cause: TLI was unable to poll the communication channel for possible incoming messages. Action: Contact your customer support representative. ORA-06791: TLI Driver: poll returned error event Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages. Action: Contact your customer support representative. ORA-06792: TLI Driver: server cannot exec oracle Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client. Action: Note the operating system error message or number and contact your system adminstrator. The permissions on the remote ORACLE program may be set incorrectly. ORA-06793: TLI Driver: server cannot create new process Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client. Action: Note the operating system error message or number and contact your system adminstrator. The remote host may be unable to create any new processes due to a full process table. ORA-06794: TLI Driver: shadow process could not retrieve protocol info Cause: The ORACLE process either failed to allocate memory to store the protocol information record, or the protocol rejected the request for some unknown reason. Action: Contact your customer support representative. ORA-06800: TLI Driver: SQL*Net SPX client went away during reconnect Cause: The client process was aborted by the system or the user, and was unable to complete the connection establishment with the server listener process. Action: Determine cause of client exit, and reattempt connection. ORA-06801: TLI Driver: listen for SPX server reconnect failed Cause: An unknown event occurred on the client"s listening socket. Action: Contact your customer support representative. ORA-06802: TLI Driver: could not open the /etc/netware/yellowpages file Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process. Action: Insure the file exists and is readable. Make sure that the server machine"s node name, network number, ethernet address, and listening socket number are encoded in the file. ORA-06803: TLI Driver: the IPX device file could not be opened Cause: The /dev/ipx file does not exist, or the driver has not been installed in the kernel correctly. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06804: TLI Driver: could not bind an IPX address at initialization Cause: The IPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06805: TLI Driver: could not send datagram SAP packet for SPX Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason. Action: Contact your customer support representative. ORA-06806: TLI Driver: could not complete protocol initialization for SPX Cause: A step in the SPX/IPX protocol initialization failed. Action: Check the previous error reported, and follow corrective action. ORA-06807: TLI Driver: could not open ethernet device driver file Cause: The file /dev/eth does not exist, or the driver it references could not be opened. Action: The system"s real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers. ORA-06808: TLI Driver: could not link IPX and ethernet streams Cause: Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported. Action: Insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers. ORA-06809: TLI Driver: could not clear the IPX ethernet SAP at init Cause: The IPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06810: TLI Driver: could not set the IPX ethernet SAP at init Cause: The IPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06811: TLI Driver: could not set the IPX network number at init Cause: The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid. Action: The network number in the yellowpages file should match the four-byte network number of your Novell file server. If this is configured correctly, reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06812: TLI Driver: could not read the ethernet driver"s node address Cause: The ethernet driver is not installed correctly, or does not support this operation. Action: Contact your customer support representative for a list of supported ethernet drivers. ORA-06813: TLI Driver: the configured ethernet address is incorrect Cause: The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server. Action: Confirm the correct ethernet node address for your LAN card, and enter this value in the yellowpages file. ORA-06814: TLI Driver: the SPX device file could not be opened Cause: The /dev/nspxd file does not exist, or the driver has not been installed in the kernel correctly. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06815: TLI Driver: could not link SPX and IPX streams Cause: The SPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06816: TLI Driver: could not set the SPX SAP address Cause: The SPX driver has not been correctly installed. Action: Reinvoke the Oracle root installation. If problem continues, contact your customer support representative. ORA-06817: TLI Driver: could not read the Novell network address Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and writing. Action: Make sure ORACLE_HOME is set, and the permissions on the ORACLE_HOME are read, write. If this file has been unintentially deleted, run spxctl (net option) to reset the configured Novell network number for SQL*Net SPX. ORA-06900: CMX: cannot read tns directory Cause: CMX is not started on your system. Action: Install and/or start CMX on your system. ORA-06901: CMX: no local name assigned to local application Cause: Local application oracmx has no local name assigned Action: Enter unique local name for oracmx in the tns directory ORA-06902: CMX: cannot attach to cmx subsystem Cause: ccp-xxxx is not started Action: start your ccp software on the communication controller ORA-06903: CMX: cannot read transport address of remote application Cause: remote application not entered in tns directory Action: enter remote application in tns directory ORA-06904: CMX: no transport address available for remote application Cause: no local name assigned to remote application Action: assign local name to remote application ORA-06905: CMX: connect error Cause: remote partner not listening Action: make sure remote node has CMX installed and running make sure oracmx is running on remote host ORA-06906: CMX: cannot get maximum packet size from CMX Cause: internal error in CMX Action: contact your customer support representative ORA-06907: CMX: error during connect confirmation Cause: remote partner aborted Action: contact your customer support representative ORA-06908: CMX: error during transfer of ORACLE_SID Cause: remote partner aborted Action: contact your customer support representative ORA-06909: CMX: error during acknowledge of ORACLE_SID Cause: remote partner aborted Action: contact your customer support representative ORA-06910: CMX: Cannot start oracle process on remote machine Cause: oracle process not found or wrong mode (should be 4751) Action: change /etc/oratab or set mode to 4751 ORA-06911: CMX: t_event returns ERROR Cause: internal error in CMX Action: contact your customer support representative ORA-06912: CMX: write error in datarq Cause: internal error in CMX Action: contact your customer support representative ORA-06913: CMX: error during redirection of connection Cause: oracmx has been stopped, or user process has been aborted Action: contact your customer support representative ORA-06914: CMX: unexepected event during start of oracle Cause: connect sequence out of sync Action: contact your customer support representative ORA-06915: CMX: unknown t_event in datarq Cause: internal error in CMX Action: contact your customer support representative ORA-06916: CMX: error in data read (t_datain) Cause: remote partner aborted Action: contact your customer support representative ORA-06917: CMX: error in data read (too many bytes read) Cause: internal error in CMX Action: contact your customer support representative ORA-06918: CMX: T_NOEVENT during wait for read event Cause: internal error in CMX Action: contact your customer support representative ORA-06919: CMX: error during write request (unknown event) Cause: internal error in CMX Action: contact your customer support representative ORA-06920: CMX: getbrkmsg illegal datatype Cause: received packets are corrupted Action: contact your customer support representative ORA-06921: CMX: getdatmsg illegal datatype Cause: received packets are corrupted Action: contact your customer support representative ORA-06922: CMX: bad write length Cause: internal error in CMX Action: contact your customer support representative ORA-06923: CMX: illegal break condition Cause: break handling out of sync Action: contact your customer support representative ORA-06924: CMX: wrong break message length Cause: received packets are corrupted Action: contact your customer support representative ORA-06925: CMX: disconnect during connect request Cause: partner is not responding Action: make sure partner is up and running and reachable ORA-06926: CMX: T_ERROR during read data Cause: internal error in CMX Action: contact your customer support representative ORA-06927: CMX: T_DATAIN received before all data written Cause: internal error in CMX Action: contact your customer support representative ORA-06928: CMX: wrong ORACLE_SID Cause: ORACLE_SID is not entered in remote oratab Action: add ORACLE_SID to remote oratab ORA-06929: CMX: error when sending ORACLE_SID Cause: internal error in CMX Action: contact your customer support representative ORA-06930: CMX: error when checking ORACLE_SID Cause: internal error in CMX Action: contact your customer support representative ORA-06931: CMX: error during read_properties for server Cause: internal error in CMX Action: contact your customer support representative ORA-06932: CMX: error in local name Cause: internal error in CMX Action: contact your customer support representative ORA-06933: CMX: error during attach Cause: internal error in CMX Action: contact your customer support representative ORA-06950: No error Cause: SQL*Net AppleTalk error codes base. This is not an error. Action: None. ORA-06951: Operating system call error Cause: AppleTalk API received error in VMS system service. Action: Contact Oracle Customer Support representative. ORA-06952: Remote end of the communication issued a forward-reset packet. Cause: Peer program may have aborted Action: Investigate network problems and try again. ORA-06953: Not enough virtual memory Cause: Not enough memory available. Action: Check VMS process quotas and/or sysgen parameters ORA-06954: Illegal file name Cause: Erroneous file name Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols. ORA-06955: Number of database servers exceed limit Cause: Too many database connections. Action: Check ATKSRV_MAXCONparameter in configuration file. ORA-06956: Failed to get local host name Cause: Unable to get Appletalk host name. Action: Check Appletalk configuration. ORA-06957: No SID is currently available Cause: Incoming SQL*Net connection specified invalid SID name. Action: Specify correct SID in connect string and retry. ORA-06958: Failed to access configuration file Cause: Unable to access CONFIG.ATK Action: Check file protections. ORA-06959: Buffer I/O quota is too small Cause: Buffered I/O quota exceeded. Action: Increase BIOlm using AUTHORIZE utility and retry. ORA-06960: Failed to access log file Cause: SQL*Net Appletalk listener could not create log file. Action: Check directory path and protections. ORA-06970: X.25 Driver: remote host is unknown Cause: Host name specified in the login (connect string) is unknown. Action: Check spelling; make sure name is in the X.25 HOST file. ORA-06973: X.25 Driver: invalid buffer size Cause: The buffer size specified in the login string must be between 5 and 4096. Action: Re-submit with valid buffer size. ORA-06974: X.25 Driver: SID lookup failure Cause: From the remote host"s SQL*Net X.25 server: the database SID, specified in the login (connect) string, was not recognized. Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net X.25 server). ORA-06975: X.25 Driver: connect to host failed Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net X.25 server on the remote host is not up, or the host itself is not up. Action: Start the SQL*Net X.25 server process on the remote host. ORA-06976: X.25 Driver: endpoint creation failure Cause: Process open file quota probably exceeded. Action: Contact your customer support representative. ORA-06977: X.25 Driver: X.25 Level 2 failure Cause: X.25 level 2 is down. X.25 link is not working. Action: Run system checks to verify functioning of X.25 software. Contact your hardware vendor. ORA-06978: X.25 Driver: Too many callback tries Cause: Call back address probably same as called address. Action: Verify that callback address and called address are different. ORA-06979: X.25 Driver: server cannot start oracle Cause: The remote X.25 server was unable to start an ORACLE process on behalf of the client. Action: Make sure permissions on the remote ORACLE program are correctly set. Contact your system administrator. ORA-07200: slsid: oracle_sid not set. Cause: The environment variable $(ORACLE_SID) is not set. Action: Set ORACLE_SID environment variable. ORA-07201: slhom: oracle_home variable not set in environment. Cause: $(ORACLE_HOME) environment variable not set. Action: Set ORACLE_HOME. ORA-07202: sltln: invalid parameter to sltln. Cause: The sltln name translation routine was called with invalid arguments. The input, or output stings were either NULL or 0 length. Action: Probable internal oracle error. Contact customer support. ORA-07203: sltln: attempt to translate a long environment variable. Cause: A string was passed to sltln containing a long environment variable. sltln accepts environment names of 30 or less characters. Action: Shorten environment variable name to less than 30 characters. ORA-07204: sltln: name translation failed due to lack of output buffer space. Cause: The sltln routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. Action: Possible internal error. Check output buffer length stored in sercose[0]. Pathnames are limited to 255 characters. ORA-07205: slgtd: time error, unable to obtain time. Cause: Time() system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07206: slgtd: gettimeofday error, unable to obtain time. Cause: Gettimeofday() system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07207: sigpidu: process ID string overflows internal buffer. Cause: The sigpidu routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. Action: Internal error. Contact customer support. ORA-07208: sfwfb: failed to flush dirty buffers to disk. Cause: The fsync system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07209: sfofi: file size limit was exceeded. Cause: The size of the file to be opened exceeded the OS limit imposed on this process. Action: Run osh to increase the file size limit. ORA-07210: slcpu: getrusage error, unable to get cpu time. Cause: Getrusage system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07211: slgcs: gettimeofday error, unable to get wall clock. Cause: Gettimeofday system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07212: slcpu: times error, unable to get cpu time. Cause: times system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07213: slgcs: times error, unable to get wall clock. Cause: times system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07214: slgunm: uname error, unable to get system information. Cause: uname system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07215: slsget: getrusage error. Cause: Getrusage system call returned an error. Possible OS error. Action: Check additional information returned. Look for information in OS reference. Contact customer support. ORA-07216: slghst: gethostname error, unable to get name of current host. Cause: gethostname system call returned an error. Possible OS error. Action: Check additional information returned in OS reference manual. Contact customer support. ORA-07217: sltln: environment variable cannot be evaluated. Cause: getenv call returned a null pointer. Action: Set the environment variable and try again. ORA-07218: slkhst: could not perform host operation Cause: Unix system() call failed Action: Examine system error message ORA-07219: slspool: unable to allocate spooler argument buffer. Cause: Malloc failed to allocate space to hold spooler arguments. Action: Check additional information returned in OS reference manual. The process may have run out of heap space. Contact customer support. ORA-07220: slspool: wait error. Cause: Wait returned an error, when waiting for spool job to complete. Possible spooler program error. Action: Check additional information returned. Refer to OS reference manual. Contact customer support. ORA-07221: slspool: exec error, unable to start spooler program. Cause: Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set. Action: Verify default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler. ORA-07222: slspool: line printer spooler command exited with an error. Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file. Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit value returned as additional informatin. ORA-07223: slspool: fork error, unable to spawn spool process. Cause: Fork system call failed to create additional process. Probable resource limit reached. Action: Check additional information returned. Retry operation. Contact system administrator. ORA-07224: sfnfy: failed to obtain file size limit; errno = string. Cause: The ulimit system call returned an error. Action: Check errno and contact customer support. ORA-07225: sldext: translation error, unable to expand file name. Cause: Additional information returned is error returned from sltln. Action: Check additional information. ORA-07226: rtneco: unable to get terminal mode. Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07227: rtneco: unable to set noecho mode. Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07228: rtecho: unable to restore terminal to echo mode. Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07229: slcpuc: error in getting number of CPUs. Cause: error in mpcntl system call Action: check errno and contact system administrator ORA-07230: slemcr: fopen error, unable to open error file. Cause: Fopen failed to open file. Action: Try to determine which file was not opened. Check that file exists and is accessible. ORA-07231: slemcc: invalid file handle, seals do not match. Cause: Function was called with an invalid argument. The file handle used was not obtained be slemcr. Action: Internal error. Contact customer support. ORA-07232: slemcc: fclose error. Cause: An error was encountered when closing the file. Possible OS error. Action: Contact system administator. ORA-07233: slemcw: invalid file handle, seals do not match. Cause: Function was called with an invalid file handle. File handle was not obtained by slemcr. Action: Internal error. Contact customer support. ORA-07234: slemcw: fseek error. Cause: Unable to seek to desired position in file. Possible OS error. Possible internal error. Action: Verify that error message file is intact. Try to regenerate error message file. Contact customer support. ORA-07235: slemcw: fwrite error. Cause: Unable to write item to file. Possible OS error. Possible permissions problem. Action: Retry operation. ORA-07236: slemop: open error. Cause: Unable to open error file. Possible permissions problem. Action: Verify permission on error message file. Check additional information for errno. ORA-07237: slemcl: invalid file handle, seals do not match. Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to slemop. Action: Internal error. ORA-07238: slemcl: close error. Cause: Unable to close file. Possible OS error. Action: Contact system administator. Check additional information for errno. ORA-07239: slemrd: invalid file handle, seals do not match. Cause: Function was called with invalid file handle. Handle was not obtained by call to slemop. Action: Internal error. Contact customer support. ORA-07240: slemrd: seek error. Cause: Unable to seek to desired position in file. Possible OS error. Action: Check that error file is still intact. Verify space on device. Contact system administrator. Check additional information for errno. ORA-07241: slemrd: read error. Cause: Unable to read file. Possible OS error. Action: Verify that error file is intact. Regenerate error message file. Contact customer support. Check additional information for errno. ORA-07242: slembfn: translation error, unable to translate error file name. Cause: Additional information indicates error returned from sltln. Action: Check additional information. ORA-07243: supplied buffer not big enough to hold entire line Cause: supplied buffer was not big enough Action: Internal error. Contact customer support. Additional information indicates how big the supplied buffer was. ORA-07244: ssfccf: create file failed, file size limit reached. Cause: An attempt was made to create a file that exceeds the process"s file size limit. Action: Run osh to raise the file size limit. ORA-07245: sfccf: unable to lseek and write the last block. Cause: An attempt was made to move and write to a bad device address. Action: Check errno. Possible lack of space on device. ORA-07246: sfofi: open error, unable to open database file. Cause: sfofi returns an error. Action: This is an oracle internal error. ORA-07247: skgfrfms, skgfrnms: read error, unable to read block from database file Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS. Action: Check errno. ORA-07248: sfwfb: write error, unable to write database block. Cause: sfwfb returns an error. Action: This is an oracle internal error. ORA-07249: slsget: open error, unable to open /proc/pid. Cause: The open() system call returned an error. Action: Check that /proc has the right permissions. ORA-07250: spcre: semget error, unable to get first semaphore set. Cause: An error occurred when trying to get first semaphore set. Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested. ORA-07251: spcre: semget error, could not allocate any semaphores. Cause: Semget failed to even allocate a single semaphore. Either they are all in use or the system is not configured to have any semaphores. Action: Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Check errno. ORA-07252: spcre: semget error, could not allocate semaphores. Cause: Semget system call returned an error. Possible resource limit problem. Action: Check errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using ipcrm. ORA-07253: spdes: semctl error, unable to destroy semaphore set. Cause: Semctl system call returned an error. Action: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult OS reference manual. ORA-07254: spdcr: translation error while expanding ?/bin/oracle. Cause: An error occurred while translating the name of the oracle executable. Action: Check sercose[0] for error returned from sltln. Perhaps $(ORACLE_HOME) is not set correctly. ORA-07255: spini: cannot set up signal handler. Cause: System failed to set up signal handler. Action: Check errno and sercose[0] for the signal number that failed. ORA-07256: sptrap: cannot set up signal handler to catch exceptions. Cause: System failed to set up signal handler to catch exceptions. Action: Check errno and sercose[0] for the signal number that failed. ORA-07257: spdcr: translation error expanding program name. Cause: Error ocurred when expanding program name ora_PNAME_@. The result of this translation is put in argv[0] of oracle process. Action: Check error returned by sltln returned in sercose[0]. ORA-07258: spdcr: fork error, unable to create process. Cause: An error occurred when creating a new process. Action: Check errno. Perhaps a system limit on the number of processes has been exceeded. ORA-07259: spdcr: exec error, detached process failed in startup. Cause: An oracle detached process died shortly after startup. Wait() indicated that a child process terminated. Action: Check ?/dbs directory for trace or core files. Check errno. ORA-07260: spdcr: wait error. Cause: Wait system call returned an error. Action: Check errno. ORA-07261: spdde: kill error, unable to send signal to process. Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process. Action: Check errno. ORA-07262: sptpa: sptpa called with invalid process id. Cause: This is an internal error. Action: This is an oracle internal error. ORA-07263: sptpa: kill error. Cause: Kill system call returned an error. Possible OS error. Action: Check errno. Additional information indicates the process ID tested. ORA-07264: spwat: semop error, unable to decrement semaphore. Cause: Semop system call returned an error. Semaphore set may not exist. Action: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a "shutdown abort" was done while this process was running. ORA-07265: sppst: semop error, unable to increment semaphore. Cause: Semop system call returned an error. Semaphore set may not exist. Action: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set existence. A possible cause for this error is that a "shutdown abort" was done while this process was running. ORA-07266: sppst: invalid process number passed to sppst. Cause: Function was passed an invalid oracle process id. Action: Internal error. ORA-07267: spwat: invalid process number. Cause: Function was passed an invalid oracle process id. Action: Internal error. Additional information indicates the invalid process id. ORA-07268: szguns: getpwuid error. Cause: Getpwuid() could not find an entry in the passwd file for a user. Action: Add an entry for the user in the passwd file. ORA-07269: spdcr: detached process died after exec. Cause: Detached process succesfully execed, but died shortly thereafter. Additional information indicates exit code, and termination status. Action: Check termination code for information as to why process exited. Check for core dump or trace file. ORA-07270: spalck: setitimer error, unable to set interval timer. Cause: An error occurred while trying to set an interval timer. Probable porting problem. Action: Check errno. ORA-07271: spwat: invalid oracle process number. Cause: Function was called with an invalid oracle process number (0). Action: Internal oracle error. ORA-07272: spwat: invalid semaphore set id. Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and oracle process number. Action: Oracle internal error. Check semaphore set index. Check oracle process number. ORA-07273: sppst: invalid semaphore id. Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and oracle process number. Action: Oracle internal error. Check semaphore set index. Check oracle process number. ORA-07274: spdcr: access error, access to oracle denied. Cause: Unable to access "oracle" program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable. Action: Check errno returned. ORA-07275: unable to send signal to process Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist. Action: Check errno. ORA-07276: no dba group in /etc/group. Cause: A group has not been set up for dba users. Action: Contact system administrator. Set up dba group in /etc/group. ORA-07277: spdde: illegal pid passed as argument. Cause: A 0 pid was passed to spdde. Action: Internal error. . ORA-07278: splon: ops$username exceeds buffer length. Cause: Splon constructed an ops$username logon which exceeded the alloted buffer space. Action: Use a shorter Unix username, or use an oracle username. Contact customer support. ORA-07279: spcre: semget error, unable to get first semaphore set. Cause: An error occurred when trying to get first semaphore set. Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested. ORA-07280: slsget: unable to get process information. Cause: The ioctl call returned an error. Possible OS error. Action: Check additional information for errno. Contact customer support. ORA-07281: slsget: times error, unable to get cpu time. Cause: times system call returned an error. Possible OS error. Action: Check additional information returned. Contact customer support. ORA-07282: sksaprd: string overflow. Cause: The internal buffer is not big enough to hold the archive control string. Action: Internal restriction. Try a shorter archive control string. ORA-07283: sksaprd: invalid volume size for archive destination. Cause: An invalid volume size was specified. Action: Specify a valid volume size in archive control string. ORA-07284: sksaprd: volume size specification not terminated properly. Cause: Some non-numeric text follows the volume size specification. Action: Enter a correct archive control string. ORA-07285: sksaprd: volume size should not be specified for a disk file. Cause: Volume size was specified for a disk file. Action: If you are archiving to a disk file, do not specify its volume size. ORA-07286: sksagdi: cannot obtain device information. Cause: Stat on the log archiving device failed. Action: Check the returned OSD error for the reason of failure. ORA-07287: sksagdi: unsupported device for log archiving. Cause: Log archiving to this device is unsupported. Action: Try log archiving to a supported device. ORA-07290: sksagdi: specified directory for archiving does not exist. Cause: The specified pathname is not a directory. Action: Verify that the archive destination directory exists. ORA-07303: ksmcsg: illegal database buffer size. Cause: The database buffer size must be a multiple of the database block size, and less than the maximum block size. Action: Verify that the db_block_size parameter is correct in INIT.ORA. ORA-07304: ksmcsg: illegal redo buffer size. Cause: The redo buffer size must be a multiple of machine block size. Action: Verify that the log_buffer INIT.ORA parameter is correctly set. ORA-07305: ksmcsg: illegal database buffer size. Cause: The database buffer size must be a multiple of the extended cache mapping size for indirect data buffers to be used. Action: Verify that the db_block_size parameter is correct in INIT.ORA, or disable the use_indirect_data_buffers parameter. ORA-07324: smpall: malloc error while allocating pga. Cause: Malloc library routine returned an error. Action: Check errno. Possibly out of swap space. ORA-07327: smpdal: attempt to destroy pga when it was not mapped. Cause: Smpdal was called when the PGA had not been previously created. Action: Internal error. ORA-07339: spcre: maximum number of semaphore sets exceeded. Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested. Action: Reconfigure OS to have more semaphores per set. ORA-07345: The datafile name must not contain the string "..". Cause: The specified datafile name contains "..". Action: Correct the datafile name and retry the operation. ORA-07346: slnrm: normalized file name is too long Cause: After normalizing the specified file name, the resulting file name was too long. Action: Specify the shorter file name and retry the operation. ORA-07390: sftopn: translate error, unable to translate file name. Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine. Action: Lookup additional error code for further information. ORA-07391: sftopn: fopen error, unable to open text file. Cause: Fopen library routine returned an error. Action: Verify existence and permissions. ORA-07392: sftcls: fclose error, unable to close text file. Cause: Fclose library routine returned an error. Action: Possible internal oracle error. ORA-07393: unable to delete text file Cause: An error occurred while deleting a text file. Action: Verify that the file exists and check additional errors. ORA-07394: unable to append string to text file Cause: An error occurred while performing a string put operation. Action: This is an internal error. Check additional information. ORA-07400: slemtr: translated name for the message file is too long. Cause: The name for the message file overflows internal buffer. Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy. ORA-07401: sptrap: cannot restore user exception handlers. Cause: The system failed to restore user exception handlers. Action: Check errno and sercose[0] for the signal number that failed. ORA-07402: sprst: cannot restore user signal handler. Cause: The system failed to restore user signal handlers. Action: Check errno and sercose[0] for the signal number that failed. ORA-07403: sfanfy: db_writers parameter not valid. Cause: The db_writers parameter in INIT.ORA exceeds the system-dependent maximum or is less than 0. Action: Change the db_writers parameter in INIT.ORA. ORA-07404: sfareq: Timeout occurred waiting for request to complete. Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running. Action: Check all database writer trace files. Shut down the database and try to warm start. ORA-07405: sptrap: cannot setup alternate signal stack. Cause: The system failed to setup an alternate signal stack. Action: Check errno and sercose[0] for the location where it failed. ORA-07406: slbtpd: invalid number. Cause: An impossible request for binary to decimal conversion was made. Action: This conversion cannot be performed. ORA-07407: slbtpd: invalid exponent. Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed. ORA-07408: slbtpd: overflow while converting to packed decimal. Cause: An impossible request for binary to decimal conversion was made. Action: This conversion cannot be performed. ORA-07409: slpdtb: invalid packed decimal nibble. Cause: An impossible request for decimal to binary conversion was made. Action: This conversion cannot be performed. ORA-07410: slpdtb: number too large for supplied buffer. Cause: An impossible request for decimal to binary conversion was made. Action: This conversion cannot be performed. ORA-07411: slgfn: full path name too big for supplied buffer. Cause: The supplied buffer is not big enough to hold the full path name. Action: The construction of the full path name cannot be performed. ORA-07412: sfaslv: Error getting entry in asynchronous write array. Cause: One of the database writer processes could not locate its entry in the SGA. Action: Contact customer support. ORA-07415: slpath: allocation of memory buffer failed. Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. Action: System has run out of heap space. Additional information indicates errno. ORA-07416: slpath: pathname construction failed; lack of output buffer space. Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. Action: Possible internal error. Check output buffer length stored in sercose[0] and constructed pathname length in sercose[1]. ORA-07417: sfareq: One or more database writers not active. Cause: One or more of the database writer processes is no longer running. Action: Check the trace files for the database writers. Shut down the database and try to warm start. ORA-07418: sfareq: Database writer got error in timing function. Cause: An error occurred when the database writer called the system timing function. Action: Check the database writer trace file. Shut down database and try to warm start. ORA-07419: sfareq: Database writer got error in timing function. Cause: An error occurred when the database writer called the system timing function. Action: Check the database writer trace file. Shut down database and try to warm start. ORA-07425: sdpri: error string in translating dump file location. Cause: An oracle error occurred when translating the location of the dump file. Action: Check the oracle error code. ORA-07426: spstp: cannot obtain the location of dbs directory. Cause: An oracle error occurred when translating the location of the dbs directory. Action: Check additional information for the error returned from sltln. ORA-07427: spstp: cannot change directory to dbs. Cause: Chdir system call returned an error. Possible permission problems. Action: Check additional information for the OS error code. ORA-07431: fork failed Cause: The server process was unable to fork a child process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-07432: unable to perform nested sleep Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability. Action: Try the SLEEP command when the process is not sleeping. ORA-07440: WMON process terminated with error Cause: The wakeup monitor process died. Action: Warm start instance. ORA-07441: function address must be aligned on string byte boundary Cause: An improperly aligned function address was specified. Action: Use a properly aligned function address. ORA-07442: function address must be in the range string to string Cause: An invalid function address was specified. Action: Use a valid function address. ORA-07443: function string not found Cause: An invalid function name was specified. Action: Use a valid function name. ORA-07444: function address string is not readable Cause: An invalid function name/address was specified. Action: Use a valid function name/address. ORA-07445: exception encountered: core dump [string] [string] [string] [string] [string] [string] Cause: An OS exception occurred which should result in the creation of a core file. This is an internal error. Action: Contact your customer support representative. ORA-07446: sdnfy: bad value "string" for parameter string. Cause: The directory specified as the value for the stated parameter could not be used. Action: Make sure the directory you have specified is a valid directory/file specification. ORA-07447: ssarena: usinit failed. Cause: Oracle failed to create a shared arena file. Action: Use sercerrno field to determine cause of failure. ORA-07448: ssarena: maximum number of shared arenas exceeded. Cause: Oracle attempted to create more shared arena files than permitted. Action: Raise the value for max_arena in INIT.ORA. ORA-07449: sc: usnewlock failed. Cause: Oracle failed to acquire a shared arena lock. Action: Check result code in sercerrno to determine the cause of failure. ORA-07451: slskstat: unable to obtain load information. Cause: kstat library returned an error. Possible OS failure Action: Check result code in sercose[0] for more information. ORA-07452: specified resource manager plan does not exist in the data dictionary Cause: User tried to load a resource manager plan that does not exist. Action: Use a resource manager plan that exists in the data dictionary. ORA-07453: requested resource manager plan schema does not contain OTHER_GROUPS Cause: User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group. Action: Use a resource manager plan schema that contains the OTHER_GROUPS group. ORA-07454: queue timeout, string second(s), exceeded Cause: User session queued for longer than maximum specified queue queue duration time for consumer group. Action: Re-submit job at a later time or increase queue timeout. ORA-07455: estimated execution time (string secs), exceeds limit (string secs) Cause: User attempted to execute an operation whose estimated execution time exceeds the limit specified for the consumer group. Action: Execute job on behalf of another group, or increase limit. ORA-07456: cannot set RESOURCE_MANAGER_PLAN when database is closed Cause: An attempt was made to turn on the Resource Manager when the database was closed. Action: Open the database and try again. ORA-07457: cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix. Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter. ORA-07458: cannot set the RESOURCE_MANAGER_PLAN parameter Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the database was quiesced. Action: Unquiesce the database. ORA-07459: cannot restore the RESOURCE_MANAGER_PLAN parameter Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it was internally set. This failed because the current plan was set by the user and therefore did not need to be restored. Action: No action needed. ORA-07460: cannot set the RESOURCE_MANAGER_PLAN parameter Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix. Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter. ORA-07468: spwat: mset error, unable to set semaphore. Cause: The mset routine returned an error. Semaphore may not exist. Action: Check result code in sercerrno. Semaphore number returned in sercose[0]. ORA-07469: sppst: mclear error, unable to clear semaphore. Cause: The mclear routine returned an error. Semaphore may not exist. Action: Check result code in sercerrno. Semaphore number returned in sercose[0]. ORA-07470: snclget: cannot get cluster number. Cause: The cluster_status system call failed to get status information for the current cluster. Action: Check result code in sercose[0]. Possible operating system failure. ORA-07471: snclrd: name translation error of sgadef.dbf file name. Cause: Unable to expand out ?/dbs/sgadef@.dbf file name. Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check error number returned from sltln in sercose[0]. ORA-07472: snclrd: open error when opening sgadef.dbf file. Cause: open failed when opening the file ?/dbs/sgadef@.dbf Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists. ORA-07473: snclrd: read error when trying to read sgadef.dbf file. Cause: Read had an error when reading sgadef.dbf file. Action: Check errno. Verify file exists, and is correct size. ORA-07474: snclrd: close error, unable to close sgadef.dbf file. Cause: An error occurred in close, while closing the file "?/dbs/sgadef@.dbf" Action: Check errno. Possible operating system error. ORA-07475: slsget: cannot get vm statistics. Cause: The vm_statistics system call failed to get virtual memory statistics. Action: Check result code in sercerrno. Possible operating system failure. ORA-07476: slsget: cannot get mapped memory statistics. Cause: The vm_mapmem system call failed to get mapped memory statistics. Action: Check result code in sercerrno. Possible operating system failure. ORA-07477: scgcmn: lock manager not initialized. Cause: Lock manager must be initialized before converting locks. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07478: scgcmn: cannot get lock status. Cause: lm_stat_lock failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07479: scgcmn: cannot open or convert lock. Cause: lm_open or lm_open_convert failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07480: snchmod: cannot change permissions on ?/dbs/sgalm.dbf. Cause: When creating an instance, snlmini could not change the permissions on ?/dbs/sgalm.dbf Action: Contact your customer support representative. ORA-07481: snlmatt: cannot attach to lock manager instance. Cause: lm_attach failed to attach to lock manager instance. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07482: snlmini: cannot create lock manager instance. Cause: lm_create failed to create lock manager instance. Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry. ORA-07483: snlkget: cannot convert(get) lock. Cause: lm_convert failed to convert(get) lock. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07484: snlkput: cannot convert(put) lock. Cause: lm_convert failed to put lock value. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07485: scg_get_inst: cannot open instance number lock. Cause: lm_open failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07486: scg_get_inst: cannot convert(get) instance number lock. Cause: lm_convert failed to get lock value. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07487: scg_init_lm: cannot create lock manager instance. Cause: lm_create failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07488: scgrcl: lock manager not initialized. Cause: Lock manager must be initialized before releasing locks. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07489: scgrcl: cannot get lock status. Cause: lm_stat_lock failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07490: scgrcl: cannot convert lock. Cause: lm_convert failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07491: scgrcl: cannot cancel lock request. Cause: lm_cancel failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07492: scgrcl: cannot close lock. Cause: lm_close failed during lock release/cancel. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07493: scgrcl: lock manager error. Cause: An error was encountered releasing the lock. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07494: scgcm: unexpected error. Cause: Unknown or unexpected error code. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07495: spwat: lm_wait failed. Cause: lm_wait failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07496: sppst: lm_post failed. Cause: lm_post failed. Action: Check result code in sercerrno. Possible lock manager failure. ORA-07497: sdpri: cannot create trace file "string"; errno = string. Cause: 1. The trace file could not be created for writing. 2. The trace file is a symbolic link. Action: 1. Check if the dump directory exists and whether it is writable. 2. Remove the symbolic link. ORA-07498: spstp: Unable to open /dev/resched. Cause: The rescheduling driver /dev/resched is not found or is not working properly. Action: Check installation of the ORACLE rescheduling driver in the AIX kernel. ORA-07499: spglk: Cannot reschedule. Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur. Action: Contact your customer support representative. 7 ORA-09870 to ORA-12100 ORA-09870: spini: failure initializing maximum number of open files. Cause: ulimit system call returned an error. Action: Check errno. ORA-09871: TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf. Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages. Action: Check additional return error for more information. ORA-09872: TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf. Cause: Create() failed when trying to create the tasdef file. Action: Verify permissions on $(ORACLE_HOME)/dbs directory. ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file. Cause: Unable to open tasdef@.dbf file. Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists. ORA-09874: TASDEF_READ: read error, unable to read tasdef@.dbf file. Cause: Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf. Action: Check errno returned. Sgadef file may be corrupted or incompatible with oracle version. ORA-09875: TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file. Cause: Write call failed. Action: Check errno returned. Possibly out of space on device. ORA-09876: TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file. Cause: Close system call returned an error. Action: Check errno returned. Possible operating system failure. ORA-09877: sstascre: shmget error, unable to get a shared memory segment. Cause: Error in shmget. Action: Check errno returned. Verify that enough shared memory is available on the system. ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page Cause: Error in shmat. Action: Check errno returned.Verify that enough shared memory is available on the system. ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page Cause: Error in shmat. Action: Check errno returned.Verify that enough shared memory is available on the system. ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page Cause: Error in shmdt. Action: Check errno returned. ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page Cause: Error in shmdt. Action: Check errno returned. ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page Cause: Error in shmctl. Action: Check errno returned. ORA-09883: Two Task interface: oratab file does not exist Cause: The oratab file does not exist. Action: Install oracle before you use it or recreate the oratab file. ORA-09884: Two Task interface: SID doens"t match current PU Cause: You are trying to start oracle on another PU than you configured oracle on or there is no entry for this SID in oratab file. Action: Start oracle with this SID on its designated PU (see oratab file). Or install the new database with SID. ORA-09885: osnTXtt: cannot create TXIPC channel Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator. ORA-09886: osnTXtt: translation error while expanding txipc@.trc. Cause: Failure of sltln(txipc@.trc) while creating debug channel. Action: Check additional return error for more information. ORA-09888: osnTXtt: txipc channel creation failed Cause: The txipc driver failed to create channels for two-task communications with the oracle shadow process. Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator. ORA-09889: osnTXtt: access error on oracle executable Cause: The txipc driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. ORA-09890: osnTXtt: malloc failed Cause: The txipx driver failed to allocate enough heap space for its context area buffers. Action: Contact your customer support representative. ORA-09908: slkmnm: gethostname returned error code. Cause: The system call gethostname returned an error. Action: This is most likely an internal error. Make sure gethostname is successful in other contexts, and if so contact Oracle support. ORA-09909: Malloc of scratch buffer failed. Cause: Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that ORACLE attempted to allocate. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support. ORA-09910: Unable to find ORACLE password file entry for user. Cause: No entry exists for the user in the ORACLE password file. Action: Have the database administrator install a password entry by running orapasswd. ORA-09911: Incorrect user password. Cause: The password entered by the user was incorrect. Action: Enter the correct password. ORA-09912: Malloc of name buffer(s) failed. Cause: ORACLE was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support. ORA-09913: Malloc of dummy name failed. Cause: ORACLE was unable to allocate memory for the user name that is to to be used in the encryption of the user"s password. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support. ORA-09914: Unable to open the ORACLE password file. Cause: ORACLE could not open the password file for reading. Action: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact ORACLE customer support. ORA-09915: Password encryption failed. Cause: ORACLE was unable to encrypt a password. Action: This is an internal error - contact ORACLE customer support. ORA-09916: Required password was not specified. Cause: A user attempted to connect as "internal," but did not specify a password. Action: Connect as internal again and specify a password. ORA-09918: Unable to get user privileges from SQL*Net Cause: ORACLE was unable to retrieve the user"s privilege set from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact ORACLE support. ORA-09919: Unable to set label of dedicated server Cause: ORACLE was unable to set the label of the dedicated to server to the required value. Action: Check the UNIX error number for a possible operating system error. Also, check the privileges on the oracle executable. It should have at least "allowmacaccess" privilege. ORA-09920: Unable to get sensitivity label from connection Cause: ORACLE was unable to retrieve the user"s sensitivity label from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact ORACLE support. ORA-09921: Unable to get information label from connection Cause: ORACLE was unable to retrieve the user"s information label from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact ORACLE support. ORA-09922: Can"t spawn process - background log directory not created properly Cause: ORACLE was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly. Action: Examine the directory pointed to by the initialization parameter "background_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user. ORA-09923: Can"t spawn process - user log directory not created properly Cause: ORACLE was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly. Action: Examine the directory pointed to by the initialization parameter "user_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user. ORA-09924: Can"t spawn process - core dump directory not created properly Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly. Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user. ORA-09925: Unable to create audit trail file Cause: ORACLE was not able to create the file being used to hold audit trail records. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support. ORA-09926: Unable to set effective privilege set of the server Cause: A dedicated server was unable to set it"s own privilege set. Action: Check the privileges granted to the ORACLE executable. It must have at least "allowmacacess" privilege. ORA-09927: Unable to set label of server Cause: ORACLE was not able to set the label of a server to a new value. Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has "allowmacaccess" privilege. ORA-09928: Unable to restore the label of server Cause: ORACLE was unable to restore the label of the server to the value that it had before raising it to database high. Action: This is an internal error - contact ORACLE support. ORA-09929: GLB of two labels is invalid Cause: The result of a greatest lower bound operation on two labels was not valid. Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels. ORA-09930: LUB of two labels is invalid Cause: The result of a least upper bound operation on two labels was not valid. Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels. ORA-09931: Unable to open ORACLE password file for reading Cause: An attempt to open a password file for reading failed. Action: Make sure that the permissions on the file have not been changed so that the ORACLE user cannot open it. ORA-09932: Close of ORACLE password file failed. Cause: An attempt to close a password file failed. Action: Check the UNIX error number for the specific reason. ORA-09933: Deletion of old password file failed. Cause: The removal of the old password file failed. Action: Check the UNIX error number for the specific reason. ORA-09934: Link of current password file to old failed. Cause: ORACLE was unable to create a link so that the old password file could be saved. Action: Check the UNIX error number for the specific reason. ORA-09935: Unlink of current password file failed. Cause: ORACLE was unable to complete the saving of the current password file. Action: Check the UNIX error number for the specific reason. ORA-09936: Open of ORACLE password file for write failed. Cause: ORACLE was unable to create a password file. Action: Check the UNIX error number for the specific reason. ORA-09937: Chmod of ORACLE password file failed. Cause: ORACLE was unable to change a password file to be readonly. Action: Check the UNIX error number for the specific reason. ORA-09938: Save of signal handlers failed. Cause: ORACLE was unable to save the previous values of selected signal handlers. Action: This is an internal error. Contact ORACLE support. ORA-09939: Restoration of signal handlers failed. Cause: ORACLE was unable to restore the previous values of selected signal handlers. Action: This is an internal error. Contact ORACLE support. ORA-09940: ORACLE password file header is corrupt Cause: The header of one of the password files was not in the format that ORACLE expected. Action: Check the headers of both files. The header should be in the format "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" where N is a number. Remove the corrupt file(s) and re-run "orapasswd". ORA-09941: Version of orapasswd or installer is older than file. Cause: The version of orapasswd or installer that is being run is older than that of the ORACLE password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created. Action: Run a version of the installer or orapasswd whose version is the same or later than that of the file. ORA-09942: Write of ORACLE password file header failed. Cause: The attempt to write out the header of the ORACLE password file failed. Action: Check the operating system error number. It is possible that the file system became full. ORA-09943: Allocation of memory for password list component failed. Cause: When it is building a list of password file entries, ORACLE allocates memory for various components. One of the allocations failed. Action: Check the operating system error number. The system has probably run out of memory. ORA-09944: Password entry is corrupt. Cause: An entry in an ORACLE password file was not in the format that ORACLE expected. Action: Removed the corrupt file(s) and re-run "orapasswd." ORA-09945: Unable to initialize the audit trail file Cause: ORACLE unable to write header information to the file being used as the audit trail. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support. ORA-09946: File name too long for buffer Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters. Action: Use a shorter file name. ORA-09947: Unable to allocate connection attributes structure Cause: ORACLE was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The "Additional Information" field holds the number of bytes that ORACLE attempted to allocate. Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE customer support. ORA-09948: Process information label retrieval failed. Cause: ORACLE was unable to get the information label for a process. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support. ORA-09949: Unable to get client operating system privileges Cause: ORACLE was unable to get the operating system privileges for the client process. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support. ORA-09950: Unable to get server operating system privileges Cause: ORACLE was unable to get its privileges from the operating system. Action: This is an error that should never happen. Contact ORACLE customer support. ORA-09951: Unable to create file Cause: ORACLE was unable to create a file. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support. ORA-09952: scgcmn: lk_open_convert unexpected return: open failed Cause: The distributed lock manager returned an unexpected value Action: Check for system error message and refer to the distributed lock manager documentation or contact your customer support representative. ORA-09953: scggc: unexpected return of a lock convert Cause: The distributed lock manager returned an unexpected value Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative. ORA-09954: scgcc: unexpected return status to callback of lock close Cause: The distributed lock manager returned an unexpected value Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative. ORA-09955: scgcan: unexpected return status when canceling a lock Cause: DLM system service x returned an unexpected value Action: Check for system error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative. ORA-09956: scgcm: unexpected lock status condition Cause: A global locking system service returned an unexpected value. Action: Check for system error message (if any) and refer to refer to the distributed lock manager documentation or contact your customer support representative. ORA-09957: Unable to send termination request to IMON Cause: The attempt to send a termination signal to IMON failed. Action: This is an internal error, contact ORACLE support. ORA-09958: IMON: two processes with the same ORACLE pid are active Cause: The IMON process was unable to add an entry for a server process because another active process occupies the slot. Action: This is an internal error, contact ORACLE support. ORA-09959: IMON: deletion of a process failed. Cause: The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found. Action: This is an internal error, contact ORACLE support. ORA-09960: Unable to establish signal handler for termination signal Cause: ORACLE was unable to set up a handler for the signal used to notify it that the instance was shutting down. Action: This is an internal error, contact ORACLE support. ORA-09961: Unable to restore termination signal handler Cause: ORACLE failed to set the handler for the termination signal to its previous value. Action: This is an internal error, contact ORACLE support. ORA-09966: falure in translation while expanding ?/dbs/lk for lock file Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for the database mount lock or the instance startup/shutdown lock. Action: Check additional return errors for more information. ORA-09967: unable to create or open lock file Cause: Oracle failed, when making an open system call, inorder to acquire a file lock used by the database mount lock or the instance startup/shutdown lock. Action: Check errno for more information. ORA-09968: unable to lock file Cause: The system call for locking a file returned an error when trying to acquire a database mount lock or the instance startup/shutdown lock. Action: Check errno for more information. ORA-09969: unable to close or remove lock file Cause: The close system call or unlink system call returned an error. Action: Check errno for more information. ORA-09974: skxfidini: Error Initializing SDI Channel Cause: The process was unable to initialize the SDI channel properly. Action: Correct the operating system error and retry the operation. ORA-09975: kxfspini: Error Initializing SDI Process Cause: The process was unable to attach to the SDI channel. Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation. ORA-09976: skxfqdini: Error Creating Port Cause: The process was unable to create a communications endpoint. Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation. ORA-09977: skxfqhini: Error Connecting Cause: The process was unable to connect to another endpoint. Action: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation. ORA-09978: skxfqhdel: Error Disconnecting from another endpoint. Cause: The process was unable to disconnect cleanly from another endpoint. Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. ORA-09979: skxfqhsnd: Error Sending a message to another endpoint Cause: The process was unable to send a message to an existing endpoint. Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint Cause: The process encountered an error while trying to receive a message. Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation. ORA-09981: skxfqdreg: Error Adding a page to the SDI buffer pool Cause: The process was unable to add a page to the SDI buffer pool. Action: Correct the operating system error and retry the operation. ORA-09982: skxfqddrg: Error Removing a page from the SDI buffer pool Cause: The process was unable to remove a page to the SDI buffer pool. Action: Correct the operating system error and retry the operation. ORA-09983: skxfidsht: Error shutting down SDI channel Cause: The process was unable shut down the SDI channel Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance. ORA-09984: SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist Cause: file does not exist or is not accessible Action: Restart the instance to create the SGA definition file. ORA-09985: SGA definition file could not be read Cause: UNIX read() operation failed Action: check errno and take appropriate action. ORA-09986: wrong number of bytes read from SGA definition file Cause: Struct skgmsdef size differs from no. of bytes read from SGA file Action: Compare the two struct definitions and ensure that they are identical in size and structure. ORA-09987: unable to attach to SGA in READ-ONLY mode Cause: The instance is not up, or SGA segments are not read-accessible Action: Verify that the instance is up and read permissions for the SGA segments are set. ORA-09988: error while detaching SGA Cause: skgmsdef struct is corrupted and/or segment addresses are modified Action: Safely shut down instance and mount SGA segments again. ORA-09989: attempt to use invalid skgmsdef struct pointer Cause: Pointer to skgmsdef struct used without validating it Action: Assign a valid address to the skgmsdef struct pointer before using it. ORA-10243: simulated error for test string of K2GTAB latch cleanup Cause: levels 1..6 for insert, 7..11 for delete Action: none ORA-10244: make tranids in error msgs print as 0.0.0 (for testing) Cause: also makes "alter system enable distributed recovery" synchronous Action: none ORA-10259: get error message text from remote using explicit call Cause: for npigem coverage testing (normally called only for V5 remote) Action: none ORA-10261: Limit the size of the PGA heap Cause: the limit is one kilobyte times the level of the event. If the pga grows bigger than this signal an internal error. Action: none ORA-10262: Don"t check for memory leaks Cause: Setting this event to level one causes memory leak checking to be disabled. Setting this event to any other non-zero number allows that number to be used as a threshold value when checking for memory leaks in the PGA, SGA, and UGA heaps. Action: none ORA-10263: Don"t free empty PGA heap extents Cause: This is useful for debugging since watchpoints are lost on free Action: none ORA-10265: Keep random system generated output out of error messages Cause: so test system files don"t diff Action: none ORA-10266: Trace OSD stack usage Cause: Porters should implement this to help them debug their stack implementations. It should be used in at least smcstk(). Action: none ORA-10267: Inhibit KSEDMP for testing Cause: Some tests may generate internal or fatal errors on purpose. Action: LEVEL used by KSEDMP is one less than level of this event. ORA-10268: Don"t do forward coalesce when deleting extents Cause: setting this event keeps kts from coalescing forward at each extent when dropping a temp segment. Action: none ORA-10269: Don"t do coalesces of free space in SMON Cause: setting this event prevents SMON from doing free space coalesces Action: none ORA-10270: Debug shared cursors Cause: Enables debugging code in shared cursor management modules Action: none ORA-10281: maximum time to wait for process creation Cause: used to override the default SPMXWAIT, level = timeout in sec. Action: none ORA-10282: Inhibit signalling of other backgrounds when one dies Cause: Used in KSB Action: none ORA-10284: simulate zero/infinite asynch I/O buffering Cause: Used in KCF, level=1 out of space (red), level=2 infinite (green) Action: none ORA-10360: enable dbwr consistency checking Cause: internal use only Action: enables consistency checking of buffers written by dbwriter and consistency checking of LRU working sets ORA-10361: check buffer change vector count consistency Cause: internal use only Action: invoke buffer change vector count consistency every 5 minutes ORA-10362: simulate a write error to take a file offline Cause: internal use only Action: Enables testing of DBWR taking a file offline because of a write error. The level is the absolute file number of the file to be taken offline when DBWR attemts to write to it. ORA-10364: Do not clear GIMH_STC_SHUT_BEGIN state during shutdown Cause: internal use only Action: Enables testing of shutdown begin event by not clearing GIMH_STC_SHUT_BEGIN state before shutdown completes. ORA-10370: parallel query server kill event Cause: internal use only Action: this event should never be set externally ORA-10371: disable TQ hint Cause: internal use only Action: this event should never be set externally ORA-10372: parallel query server kill event proc Cause: internal use only Action: this event should never be set externally ORA-10373: parallel query server kill event Cause: internal use only Action: this event should never be set externally ORA-10382: parallel query server interrupt (reset) Cause: internal use only Action: this event should never be set externally ORA-10387: parallel query server interrupt (normal) Cause: internal use only Action: this event should never be set externally ORA-10388: parallel query server interrupt (failure) Cause: internal use only Action: this event should never be set externally ORA-10389: parallel query server interrupt (cleanup) Cause: internal use only Action: this event should never be set externally ORA-10560: block type "string" Cause: Report block type for details of another error. Action: See associated error message. ORA-10561: block type "string", data object# string Cause: Report block type and data object number for details of another error. Action: See associated error message. ORA-10562: Error occurred while applying redo to data block (file# string, block# string) Cause: See other errors on error stack. Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block. ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed Cause: Test recovery completed. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery. ORA-10564: tablespace string Cause: Report tablespace name for details of another error. Action: See associated error message. ORA-10565: Another test recovery session is active Cause: There can only be one test recovery session at any time. Another test recovery session is active. Action: Wait till the other test recovery session completes. ORA-10566: Test recovery has used all the memory it can use Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery. ORA-10567: Redo is inconsistent with data block (file# string, block# string) Cause: There are two possible causes of this error: (1) A write issued by Oracle was lost by the underlying OS or storage system. (2) an Oracle internal error. Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block. ORA-10568: Failed to allocate recovery state object: out of SGA memory Cause: out of SGA memory Action: Restart the instance. If problem persists, call Oracle support. ORA-10570: Test recovery complete Cause: Test recovery completed. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery. ORA-10571: Test recovery canceled Cause: User canceled test recovery. Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery. ORA-10572: Test recovery canceled due to errors Cause: See other errors on the error stack. Action: is needed. See other messages on error stack for a summary of the result of the test recovery so far. ORA-10573: Test recovery tested redo from change string to string Cause: This message show the range of test recovery have tested. Action: No action is needed. See other messages on error stack. ORA-10574: Test recovery did not corrupt any data block Cause: This message summarizes test recovery result. Action: No action is needed. See other messages on error stack. ORA-10575: Give up restoring recovered datafiles to consistent state: out of memory Cause: There were not enough memory to restore recovered datafiles to consistent state Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again. ORA-10576: Give up restoring recovered datafiles to consistent state: some error occurred Cause: See alert file or other errors on the stack for a cause of the problem. Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again. ORA-10577: Can not invoke test recovery for managed standby database recovery Cause: Test recovery option is used for managed standby database recovery. Action: Either remove the test recovery option or invoke manual test standby database recovery. ORA-10578: Can not allow corruption for managed standby database recovery Cause: You used the allow corruption option for managed standby database recovery. Action: Either remove the allow corruption option or invoke manual standby database recovery. ORA-10579: Can not modify control file during test recovery Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify control file. Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream. ORA-10580: Can not modify datafile header during test recovery Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers. Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream. ORA-10581: Can not modify redo log header during test recovery Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers. Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream. ORA-10582: The control file is not a backup control file Cause: User requested backup control file test recovery, but the control file is not a backup control file. Action: Use a backup control file, or do not use USING BACKUP CONTROLFILE option. ORA-10583: Can not recovery file string renamed as missing during test recovery Cause: One of the files to be recovered is renamed as missing. Action: Rename the file to the correct file or offline it. ORA-10584: Can not invoke parallel recovery for test recovery Cause: Both test recovery and parallel recovery are requested. Action: Drop either one of the two recovery options. ORA-10585: Test recovery can not apply redo that may modify control file Cause: Test recovery has encountered a special redo that may modify control file. Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point. ORA-10586: Test recovery had to corrupt 1 data block in order to proceed Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested. Action: See alert log for details of the problem. ORA-10587: Invalid count for ALLOW n CORRUPTION option Cause: The number specified in the ALLOW n CORRUPTION option is too big. Action: Use a smaller number. ORA-10588: Can only allow 1 corruption for normal media/standby recovery Cause: The number specified in the ALLOW n CORRUPTION option is too big. Action: change to allow zero or one corruption. ORA-10589: Test recovery had to corrupt string data blocks in order to proceed Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested. Action: See alert log for details of the problems. ORA-10614: Operation not allowed on this segment Cause: This procedure can be used only on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the segment name and type and re-issue the statement ORA-10615: Invalid tablespace type for temporary tablespace Cause: Tablespace with AUTO SEGMENT SPACE MANAGENEMT specified cannot be used as a temporary tablespace Action: Recheck the tablespace name and re-issue the statement ORA-10616: Operation not allowed on this tablespace Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the tablespace name and re-issue the statement ORA-10617: Cannot create rollback segment in dictionary managed tablespace Cause: Rollback segments cannot be created in dictionary managed tablespaces when SYSTEM tablespace is locally managed Action: Recheck the tablespace name and re-issue the statement ORA-10618: Operation not allowed on this segment Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the segment name and type and re-issue the statement ORA-10619: Avoid assertions when possible Cause: A bug (or upgrade) hits unicode assertions (csid, csform, bfc) Action: Event makes RDBMS skip assertions and patch up datastructures ORA-10620: Operation not allowed on this segment Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT Action: Recheck the segment name and re-issue the statement ORA-10627: Dump the content of the index leaf block Cause: Generate a complete index tree dump, not just an overview during alter session set events immediate trace name treedump Action: This event is recommended only for small table/index since it ORA-10628: Turn on sanity check for kdiss index skip scan state Cause: Will do sanity checking on the kdiss state. Action: set this event only under the supervision of Oracle development ORA-10630: Illegal syntax specified with SHRINK clause Cause: An illegal option was specified with the SHRINK clause Action: Verify the SQL Reference Manual and reissue the command ORA-10631: SHRINK clause should not be specified for this object Cause: It is incorrect to issue shrink on the object Action: Verify the object name and type and reissue the command ORA-10632: Invalid rowid Cause: Segment Highwatermark was overwritten due to shrink and space reused Action: Reissue this command. ORA-10633: No space found in the segment Cause: Raised while trying to find space during segment shrink Action: This error should be trapped internally and treated. The user should not be able to see the error. ORA-10634: Segment is already being shrunk Cause: Only one invocation of shrink can be in progress on a segment at any time Action: Reissue the command after the first shrink is over ORA-10635: Invalid segment or tablespace type Cause: Cannot shrink the segment because it is not in auto segment space managed tablespace or it is not a data, index or lob segment. Action: Check the tablespace and segment type and reissue the statement ORA-10636: ROW MOVEMENT is not enabled Cause: To shrink a data segment, row movement must be enabled. Action: Enable row movement and reissue this command. ORA-10637: The segment does not exist Cause: Segment to be shrunk has been dropped Action: none ORA-10638: Index status is invalid Cause: Cannot shrink an index which is being rebuilt or disabled is an unusable state. Action: none ORA-10639: Dump library cache during kksfbc-reparse-infinite-loop error Cause: During this error a library cache dump is necessary , so enable librarycache dump if event is set. Action: Dump a library cache if this event is set when reparse error. ORA-10640: Operation not permitted during SYSTEM tablespace migration Cause: SYSTEM tablespace is being migrated to locally managed format. Action: Reissue this command once SYSTEM tablespace migration is over. ORA-10641: Cannot find a rollback segment to bind to Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace. Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace and retry migration. ORA-10642: Found rollback segments in dictionary managed tablespaces Cause: When SYSTEM tablespace is migrated found rollback segments in dictionary managed tablespaces. Action: Drop the rollback segments in dictionary managed tablespaces and reissue the command ORA-10643: Database should be mounted in restricted mode and Exclusive mode Cause: When SYSTEM tablespace is being migrated database should be mounted in Exclusive mode and in Restricted mode. Action: Reissue this command after mounting the database in right mode. ORA-10644: SYSTEM tablespace cannot be default temporary tablespace Cause: When SYSTEM tablespace is being migrated no user should have SYSTEM as the default temporary tablespace. Action: Reissue this command after altering the default temporary tablespace setting for all users. ORA-10645: Recursive Extension in SYSTEM tablespace during migration Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively. Must be caught and processed internally. Should not be thrown to the user. Action: Report the error as a bug. ORA-10646: Too many recursive extensions during SYSTEM tablespace migration Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times. Action: If SYSTEM tablespace is very large, then simply reissue the tablespace migration command. ORA-10647: Tablespace other than SYSTEM, string, string not found in read only mode Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three should be ALTERed to read only. Action: Alter the tablespace status to read only and retry migration. ORA-10648: Tablespace SYSAUX is not offline Cause: The SYSAUX tablespace was online while SYSTEM tablespace was being migrated. Action: Alter the SYSAUX tablespace status to offline and retry migration. ORA-10651: incorrect file number block number specified Cause: The dba specified is not valid Action: Check if the dba specified belongs to the segment and is under the segment HWM and reissue the statement ORA-10652: Object has on-commit materialized views Cause: It is illegal to issue shrink on an object with on-commit materialized views Action: none ORA-10653: Table is in a cluster Cause: It is illegal to shrink a table belonging to a cluster Action: none ORA-10654: Table is of type temporary or external Cause: It is illegal to shrink a temporary table or an external table Action: none ORA-10655: Segment can be shrunk Cause: Error message returned when called in probe mode by OEM Action: none ORA-10656: Table is in unusable state due to incomplete operation Cause: ALTER TABLE SHRINK operation was tried on the table which is in unusable state because of previously failed/incomplete operation. Action: If the previous operation was - DROP COLUMN, resubmit DROP COLUMN CONTINUE - DROP TABLE, resubmit DROP TABLE
PURGE ORA-10657: Lob column to be shrunk does not exist Cause: Shrink was issued on a lob segment that did not exist Action: none ORA-10658: Lob column to be shrunk is marked unused Cause: Shrink was issued on a lob segment that is marked as unused Action: none ORA-10659: Segment being shrunk is not a lob Cause: Shrink was issued on a segment that should be a first class lob or other data type stored in lob Action: none ORA-10660: Segment is a shared lob segment Cause: Shrink was issued on a segment that was being shared by multiple lob columns Action: none ORA-10661: Invalid option specified Cause: Check option can be specified for one segment only Action: none ORA-10662: Segment has long columns Cause: Shrink was issued on a segment with long columns. This is not supported. Action: none ORA-10663: Object has rowid based materialized views Cause: Shrink was issued on an object with rowid based materialized views. Action: Drop the rowid based materialized views and issue shrink on the object ORA-10664: Table has bitmap join indexes Cause: SHRINK was issued on a table with bitmap join indexes. Action: Drop bitmap join indexes and reissue SHRINK on the object. ORA-10665: Inject Evil Literals Cause: Event 10665 is set to some number > 0, causing 1/(value-1) of all literals to be replaced by 2000 letter "A"s. A value of 1 does not corrupt anything. Action: never set this event ORA-10668: Inject Evil Identifiers Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all identifiers to be replaced by a maximum amount of x"s. It is common for an identifier to be parsed once with a max of 30 bytes, then reparsed later with a max of 4000, so it may not be possible to inject such an identifier without the aid of this event. A value of 1 causes no identifiers to be corrupted. Action: never set this event ORA-10690: Set shadow process core file dump type (Unix only) Cause: Control core file size for shadow processes Action: Level 1: Detach SGA before dumping core Level 2: Do not produce any core ORA-10691: Set background process core file type (Unix only) Cause: Control core file size file for background processes Action: Level 1: Detach SGA before dumping core ORA-10700: Alter access violation exception handler Cause: Use this event to control what the VMS exception handler does when it encounters an access violation. Action: Level: >=10 Suspend current process on access violation *** SET THIS EVENT ONLY UNDER THE SUPERVISION OF ORACLE DEVELOPMENT *** ORA-10701: Dump direct loader index keys Cause: Dumps index keys at various points in a direct load based on the value of this event. Action: none ORA-10704: Print out information about what enqueues are being obtained Cause: When enabled, prints out arguments to calls to ksqcmi and ksqlrl and the return values. Action: Level indicates details: Level: 1-4: print out basic info for ksqlrl, ksqcmi 5-9: also print out stuff in callbacks: ksqlac, ksqlop 10+: also print out time for each line ORA-10706: Print out information about global enqueue manipulation Cause: When enabled, prints out activity in ksi routines. Action: Level indicates details: 0-4: show args for each main call 5-9: also indicate callbacks 10+: also printout time for each line ORA-10707: Simulate process death for instance registration Cause: When enabled, process commits suicide to test instance registration recovery code. Action: Level indicates where the process will die ORA-10841: Default un-inintialized charact set form to SQLCS_IMPLICIT Cause: client side, such as JDBC-THIN 8i client sends 0 as charset form Action: This event sets charset form as SQLCS_IMPLICIT when it is 0 ORA-10842: Event for OCI Tracing and Statistics Info Cause: This event is meant for tracing OCI Calls and getting statistics Action: This event sets tracing OCI Calls and gets statistics info ORA-10852: Enable tracing for Enqueue Dequeue Operations Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. ORA-10854: Sets poll count used for AQ listen code under RAC Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. ORA-10862: resolve default queue owner to current user in enqueue/dequeue Cause: resolve default queue owner to current user in enqueue/dequeue. Action: turn on if client wish to resolve the default queue owner to the current user. If not turned on, the default queue owner will be resolved to the login user. ORA-10863: Control behavior of buffered background operations Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. ORA-10865: Control tracing of notification operations Cause: NA Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL TESTING. ORA-10900: extent manager fault insertion event #string Cause: causes faults to be generated in instrumented extent code Action: this should only be enabled for internal testing ORA-10902: disable seghdr conversion for ro operation Cause: causes seghdr conversion to be turned off for ro ops(#555856) Action: this should be enabled only if determined that bug 555856 has occured. Table needs to be exported subsequently ORA-10906: Unable to extend segment after insert direct load Cause: This is a restriction with insert direct load transactions. Action: When a segment has been insert direct loaded, avoid DMLs that could cause more space to be consumed. ORA-10914: invalid TABLESPACE GROUP clause Cause: An invalid option appears for TABLESPACE GROUP clause. Action: Specify a valid tablespace group name. ORA-10915: TABLESPACE GROUP cannot be specified for this type of tablespace Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP clause was used while creating/altering a tablespace that is not TEMPORARY. Action: Remove the TABLESPACE GROUP clause. ORA-10916: TABLESPACE GROUP already specified Cause: In CREATE/ALTER TABLESPACE, the TABLESPACE GROUP option was specified more than once. Action: Remove all but one of the TABLESPACE GROUP specifications. ORA-10917: TABLESPACE GROUP cannot be specified Cause: The tablespace name specified in the command is actually the name of a tablespace group. Action: Please specify an appropriate tablespace name. ORA-10918: TABLESPACE GROUP name cannot be the same as tablespace name Cause: The tablespace group name specified in the command is the same as the tablespace being CREATEd/ALTERed. Action: Please specify an appropriate tablespace group name. ORA-10919: Default temporary tablespace group must have at least one tablespace Cause: An attempt was made to move the only tablespace in the default database temporary tablespace group to another tablespace group. Action: Either change the database default temporary tablespace or add another tablespace to the group that this tablespace belongs to. ORA-10920: Cannot offline tablespace belonging to default temporary tablespace group Cause: An attempt was made to offline a tablespace in the default database temporary tablespace group. Action: Either change the database default temporary tablespace or change the tablespace group of this tablespace. ORA-10921: Cannot drop tablespace belonging to default temporary tablespace group Cause: An attempt was made to drop a tablespace in the default database temporary tablespace group. Action: Either change the database default temporary tablespace or change the tablespace group of this tablespace. ORA-10922: Temporary tablespace group is empty Cause: An attempt was made to allocate a temporary segment in a group, which now no longer has any members. Action: Either add some temporary tablespaces or change the temporary tablespace for this user. ORA-10924: import storage parse error ignore event Cause: causes server to ignore specific error associated with freelists and freelist groups when parsing Action: this should be enabled by import code only ORA-10925: trace name context forever Cause: When enabled, turns off bugfix 237911 Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10926: trace name context forever Cause: When enabled, turns off bugfix 190119 Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10927: trace name context forever Cause: When enabled, turns off bugfix 235190 Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10929: trace name context forever Cause: When enabled, turns off bugfix 343966 Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10930: trace name context forever Cause: When enabled, provides V7 behavior for fixed char binds Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10931: trace name context forever Cause: When enabled, allows normal packages to be compiled with standard extensions like "" Action: Set this event only for a short amount of time. Once the packages are compiled, this event should be turned off. Level 1 - Turn the event on Level > 1 - Turn the event off ORA-10932: trace name context forever Cause: When enabled, disables one or more features or bug fixes available only in version 8.x. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10933: trace name context forever Cause: When enabled, disables one or more features or bug fixes available only in version 8.x. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10936: trace name context forever Cause: When enabled, disables one or more features or bug fixes available in versions 7.x and 8.x. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10940: trace name context forever Cause: Size of the PL/SQL tracing circular buffer, in kilobytes. Action: Set this event in concert with the 10938 event and the _PLSQL_DUMP_BUFFER_EVENTS init.ora parameter, under supervision of Oracle Support. ORA-10941: trace name context forever Cause: When enabled, turns on PL/SQL profiler Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10943: trace name context forever Cause: When enabled, disables one or more features or bug fixes available only in version 8.x. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10944: trace name context forever Cause: When enabled, allows or controls PL/SQL OPT code gen project. available only in version 8.2+. Action: set this event ONLY for development of the OPT project. This is not for general use or deployment. ORA-10945: trace name context forever Cause: When enabled, disables the behaviour change introduced by the fix for bug 822764, which traps and handles invalidations of packages whereas the previous behaviour was to use stale invalidated instantiations of the stateful package body. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10946: trace name context forever Cause: When enabled, disables one or more features or bug fixes available only in version 10.x. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10947: trace name context forever Cause: When enabled, causes various PL/SQL warnings related debugging info to be written in a trace file. Useful for debugging varous Oracle processes. available only in version 10.x. Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support. ORA-10948: trace name context forever Cause: When enabled, inflate callout argument. available only in version 10.x. Action: internal use only. ORA-10970: backout event for bug 2133357 Cause: 2133357 dynamically sets the varying width flag and character width. Lob data which is not migrated during migration from single byte to multibyte charater set will be displayed as special characters. Action: To help migrate lob data which was not migrated during migration by backing out 2133357, so lob data can be selected and moved to multibyte character set. ORA-10973: backout evet for 2619509 Cause: 2619509 catches offsets when not reading/writing on full character boundary. To facilitate backward compatiblity event is being introduced. Action: To help upgrade/migrate issues which already have corrupt data ORA-10979: trace flags for join index implementation Cause: This is an informational message. Action: Values are as follows: LEVEL ACTION --------------------------------------------------------------------------- > 1 Dump refresh expressions (SQL) to trace file. > 999 If a complete refresh is invoked, it will not be performed but the system will assume that a complete refresh was done, causing the view to be VALID and updating timestamps. This should be used only under Oracle Support supervision. ORA-10997: another startup/shutdown operation of this instance inprogress Cause: An Oracle Instance startup or shutdown operation failed to procure the serialization primitive. Another foreground process may have attempted startup or shutdown operation in parallel. Action: Check additional error messages in the alert log and the process trace file. ORA-12001: cannot create log: table "string" already has a trigger Cause: Materialized view logs are filled by a trigger on the master table. That trigger cannot be created. Action: To create a materialized view log, drop the current trigger on the master. ORA-12002: there is no materialized view log on table "string"."string" Cause: There was no materialized view log on the master table. Action: Create a materialized view log on the master table. ORA-12003: materialized view "string"."string" does not exist Cause: The materialized view with the given owner and name does not exist. Action: Verify inputs and create a materialized view. ORA-12004: REFRESH FAST cannot be used for materialized view "string"."string" Cause: The materialized view log does not exist or cannot be used. PCT refresh is also not enabled on the materialized view Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log or PCT refresh is possible after a given set of changes, REFRESH FAST will be available starting the next time the materialized view is refreshed. ORA-12005: may not schedule automatic refresh for times in the past Cause: An attempt was made to schedule an automated materialized view refresh for a time in the past. Action: Choose a time in the future instead. ORA-12007: materialized view reuse parameters are inconsistent Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG .. REUSE command was given inconsistent parameters immediately after the REUSE. Action: Examine the other messages on the stack to find the problem. ORA-12008: error in materialized view refresh path Cause: Table SNAP$_ reads rows from the view MVIEW$_, which is a view on the master table (the master may be at a remote site). Any error in this path will cause this error at refresh time. For fast refreshes, the table .MLOG$_ is also referenced. Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_, MVIEW$_, .@, .MLOG$_@ still exist. ORA-12010: cannot create materialized view log on table owned by SYS Cause: An attempt was made to create a materialized view log on the table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the table, but triggers can not be created on SYS tables. Action: Do not create a materialized view log on SYS tables. ORA-12011: execution of string jobs failed Cause: An error was caught in dbms_ijob.run from one or more jobs which were due to be run. Action: Look at the alert log for details on which jobs failed and why. ORA-12012: error on auto execute of job string Cause: An error was caught while doing an automatic execution of a job. Action: Look at the accompanying errors for details on why the execute failed. ORA-12013: updatable materialized views must be simple enough to do fast refresh Cause: The updatable materialized view query contained a join, subquery, union, connect by, order by, or group by caluse. Action: Make the materialized view simpler. If a join is really needed, make multiple simple materialized views then put a view on top of them. ORA-12014: table "string" does not contain a primary key constraint Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH PRIMARY KEY option and the master table did not contain a primary key constraint or the constraint was disabled. Action: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint. ORA-12015: cannot create a fast refresh materialized view from a complex query Cause: Neither ROWIDs and nor primary key constraints are supported for complex queries. Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple materialized view. ORA-12016: materialized view does not include all primary key columns Cause: The query that instantiates the materialized view did not include all of the columns in the master"s primary key constraint. Action: Include all of the master"s primary key columns in the materialized view query or create a ROWID materialized view. ORA-12017: cannot alter primary key mview "string" to a rowid mview Cause: An attempt was made to convert the primary key of a materialized view to a ROWID materialized view. Action: Conversion of a primary key materialized view to a ROWID materialized view is not supported. Create a new materialized view with ROWIDs or drop and recreate the materialized view with ROWIDs. ORA-12018: following error encountered during code generation for "string"."string" Cause: The refresh operations for the indicated materialized view could not be regenerated due to errors. Action: Correct the problem indicated in the following error messages and repeat the operation. ORA-12019: master table is a synonym to a remote object Cause: An attempt was made to create a materialized view or a materialized view log on a remote synonym which is unsupported. Action: Do not create a materialized view or materialized view log on a remote synonym. ORA-12020: materialized view string is not registered Cause: An attempt was made to unregister a materialized view that is not registered. Action: No action required. ORA-12021: materialized view "string"."string" is corrupt Cause: The materialized view indicated is no longer valid. Action: Contact Oracle Customer Support. ORA-12022: materialized view log on "string"."string" already has rowid Cause: Materialized view log on the indicated table already has ROWID information. Action: No action required. ORA-12023: missing index on materialized view "string"."string" Cause: The specified ROWID materialized view did not have the required index on the ROWID column of its underlying table. Action: Drop and recreate the materialized view. ORA-12024: materialized view log on "string"."string" does not have primary key columns Cause: Materialized view log on the indicated table does not have primary key information. Action: Add primary keys to the materialized view log using the ALTER MATERIALIZED VIEW command. ORA-12025: materialized view log on "string"."string" already has primary keys Cause: Materialized view log on the indicated table already has primary key columns. Action: No action required. ORA-12026: invalid filter column detected Cause: One or more of the specified filter columns did not exist or was a primary key column or a primary key based object identifier. Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns or primary key based object identifiers are not included in the list of filter columns. ORA-12027: duplicate filter column Cause: One or more of the specified filter columns were already being recorded in the materialized view log. Action: Describe the materialized view log table and reissue the SQL command with the filter columns that are already being recorded in the materialized view log. ORA-12028: materialized view type is not supported by master site string Cause: Pre-Oracle8 master sites are not able to support primary key or subquery materialized views that are able to perform a fast refresh. Action: Create a ROWID materialized view or use a master table from an Oracle8 site. ORA-12029: LOB columns may not be used as filter columns Cause: An attempt was made to use LOB columns as filter columns. Action: Remove LOB columns from the filter columns list and retry command. ORA-12030: cannot create a fast refresh materialized view Cause: The materialized view log did not exist or did not log the information needed by the materialized view to perform a fast refresh. Action: Ensure that the materialized view log exists and logs the necessary information. - For ROWID materialized views, the master table"s ROWID must be logged. - For primary key materialized views, the master table"s primary key columns must be logged. - For subquery materialized views, the filter columns, primary key, and ROWID values must be logged. - For object materialized views, object id must be logged. ORA-12031: cannot use primary key columns from materialized view log on "string"."string" Cause: The materialized view log either did not have primary key columns logged, or the timestamp associated with the primary key columns was more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add primary key columns to the materialized view log, if required. ORA-12032: cannot use rowid column from materialized view log on "string"."string" Cause: The materialized view log either does not have ROWID columns logged, or the timestamp associated with the ROWID columns is more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required. ORA-12033: cannot use filter columns from materialized view log on "string"."string" Cause: The materialized view log either did not have filter columns logged, or the timestamp associated with the filter columns was more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add filter columns to the materialized view log, if required. ORA-12034: materialized view log on "string"."string" younger than last refresh Cause: The materialized view log was younger than the last refresh. Action: A complete refresh is required before the next fast refresh. ORA-12035: could not use materialized view log on "string"."string" Cause: The materialized view log did not exist or could not be used. Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed. ORA-12036: updatable materialized view log is not empty, refresh materialized view Cause: The updatable materialized view log was not empty. The updatable materialized view log must be empty before an updatable rowid materialized view can be altered to a primary key materialized view. Action: Ensure that updatable materialized view log is empty by refreshing the materialized view before converting the updatable ROWID materialized view to a primary key materialized view. ORA-12037: unknown export format Cause: An attempt was made to import a materialized view exported by an unknown export version (e.g., from a newer release than the importing site) Action: Re-export the file using a version of export known by the importing site. ORA-12039: unable to use local rollback segment "string" Cause: A local rollback segment was specified in the CREATE MATERIALIZED VIEW command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the materialized view and the local rollback segment can"t be registered for future use. Action: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment. ORA-12040: master rollback segment option not support by master site string Cause: An attempt was made to specify master rollback segment in the current operation. The master site of the current materialized view does not allow users to specify a rollback segment to be used for materialized view operations. This feature is only supported by Oracle8 or later master sites. Action: Do not specify a master rollback segment in the current operation or choose a new master site. ORA-12041: cannot record ROWIDs for index-organized table "string"."string" Cause: Index-organized tables do not have ROWIDs. Therefore a materialized view log that records the ROWIDs of an index-organized table could not be created. Action: Do not include the WITH ROWID option when using the CREATE MATERIALIZED VIEW command and do not include the ADD ROWID option when using the ALTER MATERIALIZED VIEW command if the master table is index-organized. ORA-12042: cannot alter job_queue_processes in single process mode Cause: An attempt was made to alter job_queue_processes in single process mode. Action: Do not attempt to set job_queue_processes in single process mode. ORA-12043: invalid CREATE MATERIALIZED VIEW option Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement. Action: Specify only valid options. ORA-12044: invalid CREATE MATERIALIZED VIEW LOG option Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement. Action: Specify only valid options. ORA-12045: invalid ALTER MATERIALIZED VIEW LOG option Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement. Action: Specify only valid options. ORA-12046: cannot use trusted constraints for refreshing remote MV Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER MATERIALIZED VIEW or CREATE MATERIALIZED VIEW of a remote materialized view Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW DDL ORA-12047: PCT FAST REFRESH cannot be used for materialized view "string"."string" Cause: PCT refresh is either not enabled on this materialized view or not possible after set of the base table changes since last refresh. Action: Use just REFRESH FORCE, which will reinstantiate the entire table and try to pick the best refresh method on the materialized view Do explain_mview to look at the cause why PCT refresh is not possible on this materialized view ORA-12048: error encountered while refreshing materialized view "string"."string" Cause: Some problem occurs during refresh of multiple materialized views in atomic mode. The materialized view whose refresh failed has raised this error. Action: Examine the other messages on the stack to find the refresh problem. ORA-12051: ON COMMIT attribute is incompatible with other options Cause: ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified. Action: Specify only valid options. ORA-12052: cannot fast refresh materialized view string.string Cause: Either ROWIDs of certain tables were missing in the definition or the inner table of an outer join did not have UNIQUE constraints on join columns. Action: Specify the FORCE or COMPLETE option. If this error is got during creation, the materialized view definition may have be changed. Refer to the documentation on materialized views. ORA-12053: this is not a valid nested materialized view Cause: The list of objects in the FROM clause of the definition of this materialized view had some dependencies upon each other. Action: Refer to the documentation to see which types of nesting are valid. ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view Cause: The materialized view did not satisfy conditions for refresh at commit time. Action: Specify only valid options. ORA-12055: materialized view definition contains cyclic dependencies with existing materialized views Cause: The materialized view query definition introduced a cyclic dependency with existing materialized view. Action: Modify the materialized view query definition. ORA-12056: invalid REFRESH method Cause: The NEVER REFRESH option may not be used under the following conditions: * The materialized view is updatable * The materialized view refreshes ON COMMIT * Automatic refresh options are specified Action: For updatable materialized views, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized views, reissue the SQL command using ON DEMAND. ORA-12057: materialized view "string"."string" is INVALID and must complete refresh Cause: The status of the materialized view was INVALID and an attempt was made to fast refresh the materialized view. Action: Perform a complete refresh of the materialized view. Check the value of the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that the materialized view is VALID after the complete refresh. ORA-12058: materialized view cannot use prebuilt table Cause: An attempt was made to use the prebuilt tables. Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED. ORA-12059: prebuilt table "string"."string" does not exist Cause: The specified prebuilt table did not exist. Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists. ORA-12060: shape of prebuilt table does not match definition query Cause: The number of columns or the type or the length semantics of a column in the prebuilt table did not match the materialized view definition query. Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the materialized view definition query. ORA-12061: invalid ALTER MATERIALIZED VIEW option Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement. Action: Specify only valid options. ORA-12062: transaction string received out of sequence from site string Cause: A transaction from the client site was received out of sequence. This implies that one or more transactions were missing. Action: Ensure that the transaction queue at the client site is valid and has not been corrupted. ORA-12063: unable to apply transaction from site string Cause: The current transaction from the client site could not be applied to the master site. Action: Ensure that the client site is still valid and that it has not been dropped from the master site. ORA-12064: invalid refresh sequence number: string Cause: The client site was attempting to perform a refresh with an invalid refresh sequence. Action: Perform a complete refresh to synchronize the refresh sequence number. ORA-12065: unknown refresh group identifier string Cause: The specified refresh group did not exist at the master site. Action: Ensure that the client site is still valid and that it has not been dropped from the master site. ORA-12066: invalid CREATE MATERIALIZED VIEW command Cause: The Replication API does not support the following options and types of materialized view: o ROWID materialized views o REFRESH ON COMMIT o ON PREBUILT TABLE o BUILD DEFERRED o NEVER REFRESH o ENABLE QUERY REWRITE Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY KEY and/or remove the invalid options. ORA-12067: empty refresh groups are not allowed Cause: The refresh group being instantiated did not contain any materialized views. Action: Modify the template to include at least one materialized view. ORA-12068: updatable mview log for mview "string"."string" does not exist Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view. Action: Create the updatable materialized view log. ORA-12069: invalid object for offline instantiation Cause: Only materialized views can be offline instantiated. The object being offline instantiated was not a valid materialized view. Action: Remove the object from the template or replace the object with a valid materialized view. ORA-12070: cannot offline instantiate materialized view "string"."string" Cause: Offline instantiation does not support materialized views using the following options: o ON PREBUILT TABLE o BUILD DEFERRED Action: Remove the invalid options. ORA-12071: definition query of "string"."string" is invalid for offline instantiation Cause: Offline instantiation requires materialized view definition queries to observe the following constraints: o The database link that will be used by the materialized view site to connect to the master site must be included with each master table referenced in the query. o All master tables referenced must be located at the local site. References to other sites are not allowed. Action: Modify the materialized view definition query. ORA-12072: updatable materialized view log data for "string"."string" cannot be created Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view. Action: Create an updatable materialized view log. ORA-12073: request cannot be processed Cause: An out-of-sequence request was made and it cannot be processed. Action: Try again with a valid request. ORA-12074: invalid memory address Cause: An attempt was made to access an invalid memory region. Action: Reconnect and try the command again. ORA-12075: invalid object or field Cause: An attempt was made to access an invalid field or object in the Java Virtual Memory. Action: Retry the request. ORA-12076: invalid threshold value Cause: The result set threshold or LOB threshold value is not supported. Action: Specify a threshold value below 64K. ORA-12077: temporary updatable materialized view log does not exist Cause: Temporary updatable materialized view log was not created or was dropped. Action: Re-create the temporary updatable materialized view log. Warning: This will cause a complete refresh of the materialized view. ORA-12078: fast refresh of refresh group ID string failed Cause: Refresh result set sent through client method REFRESH_REQ_RESULT returned an unknown value. Action: Re-issue the refresh request. ORA-12079: materialized view options require COMPATIBLE parameter to be string or greater Cause: The following materialized view options require 8.1 or higher compatibility setting: o ON COMMIT o ON PREBUILT TABLE o BUILD DEFERRED o NEVER REFRESH o ENABLE QUERY REWRITE The following materialized view options require 8.2 or higher compatibility setting: o materialized views with user-defined types The following materialized view options require 9.2 or higher o materialized views (query rewrite enabled) with set operators that are not inside an inline view or named view The following materialized view options require 10.0 or higher o materialized views which can be refreshed USING TRUSTED CONSTRAINTS o materialized views with SELECT column alias clause In addition, ALTER MATERIALIZED VIEW LOG can be used to add sequence number only if compatibility is set to 10.0 or higher Action: Shut down and restart with an appropriate compatibility setting. ORA-12081: update operation not allowed on table "string"."string" Cause: An attempt was made to update a read-only materialized view. Action: No action required. Only Oracle is allowed to update a read-only materialized view. ORA-12082: "string"."string" cannot be index organized Cause: An attempt was made to create an index-organized materialized aggregate view or an index-organized updatable ROWID materialized view. This is not supported. Action: Try to create the materialized view without the index organization clause. ORA-12083: must use DROP MATERIALIZED VIEW to drop "string"."string" Cause: An attempt was made to drop a materialized view using a command other than DROP MATERIALIZED VIEW. Action: Use the DROP MATERIALIZED VIEW command. ORA-12084: must use ALTER MATERIALIZED VIEW to alter "string"."string" Cause: An attempt was made to alter a materialized view using a command other than ALTER MATERIALIZED VIEW. Action: Use the ALTER MATERIALIZED VIEW command. ORA-12085: materialized view log on "string"."string" already has object id Cause: Materialized view log on the indicated table already has object id information. Action: No action required. ORA-12086: table "string"."string" is not an object table Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH OBJECT ID option and the master table is not an object table. Action: Either specify the name of an object table, or remove the WITH OBJECT ID clause. ORA-12087: online redefinition not allowed on tables owned by "string" Cause: An attempt was made to online redefine a table owned by SYS or SYSTEM. Action: Do not attempt to online redefine a table owned by SYS or SYSTEM. ORA-12088: cannot online redefine table "string"."string" with unsupported datatype Cause: An attempt was made to online redefine a table containing a LONG column, an ADT column, or a FILE column. Action: Do not attempt to online redefine a table containing a LONG column, an ADT column, or a FILE column. ORA-12089: cannot online redefine table "string"."string" with no primary key Cause: An attempt was made to online redefine a table that does not have a primary key defined on it. Action: Do not attempt to online redefine a table that does not have a primary key defined on it. ORA-12090: cannot online redefine table "string"."string" Cause: An attempt was made to online redefine a table that is either a clustered table, AQ table, temporary table, IOT overflow table or table with FGA/RLS enabled. Action: Do not attempt to online redefine a table that is a clustered table, AQ table, temporary table, IOT overflow table or table with FGA/RLS enabled. ORA-12091: cannot online redefine table "string"."string" with materialized views Cause: An attempt was made to online redefine a table that had materialized views defined on it or had a materialized view log defined on it or is a master. Action: Drop all materialized views and materialized view logs before attempting to online redefine the table. ORA-12092: cannot online redefine replicated table "string"."string" Cause: An attempt was made to online redefine a table that is either a materialized view or a replicated table. Action: Do not attempt to online redefine a table that is either a materialized view or a replicated table. ORA-12093: invalid interim table "string"."string" Cause: The table is not the interim table of the corresponding table to be online redefined. Action: Pass in the valid interim table. ORA-12094: error during online redefinition Cause: There was an error during the online redefinition process. Action: Abort the online redefinition process. ORA-12096: error in materialized view log on "string"."string" Cause: There was an error originating from this materialized view log. One possible cause is that schema redefinition has occurred on the master table and one or more columns in the log is now a different type than corresponding master column(s). Another possible cause is that there is a problem accessing the underlying materialized view log table. Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop the materialized view log and recreate it. ORA-12097: changes in the master tables during refresh, try refresh again Cause: There are some changes (i.e., conventional DML, direct load, partition maintenance operation) in the master tables during materialized view refresh. Action: Refresh the affected materialized views again. ORA-12098: cannot comment on the materialized view Cause: An attempt was made to issue a COMMENT ON TABLE statement on a materialized view. Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead. ORA-12100: materialized view log on "string"."string" already has sequence Cause: Materialized view log on the indicated table already has sequence information. Action: No action required. 8 ORA-07500 to ORA-09859 ORA-07500: scglaa: $cantim unexpected return Cause: VMS system service $CANTIM returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07501: scgtoa: $deq unexpected return Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07502: scgcmn: $enq unexpected return Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07503: scgcmn: $setimr unexpected return Cause: VMS system service $SETIMR returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07504: scgcmn: $hiber unexpected return Cause: VMS system service $HIBER returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07505: scggt: $enq parent lock unexpected return Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07506: scgrl: $deq unexpected return on lockid string Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07507: scgcm: unexpected lock status condition Cause: A global locking system service returned an unexpected value. Action: Check for system error message (if any) and refer to VMS documentation, or contact your customer support representative. ORA-07508: scgfal: $deq all unexpected return Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07509: scgfal: $deq parent lock unexpected return Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07510: scgbrm: $getlki unexpected return on lockid string Cause: VMS system service $GETLKI returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07511: sscggtl: $enq unexpected return for master termination lock Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07512: sscggtl: $enq unexpected return for client termination lock Cause: VMS system service $ENQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07513: sscgctl: $deq unexpected return on cancel of term. lock Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07514: scgcan: $deq unexpected return while canceling lock Cause: VMS system service $DEQ returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07534: scginq: $getlki unexpected return on lockid string Cause: VMS system service $GETLKI returned an unexpected value Action: Check for system error message and refer to VMS documentation ORA-07548: sftopn: Maximum number of files already open Cause: Too many test files open Action: This is an internal error, please report to Oracle ORA-07549: sftopn: $OPEN failure Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07550: sftopn: $CONNECT failure Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07551: sftcls: $CLOSE failure Cause: VMS system service $CLOSE failed Action: Examine system error message and refer to VMS documentation ORA-07552: sftget: $GET failure Cause: VMS system service $GET failed Action: Examine system error message and refer to VMS documentation ORA-07561: szprv: $IDTOASC failure Cause: VMS system service $IDTOASC failed Action: Examine system error message and refer to VMS documentation ORA-07562: sldext: extension must be 3 characters Cause: An extension was found but it is of improper length Action: This is an internal error, please report to Oracle ORA-07563: sldext: $PARSE failure Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation ORA-07564: sldext: wildcard in filename or extension Cause: A wildcard was used in the file name Action: Reenter the file name completely ORA-07565: sldext: $SEARCH failure Cause: VMS system service $SEARCH failed Action: Examine system error message and refer to VMS documentation ORA-07568: slspool: $OPEN failure Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07569: slspool: $CLOSE failure Cause: VMS system service $CLOSE failed Action: Examine system error message and refer to VMS documentation ORA-07570: szrfc: $IDTOASC failure Cause: VMS system service $IDTOASC failed Action: Examine system error message and refer to VMS documentation ORA-07571: szrfc: $FIND_HELD failure Cause: VMS system service $FIND_HELD failed Action: Examine system error message and refer to VMS documentation ORA-07572: szrfc: insufficient rolename buffer space Cause: An OS role name was too long. Action: Re-define the role name to be of correct length. ORA-07573: slkhst: could not perform host operation Cause: VMS system service LIB$SPAWN failed Action: Examine system error message and refer to VMS documentation ORA-07574: szrfc: $GETUAI failure Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation ORA-07576: sspexst: $GETJPIW failure on process ID string Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07577: no such user in authorization file Cause: An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA__DBA or ORA__OPER) hasn"t been created yet. Action: Add a VMS account for ORA__DBA and/or ORA__OPER before trying to set a password for them. ORA-07578: szprv: $FIND_HELD failure Cause: VMS system service $FIND_HELD failed Action: Examine system error message and refer to VMS documentation ORA-07579: spini: $DCLEXH failure Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation ORA-07580: spstp: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07581: spstp: cannot derive SID from unexpected process name Cause: A background process did not have name of correct form Action: If the job name was changed, restore it, otherwise this is an internal error, please report to Oracle. ORA-07582: spstp: ORA_SID has illegal value Cause: The ORA_SID must exist and be less than 6 characters Action: Consult the VMS Installation guide for information on setting the SID. ORA-07584: spdcr: invalid value for ORA_sid_(proc_)PQL$_item Cause: A logical name used to set a detached process quota value has an invalid value (probably non-numeric). Action: Examine the values of these logical names, correct the one in error, and retry. ORA-07585: spdcr: $PARSE failure Cause: VMS system service $PARSE failed Action: Examine system error message and refer to VMS documentation ORA-07586: spdcr: $SEARCH failure Cause: VMS system service $SEARCH failed Action: Examine system error message and refer to VMS documentation ORA-07587: spdcr: $CREPRC failure Cause: VMS system service $CREPRC failed Action: Examine system error message and refer to VMS documentation ORA-07588: spdcr: $GETJPIW get image name failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07589: spdde: system ID not set Cause: The logical name ORA_SID doesn"t translate to a valid value. Action: Check the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly. ORA-07590: spdde: $DELPRC failure Cause: VMS system service $DELPRC failed Action: Examine system error message and refer to VMS documentation ORA-07591: spdde: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07592: sspgprv: Error obtaining required privileges Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. Action: This is an internal error. Please report to Oracle ORA-07593: ssprprv: Error release privileges Cause: While releasing privileges, an error was returned from SYS$SETPRV. Action: This is an internal error. Please report to Oracle ORA-07594: spiip: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07595: sppid: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07596: sptpa: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07597: spguns: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07598: spwat: $SETIMR failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07599: spwat: $SCHDWK failure Cause: VMS system service $SCHDWK failed Action: Examine system error message and refer to VMS documentation ORA-07600: slkmnm: $GETSYIW failure Cause: VMS system service $GETSYIW failed Action: Examine system error message and refer to VMS documentation ORA-07601: spguno: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07602: spgto: $GETJPIW failure Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07605: szprv: $ASCTOID failure Cause: VMS system service $ASCTOID failed Action: Examine system error message and refer to VMS documentation ORA-07606: szprv: $CHKPRO failure Cause: VMS system service $CHKPRO failed Action: Examine system error message and refer to VMS documentation ORA-07607: szaud: $SNDOPR failure Cause: VMS system service $SNDOPR failed Action: Examine system error message and refer to VMS documentation ORA-07608: szprv: $GETUAI failure Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation ORA-07609: szprv: $HASH_PASSWORD failure Cause: VMS system service $HASH_PASSWORD failed Action: Examine system error message and refer to VMS documentation ORA-07610: $GETJPIW failed in retrieving the user"s MAC priviledges Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07612: $GETUAI failed in retrieving the user"s clearance level Cause: VMS system service $GETUAI failed Action: Examine system error message and refer to VMS documentation ORA-07613: $GETJPIW failed in retrieving the user"s process label Cause: VMS system service $GETJPIW failed Action: Examine system error message and refer to VMS documentation ORA-07614: $CHANGE_CLASS failed in retrieving the user"s process label Cause: VMS system service $CHANGE_CLASS failed Action: Examine system error message and refer to SEVMS documentation ORA-07615: $CHANGE_CLASS failed in retrieving the specified file label Cause: VMS system service $CHANGE_CLASSS failed Action: Examine system error message and refer to SEVMS documentation ORA-07616: $CHANGE_CLASS failed in retrieving the specified device label Cause: VMS system service $CHANGE_CLASS failed Action: Examine system error message and refer to SEVMS documentation ORA-07617: $FORMAT_CLASS failed translating the binary label to a string Cause: VMS system service $FORMAT_CLASS failed because the given binary classification was not valid. Action: Examine system error message and refer to SEVMS documentation ORA-07618: $IDTOASC failed translating a secrecy level Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level. Action: Define the entry in the rights database which the binary label you specified references. ORA-07619: $IDTOASC failed translating an integrity level Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level. Action: Define the entry in the rights database which the binary label you specified references. ORA-07620: smscre: illegal database block size Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size. Action: Change db_block_size in the parameter file to conform to these limits. ORA-07621: smscre: illegal redo block size Cause: An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512. Action: Change log_buffer in the parameter file to conform to these limits. ORA-07622: smscre: $CREATE failure Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed. Action: Examine the system error message and refer to VMS documentation. ORA-07623: smscre: $CRMPSC failure Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed. Action: Examine the system error message and refer to VMS documentation. ORA-07624: smsdes: $DGBLSC failure Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed. Action: Examine the system error message and refer to VMS documentation. ORA-07625: smsget: $MGBLSC failure Cause: While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. The usual reason is that Oracle has not been started up. Action: Examine the system error message and refer to VMS documentation. Start up Oracle if it is not already started. ORA-07626: smsget: sga already mapped Cause: An attempt to map the SGA during logon failed because it was already mapped. This is an internal error. Action: Exit your program and try again, and report this to your customer support representative. ORA-07627: smsfre: $CRETVA failure Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed. Action: Examine the system error message and refer to VMS documentation. ORA-07628: smsfre: sga not mapped Cause: An attempt to unmap the SGA during logoff failed because it was not mapped. This is an internal error. Action: Exit your program and try again, and report this to your customer support representative. ORA-07629: smpall: $EXPREG failure Cause: While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded. Action: Examine the system error message and refer to VMS documentation. ORA-07630: smpdal: $DELTVA failure Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed. Action: Examine the system error message and refer to VMS documentation. ORA-07631: smcacx: $EXPREG failure Cause: While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded. Action: Examine the system error message and refer to VMS documentation. ORA-07632: smsrcx: $DELTVA failure Cause: While deleting a context area, VMS system service $DELTVA failed. Action: Examine the system error message and refer to VMS documentation. ORA-07633: smsdbp: illegal protection value Cause: The buffer debug function was called with an illegal value. This is an internal error. Action: Contact your customer support representative. ORA-07634: smsdbp: $CRETVA failure Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed. Action: Contact your customer support representative. ORA-07635: smsdbp: $SETPRT failure Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed. Action: Contact your customer support representative. ORA-07636: smsdbp: $MGBLSC failure Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed. Action: Contact your customer support representative. ORA-07637: smsdbp: buffer protect option not specified when sga created Cause: Trying to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error. Action: Contact your customer support representative. ORA-07638: smsget: SGA pad area not large enough for created SGA Cause: An attempt was made to map an SGA with software in which the SGA pad area isn"t large enough. Action: Create a smaller SGA, or relink the software with a larger pad. ORA-07639: smscre: SGA pad area not large enough (string bytes required) Cause: An attempt was made to create an SGA with software in which the SGA pad area isn"t large enough. Action: Create a smaller SGA, or relink the software with a larger pad. ORA-07640: smsget: SGA not yet valid. Initialization in progress Cause: An attempt was made to map to the SGA while it was being initialized. Action: Wait until initialization is complete, and try again. ORA-07641: smscre: Unable to use the system pagefile for the SGA Cause: The system global area (SGA) backing file could not be allocated using the system pagefile because the system-wide limit on global pages has been exceeded. Action: Either increase the VMS system parameter GBLPAGFIL or use a disk file as the SGA backing file. ORA-07642: smprtset: $CMKRNL failure Cause: While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service. Action: Examine the system error message and refer to VMS documentation. ORA-07643: smsalo: SMSVAR is invalid Cause: an internal error Action: Report this error to Oracle Support Services, provide your INIT.ORA file. ORA-07645: sszfsl: $CHANGE_CLASS failure Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed. Action: Examine the system message and refer to SEVMS system documentation. ORA-07646: sszfck: $CREATE failure Cause: While attempting to create a file, VMS system service $CREATE failed. Action: Examine the system message and refer to VMS system documentation. ORA-07647: sszfck: $OPEN failure Cause: While attempting to reopen a file, VMS system service $OPEN failed. Action: Examine the system message and refer to VMS system documentation. ORA-07650: sigunc: $GETJPIW failure Cause: While attempting to get the user"s terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed. Action: Examine the system error message and refer to VMS documentation. ORA-07655: slsprom:$TRNLOG failure Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed. Action: Examine the system error message and refer to VMS documentation. ORA-07656: slsprom:$GETDVI failure Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed. Action: Examine the system error message and refer to VMS documentation. ORA-07657: slsprom:$ASSIGN failure Cause: While prompting for a password, VMS system service $ASSIGN failed. Action: Examine the system error message and refer to VMS documentation. ORA-07658: slsprom:$QIOW read failure Cause: While prompting for a password, VMS system service $QIOW failed. Action: Examine the system error message and refer to VMS documentation. ORA-07665: ssrexhd: recursive exception encountered string string string string string string Cause: A VMS exception occurred while executing in the Oracle exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error. Action: Contact your customer support representative. ORA-07670: $IDTOASC failed translating a secrecy category Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category. Action: Define the entry in the rights database which the binary label you specified references. ORA-07671: $IDTOASC failed translating an integrity category Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category. Action: Define the entry in the rights database which the binary label you specified references. ORA-07672: $PARSE_CLASS failed translating the string into a binary label Cause: SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification. Action: Examine system error message and refer to SEVMS documentation. ORA-07680: sou2os: another call to Oracle currently executing Cause: A call to the Oracle shared image entry point occurred from within the shared image. This is an internal error. Action: Contact your customer support representative. ORA-07681: sou2os: An error occurred while initializing Oracle Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error. Action: Contact your customer support representative. ORA-07682: sou2os: set kernel dispatch fail err Cause: During Oracle shared image entry, a dispatch to kernel mode failed. Action: Make sure that your shared image is installed with the CMKRNL privilege, then contact your customer support representative. ORA-07683: sou2os: $SETPRV reset error Cause: During an attempt to restore user privileges at Oracle shared image exit, VMS system service $SETPRV failed. This is an internal error. Action: Contact your customer support representative. ORA-07684: sou2os: supervisor stack reset error Cause: During an attempt to restore the supervisor-mode stack at Oracle shared image exit, VMS system service $SETSTK failed. This is an internal error. Action: Contact your customer support representative. ORA-07685: sou2os: supervisor stack set error Cause: During an attempt to set the Oracle supervisor-mode stack at Oracle shared image entry, VMS system service $SETSTK failed. This is an internal error. Action: Contact your customer support representative. ORA-07700: sksarch: interrupt received Cause: An interrupt was received while archiving the logs Action: Retry operation ORA-07701: sksatln: internal exception: output buffer too small Cause: Overflow of buffer for parsing archive control text string Action: This is an internal error, please report to Oracle ORA-07702: unrecognized device type in archive text Cause: Unrecognized device type in archive text Action: This is an internal error, please report to Oracle ORA-07703: error in archive text: need "/" after device type Cause: The archive control text in the ARCHIVE command is invalid; the device type (to indicate a file or tape) must be followed by a "/". Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07704: error in archive text: need ":" after device name Cause: The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ":". Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07705: sksaprs: device name buffer too small Cause: The buffer supplied for the device name is too small. This is an internal error. Action: Contact your customer support representative. ORA-07706: error in archive text: need disk file name Cause: The archive control text in the ARCHIVE command is invalid; the disk file name is missing. Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07707: error in archive text: need tape label name Cause: The archive control text in the ARCHIVE command is invalid; the tape label name is missing. Action: Refer to the SQLDBA Guide for the proper syntax of the text. ORA-07708: sksaprs: tape label name buffer too small Cause: The buffer supplied for the tape label is too small. This is an internal error. Action: Contact your customer support representative. ORA-07709: sksaprs: archiving to a remote host is not allowed Cause: The user specified a remote disk for archiving via DECnet. Action: Archive to a disk on the local host. ORA-07710: sksaprs: file name buffer too small Cause: The buffer supplied for the file name is too small. This is an internal error. Action: Contact your customer support representative. ORA-07713: sksamtd: could not mount archival device (SYS$MOUNT failure) Cause: VMS system service SYS$MOUNT failed Action: Examine system error message and refer to VMS documentation ORA-07715: sksadtd: could not dismount archival device (SYS$DISMNT failure) Cause: VMS system service SYS$DISMNT failed Action: Examine system error message and refer to VMS documentation ORA-07716: sksachk: invalid device specification for ARCHIVE Cause: VMS system service SYS$GETDVI failed" Action: Specify a valid device in ARCHIVE control string ORA-07717: sksaalo: error allocating memory Cause: VMS system service LIB$GET_VM failed" Action: Examine system error message and refer to VMS documentation ORA-07718: sksafre: error freeing memory Cause: VMS system service LIB$FREE_VM failed Action: Examine system error message and refer to VMS documentation ORA-07721: scgcm: not enough OS resource to obtain system enqueue Cause: d by the messages SS$_EXENQLM or SS$_INSFMEM. Action: Free up some of the required resource to allow the creation of the required lock. ORA-07740: slemop: incorrect handle size (programming error) Cause: structures used for reading error message files do not match Action: this is an internal error, please report to Oracle ORA-07741: slemop: $OPEN failure Cause: VMS system service $OPEN failed Action: Examine system error message and refer to VMS documentation ORA-07742: slemop: $CONNECT failure Cause: VMS system service $CONNECT failed Action: Examine system error message and refer to VMS documentation ORA-07743: slemop: incorrect error file attributes Cause: An error message file is of incorrect format Action: Unless an error file has been changed, report this to Oracle ORA-07744: slemcl: invalid error message file handle Cause: seal in passed in handle does not match correct value Action: this is an internal error, please report to Oracle ORA-07745: slemcl: $CLOSE failure Cause: VMS system service $CLOSE failed Action: Check system error and refer to VMS documentation ORA-07746: slemrd: invalid error message file handle Cause: seal in passed in handle does not match correct value Action: this is an internal error, please report to Oracle ORA-07747: slemrd: $READ failure Cause: VMS system service $READ failed Action: Check system error and refer to VMS documentation ORA-07750: slemcr: fopen failure Cause: An attempt to create a message file failed. This is an internal error. Action: Contact your customer support representative. ORA-07751: slemcr: malloc failure Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error. Action: Contact your customer support representative. ORA-07753: slemcf: fseek before write failure Cause: An attempt to seek before writing a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07754: slemcf: fwrite failure Cause: An attempt to write a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07755: slemcf: fseek before read failure Cause: An attempt to seek before reading a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07756: slemcf: fread failure Cause: An attempt to read a message file cache element failed. This is an internal error. Action: Contact your customer support representative. ORA-07757: slemcc: invalid handle Cause: The seal in a passed-in handle does not match correct value. This is an internal error. Action: Contact your customer support representative. ORA-07758: slemcw: invalid handle Cause: The seal in a passed-in handle does not match correct value. This is an internal error. Action: Contact your customer support representative. ORA-07759: slemtr: invalid destination Cause: The destination string provided to the function is too short This is an internal error. Action: Contact your customer support representative. ORA-07760: slemtr: $open failure Cause: the $open service failed. This is an internal error Action: Contact your customer support representative. ORA-07800: slbtpd: invalid number Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed ORA-07801: slbtpd: invalid exponent Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed ORA-07802: slbtpd: overflow while converting to packed decimal Cause: An impossible request for binary to decimal conversion was made Action: This conversion cannot be performed ORA-07803: slpdtb: invalid packed decimal nibble Cause: An impossible request for decimal to binary conversion was made Action: This conversion cannot be performed ORA-07804: slpdtb: number too large for supplied buffer Cause: An impossible request for decimal to binary conversion was made Action: This conversion cannot be performed ORA-07820: sspscn: SYS$CRELNM failure Cause: An error was returned from the SYS$CRELNM function Action: Check system error and refer to VMS documentation ORA-07821: sspsdn: SYS$DELLNM failure Cause: An error was returned from the SYS$DELLNM function Action: Check system error and refer to VMS documentation ORA-07822: sspscm: SYS$CREMBX failure Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07823: sspsqr: $QIO failure Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07824: sspain: $SETIMR failure Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer. Action: Check system error and refer to VMS documentation ORA-07825: sspsck: $QIO failure at AST level Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07826: sspscm: SYS$GETDVIW failure Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox. Action: Check system error and refer to VMS documentation ORA-07840: sllfop: LIB$GET_VM failure Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an i/o vector. Action: Check system error and refer to VMS documentation ORA-07841: sllfop: SYS$OPEN failure Cause: An error was returned from SYS$OPEN while attempting to open the data file for reading Action: Check system error and refer to VMS documentation ORA-07842: sllfcl: SYS$CLOSE failure Cause: An error was returned from SYS$CLOSE while attempting to close the input data file Action: Check system error and refer to VMS documentation ORA-07843: sllfcl: LIB$FREE_VM failure Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the i/o vector Action: Check system error and refer to VMS documentation ORA-07844: sllfop: LIB$GET_VM failure Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers Action: Check system error and refer to VMS documentation ORA-07845: sllfcl: LIB$FREE_VM failue Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers Action: Check system error and refer to VMS documentation ORA-07846: sllfop: string byte record too big for string byte user buffer Cause: The longest record in the file will not fit into the largest data buffer that can be allocated Action: Modify the RMS file to have smaller records ORA-07847: sllfop: $CONNECT failure Cause: An error was returned by SYS$CONNECT while attempting to open the data file Action: Check system error and refer to VMS documentation ORA-07848: sllfrb: $GET failure Cause: An error was returned by SYS$GET while attempting to read the data file Action: Check system error and refer to VMS documentation ORA-07849: sllfsk: $GET failure Cause: An error was returned by SYS$GET while attempting to skip records in the input file Action: Check system error and refer to VMS documentation ORA-07850: sllfop: bad option Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others. Action: Check documentation ORA-07860: osnsoi: error setting up interrupt handler Cause: An error occurred while setting up the control interrupt handler Action: This is an internal error. Contact your Oracle representative. ORA-07880: sdopnf: internal error Cause: A list of all files open by this process could not be obtained. Action: This is an internal error. Contact your customer support representative. ORA-08000: maximum number of session sequence lists exceeded Cause: the sequence parent state objects for this session are all used Action: an internal error; quit the session and begin a new one ORA-08001: maximum number of sequences per session exceeded Cause: the limit on the number of sequences usable by session has been hit Action: increase INIT.ORA parameter user_sequences to get more ORA-08002: sequence string.CURRVAL is not yet defined in this session Cause: sequence CURRVAL has been selected before sequence NEXTVAL Action: select NEXTVAL from the sequence before selecting CURRVAL ORA-08003: sequence string.NEXTVAL exceeds internal limits Cause: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal represention size. Action: Alter or recreate the sequence number with legal limits. ORA-08004: sequence string.NEXTVAL string stringVALUE and cannot be instantiated Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE Action: alter the sequence so that a new value can be requested ORA-08005: specified row does not exist Cause: A row with the given rowid does not exist in any of the tables given Action: check the query for misspellings of table names and the rowid ORA-08006: specified row no longer exists Cause: the row has been deleted by another user since the operation began Action: re-try the operation ORA-08007: Further changes to this block by this transaction not allowed Cause: Max locks have been reached for this transaction in this block Action: Commit changes ORA-08008: another instance is mounted with USE_ROW_ENQUEUES = string Cause: the shared instance being started does not have the same value for use_row_enqueues as already running instances Action: ensure that all instances" INIT.ORA files specify the same value for the parameter "use_row_enqueues" ORA-08100: index is not valid - see trace file for diagnostics Cause: Validate Index detected an inconsistency in its argument index Action: Send trace file to your customer support representative ORA-08101: index key does not exist file string: (root string, node string) blocks (string) Cause: Internal error: possible inconsistency in index Action: Send trace file to your customer support representative, along with information on reproducing the error ORA-08102: index key not found, obj# string, file string, block string (string) Cause: Internal error: possible inconsistency in index Action: Send trace file to your customer support representative, along with information on reproducing the error ORA-08103: object no longer exists Cause: The object has been deleted by another user since the operation began, or a prior incomplete recovery restored the database to a point in time during the deletion of the object. Action: Delete the object if this is the result of an incomplete recovery. ORA-08104: this index object string is being online built or rebuilt Cause: the index is being created or rebuild or waited for recovering from the online (re)build Action: wait the online index build or recovery to complete ORA-08105: Oracle event to turn off smon cleanup for online index build Cause: set this event only under the supervision of Oracle development Action: debugging only ORA-08106: cannot create journal table string.string Cause: The online index builder could not create its journal table Action: rename your table in conflict or rerun the SQL statement * there may be a concurrent online index rebuild on the same object. ORA-08108: may not build or rebuild this type of index online Cause: only support normal index or IOT top-level index Action: change your index type ORA-08109: nosort is not a supported option for online index build Cause: may not specify nosort for online index build Action: get rid of nosort in the index creation command ORA-08110: Oracle event to test SMON cleanup for online index build Cause: Oracle Kernel test only Action: Donot set this event(for test only) ORA-08111: a partitioned index may not be coalesced as a whole Cause: User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal Action: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE) ORA-08112: a composite partition may not be coalesced as a whole Cause: User attempted to coalesce a composite partition Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE) ORA-08113: composite partition index may not be compressed Cause: User attempted to compress a composite partition index Action: create uncompressed composite partition index ORA-08114: can not alter a fake index Cause: User attempted to alter a fake index Action: drop fake index ORA-08115: can not online create/rebuild this index type Cause: User attempted to create index type that online doesnot support Action: use offline index create/rebuild command ORA-08116: can not acquire dml enough lock(S mode) for online index build Cause: User attempted to create index online without allowing DML Share lock Action: allow DML share lock on the base table ORA-08117: Index Organized Table operation released its block pin Cause: Block maintenance forced the release of a block pin Action: Contact your customer support representative ORA-08118: Deferred FK constraints cannot be enforced, index too big (string) Cause: Deferred Foreign Key constraints cannot be enforced due to the index key being too big and built on a non-default DB_BLOCK_SIZE. Action: First try to drop the Foreign Key and then the primary key. ORA-08119: The new initrans will make the index too big Cause: Specifying the initrans need additional space to hold the index key which might make the index too big Action: Try giving a smaller initrans value ORA-08120: Need to create SYS.IND_ONLINE$ table in order to (re)build index Cause: Alter index Build/Rebuild online require existing of SYS.IND_ONLINE$ table. Action: User/DBA needs to create sys.ind_online$ before alter the index /rdbms/admin/catcio.sql contains script to create ind_online$. ORA-08121: Number of indexes need to be maintained offline exceeds limit for DML Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes for each DML statement Action: Make sure the index maintainance is online. If indexes need to be maintained offline, drop some indexes. ORA-08175: discrete transaction restriction violated (string) Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction. Action: Rollback the transaction, and retry it as a normal transaction. ORA-08176: consistent read failure; rollback data not available Cause: Encountered data changed by an operation that does not generate rollback data : create index, direct load or discrete transaction. Action: In read/write transactions, retry the intended operation. Read only transactions must be restarted. ORA-08177: can"t serialize access for this transaction Cause: Encountered data changed by an operation that occurred after the start of this serializable transaction. Action: In read/write transactions, retry the intended operation or transaction. ORA-08178: illegal SERIALIZABLE clause specified for user INTERNAL Cause: Serializable mode is not supported for user INTERNAL. Action: Reconnect as another user and retry the SET TRANSACTION command. ORA-08179: concurrency check failed Cause: Encountered data changed by an operation that occurred after a specific snapshot. This is usually used to indicate that a particular cached copy of a datablock is stale. This is used for internal use for now. Action: refresh the cached copy of the datablock and retry operation. ORA-08180: no snapshot found based on specified time Cause: Could not match the time to an SCN from the mapping table. Action: try using a larger time. ORA-08181: specified number is not a valid system change number Cause: supplied scn was beyond the bounds of a valid scn. Action: use a valid scn. ORA-08182: operation not supported while in Flashback mode Cause: user tried to do dml or ddl while in Flashback mode Action: disable Flashback and re-attempt the operation ORA-08183: Flashback cannot be enabled in the middle of a transaction Cause: user tried to do Flashback in the middle of a transaction Action: do a commit ORA-08184: attempting to re-enable Flashback while in Flashback mode Cause: as stated above Action: disable first before re-enabling ORA-08185: Flashback not supported for user SYS Cause: user logged on as SYS Action: logon as a different (non SYS) user. ORA-08186: invalid timestamp specified Cause: as stated above Action: enter a valid timestamp ORA-08187: snapshot expression not allowed here Cause: A snapshot expression using AS OF was specified when not allowed. Action: Do not use the AS OF clause ORA-08189: cannot flashback the table because row movement is not enabled Cause: An attempt was made to perform Flashback Table operation on a table for which row movement has not been enabled. Because the Flashback Table does not preserve the rowids, it is necessary that row movement be enabled on the table. Action: Enable row movement on the table ORA-08190: restore point string is from a different incarnation of the database Cause: An attempt was made to perform Flashback Table operation using a restore point from a different incarnation of the database Action: Provide a restore point from the current database incarnation ORA-08191: Flashback Table operation is not supported on remote tables Cause: An attempt was made to perform Flashback Table operation on a remote table. This is not permitted. Action: Do not perform a Flashback Table operation on remote tables. ORA-08192: Flashback Table operation is not allowed on fixed tables Cause: An attempt was made to perform Flashback Table operation on a fixed table. This is not permitted. Action: Do not perform a Flashback Table operation on fixed tables. ORA-08193: Flashback Table operation is not allowed on temporary tables Cause: An attempt was made to perform Flashback Table operation on a temporary table. This is not permitted. Action: Do not perform a Flashback Table operation on temporary tables. ORA-08194: Flashback Table operation is not allowed on materialized views Cause: An attempt was made to perform Flashback Table operation on a materialized view. This is not permitted. Action: Do not perform a Flashback Table operation on materialized views or snapshot logs. ORA-08195: Flashback Table operation is not supported on partitions Cause: An attempt was made to perform Flashback Table operation on a partition. This is not permitted. Action: Do not perform a Flashback Table operation on partitions. ORA-08196: Flashback Table operation is not allowed on AQ tables Cause: An attempt was made to perform Flashback Table operation on AQ tables. This is not permitted. Action: Do not perform a Flashback Table operation on AQ tables. ORA-08197: Flashback Table operation is not supported on clustered tables Cause: An attempt was made to perform Flashback Table operation on a clustered table. This is not permitted. Action: Do not perform a Flashback Table operation on clustered tables. ORA-08198: Flashback Table is not supported on object tables, nested tables Cause: An attempt was made to perform Flashback Table operation on a object table or a nested table or a table with nested table column. This is not permitted. Action: Do not perform a Flashback Table operation on such tables. ORA-08199: Flashback Table operation is not supported on this object Cause: An attempt was made to perform Flashback Table operation on an object on which the operation is not supported. Action: Do not perform a Flashback Table operation on such objects. ORA-08205: ora_addr: $ORACLE_SID not set in environment Cause: The environment variable ORACLE_SID is not set. Action: Set the ORACLE_SID environment variable. ORA-08206: ora_addr: cannot translate address file name Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf. Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set. ORA-08207: ora_addr: cannot open address file Cause: The address file could not be opened. Action: Check that ORACLE is up. Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct permissions. ORA-08208: ora_addr: cannot read from address file Cause: The address file could not be read. Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of text. ORA-08209: scngrs: SCN not yet initialized Cause: The System Commit Number has not yet been initialized. Action: Contact your customer support representative. ORA-08210: Requested I/O error Cause: Oracle requested that an I/O error be returned for this operation. Action: This should not occur in normal Oracle operation. Contact support. ORA-08230: smscre: failed to allocate SGA Cause: The n_core system call failed, maybe due to insufficient memory. Action: Specify a smaller number of buffers. Check INIT.ORA parameters. ORA-08231: smscre: unable to attach to SGA Cause: The process cannot attach to the SGA. This can happen if either the listener can"t attach, or the process cannot communicate with the listener. Action: Verify that the instance is up and running. Contact your customer support representative. ORA-08232: smsdes: cannot detach from SGA Cause: Probably, the listener process has died. Action: Contact your customer support representative. ORA-08233: smsdes: cannot unmap SGA Cause: The n_core system call failed while detaching from the SGA. Action: Note nCX error returned; contact your customer support representative. ORA-08234: smsget: cannot get instance listener address Cause: The instance listener address cannot be read from the sgadef file. Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional information gives error return from ora_addr. ORA-08235: smsget: listener not on this node Cause: A process wishing to attach to the SGA is on a different node from its instance"s listener. Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact your customer support representative. ORA-08236: smsget: cannot share subcube with listener Cause: The n_share call failed, probably because the listener has died. Action: Check if the listener is running, and contact your customer support representative. ORA-08237: smsget: SGA region not yet created Cause: Attempting to attach to an SGA which has not yet been created. Action: Verify that the instance is running. Contact your customer support representative. ORA-08238: smsfre: cannot detach from SGA Cause: The n_core system call failed while detaching from the SGA. Action: Check nCX error, and contact your customer support representative. ORA-08260: ora_addr: cannot open nameserver Cause: A process could not connect to the nameserver. Action: Make sure the nameserver is up and running. Additional information gives nameserver"s returned status. ORA-08261: ora_addr: cannot find name in nameserver Cause: The listener nameserver entry for an instance could not be found. Action: Make sure the nameserver is up and running. Additional information gives nameserver"s returned status. ORA-08263: ora_addr: cannot free listener address Cause: The listener nameserver entry could not be freed Action: Additional information gives nameserver"s returned status. Contact your customer support representative. ORA-08264: ora_addr: cannot close nameserver Cause: The connection to the nameserver could not be closed. Action: Additional information gives nameserver"s returned status. Contact your customer support representative. ORA-08265: create_ora_addr: cannot open nameserver Cause: A process could not connect to the nameserver. Action: Make sure the nameserver is up and running. Additional information gives nameserver"s returned status. ORA-08266: create_ora_addr: cannot register name in nameserver Cause: The listener"s addressing information could not be registered. Action: Make sure the nameserver is up and running. Additional information gives nameserver"s returned status. ORA-08267: destroy_ora_addr: cannot close nameserver Cause: The connection to the nameserver could not be closed. Action: Additional information gives nameserver"s returned status. Contact your customer support representative. ORA-08268: create_ora_addr: cannot close nameserver Cause: The connection to the nameserver could not be closed. Action: Additional information gives nameserver"s returned status. Contact your customer support representative. ORA-08269: destroy_ora_addr: cannot destroy name Cause: The listener"s addressing information could not be removed. Action: Additional information gives nameserver"s returned status. Contact your customer support representative. ORA-08270: sksachk: Illegal archival control string Cause: Archive files cannot be created with the given archival control string. Action: Check that the volume exists ORA-08271: sksabln: Buffer size not large enough for archive control string Cause: The given archival control string expands into too many characters. Action: Reduce archive control string length. ORA-08274: Out of memory for environment variable Cause: There is insufficient memory to return the requested value Action: Reduce memory usage and retry. ORA-08275: Environment variable unset Cause: The requested environment variable is not set Action: Ensure that the variable name requested is correct. ORA-08276: No room in nameserver for pid Cause: There is no room to record the pid for a background process Action: Shutdown abort and restart the database. ORA-08277: Cannot set environment variable Cause: There is insufficient memory to expand the environment. Action: Reduce memory usage and retry. ORA-08278: Cannot get CPU statistics Cause: Could not retrieve CPU times because n_stat failed. Action: Contact customer support. ORA-08308: sllfop: Cannot open file Cause: Oracle could not open a file. Action: Check the Unix errno returned as additional information. ORA-08309: sllfop: Cannot fstat file Cause: Oracle could not obtain information about an open file. Action: Check the Unix errno returned as additional information. ORA-08310: sllfop: Bad value for recsize Cause: An illegal value for the record size was specified. Action: Specify a value for the recsize option that is greater than 0. ORA-08311: sllfop: bad value for maxrecsize Cause: An illegal value for the maximum record size was specified. Action: Specify a value for the maxrecsize option that is greater than 0. ORA-08312: sllfop: unrecognized processing option Cause: An unrecognized processing option was specified. Action: Check the Oracle for nCUBE 2 User"s Guide for valid options. ORA-08313: sllfop: could not allocate buffers Cause: Memory for the load buffers could not be allocated. Action: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again. ORA-08314: sllfcf: Error closing file Cause: An error occurred trying to close a file. Action: Check the Unix errno returned as additional information. ORA-08315: sllfrb: Error reading file Cause: An error occurred trying to read from a file. Action: Check the Unix errno returned as additional information. ORA-08316: sllfsk: Error seeking in file. Cause: The lseek system call returned an error. Action: Check the Unix errno returned as additional information. ORA-08317: sllfsk: Error seeking in file. Cause: The lseek system call returned an error. Action: Check the Unix errno returned as additional information. ORA-08318: sllfsk: Error reading file Cause: An error occurred trying to read from a file. Action: Check the Unix errno returned as additional information. ORA-08319: sllfsk: Error reading file Cause: An error occurred trying to read from a file. Action: Check the Unix errno returned as additional information. ORA-08320: scnget: Call to scnget before scnset or scnfnd. Cause: An internal error Action: Contact your customer support representative. ORA-08321: scnmin: NOT IMPLEMENTED YET Cause: An internal error Action: Contact your customer support representative. ORA-08322: scnmin: open/convert of bias lock failed Cause: A call to the lkmgr failed to open and convert the bias lock Action: Check to make sure the lkmgr is up. ORA-08323: scnmin: close of bias lock failed Cause: A call to the lkmgr failed to close the bias lock Action: Check to make sure the lkmgr is up. ORA-08330: Printing not supported Cause: An attempt was made to automatically spool a file to the printer Action: none ORA-08331: Wait operation timed out Cause: Oracle timed out waiting for an event Action: Contact your Oracle support representative ORA-08332: rollback segment #string specified not available Cause: (same as 1545) Action: (same as 1545). Also, make sure you have created enough rollback segments for the number of instances you are trying to start. ORA-08340: This command not allowed on nCUBE, only one thread is ever used. Cause: An illegal command was executed for the nCUBE platform. Action: There is no need to issue this command. ORA-08341: On nCUBE, this command can only be executed from instance 1. Cause: A command that can only be issued on instance 1 was issued elsewhere. Action: Log on to instance 1 and repeat the command. ORA-08342: sropen: failed to open a redo server connection Cause: An error occurred trying to connect to the redo server. Action: The OS specific error message should tell you what to do. ORA-08343: srclose: failed to close a redo server connection Cause: An error occurred trying to close the redo server connection. Action: The OS specific error message should tell you what to do. ORA-08344: srapp: failed to send redo data to the redo server Cause: An error occurred trying to send redo to the redo server. Action: The OS specific error message should tell you what to do. ORA-08401: invalid compiler name: string Cause: An invalid compiler name was passed to a UTL_PG conversion routine. Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine. ORA-08412: error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message Cause: The WMSGBSIZ is the maximun size for warning message block, it is recommanded to be 1024 bytes to 8 kbytes. Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK). ORA-08413: invalid compiler type in FORMAT parameter at string Cause: An invalid compiler type is defined in format control block. The format control block is invalid. Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. ORA-08414: error encountered in string Cause: The function returned an error. Where may be: RAW_TO_NUMER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT Action: to take. ORA-08429: raw data has invalid digit in display type data Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit. Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. ORA-08430: raw data missing leading sign Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign. Action: Correct the input raw data or the mask options so that they match. ORA-08431: raw data missing zero as defined in picture Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero. Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. ORA-08432: raw data has invalid floating point data Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data. Action: Correct the input raw data. ORA-08433: invalid picture type in convert raw to number Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type. Action: Correct the picture mask parameter. ORA-08434: raw data has invalid trailing sign Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign. Action: Correct the input raw data or the mask options so that they match. ORA-08435: PICTURE MASK missing the leading sign when SIGN IS LEADING specified Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign. Action: Correct the input raw data or the mask options so that they match. ORA-08436: raw data has invalid sign digit Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign. Action: Correct the input raw data or the picture mask so that they match. ORA-08437: invalid picture type in picture mask Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type. Action: Correct the picture mask parameter. ORA-08440: raw buffer is too short to hold converted data Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask. Action: Increase the raw buffer size to the size necessary to hold the entire result of the conversion. ORA-08441: closed parenthesis missing in picture mask Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine. Action: Correct the picture mask. ORA-08443: syntax error in BLANK WHEN ZERO clause in mask options Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: BLANK ZERO BLANK ZEROS BLANK ZEROES BLANK WHEN ZERO BLANK WHEN ZEROS BLANK WHEN ZEROES Action: Correct the mask options parameter. ORA-08444: syntax error in JUSTIFIED clause in mask options Cause: A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: JUST JUST RIGHT JUSTIFIED JUSTIFIED RIGHT Action: Correct the mask options parameter. ORA-08445: syntax error in SIGN clause in mask options Cause: A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SIGN LEADING SIGN LEADING SEPARATE SIGN LEADING SEPARATE CHARACTER SIGN TRAILING SIGN TRAILING SEPARATE SIGN TRAILING SEPARATE CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS LEADING SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING SEPARATE SIGN IS TRAILING SEPARATE CHARACTER Action: Correct the mask options parameter. ORA-08446: syntax error in SYNCHRONIZED clause in mask options Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SYNC SYNC LEFT SYNC RIGHT SYNCHRONIZED SYNCHRONIZED LEFT SYNCHRONIZED RIGHT Action: Correct the mask options parameter. ORA-08447: syntax error in USAGE clause in mask options Cause: A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: USAGE DISPLAY USAGE COMP USAGE COMP-3 USAGE COMP-4 USAGE COMPUTATIONAL USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS DISPLAY USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS COMPUTATIONAL USAGE IS COMPUTATIONAL-3 USAGE IS COMPUTATIONAL-4 Action: Correct the mask options parameter. ORA-08448: syntax error in DECIMAL-POINT environment clause Cause: A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA Action: Correct the environment clause parameter. ORA-08449: invalid numeric symbol found in picture mask Cause: An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine. Action: Correct the picture mask parameter. ORA-08450: invalid specification of CR in picture mask Cause: The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask. Action: Correct the picture mask parameter. ORA-08451: invalid specification of DB in picture mask Cause: The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask. Action: Correct the picture mask parameter. ORA-08452: specification of E in picture mask is unsupported Cause: The floating point exponent symbol "E" was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines. Action: Correct the picture mask parameter, and the data, if necessary. ORA-08453: more than one V symbol specified in picture mask Cause: The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator ("V"). Only one decimal point indicator is allowed in the picture mask. Action: Correct the picture mask parameter. ORA-08454: more than one S symbol specified in picture mask Cause: The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator ("S"). Only one operational sign indicator is allowed in the picture mask. Action: Correct the picture mask parameter. ORA-08455: syntax error in CURRENCY SIGN environment clause Cause: A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid currency sign Action: Correct the environment clause parameter. ORA-08456: no sign in picture mask but SIGN clause in mask options Cause: The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol ("S", "+", or "-"), but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause. Action: Correct the picture mask parameter or the mask options parameter. ORA-08457: syntax error in SEPARATE CHARACTER option of SIGN clause Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE SEPARATE CHARACTER Action: Correct the mask options parameter. ORA-08458: invalid format parameter Cause: The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT. Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. ORA-08459: invalid format parameter length Cause: The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length. Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure. ORA-08460: invalid environment clause in environment parameter Cause: The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported. Action: Correct the environment parameter. ORA-08462: raw buffer contains invalid decimal data Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data. Action: Correct the input data. ORA-08463: overflow converting decimal number to Oracle number Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number. Action: Be sure that the input decimal number is valid, and besure that the output variable is large enough to hold the Oracle number value. ORA-08464: input raw decimal data contains more than 42 digits Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number. Action: Correct the raw input buffer. ORA-08465: input mask contains more than 32 characters Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters. Action: Correct the mask input buffer. ORA-08466: raw buffer length string is too short for string Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than %s bytes long, but the picture mask parameter specified that %s bytes of input data were to be converted. Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item. ORA-08467: error converting Oracle number to string Cause: An error occurred when converting an Oracle number to a COBOL of: DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format. mat. Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable. ORA-08468: mask option string is not supported Cause: The mask option was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS COMP-2 POINTER Action: Remove the from the mask options parameter in the PL/SQL call to UTL_PG. ORA-08498: Warning: picture mask "string" overrides picture mask option "USAGE IS string" to "USAGE IS DISPLAY" Cause: Picture mask USAGE option was overridden by the picture mask. Action: This is an informational message only. The message may be eliminated by changing the USAGE option to match the picture mask. ORA-08499: Warning: picture mask options "string" ignored by UTL_PG Cause: Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines. Action: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine. ORA-09200: sfccf: error creating file Cause: Could be out of disk space Action: See OSD error accompanying this message ORA-09201: sfcopy: error copying file Cause: Block sizes may not match Action: See OSD error accompanying this message ORA-09202: sfifi: error identifying file Cause: db_block_size specified in init.ora could be incorrect Action: See OSD error accompanying this message ORA-09203: sfofi: error opening file Cause: File attributes may have changed Action: See OSD error accompanying this message ORA-09204: sfotf: error opening temporary file Cause: Incorrect path may have been specified for the file Action: See OSD error accompanying this message ORA-09205: sfqio: error reading or writing to disk Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09206: sfrfb: error reading from file Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09207: sfsrd: error reading from file Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09208: sftcls: error closing file Cause: File may have been corrupted Action: See OSD error accompanying this message ORA-09209: sftget: error reading from file Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09210: sftopn: error opening file Cause: Incorrect path may have been specified for the file Action: See OSD error accompanying this message ORA-09211: sfwfb: error writing to file Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09212: sfwfbmt: error writing to file Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09213: slgfn: error fabricating file name Cause: Filename may be too long Action: See OSD error accompanying this message ORA-09214: sfdone: I/O error detected Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09215: sfqio: error detected in IOCompletionRoutine Cause: File may have been truncated or corrupted Action: See OSD error accompanying this message ORA-09216: sdnfy: bad value "string" for parameter string Cause: The directory specified as the value for the stated parameter could not be used. Action: Make sure the directory you have specified is a valid directory/file specification. ORA-09217: sfsfs: failed to resize file Cause: Could be out of disk space Action: See OSD error accompanying this message ORA-09218: sfrfs: failed to refresh file size Cause: File may be corrupted or truncated Action: See OSD error accompanying this message ORA-09240: smpalo: error allocating PGA memory Cause: Could be out of memory Action: See OSD error accompanying this message ORA-09241: smsalo: error allocating SGA memory Cause: Could be out of memory Action: See OSD error accompanying this message ORA-09243: smsget: error attaching to SGA Cause: SGA may not have been created (database not started) Action: See OSD error accompanying this message ORA-09260: sigpidu: error obtaining process id Cause: May be out of resources Action: See OSD error accompanying this message ORA-09261: spdcr: error creating detached (background) process Cause: Could be out of resources Action: See OSD error accompanying this message ORA-09262: spdde: error terminating detached (background) process Cause: Could be out of resources Action: See OSD error accompanying this message ORA-09263: spini: error initializing process Cause: Could be out of memory Action: See OSD error accompanying this message ORA-09264: sptpa: error flagging process Cause: Could be out of resources Action: See OSD error accompanying this message ORA-09265: spwat: error temporarily suspending process Cause: Could be out of resources Action: See OSD error accompanying this message ORA-09266: spawn: error starting an Oracle process Cause: Could be out memory Action: See OSD error accompanying this message ORA-09270: szalloc: error allocating memory for security Cause: Could be out of memory Action: See OSD error accompanying this message ORA-09271: szlon: error verifying user name Cause: Username may be too long Action: See OSD error accompanying this message ORA-09272: remote os logon is not allowed Cause: Remote os login attempted when not allowed. Action: See OSD error accompanying this message ORA-09273: szrfc: error verifying role name Cause: An OS error was returned when verifying the role name. Action: See OSD error accompanying this message ORA-09274: szrfc: insufficient role name buffer space Cause: An OS role name was too long. Action: See OSD error accompanying this message ORA-09275: CONNECT INTERNAL is not a valid DBA connection Cause: CONNECT INTERNAL is no longer supported for DBA connections. Action: Please try to connect AS SYSDBA or AS SYSOPER. ORA-09276: All bequeath database links must be loopback database links Cause: A non-loopback bequeath connect string was supplied for a database link. Action: Please use a connect string with a different transport protocol, or specify a loopback connect string (one that points to the instance for the current session) using "(PROGRAM=/bin/oracle)" and, optionally, "(ENVS=""ORACLE_SID="")". ORA-09280: sllfcf: error closing file Cause: File may be corrupted Action: See OSD error accompanying this message ORA-09281: sllfop: error opening file Cause: Possibly incorrect path specified to the file Action: See OSD error accompanying this message ORA-09282: sllfrb: error reading records Cause: File could be corrupted Action: See OSD error accompanying this message ORA-09283: sllfsk: error skipping records Cause: File could be corrupted Action: See OSD error accompanying this message ORA-09284: sllfop: cannot allocate read buffer Cause: malloc() system call returned an error. The system might have run out of heap space Action: Check additional information for the OS error. ORA-09285: sllfop: unrecognizable processing option, incorrect format Cause: Processing option passed is of incorrect format Action: Consult your IUG for permissible formats ORA-09290: sksaalo: error allocating memory for archival Cause: Could be out of memory Action: See OSD error accompanying this message ORA-09291: sksachk: invalid device specified for archive destination Cause: Unable to access directory Action: Specify a valid device in ARCHIVE control string ORA-09292: sksabln: unable to build archive file name Cause: Bad directory or format specified Action: Specify a valid directory in "log_archive_format" and a valid format string in "log_archive_format" in init.ora ORA-09293: sksasmo: unable to send message to console Cause: An error was returned while attempting to send a message to the console operator Action: See OSD error accompanying this message ORA-09300: osncon: unable to connect, DPMI not available Cause: Unable to detect the presence of DPMI Action: Restart Windows and retry ORA-09301: osncon: local kernel only supported in standard mode Cause: An attempt was made to connect to S: while in enhanced mode Action: Restart Windows in standard mode ORA-09310: sclgt: error freeing latch Cause: Internal error Action: See OSD error accompanying this message ORA-09311: slsleep: error temporarily suspending process Cause: May be out of resources Action: See OSD error accompanying this message ORA-09312: slspool: error spooling file to printer Cause: Could be out of resources Action: See OSD error accompanying this message ORA-09313: slsprom: error prompting user Cause: May be out of resources Action: See OSD error accompanying this message ORA-09314: sltln: error translating logical name Cause: Internal buffer may have overflowed Action: See OSD error accompanying this message ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE Cause: Internal error Action: See OSD error accompanying this message ORA-09316: szrpc: unable to verify password for role Cause: OS roles may not be supported for this platform Action: See OSD error accompanying this message ORA-09317: szprv: insufficient privileges Cause: The password specified is invalid Action: See OSD error accompanying this message ORA-09318: slkhst: unable to host out to operating system Cause: There might not be enough memory for the command or hosting out may not be supported on this platform Action: See OSD error accompanying this message ORA-09319: slgtd: unable to obtain the current date and time Cause: The system time might be set incorrectly Action: See OSD error accompanying this message ORA-09320: szrfc: unable to obtain the list of valid OS roles Cause: OS roles may not be supported on this platform Action: See OSD error accompanying this message ORA-09321: slzdtb: unable to convert zoned decimal to binary Cause: internal error Action: See OSD error accompanying this message ORA-09322: slpdtb: unable to convert packed decimal to binary Cause: internal error Action: See OSD error accompanying this message ORA-09330: Session terminated internally by Oracle or by an Oracle DBA Cause: Oracle to terminate that session after about a minute. This message also appears in the trace file if a shutdown abort is performed. Action: none ORA-09340: Specified ORACLE_SID is either invalid or too long Cause: ORACLE_SID must be at the most 4 alphanumeric characters. Action: none ORA-09341: scumnt: unable to mount database Cause: Another instance is currently mounting the database Action: none ORA-09342: Detached process terminated by Oracle during shutdown abort Cause: The user performed a shutdown abort. Action: none ORA-09344: spsig: error signalling thread Cause: This function may not be implemented. Action: none ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area Cause: See OSD error accompanying this message Action: none ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory Cause: See OSD error accompanying this message Action: none ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task Cause: See OSD error accompanying this message Action: none ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore Cause: See OSD error accompanying this message Action: none ORA-09354: Windows 32-bit Two-Task driver: ORACLE task unexpectedly died Cause: See OSD error accompanying this message Action: none ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area Cause: See OSD error accompanying this message Action: none ORA-09361: Windows 3.1 Two-Task driver unable to lock context area Cause: See OSD error accompanying this message Action: none ORA-09362: Windows 3.1 Two-Task driver unable to deallocate context area Cause: See OSD error accompanying this message Action: none ORA-09363: Windows 3.1 Two-Task driver invalid context area Cause: See OSD error accompanying this message Action: none ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window Cause: See OSD error accompanying this message Action: none ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window Cause: See OSD error accompanying this message Action: none ORA-09366: Windows 3.1 Two-Task driver unable to allocate shared memory Cause: See OSD error accompanying this message Action: none ORA-09367: Windows 3.1 Two-Task driver unable to deallocate shared memory Cause: See OSD error accompanying this message Action: none ORA-09368: Windows 3.1 Two-Task driver unable to spawn ORACLE Cause: See OSD error accompanying this message Action: none ORA-09369: Windows 3.1 Two-Task driver bad instance handle Cause: See OSD error accompanying this message Action: none ORA-09370: Windows 3.1 Two-Task driver ORACLE task timed out Cause: See OSD error accompanying this message Action: none ORA-09700: sclin: maximum number of latches exceeded Cause: ORACLE wants to use more latches then available. Action: increase INIT.ORA parameter latch_pages or decrease the amount of shared memory you are using. ORA-09701: scnfy: maximum number of processes exceeded Cause: PROCESSES INIT.ORA parameter exceeded. Action: Decrease the PROCESSES parameter and restart. ORA-09702: sem_acquire: cannot acquire latch semaphore Cause: The semaphore used for accessing latches could not be seized Action: Send trace file to your customer support representative, along with information on reproducing the error. ORA-09703: sem_release: cannot release latch semaphore Cause: The semaphore used for accessing latches could not be released Action: Send trace file to your customer support representative, along with information on reproducing the error. ORA-09704: sstascre: ftok error in creating test and set pages. Cause: the ftok() library call failed in sstastcre(). Action: Verify that tasdef@.dbf file exists. If it does then this is a possible system failure. Perhaps System V compatibility is not enabled. ORA-09705: spcre: cannot initialize latch semaphore Cause: The semaphore used for accessing latches could not be initialized Action: Send trace file to your customer support representative, along with information on reproducing the error. ORA-09706: slsget: get_process_stats error. Cause: get_process_stats system call returned an error. Possible OS error. Action: Check additional information returned. Look for information in OS reference. Contact customer support. ORA-09708: soacon: failed to bind socket to port. Cause: The bind system call failed on the socket. Action: Check additional information for OS error. Try connecting again. ORA-09709: soacon: failed to accept a connection. Cause: The accept system call failed on the socket. Action: Check additional information for OS error. Try connecting again. ORA-09710: soarcv: buffer overflow. Cause: The internal buffer is not big enough to hold the message read. Action: Internal error. Contact customer support representative. ORA-09711: orasrv: archmon already connected. Cause: An existing connection has already been made from archmon to orasrv. Action: Stop trying to connect. ORA-09712: orasrv: log archiver already connected. Cause: An existing connection has already been made from log archiver to orasrv. Action: Stop trying to connect. ORA-09714: Two Task interface: cannot obtain puname Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error) Action: Check if the PUs are named (consistend). ORA-09715: orasrv: cannot obtain puname Cause: Orasrv cannot obtain the name of the PU. (Possible OS error) Action: Check if the PUs are named (consistend). ORA-09716: kslcll: Unable to fix in-flux lamport latch. Cause: One Oracle process died while still holding a lamport latch. Action: Exit (kill) all Oracle user processes. Shutdown (abort) and restart Oracle RDBMS kernel. ORA-09717: osnsui: maximum number of user interrupt handlers exceeded. Cause: The internal limit on the number of user interrupt handlers has been exceeded. Action: Reduce the number of simulataneous logons or reduce the number of user interrupt handlers. ORA-09718: osnsui: cannot set up user interrupt handler. Cause: Malloc() failed to allocate space to hold user interrupt handler. Action: Possible memory resource shortage. ORA-09719: osncui: invalid handle. Cause: The handle passed to osncui is out of the valid range. Action: Use a valid handle. ORA-09740: slsget: cannot get virtual memory region statistics. Cause: The vm_region system call failed to get virual memory region statistics. Action: Check return code in sercerrno. Possible operating system failure. ORA-09741: spwat: error waiting for a post. Cause: Msg_receive system call returned an error. Internal error. Action: Check return code in sercerrno. Port name is returned in sercose[0]. ORA-09742: sppst: error during a post. Cause: Msg_send system call returned an error. Internal error. Action: Check return code in sercerrno. Port name is returned in sercose[0]. ORA-09743: smscre: could not attach shared memory. Cause: The mmap or write system call returned an error. Internal error. Action: Contact Oracle support. ORA-09744: smsget: mmap returned an error. Cause: The mmap system call returned an error. Internal error. Action: Contact Oracle support. ORA-09745: smscre: vm_allocate error, unable to create shared memory. Cause: Error in system call vm_allocate. Failed to create SGA as a single shared memory segment. Action: Check result code returned in sercerrno. Verify that the SGA attach address is valid. ORA-09746: smscre: shared memory attach address incorrect. Cause: The vm_allocate system call attached the SGA at an incorrect location. Action: Verify that the SGA attach address is valid. ORA-09747: pw_detachPorts: server call pws_detach failed. Cause: The call pws_detach to (Oracle helper) failed. Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file. ORA-09748: pws_look_up: fork failed Cause: The pws_look_up call could not fork the (Oracle helper) process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-09749: pws_look_up: port lookup failure Cause: The pws_look_up could not find a port to (Oracle helper). Action: Make sure the (Oracle helper) server has been started correctly by pws_look_up, and that the network name server is still running. ORA-09750: pw_attachPorts: port_rename failed. Cause: The port_rename system call failed; possible internal error. Action: Check return code in sercerrno, report to Oracle customer support. ORA-09751: pw_attachPorts: server call pws_attach failed. Cause: The call pws_attach to (Oracle helper) failed. Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file. ORA-09752: pw_attachPorts: port_allocate failed. Cause: The port_allocate system call failed; possible resource exhaustion. Action: Check return code in sercerrno, report to Oracle customer support. ORA-09753: spwat: invalid process number. Cause: Function was passed an invalid oracle process id. Action: Internal error. Additional information indicates the invalid process id. ORA-09754: sppst: invalid process number passed to sppst. Cause: Function was passed an invalid oracle process id. Action: Internal error. Contact Oracle support. ORA-09755: osngpn: port allocation failure. Cause: The port_allocate system call failed. Action: Possible system resource shortage; check the error code in sercerrno. ORA-09756: osnpns: no port in the name server. Cause: osnpns could not find the given named port in the name server. Action: Check the error code in sercerrno. Make sure the shadow process and network name server are still running. ORA-09757: osnipn: port allocation failure. Cause: The port_allocate system call failed. Action: Possible system resource shortage; check the error code in sercerrno. ORA-09758: osnipn: could not check port in name server. Cause: The netname_check_in call failed. Action: Check the error code in sercerrno. Make sure the network name server is running. ORA-09759: osnsbt: bad message received. Cause: The msg_receive system call failed, or received a bad message. Action: Internal error. Report the error code returned in sercerrno. ORA-09760: osnpui: cannot send break message Cause: The Pipe driver could not send a break message to the ORACLE shadow process break thread. Action: Contact your customer support representative. ORA-09761: pw_destroyPorts: server call pws_stop_instance failed. Cause: The call pws_stop_instance to (Oracle helper) failed. Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file. ORA-09762: sNeXT_instanceName: translation error. Cause: A failure was detected while translating the value of ORACLE_SID. Action: Make sure ORACLE_SID is defined, and that it is of legal length. ORA-09763: osnmpx: send/receive error exchanging Mach ports. Cause: The Mach driver failed to exchange port information with the other side of the connection. Either msg_send (sercose[0] == 1) or msg_receive (sercose[0] == 2) failed. Action: Check return code in sercerrno. Make sure both sides of the connection are still running. ORA-09764: osnmop: access error on oracle executable Cause: The Mach driver could not access the oracle executable. Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path. ORA-09765: osnmop: fork failed Cause: The Mach driver could not fork the oracle shadow process. Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient. ORA-09766: osnmop: buffer allocation failure. Cause: The Mach driver failed to allocate enough vm space for its I/O buffers. Action: Decrease the value of buffer_size parameter in the Two-Task driver hoststring. ORA-09767: osnmfs: bad return code from msg_send. Cause: The msg_send system call failed while flushing the Mach driver"s send buffer. Action: Internal error. Contact your customer support representative. ORA-09768: osnmgetmsg: could not read a message Cause: The msg_receive system call returned a failure code while waiting for a message in the Mach driver. Action: Internal error. Contact your customer support representative. ORA-09769: osnmbr: cannot send break message Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread. Action: Internal error. Contact your customer support representative. ORA-09770: pws_look_up: translation failure. Cause: The pws_look_up routine failed to translate the name of the (Oracle helper) executable. Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct. Additional information gives the translation error code. ORA-09771: osnmwrtbrkmsg: bad return code from msg_send. Cause: The msg_send sytem call failed while sending a Mach driver break. Action: Internal error. Contact your customer support representative. ORA-09772: osnpmetbrkmsg: message from host had incorrect message type Cause: The Mach driver received a message having an unrecognizable message type. Action: Internal error. Contact your customer support representative. ORA-09773: osnmgetdatmsg: message from host had incorrect message type Cause: The Mach driver received a message having an unrecognizable message type. Action: Internal error. Contact your customer support representative. ORA-09774: osnmui: cannot send break message Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread. Action: Internal error. Contact your customer support representative. ORA-09775: osnmrs: reset protocol error Cause: The Mach two-task driver could not reset the connection. Action: Internal error. Contact your customer support representative. ORA-09776: pws_look_up: access error on (Oracle helper) executable Cause: The pws_look_up call could not access the (Oracle helper) executable. Action: Check the permissions on the (Oracle helper) executable and each component of the ORACLE_HOME/bin path. ORA-09777: osnpbr: cannot send break message Cause: The pipe driver could not send a break message to the ORACLE shadow process break thread. Action: Internal error. Contact your customer support representative. ORA-09778: snynfyport: failure allocating the notify port. Cause: The routine failed to allocate or set the task"s notify port. Action: Possible operating system error. Contact Oracle support. ORA-09779: snyGetPort: failure to allocate a port. Cause: The port_allocate system call failed; system resources might be exhausted. Action: Possible operating system error. Contact Oracle support. ORA-09786: sllfop: open error, unable to open file. Cause: Open system call returned an error. Action: Check errno. ORA-09787: sllfop: unrecognizable processing option, incorrect format. Cause: Processing option passed is of incorrect format. Action: Consult your IUG for permissible formats. ORA-09788: sllfrb: unable to read file. Cause: Read system call returned an error. Action: Check errno. Verify file exists. ORA-09789: sllfsk: unable to read file. Cause: Read system call returned an error. Action: Check errno. Verify file exists. ORA-09790: sllfcf: unable to close file. Cause: Close system call returned an error. Action: Check errno. ORA-09791: slembdf: translation error, unable to translate error file name. Cause: Additional information indicates error returned from sltln. Action: Check additional information. ORA-09792: sllfop: cannot allocate read buffer. Cause: Malloc system call returned an error. The system might have run out of heap space. Action: Check additional information for the OS error. ORA-09793: szguns: length of user name is greater than buffer. Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine. Action: This is an internal error. Contact Oracle Support Services. ORA-09794: szrbuild: length of role name is greater than buffer. Cause: The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine. Action: This is an internal error. Contact Oracle Support Services. ORA-09795: szrbuild: malloc of role structure failed. Cause: The allocation of memory for an internal structure used to hold a role descriptor failed. Action: Check the UNIX error number for a possible operating system failure. ORA-09796: szrbuild: malloc of role name failed. Cause: The allocation of memory for an internal buffer used to hold the name of a role failed. Action: Check the UNIX error number for a possible operating system failure. ORA-09797: Failed to get O/S MAC privileges. Cause: The operating system would not allow the retrieval of this process" privileges. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09798: Label comparison failed. Cause: The comparison of two binary labels failed. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09799: File label retrieval failed. Cause: ORACLE was unable to get a label attached to a file. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09800: Process sensitivity label retrieval failed. Cause: ORACLE was unable to get the sensitivity label for a process. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09801: Unable to get user ID from connection Cause: ORACLE was unable to retrieve the user"s ID number from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services. ORA-09802: Conversion of binary label to string failed. Cause: ORACLE was unable to convert a binary label to a string. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09803: Allocation of string buffer failed. Cause: a buffer used to hold the name of the file for which a label was to be obtained could not be allocated. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that ORACLE attempted to allocate is in the "Additional Information" field. ORA-09804: Class conversion from binary to ORACLE failed. Cause: ORACLE was unable to convert a class component from binary format to ORACLE format. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09805: conversion of category number to string failed. Cause: ORACLE was unable to translate a category number to its corresponding string representation failed. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The category number is contained in the "Additional information" field. ORA-09806: Allocation of label string buffer failed. Cause: a temporary buffer used to hold a label could not be allocated. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that ORACLE attempted to allocate is in the "Additional Information" field. ORA-09807: Conversion of label from string to binary failed. Cause: ORACLE was unable to convert the string representation of a label to binary format. Action: Re-enter a valid label. ORA-09808: Could not obtain user clearance. Cause: ORACLE was unable to get a user"s clearance level. Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. ORA-09809: Unable to get user"s group ID from connection Cause: ORACLE was unable to retrieve the user"s group ID number from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services. ORA-09810: Unable to get process ID from connection Cause: ORACLE was unable to retrieve the user"s process ID number from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services. ORA-09811: Unable to initialize package. Cause: ORACLE was unable to initialize the library used to obtain security information. Action: This is an internal error. Contact Oracle Support Services. ORA-09812: Unable to get user clearance from connection Cause: ORACLE was unable to retrieve the user"s operating system session clearance from the SQL*Net connection. Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services. ORA-09813: Unable to get directory status Cause: ORACLE was unable to determine if a directory is multilevel. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. ORA-09814: Unable to expand file name Cause: ORACLE was unable to expand the name of a file that resides in multilevel directory. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. ORA-09815: File name buffer overflow Cause: The buffer that ORACLE uses to hold the expanded name of a too small. Action: This is an internal error. Contact Oracle Support Services. ORA-09817: Write to audit file failed. Cause: ORACLE was unable to write an entry to the file used as the audit trail. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. ORA-09818: Number is too large Cause: ORACLE was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum. Action: Correct the string and repeat the conversion. ORA-09819: Number exceeds maximum legal value Cause: the number specified for a component was greater than the maximum value allowed for that component. Action: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the "Additional information" field. ORA-09820: Conversion of class string to numeric representation failed. Cause: ORACLE was unable to convert a class string to a number because all of the characters in the string were not numeric. Action: Change the string to be either all numbers or all non-numeric characters and repeat the conversion. ORA-09821: Numeric label is not valid Cause: A label specified in ORACLE numeric format was found not to be valid. Action: Re-enter a valid label. Consult your system"s encodings for valid numeric component values. ORA-09822: Translation of audit file name failed. Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST initialization parameter. Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services. ORA-09823: device name is too long Cause: The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name. Action: This is an internal error. Contact Oracle Support Services. ORA-09824: Unable to enable allowmacaccess privilege. Cause: ORACLE was not able to turn on allowmacaccess privilege so that it could do a label comparison. Action: Check the UNIX error number. If it indicates that ORACLE does not have the allowmacaccess privilege, add the allowmacaccess privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using chpriv (1M). If the executable already has the allowmacaccess privilege, contact Oracle Support Services. ORA-09825: Unable to disable allowmacaccess privilege. Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a label comparison. Action: This is an internal error. Contact Oracle Support Services. ORA-09826: SCLIN: cannot initialize atomic latch. Cause: System call atomic_op() return error. Action: Check additional information in the trace file. ORA-09827: SCLGT: atomic latch return unknown error. Cause: System call atomic_op() return unexpected error. Action: Check additional information in the trace file. ORA-09828: SCLFR: atomic latch return error. Cause: System call atomic_op() return unexpected error. Action: Check additional information in the trace file. ORA-09829: pw_createPorts: server call pws_start_instance failed. Cause: The call pws_start_instance to (Oracle helper) failed; system resources might be exhausted. Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file. ORA-09830: snyAddPort: failed to perform a remote procedure call. Cause: The msg_rpc system call returned an error. Action: Internal error. Contact Oracle support. ORA-09831: snyStartThread: failed to build the server port set. Cause: The routine failed to build a port set on which to listen for requests. Action: Possible operating system failure. Contact Oracle support. ORA-09832: infoCallback: bad message format. Cause: The routine received an incorrectly formatted request. Action: Internal error. Contact Oracle support. ORA-09833: addCallback: bad message format. Cause: The routine received an incorrectly formatted request. Action: Internal error. Contact Oracle support. ORA-09834: snyGetPortSet: failed to collect info on a port. Cause: The port_status system called failed. Action: Possible operating system error. Contact Oracle support. ORA-09835: addCallback: callback port is already in a set. Cause: The port to be added to the callback list is already in a port set. Action: Internal error. Contact Oracle support. ORA-09836: addCallback: could not add a port to the callback set. Cause: The port_set_add system called failed. Action: Possible operating system error. Contact Oracle support. ORA-09837: addCallback: could not add allocate a callback link. Cause: The malloc library call failed to allocate space for a callback link. Action: Possible operating system error. Contact Oracle support. ORA-09838: removeCallback: failure removing the callback port. Cause: The port port_set_remove system call failed. Action: Possible operating system error. Contact Oracle support. ORA-09839: removeCallback: callback port is not in the callback set. Cause: The port to be removed to the callback list is not in the callback port set. Action: Internal error. Contact Oracle support. ORA-09840: soacon: Name translation failure. Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@. Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct. ORA-09841: soacon: Name translation failure. Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@. Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct. ORA-09842: soacon: Archmon unable to create named pipe. Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@. Action: Your current OS login may lack write permission for the ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab. ORA-09843: soacon: Archmon unable to create named pipe. Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@. Action: Your current OS login may lack write permission for the ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab. ORA-09844: soacon: Archmon unable to open named pipe. Cause: open() failed to open named pipe ?/dbs/mon2arch_@. Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. ORA-09845: soacon: Archmon unable to open named pipe. Cause: open() failed to open named pipe ?/dbs/arch2mon_@. Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. ORA-09846: soacon: ARCH unable to open named pipe. Cause: open() failed to open named pipe ?/dbs/mon2arch_@. Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. ORA-09847: soacon: ARCH unable to open named pipe. Cause: open() failed to open named pipe ?/dbs/arch2mon_@. Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded. ORA-09850: soacon: Archmon unable to lock named pipe. Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@. Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance. ORA-09851: soacon: Archmon unable to lock named pipe. Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@. Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance. ORA-09853: snyRemovePort: bad return code from request. Cause: The request to remove a port from the callback set returned a failure code. Action: Possible operating system error. Contact Oracle support. ORA-09854: snyPortInfo: bad return code from request. Cause: The request to collect info on a port in the callback set returned a failure code. Action: Possible operating system error. Contact Oracle support. ORA-09855: removeCallback: bad message format. Cause: The routine received an incorrectly formatted request. Action: Internal error. Contact Oracle support. ORA-09856: smpalo: vm_allocate error while allocating pga. Cause: The vm_allocate system call returned an error. Action: Check returned error. Possibly out of system resources. ORA-09857: smprset: vm_protect error while protecting pga. Cause: The vm_protect system call returned an error. Action: Internal error. Contact Oracle support. ORA-09858: sfngat: the input file name is not in the OMF format Cause: The function sfngat() received a filename which is not an OMF file name. Action: Further diagnostic information should be in the error stack. ORA-09859: sfngat: the input file name is not in the autobackup OMF format Cause: The function sfngat() received a filename which is not an autobackup OMF file name. Action: Further diagnostic information should be in the error stack. 9 ORA-12150 to ORA-12236 ORA-12150: TNS:unable to send data Cause: Unable to send data. Connection probably disconnected. Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation. ORA-12151: TNS:received bad packet type from network layer Cause: Internal error. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12152: TNS:unable to send break message Cause: Unable to send break message. Connection probably disconnected. Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation. ORA-12153: TNS:not connected Cause: Not currently connected to a remote host. Action: Reestablish connection. ORA-12154: TNS:could not resolve the connect identifier specified Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: - If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming. ORA-12155: TNS:received bad datatype in NSWMARKER packet Cause: Internal error during break handling. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12156: TNS:tried to reset line from incorrect state Cause: Internal error during break handling. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12157: TNS:internal network communication error Cause: Internal error during network communication. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12158: TNS:could not initialize parameter subsystem Cause: Unable to locate parameter file. Action: Verify that a valid parameter file exists, and is readable. ORA-12159: TNS:trace file not writeable Cause: The trace file to be generated is not writeable by this user. Action: If the user does not have write permissions in the directory to which the trace file will be written, contact an administrator to get the proper permissions or set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a directory the user can write to. ORA-12160: TNS:internal error: Bad error number Cause: Corrupt error reporting subsystem. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12161: TNS:internal error: partial data received Cause: The connection may be terminated. Action: Reconnect and try again. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12162: TNS:net service name is incorrectly specified Cause: The connect descriptor corresponding to the net service name in TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly specified. Action: If using local naming make sure there are no syntax errors in the corresponding connect descriptor in the TNSNAMES.ORA file. If using directory naming check the information provided through the administration used for directory naming. ORA-12163: TNS:connect descriptor is too long Cause: The connect descriptor corresponding to the net service name specified as the connect identifier is too long. The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded. Action: Check the net service name"s connect descriptor in the local naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support. ORA-12164: TNS:Sqlnet.fdf file not present Cause: The sqlnet.fdf file doesn"t exist in $ORACLE_HOME/network/admin. Action: The sqlnet.fdf file is required for Oracle Tracing to occur. Either install the sqlnet.fdf file in $ORACLE_HOME/network/admin or turn off tracing in your ORA file. ORA-12165: TNS:Trying to write trace file into swap space. Cause: Oracle Trace doesn"t allow writing trace information into your swap space. Action: Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk. ORA-12166: TNS:Client can not connect to HO agent. Cause: NVstring contained DESCRIPTION/HO. Action: Call HO agent from integrating server. ORA-12168: TNS:Unable to contact LDAP Directory Server Cause: Cannot contact LDAP directory server to get Oracle Net configuration. Action: Verify that the directory server is up and accessible from the network. Verify that directory access configuration is correct. For more information see the Oracle Internet Directory Administrators Guide or the Oracle Net Administrators Guide. ORA-12169: TNS:Net service name given as connect identifier is too long Cause: The net service name you are attempting to resolve is too long. Action: The maximum length of a net service name is 255 bytes; this limit has been exceeded. Use a smaller net service name. If this is not possible, contact Worldwide Customer Support. ORA-12170: TNS:Connect timeout occurred Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server. Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP). ORA-12171: TNS:could not resolve connect identifier: string Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: - If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming. ORA-12196: TNS:received an error from TNS Cause: The navigation layer received an error from TNS. Action: See the error log file for the specific TNS error. ORA-12197: TNS:keyword-value resolution error Cause: The navigation layer received an error while trying to look up a value for a keyword. Action: Check the syntax of the connect descriptor. ORA-12198: TNS:could not find path to destination Cause: Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down. Action: Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used. ORA-12200: TNS:could not allocate memory Cause: Out of memory on machine. Action: Reconfigure machine to have more storage or run fewer applications while the Interchange is running. ORA-12201: TNS:encountered too small a connection buffer Cause: TNS connection buffer supplied by the application was too small to retrieve the data sent back. Action: Supply a larger connection buffer. If problem persists, call Worldwide Customer Support. ORA-12202: TNS:internal navigation error Cause: Internal navigation error. Action: Not normally visible to the user. For further details contact Worldwide Customer Support. ORA-12203: TNS:unable to connect to destination Cause: Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems. Action: Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node. ORA-12204: TNS:received data refused from an application Cause: The application using Connection Manager refused the connection at the listener. Action: Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Worldwide Customer Support. ORA-12205: TNS:could not get failed addresses Cause: Internal navigation error. Action: Not normally visible to the user. For further details contact Worldwide Customer Support. ORA-12206: TNS:received a TNS error during navigation Cause: Internal navigation error because of an unexpected TNS error. Action: Look at the log file to find the TNS error. If necessary, turn on tracing and repeat the operation. ORA-12207: TNS:unable to perform navigation Cause: Improperly configured navigation file TNSNAV.ORA. Action: Check the syntax of the TNSNAV.ORA file on the application`s machine, and verify that it lists the correct communities. ORA-12208: TNS:could not find the TNSNAV.ORA file Cause: Either the ORACLE environment is not set up correctly, or the TNSNAV.ORA file is not present. Action: Ensure that the ORACLE environment is set up appropriately on your platform and that a TNSNAV.ORA file is present. ORA-12209: TNS:encountered uninitialized global Cause: Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support. ORA-12210: TNS:error in finding Navigator data Cause: Application calling navigation routine has not properly configured the TNSNAV.ORA file. Action: Check the syntax of the TNSNAV.ORA file. ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA Cause: TNSNAV.ORA does not have a PREFERRED_CMANAGERS defined. Action: Add a PREFERRED_CMANAGERS entry to the TNSNAV.ORA file. ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA Cause: The PREFERRED_CMANAGERS binding in the client"s TNSNAV.ORA file does not have a CMANAGER_NAME specified. Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error. ORA-12213: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA Cause: The PREFERRED_CMANAGERS binding in the client"s TNSNAV.ORA file does not have an ADDRESS specified. Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. ORA-12214: TNS:missing local communities entry in TNSNAV.ORA Cause: There is no LOCAL_COMMUNITIES entry in TNSNAV.ORA. Action: Define the LOCAL_COMMUNITIES for this node in the TNSNAV.ORA file. ORA-12215: TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA Cause: Address binding for PREFERRED_NAVIGATORS entry is improperly entered. entry. Action: Check your PREFERRED_NAVIGATORS entry and fix it in TNSNAV.ORA ORA-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA Cause: Address binding for the PREFERRED_CMANAGERS entry in the client"s TNSNAV.ORA file is improperly entered. Action: Define the ADDRESS as part of the PREFERRED_CMANAGERS binding. ORA-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses specified are wrong, or the intended Connection Managers are unavailable. Action: Check the PREFERRED_CMANAGERS entries in the client"s TNSNAV.ORA file and correct them or talk with your network administrator to determine if the specified Connection Managers are available. Verify that the Interchanges are active by using the INTCTL STATUS command. ORA-12218: TNS:unacceptable network configuration data Cause: Poorly formed network configuration data. For example, a PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the client"s TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA. Action: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary. ORA-12219: TNS:missing community name from address in ADDRESS_LIST Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it that have no COMMUNITY component and others that do have a COMMUNITY component. Action: Check that in the connect descriptors you are using either all the ADDRESSes have a COMMUNITY component or all do not. ORA-12221: TNS:illegal ADDRESS parameters Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport. Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA or in the directory. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation or the Oracle Net Administrator"s Guide. Protocols that resolve names at the transport layer are vulnerable to this error if not properly configured or names are misspelled. ORA-12222: TNS:no support is available for the protocol indicated Cause: The protocol requested in the ADDRESS portion of the connect descriptor identified through the net service name is not available. If the supplied ADDRESS is typographically correct then support for that protocol is not installed. Action: Install support for the protocol or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the net service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA) or in the directory server. ORA-12223: TNS:internal limit restriction exceeded Cause: Too many TNS connections open simultaneously. Action: Wait for connections to close and re-try. ORA-12224: TNS:no listener Cause: The connection request could not be completed because the listener is not running. Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine. ORA-12225: TNS:destination host unreachable Cause: Contact can not be made with remote party. Action: Make sure the network driver is functioning and the network is up. ORA-12226: TNS:operating system resource quota exceeded Cause: The current user has exceeded the allotted resource assigned in the operating system. Action: Acquire more operating system resource, or perform a different function. ORA-12227: TNS:syntax error Cause: The supplied connect descriptor contains illegal syntax. Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. ORA-12228: TNS:protocol adapter not loadable Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded. ORA-12229: TNS:Interchange has no more free connections Cause: One or more Interchanges along the path to the destination desired has no more free connections available to be used for this call. Action: Try again later when the Interchanges are less busy, or contact your network administrator to have him determine which interchange it is, and increase the number of connections available on that interchange. ORA-12230: TNS:Severe Network error occurred in making this connection Cause: This error is reported by an interchange which fails to make contact with the destination due to a physical network error while calling a destination. Action: Try again later when the network service may have been fixed or report the problem to your Network Administrator so that he may fix the problem. ORA-12231: TNS:No connection possible to destination Cause: This error is reported by an interchange which fails to find a possible connection along the path to the destination. Action: Report the problem to your Network Administrator so that he may fix the problem. ORA-12232: TNS:No path available to destination Cause: This error is reported by an interchange which fails to find a possible path to the destination. Action: Report the problem to your Network Administrator so that he may fix the problem. ORA-12233: TNS:Failure to accept a connection Cause: This error is reported by an interchange which fails to accept a connection due to a redirect failure. Action: Report the problem to your Network Administrator so that he may isolate the interchange problem. ORA-12234: TNS:Redirect to destination Cause: This error is reported by an interchange which determines that this interchange is not the right gateway and needs to redirect the connection to another gateway along the path to the destination. Action: None. ORA-12235: TNS:Failure to redirect to destination Cause: This error is reported by an interchange which fails to redirect a connection to another interchange along the path to the destination. Action: Report the problem to your Network Administrator so that he may fix the problem. ORA-12236: TNS:protocol support not loaded Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded. 10 ORA-12315 to ORA-12354 ORA-12315: database link type is invalid for the ALTER DATABASE statement Cause: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database. Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted ORACLE RDBMS Guide to Security Features for more information about creating database links using the ROM: link type. ORA-12316: syntax error in database link"s connect string Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error. Action: Drop the database link and recreate it using valid syntax. See the SQL Language Reference Manual for more information about the connect string portion of the CREATE DATABASE LINK statement. ORA-12317: logon to database (link name string) denied Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username/password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password). Action: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In general, you should always use operating system authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS Guide to Security Features for more information about the advantages of OS authentication). In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database. ORA-12318: database (link name string) is already mounted Cause: You are attempting to mount a secondary database that has already been mounted by your instance. Action: to mount it. To establish access, use the ALTER DATABASE OPEN command to open the database. ORA-12319: database (link name string) is already open Cause: You are attempting to open a secondary database that is already open. Action: The database is open and you need not take additional action to establish access. ORA-12321: database (link name string) is not open and AUTO_MOUNTING=FALSE Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled. Action: Manually mount and open the secondary database using ALTER DATABASE with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE. ORA-12322: unable to mount database (link name string) Cause: This message should be accompanied by additional error messages that indicate the cause of the problem. Action: Follow the steps outlined in the accompanying error messages to resolve the problem. ORA-12323: unable to open database (link name string) Cause: This message should be accompanied by additional error messages that indicate the cause of the problem. Action: Follow the steps outlined in the accompanying error messages to resolve the problem. ORA-12324: cannot use the ROM: link type on a private database link Cause: You can only specify the ROM: link type on a public, not a private, database link. Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command. ORA-12326: database string is closing immediately; no operations are permitted Cause: The database you attempted to access is closing, so your operation has been terminated. Action: Wait until the database has been reopened, or contact the database adminstrator. ORA-12329: database string is closed; no operations are permitted Cause: The database you attempted to access is closed, so your operation has been terminated. Action: Wait until the database is reopened, or contact the database administrator. ORA-12333: database (link name string) is not mounted Cause: You attempted to open a database that has not been mounted. Action: Mount the database with the ALTER DATABASE MOUNT command, then re-attempt to open the database. ORA-12334: database (link name string) is still open Cause: You attempted to dismount a database that is still open. Action: Close the database with the ALTER DATABASE CLOSE command, then re-attempt to dismount the database. ORA-12335: database (link name string) is not open Cause: You attempted to close a database that is not open. Action: The database is closed; you can proceed with dismounting it. ORA-12336: cannot login to database (link name string) Cause: You are tyring to login while another user is mounting or dismounting the same database. Action: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible. ORA-12341: maximum number of open mounts exceeded Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255). Action: Change the value of this parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255. ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter. Action: Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases. ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string) Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege. Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database. ORA-12350: database link being dropped is still mounted Cause: An attempt was made to drop a ROM: database link that was still mounted and/or opened. Action: Close and dismount the database and then re-issue the drop statement. ORA-12351: cannot create view using a remote object which has a remote object reference Cause: You tried to create a view which references a remote object which, in turn, references an object on another database. Since the view that you tried to create references a remote object, that object cannot reference an object on another database. Action: Choose a different object to reference in your view or change the remote object so that it does not reference another database. ORA-12352: object string.string@string is invalid Cause: An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database. Action: Manually recompile the invalid object in the secondary database. ORA-12353: secondary stored object cannot reference remote object Cause: You tried to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done. Action: Choose a different object to reference or change the remote view or procedure so that it does not reference another database. ORA-12354: secondary object being dropped Cause: You tried to access a object (for example, a table or view) on a secondary database that was in the process of being dropped. Action: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle WorldWide Technical Support. 11 ORA-12400 to ORA-12497 ORA-12400: invalid argument to facility error handling Cause: An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility. Action: Specify a valid facility error handling parameter value. ORA-12401: invalid label string: string Cause: The policy could not convert the label string to a valid internal label. Action: Correct the syntax of the label string. ORA-12402: invalid format string: string Cause: The format string is not supported by the policy. Action: Correct the syntax of the format string. ORA-12403: invalid internal label Cause: An internal label could not be converted to a valid label for the policy. Action: Analyze any additional messages on the error stack and consult the policy documentation. ORA-12404: invalid privilege string: string Cause: The policy could not interpret the privilege string. Action: Specify a privilege string that is supported by the policy. ORA-12405: invalid label list Cause: The policy determined that the label list was invalid for its intended use. Action: Check the policy constraints on the specific list of labels. ORA-12406: unauthorized SQL statement for policy string Cause: The policy did not authorize the database session to perform the requested SQL statement. Action: Grant the user or program unit the necessary policy privilege or additional authorizations. ORA-12407: unauthorized operation for policy string Cause: The policy did not authorize the database session to perform the requested operation. Action: Grant the user or program unit the necessary policy privilege or additional authorizations. ORA-12408: unsupported operation: string Cause: The specified policy does not support the requested operation. Action: Consult the policy documentation to determine the supported access mediation operations. ORA-12409: policy startup failure for string policy Cause: The policy encountered an error during startup processing; access to the data protected by the policy is prohibited. Action: Check the alert log for additional information, correct the policy error, and restart the instance. ORA-12410: internal policy error for policy: string Error: string Cause: The policy enforcement encountered an internal error. Action: Consult the policy documentation for details. ORA-12411: invalid label value Cause: The specified label value does not exist. Action: Check the data dictionary views for the policy to identify valid labels. ORA-12412: policy package string is not installed Cause: The policy package does not exist in the database. Action: Check that the policy package name is correct or install the required policy package. ORA-12413: labels do not belong to the same policy Cause: The labels being compared belong to different policies. Action: Only compare labels that belong to the same policy. ORA-12414: internal LBAC error: string Error: string Cause: An internal label policy framework error occurred. Action: Contact Oracle Customer Support. ORA-12415: A column of another datatype exists on the specified table Cause: The datatype of the column present in the table is different from the datatype set for the policy column. Action: Drop the column on the table or change the datatype for policy column. ORA-12416: policy string not found Cause: The specified policy does not exist in the database. Action: Enter the correct policy name or create the policy. ORA-12417: database object "string" not found Cause: The specified object was not in the database. Action: Enter the correct name for the database object. ORA-12418: user string not found Cause: The specified user does not exist in the database. Action: Correct the user name or create the user. ORA-12419: null binary label value Cause: A null value was provided for a binary label operation. Action: Provide a valid binary label for the operation. ORA-12420: required procedures and functions not in policy package "string" Cause: The policy package did not contain all of the procedures and functions necessary to enforce the policy. Action: Consult the label framework documentation for a list of required procedures and functions for a policy package. ORA-12421: different size binary labels Cause: The label sizes for the binary label operation were not equal. Action: Provide binary labels with the same lengths for the operation. ORA-12422: max policies exceeded Cause: You tried to create a new policy, but the maximum number of policies for the instance had already been created. Action: Increase the size of the MAX_LABEL_POLICIES initialization parameter and restart the server. ORA-12423: invalid position specified Cause: The position specified for a binary label operation was invalid. Action: Provide a position that is within the label size limits. ORA-12424: length exceeds binary label size Cause: The length specified for a binary label operation exceeded the the size of the binary label. Action: Provide a bit or byte length that is within the label size limits. ORA-12425: cannot apply policies or set authorizations for system schemas Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS schema or to set user labels/privileges for the SYS, SYSTEM, or LBACSYS user. Action: Apply policies and set authorizations only for non-system users. ORA-12426: invalid audit option Cause: The option specified was not a valid audit option for the specified policy. Action: Enter a correct audit option. ORA-12427: invalid input value for string parameter Cause: An input parameter was specified incorrectly. Action: Correct the parameter value. ORA-12429: label list range exceeded Cause: The specified index value was not between 1 and 6. Action: Correct the index value for the label list operation. ORA-12430: invalid privilege number Cause: The specified privilege number was not between 1 and 32. Action: Correct the privilege number. ORA-12431: invalid audit action Cause: The specified audit action was not a valid audit action. Action: Correct the audit action number. ORA-12432: LBAC error: string Cause: LBAC enforcement resulted in an error. Action: Correct the problem identified in the error message. ORA-12433: create trigger failed, policy not applied Cause: The policy could not be applied due to errors during the creation of a DML trigger. Action: Correct the SQL syntax of the label function specification. ORA-12434: invalid audit type: string Cause: The audit type must be BY ACCESS or BY SESSION. Action: Correct the audit type value. ORA-12435: invalid audit success: string Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL. Action: Correct the audit success value. ORA-12436: no policy options specified Cause: A NULL option string was specified, but no default schema or policy option string was found. Action: Enter a valid option string, or alter the schema or policy to have a valid default option string. ORA-12437: invalid policy option: string Cause: A value that was not a valid policy option was entered. Action: Correct the policy option value. ORA-12438: repeated policy option: string Cause: A policy option was entered more than once in the option string. Action: Remove the duplicate policy option value. ORA-12439: invalid combination of policy options Cause: A set of contradictory policy options was entered. Action: Provide a set of compatible policy options. ORA-12440: insufficient authorization for the SYSDBA package Cause: The use of the SYSDBA package requires the LBAC_DBA role. Action: Grant the LBAC_DBA role to the database user. ORA-12441: policy string already exists Cause: You tried to create a policy with the same name as an existing one. Action: Use a different name or drop the existing policy. ORA-12442: policy column "string" already used by an existing policy Cause: You tried to create a policy with the same policy column name as an existing policy. Action: Use a different name for the policy column or drop the existing policy. ORA-12443: policy not applied to some tables in schema Cause: You applied a policy to a schema, and some of the tables in the schema already had the policy applied. Action: No action necessary; the policy was applied to the remaining tables. ORA-12444: policy already applied to table Cause: You tried to apply a policy to a table that was already protected by the policy. Action: To change the policy options, predicate, or label function, remove the policy from the table and re-apply it. ORA-12445: cannot change HIDDEN property of column Cause: You tried to specify a different HIDE option for a table with an existing policy column. Action: Drop the column from the table and reapply the policy with the new HIDE option. ORA-12446: Insufficient authorization for administration of policy string Cause: You tried to perform an administrative function for a policy, but you have not been granted the _DBA role. Action: Grant the user the _DBA role for the specified policy. ORA-12447: policy role already exists for policy string Cause: The role named _DBA already exists. Action: Correct the policy name or delete the existing policy. ORA-12448: policy string not applied to schema string Cause: You tried to alter a schema policy that was not applied. Action: Correct the policy name or schema name. ORA-12449: Labels specified for user must be of type USER Cause: You tried to set labels for a user, but the labels in the list were not all designated as USER labels. Action: Alter the labels to be USER labels. ORA-12450: LOB datatype disabled in LBAC initialization file Cause: You tried to specify a LOB datatype for a column or attribute, but the use of the LOB datatype has been disabled. Action: Change the LBAC initialization file to allow the creation of LOB columns and attributes. ORA-12451: label not designated as USER or DATA Cause: A label is either a DATA label, a USER label, or both DATA and USER. Action: Enter TRUE for at least DATA or USER. ORA-12452: label tag string already exists Cause: The label tag value you entered is already in use for another label. Action: Enter a different value for the label tag. ORA-12453: label string already exists Cause: The label value you entered already exists. Action: No action necessary; alter the label to change its tag or type. ORA-12454: label string does not exist for policy string Cause: The label tag or value you entered did not identify a label for the policy. Action: Enter a label value or tag that is in use by the policy. ORA-12455: internal error in Label Security MMON cleanup task Cause: An internal error occurred in the Label Security MMON cleanup task. Action: Contact Oracle Customer Support. ORA-12456: label security startup in progress Cause: You attempted to connect to the database before the Oracle Label Security component was fully initialized. Action: Wait until the database is fully open before attempting to connect. ORA-12457: security label exceeded maximum allowable length Cause: An operation attempted to materialize a security label greater than 4000 bytes in length. Action: Consult the Oracle Label Security documentation for information on how the length of a security label is calculated. Re-submit the operation once the problem has been corrected. ORA-12461: undefined level string for policy string Cause: The specified level is not defined for the policy. Action: Correct the level identifier value. ORA-12462: undefined compartment string for policy string Cause: The specified compartment is not defined for the policy. Action: Correct the compartment identifier value. ORA-12463: undefined group string for policy string Cause: The specified group is not defined for the policy. Action: Correct the group identifier value. ORA-12464: invalid characters in label component string Cause: Label components can contain only alphanumeric characters, blanks, and underscores. Action: Correct syntax of the label component. ORA-12465: Not authorized for read or write on specified groups or compartments Cause: You included groups or compartments that are not in the user"s list of groups and compartments authorized for read or write access. Action: Include read access when authorizing groups or compartments for write access. ORA-12466: default level is greater than the user"s maximum Cause: The default level cannot be greater than the user"s maximum. Action: Enter an authorized level. ORA-12467: minimum label can contain a level only Cause: You included compartments or groups in the minimum label. Action: Enter only an authorized minimum level as the label. ORA-12468: max write level does not equal max read level Cause: The level in the max write label must equal the level in the max read label. Action: Enter max read and max write labels with the same level component. ORA-12469: no user levels found for user string and policy string Cause: No levels have been specified for the user. Action: Enter the maximum and minimum labels for the user. ORA-12470: NULL or invalid user label: string Cause: The label entered is NULL or not within the user"s authorizations. Action: Enter the authorized labels for the user. ORA-12471: Specified compartment or group is not authorized for user Cause: The specified compartment or group is not in user"s authorizations or the user does not have read on compartment or group specified for write. Action: Enter an authorized compartment or group. ORA-12472: policy string is being used Cause: The policy which was being dropped due to event propagation from OID was applied to some table or schema. Action: Drop a policy in OID only if it is not used in any of the databases using the policy. ORA-12473: The procedure is disabled when Label Security is used with OID. Cause: Using Label Security with OID disabled this procedure. Action: Do not use OID with Label Security if this procedure is required to function. ORA-12476: least upper bound resulted in an invalid OS label Cause: You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system. Action: Consult your OS label management documentation for information on invalid label generation. ORA-12477: greatest lower bound resulted in an invalid OS label Cause: You tried to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system. Action: Consult your OS label management documentation for information on invalid label generation. ORA-12479: file label string must equal DBHIGH string Cause: A database file had an OS label that did not match DBHIGH. Either DBHIGH was altered or the OS file was relabeled. Action: Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file. ORA-12480: specified clearance labels not within the effective clearance Cause: You specified a clearance range that was not within your authorized clearance; you can only specify clearance ranges that are within your clearance. Action: Specify clearance labels that are within your own clearance range. ORA-12481: effective label not within program unit clearance range Cause: The effective label when the program unit was invoked was not within the range authorized for the program unit. Action: Modify the program unit clearance range or invoke the program unit from a session with an authorized effective clearance. ORA-12482: internal MLS error: string Error: string Cause: An internal MLS policy error occurred. Action: Contact Oracle Customer Support. ORA-12483: label not in OS system accreditation range Cause: The specified label is above the OS maximum label or below the OS minimum label. Action: Use a label that is within the accreditation range for the host OS. ORA-12484: invalid OS label Cause: The specified label does not exist in the OS host"s label definition file. Action: Use the OS label management tools to define the label. ORA-12485: new effective label not within effective clearance Cause: You attempted to enter a value for an effective label that did not dominate the effective min label or was not dominated by the effective max label. Action: Enter a value between the min and the max labels. ORA-12486: effective max labels and min labels cannot be changed Cause: You attempted to enter a value for an effective min label or effective max label, but these labels cannot be changed. Action: Enter NULL values for the effective minimum and maximum labels. ORA-12487: clearance labels not between DBHIGH and DBLOW Cause: You attempted to enter a value for a clearance label that was not dominated by DBHIGH or did not dominate DBLOW. Action: Enter clearance label values between DBHIGH and DBLOW. ORA-12488: maximum label does not dominate minimum label Cause: You attempted to enter a value for a clearance label that did not preserve the dominance relationship between the minimum and maximum labels. Action: Enter label values that preserves the dominance relationship between the minimum and maximum. ORA-12489: default label not within clearance range Cause: You attempted to enter a value for a default label that did not dominate the minimum clearance or was not dominated by the maximum clearance. Action: Enter a default label value within the clearance range. ORA-12490: DBHIGH cannot be lowered Cause: You attempted to enter a value for DBHIGH that did not dominate the existing value of DBHIGH. Action: Enter a value for DBHIGH that dominates the old value. ORA-12491: DBHIGH value does not dominate DBLOW Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW. Action: Enter a value for DBHIGH that dominates DBLOW. ORA-12492: DBLOW cannot be changed Cause: You attempted to change the value of DBLOW after it had been set to any initial value. DBLOW can only be set once after initial database creation. Action: To change DBLOW, you have to create a new database, set DBLOW to the new value, and import your data into the new database. ORA-12493: invalid MLS binary label Cause: The MLS binary label contained an invalid value, was not the correct size, or contained a level, category, or release category that was not enabled. Action: Check the DBA_MLS_LABELS view for the valid MLS labels. ORA-12494: cannot insert or delete a level, category, or release category Cause: You attempted to insert or delete a level, category, or release category definition. Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used. ORA-12495: cannot disable an enabled level, category, or release category Cause: You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may be exist in some database label, so cannot be disabled. Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used. ORA-12496: cannot change existing level, category, or release numbers Cause: You attempted to change the number assigned to level, category or releasability category. Action: Change the character string representations, not the numbers. ORA-12497: maximum combined categories exceeds string Cause: The maximum number of descriptive categories plus release categories supported by the MLS policy was exceeded. Action: Enter numbers that do not add up to more than the maximum. 12 ORA-12500 to ORA-12699 ORA-12500: TNS:listener failed to start a dedicated server process Cause: The process of starting up a dedicated server process failed. The executable could not be found or the environment may be set up incorrectly. Action: Turn on tracing at the ADMIN level and reexecute the operation. Verify that the ORACLE Server executable is present and has execute permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked. If error persists, contact Oracle Customer Support. ORA-12502: TNS:listener received no CONNECT_DATA from client Cause: No CONNECT_DATA was passed to the listener. Action: Check that the service name resolved from TNSNAMES.ORA has the CONNECT_DATA component of the connect descriptor. ORA-12504: TNS:listener was not given the SID in CONNECT_DATA Cause: The SID was missing from the CONNECT_DATA. Action: Check that the connect descriptor corresponding to the service name in TNSNAMES.ORA has an SID component in the CONNECT_DATA. ORA-12505: TNS:listener does not currently know of SID given in connect descriptor Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: - Wait a moment and try to connect a second time. - Check which instances are currently known by the listener by executing: lsnrctl services - Check that the SID parameter in the connect descriptor specifies an instance known by the listener. - Check for an event in the listener.log file. ORA-12508: TNS:listener could not resolve the COMMAND given Cause: d by incompatible Oracle Net or Net8 versions. Do not include in error manual. Action: This is not seen in normal use of Oracle Net. ORA-12509: TNS:listener failed to redirect client to service handler Cause: The dispatcher terminated unexpectedly Action: Attempt to connect again and if the same error occurs, contact the DBA to check the state of the dispatchers for this SID. If the problem persists, turn on tracing in the listener to determine the TNS error caused by the redirect. ORA-12510: TNS:database temporarily lacks resources to handle the request Cause: The dispatchers appear to be busy handling other requests. Action: Attempt the connection again. If error persists, ask the DBA to increase the number of dispatchers and/or dispatchers" limit on number of connections/sessions that they can accept. ORA-12511: TNS:service handler found but it is not accepting connections Cause: The dispatchers notified the listener that they temporarily do not accept new connections. Action: Attempt the connection again. If error persists, contact the DBA to check the state of the dispatchers and/or ask him to increase the number of dispatchers. ORA-12513: TNS:service handler found but it has registered for a different protocol Cause: The dispatchers registered for this service are connected to the listener by way of a different network protocol than that of the client. Action: Contact the DBA to register a dispatcher on your protocol. ORA-12514: TNS:listener does not currently know of service requested in connect descriptor Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: - Wait a moment and try to connect a second time. - Check which services are currently known by the listener by executing: lsnrctl services - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. - Check for an event in the listener.log file. ORA-12515: TNS:listener could not find a handler for this presentation Cause: None of the listener"s known service handlers are registered as supporting the presentation protocol required by the connecting client. Action: Check that the destination service is configured to accept the presentation protocol. ORA-12516: TNS:listener could not find available handler with matching protocol stack Cause: None of the known and available service handlers for the given SERVICE_NAME support the client"s protocol stack: transport, session, and presentation protocols. Action: Check to make sure that the service handlers (e.g. dispatchers) for the given SERVICE_NAME are registered with the listener, are accepting connections, and that they are properly configured to support the desired protocols. ORA-12518: TNS:listener could not hand off client connection Cause: The process of handing off a client connection to another process failed. Action: Turn on listener tracing and re-execute the operation. Verify that the listener and database instance are properly configured for direct handoff. If problem persists, call Oracle Support. ORA-12519: TNS:no appropriate service handler found Cause: The listener could not find any available service handlers that are appropriate for the client connection. Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the listener, and are accepting connections. ORA-12520: TNS:listener could not find available handler for requested type of server Cause: None of the known and available service handlers for requested type of server (dedicated or shared) are appropriate for the client connection. Action: Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that the appropriate handlers are accepting connections. ORA-12521: TNS:listener does not currently know of instance requested in connect descriptor Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified in addition to the service name an instance name for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. Action: - Wait a moment and try to connect a second time. - Check which instances are currently known by the listener by executing: lsnrctl services - Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener. - Check for an event in the listener.log file. ORA-12522: TNS:listener could not find available instance with given INSTANCE_ROLE Cause: There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified). Action: Check to make sure that the INSTANCE_ROLE specified is correct. Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that they are ready to accept connections. ORA-12523: TNS:listener could not find instance appropriate for the client connection Cause: The listener could not find any available (database) instances, that are appropriate for the client connection. Action: Run "lsnrctl services" to ensure that the instance(s) are registered with the listener, and have status READY. ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor Cause: The HANDLER_NAME in the CONNECT_DATA was not found in the listener"s tables for the specified SERVICE_NAME and INSTANCE_NAME. Action: Check to make sure that the HANDLER_NAME specified is correct. ORA-12525: TNS:listener has not received client"s request in time allowed Cause: The listener disconnected the client because the client failed to provide the necessary connect information within the allowed time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the listener. Action: If the error occurred because of a slow network or system, reconfigure INBOUND_CONNECT_TIMEOUT to a larger value. If a malicious client is suspected, use the address in listener.log to identify the source and restrict access. Turn on tracing for more information. ORA-12526: TNS:listener: all appropriate instances are in restricted mode Cause: Database instances supporting the service requested by the client were in restricted mode. The Listener does not allow connections to instances in restricted mode. This condition may be temporary, such as during periods when database administration is performed. Action: Attempt the connection again. If error persists, then contact the database administrator to change the mode of the instance, if appropriate. ORA-12527: TNS:listener: all instances are in restricted mode or blocking new connections Cause: All appropriate database instances supporting the service requested by the client reported that they either were in restricted mode or were blocking the new connections. The Listener does not allow connections to such instances. This condition may be temporary, such as at instance startup. Action: Attempt the connection again. If error persists, then contact the database administrator to check the status of the instances. ORA-12528: TNS:listener: all appropriate instances are blocking new connections Cause: All instances supporting the service requested by the client reported that they were blocking the new connections. This condition may be temporary, such as at instance startup. Action: Attempt the connection again. If error persists, then contact the administrator to check the status of the instances. ORA-12529: TNS:connect request rejected based on current filtering rules Cause: Connection Manager and its listener were configured with filtering rules specifying that the connect request be rejected. Action: If this connect request should be allowed, then contact the administrator to modify the filtering rules. ORA-12531: TNS:cannot allocate memory Cause: Sufficient memory could not be allocated to perform the desired activity. Action: Either free some resource for TNS, or add more memory to the machine. For further details, turn on tracing and reexecute the operation. ORA-12532: TNS:invalid argument Cause: An internal function received an invalid parameter. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12533: TNS:illegal ADDRESS parameters Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport. Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform. Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled. ORA-12534: TNS:operation not supported Cause: An internal function received a request to perform an operation that is not supported (on this machine). Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12535: TNS:operation timed out Cause: The requested operation could not be completed within the time out period. Action: Look at the documentation on the secondary errors for possible remedy. See SQLNET.LOG to find secondary error if not provided explicitly. Turn on tracing to gather more information. ORA-12536: TNS:operation would block Cause: An internal operation did not commence because to do so would block the current process and the user has requested that operations be non-blocking. Action: None needed; this is an information message. ORA-12537: TNS:connection closed Cause: "End of file" condition has been reached; partner has disconnected. Action: None needed; this is an information message. ORA-12538: TNS:no such protocol adapter Cause: The protocol adapter requested (by way of the "(PROTOCOL=..)" keyword-value pair in a TNS address) is unknown. If the supplied address is typographically correct then the protocol adapter is not installed. Action: Install the protocol adapter or correct typographically error, as appropriate. Note: if the supplied address was derived from resolving the service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA or SQLNET.ORA). ORA-12539: TNS:buffer over- or under-flow Cause: Buffer too small for incoming data or too large for outgoing data. Action: This restriction (which is associated with CONNECT DATA) is not normally visible to the user. For further details, turn on tracing and reexecute the operation; contact Oracle Customer Support. ORA-12540: TNS:internal limit restriction exceeded Cause: Too many TNS connections open simultaneously. Action: Wait for connections to close and re-try. ORA-12541: TNS:no listener Cause: The connection request could not be completed because the listener is not running. Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine. ORA-12542: TNS:address already in use Cause: Specified listener address is already being used. Action: Start your listener with a unique address. ORA-12543: TNS:destination host unreachable Cause: Contact can not be made with remote party. Action: Make sure the network driver is functioning and the network is up. ORA-12544: TNS:contexts have different wait/test functions Cause: Two protocol adapters have conflicting wait/test functions. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12545: Connect failed because target host or object does not exist Cause: The address specified is not valid, or the program being connected to does not exist. Action: Ensure the ADDRESS parameters have been entered correctly; the most likely incorrect parameter is the node name. Ensure that the executable for the server exists (perhaps "oracle" is missing.) If the protocol is TCP/IP, edit the TNSNAMES.ORA file to change the host name to a numeric IP address and try again. ORA-12546: TNS:permission denied Cause: User has insufficient privileges to perform the requested operation. Action: Acquire necessary privileges and try again. ORA-12547: TNS:lost contact Cause: Partner has unexpectedly gone away, usually during process startup. Action: Investigate partner application for abnormal termination. On an Interchange, this can happen if the machine is overloaded. ORA-12548: TNS:incomplete read or write Cause: A data send or receive failed. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12549: TNS:operating system resource quota exceeded Cause: The current user has exceeded the allotted resource assigned in the operating system. Action: Acquire more operating system resource, or perform a different function. ORA-12550: TNS:syntax error Cause: The supplied connect descriptor contains illegal syntax. Action: Check the syntax of the connect descriptor in TNSNAMES.ORA. ORA-12551: TNS:missing keyword Cause: The supplied connect descriptor is missing one or more TNS keywords. Action: Check the syntax, and ensure all required keywords are present. ORA-12552: TNS:operation was interrupted Cause: An internal operation was interrupted and could not complete. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12554: TNS:current operation is still in progress Cause: An internal operation is still in progress. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12555: TNS:permission denied Cause: User has insufficient privileges to perform the requested operation. Action: Acquire necessary privileges and try again. ORA-12556: TNS:no caller Cause: TNS detected an incoming connect request but there was no caller. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12557: TNS:protocol adapter not loadable Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded. ORA-12558: TNS:protocol adapter not loaded Cause: On some platforms (such as OS/2) protocol adapters are loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned. Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded. ORA-12560: TNS:protocol adapter error Cause: A generic protocol adapter error occurred. Action: Check addresses used for proper protocol specification. Before reporting this error, look at the error stack and check for lower level transport errors. For further details, turn on tracing and reexecute the operation. Turn off tracing when the operation is complete. ORA-12561: TNS:unknown error Cause: A generic protocol error occurred. Action: For further details, turn on tracing and reexecute the operation. ORA-12562: TNS:bad global handle Cause: Internal error - bad "gbh" argument passed to TNS from caller. System may have been linked with old libraries. Action: Not normally visible to the user, contact Oracle Customer Support. ORA-12564: TNS:connection refused Cause: The connect request was denied by the remote user (or TNS software). Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. ORA-12566: TNS:protocol error Cause: An unexpected TNS protocol error has occurred. Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12569: TNS:packet checksum failure Cause: The data received is not the same as the data sent. Action: Attempt the transaction again. If the error is persistent, turn on tracing and reexecute the operation. ORA-12570: TNS:packet reader failure Cause: An error occurred during a data receive. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12571: TNS:packet writer failure Cause: An error occurred during a data send. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12574: TNS:redirection denied Cause: The connect request failed because it would have required redirection and the caller has requested no redirections. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12582: TNS:invalid operation Cause: An internal function received an invalid request. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12583: TNS:no reader Cause: A send operation has been requested but partner has already disconnected. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12585: TNS:data truncation Cause: A receive operation has completed with insufficient data to satisfy the user"s request. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12589: TNS:connection not bequeathable Cause: An attempt to hand-off a connection from one process to another has failed because the protocol provider does not support it. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12590: TNS:no I/O buffer Cause: An attempt to perform an I/O operation failed because no buffer was available. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12591: TNS:event signal failure Cause: The TNS software is unable to signal an event occurrence. Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12592: TNS:bad packet Cause: An ill-formed packet has been detected by the TNS software. Action: For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12593: TNS:no registered connection Cause: An attempt to solicit network event activity has failed because no connections are registered for event notification. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12595: TNS:no confirmation Cause: TNS is unable to get requested confirmation acknowledgment from remote partner. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12596: TNS:internal inconsistency Cause: TNS has detected an internal inconsistency. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12597: TNS:connect descriptor already in use Cause: Internal error - illegal use of connect descriptor. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12598: TNS:banner registration failed Cause: The registration of a product banner with the Oracle server failed. Action: This is an error which is not normally visible externally. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. ORA-12599: TNS:cryptographic checksum mismatch Cause: The data received is not the same as the data sent. Action: Attempt the transaction again. If error persists, check (and correct) the integrity of your physical connection. ORA-12600: TNS: string open failed Cause: The creation of a string in ORACLE NLS format failed. Action: This is an internal error, enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. ORA-12601: TNS:information flags check failed Cause: The TNS information flags set by the process prior to connection negotiation were not present after the negotiation was finished. Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. ORA-12602: TNS: Connection Pooling limit reached Cause: The operation failed because maximum active current connections has been reached. It may not be a real error when the Connection Pooling feature is enabled. It is possible that the application later reissues the operation and successfully grabs the connection pool slot and proceeds. Action: This is an internal error. Enable tracing and attempt to repeat the error. If it occurs again, contact Oracle Customer Support. ORA-12606: TNS: Application timeout occurred Cause: A network session did not reach an application-defined stage within the allowed time interval. Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description. ORA-12607: TNS: Connect timeout occurred Cause: A network session did not reach a predefined connect stage within the allowed time interval. Action: This is an error which does not normally appear at the high level. The action to take is application specific, and is detailed in the higher level error description. ORA-12608: TNS: Send timeout occurred Cause: The send or write operation did not complete within the allowed time interval. Action: Check if the peer host is available. Increase the send timeout value if necessary. ORA-12609: TNS: Receive timeout occurred Cause: The receive or read operation did not complete within the allowed time interval. Action: Check if the peer host is available. Increase the receive timeout value if necessary. ORA-12611: TNS:operation is not portable Cause: Attempted operation is not portable. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12612: TNS:connection is busy Cause: Attempted operation failed because it conflicts with an ongoing Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12615: TNS:preempt error Cause: A request to service an event failed because no event notification has yet been posted. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12616: TNS:no event signals Cause: The operation failed because the type of data specified is unknown. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12618: TNS:versions are incompatible Cause: The two machines are running incompatible versions of TNS. Action: Check the version numbers, and upgrade the machine with the smaller one. ORA-12619: TNS:unable to grant requested service Cause: The connect request failed because requested service could not be provided by the local TNS software. Action: If appropriate, reexecute with reduced service requirements. ORA-12620: TNS:requested characteristic not available Cause: The connect request failed because a requested transport characteristic could not be supported by the remote TNS software. Action: If appropriate, reexecute with reduced requirements. ORA-12622: TNS:event notifications are not homogeneous Cause: An attempt to register a connection for event notification failed because the event notification type conflicts with existing registrations. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12623: TNS:operation is illegal in this state Cause: Connection is half-duplex and a full-duplex operation was attempted. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support. ORA-12624: TNS:connection is already registered Cause: An attempt to register a connection for event notification failed because the connection is already registered. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12625: TNS:missing argument Cause: An operation failed because an argument was missing" Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12626: TNS:bad event type Cause: An attempt to register a connection for event notification failed because the event type is unknown. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12628: TNS:no event callbacks Cause: An attempt to register a connection for event notification failed because asynchronous callbacks are not available. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12629: TNS:no event test Cause: An attempt to register a connection for event notification failed because the ability to test for events is not available. Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation and contact Oracle Customer Support. ORA-12630: Native service operation not supported Cause: An operation requested by a user is not supported by the native services component. Action: This may be an internal error if the operation should have been supported. ORA-12631: Username retrieval failed Cause: The authentication service failed to retrieve the name of a user. Action: Enable tracing to determine which routine is failing. ORA-12632: Role fetch failed Cause: The authentication service failed to retrieve one of the user"s roles. Action: Enable tracing to determine which routine is failing. ORA-12633: No shared authentication services Cause: The list of authentication services specified by the user does not match those supported by the process. Action: Either specify another list or relink the executable with the desired services. ORA-12634: Memory allocation failed Cause: Process was unable to allocate memory. Action: Terminate other processes in order to reclaim needed memory. ORA-12635: No authentication adapters available Cause: The executable was not linked with any authentication service adapters but the sqlnet.ora parameter that determines whether or not authentication is required was set to true. Action: Either disable the parameter or relink the executable with service adapters. ORA-12636: Packet send failed Cause: A process was unable to send a packet to another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. Action: If the cause is not obvious, contact Oracle Customer Support. ORA-12637: Packet receive failed Cause: A process was unable to receive a packet from another process. Possible causes are: 1. The other process was terminated. 2. The machine on which the other process is running went down. 3. Some other communications error occurred. Action: If the cause is not obvious, contact Oracle Customer Support. ORA-12638: Credential retrieval failed Cause: The authentication service failed to retrieve the credentials of a user. Action: Enable tracing to determine the exact error. ORA-12639: Authentication service negotiation failed Cause: No match was found between the types of authentication services that the client supports and those that the server is using. Action: Possible solutions: 1. Change the entry in sqlnet.ora that determines which services are to be used. 2. Relink the client with at least one of the authentication service adapters that the server supports. 3. Relink the server with at least one of the authentication service adapters that the client supports. 4. Disable authentication on both the client and server. ORA-12640: Authentication adapter initialization failed Cause: The function specified in the authentication table entry for the service failed. Action: Enable tracing to determine the exact error. ORA-12641: Authentication service failed to initialize Cause: The authentication service failed during initialization. Action: Enable tracing to determine the exact error. ORA-12642: No session key Cause: A process has no session key associated with it because the authentication service being used does not use one. Action: If a session key is required, use another authentication service. ORA-12643: Client received internal error from server Cause: The client process received an error from the server that indicated that an internal Oracle Net native services error had occurred. Action: Enable tracing on both processes and attempt to recreate the problem. If successful in recreating the problem, contact Oracle Customer Support. ORA-12645: Parameter does not exist. Cause: A sqlnet.ora parameter from which a value was needed does not exist. Action: Set the parameter in the parameter file. ORA-12646: Invalid value specified for boolean parameter Cause: The value specified for a parameter was set to a value other than true/false or on/off. Action: Correct the value of the parameter. ORA-12647: Authentication required Cause: The parameter that controls whether authentication is required was set to true, but the executable does not have an authentication service linked in. Action: Either re-link the executable with an authentication service adapter or disable the parameter. ORA-12648: Encryption or data integrity algorithm list empty Cause: An Oracle Advanced Security list-of-algorithms parameter was empty, e.g. "()". Action: Change the list to contain the name of at least one installed algorithm, or remove the list entirely if every installed algorithm is acceptable. ORA-12649: Unknown encryption or data integrity algorithm Cause: An Oracle Advanced Security list-of-algorithms parameter included an algorithm name that was not recognized. Action: Either remove that algorithm name, correct it if it was misspelled, or install the driver for the missing algorithm. ORA-12650: No common encryption or data integrity algorithm Cause: The client and server have no algorithm in common for either encryption or data integrity or both. Action: Choose sets of algorithms that overlap. In other words, add one of the client"s algorithm choices to the server"s list or vice versa. ORA-12651: Encryption or data integrity algorithm unacceptable Cause: The algorithm the server chose to use for encryption or data integrity was not one of the choices acceptable to the client. This is either the result of an internal error, of a network data transmission error, or of deliberate tampering with the transmitted data. Action: For further details, turn on tracing, re-execute the operation, and contact Oracle Customer Support. ORA-12652: String truncated Cause: Not enough memory was allocated for a string so it had to be truncated Action: If it is OK that the string is truncated, then it is not an error. Otherwise, call the routine that reported the error again with a larger string buffer. ORA-12653: Authentication control function failed Cause: The control function utilized by the authentication service driver failed. Action: Enable tracing to determine the exact error. ORA-12654: Authentication conversion failed Cause: The authentication service was unable to convert the credentials of a user from the format specific to the format into the ORACLE format. Action: Enable tracing to determine the exact error. ORA-12655: Password check failed Cause: The authentication service being used was unable to verify the provided password. Action: Enable tracing to determine the exact error. ORA-12656: Cryptographic checksum mismatch Cause: The cryptographic checksum received with a packet of incoming data didn"t match the checksum computed by the receiving end. This indicates that the packet was tampered with or otherwise corrupted in transit. Action: Look for sources of data corruption, perhaps including deliberate tampering. ORA-12657: No algorithms installed Cause: The near side of the connection required the use of a service (either encryption or checksumming) when no algorithms for that service were installed. Action: Remove the "ON" requirement for that service. ORA-12658: ANO service required but TNS version is incompatible Cause: A client process that is running an earlier version of TNS attempted to connect but the connection failed because the server process required that an ANO service (authentication, encryption, etc.) be used. Action: Relink the calling executable and retry the connection or eliminate the requirement that the service be used on the server side. ORA-12659: Error received from other process Cause: An error was received by one or more services from the process on the other side of the connection. Action: Enable tracing to determine the exact error(s). The error(s) is (are) not returned directly because an error generated by a server may not make sense on the client side and vice-versa. ORA-12660: Encryption or crypto-checksumming parameters incompatible Cause: One side of the connection specified "REQUIRED" for encryption or crypto-checksumming, while the other side specified "REJECTED". Action: Change the "REQUIRED" side to "REQUESTED" if the you want encryption or crypto-checksumming to be optional, or change the "REJECTED" side to "ACCEPTED" if you do not want the service to be optional. ORA-12661: Protocol authentication to be used Cause: The Oracle Advanced Security authentication service has determined that the Oracle Net transport protocol in use is to be utilized to authenticate a user"s identity. Action: This error is used solely to communicate information between the authentication service and the Oracle Net session layer and should not normally be visible. If the error is seen, contact Oracle Worldwide Support. ORA-12662: proxy ticket retrieval failed Cause: The authentication adapter used by Oracle Net failed to retrieve the credentials needed to authenticate a database link. Action: Enable tracing to determine the exact error. ORA-12663: Services required by client not available on the server Cause: Service(s) that was (were) required by the client process were not available on the server process. Action: Configure the server with the services required by the client (best solution) or delete the requirement from the configuration file of the client (least secure). ORA-12664: Services required by server not available on the client Cause: Service(s) that was (were) required by the server process were not available on the client process. Action: Configure the client with the services required by the server (best solution) or delete the requirement from the configuration file of the server (least secure). ORA-12665: NLS string open failed Cause: A native service was unable to make a string available for use by the National Language Support component. Action: Make sure the National Language Support component has been properly. If it has, enable tracing and report the problem to Customer Support. ORA-12666: Dedicated server: outbound transport protocol different from inbound Cause: The protocol specified for an externally-identified outbound connection from a dedicated server (database link) was not the same as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the dedicated server. Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection. ORA-12667: Shared server: outbound transport protocol different from inbound Cause: The protocol specified for an externally-identified outbound connection from a shared server (database link) was not the same as as that used for the inbound connection. It is not possible for Oracle Net to authenticate a proxy connection that uses a protocol that is different from that which was used for the connection to the shared server. Action: Specify the same protocol in the Oracle Net connect descriptor for the outbound connection as that used for the inbound connection ORA-12668: Dedicated server: outbound protocol does not support proxies Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a dedicated server does not support proxy connections. Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server. ORA-12669: Shared server: outbound protocol does not support proxies Cause: The protocol specified to perform an externally-identified proxy connection (database link) from a shared server does not support proxy connections. Action: Specify a protocol in the Oracle Net connect descriptor used for the connection that does support externally-authenticated proxy connections. NOTE: Because of a limitation in Oracle Net, the protocol used for the proxy connection must the same as that used for the connection from the client to the server. ORA-12670: Incorrect role password Cause: A password supplied for a role could not be validated by the authentication service. Action: Supply the correct password. ORA-12671: Shared server: adapter failed to save context Cause: The adapter for the authentication service failed when it tried to save the data needed for proxy connections (database links) through the shared server. Action: Enable tracing to determine the exact error. Contact Oracle Customer Support if the reason is not obvious. ORA-12672: Database logon failure Cause: The authentication service adapter in use encountered an error it attempted to validate the logon attempt of a user. Action: Enable tracing to determine the exact error encountered by the adapter. ORA-12673: Dedicated server: context not saved Cause: A connection was marked as being a proxy connection (database link) from a dedicated server but no inbound context was present. Action: This error should not normally be visible to the user. Contact Oracle Customer Support. ORA-12674: Shared server: proxy context not saved Cause: A connection was marked as being a proxy connection (database link) from a shared server but no inbound context was present. Action: This error should not normally be visible to the user. Contact Oracle Customer Support. ORA-12675: External user name not available yet Cause: The authentication service in use was not able to return the external name of a user of the ORACLE server because it is not available to the service yet. Action: This is just an informational message and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support. ORA-12676: Server received internal error from client Cause: The server process received an error from the client which indicated that an internal Oracle Net native services error had occurred. Action: Enable tracing on both processes and attempt to recreate the problem. If the problem recurs, contact Oracle Customer Support. ORA-12677: Authentication service not supported by database link Cause: The authentication service used by the proxy process (database link) was unable to find the adapter being used by the client in its list of authentication mechanisms. Action: Specify an authentication adapter that is shared by the client and the server being used for the database link. ORA-12678: Authentication disabled but required Cause: The configuration parameters that control whether Oracle Advanced Security authentication is disabled or required were both set to TRUE. Action: Set one or both of the parameters to FALSE. ORA-12679: Native services disabled by other process but required Cause: The remote process has disabled native services but the local process requires them. Action: Enable native services on the remote process or disable them locally. ORA-12680: Native services disabled but required Cause: The process has disabled native services but at least one service is required. Action: Enable native services or change the configuration file so that none of the available services are required. ORA-12681: Login failed: the SecurID card does not have a pincode yet Cause: The SecurID card that is used to logon to Oracle, does not have a pincode assigned to it. Action: Use one of the programs supplied by Security Dynamics to assign a pincode to the card. ORA-12682: Login failed: the SecurID card is in next PRN mode Cause: The SecurID card and the SecurID server are out of sync and the server requires the next cardcode to resynchronize the card. Action: Use one of the programs supplied by Security Dynamics to resynchronize the SecurID card. ORA-12683: encryption/crypto-checksumming: no Diffie-Hellman seed Cause: The "sqlnet.crypto_seed" parameter is missing from the SQLNET.ORA parameters file for Oracle Advanced Security. Action: Add this line to SQLNET.ORA: sqlnet.crypto_seed = "randomly-chosen text" ORA-12684: encryption/crypto-checksumming: Diffie-Hellman seed too small Cause: The "sqlnet.crypto_seed" parameter in the SQLNET.ORA parameter file for Oracle Advanced Security is too small. Action: Add more randomly-chosen text to it, perhaps using Network Manager. ORA-12685: Native service required remotely but disabled locally Cause: A native service is required by the remote process but native services have been disabled locally. Action: Enable native services locally or change the configuration parameters on the remote host so that no native services are required. ORA-12686: Invalid command specified for a service Cause: An operation which does not exist was specified for a native service. Action: This is a programming error and should not normally be visible to the user. If the error does appear, contact Oracle Customer Support. ORA-12687: Credentials expired. Cause: The credentials that are used to authenticate the user for the requested connection have expired. Action: Renew your credentials. Refer to the documentation specific for your Network Authentication Adapter on how to do this. ORA-12688: Login failed: the SecurID server rejected the new pincode Cause: There are a number of reasons why the SecurID server would refuse a pincode: - The user might not have permission to make up his own pincode. - The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters. - The pincode contains any non alphanumeric characters. Action: Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error. ORA-12689: Server Authentication required, but not supported Cause: Server Authentication is required for this connection, but not supported by both sides of the connection. Action: Make sure both sides of the connection have the correct version of Advanced Networking Option, and that the Authentication Adapter supports Server Authentication. ORA-12690: Server Authentication failed, login cancelled Cause: Server Authentication is required, but the server"s credentials were found invalid by the client. Action: Make sure that the server has a valid set of credentials. Refer to your authentication adapter specific documentation on how to do this. ORA-12696: Double Encryption Turned On, login disallowed Cause: The user is using a Secure Protocol Adapter that has Encryption turned ON as well as ANO Encryption. Action: Turn OFF either ANO Encryption or the Protocol Adapter Encryption if possible. Refer to Oracle Advanced Security Administrator"s Guide on how to do this. ORA-12699: Native service internal error Cause: An internal error occurred in the native services component. Action: Enable tracing to determine the exact error. Contact Oracle Customer Support. 13 ORA-12700 to ORA-19380 ORA-12700: invalid NLS parameter value (string) Cause: An invalid or unknown NLS configuration parameter was specified. Action: none ORA-12701: CREATE DATABASE character set is not known Cause: The character set specified when creating the database is unknown. Action: none ORA-12702: invalid NLS parameter string used in SQL function Cause: An unknown parameter name or invalid value is specified in a NLS parameter string. Action: none ORA-12703: this character set conversion is not supported Cause: The requested conversion between two character sets in the CONVERT function is not implemented Action: none ORA-12704: character set mismatch Cause: One of the following: - The string operands(other than an nlsparams argument) to an operator or built-in function do not have the same character set. - An nlsparams operand is not in the database character set. - String data with character set other than the database character set is passed to a built-in function not expecting it. - The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS. - A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted. - A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column. - An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter. Action: none ORA-12705: Cannot access NLS data files or invalid environment specified Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located. Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify the correct directory path/values in the environment variables. ORA-12706: this CREATE DATABASE character set is not allowed Cause: It is not allowed to create a database on a native ASCII-based machine using an EBCDIC-based character set, and vice versa. Action: none ORA-12707: error while getting create database NLS parameter string Cause: Internal error Action: none ORA-12708: error while loading create database NLS parameter string Cause: Internal error Action: none ORA-12709: error while loading create database character set Cause: Internal error Action: none ORA-12710: CREATE CONTROLFILE character set is not known Cause: The character set specified when creating the control file is unknown. Action: none ORA-12711: this CREATE CONTROLFILE character set is not allowed Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa. Action: none ORA-12712: new character set must be a superset of old character set Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC. Action: Specify a superset character set. ORA-12713: Character data loss in NCHAR/CHAR conversion Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set. Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to be FALSE. ORA-12714: invalid national character set specified Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set Action: Ensure that the specified national character set is valid ORA-12715: invalid character set specified Cause: The character set specified is not allowed for this operation or is invalid Action: Ensure that the specified character set is valid ORA-12716: Cannot ALTER DATABASE CHARACTER SET when CLOB data exists Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as import/export ORA-12717: Cannot issue ALTER DATABASE NATIONAL CHARACTER SET when NCLOB, NCHAR or NVARCHAR2 data exists Cause: NCLOB, NCHAR or NVARCHAR2 data changed the representation to Unicode when converting to a multibyte character set and must be migrated. Action: Remove NCLOB, NCHAR or NVARCHAR2 data as listed in the alert file. The above type data can be migrated by methods such as import/export. ORA-12718: operation requires connection as SYS Cause: This command can only be run when connecting as SYS Action: Connect as SYS to run this command ORA-12719: operation requires database is in RESTRICTED mode Cause: This command can only be run when the database is in RESTRICTED mode Action: Ensure that the system is in RESTRICTED mode ORA-12720: operation requires database is in EXCLUSIVE mode Cause: This command can only be run when the database is in EXCLUSIVE mode Action: Ensure that the system is in EXCLUSIVE mode ORA-12721: operation cannot execute when other sessions are active Cause: This command can only be run when there are no other sessions active Action: Ensure there are no other connections to the database ORA-12722: regular expression internal error Cause: A regular expression internal error occurred. Action: This is an internal error. Contact Oracle Support Services. ORA-12723: regular expression too complex Cause: The regular expression was too complex and could not be parsed. Action: This is an internal error. Contact Oracle Support Services. ORA-12724: regular expression corrupt Cause: The regular expression contained an incorrect sequence of metacharacters. Action: Ensure the metacharacters are correctly positioned. ORA-12725: unmatched parentheses in regular expression Cause: The regular expression did not have balanced parentheses. Action: Ensure the parentheses are correctly balanced. ORA-12726: unmatched bracket in regular expression Cause: The regular expression did not have balanced brackets. Action: Ensure the brackets are correctly balanced. ORA-12727: invalid back reference in regular expression Cause: A back references was found before a sub-expression. Action: Ensure a valid sub-expression is being referenced. ORA-12728: invalid range in regular expression Cause: An invalid range was found in the regular expression. Action: Ensure a valid range is being used. ORA-12729: invalid character class in regular expression Cause: An unknown character class was found in the regular expression. Action: Ensure a valid characters class is being used. ORA-12730: invalid equivalence class in regular expression Cause: An unknown equivalence class was found in the regular expression. Action: Ensure a valid equivalence class is being used. ORA-12731: invalid collation class in regular expression Cause: An unknown collation class was found in the regular expression. Action: Ensure a valid collation class is being used. ORA-12732: invalid interval value in regular expression Cause: An invalid interval value was found in the regular expression. Action: Ensure a valid interval value is being used. ORA-12733: regular expression too long Cause: The operation failed because the regular expression it used exceeds the maximum supported size. Action: Use a shorter regular expression. ORA-12734: Instant Client Light: unsupported client national character set string Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set ORA-12735: Instant Client Light: unsupported client character set string Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set ORA-12736: Instant Client Light: unsupported server national character set string Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set ORA-12737: Instant Client Light: unsupported server character set string Cause: The character set specified is not allowed for this operation or is invalid. Instant Client Light has only minimal character sets. Action: Do not use Instant Client Light for this character set ORA-12800: system appears too busy for parallel query execution Cause: load on system is too high to perform parallel queries. Action: re-execute serially or wait until system load is reduced. ORA-12801: error signaled in parallel query server string Cause: A parallel query server reached an exception condition. Action: Check the following error message for the cause, and consult your error manual for the appropriate action. ORA-12802: parallel query server lost contact with coordinator Cause: A parallel query server lost contact with the foreground (coordinator) process/thread. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. ORA-12803: parallel query server lost contact with another server Cause: A parallel query server lost contact with another server. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. ORA-12804: parallel query server appears to have died Cause: Cannot find process information for a parallel query server thread. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. ORA-12805: parallel query server died unexpectedly Cause: A parallel query server died unexpectedly, PMON cleaning up the process. Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. See trace file for more details. ORA-12806: could not get background process to hold enqueue Cause: Internal error. Action: This error should not normally occur. If it persists, contact Oracle Support Services. ORA-12807: process queue could not receive parallel query message Cause: Internal error. Action: This error should not normally occur. If it persists, contact Oracle Support Services. ORA-12808: cannot set string_INSTANCES greater than number of instances string Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command to a value larger than the number of available instances. Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL. ORA-12809: cannot set string_INSTANCES when mounted in exclusive mode Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode. Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle Real Application Clusters mounted in CLUSTER_DATABASE mode. ORA-12810: PARALLEL_MAX_SERVERS must be less than or equal to string Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system. Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry. ORA-12811: PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS. Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry. ORA-12812: only one PARALLEL or NOPARALLEL clause may be specified Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command. Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement. ORA-12813: value for PARALLEL or DEGREE must be greater than 0 Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement. Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause. ORA-12814: only one CACHE or NOCACHE clause may be specified Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement. Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement. ORA-12815: value for INSTANCES must be greater than 0 Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired. ORA-12817: parallel query option must be enabled Cause: A parallel query option feature has been invoked but this option has not been enabled. Action: Enable the parallel query option. ORA-12818: invalid option in PARALLEL clause Cause: an unrecognized option was used within a PARALLEL clause. Action: specify any combination of DEGREE { | DEFAULT } and INSTANCES { | DEFAULT } within the PARALLEL clause. ORA-12819: missing options in PARALLEL clause Cause: PARALLEL clause cannot be empty. Action: specify any combination of DEGREE { | DEFAULT } and INSTANCES { | DEFAULT } within the PARALLEL clause. ORA-12820: invalid value for DEGREE Cause: invalid value for DEGREE was specified within a PARALLEL clause. Action: specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause. ORA-12821: invalid value for INSTANCES Cause: invalid value for INSTANCES was specified within a PARALLEL clause. Action: specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause. ORA-12822: duplicate option in PARALLEL clause Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause. Action: specify each desired PARALLEL clause option only once. ORA-12823: default degree of parallelism may not be specified here Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command. Action: respecify with an explicit degree of parallelism. ORA-12824: INSTANCES DEFAULT may not be specified here Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command Action: respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired. ORA-12825: explicit degree of parallelism must be specified here Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER command. Action: respecify with an explicit degree of parallelism. ORA-12826: hung parallel query server was killed Cause: parallel query server was hung and subsequently killed. Action: re-execute query and report suspicious events in trace file to Oracle Support Services if error persists. ORA-12827: insufficient parallel query slaves available Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired Action: either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves ORA-12828: Can"t start parallel transaction at a remote site Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction. Action: Do not use PDML at remote sites. ORA-12829: Deadlock - itls occupied by siblings at block string of file string Cause: parallel statement failed because all itls in the current block are occupied by siblings of the same transaction. Action: increase MAXTRANS of the block or reduce the degree of parallelism for the statement. Reexecute the statement. Report suspicious events in trace file to Oracle Support Services if error persists. ORA-12830: Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued. Action: Execute COMMIT or ROLLBACK before issuing another SQL command. ORA-12831: Must COMMIT or ROLLBACK after executing INSERT with APPEND hint Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued. Action: Execute COMMIT or ROLLBACK before issuing another SQL command. ORA-12832: Could not allocate slaves on all specified instances Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query Action: To allow results to be returned by sucessfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances ORA-12833: Coordinator"s instance not a member of parallel_instance_group Cause: The coordinator"s instance must be a member of the parallel_instance_group in which this operation will be run. Action: Either add the coordinator"s instance to the current parallel_instance_group or change parallel_instance_group. ORA-12834: Instance group name, "string", too long, must be less than string characters Cause: The instance group name is too long. Action: Either shorten the name or get rid of the instance group. ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP ORA-12838: cannot read/modify an object after modifying it in parallel Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted. Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation. ORA-12839: cannot modify an object in parallel after modifying it Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted. Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation. ORA-12840: cannot access a remote table after parallel/insert direct load txn Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued. Action: Commit/rollback the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction. ORA-12841: Cannot alter the session parallel DML state within a transaction Cause: Transaction in progress Action: Commit or rollback transaction and then re-execute ORA-12842: Cursor invalidated during parallel execution Cause: The cursor was invalidated during the parse phase of deferred parallel processing, e.g. when set operands are parallelized. Action: Depends on why the cursor was invalidated. Possible causes include DDL on a schema object and shared pool being flushed. ORA-12843: pdml lock not held properly on the table Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire currently. Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the pdml again. ORA-12844: cluster reconfiguration in progress Cause: Internal error Action: THIS IS NOT A USER ERROR NUMBER/MESSAGE. THIS DOES NOT NEED TO BE TRANSLATED OR DOCUMENTED. IT IS USED ONLY FOR INTERNAL ERROR. ORA-12845: failed to receive interinstance parallel execution message Cause: OS or interconnect problem receiving interinstance message Action: Check OS specific diagnostics ORA-12850: Could not allocate slaves on all specified instances: string needed, string allocated Cause: When executing a query on a gv$ fixed view, one or more instances failed to allocate a slave to process query. Action: Check trace output for instances on which slaves failed to start. GV$ query can only proceed if slaves can be allocated on all instances. ORA-12851: PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value less than PARALLEL_MIN_SERVERS. Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to PARALLEL_MIN_SERVERS value specified in the accompanying message and retry. ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES, string Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES. Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES value specified in the accompanying message and retry. ORA-12853: insufficient memory for PX buffers: current stringK, max needed stringK Cause: Insufficient SGA memory for PX buffers Action: Reconfigure sga to include at least (max - current) bytes of additional memory ORA-12854: Parallel query is not supported on temporary LOBs Cause: The parallel query statement produced a temporary LOB. Action: Turn off parallelism for the query or underlying table ORA-12855: cannot run parallel or insert direct load in a loopback Cause: A loopback was created in the transaction before this operation. Action: Do not use loopback when using pdml or insert direct load. ORA-12856: cannot run parallel query on a loopback connection Cause: A table or index in a parallel query is referenced via a loopback connection. Action: Do not use loopback connection when running a query in parallel. ORA-12872: First slave parse gave different plan Cause: First hard parse on slave given QC-supplied environment and parameters gave different plan from QC. Try again with outline. Action: No external action. Internally used for outline-based reparse. ORA-12899: value too large for column string (actual: string, maximum: string) Cause: An attempt was made to insert or update a column with a value which is too wide for the width of the destination column. The name of the column is given, along with the actual width of the value, and the maximum allowed width of the column. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes. Action: Examine the SQL statement for correctness. Check source and destination column data types. Either make the destination column wider, or use a subset of the source column (i.e. use substring). ORA-12900: must specify a default temporary tablespace for a locally managed database Cause: a locally managed database must have a temporary tablespace other than SYSTEM tablespace Action: specify the default temporary tablespace when creating a locally managed database ORA-12901: default temporary tablespace must be of TEMPORARY type Cause: in a locally managed database, default temporary tablespace must be TEMPORARY type Action: none ORA-12902: default temporary tablespace must be SYSTEM or of TEMPORARY type Cause: in a dictionary managed database, default temporary tablespace must be SYSTEM or TEMPORARY type Action: none ORA-12910: cannot specify temporary tablespace as default tablespace Cause: attempt to assign a temporary tablespace to be a user"s default tablespace Action: assign a permanent tablespace to be the default tablespace ORA-12911: permanent tablespace cannot be temporary tablespace Cause: attempt to assign a permanent tablespace to be a user"s temporary tablespace Action: assign a temporary tablespace to be user"s temporary tablespace ORA-12912: Dictionary managed tablespace specified as temporary tablespace Cause: attempt to assign a dictionary managed tablespace to be a user"s temporary tablespace Action: Assign a locally managed temporary tablespace to be user"s temporary tablespace ORA-12913: Cannot create dictionary managed tablespace Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed Action: Create a locally managed tablespace. ORA-12914: Cannot migrate tablespace to dictionary managed type Cause: Attemp to migrate locally managed tablespace to dictionary managed type when the database has locally managed system tablespace. Action: Command cannot be issued. ORA-12915: Cannot alter dictionary managed tablespace to read write Cause: Attemp to alter dictionary managed tablespace to read write in database which has system tablespace as locally managed. This tablespace can only be dropped. Action: Command cannot be issued. ORA-12916: Cannot use default permanent tablespace with this release Cause: To use default permanent tablespace the release should be 10.0 or higher Action: Check the compatibility setting and reissue the statement ORA-12918: Invalid tablespace type for default permanent tablespace Cause: The tablespace is either dropped, temporary or undo Action: Check the tablespace type and reissue the statement ORA-12919: Can not drop the default permanent tablespace Cause: An attemp was made to drop the default permanent tablespace Action: Make a different tablespace as the default permanent tablespace and reissue the drop ORA-12920: database is already in force logging mode Cause: ALTER DATABASE FORCE LOGGING command failed because the database is already in force logging mode. Action: none ORA-12921: database is not in force logging mode Cause: ALTER DATABASE NO FORCE LOGGING command failed because the database is not in force logging mode. Action: none ORA-12922: concurrent ALTER DATABASE [NO] FORCE LOGGING command is running Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING command running in the system. Action: Contact the database administrator who is responsible for the concurrent command. ORA-12923: tablespace string is in force logging mode Cause: An attempt to alter the specified tablespace temporary failed because the tablespace is in force logging mode. Action: Put the tablespace out of force logging mode by ALTER TABLESPACE NO FORCE LOGGING command. ORA-12924: tablespace string is already in force logging mode Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode. Action: none ORA-12925: tablespace string is not in force logging mode Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode. Action: none ORA-12926: FORCE LOGGING option already specified Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once. Action: Remove all but one of the FORCE LOGGING options. ORA-12927: RETENTION option already specified Cause: In CREATE TABLESPACE, the RETENTION option was specified more than once. Action: Remove all but one of the RETENTION options. ORA-12950: SYSTEM tablespace specified as default permanent tablespace Cause: SYSTEM tablespace was specified as the default permanent during database creation. Action: If default permanent tablespace is not specified,then SYSTEM will implicitly become the default permanent tablespace. Specify an alternate tablespace or omit the default tablespace clause and reissue the CREATE DATABASE statement ORA-12951: Attempt to change default permanent tablespace to temporary Cause: It is incorrect to alter the default permanent tablespace of a database to temporary type Action: none ORA-12980: checkpoint option not allowed with SET UNUSED Cause: An attempt was made to specify checkpoint option with SET UNUSED. Action: Remove checkpoint option. ORA-12981: cannot drop column from an object type table Cause: An attempt was made to drop a column from an object type table. Action: This action is not allowed. ORA-12982: cannot drop column from a nested table Cause: An attempt was made to drop a column from a nested table. Action: This action is not allowed. ORA-12983: cannot drop all columns in a table Cause: An attempt was made to drop all columns in a table. Action: Make sure at least one column remains in the table after the drop column operation. ORA-12984: cannot drop partitioning column Cause: An attempt was made to drop a column used as the partitioning key. Action: This action is not allowed. ORA-12985: tablespace "string" is read only, cannot drop column Cause: An attempt was made to drop column from a partition/subpartition on a read only tablespace. Action: Set the tablespace to read write and resubmit statement. ORA-12986: columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE Cause: An attempt was made to access a table with columns in partially dropped state (i.e., drop column operation was interrupted). Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table. ORA-12987: cannot combine drop column with other operations Cause: An attempt was made to combine drop column with other ALTER TABLE operations. Action: Ensure that drop column is the sole operation specified in ALTER TABLE. ORA-12988: cannot drop column from table owned by SYS Cause: An attempt was made to drop a column from a system table. Action: This action is not allowed ORA-12989: invalid value for checkpoint interval Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1). Action: Correct checkpoint interval and resubmit statement ORA-12990: duplicate option specified Cause: Duplicate option specified in statement. Action: Remove the duplicate option and resubmit statement. ORA-12991: column is referenced in a multi-column constraint Cause: An attempt was made to drop a column referenced by some constraints. Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement. ORA-12992: cannot drop parent key column Cause: An attempt was made to drop a parent key column. Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement. ORA-12993: tablespace "string" is offline, cannot drop column Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace. Action: Bring the tablespace online and resubmit statement. ORA-12994: drop column option only allowed once in statement Cause: An attempt was made to repeat the drop column option in a single statement. Action: Separate drop column options into different statements and resubmit statements. ORA-12995: no columns in partially dropped state Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns. Action: Cannot submit this statement. ORA-12996: cannot drop system-generated virtual column Cause: An attempt was made to drop a virtual column generated by the system. Action: none ORA-12997: cannot drop primary key column from an index-organized table Cause: An attempt was made to drop a primary key column from an index- organized table. Action: This action is not allowed. ORA-13000: dimension number is out of range Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE. Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE. ORA-13001: dimensions mismatch error Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match. Action: Make sure that the number of dimensions in the HHCODEs match. ORA-13002: specified level is out of range Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE. Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE. ORA-13003: the specified range for a dimension is invalid Cause: The specified range for a dimension is invalid. Action: Make sure that the lower bound (lb) is less than the upper bound (ub). ORA-13004: the specified buffer size is invalid Cause: The buffer size for a function is not valid. Action: This is an internal error. Contact Oracle Support Services. ORA-13005: recursive HHCODE function error Cause: An error occurred in a recursively called HHCODE function. Action: This is an internal error. Contact Oracle Support Services. ORA-13006: the specified cell number is invalid Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1). Action: Make sure that the cell identifier is between 0 and (2^ndim - 1). ORA-13007: an invalid HEX character was detected Cause: A character that is not in the range [0-9] or [A-F a-f] was detected. Action: Verify that all characters in a string are in [0-9] or [A-F a-f]. ORA-13008: the specified date format has an invalid component Cause: Part of specified date format is invalid. Action: Verify that the date format is valid. ORA-13009: the specified date string is invalid Cause: The specified date string has a bad component or does not match the specified format string. Action: Make sure that the components of the date string are valid and that the date and format strings match. ORA-13010: an invalid number of arguments has been specified Cause: An invalid number of arguments was specified for an SDO function. Action: Verify the syntax of the function call. ORA-13011: value is out of range Cause: A specified dimension value is outside the range defined for that dimension. Action: Make sure that all values to be encoded are within the defined dimension range. ORA-13012: an invalid window type was specified Cause: An invalid window type was specified. Action: Valid window types are RANGE, PROXIMITY, POLYGON. ORA-13013: the specified topology was not INTERIOR or BOUNDARY Cause: A topology was specified that was not INTERIOR or BOUNDARY. Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE"s topology. ORA-13014: a topology identifier outside the range of 1 to 8 was specified Cause: A topology identifier outside the range of 1 to 8 was specified. Action: Specify a topology in the range of 1 to 8. ORA-13015: the window definition is not valid Cause: The number of values used to define the window does not correspond to the window type. Action: Verify that the number of values used to defined the window is correct for the window type and number of dimensions. ORA-13016: specified topology [string] is invalid Cause: The specified topology did not exist in the database, or some components of the topology were missing from the database. Action: Check the specified topology by executing the SDO_TOPO.validate_topology function. ORA-13017: unrecognized line partition shape Cause: The shape of a 2-D line partition could not be determined. Action: This is an internal error. Contact Oracle Support Services. ORA-13018: bad distance type Cause: The specified distance type is invalid. Action: The only supported distance functions are EUCLID and MANHATTAN. ORA-13019: coordinates out of bounds Cause: Vertex coordinates lie outside the valid range for specified dimension. Action: Redefine vertex coordinates within specified boundaries. ORA-13020: coordinate is NULL Cause: A vertex coordinate has a NULL value. Action: Redefine vertex coordinate to have non-NULL value. ORA-13021: element not continuous Cause: The coordinates defining a geometric element are not connected. Action: Redefine coordinates for the geometric element. ORA-13022: polygon crosses itself Cause: The coordinates defining a polygonal geometric element represent crossing segments. Action: Redefine coordinates for the polygon. ORA-13023: interior element interacts with exterior element Cause: An interior element of a geometric object interacts with the exterior element of that object. Action: Redefine coordinates for the geometric elements. ORA-13024: polygon has less than three segments Cause: The coordinates defining a polygonal geometric element represent less than three segments. Action: Redefine the coordinates for the polygon. ORA-13025: polygon does not close Cause: The coordinates defining a polygonal geometric element represent an open polygon. Action: Redefine the coordinates of the polygon. ORA-13026: unknown element type for element string.string.string Cause: The SDO_ETYPE column in the _SDOGEOM table contains an invalid geometric element type value. Action: Redefine the geometric element type in the _SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial documentation for an explanation of SDO_ETYPE and its possible values. ORA-13027: unable to read dimension definition from string Cause: There was a problem reading the dimension definition from the _SDODIM table. Action: Verify that the _SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message. ORA-13028: Invalid Gtype in the SDO_GEOMETRY object Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object. Action: Verify that the geometries have valid gtypes. ORA-13029: Invalid SRID in the SDO_GEOMETRY object Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range. Action: Verify that the geometries have valid SRIDs. ORA-13030: Invalid dimension for the SDO_GEOMETRY object Cause: There is a mismatch between the dimension in the SDO_GTYPE and dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object. Action: Verify that the geometries have valid dimensionality. ORA-13031: Invalid Gtype in the SDO_GEOMETRY object for point object Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT. Action: Verify that the geometries have valid gtypes. ORA-13032: Invalid NULL SDO_GEOMETRY object Cause: There are invalid SDO_POINT_TYPE or SDO_ELEM_INFO_ARRAY or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object. Action: Verify that the geometries have valid fields. To specify a NULL geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL. ORA-13033: Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry. Action: Verify that the geometries have valid data. ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X or Y or both. Action: Verify that the geometries have valid data. ORA-13035: Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates. Action: Verify that the geometries have valid data. ORA-13036: Operation [string] not supported for Point Data Cause: The specified geometry function is not supported for point data. Action: Make sure that the specified geometry function is not called on point data. ORA-13037: SRIDs do not match for the two geometries Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID. Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs. ORA-13039: failed to update spatial index for element string.string.string Cause: Another error will accompany this message that will indicate the problem. Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services. ORA-13040: failed to subdivide tile Cause: This is an internal error. Action: Note any accompanying errors and contact Oracle Support Services. ORA-13041: failed to compare tile with element string.string.string Cause: The spatial relationship between a generated tile and the specified element could not be determined. Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13041 and contact Oracle Support Services. ORA-13042: invalid SDO_LEVEL and SDO_NUMTILES combination Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the _SDOLAYER table. The most likely cause is that the columns are NULL. Action: Verify the that SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial documentation. Then retry the operation. ORA-13043: failed to read metadata from the _SDOLAYER table Cause: An error was encountered reading the layer metadata from the _SDOLAYER table. Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, contact Oracle Support Services. ORA-13044: the specified tile size is smaller than the tolerance Cause: The tile size specified for fixed size tessellation is smaller than the tolerance as specified in the layer metadata. Action: See the Oracle Spatial documentation for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a smaller tile size value than the current one. ORA-13045: invalid compatibility flag Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13046: invalid number of arguments Cause: An invalid number of arguments were specified for an SDO_GEOM function. Action: See the Oracle Spatial documentation for a description of the syntax and semantics of the relevant SDO_GEOM function. ORA-13047: unable to determine ordinate count from table _SDOLAYER Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer . Action: Verify that the _SDOLAYER table has a valid value for the column SDO_ORDCNT. Then retry the operation. ORA-13048: recursive SQL fetch error Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13049: unable to determine tolerance value from table _SDODIM Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer . Action: Verify that the _SDODIM table has a valid value for the column SDO_TOLERANCE. ORA-13050: unable to construct spatial object Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13051: failed to initialize spatial object Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13052: unsupported geometric type for geometry string.string Cause: The geometry type for a specific instance in a _SDOGEOM table is not among the set of geometry types supported by Oracle Spatial. Action: Check the Oracle Spatial documentation for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema. ORA-13053: maximum number of geometric elements in argument list exceeded Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded. Action: Check the Oracle Spatial documentation for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it in as an argument in a call to the SDO_GEOM function. ORA-13054: recursive SQL parse error Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13055: Oracle object string does not exist in specified table Cause: The requested object is not present in the specified table. Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Then retry the operation. ORA-13060: topology with the name string already exists Cause: The specified topology name was not unique in the database. Action: Verify that the CREATE_TOPOLOGY call specifies the correct topology name and that the procedure is invoked from the correct schema. ORA-13061: topology with the name string does not exist Cause: The specified topology did not exist in the database. Action: Verify that the current procedure/function call specifies the correct schema and topology name. ORA-13062: topology IDs do not match in the feature table and the topology Cause: The specified topology ID in the feature table did not match the topology ID stored in the topology metadata. Action: Verify that the specified topology ID matches the topology ID stored in the topology metadata. ORA-13063: relationship information table is missing data for feature table [string] Cause: The topology relationship information table (xxx_RELATION$) did not have the matching partition corresponding to the feature table. Action: Make sure the correct topology IDs and names are specified in the call to register the feature table with the topology. ORA-13064: relationship information table has inconsistent data for feature table [string] Cause: The topology_id, tg_layer_id values stored in the feature table did not match the values stored in the topology relationship information table (xxx_RELATION$). Action: Make sure that the correct feature tables are specified in the call to register the feature table with the topology. ORA-13065: cannot delete a child layer with a parent layer Cause: A call was made to delete a feature layer which has a dependent layer defined on it. Action: Make sure that all dependent feature layers are deleted before deleting the current feature layer. ORA-13066: wrong feature geometry or element type Cause: The SDO_TOPO_GEOMETRY object had the wrong geometry and/or element type. Action: Correct the geometry and/or element type in the SDO_TOPO_GEOMETRY object. ORA-13067: operator requires both parameters from the same topology Cause: Both SDO_TOPO_GEOMETRY parameters did not come from the same topology. Action: Make sure both the parameters to the operator are from the same topology. If this is not possible, consider using a signature of the operator that does not use two SDO_TOPO_GEOMETRY parameters. ORA-13068: wrong table or column name in SDO_TOPO_GEOMETRY constructor Cause: An SDO_TOPO_GEOMETRY constructor was invoked with incorrect parameters for table name and/or column name. Action: Fix the parameters in the call and try again. ORA-13108: spatial table string not found Cause: The specified spatial table does not exist. Action: Check the Spatial data dictionary to make sure that the table is registered. ORA-13109: spatial table string exists Cause: The specified spatial table is registered in the Spatial data dictionary. Action: Remove the existing table from the Spatial data dictionary or use a different name. ORA-13110: cannot drop topology with associated topo_geometry tables Cause: The drop_topology procedure was invoked for a topology that has assocated topo_geometry layers with it. Action: Delete the topo_geometry layers from the topology before dropping the topology. Use SDO_TOPO.delete_topo_geometry_layer to delete topo_geometry layers from the topology. ORA-13111: cannot add topo_geometry layer [string] to topology Cause: It was not possible to add the specified topo_geometry layer to the topology. Action: Make sure the topo_geometry layer table exists in the database. ORA-13112: cannot delete topo_geometry layer [string] from topology Cause: It was not possible to delete the specified topo_geometry layer from the topology. Action: Check USER_SDO_TOPO_METADATA to see if the specified topo_geometry layer is part of the topology. Only those topo_geometry layers which are part of the topology can be deleted from it. ORA-13113: invalid tg_layer_id in sdo_topo_geometry constructor Cause: An invalid layer_id was passed to the SDO_TOPO_GEOMETRY constructor. Action: Valid layer_ids are obtained by adding a topo_geometry layer to the topology. Check USER_SDO_TOPO_METADATA to find out the layer_id for an existing topo_geometry layer. ORA-13114: [string]_NODE$ table does not exist Cause: The NODE$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. ORA-13115: [string]_EDGE$ table does not exist Cause: The EDGE$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. ORA-13116: [string]_FACE$ table does not exist Cause: The FACE$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. ORA-13117: [string]_RELATION$ table does not exist Cause: The RELATION$ table for the topology did not exist in the database. Action: There is a severe corruption of the topology. Call Oracle Support Services with the error number. ORA-13118: invalid node_id [string] Cause: A topology node operation was invoked with an invalid node_id. Action: Check the topology node$ table to see if the specified node_id exists in the topology. ORA-13119: invalid edge_id [string] Cause: A topology edge operation was invoked with an invalid edge_id. Action: Check the topology edge$ table to see if the specified edge_id exists in the topology. ORA-13120: invalid face_id [string] Cause: A topology face operation was invoked with an invalid face_id. Action: Check the topology face$ table to see if the specified face_id exists in the topology. ORA-13121: layer type type mismatch with topo_geometry layer type Cause: The tg_type in SDO_TOPO_GEOMETRY constructor did not match the type specified for the layer. Action: Check the USER_SDO_TOPO_METADATA view to see the layer type for the layer and use it in the constructor. ORA-13122: invalid topo_geometry specified Cause: The SDO_TOPO_GEOMETRY object passed into the function/operator was not valid. Action: Check the SDO_TOPO_GEOMETRY object and verify that it is a valid topo_geometry object. ORA-13123: invalid name specified Cause: The create_topo operation requires a unique TOPOLOGY name, that already does not exist in the database. Action: Check to see if there is already an entry in the USER_SDO_TOPO_METADATA (or the MDSYS.SDO_TOPO_METADATA_TABLE) with this topology name. ORA-13124: unable to determine column id for column string Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13125: partition key is already set Cause: A partition key is already set for the spatial table. Action: Only one partition key can be specified per spatial table. ORA-13126: unable to determine class for spatial table string Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13127: failed to generate target partition Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13128: current tiling level exceeds user specified tiling level Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13129: HHCODE column string not found Cause: The specified spatial column does not exist. Action: Verify that the specified column is a spatial column by checking the Spatial data dictionary. ORA-13135: failed to alter spatial table Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13136: null common code generated Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13137: failed to generate tablespace sequence number Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13138: could not determine name of object string Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13139: could not obtain column definition for string Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13140: invalid target type Cause: The specified target type is not valid. Action: Substitute a valid target type. Valid target types are TABLE and VIEW. ORA-13141: invalid RANGE window definition Cause: The RANGE window specified is not correctly defined. Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (e.g.: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values. ORA-13142: invalid PROXIMITY window definition Cause: The PROXIMITY window specified is not correctly defined. Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values. ORA-13143: invalid POLYGON window definition Cause: The POLYGON window specified is not correctly defined. Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values. ORA-13144: target table string not found Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13145: failed to generate range list Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13146: could not find table substitution variable string Cause: The partition name substitution variable %s was not found in the SQL filter. Action: The substitution variable %s must be in the SQL filter to indicate where that partition name should be placed. ORA-13147: failed to generate MBR Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13148: failed to generate SQL filter Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13149: failed to generate next sequence number for spatial table string Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13150: failed to insert exception record Cause: Operation failed to insert a record into the exception table. Action: Fix any other errors reported. ORA-13151: failed to remove exception record Cause: Operation failed to remove a record from the exception table. Action: Fix any other errors reported. ORA-13152: invalid HHCODE type Cause: Specified HHCODE type is not valid. Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE. ORA-13153: invalid high water mark specified Cause: The high water mark must be greater than or equal to zero. Action: Make sure that the high water mark is an integer greater than or equal to zero. ORA-13154: invalid precision specified Cause: The precision specified is out of range. Action: The precision must be an integer greater than or equal to zero. ORA-13155: invalid number of dimensions specified Cause: The number of dimensions specified is out of range. Action: The number of dimension must be between 1 and 32. ORA-13156: table to be registered string.string is not empty Cause: The specified table has rows in it. Action: Make sure that the table to be registered is empty. ORA-13157: Oracle error ORAstring encountered while string Cause: The specified Oracle error was encountered. Action: Correct the Oracle error. ORA-13158: Oracle object string does not exist Cause: The specified object does not exist. Action: Verify that the specified object exists. ORA-13159: Oracle table string already exists Cause: The specified table already exists. Action: Drop the specified table. ORA-13181: unable to determine length of column string_SDOINDEX.SDO_CODE Cause: The length of the SDO_CODE column in the _SDOINDEX table could not be determined. Action: Make sure that the _SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Then retry the operation. ORA-13182: failed to read element string.string.string Cause: The specified element could not be read from the _SDOGEOM table. Action: Verify that the specified element exists in the table. Then retry the operation. ORA-13183: unsupported geometric type for geometry string.string Cause: The geometry type in the _SDOGEOM table is unsupported. Action: Modify the geometry type to be one of the supported types. ORA-13184: failed to initialize tessellation package Cause: Initialization of the tessellation package failed. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13185: failed to generate initial HHCODE Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13186: fixed tile size tessellation failed Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13187: subdivision failed Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13188: cell decode failed Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13189: recursive SQL parse failed Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13190: recursive SQL fetch failed Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13191: failed to read SDO_ORDCNT value Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13192: failed to read number of element rows Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13193: failed to allocate space for geometry Cause: There was insufficient memory to read the geometry from the database. Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services. ORA-13194: failed to decode supercell Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13195: failed to generate maximum tile value Cause: This is an internal error. Action: Record the error messages that are returned and contact Oracle Support Services. ORA-13196: failed to compute supercell for element string.string.string Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry. Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. ORA-13197: element string.string.string is out of range Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the _SDODIM table. Action: Verify that the geometry is valid and within the defined domain. ORA-13198: Spatial error: string Cause: Internal error in some Oracle Spatial stored procedure. Action: Record the sequence of procedure calls or events that preceded this error, and contact Oracle Support Services if the error message text does not clearly specify the cause of the error. ORA-13199: %s Cause: This is an internal error. Action: Contact Oracle Support Services. ORA-13200: internal error [string] in spatial indexing. Cause: This is an internal error. Action: Contact Oracle Support Services with the exact error text. ORA-13201: invalid parameters supplied in CREATE INDEX statement Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement. Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for spatial index creation. ORA-13202: failed to create or insert into the SDO_INDEX_METADATA table Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it. Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace. ORA-13203: failed to read USER_SDO_GEOM_METADATA view Cause: An error encountered while trying to read the USER_SDO_GEOM_METADATA view. Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table. ORA-13204: failed to create spatial index table Cause: An error was encountered while trying to create the index table. Action: Check that user has CREATE TABLE privilege in the current schema and that the user has sufficient quota in the default or specified tablespace. ORA-13205: internal error while parsing spatial parameters Cause: An internal error was encountered while parsing the spatial parameters. Action: Check that the parameters passed in the parameter string are all valid. ORA-13206: internal error [string] while creating the spatial index Cause: An internal error was encountered while creating the spatial index. Action: Contact Oracle Support Services with the exact error text. ORA-13207: incorrect use of the [string] operator Cause: An error was encountered while evaluating the specified operator. Action: Check the parameters and the return type of the specified operator. ORA-13208: internal error while evaluating [string] operator Cause: An internal error was encountered. Action: Contact Oracle Support Services with the exact error text. ORA-13209: internal error while reading SDO_INDEX_METADATA table Cause: An internal error was encountered while trying to read the SDO_INDEX_METADATA table. Action: Contact Oracle Support Services. Note this and accompanying error numbers. ORA-13210: error inserting data into the index table Cause: An error was encountered while trying to insert data into the index table. Likely causes are: - Insufficient quota in the current tablespace - User does not appropriate privileges Action: Check the accompanying error messages. ORA-13211: failed to tessellate the window object Cause: An internal error was encountered while trying to tessellate the window object. Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. ORA-13212: failed to compare tile with the window object Cause: The spatial relationship between a generated tile and the specified window object could not be determined. Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any accompanying errors and contact Oracle Support Services. ORA-13213: failed to generate spatial index for window object Cause: Another error, indicating the real cause of the problem, should accompany this error. Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services. ORA-13214: failed to compute supercell for window object Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry. Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. ORA-13215: window object is out of range Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view. Action: Verify that the geometry is valid and within the defined domain. ORA-13216: failed to update spatial index Cause: Another error will accompany this message that will indicate the problem. Action: Correct any accompanying errors. If no accompanying error message appears, contact Oracle Support Services. ORA-13217: invalid parameters supplied in ALTER INDEX statement Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement. Action: Check the Oracle Spatial documentation for the number, syntax, and semantics of expected parameters for the spatial ALTER INDEX statement. ORA-13218: max number of supported index tables reached for [string] index Cause: An add_index parameter was passed to ALTER INDEX when the number of existing index tables is already at maximum. Action: Delete one of the index tables before adding another index table. ORA-13219: failed to create spatial index table [string] Cause: An error was encountered while trying to create the index table. Action: There is a table in the index"s schema with the specified name. The CREATE INDEX statement will try to create an index table with this name. Either rename this table or change the name of the index. ORA-13220: failed to compare tile with the geometry Cause: The spatial relationship between a generated tile and the specified geometry could not be determined. Action: This is an internal error. Validate the geometry using the VALIDATE_GEOMETRY_WITH_CONTEXT procedure. If the procedure does not return any errors, note any errors that accompany ORA-13220 and contact Oracle Support Services. ORA-13221: unknown geometry type in the geometry object Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value Action: Redefine the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial documentation for an explanation of SDO_GTYPE and its possible values. ORA-13222: failed to compute supercell for geometry in string Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table. Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness. ORA-13223: duplicate entry for string in SDO_GEOM_METADATA Cause: There are duplicate entries for the given table and column value pair in the USER_SDO_GEOM_METADATA view. Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the USER_SDO_GEOM_METADATA view. ORA-13224: zero tolerance specified for layer in USER_SDO_GEOM_METADATA Cause: A tolerance of zero or NULL is supplied for a layer in USER_SDO_GEOM_METADATA view. Action: Check the tolerance specified to make sure it is a positive value. ORA-13225: specified index table name is too long for a spatial index Cause: An index table name is specified which is longer than the supported length of the spatial index table name. Action: Check the supported size of the index table name and reduce the size of the index name. ORA-13226: interface not supported without a spatial index Cause: The geometry table does not have a spatial index. Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it. ORA-13227: SDO_LEVEL values for the two index tables do not match Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match. Action: Verify that two compatible indexes are used for the spatial join operator. Quadtree indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values ORA-13228: spatial index create failed due to invalid type Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY. Action: Make sure that the index is created on a column of type SDO_GEOMETRY. ORA-13230: failed to create temporary table [string] during R-tree creation Cause: The specified temporary table either already exists or there is not enough tablespace. Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace. ORA-13231: failed to create index table [string] during R-tree creation Cause: The specified index table either already exists or there is not enough tablespace. Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privileges and has sufficient space in the default or specified tablespace. If that fails to correct the problem, contact Oracle Support Services. ORA-13232: failed to allocate memory during R-tree creation Cause: This feature assumes a minimum of 64K memory for bulk creation. Action: Create the index for a small subset of the data. Then, use transactional insert operations for the rest of the data. ORA-13233: failed to create sequence number [string] for R-tree Cause: The specified sequence number exists. Action: Delete the sequence object, or contact Oracle Support Services. ORA-13234: failed to access R-tree-index table [string] Cause: The index table is either deleted or corrupted. Action: Rebuild the index or contact Oracle Support Services with accompanying error messages. ORA-13236: internal error in R-tree processing: [string] Cause: An internal error occurred in R-tree processing. Action: Contact Oracle Support Services with the message text. ORA-13237: internal error during R-tree concurrent updates: [string] Cause: An inconsistency is encountered during concurrent updates, possibly due to the use of serializable isolation level. Action: Change the isolation level to "read committed" using the ALTER SESSION statement, or contact Oracle Support Services with the message text. ORA-13239: sdo_dimensionality not specified during n-d R-tree creation Cause: An error occurred in reading the dimensionality parameter Action: Check the documentation for a valid range, and specify the dimensionality as a parameter. ORA-13240: specified dimensionality greater than that of the query mbr Cause: An error occurred because of too few values in the query minimum bounding rectangle (MBR). Action: Omit the dimensionality, or use the dimensionality of the query. ORA-13241: specified dimensionality does not match that of the data Cause: An error occurred because the dimensionality specified in the CREATE INDEX statement does not match that of the data. Action: Change the statement to reflect the data dimensionality. ORA-13243: specified operator is not supported for 3- or higher-dimensional R-tree Cause: Currently, an R-tree index with three or more index dimensions can be used only with the SDO_FILTER operator. Action: Use the SDO_FILTER operator, and check the documentation for the querytype parameter for SDO_FILTER; or contact Oracle Support Services. ORA-13249: %s Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component. Action: Contact Oracle Support Services with the exact error text. ORA-13250: insufficient privileges to modify metadata table entries Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables. Action: Check that the specified feature and geometry table names are correct, and then verify that the current user has at least SELECT privilege on those tables. ORA-13251: duplicate entry string in metadata table Cause: The specified entry already exists in the metadata table. Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once. ORA-13260: layer table string does not exist Cause: Data migration source table _SDOGEOM does not exist. Action: Ensure that the specified layer name is correct and that the corresponding spatial layer tables exist in the current schema. ORA-13261: geometry table string does not exist Cause: The specified geometry table does not exist in the current schema. Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values. ORA-13262: geometry column string does not exist in table string Cause: The specified table does not have a column of type SDO_GEOMETRY. Action: Alter or re-create the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER. ORA-13263: column string in table string is not of type SDO_GEOMETRY Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY. Action: Alter the column definition to be of type SDO_GEOMETRY. ORA-13264: geometry identifier column string does not exist in table string Cause: The specified table does not contain a GID column. Action: Confirm that the GID column name was correctly specified and that it exists in the specified table. ORA-13265: geometry identifier column string in table string is not of type NUMBER Cause: GID column is not of type NUMBER. Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER. ORA-13266: error inserting data into table string Cause: An OCI error occurred, or the user has insufficient quota in the active tablespace, or the rollback segments are too small. Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem. ORA-13267: error reading data from layer table string Cause: There was an error reading the geometry data from the _SDOGEOM table. Action: Verify that _SDOGEOM and _SDODIM exist. If they do exist, run VALIDATE_LAYER_WITH_CONTEXT on the specified layer. ORA-13268: error obtaining dimension from USER_SDO_GEOM_METADATA Cause: There is no entry in the USER_SDO_GEOM_METADATA view for the specified geometry table. Action: Insert an entry for the destination geometry table with the correct dimension information. ORA-13269: internal error [string] encountered when processing geometry table Cause: An internal error occurred. Action: Contact Oracle Support Services with the exact error message text. ORA-13270: OCI error string Cause: An OCI error occurred while processing the layer or geometry tables. Action: Take the appropriate steps to correct the OCI-specific error. ORA-13271: error allocating memory for geometry object Cause: Insufficient memory. Action: Make more memory available to the current session/process. ORA-13272: geometric object string in table string is invalid Cause: The specified object failed the geometric integrity checks performed by the validation function. Action: Check the Oracle Spatial documentation for information about the geometric integrity checks performed by VALIDATE_GEOMETRY_WITH_CONTEXT and correct the geometry definition if required. ORA-13273: dimension metadata table string does not exist Cause: The _SDODIM table does not exist. Action: Verify that the specified layer name is correct and that the _SDODIM table exists in the current schema. ORA-13274: operator invoked with non-compatible SRIDs Cause: A Spatial operator was invoked with a window geometry with an SRID but the layer has no SRID; or the window has no SRID but the layer has an SRID. Action: Make sure that the layer and window both have an SRID or that they both do not have an SRID. ORA-13275: spatial index creation failure on unsupported type Cause: An attempt was made to create a spatial index create on a column that is not of type SDO_GEOMETRY. Action: A spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column is of type SDO_GEOMETRY. ORA-13276: internal error [string] in coordinate transformation Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. ORA-13278: failure to convert SRID to native format Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. ORA-13281: failure in execution of SQL statement to retrieve WKT Cause: OCI internal error, or SRID does not match a table entry. Action: Check that a valid SRID is being used. ORA-13282: failure on initialization of coordinate transformation Cause: Parsing error on source or destination coordinate system WKT, or incompatible coordinate systems. Action: Check the validity of the WKT for table entries, and check if the requested transformation is valid. ORA-13283: failure to get new geometry object for conversion in place Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. ORA-13284: failure to copy geometry object for conversion in place Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. ORA-13285: Geometry coordinate transformation error Cause: A coordinate pair was out of valid range for a conversion/projection. Action: Check that data to be transformed is consistent with the desired conversion/projection. ORA-13287: can"t transform unknown gtype Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed. Action: Check the Oracle Spatial documentation for SDO_GTYPE values, and specify a value whose last digit is 1 or higher. ORA-13288: point coordinate transformation error Cause: An internal error occurred while transforming points. Action: Check the accompanying error messages. ORA-13290: the specified unit is not supported Cause: An Oracle Spatial function was called with an unknown UNIT value. Action: Check Spatial documentation for the supported units, and call the function with the correct UNIT parameter. ORA-13291: conversion error between the specified unit and standard unit Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area. Action: Check the unit specification and respecify it. ORA-13292: incorrect ARC_TOLERANCE specification Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified, and it should not be less than the tolerance specified for the geometry. Action: Check ARC_TOLERANCE specification and make sure it is correct. ORA-13293: cannot specify unit for geometry without a georeferenced SRID Cause: An Oracle Spatial function with a UNIT parameter was called on a geometry without a georeferenced SRID. Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs. ORA-13294: cannot transform geometry containing circular arcs Cause: It is impossible to transform a 3-point representation of a circular arc without distortion. Action: Make sure a geometry does not contain circular arcs. ORA-13295: geometry objects are in different coordinate systems Cause: An Oracle Spatial function was called with two geometries that have different SRIDs. Action: Transform geometry objects to be in the same coordinate system and call the spatial function. ORA-13296: incorrect coordinate system specification Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID. Action: Check WKT in the MDSYS.CS_SRS table for Earth radius and inverse flattening. ORA-13300: single point transform error Cause: Low-level coordinate transformation error trap. Action: Check the accompanying error messages. ORA-13303: failure to retrieve a geometry object from a table Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. ORA-13304: failure to insert a transformed geometry object in a table Cause: OCI internal error. Action: Contact Oracle Support Services with the exact error message text. ORA-13330: invalid MASK Cause: The MASK passed to the RELATE function is not valid. Action: Verify that the mask is not NULL. See the Oracle Spatial documentation for a list of supported masks. ORA-13331: invalid LRS segment Cause: The given LRS segment was not a valid line string. Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in the Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or longitude/latitude, plus measure) ORA-13332: invalid LRS point Cause: The specified LRS point was not a point geometry with measure information. Action: Check the given point geometry. A valid LRS point is a point geometry in Oracle Spatial with an additional dimension for measure. ORA-13333: invalid LRS measure Cause: The given measure for linear referencing was out of range. Action: Redefine the measure. ORA-13334: LRS segments not connected Cause: The specified geometric segments are not connected. Action: Check the start/end points of the given geometric segments. ORA-13335: LRS measure information not defined Cause: The measure information of a geometric segment was not assigned (IS NULL). Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null). ORA-13336: failure in converting standard diminfo/geometry to LRS dim/geom Cause: There is no room for the measure dimension in the given diminfo, or the specified standard geometry is not a point a line string. Action: Check if the diminfo dimensions are less than 3 or if the geometry type is point or line string. ORA-13337: failure in concatenating LRS polygons Cause: LRS concatenation involving LRS polygons is not supported. Action: Check the geometry and element types to make sure the concatenate operation is not called with a polygon type. ORA-13338: failure in reversing LRS polygon/collection geometry Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry. Action: Check the geometry type to make sure this operation is called on non-polygon geometries. ORA-13339: LRS polygon clipping across multiple rings Cause: Clipping (dynseg) a polygon across multiple rings is not allowed. Action: Polygon clipping is allowed only for a single ring. ORA-13340: a point geometry has more than one coordinate Cause: A geometry, specified as being a point, has more than one coordinate in its definition. Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, remove the extraneous coordinates from its definition. ORA-13341: a line geometry has fewer than two coordinates Cause: A geometry, specified as being a line, has fewer than two coordinates in its definition. Action: A line must consist of at least two distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. ORA-13342: an arc geometry has fewer than three coordinates Cause: A geometry, specified as being an arc, has fewer than three coordinates in its definition. Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. ORA-13343: a polygon geometry has fewer than four coordinates Cause: A geometry, specified as being a polygon, has fewer than four coordinates in its definition. Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. ORA-13344: an arcpolygon geometry has fewer than five coordinates Cause: A geometry, specified as being an arcpolygon, has fewer than five coordinates in its definition. Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. ORA-13345: a compound polygon geometry has fewer than five coordinates Cause: A geometry, specified as being a compound polygon, has fewer than five coordinates in its definition. Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates respectively. Correct the geometric definition, or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry. ORA-13346: the coordinates defining an arc are collinear Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates. Action: Alter the definition of the arc, or set the SDO_ETYPE or SDO_GTYPE to the line type. ORA-13347: the coordinates defining an arc are not distinct Cause: Two or more of the three points defining an arc are the same. Action: Alter the definition of the arc to ensure that three distinct coordinate values are used. ORA-13348: polygon boundary is not closed Cause: The boundary of a polygon does not close. Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry. ORA-13349: polygon boundary crosses itself Cause: The boundary of a polygon intersects itself. Action: Correct the geometric definition of the object. ORA-13350: two or more rings of a complex polygon touch Cause: The inner or outer rings of a complex polygon touch. Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object. ORA-13351: two or more rings of a complex polygon overlap Cause: The inner or outer rings of a complex polygon overlap. Action: All rings of a complex polygon must be disjoint. Correct the geometric definition of the object. ORA-13352: the coordinates do not describe a circle Cause: The set of coordinates used to describe a circle are incorrect. Action: Confirm that the set of coordinates actually represent points on the circumference of a circle. ORA-13353: ELEM_INFO_ARRAY not grouped in threes Cause: The ELEM_INFO_ARRAY in an SDO_GEOMETRY definition has more or fewer elements than expected. Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3. ORA-13354: incorrect offset in ELEM_INFO_ARRAY Cause: The offset field in ELEM_INFO_ARRAY of an SDO_GEOMETRY definition references an invalid array subscript in SDO_ORDINATE_ARRAY. Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY. ORA-13355: SDO_ORDINATE_ARRAY not grouped by number of dimensions specified Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user. Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY. ORA-13356: adjacent points in a geometry are redundant Cause: There are repeated points in the sequence of coordinates. Action: Remove the redundant point. ORA-13357: extent type does not contain 2 points Cause: Extent type should be represented by two points: lower left and upper right. Action: Confirm that there are only two points for an extent type. ORA-13358: circle type does not contain 3 points Cause: Circle type should be represented by three distinct points on the circumference. Action: Confirm that there are only three points for a circle type. ORA-13359: extent does not have an area Cause: The two points representing the extent are identical. Action: Confirm that the two points describing the extent type are distinct. ORA-13360: invalid subtype in a compound type Cause: This subtype is not allowed within the ETYPE specified. Action: Check the Oracle Spatial documentation for type definitions. ORA-13361: not enough sub-elements within a compound ETYPE Cause: The compound type declare more sub-elements than actually defined. Action: Confirm that the number of sub-elements is consistent with the compound type declaration. ORA-13362: disjoint sub-element in a compound polygon Cause: Compound polygon must describe an enclosed area. Action: Confirm that all sub-elements are connected. ORA-13363: no valid ETYPE in the geometry Cause: None of the ETYPEs within the geometry is supported. Action: Confirm that there is at least one valid ETYPE. ORA-13364: layer dimensionality does not match geometry dimensions Cause: The spatial layer has a geometry with a different dimensions than the dimensions specified for the layer. Action: Make sure that all geometries in a layer have the same dimensions and that they match the dimensions in the SDO_DIM_ARRAY object for the layer in the USER_SDO_GEOM_METADATA view. ORA-13365: layer SRID does not match geometry SRID Cause: The spatial layer has a geometry with a different SRID than the SRID specified for the layer. Action: Make sure that all geometries in a layer have the same SRID and that the SRIDs match the SRID for the layer in the USER_SDO_GEOM_METADATA view. ORA-13366: invalid combination of interior exterior rings Cause: In an Oracle Spatial geometry, interior and exterior rings are not used consistently. Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array. ORA-13367: wrong orientation for interior/exterior rings Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly. Action: Be sure that the exterior rings are oriented counterclockwise and the interior rings are oriented clockwise. ORA-13368: simple polygon type has more than one exterior ring Cause: In a polygon geometry there is more than one exterior ring. Action: Set the type to be multipolygon if more than one exterior ring is present in the geometry. ORA-13369: invalid value for etype in the 4-digit format Cause: A 4-digit etype for a non-polygon type element is used, or the orientation is not a valid orientation for interior/exterior rings of the polygon. Action: Correct the geometry definition. ORA-13370: failure in applying 3D LRS functions Cause: Only non-geodetic 3D line string geometries (made of line segments) are supported for 3D LRS functions. Action: Check the geometry and element types and the SRID values. ORA-13371: invalid position of measure dimension Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in the dim_info_array. Action: Check the geometry"s gtype and its position in the dim_info_array. ORA-13372: failure in modifying metadata for a table with spatial index Cause: Modifying the metadata after the index is created will cause an inconsistency between the geometry"s gtype and diminfo. Action: Modify (or Prepare) metadata before creating an index on the SDO_GEOMETRY column. ORA-13373: invalid line segment in geodetic data Cause: A geodetic line segment was not less than half of a great circle. Action: Densify the line by adding points. ORA-13374: SDO_MBR not supported for geodetic data Cause: The SDO_MBR functionality is not supported for geodetic data. Action: Find an alternative function that can be used in this context. ORA-13375: the layer is of type [string] while geometry inserted has type [string] Cause: The layer has a type that is different or inconsistent with the type of the current geometry. Action: Change the geometry type to agree with the layer type, or change the layer type to agree with the geometry type. ORA-13376: invalid type name specified for layer_gtype parameter Cause: An invalid type name is specified for the layer_gtype constraint. Action: See the Spatial documentation for of valid keywords that can be used in defining a layer_gtype constraint. ORA-13377: invalid combination of elements with orientation Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4-digit etype). Action: Make sure all the polygon elements have orientation specified using the 4-digit etype notation. ORA-13378: invalid index for element to be extracted Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry. Action: Make sure the parameters to the extract function are in the valid range for the geometry. ORA-13379: invalid index for sub-element to be extracted Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry. Action: Make sure the parameters to the extract function are in the valid range for the geometry. ORA-13380: network not found Cause: The specified network was not found in the network metadata. Action: Insert the network information in the USER_SDO_NETWORK_METADATA view. ORA-13381: table:string not found in network:string Cause: The specified table was not found in the network metadata. Action: Insert the table information in the USER_SDO_NETWORK_METADATA view. ORA-13382: geometry metadata (table:string column:string) not found in spatial network:string Cause: The specified geometry metadata was not found in the spatial network metadata. Action: Insert the spatial metadata information in the USER_SDO_NETWORK_METADATA view. ORA-13383: inconsistent network metadata: string Cause: There was an inconsistency between the network metadata and the node/link information. Action: Check the network metadata and the node/link information. ORA-13384: error in network schema: string Cause: The network table(s) did not have required column(s) Action: Check the network schema. ORA-13385: error in network manager: [string] Cause: There was an internal error in network manager. Action: Contact Oracle Customer Support for more help. ORA-13386: commit/rollback operation error: [string] Cause: The index-level changes were not fully incorporated as part of the commit or rollback operation. Action: Correct the specified error and use the following statement: ALTER INDEX PARAMETERS ("index_status=synchronize"); ORA-13387: sdo_batch_size for array inserts should be in the range [number,number] Cause: The specified value for sdo_batch_size was too high or too low. Action: Change the value to be in the specified range. ORA-13388: invalid value for dst_spec parameter Cause: The dst_spec parameter was specified in the wrong format. Action: Check the documentation for this parameter. ORA-13389: unable to compute buffers or intersections in analysis function Cause: There was an internal error in computing the buffers or intersections in the specified spatial analysis function. Action: Modify the tolerance value in the USER_SDO_GEOM_METADATA view before invoking the spatial analysis function. ORA-13390: error in spatial analysis and mining function: [string] Cause: There was an internal error in the specified analysis function. Action: Contact Oracle Customer Support for more help. ORA-13401: duplicate entry for string in USER_SDO_GEOR_SYSDATA view Cause: The RASTER_DATA_TABLE and RASTER_ID columns contained the same information in two or more rows in the USER_SDO_GEOR_SYSDATA view. Action: Ensure that the RASTER_DATA_TABLE and RASTER_ID columns in the USER_SDO_GEOR_SYSDATA view contain the correct information, and that the value pair is unique for each row. ORA-13402: the rasterType is null or not supported Cause: The specified rasterType was null or not supported. Action: Check the documentation for the rasterType number and/or formats supported by GeoRaster. ORA-13403: invalid rasterDataTable specification: string Cause: Each GeoRaster object must have an associated raster data table whose name is unique among raster data table names in the database. If the GeoRaster object is not empty and not blank, the raster data table must exist, be visible in the current schema, be defined in the same schema as the GeoRaster data table, and be an object table of SDO_RASTER type. However, one or more of these requirements were not met. Action: Check the rasterDataTable specification and ensure that all relevant raster data table requirements are met. ORA-13404: invalid ultCoordinate parameter Cause: The ultCoordinate array parameter had the wrong length or contained an invalid value. Action: Check the documentation, and make sure the ultCoordinate parameter is correct. ORA-13405: null or invalid dimensionSize parameter Cause: The dimensionSize array parameter was null, had the wrong length, or contained an invalid value. Action: Check the documentation, and make sure the dimensionSize parameter is correct. ORA-13406: null or invalid GeoRaster object for output Cause: The GeoRaster object for output was null or invalid. Action: Make sure the GeoRaster object for output has been initialized properly. ORA-13407: invalid storage parameter Cause: The storage parameter contained an invalid specification. Action: Check the documentation, and make sure the storage parameter is correct. ORA-13408: invalid blockSize storage parameter Cause: The blockSize storage parameter had the wrong length or contained invalid value. Action: Check the documentation, and make sure the blockSize storage parameter is correct. ORA-13409: null or invalid pyramidLevel parameter Cause: The specified pyramidLevel parameter was null or invalid. Action: Make sure the pyramidLevel parameter specifies a valid pyramid level value for the GeoRaster object. ORA-13410: invalid layerNumbers or bandNumbers parameter Cause: The layerNumbers or bandNumbers parameter was invalid. Action: Check the documentation and make sure the layerNumbers or bandNumbers parameter is valid. ORA-13411: subset results in null data set Cause: The intersection of cropArea and source GeoRaster object was null. Action: Check the documentation, and make sure the cropArea parameter is correct. ORA-13412: invalid scale parameter Cause: The scale parameter was invalid. Action: Check the documentation, and make sure the scale parameter is correct. ORA-13413: null or invalid resampling parameter Cause: The resampling parameter was null or invalid. Action: Check the documentation, and make sure the resampling parameter is correct. ORA-13414: invalid pyramid parameter Cause: The pyramid parameter was invalid. Action: Check the documentation, and make sure the pyramid parameter is correct. ORA-13415: invalid or out of scope point specification Cause: The point position specified by the or parameter combination was invalid or out of scope. Action: Make sure the parameter(s) specify a valid point that is or can be translated into a cell position inside the cell space of the GeoRaster object. ORA-13416: invalid geometry parameter Cause: The geometry parameter did not specify a valid single-point geometry. Action: Specify a valid single-point geometry. ORA-13417: null or invalid layerNumber parameter Cause: The layerNumber parameter was null or out of scope. Action: Specify a valid layerNumber parameter. ORA-13418: null or invalid parameter(s) for set functions Cause: A parameter for set metadata operations was null or invalid. Action: Check the documentation for information about the parameters. ORA-13419: cannot perform mosaick operation on the specified table column Cause: An attempt to perform a mosaick operation failed because the GeoRaster objects in the specified table column did not meet necessary conditions. Action: Check the documentation for SDO_GEOR.Mosaick for details. ORA-13420: the SRID of the geometry parameter was not null Cause: The input geometry must be in the GeoRaster cell space, which has a null SRID value. Action: Make sure the geometry parameter has a null SRID. ORA-13421: null or invalid cell value Cause: The cell value was null or out of scope. Action: Make sure the cell value is not null and is in the range as designated by the cellDepth of the specified GeoRaster object. ORA-13422: invalid model coordinate parameter Cause: The model coordinate array parameter had the wrong length or had null ordinate element(s). Action: Make sure the model coordinate parameter is valid. ORA-13423: invalid cell coordinate parameter Cause: The cell coordinate array parameter had the wrong length or had null ordinate element(s). Action: Make sure the cell coordinate parameter is valid. ORA-13424: the GeoRaster object is not spatially referenced Cause: The GeoRaster object was not spatially referenced. Action: Make sure the GeoRaster object is spatially referenced. ORA-13425: function not implemented Cause: This specific function was not implemented. Action: Do not use the function that causes this error. ORA-13426: invalid window parameter for subset operation Cause: The specified window parameter was invalid. Action: Specify a valid window parameter. Check the documentation for details. ORA-13427: invalid BLOB parameter for output Cause: The specified output BLOB parameter was invalid. Action: Make sure the output BLOB parameter is initialized properly. ORA-13428: invalid modelCoordinateLocation Cause: The program [or user] specified a modelCoordinateLocation that is not supported, or the modelCoordinateLocation of the GeoRaster object was wrong. Action: Set or specify the modelCoordinateLocation to be CENTER (0) or UPPERLEFT (1). ORA-13429: invalid xCoefficients or yCoefficients parameter(s) Cause: An attempt to perform a georeference operation failed. Possible reasons include xCoefficients or yCoefficients having the wrong number of coefficients or invalid coefficients. Action: Check the documentation for supported coefficient specifications. ORA-13430: the GeoRaster object has null attribute(s) Cause: The metadata or rasterType of the GeoRaster object was null. Action: This object may only be used as an output parameter of procedures or functions. It is not valid for other purposes. ORA-13431: GeoRaster metadata rasterType error Cause: The rasterType in the metadata of the GeoRaster object was inconsistent with the GeoRaster rasterType attribute. Action: Make sure the rasterType in the metadata of the GeoRaster object and the GeoRaster rasterType attribute have the same value. ORA-13432: GeoRaster metadata blankCellValue error Cause: The blankCellValue specification could not be found in the metadata of a blank GeoRaster object. Action: Add blankCellValue to the metadata whenever isBlank is true. ORA-13433: GeoRaster metadata default RGB error Cause: At least one of the defaultRed, defaultGreen, and defaultBlue values (logical layer numbers) was zero, negative, or out of range. Action: Check the documentation for details. ORA-13434: GeoRaster metadata cellRepresentation error Cause: The cellRepresentation type was not supported. Action: Check the documentation for supported cellRepresentation types. ORA-13435: GeoRaster metadata dimension inconsistent Cause: The specification of dimensions or totalDimensions was inconsistent with rasterType, or vice versa. Action: Make sure dimension specifications are consistent. ORA-13436: GeoRaster metadata dimensionSize error Cause: Either the dimensionSize for each dimension was not specified, or an extraneous dimensionSize was specified. Action: Add a dimsenionSize for each dimension of the GeoRaster object and delete extra dimensionSize elements. ORA-13437: GeoRaster metadata blocking error Cause: Either the wrong block number(s) or block size(s) along dimensions were specified, or the block numbers and sizes when taken together were not consistent. Action: Check the documentation for details. ORA-13438: GeoRaster metadata pyramid type error Cause: The specified pyramid type was not supported. Action: Check the documentation for supported pyramid types. ORA-13439: GeoRaster metadata pyramid maxLevel error Cause: The specified maxLevel exceeded the maximum level allowed by the specified pyramid type. Action: Check the documentation for supported pyramid types and their total level limitations. ORA-13440: GeoRaster metadata compression type error Cause: The specified compression type was not supported. Action: Check the documentation for supported compression types. ORA-13441: GeoRaster metadata SRS error Cause: The referenced GeoRaster object had no defined polynomial referencing model. Action: Define or generate the polynomialModel, or set isReferenced to FALSE. ORA-13442: GeoRaster metadata SRS error Cause: The polynomialModel did not match the supported number of variables. Action: Check the documentation for supported number of variables in the polynomialModel specification. ORA-13443: GeoRaster metadata SRS error Cause: The polynomialModel specification had an incorrect pType value. Action: Check the documentation for supported polynomial types. ORA-13444: GeoRaster metadata SRS error Cause: The polynomialModel specification had the wrong number of coefficients. Action: Check the documentation for the required number of coefficients under different conditions. ORA-13445: GeoRaster metadata SRS error Cause: The polynomialModel specification had a zero denominator. Action: Make sure the denominator of the polynomialModel specification is not zero. ORA-13446: GeoRaster metadata TRS error Cause: The GeoRaster Temporal Reference System was not supported. Action: Set isReferenced to FALSE. ORA-13447: GeoRaster metadata BRS error Cause: The GeoRaster Band Reference System was not supported. Action: Set isReferenced to FALSE. ORA-13448: GeoRaster metadata BRS error Cause: The GeoRaster spectral extent specification was incorrect. Action: The MIN value must be less than the MAX value in the spectralExtent element. ORA-13449: GeoRaster metadata ULTCoordinate error Cause: The GeoRaster rasterInfo ULTCoordinate was not correct. Action: Check the documentation for restrictions. ORA-13450: GeoRaster metadata layerInfo error Cause: The GeoRaster had more than one layerInfo element, or the layerDimension value was not supported. Action: The current release only supports one layerInfo element; layer can only be defined along one dimension, and this dimension must be BAND. ORA-13451: GeoRaster metadata scaling function error Cause: The scaling function had a zero denominator. Action: Make sure the scaling function denominator is not zero. ORA-13452: GeoRaster metadata BIN function error Cause: The bin function data did not match its type. Action: For EXPLICIT type, provide a binTableName element; otherwise, provide a binFunctionData element. ORA-13453: GeoRaster metadata layer error Cause: Too many subLayers were defined for the GeoRaster object, or layerNumber or layerDimensionOrdinate was not assigned correctly. Action: The total number of logical layers cannot exceed the total number of physical layers, and each logical layer must be assigned a valid physical layer number following the same order. Check the documentation for more details. ORA-13454: GeoRaster metadata is invalid Cause: The GeoRaster metadata was invalid against its XML Schema. Action: Run the schemaValidate routine to find the errors. ORA-13455: GeoRaster metadata TRS error Cause: The beginDateTime value was later than the endDateTime value. Action: Make sure that the beginDateTime value is not later than the endDateTime value. ORA-13456: GeoRaster cell data error Cause: There was error in the GeoRaster cell data. Action: The GeoRaster object is invalid. ORA-13457: GeoRaster cell data error Cause: There was error in the cell data of the pyramids. Action: Delete the pyramids and re-generate them. ORA-13458: GeoRaster metadata SRS error Cause: The polynomial model did not match the requirements of a rectified GeoRaster object. Action: Check the documentation for the requirements of the polynomial model for a rectified GeoRaster object, or set isRectified to be false. ORA-13459: GeoRaster metadata SRS error Cause: The polynomial model was not an six-parameter transformation, or the six-parameter transformation was not valid. Action: Check the documentation and make sure the polynomial model is a valid six-parameter affine transformation. ORA-13460: GeoRaster metadata SRS error Cause: The referenced GeoRaster object had a zero model space SRID or the specified model space SRID was zero. Action: Set or specify the model space SRID to be a nonzero number. ORA-13461: the interleaving type is not supported Cause: The interleaving type of the GeoRaster object was not supported. Action: Check the documentation for the interleaving types supported by GeoRaster. Use SDO_GEOR.changeFormat to transform the image to a supported interleaving type. ORA-13462: invalid blocking specification Cause: The specified blocking configuration was invalid. Action: Block size must always be a power of 2. ORA-13463: error retrieving GeoRaster data: string Cause: An internal error occurred while retrieving GeoRaster data from the database. Action: Check the error message for details. ORA-13464: error loading GeoRaster data: string Cause: An internal error occurred while loading GeoRaster data into the database. Action: Check the error message for details. ORA-13465: null or invalid table or column specification Cause: The specified table or column did not exist, or the column was not a GeoRaster column. Action: Make sure the specified table exists and the specified column is a GeoRaster column. ORA-13466: format not appropriate for specified compression method Cause: The operation failed because the GeoRaster object had an inappropriate type or format for the specified compression method. The GeoRaster type or format is not supported by the specified compression. Action: Check the documentation for the appropriate GeoRaster types and formats for each compression method. Use SDO_GEOR.changeFormat to transform the GeoRaster object to an appropriate format, or apply another compression method. ORA-13467: unsupported GeoRaster metadata specification: string Cause: The GeoRaster metadata specification is not supported. Action: Check the documentation for the supported GeoRaster metadata specifications. ORA-13480: the Source Type is not supported Cause: The specified source type was not supported. Action: Check the documentation for the source types (such as FILE and HTTP) supported by GeoRaster. ORA-13481: the destination type is not supported Cause: The specified destination type was not supported. Action: Check the documentation for the destination types (such as FILE) supported by GeoRaster. ORA-13482: GeoRaster object is not initialized for the image Cause: No GeoRaster object has been initialized for the specified image. Action: Initialize a GeoRaster object to hold this image before loading it into the database. Check the documentation for details. ORA-13483: insufficient memory for the specified GeoRaster data Cause: There was insufficient memory to hold the specified GeoRaster data for this operation. Action: Use SDO_GEOR.subset to isolate a subset of the GeoRaster data, or reblock the GeoRaster data into smaller sized blocks. Check the documentation for details. ORA-13484: the file format and/or compression type is not supported Cause: The file format and/or compression type was not supported. Action: Check the documentation for formats that are currently supported by GeoRaster. ORA-13485: error occurred during compression or decompression: string Cause: The operation could not be completed because an error occurred during compression or decompression. Check the error message for details. Action: Check that the GeoRaster object is valid, that its metadata is valid for the specified compression format, and that valid parameters are passed into the compression or decompression operation. ORA-13497: %s Cause: This is an internal GeoRaster error. Action: Contact Oracle Support Services. You may want to make sure the GeoRaster object is valid before you do so. ORA-13498: %s Cause: An error related to an external plugin was encountered in the GeoRaster component. Action: Check the documentation for the external plugin, or contact the plugin provider and supply the exact error text. ORA-13499: %s Cause: This is an internal Spatial error. Action: Contact Oracle Support Services. ORA-13500: SYSAUX DATAFILE clause specified more than once Cause: The CREATE DATABASE command contains more than one SYSAUX DATAFILE clause. Action: Specify at most one SYSAUX DATAFILE clause. ORA-13501: Cannot drop SYSAUX tablespace Cause: Tried to drop SYSAUX tablespace Action: None ORA-13502: Cannot rename SYSAUX tablespace Cause: An attempt to rename the SYSAUX tablespace failed. Action: No action required. ORA-13503: Creating SYSAUX tablespace with invalid attributes Cause: An attempt to create the SYSAUX tablespace with invalid attributes. Action: Create SYSAUX tablespace with ONLINE, PERMANENT, EXTENT MANAGEMENT LOCAL, SEGMENT SPACE MANAGEMENT AUTO attributes. ORA-13504: No SYSAUX datafile clause specified Cause: If Create Database has the datafile clause, then SYSAUX datafile clause has to be specified, unless using OMF. Action: Specify the SYSAUX datafile clause. ORA-13505: SYSAUX tablespace can not be made read only Cause: Attempting to set the SYSAUX tablespace to read only. The SYSAUX tablespace must remain read write for database operation. Action: Leave SYSAUX tablespace read write. ORA-13506: operation failed due to invalid snapshot range (string, string) Cause: An attempt was made to perform operation with an invalid Start/End Snapshot Pair. Action: Choose a valid Start/End Snapshot Pair. ORA-13509: error encountered during updates to a AWR table Cause: An update error occurred during OCI operation due to an underlying error. Action: Check associated OCI error. Correct problem and retry the operation. ORA-13510: invalid RETENTION string, must be in the range (string, string) Cause: The user has specified a RETENTION setting that is not in the supported range of (MIN, MAX). Action: Choose a valid RETENTION setting and retry the operation. ORA-13511: invalid INTERVAL string, must be in the range (string, string) Cause: The user has specified a INTERVAL setting that is not in the supported range of (MIN, MAX). Action: Choose a valid INTERVAL setting and retry the operation. ORA-13514: Metric Capture too close to last capture, group string Cause: The metric capture cannot be executed because it is too close to the last capture (within 1 centi-second). Action: add some delay and reissue command to retry. ORA-13515: Error encountered during Database Usage Statistics capture Cause: Error occurred during OCI operation due to underlying error. Action: Check associated OCI error. Correct problem and retry the operation. ORA-13516: AWR Operation failed: string Cause: The operation failed because AWR is not available. The possible causes are: AWR schema not yet created; AWR not enabled; AWR schema not initialized; or database not open or is running in READONLY or STANDBY mode. Action: check the above conditions and retry the operation. ORA-13517: Baseline (id = string) does not exist Cause: The operation failed because the specified baseline ID does not exist in the Workload Repository. Action: check the baseline id and retry the operation. ORA-13518: Invalid database id (string) Cause: The operation failed because the specified database ID does not exist in the Workload Repository. Action: check the database id and retry the operation. ORA-13519: Database id (string) exists in the workload repository Cause: The operation failed because the specified database ID already exists in the Workload Repository. Action: check the database id and retry the operation. ORA-13520: Database id (string) not registered, Status = string Cause: The operation failed because the specified database ID was not registered in the Workload Repository properly. Action: check the status of database id and retry the operation. ORA-13521: Unregister operation on local Database id (string) not allowed Cause: The operation failed because the local database ID cannot be unregistered from the Workload Repository. Action: check the database id and retry the operation. ORA-13523: unable to allocate required space for return type Cause: Out of memory to allocate the space for the return variable for an external procedure. Action: Try operation again. ORA-13524: error encountered while retrieving baseline information Cause: A read error occurred during the OCI operation to retrieve the baseline information Action: Check associated error. Correct problem and retry the operation. ORA-13525: error with computing space usage for sysaux occupant Cause: Error occurred during OCI operation due to underlying error. Action: Check associated OCI error. Correct problem and retry the operation. ORA-13526: baseline (string) does not exist Cause: The operation failed because the specified baseline name does not exist in the Workload Repository. Action: check the baseline name and retry the operation. ORA-13527: invalid baseline name Cause: The operation failed because the specified baseline name does not exist in the Workload Repository. Action: check the baseline name and retry the operation. ORA-13528: name (string) is already used by an existing baseline Cause: The operation failed because the specified baseline name already exists in the Workload Repository. Action: check the baseline name and retry the operation. ORA-13529: Error occurred when flushing AWR table group Cause: An error occurred during the flushing of a table group. Because of the error in the group, we are unable to flush this table. Action: Check the error associated with the table group. ORA-13530: invalid TOPNSQL string, must be in the range (string, string) Cause: The user has specified a TOPNSQL setting that is not in the supported range of (MIN, MAX). Action: Choose a valid TOPNSQL setting and retry the operation. ORA-13600: error encountered in Advisor string Cause: An error occurred in the Advisor. This message will be followed by a second message giving more details about the nature of the error. Action: See the Advisor documentation for an explanation of the second error message. ORA-13601: The specified Advisor string does not exist. Cause: The user specified an advisor name that has not be defined in the advisor repository. Action: Correct the advisor name and retry the operation. ORA-13602: The specified parameter string is not valid for task or object string. Cause: The user attempted to access a task parameter that does not exist for the specified advisor object. The parameter may be misspelled or the user has selected a parameter that is not supported by the particular advisor. Action: Validate the parameter name and retry the operation. ORA-13603: The specified parameter string cannot be fetched as a numeric value for task or object string. Cause: The user attempted to retrieve a string parameter as a numeric value. Action: Check the datatype for the task parameter and retry the operation. ORA-13604: The specified parameter string cannot be fetched as a SQL table. Cause: The user attempted to retrieve a non-table parameter as a table name. Action: Check the datatype for the task parameter and retry the operation. ORA-13605: The specified task or object string does not exist for the current user. Cause: The user attempted to reference an advisor task or object using a name that does not exist in the Advisor repository. Action: Adjust the name and retry the operation. ORA-13606: the specified task parameter element string is out of range for parameter string. Cause: The user attempted to reference an invalid parameter element. Action: Adjust the element offset and retry the operation. ORA-13607: The specified task or object string already exists Cause: The user attempted to create the specified task or object using a name that already exists in the Advisor repository. Task names must be unique to the database user. Action: Adjust the name and retry the operation. ORA-13608: The task or object name string is invalid. Cause: The user attempted to specify a task name that contains invalid characters or an invalid wildcard specifier. Action: Adjust the name and retry the operation. ORA-13609: The specified task string must be executing to be cancelled or interrupted. Cause: The user attempted to cancel or interrupt a task that is not currently executing. Action: Check the status of the task and retry the operation. ORA-13610: The directive string does not exist for task string. Cause: The user attempted to access a task directive that does not exist. Action: Validate the directive and retry the operation. ORA-13611: The command string is not a valid advisor command. Cause: The user attempted to specify a command that does not exist. Action: Validate the command and retry the operation. ORA-13612: The recommendation action string,string is not valid for task string. Cause: The user attempted to access a recommendation action that does not exist in the task. Action: Validate the recommendation-action and retry the operation. ORA-13613: The requested operation is not supported for this advisor object. Cause: The user attempted to perform an operation that is not supported for the particular advisor or task type. Action: Validate the task or object and retry the operation. ORA-13614: The template string is not compatible with the current advisor. Cause: The user attempted to create a new task or object using an existing task or object that was not created by the same advisor. Action: Validate the template and retry the operation. ORA-13615: The task or object string is greater than the maximum allowable length of 30 characters. Cause: The user attempted to create a new task or object using a name that is too long. Action: Shorten the name and retry the operation. ORA-13616: The current user string has not been granted the ADVISOR privilege. Cause: The user attempted an advisor operation that requires privilege. Action: Adjust the user"s privileges and retry the operation. ORA-13617: The specified task string already executing Cause: The user attempted to execute a task that is currently executing. Action: Wait for the task to finish before attempting any further task activities. ORA-13618: The specified value is not a valid value for procedure argument string. Cause: The user executed a procedure but failed to provide correct values for the argument. Action: Correct the procedure arguments and retry the operation. ORA-13619: The procedure argument string is greater than the maximum allowable length of string characters. Cause: The user attempted to pass a character argument that is too long. Action: Shorten the specified character argument and retry the operation. ORA-13620: The task or object string is read-only and cannot be deleted or modified. Cause: The user attempted to perform an operation that will update or delete a read-only task or object. Action: Adjust the READ_ONLY property for the object and retry the operation. ORA-13621: The task_or object string is marked as a template and cannot perform the requested operation. Cause: The user attempted perform an unsupported operation on a task or object that is identified as a template. Action: Choose a different object and retry the operation. ORA-13622: invalid recommendation annotation Cause: The user attempted to mark a recommendation using an invalid annotation. Valid annotation actions are ACCEPT, REJECT and IGNORE. Action: Correct the action and retry the operation. ORA-13623: The recommendation string is not valid for task string. Cause: The user attempted to access a recommendation that does not exist in the task. Action: Validate the recommendation and retry the operation. ORA-13624: The task string is executing and cannot be deleted or modified. Cause: The user attempted to access a task that currently executing. Action: Wait for the task to complete and retry the operation. ORA-13625: %s is an invalid advisor object type. Cause: The user has specified an invlaid object type. Action: Refre to dba_advisor_object_types for all valid object types ORA-13626: The specified object string is not valid for task string. Cause: The user specified an non-existent object for the task Action: Choose a different object and retry the operation. ORA-13627: Setting of parameter string is disallowed until the task is reset. Cause: The user attempted to set the value of a parameter before the task was reset. This parameter cannot be changed until the task is reset. Action: Reset the task and retry the operation. ORA-13628: Insufficient privileges to access the task belonging to the specified user Cause: The user could not access dba_* views. Action: Retry operation as owner of the task or after granting new privileges. ORA-13629: The task or object string is being used by another operation. Cause: The user attempted to access a task or object that is locked by another session. Action: Wait for the task or object activity to complete and retry the operation. ORA-13630: The task string contains execution results and cannot be executed. Cause: The user attempted to execute a task that already contains execution results. Action: Reset the task to its initial state and retry the operation. ORA-13631: The task string contains no execution results. Cause: The user attempted to create a report or script from a task that has not successfully completed an execution. Action: Execute the task and then retry the operation ORA-13632: The user cancelled the current operation. Cause: The user signaled a cancel during a task or object operation. Action: None ORA-13633: The task string was interrupted and needs to be resumed. Cause: The user attempted to execute a task that was interrupted. Action: Resume the execution of the task via the RESUME_TASK API. ORA-13634: The task string needs to be reset before being re-executed. Cause: The task must be in an inital state to be executed. Action: Reset the task to its initial state and retry the operation. ORA-13635: The value provided for parameter string cannot be converted to a number. Cause: A numeric parameter was incorrectly supplied in string form. Action: Retry by supplying valid numeric value. ORA-13636: The specified value provided for parameter string is not valid for this advisor. Cause: The user supplied an invalid parameter value. Action: Retry by supplying valid value. ORA-13637: Executing or modifying task string is disallowed until the task is reset to its initial state. Cause: The user attempted to execute or modify the task that is in not in its INITIAL state. Action: Reset the task and retry the operation. ORA-13638: The user interrupted the current operation. Cause: The user signaled an interrupt during a task or object operation. Action: None ORA-13639: The current operation was interrupted because it timed out. Cause: The task or object operation timed out. Action: None ORA-13640: The current operation was cancelled because it timed out, and was not in interruptible mode. Cause: The task or object operation timed out. Action: None ORA-13641: Task cannot be interrupted yet. You may cancel it instead. Cause: The user attempted to interrupt a task that has not reached interruptible mode. Action: Wait until the task reaches interruptible mode, or cancel the task execution. ORA-13642: The specified string string provided for string cannot be converted to a date. The acceptable date format is string. Cause: The user supplied a date value in an incorrect format. Action: Retry by supplying valid value. ORA-13643: The task can not be interrupted or cancelled. Cause: Request to interrupt or cancel task execution can not be granted because the task has not reached the appropriate mode. Action: User should wait for a few seconds and try again. ORA-13644: The user "string" is invalid. Cause: Invalid user name specified to advisor framework Action: User should specify a correct, case-sensitive, name ORA-13699: Advisor feature is not currently implemented. Cause: The user attempted to execute an unsupported advisor operation. Action: Verify the availability of the operation. ORA-13701: Snapshot pair [string, string] seems to be specified in reverse order. Cause: The start snapshot id was greater than the end snapshot id. Action: Swap the start and end snapshot ids. ORA-13702: Snapshot IDs specified by the range [string, string] are equal. Cause: The start snapshot id and end snapshot id were identical. Action: Provide different start and end snapshot ids. ORA-13703: The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository. Cause: The snapshot ids or the database id or the instance id was invalid or the specified snapshots have already been purged. Action: Set valid snapshot ids and retry. ORA-13704: Invalid value "string" specified for parameter "string". Cause: The parameter was not set before executing the ADDM. Action: Set the parameter to a valid value and retry. ORA-13705: There was a instance shutdown/startup between the snapshots in the range [string, string]. Cause: Instance was shut down and restarted between the two specified snapshots. Action: Specify start and end snapshot ids that does not have a shutdown/startup in between them. ORA-13706: Invalid value "string" specified for parameter "string" in "string" analysis mode. Cause: The parameter was not set to an acceptable value for this particular mode of analysis. Action: Set the parameter to a valid value and retry. ORA-13707: Either the start snapshot string or the end snapshot string is incomplete or missing key statistics. Cause: Either the start or the end snaphots was missing or purged or had encountered errors while creating them. Action: Verify that AWR is done taking these two snapshots, or Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the start/end snapshots. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that has valid start and end snapshots. ORA-13708: Some snapshots in the range [string, string] were purged before the analysis was complete. Cause: One or both of the snapshots have been purged from AWR. Action: Verify that the AWR auto purging is not trying to purge these snapshots and re-run ADDM. ORA-13709: Required parameter "string" must be set before execution. Cause: The parameter needs to be set before running the ADDM Action: Set the parameter to a valid value and retry. ORA-13710: Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively. Cause: Invalid interaction between two parameter values. Action: Set at least one of the values so the value of the first parameter is higher than the value of the second parameter. ORA-13711: Some snapshots in the range [string, string] are missing key statistics. Cause: Some AWR tables encountered errors while creating one or more snapshots in the given range. The data present in one or more of these missing tables is necessary to perform an ADDM analysis. Action: Look in DBA_HIST_SNAP_ERROR to find what tables are missing in the given snapshot range. Use the ERROR_NUMBER column in that view together with the alert log to identify the reason for failure and take necessary action to prevent such failures in the future. Try running ADDM on a different snapshot range that does not include any incomplete snapshots. ORA-13712: Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string". Cause: ADDM analysis can only be performed on AWR snapshots taken in the current release. Action: One can still generate AWR and ASH reports using ?/rdbms/admin/awrrpt and ?/rdbms/admin/ashrpt on these snapshots to analyze the data in them. ORA-13750: User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege. Cause: The user attempted an SQL Tuning Set operation that requires a specific privilege. Action: Adjust the user"s privileges and retry the operation. ORA-13751: "SQL Tuning Set" "string" does not exist for owner "string" or user "string" does not have permission to access the "SQL Tuning Set". Cause: The user attempted to access a SQL Tuning Set that does not exist or the user does have permission to access the SQL Tuning Set Action: Check the existence of the "SQL Tuning Set" or adjust the user"s privileges and retry the operation. ORA-13752: User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege. Cause: The attempted to create a SQL Tuning Set in another schema without having the right privilege. Action: Connect as SYS or adjust the user"s privilege and retry the operation. ORA-13753: "SQL Tuning Set" "string" already exists for user "string". Cause: The user attempted to create a "\SQL Tuning"\ Set using a name that already exists for that owner. Action: Change the name of the SQL Tuning Set and retry the operation. ORA-13754: "SQL Tuning Set" "string" does not exist for user "string". Cause: The user attempted to access a SQL Tuning Set that does not exist. Action: Check the speelling of the SQL Tuning Set name and retry the operation. ORA-13755: invalid "SQL Tuning Set" name Cause: The user attempted to specify a SQL Tuning Set name that is invalid. A name must not contain wildcards and its length must be less than 30 characters. Action: Adjust the name and retry the operation. ORA-13756: Cannot update attribute "string". Cause: The user attempted to update an attribute element that cannot be modified. The only string attributes that can be updated are MODULE, ACTION, PARSING_SCHEMA_NAME, PRIORITY, and OTHER. Action: Adjust the attribute name and retry the operation. ORA-13757: "SQL Tuning Set" "string" owned by user "string" is active. Cause: The user attempted to update an active SQL Tuning Set. Action: Remove all reference to the SQL Tuning Set and retry the operation. ORA-13758: "SQL Tuning Set" "string" owned by user "string" is in use. Cause: The user attempted to modify a SQL Tuning Set or to add a reference to a SQL Tuning Set which is in use. Action: Wait until the end of the previous operation and retry. ORA-13759: User "string" cannot remove reference "string". Cause: The user attempted to remove a SQL Tuning Set reference that does not exist. The user might not own the reference. Action: Check the reference ID and the reference owner and retry the operation. ORA-13761: invalid filter Cause: The user attempted to select data from a data source using an invalid filter. A filter is a WHERE clause on data source content. Action: Correct the filter and retry the operation. ORA-13762: The string ranking measure is invalid. Cause: The user attempted to select data from a data source using an invlaid ranking measure. A ranking measure must represent a valid numerical expression. Action: Correct the ranking measure and retry the operation. ORA-13763: illegal ranking attribute "string" Cause: The user attempted to use an attribute element that is not allowed in a ranking meseare. Action: Check the attribute in the ranking meseare and retry the operation. ORA-13764: Value "string" is illegal as a result percentage. Cause: The user attempted to select data from a SQL Tuning Set using an invalid result percentage. The result percentage must be between 0 and 1. Action: Correct the result percentage value and retry the operation. ORA-13765: Value "string" is illegal for a result limit. Cause: The user attempted to select data from a SQL Tuning Set using an invalid result limit. A result limit must be a positive interger. Action: Correct the result limit value and retry the operation. ORA-13766: A ranking measure is required. Cause: The user attempted to select data from a SQL Tuning Set using a percentage argument without specifying a ranking measure. Action: Add a ranking measure or remove the percentage argument and retry the operation. ORA-13767: End snapshot ID must be greater than or equal to begin snapsho ID. Cause: The user attempted to select data from the workload repository using an invalid snaphot ID range. Action: Adjust the snapshot ID range and retry the operation. ORA-13768: Snapshot ID must be between string and string. Cause: The user attempted to select data from the workload repository using a snaphot ID which does not exist. Action: Adjust the snapshot ID and retry the operation. ORA-13769: Snapshots string and string do not exist. Cause: The user attempted to select data from the workload repository using snapshots that do not exist. Action: Check the snapshot identifiers and retry the operation. ORA-13770: Baseline "string" does not exist. Cause: The user attempted to access a baseline that does not exsit. Action: Check the speelling of the baseline name and retry the operation. ORA-13771: cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string" Cause: Unexpected error from DBMS_LOCK.REQUEST. Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services. ORA-13772: unexpected deadlock on "SQL Tuning Set" "string" owned by user "string" Cause: Unexpected error from DBMS_LOCK.REQUEST Action: This error should not normally occur. Check your system for anomalies and retry the operation. If this error persists, contact Oracle Support Services. ORA-13773: insufficient privileges to select data from the cursor cache Cause: The user attempted to perform an operation without having the appropriate privileges on V$SQL and V$SQL_BIND_CAPTURE. Action: Adjust the user"s privileges and retry the operation. ORA-13774: insufficient privileges to select data from the workload repository Cause: The user attempted to perform an operation without having the appropriate privileges on views DBA_HIST_BASELINE, DBA_HIST_SQLTEXT, DBA_HIST_SQLSTAT, DBA_HIST_SQLBIND, DBA_HIST_OPTIMIZER_ENV, and DBA_HIST_SNAPSHOT. Action: Adjust the user"s privileges and retry the operation. ORA-13775: inconsistent datatype in input cursor Cause: The user attempted to load a SQL Tuning Set using an invalid input cursor. All rows in the cursor must match type SQLSET_ROW. Action: Check the rows type in the cursor and retry the operation. ORA-13776: User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views. Cause: The user attempted to read a SQL tuning set belonging to someone else without having SELECT privilege on the DBA views Action: User should be granted the privilege or only access his own STS ORA-13777: invalid list of attribute names Cause: The user specified an attribute element that is not valid. The only attributes that can be selected are NULL, BASIC, TYPICAL, ALL or a comma separated list of the names including EXECUTION_STATISTICS, OBJECT_LIST, BIND_LIST and SQL_PLAN. Action: Adjust the attribute list and retry the operation. ORA-13778: no new name or owner specified for "SQL Tuning Set" Cause: The user attempted to call remap_stgtab_sqlset without specifying either a new SQL tuning set name or a new SQL tuning set owner Action: Specify at least one or the other argument as non-NULL ORA-13779: invalid load option Cause: The user attempted to call load_sqlset with a load option that is different than INSERT, UPDATE and MERGE. Action: Adjust the load option and retry the operation. ORA-13780: SQL statement does not exist. Cause: The user attempted to tune a SQL statement that does not exist. Action: Verify the sql_id and the plan hash value of the statement and retry the operation. ORA-13783: invalid tuning scope Cause: The user attempted to specify a tuning task scope that is invalid. The possible values are LIMITED or COMPREHENSIVE. Action: Check the scope value and retry the operation. ORA-13784: cannot accept SQL profiles for all statements in the "SQL Tuning Set" Cause: The user attempted to accept SQL profiles for all statements in a SQL Tuning Set. Action: Provide the object identifier corresponding to a statement in the SQL Tuning Set and retry the operation. ORA-13785: missing target object for tuning task "string" Cause: The user attempted to perform an operation on a task without specifying a target object or by using an invalid object identifier. Action: Check the identifier of the object and retry the operation. ORA-13786: missing SQL text of statement object "string" for tuning task "string" Cause: The user attempted to accept SQL profile for an object that has not a SQL text associated to it. Action: Check the identifier of the object and retry the operation. ORA-13787: missing SQL profile for statement object "string" for tuning task "string" Cause: The user attempted to accept a SQL profile for an object that has not a SQL profile associated to it. Action: Check the identifier of the object and retry the operation. ORA-13788: invalid recommendation type Cause: The user passed an invalid recommendation type in the rec_type argument to script_tuning_task. Possible values are ALL or any subset of a comma-separated list of PROFILES, STATISTICS and INDEXES. Action: Check the rec_type arg and retry the operation. ORA-13789: invalid process action Cause: The user passed an invalid action to process a SQL statement. Possible value is any subset of a comma-seperated list of EXECUTE and EXPLAIN_PLAN. Action: Check the action argument and retry the operation. ORA-13790: invalid value for time limit Cause: The user passed an invalid value for the time limit argument. Action: Check the argument specified value and retry the operation. ORA-13791: cannot resume a tuning task created to tune a single statement Cause: The user attempted to resume a tuning task that was created to tune a single SQL statement. A task can be resumed only if it is used to tune a SQL Tuning Set. Action: No action required. ORA-13797: invalid SQL Id specified, string Cause: Invalid SQL Id specified for conversion. Action: Specify valid SQL Id. ORA-13798: Parameter string cannot be NULL. Cause: A call to GET_THRESHOLD procedure was made without a required parameter. Action: Specify a valid value for this parameter. ORA-13799: threshold not found Cause: No threshold was found with the specified threshold key. Action: No action required. ORA-13800: concurrent DDL failure on SQL repository objects Cause: A SQL repository object was the target of two concurrent DDL operations. Action: Check the current state of the object and retry the operation that failed. ORA-13801: invalid value for SQLTUNE_CATEGORY parameter Cause: An invalid Oracle identifier was used as the value of the parameter. Action: Specify the parameter conforming to the rules for Oracle identifiers. ORA-13802: failed to purge SQL Tuning Base entry from sql$ Cause: An error occured while try to delete a SQL Tuning Base object. Action: Look at the underlying error(s) on the error stack. ORA-13825: missing SQL statement text for create SQL profile Cause: No SQL text was provided to the create SQL profile operation. Action: Retry with properly specified SQL text. ORA-13826: empty SQL profile not allowed for create or update SQL profile Cause: No attributes were specified to the create SQL profile operation. Action: Retry with at least one hint specified. ORA-13827: null or zero length attribute specified in SQL profile collection Cause: One of the attributes within the SQL profile was not properly specified. Action: Retry with a fully specified SQL profile. ORA-13828: generated SQL profile name string already exists Cause: A SQL profile already exists with the name generated by the system. Action: Retry the operation as the generated name is time sensitive. ORA-13829: SQL profile named string already exists Cause: A SQL profile already exists with the name specified. Action: Specify a different name or drop the existing SQL profile. ORA-13830: SQL profile with category string already exists for this SQL statement Cause: A SQL profile already exists for the given SQL statement and category. Action: Drop or update the existing SQL profile. ORA-13831: SQL profile name specified is invalid Cause: An invalid SQL profile name was specified. Action: Look for the underlying error on the error message stack. ORA-13832: category name specified is invalid Cause: An invalid category name swas pecified. Action: Look for the underlying error on the error message stack. ORA-13833: SQL profile named string doesn"t exist Cause: A SQL profile name was specified that doesn"t exist. Action: Verify the name of the SQL profile. ORA-13834: name of SQL profile to be cloned must be provided Cause: A SQL profile name was not provided as the from target of a clone SQL profile operation. Action: Provide the name of the SQL profile being cloned. ORA-13835: invalid attribute name specified Cause: An invalid attribute name was specified for an alter SQL profile operation. Action: Verify the name of the attribute. ORA-13836: invalid attribute value specified Cause: An invalid attribute value was specified for an alter SQL profile operation. Action: Verify the attribute value. ORA-13837: invalid HASH_VALUE Cause: An invalid HASH_VALUE was passed to a create SQL profile operation Action: Verify the HASH_VALUE. ORA-13838: invalid ADDRESS value Cause: An invalid ADDRESS value was passed to a create SQL profile operation. Action: Verify the ADDRESS value. ORA-13839: V$SQL row doesn"t exist with given HASH_VALUE and ADDRESS. Cause: A HASH_VALUE and ADDRESS combination passed to the create SQL profile operation doesn"t coorespond to an existing V$SQL entry. Action: Verify the HASH_VALUE and ADDRESS in V$SQL. ORA-13840: Concurrent DDL Error in create SQL profile operation. Cause: A concurrent DDL operation was performed during a create or replace sql profile operation. Action: Try operation again ORA-13841: SQL profile named string already exists for a different signature/category pair Cause: A SQL profile already exists with the name specified under a different signature/category pair so it cannot be replaced, even with FORCE specified. Action: Specify a different name or drop the existing SQL profile. ORA-13842: no SELECT privilege on DBA_SQL_PROFILES Cause: A user has tried to perform an operation that requires SELECT privileges on the DBA_SQL_PROFILES view. Action: Either perform the operation as another user or get the privilege ORA-13843: no SQL profile with name like "string" exists for category like "string" Cause: A user tried to perform an operation by specifying a profile name/ category filter that did not target any profiles Action: Try a different filter after checking the profile name/category ORA-13844: no new SQL profile name or category specified. Cause: A user called remap_stgtab_sqlprof without specifying new values for the sql profile name or category. At least one is required. Action: Specify either a new profile name, or a new category, or both ORA-13850: Tracing for client identifier string is not enabled Cause: Attempt to disable a client identifier tracing which was never enabled Action: Supply correct client identifier ORA-13851: Tracing for client identifier string is already enabled Cause: Attempt to enable a client identifier tracing which has been already enabled Action: Supply correct client identifier, or disable and re-enable tracing with different bind/wait options ORA-13852: Tracing for service(module/action) string is not enabled Cause: Attempt to disable a service-level tracing which was never enabled Action: Supply correct service(module/action) name ORA-13853: Tracing for service (module/action) string is already enabled Cause: Attempt to enable a service-level tracing which has been already enabled Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options ORA-13854: Tracing for service(module/action) string on instance string is not enabled Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance Action: Supply correct service(module/action) name ORA-13855: Tracing for service (module/action) string on instance string is already enabled Cause: Attempt to enable a service-level tracing which has been already enabled on a specific instance Action: Supply correct service(module/action), or disable and re-enable tracing with different bind/wait options ORA-13856: Service name must be specified Cause: Omitting service name while enabling/disabling tracing or aggregation Action: Supply the service name ORA-13857: Invalid module name Cause: Module name is too long (exceeding 48 characters) Action: Supply correct name ORA-13858: Invalid action name Cause: Action name is too long (exceeding 32 characters) Action: Supply correct name ORA-13859: Action cannot be specified without the module specification Cause: Action name is specified, but the module name is not Action: Supply the module name ORA-13860: Invalid service name Cause: Service name is too long (exceeding 64 characters) Action: Supply correct name ORA-13861: Statistics aggregation for client identifier string is already enabled Cause: Attempt to enable a client identifier aggregation which has been already enabled Action: Supply correct client identifier ORA-13862: Statistics aggregation for client identifier string is not enabled Cause: Attempt to disable a client identifier statistics aggregation which was never enabled Action: Supply correct client identifier ORA-13863: Statistics aggregation for service(module/action) string is not enabled Cause: Attempt to disable a service-level statistics aggregation which was never enabled Action: Supply correct service(module/action) name ORA-13864: Statistics aggregation for service (module/action) string is already enabled Cause: Attempt to enable a service-level statistics aggregation which has been already enabled Action: Supply correct service(module/action) ORA-13865: Module name must be specified Cause: Attempt to enable/disable a service-level statistics aggregation without a module specification Action: Supply module name ORA-13866: Client identifier must be specified Cause: Omitting client identifier while enabling/disabling tracing or aggregation Action: Supply the client identifier ORA-13867: Database-wide SQL tracing is already enabled Cause: Attempt to enable a database-level tracing which has been already enabled Action: Disable and re-enable tracing with different bind/wait options ORA-13868: Instance-wide SQL tracing on instance string is not enabled Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance Action: No action required ORA-13869: Instance-wide SQL tracing on instance string is already enabled Cause: Attempt to enable an instance-level tracing which has been already enabled on a specific instance Action: Disable and re-enable tracing with different bind/wait options ORA-13870: Database-wide SQL tracing is not enabled Cause: Attempt to disable a database-level tracing which was never enabled Action: No action required ORA-13871: Invalid instance name Cause: Instance name is too long (exceeding 16 characters) Action: Supply correct name ORA-13900: missing or invalid parameter string Cause: A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid. Action: Specify a valid value for this parameter. ORA-13901: Object string was not found. Cause: An object name was passed to SET_THRESHOLD procedure that did not map to a valid object. Action: Specify a valid object name. ORA-13902: The specified file string is not a data file. Cause: The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file. Action: Specify a valid data file name. ORA-13903: Invalid combination of string threshold value and operator. Cause: A non-positive number was used for "Blocked User Session Count" metrics while operator contains equal. Action: Use a positive number for the threshold value or use "greater than" operator. ORA-13904: The file has been dropped and recreated during the procedure call. Cause: The file on which threshold is specified was dropped and recreated during the procedure call. Action: Retry this operation. ORA-13905: Critical or warning threshold have incorrect values Cause: The tablespace threshold values can be in the range 0 to 100 only. Action: Check the threshold values ORA-13906: The tablepace is not of the right type. Cause: An attempt was made to set a threshold on dictionary-managed tablespaces. Action: Check the tablespace type and reissue the command. ORA-13907: Threshold value is invalid. Cause: An attempt was made to specify an invalid value for critical or warning thresholds. Action: Use non-negative integers only for threshold values. ORA-13908: Invalid combination of metrics id and object type parameters. Cause: An attempt was made to specify an invalid combination of metrics id // and object type parameters. Action: Specify a valid combination of metrics id and object type parameters. ORA-13909: Invalid combination of threshold value and operator. Cause: An attempt was made to specify an invalid combination of threshold value and operator. Action: Check the operator and threshold values and reissue statement. ORA-13910: Parameter string cannot be NULL. Cause: An attempt was made to call GET_THRESHOLD procedure without a required parameter. Action: Specify a valid value for this parameter. ORA-13911: Threshold not found Cause: The threshold did not exist with the specified threshold key. Action: No action required. ORA-13912: Critical threshold value is less than warning threshold value. Cause: An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value. Action: Check the threshold values and reissue the statement. ORA-13913: The threshold cannot be set when SYSAUX is offline. Cause: SET_THRESHOLD procedure was called when SYSAUX tablespace was offline. Action: Call SET_THRESHOLD procedure when SYSAUX is online. ORA-13914: Threshold notification failed. Cause: An error occurred when sending notification for this threshold. Action: Make sure you have enough space on SYSAUX tablespace and retry this operation. ORA-13915: Critical byte based free space threshold value is greater than warning threshold value. Cause: An attempt was made to call SET_THRESHOLD procedure with the bytes based critical threshold value greater than the warning threshold value. Action: Check the threshold values and reissue the statement. ORA-13916: Invalid value "string" specified for parameter "string" Cause: An invalid value was specified for the the given parameter. Action: Correct the value being specified for the parameter. ORA-13917: Posting system alert with reason_id string failed with code [string] [string] Cause: Connection to the database is dead, or invalid parameter to alert routine. Action: If this condition repeats, please contact Oracle Support. ORA-13918: Updating system alert with reason_id string failed; previous alert not found Cause: System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING. Action: Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support. ORA-13919: Cannot specify values for parameter "string" and for parameter "string" Cause: Can only specify a value for one or the other. Action: Pass just one of the parameters. ORA-13951: MMON sub-action time limit exceeded Cause: This is an internal Server Manageability Error Action: Contact Oracle Support Services ORA-14000: only one LOCAL clause may be specified Cause: CREATE INDEX statement contained more than one LOCAL clause Action: Specify LOCAL option at most once ORA-14001: LOCAL clause contradicts previosly specified GLOBAL clause Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause Action: Specify LOCAL or GLOBAL clause, but not both ORA-14002: only one GLOBAL clause may be specified Cause: CREATE INDEX statement contained more than one GLOBAL clause Action: Specify GLOBAL option at most once ORA-14003: GLOBAL clause contradicts previosly specified LOCAL clause Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause Action: Specify GLOBAL or LOCAL clause, but not both ORA-14004: missing PARTITION keyword Cause: keyword PARTITION missing Action: supply missing keyword ORA-14005: missing RANGE keyword Cause: keyword RANGE missing Action: supply missing keyword ORA-14006: invalid partition name Cause: a partition name of the form is expected but not present. Action: enter an appropriate partition name. ORA-14007: missing LESS keyword Cause: keyword LESS missing Action: supply missing keyword ORA-14008: missing THAN keyword Cause: keyword THAN missing Action: supply missing keyword ORA-14009: partition bound may not be specified for a LOCAL index partition Cause: while parsing a CREATE INDEX statement to create a LOCAL partitioned index, of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table Action: remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions ORA-14010: this physical attribute may not be specified for an index partition Cause: unexpected option was encountered while parsing physical attributes of an index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for Hash partitions Action: remove invalid option(s) from the list of physical attributes of an index partition ORA-14011: names assigned to resulting partitions must be distinct Cause: Names of partitions resulting from splitting of an existing table or index partition are not distinct Action: rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index ORA-14012: resulting partition name conflicts with that of an existing partition Cause: Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index Action: rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index ORA-14013: duplicate partition name Cause: Name of a partition of a table or index being created is not unique Action: rename partition(s) to ensure that their names are unique among partitions of the table or index being created ORA-14014: maximum number of partitioning columns is 16 Cause: number of columns in a partitioning column list exceeded the legal limit of 16 Action: modify partitioning column list so that it consists of at most 16 columns ORA-14015: too many partition descriptions Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 1048575 (1024K-1). Action: Reduce number of partitions to not exceed 1048575 (1024K -1). ORA-14016: underlying table of a LOCAL partitioned index must be partitioned Cause: User attempted to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned table. Action: Correct the statement and reenter ORA-14017: partition bound list contains too many elements Cause: Partition bound list contained more elements than there are partitioning columns Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index ORA-14018: partition bound list contains too few elements Cause: Partition bound list contained fewer elements than there are partitioning columns Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or MAXVALUE) Action: Ensure that all elements of partition bound list are of valid type ORA-14020: this physical attribute may not be specified for a table partition Cause: unexpected option was encountered while parsing physical attributes of a table partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for Hash partitions Action: remove invalid option(s) from the list of physical attributes of a table partition ORA-14021: MAXVALUE must be specified for all columns Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns Action: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns ORA-14022: creation of LOCAL partitioned cluster indices is not supported Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal Action: Remove LOCAL along with s, if any, from the CREATE INDEX statement. ORA-14023: creation of GLOBAL partitioned cluster indices is not supported Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal Action: Remove PARTITION BY RANGE clause along with s from the CREATE INDEX statement. ORA-14024: number of partitions of LOCAL index must equal that of the underlying table Cause: User attempted to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table. Action: Correct the CREATE INDEX statement to specify a correct number of partitions ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log Cause: PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log Action: Ensure that a definition of a MATERIALIZED VIEW does not include invalid options ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive Cause: definition of a table contained both PARTITION and CLUSTER clauses which is illegal Action: Remove one of the conflicting clauses ORA-14027: only one PARTITION clause may be specified Cause: CREATE TABLE statement contained more than one PARTITION clause Action: Specify PARTITION option at most once ORA-14028: missing AT or VALUES keyword Cause: keyword AT or VALUES missing Action: supply missing keyword ORA-14029: GLOBAL partitioned index must be prefixed Cause: partitioning columns of a global partitioned index must form a prefix of the index" key columns Action: Ensure that the GLOBAL partitioned index being created is prefixed ORA-14030: non-existent partitioning column in CREATE TABLE statement Cause: Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created. Action: Ensure that all columns in the partitioning column list are columns of the table being created. ORA-14031: partitioning column may not be of type LONG or LONG RAW Cause: Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal. Action: Ensure that no partitioning column is of type LONG or LONG RAW. ORA-14032: partition bound of partition number string is too high Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal. Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. ORA-14036: partition bound value too large for column Cause: Length of partition bound value is longer than that of the corresponding partitioning column. Action: Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns ORA-14037: partition bound of partition "string" is too high Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal. Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. ORA-14038: GLOBAL partitioned index must be prefixed Cause: User attempted to create a GLOBAL non-prefixed partitioned index which is illegal Action: If the user, indeed, desired to create a non-prefixed index, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE index Cause: User attempted to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal Action: If the user, indeed, desired to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index" partitioning columns form a subset of its key columns ORA-14041: partition bound may not be specified for resulting partitions Cause: while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, of a resulting partition was found to contain VALUES LESS THAN clause which is illegal Action: remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition ORA-14042: partition bound may not be specified for a partition being moved, modified or rebuilt Cause: while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal Action: remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt ORA-14043: only one partition may be added Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas ORA-14044: only one partition may be moved Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas ORA-14045: only one partition may be modified Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas ORA-14046: a partition may be split into exactly two new partitions Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; ORA-14048: a partition maintenance operation may not be combined with other operations Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (e.g. MOVE PARTITION) with some other operation (e.g. ADD PARTITION or PCTFREE which is illegal Action: Ensure that a partition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will ORA-14049: invalid ALTER TABLE MODIFY PARTITION option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement for a Range or Composite Range partition. Action: Specify only legal options. ORA-14050: invalid ALTER INDEX MODIFY PARTITION option Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement. Action: Specify only legal options. ORA-14051: invalid ALTER MATERIALIZED VIEW option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW statement. Action: Specify only legal options. ORA-14052: partition-extended table name syntax is disallowed in this context Cause: User attempted to use partition-extended table name syntax in illegal context (i.e. not in FROM-clause or INSERT, DELETE, or UPDATE statement) Action: Avoid use of partition-extended table name in contexts other those mentioned above. ORA-14053: illegal attempt to modify string in string statement Cause: Certain attributes of objects (e.g. tables) may be specified at creation time, but may not be modified using ALTER statement. Unfortunately, user specified one of such attributes. Action: Ensure that ALTER statement specifies new values only for attributes which may be changed once an object has been created ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION option Cause: Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION ORA-14055: keyword REBUILD in ALTER INDEX REBUILD must immediately follow Cause: ALTER INDEX statement contained REBUILD keyword following some index attributes (e.g. INITRANS.) Action: Ensure that keyword REBUILD immediately follows the name of the index being altered ORA-14056: partition number string: sum of PCTUSED and PCTFREE may not exceed 100 Cause: the sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100 ORA-14057: partition "string": sum of PCTUSED and PCTFREE may not exceed 100 Cause: the sum of PCTUSED and PCTFREE for a partition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100 ORA-14058: partition number string: INITRANS value must be less than MAXTRANS value Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that value of INITRANS (whether specified explcitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS ORA-14059: partition "string": INITRANS value must be less than MAXTRANS value Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used. Action: ensure that value of INITRANS (whether specified explcitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS ORA-14060: data type or length of a table partitioning column may not be changed Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of table partitioning column(s) ORA-14061: data type or length of an index partitioning column may not be changed Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition some index defined on the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of index partitioning column(s) ORA-14062: one or more of table"s partitions reside in a read-only tablespace Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more partitions of which reside in read-only tablespaces, which is illegal Action: Avoid performing aformentioned operations on a partitioned table one or more partitions of which reside in read-only tablespaces ORA-14063: Unusable index exists on unique/primary constraint key Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable. Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD ORA-14064: Index with Unusable partition exists on unique/primary constraint key Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index one or more partitions of which are marked Index Unusable. Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION ORA-14065: ALLOCATE STORAGE may not be specified for a partitioned table Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement. ORA-14066: illegal option for a non-partitioned index-organized table Cause: An attempt was made to issue a CREATE or ALTER TABLE command on a non-partitioned IOT, but the command contains an option that is legal only for partitioned index-organized tables. Such options are: ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT. Action: Remove the illegal option(s) from the command. ORA-14067: duplicate TABLESPACE_NUMBER specification Cause: TABLESPACE_NUMBER clause was specified more than once for an table, index or an index partition Action: Correct the code generating text of CREATE INDEX statement sent to the slaves ORA-14068: TABLESPACE and TABLESPACE_NUMBER may not be both specified Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, index or an index partition Action: Correct the code generating text of CREATE INDEX statement sent to the slaves ORA-14069: invalid TABLESPACE_NUMBER value Cause: The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF Action: Correct the code generating text of CREATE INDEX statement sent to the slaves ORA-14070: option may be specified only for partitioned indices or with REBUILD Cause: User issued ALTER INDEX statament containing an option which is legal only for partitioned indices or in conjunction with REBUILD against a non-partitioned index. Such options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clause Action: Remove illegal option(s). ORA-14071: invalid option for an index used to enforce a constraint Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint. Action: Choose one of the valid index options. ORA-14072: fixed table may not be truncated Cause: User attempted to truncate a fixed table which is illegal. Action: Ensure that the table being truncated is not a fixed table. ORA-14073: bootstrap table or cluster may not be truncated Cause: User attempted to truncate a bootstrap table or cluster which is illegal Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster) ORA-14074: partition bound must collate higher than that of the last partition Cause: Partition bound specified in ALTER TABLE ADD PARTITION statement did not collate higher than that of the table"s last partition, which is illegal. Action: Ensure that the partition bound of the partition to be added collates higher than that of the table"s last partition. ORA-14075: partition maintenance operations may only be performed on partitioned indices Cause: Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, at best, meaningless Action: Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned ORA-14076: submitted alter index partition/subpartition operation is not valid for local partitioned index Cause: User attempted to either drop, split, add or coalesce a partition or a subpartition of a local index which is illegal. Action: Ensure that the index named in such statement is a global partitioned index. ORA-14078: you may not drop the highest partition of a GLOBAL index Cause: User attempted to drop highest partition of a GLOBAL index, which is illegal. Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index. ORA-14079: illegal option for a partition marked Index Unusable Cause: ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal Action: Ensure that only valid optins are specified ORA-14080: partition cannot be split along the specified high bound Cause: User attempted to split a partition along a bound which either collates higher than that of the partition to be split or lower than that of a partition immediately preceding the one to be split Action: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher that that of a partition immediately preceding the one to be split ORA-14081: new partition name must differ from the old partition name Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying which is identical to the name of the partition being renamed Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index ORA-14082: new partition name must differ from that of any other partition of the object Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying which is identical to the name of some existing partition of the object Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index ORA-14083: cannot drop the only partition of a partitioned table Cause: A drop partition command is being executed when there is only one partition in the table Action: Ensure that there is at least one partition. Drop table to remove all partitions ORA-14084: you may specify TABLESPACE DEFAULT only for a LOCAL index Cause: User attempted to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal. Action: Reenter the statement without TABLESPACE DEFAULT clause. ORA-14085: partitioned table cannot have column with LONG datatype Cause: User tried to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table. Action: LONG data types are not supported with partitioned tables. Create table without LONG column or change table to not partitioned. If adding column, do not use LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non partitioned table. ORA-14086: a partitioned index may not be rebuilt as a whole Cause: User attempted to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal Action: Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and recreate the entire index ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION option Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE PARTITION ORA-14095: ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table Cause: The table in the EXCHANGE operation is either clustered or partitioned Action: Ensure that the table with which the partition is being exchanged for is not partitioned or clustered. ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns Cause: The two tables specified in the EXCHANGE have different number of columns Action: Ensure that the two tables have the same number of columns with the same type and size. ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size Action: Ensure that the two tables have the same number of columns with the same type and size. ORA-14098: index mismatch for tables in ALTER TABLE EXCHANGE PARTITION Cause: The two tables specified in the EXCHANGE have indexes which are not equivalent Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same. ORA-14099: all rows in table do not qualify for specified partition Cause: There is at least one row in the non partitioned table which does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION Action: Ensure that all the rows in the segment qualify for the partition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them. ORA-14100: partition extended table name cannot refer to a remote object Cause: User attempted to use partition-extended table name syntax in conjunction with remote object name which is illegal Action: Correct the statement and reenter ORA-14101: partition extended table name cannot refer to a synonym Cause: User attempted to use partition-extended table name syntax in conjunction with synonym name which is illegal Action: Correct the statement and reenter ORA-14102: only one LOGGING or NOLOGGING clause may be specified Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified. Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement. ORA-14103: LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed. Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. ORA-14104: RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices Cause: CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal Action: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. ORA-14105: RECOVERABLE/UNRECOVERABLE may not be specified in this context Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context. Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option. ORA-14106: LOGGING/NOLOGGING may not be specified for a clustered table Cause: User attempted to specify LOGGING or NOLOGGING clausein CREATE TABLE or ALTER TABLE statement involving a clustered table Action: Remove offending clause. ORA-14107: partition specification is required for a partitioned object Cause: parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects. Action: supply missing parameter ORA-14108: illegal partition-extended table name syntax Cause: Partition to be accessed may only be specified using its name. User attempted to use a partition number or a bind variable. Action: Modify statement to refer to a partition using its name ORA-14109: partition-extended object names may only be used with tables Cause: User attempted to use a partition-extended object name with an object which is not a table. Action: Avoid using partition-extended name syntax with objects which are not tables ORA-14110: partitioning column may not be of type ROWID Cause: Partitioning column specified by the user was of type ROWID, which is illegal. Action: Ensure that no partitioning column is of type ROWID. ORA-14111: creation of a GLOBAL partitioned index on clustered tables is not supported Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal. Action: Remove PARTITION BY RANGE/HASH clause along with any partition descriptions to create a GLOBAL non-partitioned index on a clustered table ORA-14112: RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition Cause: Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal Action: Remove offending clause. Use LOGGING or NOLOGGING instead. ORA-14113: partitioned table cannot have column with LOB datatype Cause: User tried to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table. Action: LOB data types are not supported with partitioned tables. Create table without LOB column or change table to not partitioned. If adding column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non partitioned table. ORA-14114: partitioned table cannot have column with object, REF, nested table, array datatype Cause: User tried to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table. Action: object data types are not supported with partitioned tables. Create table without object column or change table to not partitioned. If adding column, do not use object datatypes. If modifying attributes of a column to change data type to object, it has to be a non partitioned table. ORA-14115: partition bound of partition number string is too long Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K). Action: Change representation of a partition high bound to bring its length within legal limit. ORA-14116: partition bound of partition "string" is too long Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K). Action: Change representation of a partition high bound to bring its length within legal limit. ORA-14117: partition resides in offlined tablespace Cause: User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. Action: Bring tablespace online before attempting the operation. ORA-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them. Action: Ensure that the two tables do not have CHECK constraint defined on any column ORA-14119: specified partition bound is too long Cause: Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K). Action: Change representation of a partition high bound to bring its length within legal limit. ORA-14120: incompletely specified partition bound for a DATE column Cause: An attempt was made to use a date expression whose format does not fully (i.e. day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT). Action: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (i.e. day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (i.e. including the century) specification of the year, use TO_DATE() (e.g. TO_DATE("01-01-1999", "MM-DD-YYYY") to fully express the desired date. ORA-14121: MODIFY DEFAULT ATTRIBUTES may not be combined with other operations Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will ORA-14122: only one REVERSE or NOREVERSE clause may be specified Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX statement. Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement. ORA-14123: duplicate NOREVERSE clause Cause: NOREVERSE was specified more than once in ALTER INDEX statement. Action: Remove all but one of the NOREVERSE clauses and reissue the statement. ORA-14124: duplicate REVERSE clause Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements. Action: Remove all but one of the REVERSE clauses and reissue the statement. ORA-14125: REVERSE/NOREVERSE may not be specified in this context Cause: REVERSE/NOREVERSE clause is not allowed in this context. Action: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement. ORA-14126: only a may follow description(s) of resulting partitions Cause: Descriptions of partition(s) resulting from splitting of a table or index partition may be followed by an optional which applies to the entire statement and which, in turn, may not be followed by any other clause. Action: Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement. ORA-14128: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints. Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation. ORA-14129: INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints Cause: Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command. Action: Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used. ORA-14130: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated. Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes. ORA-14131: enabled UNIQUE constraint exists on one of the tables Cause: One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding. Action: Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement. ORA-14132: table cannot be used in EXCHANGE Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply: - it is a typed table - it contains ADT columns - it contains nested-table columns - it contains REF columns - it contains array columns - it is an index-organized table - it contains LOB columns - it is a nested table - it is created with row dependency and the partitioned table is not - it is created without row dependency and the partitioned table is Action: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command. ORA-14133: ALTER TABLE MOVE cannot be combined with other operations Cause: An attempt was made to combine an ALTER TABLE MOVE statement with another operation, such as MODIFY. Action: Make sure that MOVE is the only operation specified in ALTER TABLE statement; ORA-14134: indexes cannot use both DESC and REVERSE Cause: An attempt was made to make a reverse index with some index columns marked DESC. Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC. ORA-14135: a LOB column cannot serve as a partitioning column Cause: An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column. Action: Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB. ORA-14136: ALTER TABLE EXCHANGE restricted by fine-grained security Cause: User doing exchange does not have full table access due to VPD policies. Action: Grant exempt priviliges to this user. ORA-14137: Table in partially dropped state, submit DROP TABLE PURGE Cause: An attempt was made to access a partitioned table in a partially dropped state. Action: Submit DROP TABLE
PURGE to drop the table. ORA-14138: An unexpected error encountered during drop table operation Cause: Drop table encountered an unexpected error. Action: a. Submit drop table
purge, or b. If the situation described in the next error on the stack can be corrected, do so. c. Contact Oracle Support. ORA-14150: missing SUBPARTITION keyword Cause: keyword SUBPARTITION missing Action: supply missing keyword ORA-14151: invalid table partitioning method Cause: Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, or Composite Range/Hash (R+H). Action: Specify one of valid partitioning methods ORA-14152: invalid number of partitions specified in PARTITIONS clause Cause: number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-1048575) Action: Specify a number between 1 and 1024K-1 in the number-of-partitions clause ORA-14153: only one of STORE IN or clause may be specified Cause: both STORE IN and clauses were specified in a CREATE TABLE|INDEX command Action: Remove one of offending clauses ORA-14154: only one of STORE IN or clause may be specified Cause: both STORE IN and clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a Composite Range partitioned object Action: Remove one of offending clauses ORA-14155: missing PARTITION or SUBPARTITION keyword Cause: expect either PARTITION or SUBPARTITION keyword but none was supplied Action: supply missing keyword ORA-14156: invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause Cause: number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-1048575) Action: Specify a number between 1 and 1024K-1 in the number-of-subpartitions clause ORA-14157: invalid subpartition name Cause: a subpartition name of the form is expected but not present. Action: enter an appropriate subpartition name. ORA-14158: too many subpartition descriptions Cause: CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 1048575. Action: Reduce number of subpartitions to not exceed 1024K-1. ORA-14159: duplicate subpartition name Cause: Name of a subpartition of a table or index being created is not unique Action: rename subpartition(s) to ensure that their names are unique among subpartitions of the table or index being created ORA-14160: this physical attribute may not be specified for a table subpartition Cause: unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option Action: remove invalid option(s) ORA-14161: subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100 Cause: the sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100 ORA-14162: subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100 Cause: the sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100 ORA-14163: subpartition number string: INITRANS value must be less than MAXTRANS value Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS ORA-14164: subpartition "string": INITRANS value must be less than MAXTRANS value Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used. Action: ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS ORA-14165: MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (e.g. ADD PARTITION or PCTFREE) which is illegal Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will ORA-14166: missing INTO keyword Cause: keyword INTO missing Action: supply missing keyword ORA-14167: only one subpartition may be moved Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to be moved Action: Ensure that the statement describes exactly one subpartition to be moved and that it does not contain any commas ORA-14168: only one subpartition may be modified Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to be modified Action: Ensure that the statement describes exactly one subpartition to be modified and that it does not contain any commas ORA-14169: invalid ALTER TABLE MODIFY SUBPARTITION option Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement. Action: Specify only legal options. ORA-14170: cannot specify clause in CREATE TABLE|INDEX Cause: User requested to generate default partition description(s) (possibly via PARTITIONS ) while at the same time specified clause which is illegal Action: Remove one of offending clauses. ORA-14171: cannot specify clause in CREATE|ALTER TABLE Cause: User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified clause which is illegal Action: Remove one of offending clauses. ORA-14172: invalid ALTER TABLE EXCHANGE SUBPARTITION option Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION ORA-14173: illegal subpartition-extended table name syntax Cause: Subpartition to be accessed may only be specified using its name. User attempted to use a subpartition number or a bind variable. Action: Modify statement to refer to a subpartition using its name ORA-14174: only a may follow COALESCE PARTITION|SUBPARTITION Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional . No partition/subpartition attributes may be specified Action: Ensure that no partition/subpartition attribute was specified. ORA-14175: a subpartition maintenance operation may not be combined with other operations Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (e.g. MOVE SUBPARTITION) with some other operation (e.g. MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal Action: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will ORA-14176: this attribute may not be specified for a hash partition Cause: An invalid option was encountered while parsing physical attributes of a partition of an object partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions. Action: Remove the invalid option(s). ORA-14177: STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a range/list/composite range list partitioned table Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index on range/list/composite range list partitioned table ORA-14178: STORE IN (DEFAULT) clause is not supported for hash partitioned global indexes Cause: STORE IN (DEFAULT) is valid only for local indexes. Action: a) Specify a tablespace list in place of DEFAULT, or b) Remove STORE IN clause and specify tablespaces individually for each index partition. ORA-14183: TABLESPACE DEFAULT can be specified only for Composite LOCAL index Cause: User attempted to specify TABLESPACE DEFAULT for a partition of a Range/System/Hash partitioned LOCAL index object, which is illegal. Action: Replace TABLESPACE DEFAULT with TABLESPACE or remove it. ORA-14185: incorrect physical attribute specified for this index partition Cause: unexpected option was encountered while parsing physical attributes of a local index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for Hash partitions STORE IN () is also disallowed for all but Composite Range partitions Action: remove invalid option(s) from the list of physical attributes of an index partition ORA-14186: number of sub-partitions of LOCAL index must equal that of the underlying table Cause: User attempted to create a LOCAL partitioned index with a number of sub-partitions which is different from that of the underlying table. Action: Correct the CREATE INDEX statement to specify a correct number of sub-partitions ORA-14187: partitioning method for LOCAL index is inconsistent with that of the underlying table Cause: User attempted to create a LOCAL partitioned index that is not equi-partitioned with the underlying table. The partitioning types are mismatched. Action: Correct the CREATE INDEX statement to ensure that the index partitionining method is consistent with that of the base table ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index Cause: User attempted to create a UNIQUE partitioned index whose sub-partitioning columns do not form a subset of its key columns which is illegal Action: If the user, indeed, desired to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index" subpartitioning columns form a subset of its key columns ORA-14189: this physical attribute may not be specified for an index subpartition Cause: unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option Action: remove invalid option(s) ORA-14190: only one ENABLE/DISABLE ROW MOVEMENT clause can be specified Cause: One of three possible actions caused the error: 1) ENABLE ROW MOVEMENT was specified more than once. 2) DISABLE ROW MOVEMENT was specified more than once. 3) Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified. Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses; then, reissue the command. ORA-14191: ALLOCATE STORAGE may not be specified for Composite Range partitioned object Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. ORA-14192: cannot modify physical index attributes of a Hash index partition Cause: User attempted to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a Hash partitioned index Action: Remove the physical attributes one is trying to modify ORA-14193: invalid ALTER INDEX MODIFY SUBPARTITION option Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement. Action: Specify only legal options. ORA-14194: only one subpartition may be rebuilt Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt Action: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas ORA-14195: ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement. ORA-14196: Specified index cannot be used to enforce the constraint. Cause: The index specified to enforce the constraint is unsuitable for the purpose. Action: Specify a suitable index or allow one to be built automatically. ORA-14251: Specified subpartition does not exist Cause: Subpartition not found for the object. Action: Retry with correct subpartition name. ORA-14252: invalid ALTER TABLE MODIFY PARTITION option for a Hash partition Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a Hash partition. Action: Specify only legal options. ORA-14253: table is not partitioned by Composite Range method Cause: The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned by Composite Range method Action: Ensure that the table is partitioned by Composite Range method ORA-14254: cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a Range or Composite Range partitioned table which is illegal. Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION. ORA-14255: table is not partitioned by Range, Composite Range or List method Cause: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by Range, List or Composite Range method Action: Ensure that the table is partitioned by Range, List or Composite Range method ORA-14256: invalid resulting partition description(s) Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a Composite Range partitioned table which is illegal Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range method ORA-14257: cannot move partition other than a Range or Hash partition Cause: User attempt to move a partition that is not a Range or Hash partition which is illegal Action: Specify MOVE PARTITION for a Range or Hash partition only ORA-14258: invalid partition description Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a Composite Range/Hash partitioned table which is illegal Action: Remove invalid clause(s), or ensure that the table is partitioned by Composite Range/Hash method ORA-14259: table is not partitioned by Hash method Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method Action: Specify valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method ORA-14260: incorrect physical attribute specified for this partition Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING option to a Hash partition via ALTER TABLE ADD/MOVE PARTITION command which is illegal. Only TABLESPACE may be specified. Action: Remove invalid option(s) ORA-14261: partition bound may not be specified when adding this Hash partition Cause: User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a Hash partitioned table which is illegal Action: Remove VALUES LESS THAN clause from the description of partition being added ORA-14262: new subpartition name must differ from the old subpartition name Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying which is identical to the name of the subpartition being renamed Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index ORA-14263: new subpartition name must differ from that of any other subpartition of the object Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying which is identical to the name of some existing subpartition of the object Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index ORA-14264: table is not partitioned by Composite Range method Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method Action: Ensure that the table is partitioned by Composite method ORA-14265: data type or length of a table subpartitioning column may not be changed Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of table subpartitioning column(s) ORA-14266: data type or length of an index subpartitioning column may not be changed Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal Action: Avoid modifying data type and/or length of index subpartitioning column(s) ORA-14267: cannot specify PARALLEL clause when adding a (Composite) Range partition Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a Range or Composite Range partition which is illegal Action: Remove the PARALLEL clause. ORA-14268: subpartition "string" of the partition resides in offlined tablespace Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. Action: Bring tablespace online before attempting the operation. ORA-14269: cannot exchange partition other than a Range or Hash partition Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a Range or Hash partition which is illegal Action: Specify EXCHANGE PARTITION for a Range or Hash partition only ORA-14270: table is not partitioned by Range or Hash or List method Cause: The table in ALTER TABLE MODIFY PARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Range or Hash method which is illegal. Action: Ensure that the table is partitioned by Range or Hash method ORA-14271: table is not partitioned by Composite Range method Cause: The table in ALTER TABLE MODIFY SUBPARTITION { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES } statement is not partitioned by Composite Range method which is illegal. Action: Ensure that the table is partitioned by Composite Range method ORA-14272: only a partition with higher bound can be reused Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal. Action: Use the higher-bound partition to be the resulting partition or specify a new partition name ORA-14273: lower-bound partition must be specified first Cause: User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal Action: Specify lower-bound partition then higher-bound partition ORA-14274: partitions being merged are not adjacent Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal Action: Specify two partitions that are adjacent ORA-14275: cannot reuse lower-bound partition as resulting partition Cause: User attempt to reuse lower-bound partition of the partitions being merged which is illegal Action: Specify new resulting partition name or reuse the higher-bound partition only ORA-14276: EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned Action: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered. ORA-14277: tables in EXCHANGE SUBPARTITION must have the same number of columns Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns Action: Ensure that the two tables have the same number of columns with the same type and size. ORA-14278: column type or size mismatch in EXCHANGE SUBPARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size Action: Ensure that the two tables have the same number of columns with the same type and size. ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have indexes which are not equivalent Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non partitioned index for the non partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same. ORA-14280: all rows in table do not qualify for specified subpartition Cause: There is at least one row in the non partitioned table which does not qualify for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION Action: Ensure that all the rows in the segment qualify for the subpartition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that subpartition to find out the invalid rows and delete them. ORA-14281: CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them. Action: Ensure that the two tables do not have CHECK constraint defined on any column ORA-14282: FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints. Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation. ORA-14283: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated. Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes. ORA-14284: one or more of table"s subpartitions reside in a read-only tablespace Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more subpartitions of which reside in read-only tablespaces, which is illegal Action: Avoid performing aformentioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces ORA-14285: cannot COALESCE the only partition of this hash partitioned table or index Cause: A COALESCE PARTITION command was issued when there is only one partition in the table or index, which is illegal Action: Ensure that there is at least one partition. Drop the table or index to remove all partitions. ORA-14286: cannot COALESCE the only subpartition of this table partition Cause: A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal Action: Ensure that there is at least one subpartition. Drop partition to remove all subpartitions. ORA-14287: cannot REBUILD a partition of a Composite Range partitioned index Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal Action: REBUILD the index partition, a subpartition at a time ORA-14288: index is not partitioned by Composite Range method Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by Composite Range method Action: none ORA-14289: cannot make local index partition of Composite Range partitioned table unusable Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal Action: none ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints. Action: Ensure that the two tables do not have PRIMARY KEY constraints defined on any column or disable all PRIMARY KEY constraints on both tables. Then retry the operation. ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table Cause: A composite partition can only be exchanged with a partitioned table. Action: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite. ORA-14292: Partitioning type of table must match subpartitioning type of composite partition Cause: When exchanging a partitioned table with a composite partition the partitioning type of the table must match the subpartitioning type of the composite partition. Action: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition. ORA-14293: Number of partitioning columns does not match number of subpartitioning columns Cause: When exchanging a partitioned table with a composite partition the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition. Action: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the the composite partition. ORA-14294: Number of partitions does not match number of subpartitions Cause: When exchanging a partitioned table with a composite partition the number of partitions of the table must match the number of subpartitions of the composite partition. Action: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition. ORA-14295: column type or size mismatch between partitioning columns and subpartitioning columns Cause: When exchanging a partitioned table with a composite partition the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition. Action: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition. ORA-14296: Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. For index organized tables, either the block sizes of the index or the overflow (or both) do not match. Action: Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. For index organized tables, ensure that the block sizes of both the index and the overflow of the two tables match. ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. Action: Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION Cause: The block sizes of a pair of corresponding LOB columns of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. Action: Ensure that the block sizes of corresponding pairs of LOB columns of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. ORA-14299: total number of partitions/subpartitions exceeds the maximum limit Cause: The total number of combined fragments specified in partitions /subpartitions exceeds 1048575. Action: Reissue the statement with fewer number of fragments ORA-14301: table-level attributes must be specified before partition-level attributes Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of LOB columns were encountered after processing partition-level attributes of LOB columns or while processing CREATE TABLE statement, table-level attributes of LOB columns were encountered after processing partition descriptions. Action: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement. ORA-14302: only one list of added-LOB-storage-clauses can be specified in a statement Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list. Action: Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement. ORA-14303: partitions or subpartitions are not in the right order Cause: User attempted to rebuild a partition of a Composite Range partitioned index which is illegal Action: Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement. ORA-14304: List partitioning method expects a single partitioning column Cause: number of columns in a partitioning column list exceeded the legal limit of 1 for List partitioned objects Action: modify partitioning column list so that it consists of at most 1 column ORA-14305: List value "string" specified twice in partition "string" Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value ORA-14306: List value "string" specified twice in partitions "string", "string" Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value ORA-14307: partition contains too many list values Cause: Partition list contains more than 524288 list values Action: Reduce the number of values to not exceed 524288 values ORA-14308: partition bound element must be one of: string, datetime or interval literal, number, or NULL Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or NULL) Action: Ensure that all elements of partition bound list are of valid type ORA-14309: Total count of list values exceeds maximum allowed Cause: Partitioned object contains more than 524288 list values Action: Reduce number of values to less than 524288. ORA-14310: VALUES LESS THAN or AT clause cannot be used with List partitioned tables Cause: VALUES LESS THAN or AT clause can be used only with Range partitioned tables Action: Use VALUES () clause with List partitioned tables ORA-14311: Expecting VALUES LESS THAN or AT clause Cause: VALUES () clause can be used only with List partitioned tables Action: Use VALUES LESS THAN clause with Range partitioned tables ORA-14312: Value string already exists in partition string Cause: One of the list values in the ADD PARTITION or ADD VALUES statement already exists in another partition Action: Remove the duplicate value from the statement and try again ORA-14313: Value string does not exist in partition string Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the partition Action: Remove the value from the statement and try again ORA-14314: resulting List partition(s) must contain atleast 1 value Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value Action: Ensure that each of the resulting partitions contains atleast 1 value ORA-14315: cannot merge a partition with itself Cause: The same partition name was specified twice for the merge operation Action: Re-submit operation with 2 distinct partition names ORA-14316: table is not partitioned by List method Cause: ALTER TABLE ADD|DROP VALUES can only be performed on List partitioned objects Action: Re-issue the command against a List partitoned object. ORA-14317: cannot drop the last value of partition Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition Action: Cannot execute the command, unless two or more values exist for partition ORA-14318: DEFAULT partition must be last partition specified Cause: A partition description follows the one describing the default partition Action: Ensure that the DEFAULT partition is the last partition description ORA-14319: DEFAULT cannot be specified with other values Cause: DEFAULT keyword has been specified along with other values when specifying the values for a list partition Action: Ensure that if DEFAULT is specified, it is the only value specified ORA-14320: DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT Cause: DEFAULT keyword has been specified when doing a ADD VALUES or DROP VALUES or SPLIT partition or subpartition. Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operation. ORA-14321: cannot add/drop values to DEFAULT partition Cause: A ADD/DROP VALUES operation is being done on the default partition Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT partition ORA-14322: DEFAULT partition already exists Cause: A partition already exists with DEFAULT value Action: none ORA-14323: cannot add partition when DEFAULT partition exists Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists Action: Issue a SPLIT of the DEFAULT partition instead ORA-14324: values being added already exist in DEFAULT partition Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT partition Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into the partition to which values need to be added ORA-14325: only LOCAL indexes may be specified in this clause Cause: A global index has been specified in the UPDATE INDEXES (..) clause Action: Only specify local indexes when using this clause ORA-14326: Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause Cause: A Primary index on an IOT, DOMAIN or LOB index has been specified in the UPDATE INDEXES (..) clause Action: Do not specify any of these indexes when using this clause ORA-14327: Some index [sub]partitions could not be rebuilt Cause: The first phase (partition DDL and index [sub]partition placement) completed successfully. During the second phase, some of the index [sub]partitions could not be rebuilt. Action: . ORA-14329: domain index [sub]partitions cannot be renamed in this clause Cause: The user tried to rename a domain index [sub]partition in the UPDATE INDEXES clause of a ALTER TABLE MOVE [SUB]PARTITION operation. This is not allowed. Action: Leave the name blank or use the same name. ORA-14400: inserted partition key does not map to any partition Cause: An attempt was made to insert a record into, a Range or Composite Range object, with a concatenated partition key that is beyond the concatenated partition bound list of the last partition -OR- An attempt was made to insert a record into a List object with a partition key that did not match the literal values specified for any of the partitions. Action: Do not insert the key. Or, add a partition capable of accepting the key, Or add values matching the key to a partition specification ORA-14401: inserted partition key is outside specified partition Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement Action: do not insert the key or insert it in another partition ORA-14402: updating partition key column would cause a partition change Cause: An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition Action: Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key. ORA-14403: cursor invalidation detected after getting DML partition lock Cause: cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. This error is never returned to user, because is caught in opiexe() and the DML statement is retried. Action: nothing to be done, error should never be returned to user ORA-14404: partitioned table contains partitions in a different tablespace Cause: An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace Action: find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace ORA-14405: partitioned index contains partitions in a different tablespace Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace. Action: find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them. ORA-14406: updated partition key is beyond highest legal partition key Cause: At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition. Action: Do not update the key. Or, add a partition capable of accepting the key. ORA-14407: partitioned table contains subpartitions in a different tablespace Cause: An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace Action: find tables with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move subpartitions to a different tablespace ORA-14408: partitioned index contains subpartitions in a different tablespace Cause: An attempt was made to drop a tablespace which contains indexes whose subpartitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace. Action: find indexes with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them. ORA-14409: inserted partition key is outside specified subpartition Cause: the concatenated partition key of an inserted record is outside the ranges of the two concatenated subpartition bound lists that delimit the subpartition named in the INSERT statement Action: do not insert the key or insert it in another subpartition ORA-14450: attempt to access a transactional temp table already in use Cause: An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session. Action: do not attempt to access the temporary table until the concurrent transaction has committed or aborted. ORA-14451: unsupported feature with temporary table Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause. Action: do not do that. ORA-14452: attempt to create, alter or drop an index on temporary table already in use Cause: An attempt was made to create, alter or drop an index on temporary table which is already in use. Action: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions. ORA-14453: attempt to use a LOB of a temporary table, whose data has alreadybeen purged Cause: An attempt was made to use LOB from a temporary table whose data has been dropped either because table was transaction-specific and transaction has commited or aborted, table was truncated or session which created this LOB has ended. Action: This LOB locator is invalid and cannot be used. ORA-14454: attempt to reference temporary table in a referential integrity constraint Cause: An attempt was made to reference temporary table in a referencial integrity constraint. This is not supported. Action: Use triggers. ORA-14455: attempt to create referential integrity constraint on temporary table Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported. Action: Use triggers. ORA-14456: cannot rebuild index on a temporary table Cause: An attempt was made to rebuild an index on a temp table. Action: The index data is anyway lost at end of session/transaction. ORA-14457: disallowed Nested Table column in a Temporary table Cause: An attempt made to create a Nested Table column in a temporary table. This is not supported. Action: Do not specify these datatypes for temporary tables. ORA-14458: attempt was made to create a temporary table with INDEX organization Cause: An attempt was made to create an Index Organized Temporary table. This is not supported. Action: Create the table with HEAP organization and the primary key. ORA-14459: missing GLOBAL keyword Cause: keyword GLOBAL is missing while creating temporary table. Action: supply keyword. ORA-14460: only one COMPRESS or NOCOMPRESS clause may be specified Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more than once, or both COMPRESS and NOCOMPRESS were specified. Action: specify each desired COMPRESS or NOCOMPRESS clause option only once. ORA-14461: cannot REUSE STORAGE on a temporary table TRUNCATE Cause: REUSE STORAGE was specified with TRUNCATE on a temporary table. This is unsupported as it is meaningless. Action: Specify DROP STORAGE instead (which is the default). ORA-14500: LOCAL option not valid without partition name Cause: Incorrect syntax specified Action: Retry the command ORA-14501: object is not partitioned Cause: Table or index is not partitioned. Invalid syntax. Action: Retry the command with correct syntax. ORA-14503: only one partition name can be specified Cause: More than one partition name has been specified for analyze Action: Specify one partition name. ORA-14504: syntax not supported for analyze Cause: A partition/subpartition number or bind variable has been used Action: Specify a valid partition/subpartition name. ORA-14505: LOCAL option valid only for partitioned indexes Cause: Incorrect syntax specified Action: Retry the command ORA-14506: LOCAL option required for partitioned indexes Cause: Incorrect syntax specified Action: Retry the command ORA-14507: partition corrupt. all rows do not fall within partition bounds Cause: The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation Action: Delete rows in partition which do not qualify ORA-14508: specified VALIDATE INTO table not found Cause: The specified table either does not exist or user does not have the proper privleges. Action: Specify the correct table to use. ORA-14509: specified VALIDATE INTO table form incorrect Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. See utlvalid.sql for more information. ORA-14510: can specify VALIDATE INTO clause only for partitioned tables Cause: The VALIDATE INTO has been specified for a non partitioned table or cluster or index. Action: Use syntax correctly ORA-14511: cannot perform operation on a partitioned object Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes. Action: Retry the command with correct syntax. ORA-14512: cannot perform operation on a clustered object Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes. Action: Retry the command with correct syntax. ORA-14513: partitioning column may not be of object datatype Cause: Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal. Action: Ensure that no partitioning column is an object datatype. ORA-14514: LOCAL option not valid without subpartition name Cause: Incorrect syntax specified Action: Retry the command ORA-14515: only one aubpartition name can be specified Cause: More than one subpartition name has been specified for analyze Action: Specify one subpartition name. ORA-14516: subpartition corrupt. all rows do not fall within subpartition bounds Cause: The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation Action: Delete rows in subpartition which do not qualify ORA-14517: subpartition of index "string.string" is in unusable state Cause: An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation Action: REBUILD the unusable index subpartition ORA-14518: partition contains rows corresponding to values being dropped Cause: table partition contains rows for the values being dropped. Action: DELETE all rows for the values being dropped and reissue statement ORA-14519: Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string] Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size. Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size. ORA-14520: Tablespace string block size [string] does not match existing object block size [string] Cause: A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object"s default tablespace (or one of the object"s partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object"s partitions/subpartitions. Action: Specify a tablespace of the same block size as the partitioned object. ORA-14521: Default tablespace string block size [string] for string string does not match existing string block size [string] Cause: A DDL statement was issued that would require creation of a new partition/subpartition in the object-level default tablespace of an existing partitioned object. However, the object-level default tablespace block size does not match the block size of the partitioned object. Action: Either (1) Modify the default tablespace of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. ORA-14522: Partition-level default tablespace string block size [string] for string string does not match existing string block size [string] Cause: A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object. Action: Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created. ORA-14523: Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string] Cause: A DDL statement was issued that would require a partition/subpartition of a local index/LOB column to be co-located with the corresponding partition/subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column/local index are different. Action: Either (1) Specify an object-level default tablespace (or partition-level default tablespace for the appropriate partition, if composite partitioning is used) for the partitioned local index/LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose block size does not match that of the base table. ORA-14551: cannot perform a DML operation inside a query Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave. Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave. ORA-14552: cannot perform a DDL, commit or rollback inside a query or DML Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement. Action: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation. ORA-14553: cannot perform a lob write operation inside a query Cause: A lob write operation cannot be performed inside a query or a PDML slave. Action: Ensure that the offending lob write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave. ORA-14601: Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template Cause: Cannot specify these clauses while specifying a template Action: Correct the subpartition template clause. ORA-14602: SUBPARTITION TEMPLATE is legal only for a composite partitioned table Cause: SUBPARTITION TEMPLATE can be specified only for composite partitioned tables Action: Do not use SUBPARTITION TEMPLATE on non-partitioned or non-composite partitioned tables. ORA-14603: [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables Cause: This syntax is valid only if subpartitioning dimension is hash Action: none ORA-14604: During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified Cause: Once a subpartition template has been specified during a CREATE TABLE it is illegal to specify SUBPARTITIONS or STORE IN anywhere else Action: Remove either the SUBPARTITIONS | STORE IN or remove the SUBPARTITION TEMPLATE clause ORA-14605: Name missing for subpartition / lob segment in template Cause: A subpartition / lob segment was not specified a name in the template descriptions Action: All subpartitions / lob segments must have names specified in the template ORA-14606: Tablespace was specified for previous subpartitions in template but is not specified for string Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions Action: Either specify tablespaces for all or for none of the subpartitions ORA-14607: Tablespace was not specified for previous subpartitions in template but is specified for string Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions Action: Either specify tablespaces for all or for none of the subpartitions ORA-14608: Tablespace was specified for the previous lob segments of column string in template but is not specified for string Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column Action: Either specify tablespaces for all or for none of the lob segments ORA-14609: Tablespace was not specified for the previous lob segments of column string in template but is specified for string Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column Action: Either specify tablespaces for all or for none of the lob segments ORA-14610: Lob attributes not specified for lob column string for subpartition string Cause: Lob attributes of a column must be specified for all subpartitions or must not be specified at all Action: Ensure lob attributes of a column are specified for all subpartitions or not specified at all ORA-14611: Duplicate subpartition name string in template Cause: A subpartition name cannot be duplicated within the template Action: Rename one of the subpartitions. ORA-14612: Duplicate lob segment name string for lob column string in template Cause: Two lob segments of the same column were given the same name in the template Action: Rename one of the lob segments ORA-14613: Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed Cause: Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier Action: Shorten either partition or template name. ORA-14614: List value "string" specified twice in subpartition "string" Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value ORA-14615: List value "string" specified twice in subpartitions "string", "string" Cause: A list value cannot be specified more that once Action: Remove one of the specifications of the value ORA-14616: table is not subpartitioned by List method Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD|DROP VALUES or ALTER TABLE DROP|SPLIT|MERGE SUBPARTITION can only be performed on List subpartitioned objects Action: Re-issue the command against a List subpartitoned object. ORA-14617: cannot add/drop values to DEFAULT subpartition Cause: A ADD/DROP VALUES operation is being done on the default subpartition Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition ORA-14618: cannot drop the last value of subpartition Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition Action: Cannot execute the command, unless two or more values exist for subpartition ORA-14619: resulting List subpartition(s) must contain at least 1 value Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value Action: Ensure that each of the resulting subpartitions contains atleast 1 value ORA-14620: DEFAULT subpartition already exists Cause: A subpartition already exists with DEFAULT value Action: Remove the DEFAULT value from the list specified ORA-14621: cannot add subpartition when DEFAULT subpartition exists Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists Action: Issue a SPLIT of the DEFAULT subpartition instead ORA-14622: Value string already exists in subpartition string Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition Action: Remove the duplicate value from the statement and try again ORA-14623: Value string does not exist in subpartition string Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition Action: Remove the value from the statement and try again ORA-14624: DEFAULT subpartition must be last subpartition specified Cause: A subpartition description follows the one describing the default subpartition Action: Ensure that the DEFAULT subpartition is the last subpartition description ORA-14625: subpartition contains rows corresponding to values being dropped Cause: table subpartition contains rows for the values being dropped. Action: DELETE all rows for the values being dropped and reissue statement ORA-14626: values being added already exist in DEFAULT subpartition Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added ORA-14627: Invalid operation was specified on a GLOBAL partitioned index Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index Action: Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned ORA-14628: specification of bounds is inconsistent with LIST method Cause: An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions ORA-14629: cannot drop the only subpartition of a partition Cause: A drop subpartition command is being executed when there is only one subpartition in the partition Action: none ORA-14630: subpartition resides in offlined tablespace Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint. Action: Bring tablespace online before attempting the operation. ORA-14631: the partition bounds do not match the subpartition bounds of the partition Cause: When exchanging a partitioned table with a composite partition the bounds that describe the partitions of the table must match the bounds that describe the subpartitions of the composite partition. Action: Ensure that the bounds describing partitions in the partitioned table is the same as the bounds of the subpartitions in the the composite partition. ORA-14632: cannot specify PARALLEL clause when adding a List subpartition Cause: User issued ALTER TABLE ADD SUBPARTITION statement with PARALLEL clause for a List subpartition of a Range/List partitioned object which is illegal Action: Remove the PARALLEL clause. ORA-14633: Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table. Action: Remove clause and reissue operation ORA-14634: Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table Cause: During a split or a merge of a partition of a range list partitioned table you cannot specify any subpartitioning information for the resulting partition (s) Action: Remove all subpartitioning information from the DDL. ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE Action: Ensure that the statement describes exactly one subpartition as the target that need to be MERGEd ORA-14636: only 2 resulting subpartition can be specified for SPLIT SUBPARTITION Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT Action: Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation ORA-14637: cannot merge a subpartition with itself Cause: The same subpartition name was specified twice for the merge operation Action: Re-submit operation with 2 distinct subpartition names within the same composite partition ORA-14638: cannot MERGE subpartitions in different Range Composite partitions Cause: Attempted to MERGE subpartitions in different Range Composite partitions Action: Reissue the command after ensuring that the 2 subpartitions being merged lie in the same composite partition ORA-14639: SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method Action: Reissue the command after ensuring that the SUBPARTITIONS clause is not specified, to specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause ORA-14640: add/coalesce index partition operation is valid only for hash partitioned global indexes Cause: User attempted to add or coalesce an index partition of a global index not partitioned by hash method. Action: Issue the statement on a global index partitioned by hash method. or if the index is partitioned by range method consider using split/drop instead of add/coalesce. ORA-14641: STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed" Action: Re-issue the stament after removing the STORE-IN clause ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the INCLUDING INDEXES option has been specified and the tables have different hakan factors. Action: Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable. ORA-14643: Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION Cause: Either records_per_block has been minimized for one of the tables to be exchanged, but not the other, or the hakan factors for the tables to be exchanged are not equal. Action: If records_per_block has been minimized for one of the tables, but not the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables, or perform alter table with the MINIMIZE RECORDS_PER_BLOCK for both tables. If the hakan factors do not match perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables. ORA-14644: table is not subpartitioned by Hash method Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects Action: Re-issue the command against a Hash subpartitoned object. ORA-14645: STORE IN clause cannot be specified for Range List objects Cause: A STORE IN clause was specified for Range List partitioned object Action: Re-issue the command after removng the STORE IN clause ORA-14646: Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes Cause: The first time a table is altered to include compression, it cannot have a usable bitmap index (partition). Subsequent alter table statements involving compression do not have this same restriction. Action: A) Drop any bitmap indexes defined on the table, and re-create them once the operation is complete or, B) Mark all index fragments of all bitmap indexes defined on the table UNUSABLE and rebuild them once the operation is complete. ORA-14700: Object(s) owned by SYS cannot be locked by non-SYS user Cause: Attempt to issue a LOCK TABLE statement on SYS owned object(s) by a non-SYS user, user should minimally have DML privileges Action: Re-issue LOCK TABLE statement for non-SYS user after granting DML privileges on object, or non-SYS user should connect as SYS ORA-15000: command disallowed by current instance type Cause: The user has issued a command to a conventional RDBMS instance that is only appropriate for an ASM instance. Alternatively, the user has issued a command to an ASM instance that is only appropriate for an RDBMS instance. Action: Connect to the correct instance type and re-issue the command. ORA-15001: diskgroup "string" does not exist or is not mounted Cause: An operation failed because the diskgroup specified does not exist or is not mounted by the current ASM instance. Action: Verify that the diskgroup name used is valid, that the diskgroup exists, and that the diskgroup is mounted by the current ASM instance. ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters Cause: The LOCK_NAME_SPACE initialization parameter contained a value that is too long. Action: Correct the LOCK_NAME_SPACE initialization parameter. ORA-15003: diskgroup "string" already mounted in another lock name space Cause: The diskgroup could not be mounted by the ASM instance because it was operating in a lockspace different than another existing Action: Check the LOCK_NAME_SPACE initialization parameter value, or dismount the diskgroup from the other ASM instances. ORA-15004: alias "string" does not exist Cause: The specified alias did not exist within the diskgroup. Action: Check the alias name and diskgroup name. ORA-15005: name "string" is already used by an existing alias Cause: An existing alias in the diskgroup used the same name. Action: Select another alias name, or drop the existing alias. ORA-15006: template "string" does not exist Cause: The specified template did not exist within the diskgroup. Action: Check the template name and diskgroup name. ORA-15007: name is already used by an existing template Cause: A template with the same name already exists. Action: Select another template name, or drop the existing template. ORA-15008: cannot drop system template Cause: The specified template was created by the system and must always exist for proper operation. Action: Select another template name. ORA-15009: ASM disk "string" does not exist Cause: The specified ASM disk was not found. Action: Check the ASM disk name. ORA-15010: name is already used by an existing ASM disk Cause: The specified name was already used in this diskgroup. Action: Specify a different ASM disk name. ORA-15011: failure group "string" contains no members Cause: The specified name did not match the failure group of any disks in the diskgroup. This usually indicates that the failure group name was specified incorrectly. Action: Check the failure group name. ORA-15012: ASM file "string" does not exist Cause: The ASM file was not found. Action: Check the ASM file name. ORA-15013: diskgroup "string" is already mounted Cause: An ALTER DISKGROUP MOUNT command specified the name of a diskgroup which is already mounted by the current ASM instance. Action: Check the name of the diskgroup. ORA-15014: location "string" is not in the discovery set Cause: The operating system path specified was outside the set of disks that are discovered by the instance. Action: Specify a operating system path within the set of disks that are discovered based upon the ASM_DISKSTRING parameter. Alternatively, check the setting of the ASM_DISKSTRING parameter. ORA-15017: diskgroup "string" cannot be mounted Cause: The specified diskgroup could not be mounted. Action: Check for additional errors reported. ORA-15018: diskgroup cannot be created Cause: The specified diskgroup could not be created. Action: Check for additional errors reported. ORA-15019: discovered duplicate path "string" for "string" Cause: The discovery encountered multiple paths to the same disk. Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk. ORA-15020: discovered duplicate ASM disk "string" Cause: The discovery encountered two disks claiming to be the same named ASM disk. Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk. ORA-15021: parameter "string" is not valid in string instance Cause: The specified parameter was not supported when starting an instance of this type. Action: Delete the specified parameter from the INIT.ORA file. ORA-15023: reached maximum allowable number of disks string Cause: An attempt was made to add another disk to a diskgroup which already contains the maximum number of disks allowed. Action: Consider dropping existing disks from the diskgroup before adding additional ones, or create a new diskgroup. ORA-15024: discovered duplicately numbered ASM disk string Cause: The discovery encountered two disks claiming to have the same ASM disk number. Action: Check that the ASM_DISKSTRING parameter specifies only a single path for each disk. ORA-15025: could not open disk "string" Cause: The specified disk could not be opened. Action: Check the additional error messages, if any. ORA-15026: disk "string" is not an ASM disk Cause: The disk did not contain a valid ASM disk header. Action: Check to see if the data on the disk has been changed by some system administrator action. ORA-15027: active use of diskgroup "string" precludes its dismount Cause: An ALTER DISKGROUP ... DISMOUNT command specified a diskgroup which had database client instances with open files in the diskgroup. Diskgroups cannot be dismounted until all open files in the diskgroup are closed by the database client instances. Action: Stop all clients that are using this diskgroup and retry the ALTER DISKGROUP ... DISMOUNT command. The V$ASM_CLIENT fixed view in an ASM instance provides a list of its active database client instances. ORA-15028: ASM file "string" not dropped; currently being accessed Cause: An attempt was made to drop an ASM file, but the file was being accessed by one or more database instances and therefore could not be dropped. Action: Shut down all database instances that might be accessing this file and then retry the drop command. ORA-15029: disk "string" is already mounted by this instance Cause: An attempt was made to add to a diskgroup a disk that was already mounted by the current instance as part of some (possibly other) diskgroup. Action: Specify a different disk in the command. Note that not even the FORCE option can be used to correct the situation until the diskgroup containing the disk becomes dismounted by this instance. ORA-15030: diskgroup name "string" is in use by another diskgroup Cause: A CREATE DISKGROUP command specfied a diskgroup name that was already assigned to another diskgroup. Action: Select a different name for the diskgroup. ORA-15031: disk specification "string" matches no disks Cause: The device specification string to a CREATE DISKGROUP command did not match any devices which could be discovered. Action: Check the device specification string matches a disk on the system. ORA-15032: not all alterations performed Cause: At least one ALTER DISKGROUP action failed. Action: Check the other messages issued along with this summary error. ORA-15033: disk "string" belongs to diskgroup "string" Cause: An attempt was made to ADD to a diskgroup a disk that was already part of another diskgroup, or an attempt was made to DROP / OFFLINE / ONLINE / CHECK a disk that was not part of the specified diskgroup. Action: For ADD, check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. For the other commands, check the name of the specified disk. ORA-15034: disk "string" does not require the FORCE option Cause: An attempt was made to add the disk to the diskgroup using the FORCE option. The disk was not found to be in use at the present time, so the FORCE option was not permitted. Action: Avoid gratuitous use of the FORCE option. ORA-15035: no disks belong to diskgroup "string" Cause: An attempt was made to mount a diskgroup for which no member disks were discovered. Action: Specify a valid diskgroup name that contains disks. ORA-15036: disk "string" is truncated Cause: The size of the disk, as reported by the operating system, was smaller than the size of the disk as recorded in the disk header block on the disk. Action: Check if the system configuration has changed. ORA-15037: disk "string" is smaller than mimimum of string MBs Cause: The size of the disk, as reported by the operating system, was too small to allow the disk to become part of the diskgroup. Action: Check if the system configuration is correct. ORA-15038: disk "string" size mismatch with diskgroup [string] [string] [string] Cause: An attempt was made to mount into a diskgroup a disk whose recorded allocation unit size, metadata block size, or physical sector size was inconsistent with the other diskgroup members. Action: Check if the system configuration has changed. ORA-15039: diskgroup not dropped Cause: An attempt to drop a diskgroup failed. Action: See the associated messages for details about why the drop was not successful. ORA-15040: diskgroup is incomplete Cause: Some of the disks comprising a diskgroup were not present. Action: Check the hardware to ensure that all disks are functional. Also check that the setting of the ASM_DISKSTRING initialization parameter has not changed. ORA-15041: diskgroup space exhausted Cause: The diskgroup ran out of space. Action: Add more disks to the diskgroup, or delete some existing files. ORA-15042: ASM disk "string" is missing Cause: The specified disk, which is a necessary part of a diskgroup, could not be found on the system. Action: Check the hardware configuration. ORA-15043: ASM disk "string" is not a diskgroup member Cause: The specified disk has been removed from the diskgroup, but a disk matching its name was found. Action: Check the hardware configuration. ORA-15044: ASM disk "string" is incorrectly named Cause: Either the specified disk had its contents changed such that it no longer contained an ASM disk name in its header that matches the diskgroup information or its FAILGROUP information may have become inconsistent. Action: Drop the disk from the diskgroup. ORA-15045: ASM file name "string" is not in reference form Cause: The ASM file name was not in a form that can be used to reference an existing file because a file/incarnation number or an alias name was not present or a template name was included. Action: Correct the specified ASM file name. ORA-15046: ASM file name "string" is not in single-file creation form Cause: The ASM file name was not in a form that can be used to create an single file because a file/incarnation number was present. Action: Correct the specified ASM file name. ORA-15047: ASM file name "string" is not in multiple-file creation form Cause: The ASM file name was not in a form that can be used to create multiple files because either a fully-qualified file name or an alias name was present. Action: Correct the specified ASM file name. ORA-15048: ASM internal files cannot be deleted Cause: An attempt was made to delete a metadata file used by ASM to manage the diskgroup. Action: Check the specified ASM file name. ORA-15049: diskgroup "string" contains string error(s) Cause: Errors were discovered by the ALTER DISKGROUP CHECK command. Action: See the alert log for details of the errors. ORA-15050: disk "string" contains string error(s) Cause: Errors were discovered by the ALTER DISKGROUP CHECK DISK command. Action: See the alert log for details of the errors. ORA-15051: file "string" contains string error(s) Cause: Errors were discovered by the ALTER DISKGROUP CHECK FILE command. Action: See the alert log for details of the errors. ORA-15052: ASM file name "string" is not in diskgroup "string" Cause: The ASM file name did not contain a diskgroup name that specified the correct diskgroup as implied by the other arguments to the command. Action: Correct the specified ASM file name or diskgroup name. ORA-15053: diskgroup "string" contains existing files Cause: An attempt was made to drop a diskgroup that still contains existing files. Action: Specify the INCLUDING CONTENTS option to drop the diskgroup and all of its existing files. ORA-15054: disk "string" does not exist in diskgroup "string" Cause: An attempt was made to DROP (or CHECK) a disk that is not part of the specified diskgroup. Action: Check the name of the specified disk and the specified diskgroup. ORA-15055: unable to connect to ASM instance Cause: When accessing a diskgroup for the first time, the database was unable to connect to the required ASM instance. Action: Check the additional error messages. May need to configure correct ASM sid or make sure the database instance has OS privileges for ASM SYSDBA. ORA-15056: additional error message Cause: An operating system error occured. Action: Correct the operating system error and retry the operation. ORA-15057: specified size of string MB is larger than actual size of string MB Cause: A disk size expression exceeded the amount of storage actually availalable, as reported by the operating system. Action: Specify a valid size. ORA-15058: disk "string" belongs to an incompatible diskgroup Cause: An attempt was made to ADD to a diskgroup a disk which was already part of another diskgroup. The other diskgroup was written by a more recent software release. Action: Check the path specifier for the disk. If it is certain that the disk is not in use by another diskgroup, the FORCE option may be used to override this check. ORA-15059: invalid device type for ASM disk Cause: The device type of the discovered disk was not valid for use as an ASM disk. Action: Check the file path and retry or exclude it from the discovery set. See the accompanying operating system error for additional information. ORA-15060: template "string" does not exist Cause: A command specified a template name, either directly or as part of an ASM file name, which did not exist. Action: Check the template specifier in the command. ORA-15061: ASM operation not supported [string] Cause: An ASM operation was attempted that is invalid or not supported by this version of the ASM instance. Action: This is an internal error code that is used for maintaining compatibility between software versions and should never be visible to the user; contact Oracle support Services. ORA-15062: ASM disk is globally closed Cause: The disk to which the I/O request was issued has gone offline or has been globally closed by the background process. Check other messages in the trace files for more information. Action: Bring the disk online for I/Os to get through. ORA-15063: ASM discovered an insufficient number of disks for diskgroup "string" Cause: ASM was unable to find a sufficient number of disks belonging to the diskgroup to continue the operation. Action: Check that the disks in the diskgroup are present and functioning, that the owner of the ORACLE binary has read/write permission to the disks, and that the ASM_DISKSTRING initialization parameter has been set correctly. Verify that ASM discovers the appropriate disks by querying V$ASM_DISK from the ASM instance. ORA-15064: communication failure with ASM instance Cause: There was a failure to communicate with the ASM instance, most likely because the connection went down. Action: Check the accompanying error messages for more information on the reason for the failure. Note that database instances will always return this error when the ASM instance is terminated abnormally. ORA-15065: hash collision for diskgroup names "string" and "string" Cause: There was a collision in the group name used for the diskgroup. The diskgroup(s) cannot be mounted using colliding names. Action: Use a different diskgroup name and also report to Oracle Support Services the two diskgroup names which collided. ORA-15066: offlining disk "string" may result in a data loss Cause: Following I/O failures, the disks holding all copies of a data block were attempted to be taken offline. Action: Check the accompanying error messages for more information on the reason for the disk I/O failures. ORA-15067: command or option incompatible with diskgroup redundancy Cause: An attempt was made to use a feature which is not permitted by the diskgroup"s redundancy policy. Common examples are forcibly dropping a disk from an EXTERNAL REDUNDANCY diskgroup, using the FAILGROUP clauses with an EXTERNAL REDUNDANCY diskgroup, or using invalid template attributes. Action: Omit the option from the command. ORA-15068: maximum number of diskgroups string already mounted Cause: An attempt was made to mount more diskgroups than the instance is capable of mounting at one time. Action: Dismount a mounted diskgroup and retry the command. ORA-15069: ASM file "string" not accessible; timed out waiting for lock Cause: An attempt was made to access an ASM file, but the file is currently being created, resized, or deleted and therefore cannot be accessed. Action: No action required, or try again later, after the create or resize has completed. ORA-15070: maximum number of files string exceeded in diskgroup "string" Cause: The diskgroup ran out of space. Action: Delete some existing ASM files or create files in a new diskgroup. ORA-15071: ASM disk "string" is already being dropped Cause: An attempt was made to drop a disk from a diskgroup which was already in the process of being dropped from the diskgroup. Alternatively, an attempt was made to forcibly drop a disk from a diskgroup using the FORCE option which was already being forcibly dropped from the diskgroup. Action: Check the ASM disk name and FORCE option as specified in the command. ORA-15072: command requires at least string failure groups, discovered only string Cause: An attempt was made to create either a normal redundancy diskgroup for which fewer than two failure groups were both specified and discovered, or a high redundancy diskgroup for which fewer than three failure groups were both specified and discovered. Action: Check the that the command does specify the required number of failure groups, and that all of the specified disks are discovered by ASM. A query of the V$ASM_DISK fixed view will show which disks are discovered by ASM. ORA-15073: diskgroup string is mounted by another ASM instance Cause: An attempt was made to drop a diskgroup that is still mounted somewhere in the cluster by another instance. Action: dismount the diskgroup from all nodes except the one performing the drop diskgroup command. ORA-15074: diskgroup string requires rebalance completion Cause: An attempt was made to repeatedly add or drop disks from a diskgroup. ASM could not perform the operation given the current state of the diskgroup. Action: Manually invoke the ALTER DISKGROUP REBALANCE command and allow the rebalance to run to completion. Alternatively, invoke the ALTER DISKGROUP UNDROP DISKS command and allow the rebalance to run to completion. After the rebalance has completed, retry the operation. ORA-15075: disk(s) are not visible cluster-wide Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could not be discovered by one or more nodes in a RAC cluster configuration. Action: Determine which disks are causing the problem from the GV$OSM_DISK fixed view. Check operating system permissions for the device and the storage sub-system configuration on each node in a RAC cluster that cannot identify the disk. ORA-15076: Emulating I/O errors on the OSM disk Cause: The disk to which the I/O request was issued is in an error emulation mode. Action: Bring the disk online for I/Os to get through. ORA-15077: could not locate ASM instance serving a required diskgroup Cause: The instance failed to perform the specified operation because it could not locate a required ASM instance. Action: Start an ASM instance and mount the required diskgroup. ORA-15078: ASM diskgroup was forcibly dismounted Cause: The diskgroup to which the I/O request was issued was forcibly dismounted (with the ALTER DISKGROUP DISMOUNT FORCE command) so that it could not be accessed. Action: Mount the diskgroup to allow access again. ORA-15079: ASM file is closed Cause: The file to which the I/O request was issued was closed. This could have been a consequence of the diskgroup being dismounted. Action: Make sure the diskgroup is mounted and the file is open. ORA-15080: synchronous I/O operation to a disk failed Cause: A synchronous I/O operation invoked on a disk has failed. Action: Make sure that all the disks are operational. ORA-15081: failed to submit an I/O operation to a disk Cause: A submission of an I/O operation to a disk has failed. Action: Make sure that all the disks are operational. ORA-15082: ASM failed to communicate with database instance Cause: There was a failure when ASM tried to communicate with a database instance (most likely because the connection went down). Action: Check the accompanying error messages for more information on the reason for the failure. Note that the ASM instances may return this error when a database instance is terminated abnormally. ORA-15083: failed to communicate with ASMB background process Cause: A database instance failed to communicate with its ASMB background process when attempting to access an ASM file. Action: Check the alert log for more information on the reason for the failure. ORA-15090: handle string is not a valid descriptor Cause: The file handle was not valid in this session. Action: Submit a handle obtained from a successful call to DBMS_DISKGROUP.OPEN(). ORA-15091: operation incompatible with open handle in this session Cause: The current session contained an open handle from the DBMS_DISKGROUP PL/SQL package which precluded performing the command. Action: Close the hanlde with DBMS_DISKGROUP.CLOSE() before executing the command, or execute the command in a different session. ORA-15092: I/O request size string is not a multiple of logical block size string Cause: The length of the request was not a multiple of logical block size. Action: Correct the error and retry the operation. ORA-15093: buffer only contains string bytes, I/O requested is string bytes Cause: The buffer supplied for write was too small to satisfy the request. Action: Correct the error and retry the operation. ORA-15094: attempted to write to file opened in read only mode Cause: The file handle passed to DBMS_DISKGROUP.WRITE() did not have write privileges. Action: Obtain a file handle in read-write mode and retry the write operation. ORA-15095: reached maximum ASM file size (string GB) Cause: An ASM file creation or file resize operation exceeded the maximum file size permitted by ASM. Action: Use smaller files. ORA-15096: lost disk write detected Cause: A failure either by disk hardware or disk software caused a disk write to to be lost, even though ASM received acknowledgement that the write completed. Alternatively, a clustering hardware failure or a clustering software failure resulted in an ASM instance believing that another ASM instance had crashed, when in fact it was still active. Action: The disk group is corrupt and cannot be recovered. The disk group must be recreated, and its contents restored from backups. ORA-15097: cannot SHUTDOWN ASM instance with connected RDBMS instance Cause: A SHUTDOWN command was issued to an ASM instance that had one or more connected RDBMS instances. Action: Connect to each RDBMS instance and shut it down, and then reissue the SHUTDOWN command to the ASM instance. Alternatively, use the SHUTDOWN ABORT command. Note that issuing the SHUTDOWN ABORT command to an ASM instance results in abormal termination of all RDBMS instances connected to that ASM instance. ORA-15100: invalid or missing diskgroup name Cause: The command did not specify a valid diskgroup name. Action: Specify a valid diskgroup name. ORA-15101: no action specified Cause: The ALTER DISKGROUP command did not specify any alterations. Action: Specify at least one operation clause. ORA-15102: invalid POWER expression Cause: The syntax of the POWER expression was invalid. Action: Specify a valid POWER expression. ORA-15103: conflicting or duplicate REPAIR options Cause: The command specified conflicting or duplicate REPAIR keywords. Action: Specify only one REPAIR action. ORA-15104: conflicting CONTENTS options Cause: The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options. Action: Specify only one option. ORA-15105: missing or invalid FAILGROUP name Cause: The command did not specify a valid failure group name. Action: Specify a valid failure group name. ORA-15106: missing or invalid operating system disk locator string Cause: The command did not specify a valid operating system path for the device as a string. Action: Specify a valid operating system path for the device. ORA-15107: missing or invalid ASM disk name Cause: The command did not specify a valid ASM disk name identifier. Action: Specify a valid ASM disk name identifier. ORA-15108: missing or invalid template name Cause: The command did not specify a valid template name identifier. Action: Specify a valid template name identifier. ORA-15109: conflicting protection attributes specified Cause: The command contained an invalid combination of the UNPROTECTED, MIRROR, or PARITY keywords. Action: Specify only one keyword. ORA-15110: no diskgroups mounted Cause: No diskgroups were specified in the ASM_DISKGROUPS parameter, so instance startup or the ALTER DISKGROUP ALL MOUNT command did not mount any diskgroups. Action: Specify valid diskgroups in the ASM_DISKGROUPS parameter or ignore the error. ORA-15111: conflicting or duplicate STRIPE options Cause: The command contained both a FINE and COARSE keyword, or contained the FINE keyword more than once, or contained the COARSE keyword more than once. Action: Specify only one keyword. ORA-15112: No diskgroups are currently mounted. Cause: An ALTER DISKGROUP ALL command did not find any mounted diskgroups upon which to operate. Either instance shutdown or an ALTER DISKGROUP ALL DISMOUNT command did not dismount any diskgroups, or an ALTER DISKGROUP ALL UNDROP DISKS command did not undrop any disks. Action: Mount the diskgroups on which you wish to operate or ignore the error. ORA-15113: alias name "string" refers to a directory Cause: The name specified referred to a directory in the alias directory and not a valid alias entry. Action: Check the alias name and retry. ORA-15114: missing or invalid ASM file name Cause: The command did not specify a valid ASM file name identifier. Action: Specify a valid ASM file name identifier. ORA-15115: missing or invalid ASM disk size specifier Cause: The command did not specify a valid ASM disk size. Action: Specify a valid ASM disk size. ORA-15116: invalid combination of ALTER DISKGROUP options Cause: The ALTER DISKGROUP options may not be combined in this manner. Action: Issue separate ALTER DISKGROUP commands to accomplish the desired action. ORA-15117: command only operates on one diskgroup Cause: An ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP command specified a list of diskgroups or the keyword ALL in a context where only a single diskgroup was permitted. Action: Issue separate ALTER DISKGROUP, CREATE DISKGROUP, or DROP DISKGROUP commands to accomplish the desired action. ORA-15120: ASM file name "string" does not begin with the ASM prefix character Cause: A file name was specified to ASM which did not begin with the ASM prefix character (currently "+"). ASM uses the prefix to determine that a file specification is in fact an ASM file. Action: Correct the file name specification. ORA-15121: ASM file name "string" contains an invalid diskgroup name Cause: A file name was specified that did not contain a valid diskgroup name. The diskgroup name follows immediately after the ASM prefix character. It must start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters "$" and "_". Action: Correct the file name specification. ORA-15122: ASM file name "string" contains an invalid file number Cause: A numeric file name was specified which did not contain a valid ASM file number. The ASM file number follows immediately after the diskgroup name. It must be preceeded by a "." character, and contain only numeric characters. Action: Correct the file name specification. ORA-15123: ASM file name "string" contains an invalid incarnation number Cause: A numeric file name was specified which did not contain a valid ASM incarnation number. The ASM incarnation number follows immediately after the ASM file number. It must be preceeded by a "." character, and contain only numeric characters. Action: Correct the file name specification. ORA-15124: ASM file name "string" contains an invalid alias name Cause: A file name was specified which did not contain a valid ASM alias name. The ASM alias name, if present, follows immediately after the diskgroup name, in place of the ASM file number. It must be preceeded by a slash, start with an alphabetic character, and consist of up to 48 characters which are alphabetic, numeric, or the characters "$", "_", "-", or "#". A space can separate two parts of an alias name. Action: Correct the file name specification. ORA-15125: ASM file name "string" contains an invalid template name Cause: A file name was specified to ASM which did not contain a valid template name. The template name, if present, follows immediately after the ASM incarnation number or the ASM alias name, if such is used in place of the ASM file number. It must be enclosed in parenthesis, start with an alphabetic character, and consist of up to 30 characters which are alphabetic, numeric, or the characters "$" and "_". Action: Correct the file name specification. ORA-15126: component within ASM file name "string" exceeds maximum length Cause: The maximum identifier length of 30 characters was exceeded for the diskgroup name, template name, or alias name field within the ASM file name. Action: Correct the file name specification. ORA-15127: ASM file name "string" cannot use templates Cause: A fully qualified ASM file name was specified. Such a specification does not permit the inclusion of a template name in the ASM file name. Action: Correct the file name specification. ORA-15128: ASM file name "string" exceeds maximum length string Cause: The maximum ASM file name length of 256 characters was exceeded for the combination of diskgroup name, file number, template name, alias name plus punctuation within the ASM file name. Action: Correct the file name specification. ORA-15129: entry "string" does not refer to a valid directory Cause: The entry indicated did not refer to a directory. Attempt was made to access the contents of this directory. Action: Correct the error and try again. ORA-15130: diskgroup "string" is being dismounted Cause: The diskgroup is being dismounted by request or because an I/O error was encountered that could not be handled by taking the disks offline. A disk cannot be offlined whenever doing so could result in all copies of a redundant extent being unavailable. Action: Repair the hardware problem and re-mount the diskgroup. Refer to the alert log to determine which disks have failed. ORA-15131: block string of file string in diskgroup string could not be read Cause: A block could not be read because the disk containing the block is either offline or an I/O error occured while reading the block. If this is mirrored file, then all disks that contain a copy of the block are either offline or received errors. Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed. ORA-15132: block string of file string in diskgroup string could not be written Cause: A block could not be written because the disk containing the block is either offline or an I/O error occured while writing the block. If this is mirrored file, then insufficient disks which contain a copy of the block are either offline or received errors. Action: Repair the affected disk and bring it back online. Refer to accompanying error messages to determine which disk has failed. ORA-15133: instance recovery required for diskgroup string Cause: An instance in the cluster crashed making instance recovery necessary. Action: None. This error should not normally be seen by an ASM client. ASM will trap this error and retry the operation after doing instance recovery automatically. ORA-15150: instance lock mode "string" conflicts with other ASM instance(s) Cause: Some other ASM instance used the lock name space in a conflicting mode. Action: Shut down the other instance or start up in compatible mode. Alternatively, set the DB_UNIQUE_NAME initialization parameter to avoid the conflict. ORA-15151: missing or invalid version number for rolling upgrade or downgrade Cause: The command did not sepcify a valid version number. Action: Correct the version number in the command. It should be of the form v#.#.#.#.# or other forms with fewer numbers delimited by a period. The version number must be different from the current software version of the instance. ORA-15152: cluster in rolling upgrade Cause: The cluster was already in the middle of rolling upgrade. Action: Rolling upgrade needs to be stopped before attempting to start again. ORA-15153: cluster not in rolling upgrade Cause: The cluster was not in rolling upgrade. Action: Start the rolling upgrade using the ALTER SYSTEM START ROLLING command. ORA-15154: cluster rolling upgrade incomplete Cause: The cluster was still performing rolling upgrade. Action: Ensure that all the instances in the cluster are upgraded before retrying the command. ORA-15155: version incompatible with the cluster Cause: The current software version of the instance was incompatible with the other members of the cluster. Action: Make sure that all the members of the cluster are at the same version. If you are attempting to perform rolling upgrade, execute ALTER SYSTEM START ROLLING command. Ensure that the version being upgraded to is compatible with the existing version of the cluster. ORA-15156: cluster in rolling upgrade from version [string] to [string] Cause: The current software version of the instance was incompatible with the rolling upgrade operation of the cluster. Action: The version number of new member instance must be one of the two versions involved in the rolling upgrade. ORA-15157: rolling upgrade or downgrade is not allowed Cause: The cluster was not capable of handling ASM rolling upgrade or downgrade. Action: The Oracle Cluster Services is using vendor clusterware. Oracle cannot perform rolling upgrade or downgrade using vendor cluster ware. Restart ASM instances using Oracle cluster ware and retry the operation. ORA-15158: rolling upgrade prevented by string Cause: One or more instances were blocking the rolling upgrade. Action: Terminate or wait until the reported operation is complete before attempting the rolling upgrade to the cluster. ORA-15162: cluster in rolling downgrade Cause: The cluster was already in the middle of rolling downgrade. Action: Rolling downgrade needs to be stopped before attempting to start again. ORA-15163: cluster not in rolling downgrade Cause: The cluster was not in rolling downgrade. Action: Start the rolling downgrade using the ALTER SYSTEM START ROLLING command. ORA-15164: cluster rolling downgrade incomplete Cause: The cluster was still performing rolling downgrade. Action: Ensure that all the instances in the cluster are downgraded before retrying the command. ORA-15166: cluster in rolling downgrade from version [string] to [string] Cause: The current software version of the instance was incompatible with the rolling downgrade operation of the cluster. Action: The version number of new member instance must be one of the two versions involved in the rolling downgrade. ORA-15168: rolling downgrade prevented by string Cause: One or more instances were blocking the rolling downgrade. Action: Terminate or wait until the reported operation is complete before attempting the rolling downgrade to the cluster. ORA-15169: destination "string" is a subdirectory of "string" Cause: Attempt to rename directory failed because the new directory name was a subdirectory of the original directory. Action: Correct the path of the destination and try again. ORA-15170: cannot add entry "string" in directory "string" Cause: Other errors prevented directory/alias creation. Action: Correct the errors and try again. ORA-15171: invalid syntax in the alias path after "string" Cause: An invalid alias/directory name syntax was specified. Action: Correct the alias path and try again. ORA-15173: entry "string" does not exist in directory "string" Cause: The specified alias did not exist in the given directory. Action: Correct the alias path and try again. ORA-15175: cannot create alias for diskgroup metadata file "string" Cause: An attempt was made to create an alias for a diskgroup metadata file. Action: Correct the alias path and try again. ORA-15176: file "string" already has an alias associated with it Cause: An attempt was made to create an alias for a file that already had an existing alias. Action: Correct the file name and try again or drop existing alias. ORA-15177: cannot operate on system aliases Cause: An attempt was made to modify a system alias. Action: Correct the alias name and try again. ORA-15178: directory "string" is not empty; cannot drop this directory Cause: An attempt was made to drop a directory that contained valid entries. Action: Correct the directory path or specify the FORCE option to drop a directory that is not empty. ORA-15179: missing or invalid alias name Cause: The command did not specify a valid alias identifier. Action: Specify a valid alias identifier. ORA-15180: Could not open dynamic library string, error [string] Cause: The library was not accessible Action: Correct the permissions of the library and try again. ORA-15181: Symbol [string] not found in library string, error [string] Cause: An error was encountered while loading the specified ASMLIB symbol. Action: Correct the error reported and try again. ORA-15182: ASMLIB [string] version mismatch, ORACLE version [string] Cause: The ASMLIB version reported is not supported by the ORACLE binary. Action: Install the correct library and try again. ORA-15183: ASMLIB initialization error [string] Cause: Unable to initialize the ASMLIB in ORACLE. Action: Contact ASMLIB library vendor support with the error details. ORA-15184: ASMLIB error could not be determined [string] [string] Cause: An error was encountered which cannot be diagnosed further. Action: Contact ASMLIB libary vendor for support. ORA-15185: Could not close dynamic library string, error [string] Cause: Could not close the dynamic library. Action: Contact ASMLIB libary vendor for support. ORA-15186: ASMLIB error function = [string], error = [string], mesg = [string] Cause: An error occured during a call to function listed in the error. Action: The detailed message associated with the error is listed along with the error. Correct the error and try again or contact ASMLIB library vendor for support. ORA-15190: Internal ASM testing event number 15190 Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM disks encounter rebalance IO errors. ORA-15191: Internal ASM testing event number 15191 Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM errors are emulated. ORA-15192: invalid ASM disk header [string] [string] [string] [string] [string] Cause: ASM encountered an invalid disk header. Action: Contact Oracle Support Services. ORA-15193: Internal ASM tracing event number 15193 Cause: Set this event only under the supervision of Oracle development. Action: None. ORA-15194: Internal ASM-DB interaction testing event number 15194 Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM-DB operation is interuppted. ORA-15195: Internal ASM testing event number 15195 Cause: Set this event only under the supervision of Oracle development. Action: The level controls which ASM errors are simulated. ORA-15196: invalid ASM block header [string:string] [string] [string] [string] [string != string] Cause: ASM encountered an invalid metadata block. Action: Contact Oracle Support Services. ORA-15197: suppressing string additional ASM messages Cause: The ASM command generated so many erorrs that this summary message was reported in place of many individual messages. Action: If the command contained multiple actions, try separating each action into its own command and executing each command by itself. Otherwise, try not to generate so many errors. ORA-15198: operation string is not yet available Cause: An unimplemented operation was attempted. Action: Consider upgrading to later releases as they become available. ORA-15199: Internal ASM tracing event number 15199 Cause: Set this event only under the supervision of Oracle development. Action: Traces execution of ASM. Level indicates verbosity of tracing. ORA-15200: initialization parameter string (string) is not a power of two Cause: The value specified for this initialization parameter was not a power of two. Action: Correct the initialization parameter value and restart the instance. ORA-15201: disk string contains a valid RDBMS file Cause: A disk specified in a CREATE DISKGROUP or ALTER DISKGROUP ... ADD DISK command appeared to contain a file from an existing database. By default, ASM will not allow a diskgroup to be created using this disk, as a safeguard against damaging an existing database. Action: Check that the ASM disk specification is correct. Otherwise, when storage from a defunct database is reused as part of an ASM diskgroup, specify the FORCE option to the ASM SQL command. ORA-15202: cannot create additional ASM internal change segment Cause: The mount of a diskgroup by an additional instance in a RAC cluster required more space for internal use by ASM than was available in the diskgroup. Action: Delete unused files from the diskgroup or add additional disks to the diskgroup and retry the operation. ORA-15203: diskgroup string contains disks from an incompatible version of ASM Cause: Diskgroup was created by an ASM instance with a higher compatibility setting. Action: Use an ASM instance with the appropriate software version to mount the diskgroup. ORA-15204: database version string is incompatible with diskgroup string Cause: The database compatibility of the diskgroup was advanced to a later version. Action: Upgrade the database instance to appropriate version of ORACLE. ORA-15205: requested mirror side unavailable Cause: The requested mirror side of a block is either unallocated or allocated on a disk that has been dropped from the diskgroup. Action: Resubmit the request or try another mirror side. ORA-15206: duplicate diskgroup string specified Cause: A command specified the same diskgroup twice. Action: Specify each diskgroup only once. ORA-16000: database open for read-only access Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error. Action: In order to modify the database, it must first be shut down and re-opened for read-write access. ORA-16001: database already open for read-only access by another instance Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance. Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access. ORA-16002: database already open for read-write access by another instance Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance. Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access. ORA-16003: standby database is restricted to read-only access Cause: To ensure its integrity, a standby database can only be opened for read-only access. Action: Re-issue the ALTER DATABASE OPEN specifying READ ONLY. ORA-16004: backup database requires recovery Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance. Action: Perform the necessary recovery and re-open for read-only access. ORA-16005: database requires recovery Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance. Action: Perform the necessary recovery and re-open for read-only access. ORA-16006: audit_trail destination incompatible with database open mode Cause: The audit_trail initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access. Action: When the database is opened for read-only access, the audit_trail initialization parameter can only be set to "OS" or "NONE" (FALSE). ORA-16007: invalid backup control file checkpoint Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access. Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access. ORA-16008: indeterminate control file checkpoint Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access. Action: First open the database for read-write access which will result in valid control file checkpoint. Then re-open the database for read-only access. ORA-16009: remote archive log destination must be a STANDBY database Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances. Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. ORA-16011: Archivelog Remote File Server process in Error state Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data. Action: Correct the problem at the standby database site. ORA-16012: Archive log standby database identifier mismatch Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. ORA-16013: log string sequence# string does not need archiving Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived. Action: No action is required. ORA-16014: log string sequence# string not archived, no available destinations Cause: 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. Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred. ORA-16015: log string sequence# string not archived, media recovery disabled Cause: 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. Action: Disable the standby destination or enable media recovery and retry. ORA-16016: archived log for thread string sequence# string unavailable Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file. Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command. ORA-16017: cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination Cause: The parameter LOG_ARCHIVE_DUPLEX_DEST was set to a non-NULL value when the primary archive destination was set to NULL explicitly. Action: Set the primary archive destination to a valid non-NULL value. ORA-16018: cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when a LOG_ARCHIVE_DEST_n (n = 1...10) parameter was encountered while fetching initialization parameters. 2) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 3) A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM command was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter. 4) Parameter DB_RECOVERY_FILE_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST. Action: Eliminate any incompatible parameter definitions. ORA-16019: cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST Cause: One of the following events caused an incompatibility: 1) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when the specified LOG_ARCHIVE_DEST_n (n = 1...10) or DB_RECOVERY_FILE_DEST parameter was encountered while fetching initialization parameters. 2) Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST parameter. 3) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters. 4) An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter. Action: Eliminate any incompatible parameter definitions. ORA-16020: less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST Cause: 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. Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST. ORA-16021: session string destination cannot be the same as session string destination Cause: 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. Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters. ORA-16022: LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL Cause: An attempt was made to change parameter LOG_ARCHIVE_DEST to NULL when parameter LOG_ARCHIVE_DUPLEX_DEST is non-NULL. Action: Either set parameter LOG_ARCHIVE_DEST to a non-NULL value, or set parameter LOG_ARCHIVE_DUPLEX_DEST to a NULL value. ORA-16023: system string destination cannot be the same as session string destination Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter 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 command. 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. Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter. ORA-16024: parameter string cannot be parsed Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter 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. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. ORA-16025: parameter string contains repeated or conflicting attributes Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained either repeated attributes or attributes that conflicted with each other. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. ORA-16026: parameter string contains an invalid attribute value Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained an attribute with an invalid value. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. ORA-16027: parameter string is missing a destination option Cause: The value for the indicated LOG_ARCHIVE_DEST_n (n = 1...10) parameter failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attrbute. Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires Cause: 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...10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value. Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. ORA-16029: cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations. Action: Define one or more log archive destinations using parameters LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n (n = 1...10). Then, change the value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination Cause: 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 command. Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters. ORA-16031: parameter string destination string exceeds string character limit Cause: The value for the specified parameter contained a destination string that is too long. Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message. ORA-16032: parameter string destination string cannot be translated Cause: The value for the specified parameter contained a destination string that could not be translated. Action: Use a valid destination string in the specified parameter. ORA-16033: parameter string destination cannot be the same as parameter string destination Cause: 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. Action: Specify a different value for one of the archive log parameters. ORA-16034: FROM parameter is incompatible with MANAGED recovery Cause: Use of the FROM "location" parameter is not allowed when MANAGED recovery has been specified. Action: Correct the syntax and retry the command. ORA-16035: missing required keyword string Cause: The indicated keyword is required but was not specified. Action: Correct the syntax and retry the command. ORA-16036: invalid MANAGED recovery CANCEL option Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement. Action: Specify either nothing or IMMEDIATE following CANCEL. ORA-16037: user requested cancel of managed recovery operation Cause: The managed standby database recovery operation has been canceled per user request. Action: No action is required. ORA-16038: log string sequence# string cannot be archived Cause: 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. Action: No action is required. ORA-16039: RFS request version mismatch Cause: 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. Action: Verify that compatible versions of Oracle are running on the primary and all standby sites. ORA-16040: standby destination archive log file is locked Cause: 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. Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database. ORA-16041: Remote File Server fatal error Cause: 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. Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible take corrective action. ORA-16042: user requested cancel immediate of managed recovery operation Cause: 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. Action: No action is required. ORA-16043: managed recovery session canceled Cause: The standby database managed recovery operation has been canceled per user request or operation timeout. Action: More specific messages will accompany this message. ORA-16044: destination string attribute cannot be specified at session level Cause: An archive log destination attribute was attempted to be modified at the session level. Action: Use the ALTER SYSTEM command to modify the destination attribute. ORA-16045: circular archive log destination dependency chain Cause: An archive log destination contains a dependency to another archive log destination that also contains a dependency. Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes. ORA-16046: Archive log destination failed due to failed dependent destination Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails. Action: No action required. ORA-16047: DGID mismatch between destination setting and standby Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination. Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination. ORA-16050: destination exceeded specified quota size Cause: 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. Action: No action is required. ORA-16051: parameter string contains an invalid delay time Cause: 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). Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter. ORA-16052: DB_UNIQUE_NAME attribute is required Cause: The DB_UNIQUE_NAME attribute is required when DG_CONFIG is enabled. Action: Use the DB_UNIQUE_NAME attribute to specify a valid Data Guard Name for the destination. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. ORA-16053: DB_UNIQUE_NAME string is not in the Data Guard Configuration Cause: The specified DB_UNIQUE_NAME is not in the Data Guard Configuration. Action: If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance. ORA-16055: FAL request rejected Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons. Action: to solve the problem. ORA-16056: backup control file archival requires proper syntax Cause: 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. Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required. ORA-16057: DGID from server not in Data Guard configuration Cause: The Data Guard name of the primary database or the FAL server is not in the Data Guard configuration of the standby. Action: In order for the primary database or the FAL server to archive logs to the standby database, the Data Guard name of the primary or FAL server must be in the Data Guard configuration of the standby. ORA-16058: standby database instance is not mounted Cause: The RFS process on the standby database received an internal error. Action: Check the standby alert log and RFS trace files for more information. ORA-16059: Log file is empty or invalid next available block Cause: Archiving not allowed of an empty or invalid log file. Action: No action is required. ORA-16060: Log file is current Cause: The current log file cannot be archived using its file name. Action: No action is required. ORA-16061: Log file status has changed Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation. Action: No action is required. ORA-16062: DGID from standby not in Data Guard configuration Cause: The Data Guard name from the standby is not in the Data Guard configuration of the server. Action: In order for the server to be allowed to archive logs to the standby, the Data Guard name of the standby must be in the Data Guard configuration of the server. ORA-16063: remote archival is enabled by another instance Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance. Action: Set the REMOTE_ARCHIVE_ENABLE parameter to TRUE and restart this instance. ORA-16064: remote archival is disabled by another instance Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance. Action: Set the REMOTE_ARCHIVE_ENABLE parameter to FALSE and restart this instance. ORA-16065: remote archival disabled at standby destination Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database. Action: 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, or enable the RECEIVE attribute of the LOG_ARCHIVE_CONFIG parameterand restart the standby database instance before further REDO log file archivals occur. ORA-16066: remote archival disabled Cause: 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. Action: 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, or enable the SEND attribute of the LOG_ARCHIVE_CONFIG parameter and restart the database instance before further REDO log file archivals occur. ORA-16067: activation identifier mismatch in archive log string Cause: 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. Action: Locate the appropriate archive log for the database. ORA-16068: redo log file activation identifier mismatch Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database. Action: none ORA-16069: Archive Log standby database activation identifier mismatch Cause: 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. Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing. ORA-16070: parameter string contains an invalid REGISTER attribute value Cause: 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 O/S-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S). Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter. ORA-16071: dependency archived log file not found string Cause: The specified archived log file was not found at the indicated standby destination. Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file. ORA-16072: a minimum of one standby database destination is required Cause: No standby database archive log destinations were specified. Action: Specify a standby archive log destination in the initialization parameter file. ORA-16073: archiving must be enabled Cause: Online log file archiving is disabled. Action: Enable log file archiving. ORA-16074: ARCH processes must be active Cause: There are no active ARCH processes. Action: It is required that at least one ARCH process be active. ORA-16075: standby database destination mismatch Cause: A standby database destination was specified that is not accessed by another instance. Action: All database instances must access the same standby databases. ORA-16076: unknown standby database destination Cause: A standby database destination was specified that is not accessed by another instance. Action: All database instances must access the same standby databases. ORA-16078: media recovery disabled Cause: The database is not in ARCHIVELOG mode. Action: Place the database in ARCHIVELOG mode. ORA-16079: standby archival not enabled Cause: The standby database does not have archival enabled. Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active. ORA-16080: invalid LogMiner session string for APPLY Cause: Logical standby apply engine was started with an invalid LogMiner session identifier. Action: Fix the problem with the LogMiner session or create a new session. ORA-16081: insufficient number of processes for APPLY Cause: Logical standby apply engine was started with fewer processes available than needed. Action: Increase the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view. ORA-16082: logical standby is not initialized correctly Cause: Logical standby apply engine was started but it found inconsistencies in its metadata. Action: Look in the trace file for more information. ORA-16083: LogMiner session has not been created Cause: Logical standby apply engine was started without creating a LogMiner session. Action: Create a LogMiner session and restart the apply engine. ORA-16084: an apply engine is already running Cause: A logical standby apply engine was running when another was created. Action: Shut down the previous apply engine before starting a new one. ORA-16086: standby database does not contain available standby log files Cause: The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files". Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted. ORA-16087: graceful switchover requires standby or current control file Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file. Action: 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. ORA-16088: archive log has not been completely archived Cause: 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. Action: Specify a completed archive log. ORA-16089: archive log has already been registered Cause: 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. Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information. ORA-16090: archive log to be replaced not created by managed standby process Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation. Action: No user action required. ORA-16091: dependent archive log destination already archived Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived. Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes. ORA-16092: dependent archive log destination is not active Cause: An archive log destination contains a dependency to another archive log destination that is not active" Action: The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM command to remove one of the dependency attributes. ORA-16093: dependent archive log destination is not LGWR-enabled Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process" Action: The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM command to change the parent archive log to specify the LGWR process. ORA-16094: database shutdown during archival operation Cause: The database was shut down while an online log file archival was active. Action: None required. The ARCH process is terminated. ORA-16095: Dependent destination removal for inactivation Cause: 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. Action: None required. ORA-16096: ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY Cause: None Action: Specify this command to prepare the primary database for switchover ORA-16097: ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY Cause: None Action: Specify this command to prepare the standby database for switchover ORA-16098: inaccessible standby database forced shutdown to protect primary Cause: No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode. Action: Specify an alternate standby archive log destination in the initialization parameter file. ORA-16099: internal error ORA-00600 occurred at standby database Cause: The RFS process on the standby database received an internal error. Action: Check the standby alert log and RFS trace files for more information. ORA-16100: not a valid Logical Standby database Cause: This database has not been completely configured as a Logical Standby database. Action: 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 Oracle8i SQL Reference manual for the statement syntax. ORA-16101: a valid start SCN could not be found Cause: An SCN from which to start could not be found. Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this startement. ORA-16102: remote information is not available on the specified primary Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream. Action: 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. ORA-16103: Logical Standby apply must be stopped to allow this operation Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation. Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or respecify the operation. ORA-16104: invalid Logical Standby option requested Cause: The option requested is not valid. Action: Check spelling or refer to the Oracle8i SQL Reference manual for the correct statement syntax, then re-enter the request. ORA-16105: Logical Standby is already running in background Cause: A Logical Standby apply operation is already running. Action: none ORA-16107: all log data from primary has been processed Cause: On the primary system, the log stream has been ended by the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY command. Action: Issue one of the following commands to make this standby a primary or resume applying changes from a new primary. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL PRIMARY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink; ORA-16108: database is no longer a standby database Cause: The current database has already been made a primary database. Action: Issue the following commands to make this primary a standby. ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY; ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink; ORA-16109: failed to apply log data from previous primary Cause: Log data from previous primary could not be completely applied. Action: . Then, re-issue command. ORA-16110: user procedure processing of logical standby apply DDL Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed. Action: No action necessary, 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. ORA-16111: log mining and apply setting up Cause: This logical standby process is setting up to begin processing changes. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16112: log mining and apply stopping Cause: This logical standby process is cleaning up and stopping Logical Standby apply. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16113: applying change to table or sequence string Cause: The process is applying changes to a specific schema object. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16114: applying DDL transaction with commit SCN string Cause: The process is applying a DDL change that"s committed at the given SCN. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16115: %s\% of LogMiner dictionary loading is done Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16116: no work available Cause: The process is idle waiting for additional changes to be made available. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16117: processing Cause: The process is performing its primary function and is not waiting on any significant event. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16119: building transaction at SCN string Cause: The transaction being committed at the given SCN is being prepared for apply. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16120: dependencies being computed for transaction at SCN string Cause: The transaction committed at the given SCN is being analyzed for dependencies. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16121: applying transaction with commit SCN string Cause: The transaction committed at the given SCN is being applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16122: applying large dml transaction at SCN string Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16123: transaction string string string is waiting for commit approval Cause: 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. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16124: transaction string string string is waiting on another transaction Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16125: large transaction string string string is waiting for more data Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16126: loading table or sequence string Cause: Information on the given table or sequence is being loaded into an in memory cache for future use. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16127: stalled waiting for additional transactions to be applied Cause: 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. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, increase available SGA or the number of apply processes. ORA-16128: User initiated stop apply successfully completed Cause: Logical standby was shutdown in an orderly fashion. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16129: unsupported dml encountered Cause: 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. Action: 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. ORA-16130: supplemental log information is missing from log stream Cause: Supplemental logging is not enabled at the primary database. Action: Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS; ORA-16131: An error occurred during a Terminal Recovery of the standby. Cause: An error occurred during a Terminal Recovery of the standby. Action: Check the standby alert log additional information. ORA-16132: An error occurred during activation of the standby. Cause: An error occurred during activation of the standby database following a Terminal Recovery. Action: Check the standby alert log additional information. ORA-16133: Datafile string has incorrect terminal recovery stamp. Cause: 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. Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery. ORA-16134: invalid MANAGED recovery FINISH option Cause: A mode other than NOWAIT follows the FINISH keyword in RECOVER MANAGED STANDBY DATABASE statement. Action: Specify either nothing or NOWAIT following FINISH. ORA-16135: Invalid LOG_ARCHIVE_CONFIG modification while in protected mode Cause: The LOG_ARCHIVE_CONFIG parameter can not be modified while any RAC instance is open in either maximum protection or maximum availability mode. Also, the parameter can not be modified in such way that would cause all destinations to fail while in maximum protection mode. Action: Make the modification before the database is opened by any instance. ORA-16136: Managed Standby Recovery not active Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active. Action: No action is necessary. ORA-16137: No terminal recovery is required Cause: All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required. Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby. ORA-16138: end of log stream not received from primary Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible. Action: 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. ORA-16139: media recovery required Cause: The database has not been recovered through the end of log stream. Graceful switchover is not possible. Action: Ensure that the entire log stream has been applied. If appropriate, reissue the graceful switchover command. ORA-16140: standby online logs have not been recovered Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs. Action: To recover the standby online logs issue the following command: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH. Then re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE command. To activate the standby without recovering the online logs, issue the following command: ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE. ORA-16143: RFS connections not allowed during or after terminal recovery Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery. Action: The primary must not attempt to archive to the standby after a terminal recovery. ORA-16145: archival for thread# string sequence# string in progress Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived. Action: Verify that archival of the indicated log file has completed and reissue the RECOVER STANDBY DATABASE command. ORA-16146: standby destination control file enqueue unavailable Cause: 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. Action: Check for and eliminate the standby destination archive log parameter in question. ORA-16147: standby database referenced by multiple archive log destinations Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed. Action: Remove one of the duplicate archive log destinations. ORA-16148: user requested expiration of managed recovery operation Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement. Action: No action is required. ORA-16150: FINISH recovery performed on another, older standby database Cause: 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. Action: No action is required. ORA-16151: Managed Standby Recovery not available Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation. Action: Wait for the managed standby recovery session to end. Then retry the operation. ORA-16152: standby database is in "no-data-loss" protected mode Cause: The attempted database operation is not allowed while the standby database is in "no-data-loss" protected mode. Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and reissue the statement. ORA-16154: suspect attribute: string Cause: Use of the indicated attribute is illegal in the given context. Action: Make the appropriate changes and reissue the statement. ORA-16156: LGWR archive log dependency not allowed if database is standby protected Cause: 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. Action: Remove the LGWR archive log dependency and use normal LGWR archival instead. ORA-16157: media recovery not allowed following successful FINISH recovery Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed. Action: Issue one of these operations following a FINISH recocvery: ALTER DATABASE OPEN READ ONLY or ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY. ORA-16159: Cannot change protected standby destination attributes Cause: 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. Action: No action is required. ORA-16160: Cannot change protected standby database configuration Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode. Action: The standby database must be added to the configuration before the primary database is opened. ORA-16161: Cannot mix standby and online redo log file members for group string Cause: 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. Action: Verify the log file group type using the TYPE column of the V$LOG fixed view. ORA-16162: Cannot add new standby databases to protected configuration Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode. Action: The standby database must be added to the configuration before the primary database is opened. ORA-16163: LGWR network server host attach error Cause: The LGWR network server could not attach to remote host Action: The alert log contains more problem-specific information ORA-16164: LGWR network server host detach error Cause: The LGWR network server could not detach from remote host Action: The alert log contains more problem-specific information ORA-16165: LGWR failed to hear from network server Cause: The LGWR lost its connection to the network server Action: The alert log contains more problem-specific information ORA-16166: LGWR network server failed to send remote message Cause: The LGWR network server could not communicate with the remote host Action: The alert log contains more problem-specific information ORA-16167: LGWR network server could not switch to non-blocking mode Cause: The LGWR network server could not switch to non-blocking mode Action: The alert log contains more problem-specific information ORA-16168: LGWR network server could not switch to blocking mode Cause: The LGWR network server could not switch to blocking mode Action: The alert log contains more problem-specific information ORA-16169: LGWR network server invalid parameters Cause: The LGWR network server could not switch to blocking mode Action: The alert log contains more problem-specific information ORA-16170: Terminal recovery may have left the database in an inconsistent state Cause: When terminal recovery is invoked in a standby database without synchronous log shipping, in the rare case of the recovery session being in an unrecoverable state, terminal recovery cannot bring the standby database to a consistent SCN boundary if the primary database continues to have redo thread(s) open. Action: Continue standby recovery with additional log shipping from primary. ORA-16171: RECOVER...FINISH not allowed due to gap for thr string, seq string-string Cause: See alert log for more details Action: 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, issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP command to ignore the standby redo log files. ORA-16172: archive logs detected beyond Terminal End-Of-Redo Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR. Action: none ORA-16173: incompatible archival network connections active Cause: One of two situations can cause this error: 1) An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected. 2) An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site. An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented. Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation. ORA-16174: user requested thread/sequence termination of managed recovery Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement. Action: No action is required. ORA-16175: cannot shut down database when media recovery is active Cause: An attempt was made to shut down a standby database while media recovery was active. Action: Cancel media recovery to proceed with the shutdown. ORA-16176: background dictionary build cannot be running Cause: The background process dedicated to dictionary build is active. Action: wait and try it later. ORA-16177: media recovery is not required Cause: The THROUGH LAST SWITCHOVER clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE was specified and the database has been recovered to the most recent End-Of-Redo marker. All known archived logs have been applied. Managed recovery is not required. Action: No action is necessary. The standby database may be activated as a new primary or may continue as a standby. ORA-16178: Cannot specify remote destinations in archivelog manual mode Cause: The database is operating in ARCHIVELOG MANUAL mode. Remote archivelog destinations are not allowed in this mode. Action: Use the ALTER DATABASE ARCHIVELOG command to place the database in automatic archivelog mode, or defer the archivelog destinations that specify the SERVICE= attribute. ORA-16179: incremental changes to "string" not allowed with SPFILE Cause: Incremental changes to a log_archive_dest_n parameter cannot be made when using an SPFILE. Action: Specify either LOCATION or SERVICE plus all other attributes to be set in one ALTER SYSTEM/SESSION SET command. ORA-16180: number processes specified for MAX_PARALLEL_SERVERS is too small Cause: The max number of parallel servers available for Logical Standby is less than 5 becase of the limit imposed by the too small value of MAX_PARALLEL_SERVERS. Action: Adjust the values of the initialization parameters PARALLEL_MAX_SERVERS to be at least 5. ORA-16181: SGA specified for Logical Standby is too large Cause: MAX_SGA is larger than the larger of initialization parameters SHARED_POOL_SIZE and SGA_TARGET. Action: Specify the value of MAX_SGA to be less than the maximum of SHARED_POOL_SIZE and SGA_TARGET. Likely only 75% or lower. ORA-16182: Internal error on internal channel during remote archival Cause: An internal error was encountered on the internal channel between LGWR and Network Server. Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival. ORA-16184: DB_UNIQUE_NAME string hashes to the same value as DB_UNIQUE_NAME string Cause: The internal hash value generated for one DB_UNIQUE_NAME collided with the hash value of another DB_UNIQUE_NAME. Action: Slightly modify one of the DB_UNIQUE_NAMEs so it hashes to a different value. ORA-16185: REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive Cause: Both the REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG parameters are defined in the initialization file and they are mutually exclusive. Action: The REMOTE_ARCHIVE_ENABLE parameter has been made obsolete. Use only the LOG_ARCHIVE_CONFIG parameter. ORA-16186: Modifying LOG_ARCHIVE_CONFIG requires SID="*" qualifier Cause: The setting for the LOG_ARCHIVE_CONFIG parameter must be exactly the same on all RAC instances so the SID="*" qualifier is required. Action: Re-enter the command using the SID="*" qualifier. ORA-16187: LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes Cause: The LOG_ARCHIVE_CONFIG parameter was specified with duplicate, conflicting or invalid attributes. Action: Check the documentation regarding the correct specification of the LOG_ARCHIVE_CONFIG parameter. ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance Cause: The settings for the LOG_ARCHIVE_CONFIG parameter are inconsistent with the settings of a previously started instance. The settings for this parameter must be exactly the same for all instances. Action: Make sure all instances use the exact same LOG_ARCHIVE_CONFIG settings. ORA-16191: Primary log shipping client not logged on standby Cause: An attempt to ship redo to standby without logging on to standby or with invalid user credentials. Action: Check that primary and standby are using password files and that both primary and standby have the same SYS password. Restart primary and/or standby after ensuring that password file is accessible and REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED or EXCLUSIVE. ORA-16192: Primary and standby network integrity mismatch Cause: Standby wants sqlnet network integrity for redo shipment which is not configured properly at the primary. Action: Check sqlnet.ora documentation regarding how to setup network integrity and set it up identically on both primary and standby. Restart primary and/or standby. ORA-16193: Primary and standby network encryption mismatch Cause: Standby wants sqlnet network encryption for redo shipment which is not configured properly at the primary. Action: Check sqlnet.ora documentation regarding how to setup network encryption and set it up identically on both primary and standby. Restart primary and/or standby. ORA-16194: Modifying DB_UNIQUE_NAME requires SID="*" qualifier Cause: The setting for the DB_UNIQUE_NAME parameter must be exactly the same on all RAC instances so the SID="*" qualifier is required. Action: Re-enter the command using the SID="*" qualifier. ORA-16195: DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined Cause: The DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter can only be used if the DB_UNIQUE_NAME parameter has been explicitly defined. Action: Explicitly define a valid DB_UNIQUE_NAME. ORA-16196: database has been previously opened and closed Cause: The instance has already opened and closed the database, which is allowed only once in its lifetime. Action: Shut down the instance. ORA-16197: Invalid DB_UNIQUE_NAME parameter specification Cause: The DB_UNIQUE_NAME parameter has an invalid specification. The DB_UNIQUE_NAME parameter has a maximum length of 30 characters and the only characters allowed are alpha-numeric characters and "_", "$" and "#". Action: Check the documentation and re-enter the parameter. ORA-16198: Timeout incurred on internal channel during remote archival Cause: A timeout was incurred during remote archival. Action: No action is required, as an attempt will be made to re-archive the file that had this failure during archival. ORA-16199: Terminal recovery failed to recover to a consistent point Cause: See alert log for more details Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, call Oracle support. ORA-16200: Skip procedure requested to skip statement Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16201: Skip procedure requested to apply statement Cause: Logical standby called a skip procedure that requested for a particular statement to be applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16202: Skip procedure requested to replace statement Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16203: Unable to interpret skip procedure return values Cause: The skip procedure returned conflicting or invalid values. Action: 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. ORA-16204: DDL successfully applied Cause: A DDL statement has successfully commited on the logical standby database. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16205: DDL skipped due to skip setting Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16206: database already configured as Logical Standby database Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation. Action: 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. ORA-16207: Logical standby dictionary build not permitted. Cause: A dictionary build is currently in progress. Only one build can be active at a time. Action: Wait for the active build to complete before invoking a new build. ORA-16208: Logical standby dictionary build failed to start. Cause: Failure to start the logical standby dictionary build process (LSP1)" Action: 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, check the trace file for the mentioned process until the root message is found. ORA-16209: Logical standby dictionary build failed to complete. Cause: The logical standby dictionary build process terminated abnormally." Action: 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, check the trace file for the mentioned process until the root message is found. ORA-16210: Logical standby coordinator process terminated with error Cause: The logical standby coordinator process terminated abnormally." Action: 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, check the trace file for the mentioned process until the root message is found. ORA-16211: unsupported record found in the archived redo log Cause: Log apply services encountered a record in the archived redo log that could not be interpreted. Action: 1. Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it"s unimportant. 2. ALTER DATABASE START LOGICAL STANDBY APPLY; 3. Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record. 4. Provide the log file to Oracle Support Services. ORA-16212: number processes specified for APPLY is too great Cause: Logical standby apply engine was started with more processes requested than are available. Action: Adjust the values of the initialization parameters PROCESSES and and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view. ORA-16213: ddl encountered, stopping apply engine Cause: stop_on_ddl callout specified and DDL was encountered. Action: Either disable stop_on_ddl callout or remove DDL. ORA-16214: apply stalled for apply delay Cause: A delay has been specified on the primary database for this destination. Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET("APPLY_DELAY"); to override. ORA-16215: history metadata inconsistency Cause: internal error. Action: This is an internal error. Contact Oracle support. ORA-16216: Log stream sequence error Cause: The log stream being processed did not follow the last processed stream. Action: If the database is in an active configuration, issue an ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY command to synchronize log stream data with the current primary database. If the database is not in an active configuration, manually add the next dictionary-begin logfile that followed the previous log stream. ORA-16217: prepare to switchover has not completed Cause: An ALTER DATABASE PREPARE TO SWITCHOVER command was issued, but the prepare activity did not complete. Action: Verify that the standby was prepared properly. You may cancel the prepare and perform an unprepared switchover which requires a database link to complete. Or reissue the prepare operation on the standby. ORA-16218: This database is already preparing to switch over. Cause: The database was already preparing to switch over and was not able to accomodate another prepare attempt. Action: Cancel the current prepare attempt with the ALTER DATABASE PREPARE TO SWITCHOVER CANCEL command, then reissue the prepare request. ORA-16219: This database is not preparing to switch over. Cause: The database was not preparing to switch over. Therefore, it was not possible to cancel the SWITCHOVER command. Action: Preparing for the SWITCHOVER command can be accomplished with the ALTER DATABASE PREPARE TO SWITCHOVER command. ORA-16220: no failed transaction found Cause: No failed transaction was found. Action: Retry the ALTER DATABASE START LOGICAL STANDBY APPLY command without the SKIP FAILED TRANSACTION option. ORA-16221: history table synchronization error Cause: internal error. Action: This is an internal error. Contact Oracle support. ORA-16222: automatic Logical Standby retry of last action Cause: A failure occurred while running Logical Standby apply. A new attempt is automatically being made by Logical Standby apply. Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes. ORA-16223: DDL skipped, unsupported in current version Cause: The given DDL statement was not supported in the current version of Logical Standby and was skipped. Action: No action is necessary. This informational statement is provided to record the event for diagnostic purposes. ORA-16224: Database Guard is enabled Cause: Operation could not be performed because database guard is enabled Action: Verify operation is correct and disable database guard ORA-16225: Missing LogMiner session name for Streams Cause: An attempt was made to register the log file for Streams without a specified LogMiner session name. Action: Specify a valid LogMiner session name to which the log file will be registered. ORA-16226: DDL skipped due to lack of support Cause: Logical Standby does not support this type of DDL in this version, so the DDL is skipped. Action: The DBA may apply the DDL explicitly at a later time or a procedure to handle this type of DDL can be created. see DBMS_LOGSTDBY.SKIP procedure for details. ORA-16227: DDL skipped due to missing object Cause: A table or other database object upon which this DDL depends is not defined on the Logical Standby database. Action: No action is necessary, this infomational statement is provided to record the event for diagnostic purposes. ORA-16228: Insufficient recovery for logical standby Cause: Insufficient amount of recovery was run for logical standby instantiation. Action: Continue to recover the database using ALTER DATABASE RECOVER MANAGED STANDBY DATABASE. ORA-16229: PDML child string string string for parent string string string cannot be skipped. Cause: A request was made to skip a parallel DML child transaction id. This is not supported. Action: Using the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure, remove the child transaction id, then specify the parent transaction id using DBMS_LOGSTDBY.SKIP_TRANSACTION if appropriate. ORA-16230: committing transaction string string string Cause: Logical Standby apply was committing changes for the given transaction. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16231: DDL barrier Cause: Logical Standby was holding back changes until dependent changes were applied. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16232: adding Logical Standby skip entry for table string.string Cause: Table was previously unsupported due to datatype or storage attribute definitions. Table is now capable of being supported. Action: To have Logical Standby maintain the table, import that table directly from the primary. ORA-16233: The table string.string is unsupported now Cause: Table was previously supported but now is unsupported due to altered datatype or storage attribute definitions. Action: None. ORA-16234: restarting to reset Logical Standby apply Cause: Logical Standby encountered a work load that required a restart to properly reschedule. Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. ORA-16235: DDL skipped because import has occurred Cause: An object was exported from the primary database and imported into the Logical Standby database. This DDL occurred before the export. Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes. ORA-16236: Logical Standby metadata operation in progress Cause: The requested operation failed because a Logical Standby metadata operation, such as DBMS_LOGSTDBY.SET_TABLESPACE or DBMS_LOGSTDBY.INSTANTIATE_TABLE, has not finished. Action: Wait for the Logical Standby metadata operation to finish, then re-enter or respecify the operation. ORA-16237: SGA specified for Logical Standby is too small Cause: MAX_SGA must be at least 10 Megabytes for proper functioning of Logical Standby. Action: Specify the value of MAX_SGA to be greater than or equal to 10Mb. Alternatively, increase the shared_pool_size/sga_target so that 1/4 of it will amount to 10 Megabytes. ORA-16238: attempt to use version 9 log Cause: Version 9 log files are not supported. Action: Use log files of a supported version. ORA-16239: IMMEDIATE option not available without standby redo logs Cause: The IMMEDIATE option cannot be used without standby redo logs. Action: Do not specify the IMMEDIATE option unless standby redo logs are being used." ORA-16240: Waiting for logfile (thread# string, sequence# string) Cause: Reader process is idle waiting for additional logfile to be available. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16241: Waiting for gap logfile (thread# string, sequence# string) Cause: Reader process is idle waiting for the logfile to fill the log sequence gap. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16242: Processing logfile (thread# string, sequence# string) Cause: Reader process is processing the logfile. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16243: paging out string bytes of memory to disk Cause: Builder process is paging out momery to free up space in lcr cache. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16244: taking checkpoint and paging out string bytes to disk Cause: Builder process is taking a checkpoint to advance restart_scn Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16245: paging in transaction string, string, string Cause: Builder process is paging in transactions from disk. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16246: User initiated abort apply successfully completed Cause: SQL Apply was stopped using the abort option. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16247: DDL skipped on internal schema Cause: Logical Standby ignores DDLs on internal schemas such as SYS and SYSTEM. For a complete list of internal schemas ignored by Logical Standby perform the following query: SELECT owner FROM dba_logstdby_skip WHERE statement_opt = "INTERNAL SCHEMA". Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16248: RFS connections not permitted during Terminal Apply Cause: Writes by RFS are not permitted while Logical Standby is performing Terminal Apply. Action: Permit any outstanding Logical Standby operations to complete. ORA-16249: Terminal apply failed to complete during failover Cause: The logical standby coordinator process terminated abnormally." Action: Examine the DBA_LOGSTDBY_EVENTS view for the reason behind the abnormal shutdown, and resolve accordingly. Once the problem has been rectified, reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE command to complete the failover. ORA-16250: Failed to acquire starting scn of new log stream Cause: The starting SCN for the new log stream could not be determined. Action: Please reissue the ACTIVATE LOGICAL STANDBY DATABASE command. ORA-16251: LSP1 Background Build not permitted Cause: The LSP1 background process is not permitted to start because it had previously been attempted. Action: This is an internal error. Contact Oracle support. ORA-16252: Rebuild operation not permitted Cause: The REBUILD operation is not permitted. Action: Only on a primary database that has failed to complete the LogMiner dictionary build may the REBUILD operation take place. Reissue the ACTIVATE LOGICAL STANDBY DATABASE command if it previously failed to complete. ORA-16253: Logical Standby cannot start due to incomplete terminal apply Cause: A previous ACTIVATE of the logical standby failed to complete. Action: Reissue the ALTER DATABASE ACTIVATE LOGICAL STANDBY DATABASE FINISH APPLY command. ORA-16254: change db_name to string in the client-side parameter file (pfile) Cause: An ALTER DATABASE RECOVER TO LOGICAL STANDBY new-dbname command was successfully executed without a server parameter file (spfile). Action: The client-side parameter file must be edited so that db_name is set to the given name before mounting the database again. ORA-16255: Log Auto Delete conflicts with another LogMiner session Cause: Log Auto Delete cannot be on while another LogMiner session is running on the same database. Action: Start Logical Standby without Log Auto Delete or destroy other LogMiner sessions first. ORA-16256: Failure to complete standby redo logfile archival after failover Cause: The standby redo logfiles processed during the failover of a logical standby were not archived. Action: Execute DBMS_LOGSTDBY.REBUILD to reattempt the archival. ORA-16257: Switchover initiated stop apply successfully completed Cause: SQL Apply was stopped because of a switchover. Action: No action necessary, this informational statement is provided to record the event for diagnostic purposes. ORA-16258: marking index unusable due to a constraint violation Cause: A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted. Action: No action necessary. See alert log for index schema and name. ORA-16259: Switchover to logical standby requires a log archive destination Cause: A valid log archive destination was not found to which the local system could archive the EOR logfile. A minimum of one destination is required. Action: Ensure all log archive destinations are properly configured and, if applicable, have network connectivity before re-issuing the ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY DDL operation. ORA-16260: Waiting to replace partial or corrupt logfile (thread# string, sequence# string) Cause: LogMiner Reader process reached end of a partial logfile or encountered a corrupted block. It is now waiting for the logfile to be recovered and re-registered. Action: No action necessary. Once the FAL archiver replaces the logfile, standby will automatically restart to process the replaced file. ORA-16400: quota attributes are not allowed with DB_RECOVERY_FILE_DEST Cause: Quota attributes for the destination parameters are not allowed when the parameter DB_RECOVERY_FILE_DEST is defined. Action: No action is required. ORA-16401: archivelog rejected by RFS Cause: An attempt was made to re-archive an existing archivelog. This usually happens because either a multiple primary database or standby database(s) or both are trying to archive to this standby database. Action: See alert log and trace file for more details. No action is necessary; this is an informational statement provided to record the event for diagnostic purposes. ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support Cause: The archivelog destination TRANSPORT=ONDEMAND attribute was specified on the primary database. Use of the TRANSPORT=ONDEMAND attributes requires that the corresponding standby database explicitly specify the FAL_CLIENT and FAL_SERVER initialization parameters. Action: Make sure the FAL_CLIENT and FAL_SERVER initialization parameters are explicitly specified on the standby database that received this error. ORA-16403: shutdown in progress - remote connection is not permitted Cause: The SHUTDOWN command was used to shut down a running remote primary or standby ORACLE instance, so the LGWR or ARCH processes cannot connect to ORACLE. Action: Wait for the remote instance to be restarted, or contact your DBA. ORA-16406: Primary and standby database software version mismatch Cause: The primary database and standby database Oracle software is not compatible. Action: Install the correct Oracle software and try again. ORA-16407: Standby database is in the future of the archive log Cause: An archive log, from a different Redo Branch, was received by a standby database that has applied Redo in the future of Redo contained within the archive log. The standby database has rejected the REDO Branch archive logs. Action: No action is required. ORA-16408: Incompatible archival Redo Branch lineage Cause: An archive log, from an incompatible different Redo Branch, was received by a standby database. The standby database has rejected the Redo Branch archive logs. Action: No action is required. ORA-16409: Archive log switchover reference number mismatch Cause: The archive log switchover reference numbers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. Action: No action is required. ORA-16411: ONDEMAND archival requires active managed recovery operation Cause: The use of the ONDEMAND attribute for a physical standby database destination requires that the managed recovery operation be active prior to establishing the network connection. Action: Start the managed recovery operation on the standby database. ORA-16412: ONDEMAND archival requires active SQL apply operation Cause: The use of the ONDEMAND attribute for a logical standby database destination requires that the SQL apply operation be active prior to establishing the network connection. Action: Start the SQL apply operation on the standby database. ORA-16413: Unsupported database type for ONDEMAND archivelog destinations Cause: The use of the ONDEMAND attribute for a standby database destination is supported for only physical and logical standby database types. Cross-Instance-Archival and repository database types are not valid for the ONDEMAND attribute. Action: Verify the database corresponding to the archivelog destination is either a physical standby database or a logical standby database. ORA-16416: Switchover target is not synchronized with the primary Cause: The switchover target incurred an error or has a gap at the time the switchover operation was attempted. Action: Allow the switchover target to become synchronized and then re-attempt the switchover. ORA-16417: Activation occurred after recovery from standby redo log files; a full database backup is required Cause: Activation occurred after recovery from standby redo log files. Action: Take a full database backup. ORA-16501: the Data Guard broker operation failed Cause: The Data Guard broker operation failed. Action: See accompanying messages for details. ORA-16502: the Data Guard broker operation succeeded with warnings Cause: The Data Guard broker operation succeeded with warnings. Action: See accompanying messages for details. ORA-16503: site ID allocation failure Cause: Internal error Action: Contact Oracle Support Services. ORA-16504: the Data Guard configuration already exists Cause: A request to create a Data Guard configuration was made while connected to a database that is part of an existing configuration. Action: Delete the existing configuration if you want to create a new configuration. ORA-16505: site ID is invalid Cause: The request contained an invalid site ID. Action: Make the request again with a valid site iD. ORA-16506: out of memory Cause: Process exceeded private or shared memory limits. Action: Check for memory leaks, increase system parameters and restart. ORA-16507: unrecognized request identifier Cause: The specified request identifier was not recognized by the Data Guard broker. Action: Reissue the request using a valid request identifier. ORA-16508: channel handle not initialized Cause: Internal error Action: Contact Oracle Support Services. ORA-16509: the request timed out Cause: Internal error Action: Contact Oracle Support Services. ORA-16510: messaging error using ksrwait Cause: Internal error Action: Contact Oracle Support Services. ORA-16511: messaging error using ksrget Cause: Internal error Action: Contact Oracle Support Services. ORA-16512: parameter exceeded maximum size limit Cause: Internal error Action: Contact Oracle Support Services. ORA-16513: maximum requests exceeded Cause: Non-blocking commands were issued but responses were not consumed or the commands did not complete. Action: Read pending responses or delete outstanding requests and try again. ORA-16514: the request was not found Cause: An attempt was made to read a response but a matching request was not found. Action: Verify request identifier is valid and references a previously issued request. ORA-16515: no rcv channel Cause: Internal error Action: Contact Oracle Support Services. ORA-16516: the current state is invalid for the attempted operation Cause: The broker may return this error for switchover operations and for database state change operations. If this error is returned for a switchover operation, the broker has determined that either: - The databases changing roles are offline. - The primary database is not shipping log files. - The standby database that will become the primary database is not applying log files. The broker returns this error for database state change operations if the database state specified is invalid. Action: If this error is returned when attempting a switchover operation, make sure that: - The databases changing roles are online. - The primary database is shipping log files. - The standby database is applying log files. If this error is returned when attempting a database state change operation, make sure you specify a valid state. ORA-16517: the object handle is invalid Cause: Internal error Action: Contact Oracle Support Services. ORA-16518: unable to allocate virtual instance id Cause: Internal error Action: Contact Oracle Support Services. ORA-16519: the resource handle is invalid Cause: Internal error Action: Contact Oracle Support Services. ORA-16520: unable to allocate resource id Cause: Internal error Action: Contact Oracle Support Services. ORA-16521: unable to create generic template id Cause: Internal error Action: Contact Oracle Support Services. ORA-16522: generic template not found Cause: Internal error Action: Contact Oracle Support Services. ORA-16523: operation requires the client to connect to instance "string" Cause: The switchover or failover operation requires the client to connect to the apply instance of the target database. Action: Connect to the indicated instance and reissue the switchover or failover command. ORA-16524: unsupported operation Cause: A command or option is not supported in this release. Action: Contact Oracle Support Services. ORA-16525: the Data Guard broker is not yet available Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start. Action: If the broker has not been started, set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, check the Data Guard log for possible errors. Otherwise, retry the operation. ORA-16526: unable to allocate task element Cause: The Data Guard broker was unable to allocate memory for a request. Action: Increase the size of your SGA. ORA-16527: unable to allocate SGA heap Cause: The Data Guard broker was unable to allocate a heap within the SGA. Action: Increase SGA memory. ORA-16528: unable to allocate PGA heap Cause: No space in PGA to allocate heap Action: Increase process virtual memory. ORA-16529: bad sender id Cause: Internal error Action: Contact Oracle Support Services. ORA-16530: invalid buffer or length Cause: A NULL buffer or a length of zero is specified. Action: Correct command parameters and retry. ORA-16531: unable to post message Cause: Internal error Action: Contact Oracle Support Services. ORA-16532: Data Guard broker configuration does not exist Cause: A broker operation was requested that requires an already existing broker configuration. Action: Create a Data Guard broker configuration prior to issuing other requests. ORA-16533: inconsistent Data Guard broker state Cause: Internal error Action: Contact Oracle Support Services. ORA-16534: no more requests accepted Cause: The Data Guard broker returns this status when: - A failover operation has been submitted or is currently is in progress. - A switchover operation has been submitted or is currently is in progress. - An instance restart is pending for one or more databases. Action: Wait until the operation is complete and then reissue the request. ORA-16535: CRS is preventing execution of a broker operation Cause: A broker operation was underway that required CRS to stop managing the instances of this database, but CRS management could not be stopped on behalf of the broker"s request on at least some of the instances, so the broker operation was canceled. Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D -O NONE. Then reissue the broker request. ORA-16536: unknown object type Cause: Internal error Action: Contact Oracle Support Services. ORA-16537: child count exceeded Cause: Internal error Action: Contact Oracle Support Services. ORA-16538: no match on requested item Cause: The Data Guard broker did not recognize the specified property or state name. Action: Verify command parameters and reissue the request. ORA-16539: task element not found Cause: Internal error Action: Contact Oracle Support Services. ORA-16540: invalid argument Cause: One of the arguments for the specified request was invalid for the request type. Action: Verify arguments and then reissue the request. ORA-16541: site is not enabled Cause: The site specified in the request was not enabled. Action: Select an enabled site and reissue the request. ORA-16542: unrecognized operation Cause: Internal error Action: Contact Oracle Support Services. ORA-16543: invalid request made to broker Cause: Internal error Action: Contact Oracle Support Services. ORA-16544: modifying DG_BROKER_START requires SID="*" qualifier Cause: The setting for the DG_BROKER_START parameter must be exactly the same on all RAC database instances. The SID="*" qualifier was required in the command. Action: Reenter the command using the SID="*" qualifier. ORA-16545: unable to get response Cause: The Data Guard broker was unable to return the result of a previous request. Action: Contact Oracle Support Services. ORA-16546: missing or invalid piece Cause: The piece of the request to return was not specified or was invalid. Action: Specify the piece of the response starting from 1. ORA-16547: cannot disable the primary database Cause: An attempt was made to explicitly disable broker management of the primary database. Action: Broker management of the primary database cannot be explicitly disabled. Instead you must disable the entire broker configuration if you wish to disable the primary database. ORA-16548: object not enabled Cause: An attempt was made to modify or query a disabled Data Guard object, most likely a database. This error is also returned on an attempt to enable, modify, or query a database that the broker has disabled because of a switchover or failover operation. The broker disables its management of a database when it detects that the database needs to be re-created. The broker also disables management of a database that lags behind in terms of DRC Unique ID sequence value. This value is updated after successful switchover and failover operations. Action: If broker management of the database is disabled, enable it and reissue the request. ORA-16549: invalid string Cause: A request contained an invalid or NULL string value. Action: Correct command parameters and retry. ORA-16550: truncated result Cause: A string property value was truncated due to insufficient buffer size. Action: Specify a larger receive buffer. ORA-16551: short string copied Cause: A string property value that did not fill the receive buffer was placed in the receive buffer. Action: This is an informational message only. It is not an error. ORA-16552: an error occurred when generating the CLIENT OPERATION table Cause: An error occurred while Data Guard broker was generating the CLIENT OPERATION table. Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Customer Support. ORA-16553: the Data Guard broker process (DMON) failed to shutdown Cause: Internal error Action: Contact Oracle Support Services. ORA-16554: translation not valid Cause: Internal error Action: Contact Oracle Support Services. ORA-16555: the Data Guard database is not active Cause: An operation was attempted on a database that is currently not active (off path). Action: Verify that the database is active. ORA-16556: error message is in XML already Cause: Internal error Action: Contact Oracle Support Services. ORA-16557: the database is already in use Cause: An attempt was made to create a duplicate database in the broker configuration. Action: Check the database to be added and be sure there are no duplicates. ORA-16558: the database specified for switchover is not a standby database Cause: An attempt was made to switchover to a database that is not a standby database. Action: Locate an enabled standby database and select that database as the target of the switchover. ORA-16559: out of memory at string Cause: Internal error Action: Contact Oracle Support Services. ORA-16560: unable to convert document, syntax error at "string" Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16561: cannot remove an active instance Cause: The instance to be removed is currently running. Action: Shut down the instance and reissue the REMOVE command. ORA-16562: intended_state not used here, syntax error at "string" Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16563: unable to add value, syntax error at "string" Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16564: lookup failed, syntax error at string Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16565: duplicate property, syntax error at "string" Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16566: unsupported document type Cause: The XML document submitted is not supported. Action: Correct the errors and submit the request again. ORA-16567: Data Guard broker internal parser error at "string" Cause: Internal error Action: Contact Oracle Support Services. ORA-16568: cannot set property string Cause: The named property could not be modified. The property may not be editable or may not exist. Action: Retry the operation with a valid property. ORA-16569: Data Guard configuration is not enabled Cause: The requested operation required that broker management of the Data Guard configuration must be enabled. Action: Enable the Data Guard configuration and reissue the request. ORA-16570: operation requires restart of database "string" Cause: The Data Guard broker operation required a database to be shutdown and restarted. Action: If DGMGRL or Enterprise Manager has not already done so, shutdown the Oracle instance and then restart it. ORA-16571: Data Guard configuration file creation failure Cause: The Data Guard broker was unable to create the configuration file on permanent storage. Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters and retry. ORA-16572: Data Guard configuration file not found Cause: The Data Guard broker configuration file was either unavailable or did not exist. Action: Verify that the configuration file was successfully created. If the dg_broker_config_file[1|2] parameter was changed, ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions. ORA-16573: attempt to change configuration file for an enabled broker configuration Cause: The Data Guard broker configuration file parameter was currently in use because broker management of the configuration was enabled. The attempt to alter that parameter was rejected. Action: Disable the configuration and shut down the Data Guard broker before changing this value. Be sure to rename the configuration file at the OS level to match the new value before reenabling broker management of the configuration. ORA-16574: switchover disallowed when required databases are offline Cause: Switchover failed because the primary database and/or the designated standby database are offline. Action: Check the states of the broker configuration, primary database and standby database. Set their states to ONLINE if necessary. ORA-16575: request terminated at broker discretion Cause: 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. Action: There is no action to be taken. ORA-16576: failed to update Data Guard configuration file Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage. Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters. ORA-16577: corruption detected in Data Guard configuration file Cause: The Data Guard broker detected errors while loading the configuration file. Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters. Contact Oracle Support Services. ORA-16578: failed to read Data Guard configuration file Cause: A failure was encountered while the broker was reading the configuration file on permanent storage. Action: Verify space, permissions and filename as indicated by the dg_broker_config_file[1|2] parameters. ORA-16579: bad Data Guard NetSlave state detected Cause: Internal error Action: Contact Oracle Support Services. ORA-16580: bad Data Guard NetSlave network link Cause: Internal error Action: Contact Oracle Support Services. ORA-16581: Data Guard NetSlave failed to send message to DRCX Cause: Internal error Action: Contact Oracle Support Services. ORA-16582: could not edit instance specific property Cause: The request intended to change an instance specific property, but specified a database with two or more instances. Action: Specify a specific instance instead to change the property value. ORA-16583: bad Data Guard Connection Process DRCX state Cause: Internal error Action: Contact Oracle Support Services. ORA-16584: illegal operation on a standby site Cause: Internal error Action: Contact Oracle Support Services. ORA-16585: illegal operation on a primary site Cause: Internal error Action: Contact Oracle Support Services. ORA-16586: could not edit database property through instance Cause: The request intended to change a database property but specified an instance. Action: Specify the database instead to change the database property. ORA-16587: ambiguous object specified to Data Guard broker Cause: The request specified an object that the broker could not uniquely distinguish between other objects in the configuration. Action: Try to further distinguish the object specified for the operation and reissue the request. ORA-16588: no more internal buffers Cause: See trace file. Action: Contact Oracle Support Services. ORA-16589: Data Guard Connection process detected a network transfer error Cause: The Data Guard Connection process (DRCX) detected an error while transferring data from one database to another. This error is returned in the following situations: - While transmitting the configuration file between databases, DRCX detected an inconsistency in the block count of the file. - The DRCX process got an error while writing the configuration file. Action: Contact Oracle Support Services. ORA-16590: Data Guard configuration does not contain a primary database Cause: Internal error Action: Contact Oracle Support Services. ORA-16591: unknown field "string" in document Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16592: missing field "string" in document Cause: There was an error at the given token. Action: Correct the errors and submit the request again. ORA-16593: XML conversion failed Cause: There was an error in the XML request document Action: Correct the errors and submit the request again. ORA-16594: %s process discovered that DMON process does not exist Cause: The Data Guard broker process (DMON) that was expected to be running on this instance was found to be missing by the Data Guard NetSlave (NSV*) process(es). Action: Check the Data Guard broker log and DMON process trace file to determine why the DMON process is missing. ORA-16595: NetSlave process string failed to terminate Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker. Action: Contact Oracle Support Services. ORA-16596: object not part of the Data Guard broker configuration Cause: A request was made on a database object that is not in the Data Guard broker configuration. The request cannot be completed. Action: Reissue the request on a database object that is in the broker configuration. ORA-16597: Data Guard broker detects two or more primary databases Cause: The Data Guard broker detected two or more primary databases in the broker configuration and cannot continue. Action: Contact Oracle Support Services. ORA-16598: Data Guard broker detected a mismatch in configuration Cause: The Data Guard broker detected a significant mismatch in configuration validation between two or more databases in the broker configuration. This can occur when the primary database has a stale broker configuration file. Action: Contact Oracle Support Services. ORA-16599: Data Guard broker detected a stale configuration Cause: The Data Guard broker detected a stale configuration during initialization for this database. Action: The broker will automatically resolve this situation once the primary database completes its initialization. ORA-16600: failover operation can only be submitted at target database Cause: This error is returned when a failover request specified a different database than the database to which the client is currently connected. Action: Explicitly connect to the database to which you wish to failover and reissue the failover request. ORA-16601: site contains required resources that are disabled Cause: The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled. Action: Enable all required resources and reissue the request. ORA-16602: object must be disabled to perform this operation Cause: An attempt was made to edit a database object that can only be done while broker management of that database is disabled. Action: Disable broker management of the database and reissue the request. ORA-16603: Data Guard broker detected a mismatch in configuration ID Cause: The Data Guard broker for this database detected a mismatch in configuration Unique ID. This can occur if the original configuration was recreated while this database was disconnected from the network or the same database was added to two different broker configurations. Action: Make sure the database belongs to only one broker configuration. Remove the Data Guard broker configuration files and restart the broker. ORA-16604: unable to describe template using package "string" Cause: The Data Guard broker was unable to execute the OnDescribe function in the named package. Action: Verify that the named package is loaded on the primary database. Also verify that the OnDescribe function is in the package. ORA-16605: unable to delete template, template is in use Cause: The Data Guard broker was unable to delete the template because the template is still being used by one or more resources. Action: Delete all resources using the template before deleting the template. You cannot delete the database template. ORA-16606: unable to find property "string" Cause: The named property does not exist. Action: Specify a valid property name and reissue the request. ORA-16607: one or more databases have failed Cause: The Data Guard broker detected a failure for one or more databases in the Data Guard configuration. Action: Locate the database(s) with a failure status and correct it. ORA-16608: one or more databases have warnings Cause: The Data Guard broker detected a warning status for one or more databases. Action: Locate the database(s) with a warning status and correct it. ORA-16611: operation aborted at user request Cause: The Data Guard broker aborted an operation at the user"s request. Action: No action required. ORA-16612: string value too long for attribute "string" Cause: The string value for the named attribute is too long. Action: Use a shorter string. ORA-16613: initialization in progress for database Cause: The database received a directive to change its initialization state or a change in its configuration before it has completed initialization. Action: Wait until the database has completed initialization before issuing requests to modify run-time state or configuration. ORA-16614: object has an ancestor that is disabled Cause: A request to enable an object that has an ancestor that is disabled was received by the broker. The broker has enabled management of the object to the extent that it can, but cannot fully enable the object until its ancestor is enabled. Action: Determine the ancestor object that is disabled and enable that ancestor prior to enabling the child object. ORA-16617: unknown object identifier specified in request Cause: The Data Guard broker returned this error because the object identifier specified in the request was invalid or unknown. For example, this error is returned if an invalid or unknown database object identifier is specified in a request that requires a database object identifier. Action: Verify that a valid object identifier was specified in the request and then reissue the request. ORA-16618: response document of size "string" bytes is too large Cause: The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard broker log. Action: View the broker log for the given database directly. ORA-16619: health check timed out Cause: This status is returned when the Data Guard broker could not reach a standby database during a routine health check. Action: This typically indicates a network problem where the standby database is unable to respond to the primary database within a predefined time frame. ORA-16620: one or more databases could not be contacted for a delete operation Cause: The Data Guard broker could not reach one or more standby databases for either a delete database operation or a delete broker configuration operation. Action: This typically indicates a network problem where the standby database is unable to respond to the primary database. In the event of this situation, examine the primary database"s Data Guard broker log for to determine which standby databases could not be reached. Then for each standby database not reached, connect to that database and shut down the broker by setting the initialization parameter, dg_broker_start, to false. After the broker has been shut down for the standby database, locate the Data Guard broker configuration files from the standby database"s dg_broker_config_file[1|2] parameter values and delete them. ORA-16621: database name for ADD DATABASE must be unique Cause: An attempt was made to add a database to the broker configuration that already includes a database with the specified name. The database names must be unique. Action: Verify that you have specified a unique name for the new database you wish to add. This can be done by checking that there is no database with the same name. Also note that the database name must match the DB_UNIQUE_NAME initialization parameter of the database. ORA-16622: two or more broker database objects resolve to one physical database Cause: The Data Guard broker determined that there were multiple database objects referring to the same physical database. Action: Examine the details of all databases in the broker configuration and verify that there are not two or more databases that indicate the same physical database. If you detect this situation, remove and readd the erroneously defined database(s) to resolve the ambiguity. ORA-16623: stale DRC UID sequence number detected Cause: The Data Guard broker detected a stale sequence value during its bootstrap or health check operations. The sequence value is changed each time a switchover or failover operation completes successfully. A database that is unavailable to participate in the switchover or failover operation will end up with a stale sequence number. Should the database attempt to rejoin the broker configuration, the broker will determine that the database missed a role change and will disable its management of that database. The broker disables the database since it may no longer be a viable standby database for the new primary database. Action: Examine the broker configuration for databases that were disabled and which may require re-creation.. ORA-16624: broker protocol version mismatch detected Cause: The broker detected a network protocol version number mismatch. This can happen if the databases in question are not at the same version of Oracle. The broker will disable management of the databases that do not have the same network protocol version number as the primary database. Action: Examine the version of Oracle installed for all databases to make sure they are identical. Once the Oracle versions are the same for all databases, reenable the databases that had been disabled. ORA-16625: cannot reach the database Cause: The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database. Action: Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database. ORA-16626: failed to enable specified object Cause: The broker failed to enable management of an object (most likely a standby database). You can expect to see this status when attempting to enable broker management of a standby database that: - cannot locate itself in the broker configuration file. - fails to distinguish itself from two or more databases in the configuration file. - determines it was not part of a change of primary database due to failover. Action: To correct the problem, try one of these actions: - confirm that the host and SID names for the database exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE. - confirm that you have not created two or more databases with the same connect identifier. That is, multiple databases in the broker configuration should not indicate the same physical database. - if you had performed a failover and have re-created your old primary database (or a standby database that had to be re-created), make sure the Data Guard broker configuration files have been removed for that database. Do NOT remove the configuration files that are in use by the new primary database. ORA-16627: operation disallowed since no standby databases would remain to support protection mode Cause: This status is returned in the following situations: - The broker rejects an attempt to change the configuration"s overall protection mode since it could not find any online, enabled standby databases that support the proposed protection mode. - The broker rejects an attempt to enable the configuration if it determines there are no online, enabled standby databases that support the overall protection mode. - The broker rejects an attempt to disable or remove a database that, if disabled or deleted, would result in no remaining standby databases that can support the configuration"s overall protection mode. - The broker rejects an attempt to set the configuration offline if doing so would violate the configuration"s overall protection mode. - The broker rejects an attempt to set a standby database offline if doing so would violate the configuration"s overall protection mode. - The broker rejects a switchover attempt if doing so would violate the configuration"s overall protection mode. - The broker returns this error during a health check. Action: - If changing the overall protection mode, confirm that at least one standby database satisfies the new protection mode. - For enable failures, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode. - For delete and disable failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. - For state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE you may have to downgrade the protection mode setting to maximum performance beforehand. - For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary database and a single standby database, ensure that the LogXptMode configuration property established for the primary database supports the overall protection mode. After the switchover, the old primary database will become the standby database and its LogXptMode configuration property setting must support the overall protection mode. - For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode. ORA-16628: the broker protection mode is inconsistent with the database setting Cause: The Data Guard broker protection mode saved in the broker"s configuration file was inconsistent with the actual database setting. Action: Reset the protection mode through the Data Guard broker. ORA-16629: database reports a different protection level from the protection mode Cause: The actual protection level supported by the standby database was different from the protection mode set on the primary database. This was likely caused by redo transport problems. Action: Check the database alert logs and Data Guard broker logs for more details. Check the redo transport status. Make sure at least one standby redo transport is supporting the protection mode and that the network to the standby database is working. ORA-16630: that database property was deprecated Cause: The property that was specified in the user operation was a deprecated property. Action: Check the broker documentation to identify a replacement property or issue a SQL command to achieve the same result if no such replacement property exists. ORA-16631: operation requires shutdown of database/instance "string" Cause: The Data Guard broker operation requires a shutdown of the database or instance. Action: If the client has not yet done so, please shutdown all Oracle instances for the database. ORA-16632: instance being added to database profile Cause: The Data Guard broker determined that an instance has successfully found its database profile within the broker configuration file, but yet lacks an instance-specific profile. The broker automatically creates an instance-specific profile and associates the instance with its database profile. Action: No user action is required. The broker will automatically associate the instance with its database profile and incorporate the instance in broker activity. ORA-16633: the only instance of the database cannot be removed Cause: The instance to be removed was the only instance of the corresponding database that is known to the broker. Action: Remove the corresponding database object from the broker configuration instead of that individual instance object of the database. ORA-16635: NetSlave connection was broken in the middle of a transmission session Cause: The Data Guard NetSlave process detected a connection failure to a remote database in the broker configuration. This failure happened in the middle of a transmission session. A transmission session usually requires more than one send operation for sending a large amount of data (e.g. the broker configuration file) to the remote database. This error implies the transmission has to be restarted from the beginning. Action: In most cases, no user action is required. The Data Guard broker always tries to resend the data from the beginning. If the problem persists, the user will eventually see this error reported. This will indicate there are some problems with the network connection between broker managed databases. Further network troubleshooting should be done to identify and address the actual problem. ORA-16636: Fast-Start Failover target standby in error state, cannot stop observer Cause: A STOP OBSERVER operation could not be completed when Fast-Start Failover was enabled because the target standby database could not participate in the STOP OBSERVER operation. Action: Additional information about this failure is recorded in the Data Guard broker log file for the primary database. This information helps you identify the reason why the target standby database was unable to participate in the STOP OBSERVER operation. You may correct the problem that is indicated by that information and retry the operation. Alternatively, you may forcibly disable Fast-Start Failover while connected to the primary database using the DISABLE FAST_START FAILOVER FORCE command in the DGMGRL CLI. You can then stop the observer regardless of the current state of the target standby database. ORA-16637: an instance failed to access the Data Guard broker configuration Cause: When an instance was started, the DMON process on the instance failed to access the Data Guard broker configuration. This can happen if the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 initialization parameters are not set up correctly to point to the broker configuration files shared among all instances. Action: Set DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 to the correct file specifications that point to the broker configuration files shared among all instances. Bounce the DMON process by setting DG_BROKER_START initialization parameter to FALSE and then to TRUE. ORA-16638: could not get the instance status Cause: The broker failed to check whether the given instance was alive or not. Action: See the next error message in the error stack for more detailed information. If the situation described in the next error in the stack can be corrected, do so; otherwise, contact Oracle Support Services. ORA-16639: specified instance inactive or currently unavailable Cause: An attempt was made to perform an operation on an instance that was not running or was unavailable. Action: Ensure that the instance specified in the operation is running and then retry the operation. ORA-16640: CRS warns that multiple instances may still be running Cause: A broker operation was underway that required CRS to stop monitoring the instances of this database and to shut down all but one instance. Although instance monitoring has ceased, CRS cannot guarantee that only one instance remains running. The broker operation was canceled. Action: Suspend CRS management of this database using SRVCTL STOP DATABASE -D -O NONE. Then reissue the broker request. ORA-16641: failure to acquire broker configuration metadata lock Cause: Internal error Action: Contact Oracle Support Services. ORA-16642: db_unique_name mismatch Cause: The expected db_unique_name value did not match the actual db_unique_name value for the database that the broker contacted using the connect identifier that was associated with that database. Action: Verify that the connect identifier correctly connects to the intended database. Verify that the name of the database that the broker expects to find via that connect identifier matches the actual db_unique_name for that database. ORA-16643: unable to determine location of broker configuration files Cause: The Data Guard broker was unable to determine the location of its configuration files from the DG_BROKER_CONFIG_FILE[1|2] initialization parameters. Action: Retry the operation and if the error persists, contact Oracle Support Services. ORA-16644: apply instance not available Cause: The broker operation could not finish, because it requires a running apply instance for the standby database, and either there was no such instance designated for the standby database or the designated apply instance was not currently available. Action: Start the designated apply instance or wait until the broker specifies an instance to be the apply instance and reissue the command. ORA-16645: unexpected new instance interrupted current operation Cause: A new instance unexpectedly joined the Data Guard configuration at a point when the current operation may proceed only if the set of known instances is not changing dynamically. Action: Reissue the operation after the new instance has joined the Data Guard configuration. ORA-16646: Fast-Start Failover is disabled Cause: The operation was not allowed because Fast-Start Failover is disabled. Action: Enable Fast-Start Failover and retry the operation. ORA-16647: could not start more than one observer Cause: The observer could not start because there was another observer already observing the Data Guard configuration for which Fast-Start Failover may have been enabled. Action: Stop the running observer. Retry the operation. ORA-16648: a new observer registered with identifier string Cause: The observer is registered with the Data Guard broker and will begin observing the Data Guard configuration for conditions that warrant doing a Fast-Start Failover. Action: None ORA-16649: database will open after Data Guard broker has evaluated Fast-Start Failover status Cause: The database is being opened while Fast-Start failover is enabled. The message indicates that the Data Guard broker will first determine if conditions are suitable for opening; that is, a Fast-Start failover did not occur while the database was unavailable. Action: No action is normally required. The Data Guard broker will continue opening the database after determining a Fast-Start failover did not occur. If there is a chance that a Fast-Start Failover did occur, the database will remain in the mounted state and will not open. In this case, check the target standby to see if a role transition took place. ORA-16650: command incompatible when Fast-Start Failover is enabled Cause: An attempt was made to issue a command which is not permitted when Fast-Start Failover is enabled. The command was not issued using the Data Guard broker. Action: The attempted command must be issued using the Data Guard broker. ORA-16651: requirements not met for enabling Fast-Start Failover Cause: The attempt to enable Fast-Start Failover could not be completed because one or more requirements have not been met: - The Data Guard configuration must be in MaxAvailability protection mode. - The LogXptMode property for both the primary database and the Fast-Start Failover target standby database must be SYNC. - The primary database and the Fast-Start Failover target standby database must both have flashback enabled. - No valid target standby database was specified in the primary database"s FastStartFailoverTarget property prior to the attempt to enable Fast-Start Failover, and more than one standby database exists in the Data Guard configuration. Action: Retry the attempted command after correcting the issue: - Set the Data Guard configuration to MaxAvailability protection mode. - Ensure that the LogXptMode property for both the primary database and the Fast-Start Failover target standby database are SYNC. - Ensure that both the primary database and the Fast-Start Failover target standby database have flashback enabled. - Set the primary database"s FastStartFailoverTarget property to the db_unique_name value of the desired target standby database add the desired target standby database"s FastStartFailoverTarget property to the db_unique_name value of the primary database. ORA-16652: Fast-Start Failover target standby database is disabled Cause: The command to enable or disable Fast-Start Failover could not be completed because Data Guard broker management of the Fast-Start Failover target standby database is currently disabled. Action: Enable broker management of the target standby database and reissue the command. If you are attempting to disable Fast-Start Failover when this error is reported, you may opt to disable Fast-Start Failover with the FORCE option. See the description for DGMGRL"s DISABLE FAST_START FAILOVER [FORCE] command for more information. ORA-16653: failed to reinstate database Cause: The Data Guard broker failed to reinstate the specified database because the REINSTATE command failed or because the database is already enabled. Action: Additional information about this failure is recorded in the primary database"s and/or the specified database"s Data Guard broker log files. This information will be helpful in determining how to proceed. ORA-16654: Fast-Start Failover is enabled Cause: The attempted command was not allowed while Fast-Start Failover (FSFO) was enabled: - The FastStartFailoverTarget property may not be modified. - The LogXptMode property for either the primary database or the FSFO target standby database may not be modified. - Neither the broker configuration or the FSFO target standby database may be disabled using the DGMGRL CLI"s DISABLE command. - Neither the broker configuration or the FSFO target standby database may be removed using the DGMGRL CLI"s REMOVE command. - The FAILOVER IMMEDIATE command is not allowed. Action: Disable Fast-Start Failover, using the FORCE option if required. Then retry the attempted command. ORA-16655: specified target standby database invalid Cause: The attempted command was not allowed because Fast-Start Failover was enabled for this Data Guard configuration and the target standby database specified in the command differs from the standby database that was indicated by the FastStartFailoverTarget property associated with the current primary database. Action: Retry the attempted command by specifying the standby database that is indicated by the FastStartFailoverTarget property that is associated with the current primary database. Alternatively, you may disable Fast-Start Failover. You may then retry the command while specifying the originally specified target standby database. ORA-16656: higher DRC UID sequence number detected Cause: The Data Guard broker detected a higher sequence value during its bootstrap or health check operations. The sequence value is changed each time switchover or failover completes successfully. Action: Additional information about this failure is recorded in the Data Guard "broker log" files, one for the primary database and one for each standby database in the Data Guard configuration. This information will be helpful in determining how best to proceed from this failure. ORA-16657: reinstatement of database in progress Cause: Reinstatement of this database was in progress. Action: No action is necessary. ORA-16658: unobserved Fast-Start Failover configuration Cause: The Fast-Start Failover configuration was currently unobserved so failover was disallowed. Action: Make sure the observer is running and has connectivity to both the primary and the target standby databases. Otherwise, disable Fast-Start Failover to allow a failover in the absence of the observer process. ORA-16659: failover operation in progress Cause: A primary database that restarted contacted a standby database that is being failed over to. Action: Shutdown the primary database and wait for failover to complete on the standby database. Once failover is complete, restart the old primary database. If the failover occurred due to Fast-Start Failover, restarting the primary database after failover is complete will allow it to be automatically reinstated as a standby database to the new primary database. ORA-16660: FSFO operation attempted in absence of a broker configuration Cause: An attempt was made to enable or disable Fast-Start Failover when connected to a standby database for which broker configuration details are currently unavailable. For instance, the standby database may currently require re-creation (or flashback reinstantiation) before it may respond to broker client commands. Action: 1) An attempt to enable or disable (non-FORCE) Fast-Start Failover at this standby database will be rejected until such time that the broker configuration details have been made available to that standby database"s DMON process from the primary"s DMON process. This normally occurs when the standby database is successfully re-created or flashed back, and then reenabled at the primary database. 2) You may use the FORCE option to override Fast-Start Failover that has been enabled at the standby database even when the broker configuration details are currently unavailable to the standby database. In this case, this status message is only a warning. Note that FSFO is not formally disabled in the broker configuration. The effect of this command issued under these circumstances may or may not be permanent, depending upon when the primary and standby databases regain full communication between each other at a later point in time and if the state of Fast-Start Failover had been altered at the primary database in the meantime. ORA-16661: the standby database needs to be reinstated Cause: A switchover or failover operatione has caused this database to require reinstatement. Action: Use the DGMGRL REINSTATE DATABASE command or Enterprise Manager to reinstate the database. If the target database has flashback enabled and it has sufficient flashback logs, the database will be reinstated as a standby database for the current primary database. ORA-16700: the standby database has diverged from the primary database Cause: The primary database may have been flashed back or restored from a backup set and then reopened with the RESETLOGS option. Action: Re-create the standby database from the primary database or flash back the standby database to the same point the primary database had been flashed back to. ORA-16701: generic resource guard request failed Cause: Request to modify or query the resource failed. Action: Check the Data Guard broker log for the reason for the failure, and reissue the request. ORA-16702: generic resource guard warning Cause: A request to modify or query the resource resulted in a warning. Action: Check the Data Guard broker log for the reason for the warning, and if necessary reissue the request. ORA-16703: cannot set property while the database is enabled Cause: An attempt was made to change a database property while the database was enabled. Action: Disable broker management of the database first, then update the property and reenable the database. ORA-16704: cannot modify a read-only property Cause: An attempt was made to change a read-only property. Action: The property is controlled internally by the Data Guard broker and cannot be modified. ORA-16705: internal error in resource guard Cause: Internal error Action: Contact Oracle Support Services. ORA-16706: no resource guard is available Cause: No resource guard is available to service the request. Action: Contact Oracle Support Services. ORA-16707: the value of the property string is invalid, valid values are string Cause: An invalid property value was entered while broker management of the database was disabled. Action: Reset the value to a correct one. ORA-16708: the state supplied to resource guard is invalid Cause: The state name specified is invalid for the database. Action: Check the state name and reissue the request. ORA-16709: standby archived log location settings conflict with flash recovery area Cause: The flash recovery area was already set up on the standby database for storing incoming archived logs from the primary database. In this case, the StandbyArchiveLocation and AlternateLocation properties should not be used for setting up a standby archived log location. The Data Guard broker raised this error because it detected one of the following: (1) the user attempted to use the StandbyArchiveLocation or AlternateLocation properties to set up a standby archived log location; (2) On the standby database, a local destination corresponding to the StandbyArchiveLocation or AlternateLocation property was still set up to store archived logs from the primary database. Action: If you get this error when trying to set property StandbyArchiveLocation or AlternateLocation (case (1) above), avoid setting these properties. If you get this error after a broker health check (case (2) above), reenable the standby database to clear the error. ORA-16710: the resource guard is out of memory Cause: The resource guard was unable to allocate memory while trying to service a request. Action: Disable broker management of the configuration, shut down Oracle, increase SGA size, and restart. ORA-16711: the resource guard index is out of bounds Cause: Internal error Action: Contact Oracle Support Services. ORA-16712: the resource handle is invalid Cause: Internal error Action: Contact Oracle Support Services. ORA-16713: the resource guard timed out while servicing the request Cause: The resource guard timed out while servicing the request. Action: Verify that the operation is valid for the database and then reissue the request. ORA-16714: the value of property string is inconsistent with the database setting Cause: The value of the specified configuration property is inconsistent with database in-memory settings or server parameter file settings. This may be caused by changing an initialization parameter that corresponds to a configuration property. Action: Query property InconsistentProperties on the database to determine the inconsistent values. Reset the property to make it consistent with the database setting. ORA-16715: redo transport-related property string of standby database "string" is inconsistent Cause: The value of the specified redo transport-related configuration property of the given standby database is inconsistent with the primary database"s redo transport service setting. This may be caused by changing an initialization parameter that corresponds to a configuration property. Action: Query property InconsistentLogXptProps on the primary database to determine the inconsistent values. Reset the property on the standby database to make it consistent with the primary database"s redo transport setting. ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed Cause: An attempt to clear the LOG_ARCHIVE_DEST parameter failed. Action: Contact Oracle Support Services. ORA-16717: clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST parameter failed. Action: Contact Oracle Support Services. ORA-16718: failed to locate database object Cause: The resource guard was unable to locate the database in the broker configuration. Action: Add the database to the broker configuration and then reissue the request. ORA-16719: unable to query V$ARCHIVE_DEST fixed view Cause: The broker failed to query the V$ARCHIVE_DEST fixed view." Action: Test and clear the problem using SQL*Plus. ORA-16720: no LOG_ARCHIVE_DEST_n initialization parameters available Cause: All LOG_ARCHIVE_DEST_n initialization parameters are in use. Action: Clear one or more LOG_ARCHIVE_DEST_n initialization parameters so that broker can use them to setup the primary database"s redo transport. ORA-16721: unable to set LOG_ARCHIVE_DEST_n initialization parameters Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_n initialization parameters. Action: Check the Data Guard broker log and Oracle alert logs for more details. ORA-16722: unable to set LOG_ARCHIVE_DEST_STATE_n initialization parameters Cause: The broker was unable to set one or more LOG_ARCHIVE_DEST_STATE_n initialization parameters. Action: Check the Data Guard broker log and Oracle alert logs for more details. ORA-16723: setting AlternateLocation property conflicts with the redo transport setting Cause: The standby database is not using standby redo logs, and the redo transport service to the standby database is set with a nonzero value of ReopenSecs and a zero value of MaxFailure. In this case, the redo transport service will retry the standby destination indefinitely and never switch to the alternate destination. Action: Any one of the following actions will solve the problem: (1) add standby redo logs to the standby database; (2) set ReopenSecs property to zero; (3) set MaxFailure property to a nonzero value. After executing one of the above actions, reset the AlternateLocation property. ORA-16724: the intended state for the database has been set to OFFLINE Cause: The intended state of the database has been set to offline. Action: If broker management of the database is currently enabled, set the database"s state to online. ORA-16725: the phase supplied to resource guard is invalid Cause: Internal error Action: Contact Oracle Support Services. ORA-16726: the external condition supplied to resource guard is invalid Cause: Internal error Action: Contact Oracle Support Services. ORA-16727: resource guard cannot close database Cause: The resource guard could not close the database. Action: Check if there any active sessions connect to the database, terminate them, then reissue the request. ORA-16728: consistency check for property string found string error Cause: The consistency check for the specified property failed due to the error shown. Action: Check the error message and clear the error. ORA-16729: validation of value for property string found string error Cause: The property value validitation failed due to the error shown. Action: Check the error message and clear the error. ORA-16730: error executing dbms_logstdby.skip_txn procedure Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. ORA-16731: error executing dbms_logstdby.unskip_txn procedure Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. ORA-16732: error executing dbms_logstdby.skip procedure Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. ORA-16733: error executing dbms_logstdby.unskip procedure Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. ORA-16734: error executing dbms_logstdby.skip_error procedure Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. ORA-16735: error executing dbms_logstdby.unskip_error procedure Cause: Logical standby database package may not be installed. Action: Install logical standby database packages and reissue the request. ORA-16736: unable to find the destination entry of standby database "string" in V$ARCHIVE_DEST Cause: Either the standby destination was manually changed or deleted outside the Data Guard broker"s control, or no entry was available for Data Guard broker. Action: Clean up the destination setting, remove the unused ones, and reset the redo transport service. ORA-16737: the redo transport service for standby database "string" has an error Cause: A communication problem with the standby database caused the redo transport to fail. Action: Query the LogXptStatus property to see the error message. Check the Data Guard broker log and Oracle alert log for more details. ORA-16738: redo tranport service for standby database "string" unexpectedly offline Cause: The redo transport service for the standby database was offline instead of online. Action: Check the Data Guard broker log for more details. If necessary, start the redo transport service. ORA-16739: redo transport service for standby database "string" unexpectedly online Cause: The redo transport service for the standby database was online instead of offline. Action: Check the Data Guard broker log for more details. If necessary, stop the redo transport service for the standby database. ORA-16740: redo transport service for standby database "string" incorrectly set to ALTERNATE Cause: The redo transport service to the standby database is currently set to ALTERNATE when no other destination is set to alternate to this destination. Action: Reset the database state to turn on redo transport again if necessary. ORA-16741: the destination parameter of standby database "string" has incorrect syntax Cause: The destination defined in the server parameter file of the primary database has incorrect syntax and Data Guard broker failed to update the destination when redo transport services were enabled. Action: Fix the syntax error in the primary database"s server parameter file or remove the entry from the server parameter file. Also Check the values of the redo transport-related properties for the specified standby database. ORA-16742: the standby database "string" has exhausted its quota Cause: The standby database has exhausted its quota for storing archived redo logs. Action: Remove some archived logs from the standby database or increase its quota. ORA-16743: the status of redo transport service for standby database "string" is unknown Cause: The status of redo transport to the specified standby database could not be determined. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16744: the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add a new DB_UNIQUE_NAME to the list. Action: Remove some unused entries in the DG_CONFIG list, then reenable the database. ORA-16745: unable to add DB_UNIQUE_NAME string into the DG_CONFIG list because it is full Cause: The DG_CONFIG list of the LOG_ARCHIVE_CONFIG attribute was full and the Data Guard broker was not able to add the specified DB_UNIQUE_NAME to the list. Action: Remove some unused entries in the DG_CONFIG list, then reenable the database. ORA-16746: resource guard encountered errors during database mount Cause: The resource guard could not mount the database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16747: logical standby database guard could not be turned on Cause: The resource guard could not turn on the logical standby database guard. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16748: resource guard encountered errors during database open Cause: The resource guard could not open the database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16749: resource guard encountered errors in switchover to logical primary database Cause: The resource guard was unable to switch a logical standby database to a primary database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16750: resource guard encountered errors while activating logical primary database Cause: The resource guard could not activate a primary database from a logical standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16751: resource guard encountered errors in switchover to primary database Cause: The resource guard was unable to switch a standby database to a primary database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16752: resource guard could not mount standby database Cause: The resource guard could not mount the standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16753: resource guard could not open standby database Cause: The resource guard could not open the standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16754: resource guard could not activate standby database Cause: The resource guard could not activate the standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16755: failed to set initialization parameter Cause: The ALTER SYSTEM SET or ALTER SYSTEM RESET command issued by the Data Guard broker failed. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16756: resource guard could not open standby database read-only Cause: The resource guard could not open the standby database read-only. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16757: resource guard could not get property Cause: The resource guard failed to get the specified property. Action: Check the Data Guard broker log for more details. ORA-16758: the specified apply instance is not running Cause: The apply instance specified by the user is not running, so the Data Guard broker cannot move the apply service to that instance. Action: Start the instance that you wish the apply service to upon and retry the command. ORA-16759: resource guard unable to start SQL Apply with initial SCN Cause: The resource guard failed to start SQL Apply with an initial SCN. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16760: resource guard could not start SQL Apply Cause: The resource guard failed to start SQL Apply. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16761: resource guard could not stop SQL Apply Cause: The resource guard failed to stop SQL Apply. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16762: invalid database state Cause: Database was not in the intended state. Action: Determine the reason for invalid state, and reissue the get status request. ORA-16763: redo transport service for a standby database is online Cause: The redo transport service for a standby database was online instead of offline. Action: Query the StatusReport property of the primary database for more details. If necessary, stop the redo transport service for the database. ORA-16764: redo transport service to a standby database is offline Cause: The redo transport service to a standby database was offline instead of online. Action: Query the StatusReport property of the primary database for more details. If necessary, start the redo transport service. ORA-16765: Redo Apply is unexpectedly online Cause: Redo Apply was online when it should be offline. Action: If necessary, stop Redo Apply. ORA-16766: Redo Apply unexpectedly offline Cause: Redo Apply was offline when it should be online. Action: If necessary, start Redo Apply. ORA-16767: SQL Apply unexpectedly online Cause: SQL Apply was online when it should be offline. Action: If necessary, stop SQL Apply. ORA-16768: SQL Apply unexpectedly offline Cause: SQL Apply was offline when it should be online. Action: If necessary, start SQL Apply. ORA-16769: the physical standby database is open read-only Cause: All instances in the physical standby database were put into a read-only state instead of LOG-APPLY-OFF. Action: Issue the set state command to move the database to LOG-APPLY-OFF state. ORA-16770: physical standby database not in read-only state Cause: All instances in the physical standby database were put into a LOG-APPLY-OFF state instead of READ-ONLY. Action: Issue the set state command to move the database to READ-ONLY state. ORA-16771: failover to a physical standby database failed Cause: In the failover operation, the step of converting the physical standby database to the primary database failed. Action: Check the alert log and the Data Guard broker log for more details about the error. ORA-16772: error switching over between primary and standby databases Cause: There was an error during switchover of primary and standby databases. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16773: error starting Redo Apply Cause: There was an error starting Redo Apply on a physical standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16774: error stopping Redo Apply Cause: There was an error stopping Redo Apply on a physical standby database. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16775: target standby database in broker operation has potential data loss Cause: The target standby database in the broker operation did not have all the redo logs from the primary database. The switchover or protection mode upgrade to maximum protection could not be performed. Action: Query the SendQEntries monitorable property on the primary database to see which redo logs are missing. Confirm that the redo transport service on the primary database is functioning correctly by checking its status using the StatusReport monitorable property. Perform log switches on the primary database in order to activate the redo log gap fetching mechanism. Once all redo logs are available on the target standby database, reissue the broker command. ORA-16776: health check of the redo transport service failed Cause: Due to some internal failure, the database resource guard could not complete the health check of the redo transport service. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST Cause: Either a destination was manually deleted or no entry was available for Data Guard. Action: Check the Data Guard broker log and the Oracle alert log for more details. The redo transport service may need to be reset. ORA-16778: redo transport error for one or more databases Cause: The redo transport service was unable to send redo data to one or more standby databases. Action: Check the Data Guard broker log and Oracle alert log for more details. Query the LogXptStatus property to see the errors. ORA-16779: the destination parameter of a database is set incorrectly Cause: The destination was defined in the LOG_ARCHIVE_DEST_n server parameter file with incorrect syntax. The Data Guard broker failed to update the destination when the redo transport was turned on. Action: Check the Data Guard broker log to see which database has the problem. Fix the syntax error in the server parameter file or remove the entry from the server parameter file. Check if the syntax of the redo transport-related properties are correct. ORA-16780: a database has exhausted its archived redo log storage quota Cause: A database has exhausted its quota for storing archived redo logs. Action: Check the Data Guard broker log to see which database has the problem. Remove some archived logs at the standby database or increase its quota. ORA-16781: the status of redo transport service for a database is unknown Cause: The redo transport service status to a standby database could not be determined. Action: Check the Data Guard broker log and Oracle alert log for more details. ORA-16782: instance not open for read and write access Cause: An instance was left in a mounted mode and was not open for read and write access. Action: Query the StatusReport property for more details. Open the instance manually or by reenabling the database through the Data Guard broker. ORA-16783: instance string not open for read and write access Cause: The instance was left in a mounted mode and was not open for read and write access. Action: Open the instance manually or by reenabling the database through the Data Guard broker. ORA-16784: the database name in Dependency property is incorrect Cause: The database name, which should be the value of the DB_UNIQUE_NAME initialization parameter, specified in property Dependency is incorrect. Action: Reset the Dependency property to the correct name of the database. ORA-16785: the database is not in ARCHIVELOG mode Cause: The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to be a primary database. Action: Reset the database to ARCHIVELOG mode by issuing ALTER DATABASE ARCHIVELOG command. ORA-16786: resource guard cannot access Data Guard broker metadata Cause: The Data Guard broker configuration files did not exist or for some other reason the resource guard could not access the Data Guard broker configuration metadata. Action: Check the Data Guard broker log for more details. ORA-16788: unable to set one or more database configuration property values Cause: This situation occurs when the database resource guard attempted to set database configuration property values into the database by issuing "ALTER SYSTEM" or "ALTER DATABASE" commands. Typical causes of this error are: a) The values of redo transport-related properties have syntax errors; b) The Value of LogArchiveTrace is out of range; c) Database initialization parameter STANDBY_FILE_MANAGEMENT cannot be set to AUTO because the database compatability is not set to 9.0.0.0.0 or higher. Action: Check the Data Guard broker log to see which property has the problem and reset the property correctly. ORA-16789: missing standby redo logs Cause: Standby redo logs are missing and are needed for SYNC and ASYNC log transport modes. Action: Check the Data Guard documentation to see how to create standby redo logs. ORA-16790: the value of the configurable property is invalid Cause: User entered an invalid property value. Action: Reset the property to a correct value. ORA-16791: unable to check the existence of the standby redo logs Cause: The database may not be mounted, or the query of V$STANDBY_LOG failed. Action: Bring the database to the mounted state and then query V$STANDBY_LOG to see if the problem has been corrected. Then retry the operation. ORA-16792: configuration property value is inconsistent with database setting Cause: The values of one or more configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker. Action: Query property the InconsistentProperties on the database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters. ORA-16793: logical standby database guard is unexpectedly off Cause: The logical standby database guard was unexpectedly turned off. Action: Issue the ALTER DATABASE GUARD ALL command to turn the guard on and verify that Data Guard health check error/warning is cleared. ORA-16794: database guard is on for primary database Cause: The database guard was turned on for the primary database. Action: Issue the ALTER DATABASE GUARD NONE to turn off the guard and verify that Data Guard health check error/warning is cleared. ORA-16795: database resource guard detects that database re-creation is required Cause: In the act of failover or switchover, the database resource guard may have detected that re-creation of the database is necessary. 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. Until this error status is resolved for this database, information about this database and the broker configuration to which it belongs is unavailable to a broker client that is connected to this database. Therefore, all commands directed by that client to this database cannot be completed. Action: Re-create (or flash back) the standby database. Connect to the primary database in the broker configuration and reenable broker management of that database. At this point you may connect to that standby database and resume issuing client commands. Alternatively, many client commands that cannot be completed at the standby database when in this error state can be completed successfully when issued to the primary database. In this case, simply reconnect to the primary database and retry the command. ORA-16796: one or more properties could not be imported from the database Cause: The broker was unable to import property values for the database being added to the broker configuration. This error indicates: - the net-service-name specified in DGMGRL"s CREATE CONFIGURATION or ADD DATABASE command is not one that provides access to the database being added, or - there are no instances running for the database being added. Action: Remove the database from the configuration using the REMOVE CONFIGURATION or REMOVE DATABASE command. Make sure that the database to be added has at least one instance running and that the net-service-name provides access to the running instance. Then reissue the CREATE CONFIGURATION or ADD DATABASE command. ORA-16797: database is not using a server parameter file Cause: The database is not using a server parameter file or the resource guard was unable to access the server parameter file. Action: Issue CREATE SPFILE=".." FROM PFILE="..."" command to create a server parameter file and then restart the database to use it. ORA-16798: unable to complete terminal recovery on the standby database Cause: Terminal recovery on the standby database failed during the failover operation. Action: Check Data Guard broker log and alert logs to see more details on the reason of the failure. ORA-16799: Redo Apply is offline Cause: Either the Data Guard broker metadata indicates that Redo Apply is turned off, or the recovery process, MRP0, is not running. In either of the cases, Redo Apply-related properties cannot be set. Action: Turn on Redo Apply through Data Guard broker and reissue the command to set a Redo Apply-related property. ORA-16800: redo transport service for a standby database incorrectly set to ALTERNATE Cause: The redo transport service for a standby database is currently set to ALTERNATE when no other destination is set to alternate to this destination. Action: Reset the database state to turn on redo transport again if necessary. ORA-16801: redo transport-related property is inconsistent with database setting Cause: The values of one or more redo transport-related configuration properties were inconsistent with database in-memory settings or server parameter file settings. This may happen by altering initialization parameters directly instead of altering property values using Data Guard broker. Action: Query property the InconsistentLogXptProps on the primary database or check the Data Guard broker log to find which properties are set inconsistently. Reset these properties to make them consistent with the database settings. Alternatively, enable the database or the entire configuration to allow the configuration property settings to be propagated to to the initialization parameters. ORA-16802: downgrading redo transport mode from SYNC disallowed Cause: An attempt was made to downgrade the redo transport mode of a standby database from SYNC to ASYNC or ARCH when the configuration was in Maximum Protection or Maximum Availability mode and the primary database was a RAC database. This is not allowed, even if there are other standby databases with log transport modes set to SYNC to support the data protection mode. Action: You can do one of the following if you need to downgrade the redo transport mode of the standby database: (1) Shut down all instances of the primary database and restart one instance with initialization parameter CLUSTER_DATABASE set to FALSE. Downgrade the redo transport mode, shutdown the instance, and restart all instances with CLUSTER_DATABASE set to TRUE. (2) Downgrade the protection mode to Maximum Performance mode first. Then downgrade the redo transport mode, then upgrade the protection mode again (which involves a shutdown and restart of the primary database). Note that the above only works when there exists at least one more standby database in the configuration that has the log transport mode set to SYNC. ORA-16803: unable to query a database table or fixed view Cause: Failed to query a database table or fixed view. The database may not be open or mounted. Action: Check Data Guard broker log for more details. ORA-16804: one or more configuration properties in metadata have invalid values Cause: Data Guard broker health check detected that one or more configuration properties in the broker"s configuration metadata have invalid values. The property values have been changed while broker management of the database is disabled. Action: Check Data Guard broker log for more details on which properties have invalid values and reset them through the Data Guard broker. ORA-16805: change of LogXptMode property violates overall protection mode Cause: The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database. The rejection was necessary to avoid violating the overall protection mode for the configuration. Action: If the LogXptMode configuration property must be changed for the specified standby database, first downgrade the overall protection mode for the broker configuration. After that operation has completed, you will be able to change the LogXptMode configuration property for the standby database. ORA-16806: supplemental logging is not turned on Cause: Supplemental logging was not turned on while there is a logical standby database in the configuration. This could happen either on the primary or on the logical standby database that is being switched over to be the primary database. Action: Check Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging. ORA-16807: unable to change database protection mode Cause: An attempt to issue the ALTER DATABASE SET STANDBY TO MAXIMIZE {PROTECTION | AVAILABILITY | PERFORMANCE} failed. Action: Check the Oracle alert log and Data Guard broker log for more information. ORA-16808: unable to resolve the full path name Cause: An attempt to resolve the full path name from a string failed. Action: Check the Data Guard broker log for the full error stack. This likely the result of an operating system error. ORA-16809: multiple warnings detected for the database Cause: The broker has detected multiple warnings for the database. Action: Check the StatusReport monitorable property of the database specified. ORA-16810: multiple errors or warnings detected for the database Cause: The broker detected multiple errors or warnings for the database. Action: Check the StatusReport monitorable property of the database specified. ORA-16811: apply instance not recorded by the Data Guard broker Cause: The broker has not registered an apply instance for a standby database. Action: Reenable the standby database to clear the error. ORA-16812: log apply service not running on apply instance recorded by the broker Cause: Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon. Action: Reenable the standby database to clear the error. ORA-16813: log apply service not running on apply instance string recorded by the broker Cause: Log apply services are not running on the apply instance the Data Guard Broker expects them to be running upon. Action: Reenable the standby database to clear the error. ORA-16814: incorrect redo transport setting for AlternateLocation for standby database Cause: The Data Guard broker detected that an incorrect redo transport setting for a standby database"s AlternateLocation property. The incorrect setting could be one of the following: one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error. Action: Reenable the primary database to clear the error. ORA-16815: incorrect redo transport setting for AlternateLocation for standby database "string" Cause: The Data Guard broker detected that the redo transport setting for the standby database regarding its AlternateLocation property value is incorrect. The incorrect setting could be one of the following: (1) the AlternateLocation property is empty but the log transport to the standby database has an ALTERNATE setting; (2) the AlternateLocation property is not empty but the log transport to the standby database has no ALTERNATE setting; (3) the AlternateLocation property does not match the ALTERNATE setting in the redo transport. The mismatch may include service string, directory specification of the alternate location, or the DB_UNIQUE_NAME attribute; (4) the log_archive_dest_state_n parameter corresponding to the alternate location is not set to ALTERNATE; (5) the flash recovery area is being used by the standby database for archived logs, but the redo transport to the standby database still has an ALTERNATE setting for the AlternateLocation. Data Guard broker logs provide more details on which of the above cases causes the error. Action: Reenable the primary database to clear the error. ORA-16816: incorrect database role Cause: The Data Guard broker detected that this database object had a database role that was different from the recorded database role in the Data Guard Configuration. This could be the result of a failed switchover or failover operation, or an out-of-band switchover or failover operation done to the database. Action: Manually fix the database to convert it to the appropriate database role, then issue an ENABLE DATABASE command to reenable the database object. ORA-16817: unsynchronized Fast-Start Failover configuration Cause: The Fast-Start Failover target standby database was not synchronized with the primary database. As a result, a Fast-Start Failover could not happen automatically in case of a primary database failure. Action: Ensure that the Fast-Start Failover target standby database is running and that the primary database can ship redo logs to it. When the standby database has received all of the redo logs from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database. ORA-16818: Fast-Start Failover suspended Cause: The primary database was intentionally shutdown. As a result, a Fast-Start Failover could not happen automatically. Action: Start up the primary database. This effectively restores the ability to automatically do a Fast-Start Failover in the event of a failure of the primary database. ORA-16819: Fast-Start Failover observer not started Cause: The observer for Fast-Start Failover was not started. As a result, Fast-Start Failover could not happen in the case of a primary database failure. Action: Start the Fast-Start Failover observer by using, for example, the DGMGRL START OBSERVER command. ORA-16820: Fast-Start Failover observer is no longer observing this database Cause: A previously started observer was no longer actively observing this database. A significant amount of time elapsed since this database last heard from the observer. Possible reasons were: - The node where the observer was running was not available. - The network connection between the observer and this database was not available. - Observer process was terminated unexpectedly. Action: Check the reason why the observer cannot contact this database. If the problem cannot be corrected, stop the current observer by connecting to the Data Guard configuration and issue the DGMGRL "STOP OBSERVER" command. Then restart the observer on another node. You may use the DGMGRL "START OBSERVER" command to start the observer on the other node. ORA-16821: logical standby database dictionary not yet loaded Cause: Logical standby apply had not finished loading the dictionary. This warning is flagged by the broker"s health check mechanism. This error is also flagged by failover and switchover if the target standby database has not loaded its dictionary. Action: Start SQL Apply on the logical standby database and wait for it to reach the APPLYING state. ORA-16822: new primary database not yet ready for standby database reinstatement Cause: The new primary database, as a result of a logical failover operation, had not fully completed the failover steps. Subsequent reinstatement operations could not proceed until failover has completed on the new primary database. Action: Wait until the completion of all failover steps on this new primary database and then retry the reinstate operation. ORA-16823: redo transport mode is incompatible for current operation Cause: The redo transport mode of this database was incompatible for this broker operation. Action: Reset the LogXptMode database property for this database and retry the broker operation. ORA-16824: Fast-Start Failover and other warnings detected for the database Cause: The broker has detected multiple warnings for the database. At least one of the detected warnings may prevent a Fast-Start Failover from occurring. Action: Check the StatusReport monitorable property of the database specified. ORA-16825: Fast-Start Failover and other errors or warnings detected for the database Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring. Action: Check the StatusReport monitorable property of the database specified. ORA-16826: apply service state is inconsistent with the DelayMins property Cause: This warning was caused by one of the following reasons: 1. Apply service was started without specifying the real time apply option or without the NODELAY option while DelayMins is zero. 2. Apply service was started with the real-time apply option or with the NODELAY option while DelayMins is greater than zero. Action: Reenable the standby database to allow the broker to restart the apply service with the apply options that are consistent with the specified value of the DelayMins property. ORA-16950: Remote mapped cursors are not supported by this feature. Cause: This cursor is a remote mapped cursor which could not be processed locally. Action: Try to process this statement directly on the remote site. ORA-16951: Too many bind variables supplied for this SQL statement. Cause: Binding this SQL statement failed because too many bind variables were supplied. Action: Pass the correct number of bind variables. ORA-16952: Failed to bind this SQL statement. Cause: Binding this SQL statement failed. Action: Check if bind variables for that statement are properly specified. ORA-16953: Type of SQL statement not supported. Cause: This type of SQL statement could not be processed. Action: none ORA-16954: SQL parse error. Cause: The specified SQL statement failed to be parsed. Action: Check if syntax is correct and ensure that this statement can be parsed by the specified user name. ORA-16955: Unknown error during SQL analyze. Cause: The specified SQL statement failed to be analyzed. Action: This is an internal error, please contact Oracle support. ORA-16956: Only SELECT or DML statements are supported for test execute. Cause: The specified SQL statement cannot be tested for execute. Action: none ORA-16957: SQL Analyze time limit interrupt Cause: This is an internal error code used indicate that SQL analyze has reached its time limit. Action: none ORA-16958: DML statements running parallel are not supported for test execute. Cause: The specified DML statement cannot be tested for execute because part of it is running parallel. Action: none ORA-17500: ODM err:string Cause: An error returned by ODM library Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance ORA-17501: logical block size string is invalid Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum Action: check INIT.ORA file parameters ORA-17502: ksfdcre:string Failed to create file string Cause: file creation failed due to either insufficient OS permission or the file already exists Action: check additional error messages ORA-17503: ksfdopn:string Failed to open file string Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length. Action: check additional error messages ORA-17504: ksfddel:Failed to delete file string Cause: The file that was being deleted is still in use or the process has insufficient permission to delete file. Action: check additional error messages ORA-17505: ksfdrsz:string Failed to resize file to size string blocks Cause: There is insufficient space left on the device or the process has insufficient permission to resize file. Action: check additional error messages ORA-17506: I/O Error Simulation Cause: The i/o request is marked with error because the i/o error simulation event is turned on. Action: none ORA-17507: I/O request size string is not a multiple of logical block size Cause: i/o"s are done in multiple of logical block size Action: Check additional error messages ORA-17508: I/O request buffer ptr is not alligned Cause: i/o request buffer should be alligned, check additional information for buffer ptr value Action: Call Oracle Support Services ORA-17509: Attempt to do i/o beyond block1 offset Cause: When a file is identified with logical block size of 0, only i/o"s to block1 is allowed. Action: check additional error messages and call Oracle Support Services ORA-17510: Attempt to do i/o beyond file size Cause: The i/o request points to a block beyond End Of File Action: check additional error messages and call Oracle Support Services ORA-17610: file "string" does not exist and no size specified Cause: An attempt to create a file a file found neither an existing file nor a size for creating the file. Action: Specify a size for the file. ORA-17611: ksfd: file "string" cannot be accessed, global open closed Cause: An attempt to write to a file which has gone offline/unidentified Action: Check for other errno in the stack ORA-17612: Failed to discover Oracle Disk Manager library, return value string Cause: Discovery of the odm library by calling odm_discover() failed Action: Contact your storage vendor who has provided the ODM library or call Oracle Support ORA-17613: Failed to initialize Oracle Disk Manager library: string Cause: ODM initialization for the thread failed due to insufficient previlige or memory. Action: Make sure there is enough system resources available for the oracle process and it has access to the ODM library ORA-17618: Unable to update block 0 to version 10 format Cause: An attempt was made to update block 0 to version 10 format. Action: Check additional error messages and call Oracle Support Services ORA-17619: max number of processes using I/O slaves in a instance reached Cause: An attempt was made to start large number of processes requiring I/O slaves. Action: There can be a maximum of 35 processes that can have I/O slaves at any given time in a instance. ORA-17620: failed to register the network adapter with Oracle Disk Manager library: string Cause: The ODM library returned an error while trying to register the network adapter. Action: Make sure the network adapter name given in the fileio_network_adapters is a valid name, and that the Oracle user has the correct access privileges. ORA-17621: failed to register the memory with Oracle Disk Manager library Cause: The ODM library returned an error while trying to register the memory. Action: Contact the Oracle Disk Manager Library provider. ORA-17622: failed to deregister the memory with Oracle Disk Manager library Cause: The ODM library returned an error while trying to deregister the memory. Action: Contact the Oracle Disk Manager Library provider ORA-17624: Failed to delete directory string Cause: The directory that was being deleted is still in use or the process had insufficient permission to delete the directory. Action: check additional error messages. ORA-17626: ksfdcre: string file exists Cause: trying to create a database file, but file by that name already exists Action: verify that name is correct, specify REUSE if necessary ORA-18000: invalid outline name Cause: The parser detected a missing or invalid outline name Action: none ORA-18001: no options specified for ALTER OUTLINE Cause: The parser detected that no clause was specified on the command Our performance tests, which are not typical as they exercise all branches of the code, have shown approximately a 30% performance increase line for ALTER OUTLINE. Action: Re-issue the command, specifying a valid ALTER OUTLINE clause. ORA-18002: the specified outline does not exist Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream. Action: none ORA-18003: an outline already exists with this signature Cause: The signature generation algorithm generates signatures that are 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. Action: Either re-issue the statement that led to the outline being created with some whitespace added or force the outline to be created in a different category. ORA-18004: outline already exists Cause: An outline already exists, either with the specified name, or for the specified SQL text. Action: none ORA-18008: cannot find OUTLN schema Cause: The database creation script that creates this schema must not have been executed. Action: Review the log files to see what happened when the database was created. ORA-18009: one or more outline system tables do not exist Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table Action: Review the log files to see what happened when the database was created. ORA-18010: command missing mandatory CATEGORY keyword Cause: User failed to specify the CATEGORY keyword Action: Re-issue the command with the CATEGORY keyword included ORA-18015: invalid source outline signature Cause: User imported an 8i outline into a 9i database without updating signatures Action: execute dbms_outln.update_signatures ORA-19000: missing RELATIONAL keyword Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification. Action: Supply the RELATIONAL keyword in the storage clause ORA-19001: Invalid storage option specified Cause: An invalid storage option was specified for the XMLType. Action: Supply a valid storage option. ORA-19002: Missing XMLSchema URL Cause: A XML schema URL must be specified in the storage option. Action: Specify a URL for the XMLSchema. ORA-19003: Missing XML root element name Cause: A root element in the XMLSchema must be specified if the XML schema is given. Action: Specify a root element in the XML schema. ORA-19004: Duplicate XMLType OBJECT RELATIONAL storage option Cause: A duplicate storage option for the XMLType column was specified Action: Specify a single storage option for an XMLType column ORA-19005: Duplicate XMLType LOB storage option Cause: A duplicate storage option for the XMLType column was specified Action: Specify a single storage option for an XMLType column ORA-19006: XMLType TYPE storage option not appropriate for storage type Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column ORA-19007: Schema string does not match expected string. Cause: The given XML document conformed to a different schema than expected. Action: Insert/Update only the XML documents that conform to that particular schema. ORA-19008: Invalid version of the XMLType Cause: An invalid version of the XMLType was found. Action: 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. ORA-19009: Missing XMLSchema keyword Cause: The XMLSchema keyword is missing Action: Specify the XMLSchema URL and element name. ORA-19010: Cannot insert XML fragments Cause: XML fragments got from extractNode cannot be inserted into the database. Action: Convert the fragment into a proper XML document before insertion. ORA-19011: Character string buffer too small Cause: The string result asked for is too big to return back Action: Get the result as a lob instead ORA-19012: Cannot convert XML fragment to the required datatype Cause: A conversion to a datatype was requested which cannot be performed Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype. ORA-19013: Cannot create VARRAY columns containing XMLType Cause: An attempt was made to create a VARRAY column which contains a XMLType Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead ORA-19015: Invalid XML tag identifier (string) Cause: An invalid XML identifer was detected during XML generation Action: Fix the offending tag to not contain characters or symbols that are not allowed by the XML specification ORA-19016: attributes cannot occur after element specifications Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML Action: Change the order of the types so that the attributes occur in the begining ORA-19017: Attributes can only be simple scalars Cause: Attribute values can only be simple scalar values Action: Use only simple datatypes for attribute values ORA-19018: Invalid character in XML tag "string" Cause: A tag name was found to have an invalid XML character during XML generation. Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters. ORA-19019: Invalid context passed to DBMS_XMLGEN.GETXML Cause: The value of context passed to GETXML was invalid. Action: Rewrite the query so that the value of context passed to GETXML is valid. ORA-19020: invalid dereference of XMLType columns Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table Action: You can only dereference the attributes of a base table XMLType column ORA-19023: The first argument to UPDATEXML operator has to be an XMLTYPE Cause: The first argument passed to the update value operator was not an XMLTYPE. Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE. ORA-19024: Cursor expression must be named Cause: The value of context passed to GETXML was invalid. Action: Rewrite the query so that the value of context passed to GETXML is valid. ORA-19025: EXTRACTVALUE returns value of only one node Cause: Given XPath points to more than one node. Action: Rewrite the query so that exactly one node is returned. ORA-19026: EXTRACTVALUE can only retrieve value of leaf node Cause: Given XPath does not point to a leaf node. Action: Rewrite the query so that a leaf node is returned. ORA-19028: Invalid ADT parameter passed to toObject() function Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type. Action: Pass an object of the correct type to toObject(). ORA-19029: Cannot convert the given XMLType to the required type Cause: The passed in XMLType could not be convert to the required type Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types. ORA-19030: Method invalid for non-schema based XML Documents. Cause: The method can be invoked on only schema based xmltype objects. Action: Don"t invoke the method for non schema based xmltype objects. ORA-19031: XML element or attribute string does not match any in type string.string Cause: The passed in XML tag does not match any in the object type Action: Pass a valid canonical XML that can map to the given object type ORA-19032: Expected XML tag string got string Cause: When converting XML to object, a wrong tag name was present Action: Pass a valid canonical XML that can map to the given object type ORA-19033: schema specified in the XML document does not match the schema parameter Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the "schema" parameter. Action: Change the schema parameter to match the schema specified in the XML document. ORA-19034: Type not supported during schema generation Cause: The object type contained a type that is not supported for schema generation. Action: Use a different type or do not generate a schema. ORA-19035: Invalid select item of the query in newContextFromHierarchy() Cause: The query does not have a number select item followed by an XMLType select item only. Action: Make sure the result set of the query used in the newContextFromHierarchy() must have only two selected items: the first item must be number type and the second item must be XMLType. ORA-19036: Invalid query result set in newContextFromHierarchy() Cause: The result set of the query used in the newContextFromHierarchy() does not have the same property as the result set generated by a CONNECT BY query. Action: Make sure the query used in newContextFromHierarchy() is a CONNECT BY query or the query returns the result set have the same property as the result set generated by a CONNECT BY query. ORA-19037: XMLType result can not be a fragment Cause: The select item of the query in newContextFromHierarchy() is an XML fragment. Action: Make sure the select item of the query in newContextFromHierarchy() is NOT an XML fragment ORA-19038: Invalid opertions on query context Cause: SetMaxRows, SetSkipRows, SetRowTagName opertions are applied to a query context created from newContextFromHierarchy(). Action: SetMaxRows, SetSkipRows, SetRowTagName opertions can not be applied to a query context created from newContextFromHierarchy(). ORA-19039: Keyword string reserved for future use Cause: The keyword is reserved for future use as a builtin function. Action: Change the name mentioned above to a different one. ORA-19040: Element string does not match expected string. Cause: The given XML document had a different root element than expected. Action: Insert/Update only the XML documents that conform to that particular schema and element. ORA-19041: Comment data cannot contain two consecutive "-"s Cause: The given comment string expression has two consecutive "-"s. Action: Modify comment string to eliminate one or both of the consevutive "-"s. ORA-19042: Enclosing tag string cannot be xml in any case combination Cause: The given enclosing tag matched "xml" in some case combination Action: Modify the enclosing tag so that it is not xml in any case combination. ORA-19043: Multiply nested XMLROOT function disallowed Cause: An XMLROOT function has an operand that is also an XMLROOT function. Action: Modify the query so that there are no multiply nested XMLROOT functions. ORA-19044: character length specified for XMLSerialize is too small. Cause: An XMLSerialize function was called with a type of character type (e.g. VARCHAR2(27)), and the length specified (27 in the example) was too small. Action: Modify the query so that the character length specified is larger. ORA-19045: character set id specified for XMLSerialize not valid Cause: An XMLSerialize function was called with an invalid value for the caracter set id. Action: Modify the query so that the character set id is valid. ORA-19100: PASSING or RETURNING keyword expected Cause: The keyword PASSING or RETURNING was missing. Action: Specify the PASSING or RETURNING keyword. ORA-19101: CONTENT keyword expected Cause: The keyword CONTENT was missing. Action: Specify the CONTENT keyword. ORA-19102: XQuery string literal expected Cause: The string literal containing the XQuery expression was missing. Action: Specify the XQuery expression as a string literal. ORA-19103: VALUE keyword keyword Cause: The keyword VALUE was missing. Action: Specify the VALUE keyword. ORA-19104: invalid XQueryX: missing attribute string Cause: The XQueryX expression was not assigned the expected attribute. Action: Specify a valid XQueryX. ORA-19105: invalid XQueryX: expected text node - got string Cause: The XQueryX expression did not contain a text node as expected. Action: Specify a valid XQueryX. ORA-19106: invalid XQueryX: expected string - got string Cause: The XQueryX expression did not contain the node as expected. Action: Specify a valid XQueryX. ORA-19107: invalid XQueryX - unsupported construct - string Cause: The given XQuery expression contains an unsupported construct. Action: Specify a valid XQueryX. ORA-19108: WHITESPACE keyword expected Cause: The keyword WHITESPACE was missing. Action: Specify the WHITESPACE keyword. ORA-19109: RETURNING keyword expected Cause: The keyword RETURNING was missing. Action: Specify the RETURNING keyword. ORA-19110: unsupported XQuery expression Cause: The program specified an XQuery expression that is not supported. Action: Rewrite the XQuery with a expression that is supported. ORA-19111: error during evaluation of the XQuery expression Cause: An error occurred during the processing of the XQuery expression. Action: Check the detailed error message for the possible causes. ORA-19112: error raised during evaluation: string Cause: The error function was called during evaluation of the XQuery expression. Action: Check the detailed error message for the possible causes. ORA-19113: trace function called during evaluation: string Cause: The trace function was called during evaluation of the XQuery expression. Action: Check the log file for the trace message. ORA-19114: error during parsing the XQuery expression: string Cause: An error occurred during the parsing of the XQuery expression. Action: Check the detailed error message for the possible causes. ORA-19115: too many context items specified Cause: More than one context item was specified as input to the XMLQuery function. Action: Specify a single context item for the XMLQuery function. ORA-19116: too many xmlspace declarations Cause: The query prolog contained multiple xmlspace declarations. Action: Remove the duplicate xmlspace declarations. ORA-19117: invalid redefinition of predefined namespace prefix "string" Cause: The given predefined namespace was being redefined in a namespace declaration. Action: Remove the namespace declaration that redefines the predefined namespace prefix. ORA-19118: duplicate default namespace definition - string Cause: More than one default namespace declaration used the given namespace URI. Action: Remove the duplicate default namespace definition. ORA-19121: duplicate attribute definition - string Cause: More than one attribute with the same name. Action: Remove the duplicate attribute definition. ORA-19122: unsupported XQuery declaration Cause: The program specified an XQuery declaration that is not supported. Action: Rewrite the XQuery with a declaration that is supported. ORA-19123: fn:zero-or-one() called with a sequence containing more than one item Cause: sequence with more than one item was passed into fn:zero-or-one() function Action: correct input argument to fn:zero-or-one() function ORA-19124: fn:one-or-more() called with a sequence containing no items Cause: sequence containing no items was passed into fn:one-or-more() function Action: correct input argument to fn:one-or-more() function ORA-19125: fn:exactly-one() called with a sequence containing zero or more than one item Cause: sequence containing zero or more than one item was passed into fn:exactly-one() function Action: correct input argument to fn:exactly-one() function ORA-19160: XP0003 - syntax error: invalid variable name string Cause: The given XQuery variable does not begin with the "$" sign Action: Fix the variable name to start with the "$" sign. ORA-19161: XP0004 - XQuery type mismatch: invalid argument type "string" for function "string" Cause: The type of the argument that was passed to the given function was not valid. Action: Fix the argument to be of a type supported by the given function. ORA-19162: XP0004 - XQuery type mismatch: invalid argument types "string", "string" for function "string" Cause: The type of the arguments that were passed to the given function was not valid. Action: Fix the arguments to be of a type appropriate for the given function. ORA-19163: XP0004 - XQuery type mismatch: argument type mismatch: expected - "string" got - "string" for function "string" Cause: The type of the arguments that were passed to the given function was not valid. Action: Fix the arguments to be of a type appropriate for the given function. ORA-19200: Invalid column specification Cause: All input arguments must be valid columns Action: Specify a valid list of columns ORA-19201: Datatype not supported Cause: The particular datatype is not supported in the XMLGEN operator Action: Specify only supported datatypes as arguments to the XMLGEN operator ORA-19202: Error occurred in XML processingstring Cause: An error occurred when processing the XML function Action: Check the given error message and fix the appropriate problem ORA-19203: Error occurred in DBMS_XMLGEN processingstring Cause: An error occurred when processing the DBMS_XMLGEN functions Action: Check the given error message and fix the appropriate problem ORA-19204: Non-scalar value "string" is marked as XML attribute Cause: Only scalar values (i.e. values which are not of object or collection type) can be marked as XML attribute,i.e. is prefixed by "@". In this case, a non-scalar value was prefixed with "@" Action: Remove the "@" sign, or make the value a scalar. ORA-19205: Attribute "string" qualifies a non-scalar value in the select list Cause: The attribute immediately follows a value of object or collection type in the select list or type definition. Action: Remove the "@" sign, or make the previous value a scalar. ORA-19206: Invalid value for query or REF CURSOR parameter Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query, or REF CURSOR. Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR. ORA-19207: scalar parameter string of XMLELEMENT cannot have an alias. Cause: The scalar parameter to XMLELEMENT has been qualified with an alias. Action: Remove the AS clause of the scalar element. ORA-19208: parameter string of function string must be aliased Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression. Action: Specify an alias for the expression using the AS clause. ORA-19209: invalid or unsupported formatting argument Cause: An invalid or unsupported formatting argument was supplied Action: Change the formatting argument to legal supported values ORA-19210: column "string", specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table "string" Cause: The column specified using setKeyColumn()/setUpdateColumn() did not exist in the table. Action: Change the column specified to be a column in the table ORA-19211: column "string", specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type Cause: The column specified using setKeyColumn() was a non-scalar type column. Action: Change the column specified to be a scalar column in the table ORA-19212: no key columns specified before call to DBMS_XMLSTORE.updateXML() Cause: No columns were specified as key columns before the call to DBMS_XMLSTORE.updateXML. Action: Use DBMS_XMLSTORE.setKeyColumn() to specify key columns ORA-19221: XP0001 - XQuery static context component string not initialized Cause: An unitialized static context component was encountered during the static analysis of the expression. Action: initialize the given static context. ORA-19222: XP0002 - XQuery dynamic context component string not initialized Cause: An unitialized dynamic context component was encountered during the evaluation of the expression. Action: Initialize the particular dynamic context component. ORA-19223: XP0003 - syntax error in XQuery expression Cause: The given XQuery expression contains syntax errors. Action: Fix the syntax error in the XQuery expression. ORA-19224: XP0004 - XQuery static type mismatch: expected - string got - string Cause: The expression could not be used because it"s static type is not appropriate for the context in which it was used. Action: Fix the expression to be of the required type or add appropriate cast functions around the expression. ORA-19225: XP0005 - XQuery static type error: expected non empty type got empty sequence Cause: The static type assigned to an expression other than the () expression must not be the empty type. Action: Fix the expression so it does not return empty sequences. ORA-19226: XP0006 - XQuery dynamic type mismatch: expected string got string Cause: The expression could not be used because it"s dynamic type did not match the required type as specified by XQuery sequencetype matching rules. Action: Fix the expression to return the expected type or use appropriate cast functions. ORA-19227: XP0007 - fn:data function is applied to a node (type (string)) whose type annotation denotes a complex type with non-mixed complex content. Cause: The input node for atomization contained a type annotation that denoted a complex type with non-mixed complex content. Action: Fix the input expression to fn:data to be a node that does not contain non-mixed complex content. ORA-19228: XP0008 - undeclared identifier: prefix "string" local-name "string" Cause: The given identifier refers to either a type name, function name, namespace prefix, or variable name that is not defined in the static context. Action: Fix the expression to remove the identifier, or declare the appropriate variable, type, function or namespace. ORA-19229: XP0009 - schema import not supported Cause: A schema import was encountered in the query. Action: remove the schema import. ORA-19230: XP0010 - unsupported axis string Cause: An unsupported axis was encountered in the given expression. Action: Remove the unsupported axis from the expression. ORA-19232: XQ0012 - imported schemas violate validity rules Cause: The imported schemas did not satisfy the conditions for schema validity specified in the XMLSchema specification. Action: Fix the imported schemas to satisfy the validity rules.In particular, the definitions must be valid, complete, and unique -- that is, the pool of definitions must not contain two or more schema components with the same name and target namespace. ORA-19233: XQ0013 - invalid pragma Cause: A pragma was specified whose contents are invalid. Action: Specify the pragma with the correct contents. ORA-19234: XQ0014 - invalid or unsupported must-understand extension Cause: The must-understand extension specified was either invalid or unsupported. Action: remove the unsupported must-understand extension or fix the error. ORA-19235: XQ0015 - unsupported must-understand extension Cause: The XQuery flagger was enabled and the query contained a must-understand extension. Action: remove the unsupported must-understand extension. ORA-19236: XQ0016 - module declaration or import not supported Cause: The given query had a module declaration or module import. Action: Remove the import module or module declaration. ORA-19237: XP0017 - unable to resolve call to function - string:string Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. ORA-19238: XP0018 - focus not defined Cause: The expression relied on the focus (context item, position and size) which was not defined. Action: Define the focus for the expression. ORA-19239: XP0019 - step expression must return sequence of nodes Cause: The step expression returned a sequence containing an atomic value. Action: Fix the path expression to return only nodes. ORA-19240: XP0020 - context item must be node in an axis expression Cause: The context item that was used in the axis epression is not a node. Action: Change the context item to be a node. ORA-19241: XP0021 - cast to type string failed Cause: The value inside a cast expression could not be cast to the required type. Action: Fix the input to the cast expression to be of a castable type. ORA-19242: XQ0022 - namespace declaration attribute must be a literal Cause: The namespace declaration attribute was not a literal string. Action: Fix the namespace declaration to be a literal string. ORA-19243: XQ0023 - invalid document node content in element constructor Cause: The content sequence in an element constructor contained a document node. Action: Change the content of the element constructor so that it does not contain a document node. ORA-19244: XQ0024 - invalid attribute node in element constructor Cause: The content sequence in an element constructor contained an attribute node following a node that was not an attribute node. Action: Change the content sequence of the element constructor so that it does not contain the attribute node. ORA-19245: XQ0025 - duplicate attribute name string Cause: The content sequence of the element constructor contained more than one attribute that had the same name. Action: Remove the duplicate attributes. ORA-19246: XQ0026 - validation failed - element string not found in in-scope element declarations Cause: The validation mode was strict and the element-constructor contained an element name that was not present in the in-scope element declarations. Action: Fix the validation mode to be lax or import the schema definition that contains the required element declaration. ORA-19247: XQ0027 - validation error Cause: An error was encountered during the validation of the expression. Action: Fix the validation error. ORA-19248: XQ0028 - invalid node in document constructor Cause: The content sequence in a document constructor contained either a document or an attribute node. Action: Fix the content so it does not contain any of the above node types. ORA-19249: XP0029 - value does not match facet of the target type Cause: The input value to a cast expression did not satisfy the facets of the target type. Action: Fix the value to conform to the facets of the target type. ORA-19250: XQ0030 - too many values to validate expression Cause: The argument of a validate expression returned more than one element or document node. Action: Fix the argument of the validate expression to return a single element or document node. ORA-19251: XQ0031 - unsupported query version Cause: The query version specified in the prolog was not supported. Action: Supply the version of the query that is supported. ORA-19252: XQ0032 - too many declarations for base URI Cause: The query prolog contained multiple declarations for the base URI. Action: Remove the duplicate definitions for the base URI. ORA-19253: XQ0033 - too many declarations for namespace prefix string Cause: The query prolog contained multiple declarations for the same namespace prefix. Action: Remove the duplicate definitions for the namespace prefix. ORA-19254: XQ0034 - too many declarations for function string Cause: The query module contained more than one function, either declared or imported, which have the same expanded QName. Action: Remove the duplicate function definitions. ORA-19255: XQ0035 - too many declarations of string in imported schemas Cause: Two schemas were imported that defined the same name in the same symbol space and in the same scope. Action: Fix the schema imports to remove the name conflict. ORA-19256: XQ0036 - missing type definitions in imported module Cause: A module was imported, which contains references to type names that are not defined in the in-scope type definitions inside the module. Action: Fix the module definintion to include the in-scope type definition. ORA-19257: XQ0037 - function or variable string in module already defined Cause: A module being imported contained the function or variable that is already declared in the static context of the importing module. Action: Remove the conflicting declarations. ORA-19258: XQ0038 - unsupported or duplicate default collation specified Cause: The query prolog prolog either specified more than one default collation or the collation specified was not supported. Action: Remove the duplicate definition or specify a supported collation. ORA-19259: XQ0039 - duplicate parameter name string in function declaration Cause: The function declaration contained more than one parameter with the same name. Action: Fix the function declaration to remove the duplicate parameters. ORA-19260: XQ0040 - invalid namespace node in element constructor Cause: The content sequence in an element constructor contained a namespace node node following a node that was not a namespace node. Action: Remove the namespace node in the element constructor. ORA-19261: XQ0041 - non empty URI in QName Cause: The name expression in a computed processing instruction or computed namespace constructor returned a QName whose URI part was not empty. Action: Fix the processing instruction or computed namespace constructor to return the QName with an empty URI part. ORA-19262: XQ0042 - namespace constructor not inside an element constructor Cause: The enclosing expression of a computed namespace constructor was not a computed element constructor. Action: Fix the namespace constructor to be inside an element constructor. ORA-19263: XQ0043 - duplicate namespace prefix string Cause: Two or more computed namespace constructors within the same computed element constructor attempted to bind the same namespace prefix. Action: Remove the duplicate namespace definitions. ORA-19264: XQ0044 - invalid namespace in attribute constructors Cause: A computed attribute constructor returned a QName that is in the pre-defined XML namespace (corresponding to namespace prefix xmlns). Action: Change the namespace for the computed attribute constructor. ORA-19265: XQ0045 - invalid or unknown prefix string in function declaration Cause: The declared function name in a function declaration had no namespace prefix or had one of the predefined namespace prefixes other than local. Action: Fix the function declaration to have the correct prefix. ORA-19266: XQ0046 - invalid URI Cause: The given URI contained a lexical form that was not valid according to the definition of xs:anyURI in XML Schema. Action: Fix the URI. ORA-19267: XQ0047 - module string not found Cause: The module with the given target URI could not be found. Action: Fix the prolog to import only available modules. ORA-19268: XQ0048 - namespace string does not match target namespace string Cause: The module contained a function or variable whose namespace did not match the target namespace of the module. Action: Fix the namespace of the function or variable to match the target namespace of the module. ORA-19269: XQ0049 - variable string defined multiple times Cause: The module defined or imported the same variable multiple times. Action: Fix the import or the module definition to remove duplicate definitions. ORA-19270: XP0050 - treat failed - expected string got string Cause: The type of the operand to the treat expression did not match the required type. Action: Fix the input operand to be of the correct type. ORA-19271: XP0051 - invalid atomic type definition Cause: The QName used as an AtomicType in a SequenceType was not defined in the in-scope type definitions as an atomic type. Action: Use the correct atomic type name. ORA-19272: XQ0052 - invalid atomic value in attribute or element constructor Cause: The content of the element or attribute constructor included an atomic value that could not be cast into a string. Action: Fix the content to contain atomic values that can be cast to a string. ORA-19273: XQ0053 - empty string in namespace declaration Cause: An empty string was used in a namespace declaration. Action: Fix the namespace declaration to have a non-empty string. ORA-19274: XQ0054 - variable initialization failed due to circularity Cause: A circular definition was encountered when the variable was initialized. Action: Remove the circularity in the initialization. ORA-19275: XP0055 - schema path string not found in list of in-scope schema definitions Cause: The ElementTest specified a schema path that could not be found in the list of in-scope schema definitions. Action: Include the appropriate schema that can be used to resolve the ElementTest. ORA-19276: XP0005 - XPath step specifies an invalid element/attribute name: (string) Cause: The XPath step specified invalid element or attribute name that did not match any nodes according to the input XML schema or structure. Action: Correct the element or attribute name as the name may be mis-spelled. ORA-19277: XP0005 - XPath step specifies an item type matching no node: (string) Cause: The XPath step specified an item type that did not match any nodes according to the input XML schema or structure. Action: Correct the item type defintion as node of such type does not exit in the input XML schema or structure. ORA-19278: Invalid value: (string) for type: (string) Cause: The value was invalid for the type. Action: Correct the value or change the type. ORA-19279: XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence Cause: The XQuery sequence passed in had more than one item. Action: Correct the XQuery expression to return a single item sequence. ORA-19280: XQuery dynamic type mismatch: expected atomic value - got node Cause: A node was passed in to the expression where an atomic value was expected. Action: Correct the XQuery expression to return an atomic value. ORA-19281: XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration Cause: The query prolog contained multiple inherit-namespaces declarations. Action: Remove the duplicate inherit-namespaces declarations. ORA-19282: XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration Cause: The query prolog contained multiple xmlspace declarations. Action: Remove the duplicate xmlspace declarations. ORA-19283: XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation. Cause: The query contained a version declaration not supported by this implementation. Action: Change the version declaration to 1.0 which is the version supported by this implementation. ORA-19284: Encoding specification in version declaration not supported Cause: The query contained an encoding specification. Action: Remove the encoding specification. ORA-19285: FODC0002 - error retrieving resource Cause: The URI provided could not be resolved to a valid resource. Action: Provide a valid URI for a resource. ORA-19286: XP0017 - unable to resolve call to function - string Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. ORA-19287: XP0017 - invalid number of arguments to function - string:string Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. ORA-19288: XP0017 - invalid number of arguments to function - string Cause: The name and arity of the function call given could not be matched with any in-scope function in the static context. Action: Fix the name of the function or the number of parameters to match the list of in-scope functions. ORA-19300: Error occurred in uri processingstring Cause: An error occurred when processing the URL Action: Check the given error message and fix the appropriate problem ORA-19320: Host name not specified in HTTP URL Cause: A host name was not specified in the HTTP url Action: Specify a host name in the HTTP url when creating the URL string ORA-19321: Could not open HTTP connection to host (string): port (string) Cause: A HTTP connection could not be opened to the host Action: Specify a valid host name and port to connect to ORA-19322: An error occurred while reading from host (string): port (string) Cause: An error occurred while reading from the HTTP host Action: Specify a valid host name and port to read from ORA-19323: Invalid url string Cause: The URL must be a valid URL string Action: Specify a valid url string ORA-19330: Type "string"."string" not installed. Please install the type before using the CREATE_DBURI operator Cause: The type required for the CREATE_DBURI operator has not been installed correctly. Action: Read the installation notes to install the type correctly. ORA-19331: Last argument to CREATE_DBURI operator must be a column Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created. Action: Specify a valid column name in the query. ORA-19332: Invalid column in the CREATE_DBURI operator Cause: The argument to the CREATE_DBURI operator can only be a column. Action: Specify a valid column name for the operator ORA-19333: Invalid flags for the CREATE_DBURI operator Cause: The flags argument given to the DBURI operator is invalid Action: Specify a valid flag value (TEXT) for the DBURI operator ORA-19334: Invalid column specification for CREATE_DBURI operator Cause: All columns must be valid and pointing to the same table or view Action: Specify valid list of columns that are from the same table or view. ORA-19335: Invalid format type object Cause: An invalid format type object was specified for the XML function Action: Specify a valid format type object ORA-19336: Missing XML root element Cause: The XML being generated does not have an enclosing root element. Action: The XML generated must have a root element ORA-19361: ONLINE option not allowed with this type of index Cause: The ONLINE option was specified to validate the structure of a system-generated metadata index Action: The ONLINE option can not be used with system-generated metadata indexes such as an LOB index, an IOT Top index, an Index on Clusters etc., Run query without using the ONLINE option. ORA-19371: invalid update option Cause: The user attempted to call load_sqlset with an update option that is different than REPLACE and ACCUMULATE. Action: Adjust the update option and retry the operation. ORA-19372: invalid update condition Cause: The user attempted to call load_sqlset with an invalid update condition. Action: Check the update condition (e.g., NEW.COL1_NAME >= OLD.COL2_NAME) and retry the operation. ORA-19373: invalid staging table or tablespace Cause: The user attempted to create a staging table and specified an invalid staging table (or one that already exists) or tablespace Action: Check the arguments and try again. ORA-19374: invalid staging table Cause: The user specified an invalid staging table to one of the pack, unpack, or remap stgtab routines, or the user does not have the correct privileges on the staging table Action: Provide a correct staging table or grant the appropriate privileges ORA-19375: no CREATE TABLE privilege on schema "string" Cause: The user tried to create a staging table when he is missing the CREATE TABLE privilege on the specified schema. Action: Grant the privilege to the user and retry ORA-19376: no privileges on tablespace provided or tablespace is offline Cause: The user tried to create a staging table on a tablespace on which he does not have any space allocated, or it is offline Action: Allocate space on the tablespace, bring it online, and retry ORA-19377: no "SQL Tuning Set" with name like "string" exists for owner like "string" Cause: The user specified a filter to a pack/unpack function for the SQL Tuning Set that targets no STS in the SYS schema or the staging table, respectively Action: Provide a different filter after checking the state of the system ORA-19378: invalid mode Cause: The user specified an invalid mode argument to the capture function. Action: Provide a mode argument that was defined in the dbmssqlt file ORA-19379: invalid time_limit or repeat_interval Cause: The user specified a NULL value for either the time_limit or the repeat_interval, or a repeat_interval that is greater than the time_limit Action: Provide a non-null value and make sure time_limit >= repeat_interval ORA-19380: invalid plan filter Cause: The user specified an invalid filter for the plan when calling the select_sqlset table function. Action: Adjust the the filter to be one of the following values and retry the operation: MAX_ELAPSED_TIME, MAX_CPU_TIME, MAX_DISK_READS, MAX_OPTIMIZER_COST, MAX_BUFFER_GETS, FIRST_LOADED LAST_LOADED, FIRST_GENERATED, or LAST_GENERATED. 14 ORA-19400 to ORA-24276 ORA-19400: System type conflict with object SYS.string Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly. Action: Remove the conflicting object and rerun migration. ORA-19500: device block size string is invalid Cause: the device block size returned by sequential I/O OSD is invalid Action: 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. ORA-19501: read error on file "string", blockno string (blocksize=string) Cause: read error on input file Action: check the file ORA-19502: write error on file "string", blockno string (blocksize=string) Cause: write error on output file Action: check the file ORA-19503: cannot obtain information on device, name="string", type="string", parms="string" Cause: call to get device information returned an error Action: check device name, type and parameters ORA-19504: failed to create file "string" Cause: call to create file returned an error Action: check additional messages, check access permissions ORA-19505: failed to identify file "string" Cause: call to identify the file returned an error Action: check additional messages, and check if the file exists ORA-19506: failed to create sequential file, name="string", parms="string" Cause: call to create the sequential file returned an error Action: check additional messages, check access permissions ORA-19507: failed to retrieve sequential file, handle="string", parms="string" Cause: call to retrieve the sequential file returned an error Action: check additional messages, and check if the file exists ORA-19508: failed to delete file "string" Cause: call to delete the file returned an error Action: check additional messages ORA-19509: failed to delete sequential file, handle="string", parms="string" Cause: call to delete the sequential file returned an error Action: check additional messages ORA-19510: failed to set size of string blocks for file "string" (blocksize=string) Cause: call to resize the file returned an error Action: check additional messages ORA-19511: Error received from media manager layer, error text: string Cause: 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. Action: 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. ORA-19512: file search failed Cause: Recovery manager or Oracle Server attempted to discover files that matched the specified pattern but failed. Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed. ORA-19513: failed to identify sequential file Cause: Unable to identify the sequential file. Action: Check additional messages, and check if the file exists on media. ORA-19525: temporary file for the clone database must be renamed Cause: Opening a clone database failed because Oracle server forces the temporary file to be renamed, in order to avoid overwriting the primary temporary file. Action: Rename the tempfiles manually or using the DB_FILE_NAME_CONVERT initialization parameter. ORA-19526: only one location allowed for parameter string Cause: A list of default locations was provided in an Oracle-managed files parameter. Action: Edit the parameter to include a single location. ORA-19527: physical standby redo log must be renamed Cause: The CLEAR LOGFILE command was used at a physical standby database. This command cannot be used at a physical standby database unless the LOG_FILE_NAME_CONVERT initialization parameter is set. This is required to avoid overwriting the primary database"s logfiles. Action: Set the LOG_FILE_NAME_CONVERT initialization parameter. ORA-19550: cannot use backup/restore functions while using dispatcher Cause: Attempted 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. Action: Connect directly to the instance then re-execute the backup or restore function. ORA-19551: device is busy, device type: string, device name: string Cause: 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. Action: Either attempt to allocate another device or wait until the required device is no longer busy. ORA-19552: device type string is invalid Cause: The device type indicated is invalid. Action: Supply a correct device type and retry the allocation. ORA-19553: device name string is invalid Cause: The device name indicated is invalid. Action: Supply a correct device name and retry the allocation. ORA-19554: error allocating device, device type: string, device name: string Cause: The specified device could not be allocated. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. ORA-19555: invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range. Action: 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. ORA-19556: required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred Cause: 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. Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter. ORA-19557: device error, device type: string, device name: string Cause: An error occurred in the platform-specific device code Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. ORA-19558: error de-allocating device Cause: The specified device could not be de-allocated. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. ORA-19559: error sending device command: string Cause: An error occurred while sending the indicated command to the session device. Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation. ORA-19560: %s is not a valid device limit Cause: An invalid type of device limit was specified in a call to x$dbms_backup_restore.setlimit. Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL. ORA-19561: %s requires a DISK channel Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found. Action: Deallocate the current device and allocate a DISK channel, then then retry the command. ORA-19562: file string is empty Cause: The indicated file, which is an archivelog, control file, or datafile was found to be empty during a copy, backup, or scan] operation. Action: Ensure that the correct files are being specified for the copy or backup operation. ORA-19563: %s header validation failed for file string Cause: 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, its header was not recognized as a valid file header for a file of the indicated type (data file, archived log, or control file) belonging to the current database. Action: Ensure that the correct files are being specified for the copy or backup operation. ORA-19564: error occurred writing string bytes at block number string Cause: An error occurred while writing to a file. Action: 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. ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled. Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices. ORA-19566: exceeded limit of string corrupt blocks for file string Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup. Action: None. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt. ORA-19567: cannot shrink file string because it is being backed up or copied Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied. Action: Retry the resize after the backup or copy is complete. ORA-19568: a device is already allocated to this session Cause: A device cannot be allocated to a session if another device is already allocated. Action: Deallocate the current device ORA-19569: no device is allocated to this session Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated. Action: Allocate a device then retry the operation. ORA-19570: file number string is outside valid range of 1 through string Cause: A file number used in a copy, backup, or restore operation is not valid for the current database. Action: Specify a valid file number. ORA-19571: %s recid string stamp string not found in control file Cause: 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. Action: Specify a correct recid/stamp and retry the copy or backup. ORA-19572: cannot process file string, file is being being resized Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized. Action: Wait for the resize to complete then retry the copy or backup. ORA-19573: cannot obtain string enqueue for datafile string Cause: 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. Action: 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. ORA-19574: output filename must be specified Cause: This type of copy or restore requires an output file name. Action: Specify an output filename and retry the copy. ORA-19575: expected string blocks in file string, found string Cause: During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header. Action: 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. ORA-19576: datafile string not defined in control file Cause: The specified file number was not found in the control file. Action: Specify a correct file number and retry the operation. ORA-19577: file string is MISSING Cause: A copyDataFileCopy, restoreDataFileTo or proxyRestoreDataFile function specified a file number but no output file name, indicating that the output filename 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. Action: Either specify an output filename or issue a SQL RENAME command to enter a valid name for this file in the control file. ORA-19578: end of volume while duplexing to sequential files, backup piece incomplete Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently. Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing. ORA-19579: archivelog record for string not found Cause: No archived log record corresponding to input file could be found in the control file. Action: Specify a valid archivelog file name and retry the operation. ORA-19580: %s conversation not active Cause: A backup or restore operation was attempted before a conversation was started. Action: Start a conversation then retry the operation. ORA-19581: no files have been named Cause: 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. Action: Specify some files then retry the operation. ORA-19582: archivelog file header validation for string failed Cause: Archived log file header is corrupt and could not be validated. Action: Provide a valid archivelog file and retry the operation. ORA-19583: conversation terminated due to error Cause: An error occurred which forced the termination of the current backup or restore conversation. Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation. ORA-19584: file string already in use Cause: The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database. Action: Specify a different name and retry the operation. ORA-19585: premature end of volume on piece string Cause: 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. Action: Retry the piece with a larger piece of output media. ORA-19586: %s k-byte limit is too small to hold piece directory Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data. Action: Use the setLimit procedure to increase the k-byte limit and retry the operation. ORA-19587: error occurred reading string bytes at block number string Cause: An error occurred while reading from a file. Action: 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. ORA-19588: %s recid string stamp string is no longer valid Cause: 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. Action: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new recid. ORA-19589: %s is not a snapshot or backup control file Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file. Action: Specify the name of a snapshot or backup control file. ORA-19590: conversation already active Cause: You tried to begin a backup or restore conversation, but another conversation is already active in this session. Action: Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one. ORA-19591: backup aborted because job time exceeded duration time Cause: You tried to backup with duration option and the time provided was not sufficient to complete the backup. Action: Adjust the duration time and re-run the command. Or run the backup command without duration option. ORA-19592: wrong string conversation type Cause: You attempted 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. Action: No action required - the conversation is still active, and more files can be specified. ORA-19593: datafile number string already included as string Cause: 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. Action: No action required - the conversation is still active, and more files can be specified. ORA-19594: control file already included as string Cause: 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. Action: No action required - the conversation is still active, and more files can be specified. ORA-19595: archivelog string already included in backup conversation Cause: The indicated archivelog has already been specified for inclusion in this backup conversation. Action: No action required - the conversation is still active, and more files can be specified. ORA-19596: SPFILE already included Cause: 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. Action: No action required - the conversation is still active, and more files can be specified. ORA-19597: file string blocksize string does not match set blocksize of string Cause: 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. Action: 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. ORA-19598: can not backup SPFILE because the instance was not started with SPFILE Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to startup the instance. Action: Create an SPFILE and re-start the instance using the SPFILE. ORA-19599: block number string is corrupt in string string Cause: A corrupt block was found in a control file, archivelog, or backup piece that is being read for a backup or copy. Corruption shall not be tolerated in control files, archivelogs, or backup pieces. Action: None. 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. ORA-19600: input file is string string (string) Cause: 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. For a datafile, the file number refers to the datafile"s absolute file number as shown in the DBA_DATA_FILES view. For a datafile-copy, the file number refers to the copy"s control file record number as shown in the RECID column of the V$DATAFILE_COPY view. For an archived log, the file number refers to the log"s control file record number as shown in the RECID column of the V$ARCHIVED_LOG view. Action: See other error message. ORA-19601: output file is string string (string) Cause: 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. Action: See other error message. ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode Cause: You tried 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. Action: Take the tablespace offline clean or close the database and retry the copy or backup. ORA-19603: cannot backup or copy active file with KEEP .. UNRECOVERABLE option Cause: The user tried to copy or backup a file that was not closed cleanly, with 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 KEEP .. UNRECOVEARABLE option. Action: Take the tablespace offline cleanly, or close the database and retry the copy or backup. ORA-19604: conversation file naming phase is over Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed. Action: 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. ORA-19605: input filename must be specified Cause: The input file name was not specified for a control file copy operation. Action: Specify an input file name and retry the operation. ORA-19606: Cannot copy or restore to snapshot control file Cause: 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. Action: 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. ORA-19607: %s is an active control file Cause: 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. Action: 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. ORA-19608: %s is not a backup piece Cause: 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. Action: Specify a different file name and retry the operation. ORA-19609: %s is from different backup set: stamp string count string Cause: 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. Action: Specify the correct backup piece and retry the operation. ORA-19610: directory block string is corrupt Cause: The indicated directory block failed checksum validation. This backup piece is unusable. Action: Supply another copy of the same backup piece, or terminate the restore conversation. ORA-19611: backup piece out of order. Expected string but found string Cause: This backup piece is out of sequence. Action: Supply the correct backup piece. ORA-19612: datafile string not restored due to string Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece. Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the restore conversation must be cancelled. ORA-19613: datafile string not found in backup set Cause: 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. Action: 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. ORA-19614: archivelog thread string sequence string not found in backup set Cause: The indicated archived log file was named explicitely for restoration but is not contained in this backup set. Action: 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. ORA-19615: some files not found in backup set Cause: Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each unfound file. Action: See the instructions for message 19613. ORA-19616: output filename must be specified if database not mounted Cause: A datafile restore specified no target filename, but the database is not mounted. The database must be mounted when no target filename is specified, so that the target filename can be obtained from the control file. Action: The restore conversation remains active. If you wish to restore datafiles without their target filenames, then mount the datbase before continuing. Otherwise, a target filename must be specified on all datafile restoration calls. ORA-19617: file string contains different resetlogs data Cause: 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. Action: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set. ORA-19618: cannot name files after restoreValidate has been called Cause: A call was made to specify a file to restore from a backup set, but a previous call to restoreValidate has already been made. Action: You must cancel and restart the conversation if you wish to specify files to restore. ORA-19619: cannot call restoreValidate after files have been named Cause: restoreValidate was called after some files had already been specified for restoration. Action: You must cancel and restart the conversation if you wish to call restoreValidate. ORA-19620: %s is not of string type Cause: 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, its header was not recognized as a valid file header for a file of the indicated type (data file, archived log, or control file) belonging to the current database. Action: The indicated file cannot be processed. Ensure that the correct files are being specified for the copy or backup operation. ORA-19621: archivelog range has already been specified Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation. Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired. ORA-19622: archivelog thread string sequence string not restored due to string Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece. Action: The restore conversation remains active, and the current piece must be re-processed. If the failure cannot be resolved by re-processing the current piece, then the restore conversation must be cancelled. ORA-19623: file string is open Cause: A SwitchToCopy operation specified a datafile copy whose parent datafile is open. Action: Take the owning tablespace offline or close the database, then retry the operation. ORA-19624: operation failed, retry possible Cause: 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. Action: This message is used by recovery manager to decide whether or not to retry the operation. ORA-19625: error identifying file string Cause: 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 OS-specific error accompanies this error to help pinpoint the problem. Action: Specify an different file and retry the operation. ORA-19626: backup set type is string - can not be processed by this conversation Cause: The data in the backup set is not compatible with the current conversation. Action: 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. ORA-19627: cannot read backup pieces during control file application Cause: 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. Action: The conversation is still active and more control files may be applied. ORA-19628: invalid SCN range Cause: The starting SCN for restoreRedoLogRange is greater than the ending SCN. Action: Specify a starting SCN which is less than or equal to the ending SCN. ORA-19629: no files in specified archivelog SCN range Cause: This backup set contains no files in the specified range. Action: 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. ORA-19630: end of volume encountered while copying backup piece Cause: While copying a backup piece from the OS native filesystem to an output device, the output device encountered end-of-volume. Action: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece. ORA-19631: archivelog record contains no file name Cause: This archivelog 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. Action: Specify the recid of an archivelog record that contains a file name. Fixed view v$archived_log can be used to examine the archived logs. ORA-19632: file name not found in control file Cause: The name passed to getFno was not found in the control file. Action: Supply a valid filename. ORA-19633: control file record string is out of sync with recovery catalog Cause: 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. Action: contact Oracle support ORA-19634: filename required for this function Cause: The fname or handle parameter was not specified for deletePiece, deleteDataFileCopy, deleteRedoLog or proxyDelete. Action: Specify the fname or handle parameter when calling these functions. ORA-19635: input and output filenames are identical: string Cause: Identical input and output file names were specified for a datafile copy operation. Action: Specify an output file name which is different from the input file name. ORA-19636: archivelog thread string sequence string already included Cause: The indicated archivelog has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archivelog. Action: No action required - the conversation is still active, and more files can be specified. ORA-19637: backupPieceCreate requires file name when using DISK device Cause: The session device is currently allocated to disk, and so a file name is required. Action: Supply a filename and retry the operation. ORA-19638: file string is not current enough to apply this incremental backup Cause: 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. Action: Supply a backup set that can be applied and retry the operation. ORA-19639: file string is more current than this incremental backup Cause: 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. Action: Supply a backup set that can be applied and retry the operation. ORA-19640: datafile checkpoint is SCN string time string Cause: 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. Action: See other error message. ORA-19641: backup datafile checkpoint is SCN string time string Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied. Action: See other error message. ORA-19642: start SCN of incremental backup is string Cause: This message identifies the starting SCN of an incremental backup that could not be applied. Action: See other error message. ORA-19643: datafile string: incremental-start SCN is too recent Cause: 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. Action: Specify a smaller incremental-start SCN. ORA-19644: datafile string: incremental-start SCN is prior to resetlogs SCN string Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the resetlogs SCN. Action: Specify a larger incremental-start SCN. ORA-19645: datafile string: incremental-start SCN is prior to creation SCN string Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile"s creation SCN. Action: Specify a larger incremental-start SCN. ORA-19646: cannot change size of datafile string from string to string Cause: The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size. Action: Examine the other messages which should be present to indicate the cause of the failure. ORA-19647: non-zero LEVEL cannot be specified when INCREMENTAL is FALSE Cause: BackupSetDataFile was called with a non-zero backup_level and a FALSE incremental indication. Action: Either set incremental to TRUE or change backup_level to zero. ORA-19648: datafile string: incremental-start SCN equals checkpoint SCN Cause: 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. Action: Specify a smaller incremental-start SCN. NOTE that this message will usually only be encountered by the user while taking an incremental backup with Recovery Manager. Recovery Manager should intercept all usual cases of this error and simply ignore the incremental backup for this file. So, if you do encounter this error, please report it to Oracle Support. ORA-19649: offline-range record recid string stamp string not found in file string Cause: 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. Action: Specify the recid/stamp of a record that exists in the control file copy. ORA-19650: Offline-range record recid string stamp string in file string has SCN string Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file. Action: See other error message. ORA-19651: cannot apply offline-range record to datafile string: SCN mismatch Cause: 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. Action: Specify an offline-range record whose offline-clean SCN matches the target datafile"s checkpoint. ORA-19652: cannot apply offline-range record to datafile string: file is fuzzy Cause: The target datafile for an applyOfflineRange call is fuzzy. Action: Specify a target datafile that is closed cleanly. ORA-19653: cannot switch to older file incarnation Cause: SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up. Action: 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. ORA-19654: must use backup control file to switch file incarnations Cause: This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file. Action: Restore and mount a backup control file. ORA-19655: cannot switch to incarnation with different resetlogs data Cause: This switchToCopy operation is attempting to switch to a datafile which comes from a different resetlogs version of the database. Action: 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. ORA-19656: cannot backup, copy, or delete online log string Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs. Action: The indicated log file cannot be processed - select another file. ORA-19657: cannot inspect current datafile string Cause: The file being inspected is already part of the currently mounted database. Action: None - the file is already part of the database. ORA-19658: cannot inspect string - file is from different resetlogs Cause: The resetlogs data in the log file being inspected does not match that in the currently mounted control file. Action: The indicated file cannot be processed - inspect another file. ORA-19659: incremental restore would advance file string past resetlogs Cause: 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. Action: 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. ORA-19660: some files in the backup set could not be verified Cause: 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. Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set. ORA-19661: datafile string could not be verified Cause: Some data blocks for the indicated datafile were corrupt in the backup set. Action: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set. ORA-19662: archived log thread string sequence string could not be verified Cause: Some data blocks for the indicated archived log were corrupt in the backup set. Action: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set. ORA-19663: cannot apply current offline range to datafile string Cause: 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. Action: The datafile remains unchanged. ORA-19664: file type: string, file name: string Cause: This message is issued to identify the file which is the subject of an error. Action: None - this is an informational message. There should be other Oracle messages explaining the cause of the error. ORA-19665: size string in file header does not match actual file size of string Cause: 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. Action: This file is not usable - it has most likely been truncated. ORA-19666: cannot do incremental restore of the control file Cause: The control file was included in an incremental restore conversation Action: If you wish to restore the control file, you must do a full restore of the control file ORA-19667: cannot do incremental restore of datafile string Cause: The backup of the datafile is a full backup Action: If you wish to restore the datafile, you must do a full restore of the datafile ORA-19668: cannot do full restore of datafile string Cause: The backup of the datafile is an incremental backup Action: If you wish to restore the datafile, you must do an incremental restore of the datafile ORA-19669: proxy copy functions cannot be run on DISK channel Cause: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK. Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a 3rd-party media management software product that supports the this backup/restore feature. ORA-19670: file string already being restored Cause: A proxy restore function has already named this file as a restore destination. Action: 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. ORA-19671: media management software returned invalid proxy handle Cause: During a proxy backup or restore, the media management software returned an invalid file handle. Action: 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. ORA-19672: media management software returned invalid file status Cause: During a proxy backup or restore, the media management software returned an invalid file status. Action: 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. ORA-19673: error during proxy copy of file string Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully. Action: There should be other errors on the error stack which explain why the file could not be successfully copied. ORA-19674: file string is already being backed up with proxy copy Cause: 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. Action: Wait until the other recovery manager backup of this file is complete, then retry the backup. ORA-19675: file string was modified during proxy copy Cause: A proxy backup of the specified file failed because the file was brought on-line or otherwise modified while the proxy backup was in progress. This file was off-line 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. Action: Take another backup of this file. ORA-19676: one or more files failed during proxy backup or restore Cause: 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. Action: Examine the messages regarding the specific files to determine the cause of the problems. ORA-19677: RMAN configuration name exceeds maximum length of string Cause: The configuration name string exceeds maximum length. Action: Supply a correct configuration name and retry the function. ORA-19678: RMAN configuration value exceeds maximum length of string Cause: The configuration value string exceeds maximum length. Action: Supply a correct configuration value and retry the operation. ORA-19679: RMAN configuration number string is outside valid range of 1 through string Cause: An invalid RMAN Configuration number was specified. Action: Specify a correct datafile number and retry the operation. ORA-19680: some blocks not recovered. See trace file for details Cause: Some blocks are not recovered during block media recovery. Action: See trace files for details of the problem. ORA-19681: block media recovery on control file not possible Cause: filenumber 0 specified in block media recovery Action: check filenumber ORA-19682: file string not in block media recovery context Cause: Internal error Action: none ORA-19683: real and backup blocksize of file string are unequal Cause: block size changed between backup & real file Action: use right backup ORA-19684: block media recovery failed because database is suspended Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement Action: Execute ALTER SYSTEM RESUME then retry block media recovery ORA-19685: SPFILE could not be verified Cause: Some data blocks for the SPFILE were corrupt in the backup set. Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set. ORA-19686: SPFILE not restored due to string Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece. Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set. ORA-19687: SPFILE not found in backup set Cause: The SPFILE could not be restored, because it is not in this backup set. Action: 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file. ORA-19688: control file autobackup format(string) for string does not have %F Cause: control file autobackup format must contain %F for the device. Action: Change control file format using RMAN command CONGIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE TO . ORA-19689: cannot have more than one %F in control file autobackup format(string) for string Cause: control file autobackup format contains more than one %F for the device. Action: Change control file format using RMAN command CONGIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE TO . ORA-19690: backup piece release string incompatible with Oracle release string Cause: The backup piece was created by incompatible software. Action: Either restart with a compatible software release or create another backup using the current release. ORA-19691: %s is from different database: id=string, name=string Cause: The database name or database id in backuppiece header does not match the one in control file. Action: Supply the correct backuppiece belonging to this database. ORA-19692: missing creation stamp on piece string Cause: The backuppiece doesn"t have information about creation stamp. Action: Supply another backuppiece which is created by oracle 9i or later version. ORA-19693: backup piece string already included Cause: This backup piece was already specified for inclusion in the restore conversation. A restore conversation may process only a single instance of a backup piece. Action: Remove the specified duplicate backup piece in restore steps and restart the conversation. ORA-19694: some changed blocks were not found in the change tracking file Cause: A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file. Action: This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup. ORA-19695: fixed table x$krbmsft has not been populated Cause: This is an internal error. The fixed table x$krbmaft was not populated using the function dbms_backup_restore.searchFiles. Action: Internal error - contact Oracle Customer Support. ORA-19696: control file not found in backup set Cause: The control file could not be restored because it is not in this backup set. Action: 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file. ORA-19697: standby control file not found in backup set Cause: The standby control file could not be restored because it is not in this backup set. Action: 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 in the piece. You must supply the first backup piece of a backup set that contains the requested file. ORA-19698: %s is from different database: id=string, db_name=string Cause: Catalog failed becasuse the database id in file header does not match the one in control file. Action: Supply the correct file belonging to this database. ORA-19699: cannot make copies with compression enabled Cause: Datafile copies with compression are not supported. Action: If the function dbms_backup_restore.backuppieceCreate is called outside RMAN, then the incompatible values are being passed for the parameters docompress and imagcp. If this message occurs during an RMAN job, then this is an internal error in RMAN, and you should contact Oracle support. ORA-19700: device type exceeds maximum length of string Cause: The device type indicated is invalid. Action: Supply a correct device type and retry the allocation. ORA-19701: device name exceeds maximum length of string Cause: The device name indicated is invalid. Action: Supply a correct device name and retry the allocation. ORA-19703: device command string exceeds maximum length of string Cause: The device command string exceeds maximum length. Action: Correct the command and retry the operation. ORA-19704: file name exceeds maximum length of string Cause: 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. Action: Retry the operation with a shorter file name. ORA-19705: tag value exceeds maximum length of string characters Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header. Action: Supply a shorter tag and retry the operation. ORA-19706: invalid SCN Cause: The input SCN is either not a positive integer or too large. Action: Check the input SCN and make sure it is a valid SCN. ORA-19707: invalid record block number - string Cause: The input number is either negative or too large. Action: Check the input record block number and make sure it is a valid number clauses in the create database statement. ORA-19708: log destination exceeds maximum length of string characters Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum. Action: Supply a shorter destination and retry the operation. ORA-19709: numeric parameter must be non-negative integer Cause: A numeric parameter to an x$dbms_backup_restore procedure is negative or contains a fractional portion. Action: Supply a valid numeric parameter. ORA-19710: unsupported character set string Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment. Action: Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable. ORA-19711: cannot use reNormalizeAllFileNames while database is open Cause: An attempt was made to re-normalize all the filenames in the control file while the database is open. Action: Close the database before using the reNormalizeAllFileNames procedure. ORA-19712: table name exceeds maximum length of string Cause: The table name string exceeds maximum length. Action: Retry the operation with a shorter table name. ORA-19713: invalid copy number: string Cause: The copy number is not in a valid range or you have reached maximum limit. Action: Report the error and other information to support. ORA-19714: length for generated name longer than string Cause: The specified format exceeds the maximum length for the piece name. Action: Change the format to create shorter piece names. ORA-19715: invalid format string for generated name Cause: A restricted format or undefined format was used incorrectly. Action: Change the format specified in the additional information by removing the restricted format. ORA-19716: error processing format string to generate name for backup Cause: There were errors while processing the format to generate name for backup. Action: Change the format. ORA-19717: for non-OMF search the pattern must be specified Cause: The procedure dbms_backup_restore.searchFiles was called with an empty pattern while the parameter omf was set to FALSE. Action: Either specify the pattern or set the parameter omf to TRUE. ORA-19718: length for command id longer than string Cause: The specified command id exceeds the maximum length for command id. Action: Supply a shorter command id and retry the operation. ORA-19719: length for operation name longer than string Cause: The specified operation name exceeds the maximum length for operation name. Action: Supply a shorter operation name and retry the operation. ORA-19720: Error occurred when converting an OCI number into an SCN Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file. Action: See other errors on the error stack to look for the source of the problem. ORA-19721: Cannot find datafile with absolute file number string in tablespace string Cause: Can not find one of the datafile that should be in the Pluggable Set. Action: Make sure all datafiles are specified via import command line option or parameter files. ORA-19722: datafile string is an incorrect version Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version. Action: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only. ORA-19723: Cannot recreate plugged in read-only datafile string Cause: The datafile is plugged in read only. It can not recreated. Action: Use ALTER DATABASE RENAME FILE command instead. ORA-19724: snapshot too old: snapshot time is before file string plug-in time Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database. Action: retry the query. ORA-19725: can not acquire plug-in enqueue Cause: There maybe another "ALTER DATABASE RESET COMPATIBILITY" command issued concurrently, preventing this process from acquiring the plug-in enqueue. Action: retry the operation. ORA-19726: cannot plug data [string] at level string into database running at compatibility level string Cause: 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. Action: Raise the "compatible" init.ora parameter and retry the operation. ORA-19727: cannot plug data [string] at level string into database running Oracle string Cause: 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. Action: Upgrade Oracle and retry the operation. ORA-19728: data object number conflict between table string and partition string in table string Cause: The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One can not exchange the table with the partition in this case. Action: Use "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. ORA-19729: File string is not the initial version of the plugged in datafile Cause: The file is not the initial version of the plugged in datafile. Action: Use the correct initial version of the plugged in datafile. ORA-19730: can not convert offline plugged-in datafile string Cause: As part of making a tablespace read-write, we need to convert datafiles that are plugged in read-only. The file must be online. Action: Online the datafile and retry the operation. ORA-19731: cannot apply change to unverified plugged-in datafile string Cause: 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. Action: Use the correct control file and continue recovery. ORA-19732: incorrect number of datafiles for tablespace string Cause: d by a user editing the export file. Action: Use the correct export file and retry the operation. ORA-19733: COMPATIBLE parameter needs to be string or greater Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter. Action: Shutdown and startup with a higher compatibility setting. ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile Cause: 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. Action: Either restore the converted datafile or continue recovering the datafile. ORA-19735: wrong creation SCN - control file expects initial plugged-in datafile Cause: 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. Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file. ORA-19736: can not plug a tablespace into a database using a different national character set Cause: Oracle does not support plugging a tablespace into a database using a different national character set. Action: Use import/export or unload/load to move data instead. ORA-19738: cannot find language information for character set: "string" Cause: The compatibility check failed because a character set name that was provided is not valid. Action: Correct the character set name and retry. ORA-19740: text is longer than string Cause: The specified text exceeds the maximum length for text. Action: Supply a shorter text and retry the operation. ORA-19750: change tracking file: "string" Cause: This message reports the name of a file involved in other messages. Action: See associated error messages for a description of the problem. ORA-19751: could not create the change tracking file Cause: It was not possible to create the change tracking file. Action: Check that there is sufficient disk space and no conflicts in filenames and try to enable block change tracking again. ORA-19752: block change tracking is already enabled Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database. Action: None, this is an informative message only. ORA-19753: error writing to change tracking file Cause: An I/O error occurred while writing to the change tracking file. Action: There will be other messages on the error stack that show details of the problem. ORA-19754: error reading from change tracking file Cause: An I/O error occurred while reading from the change tracking file. Action: There will be other messages on the error stack that show details of the problem. ORA-19755: could not open change tracking file Cause: The change tracking file could not be opened. Action: There will be other messages on the error stack that show details of the problem. ORA-19756: corrupt block number string found in change tracking file Cause: The specified block number is corrupt in the change tracking file. Action: There will be other messages on the error stack that show details of the problem. There will also be a trace file that contains a complete dump of the corrupt block. ORA-19757: could not resize change tracking file to string blocks Cause: An error occurred while trying to change the size of the change tracking file. Action: There will be other messages on the error stack that show details of the problem. ORA-19758: failed to enable/disable block change tracking: out of SGA memory Cause: out of SGA memory Action: Increase SGA and restart the instance. ORA-19759: block change tracking is not enabled Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled. Action: None, this is an informative message only. ORA-19760: error starting change tracking Cause: Change tracking is enabled, but a problem was encountered while enabling the change tracking subsystem in this instance. The alert log and the trace file from the CTWR process will contain more information about the error. Action: Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking. ORA-19761: block size string is not valid for change tracking file Cause: While opening the specified change tracking file, it was found that the file header did not contain a valid logical block size. This probably means that the file is corrupt. Action: If the file can be repaired, do so, otherwise disable and re-enable change tracking to re-initialize the file. ORA-19762: invalid file type string Cause: An invalid file type was found in the change tracking file. Some other file was put in place of the change tracking file, or the file is corrupt. Action: Disable then re-enable change tracking. ORA-19763: compatibility version string is higher than maximum allowed: string Cause: The compatibility version in the change tracking file is greater than what can be used by the current release of Oracle. This can happen when you upgrade, use change tracking with a new release, then downgrade. Action: Disable then re-enable change tracking. ORA-19764: database id string does not match database id string in control file Cause: The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed. Action: Disable then re-enable change tracking. ORA-19765: mount id string does not match mount id string in control file Cause: d by having a change tracking file that cannot be consistently updated by all instances. Action: In RAC, ensure that the name specified for the change tracking file truly represents the same disk location for all nodes in the cluster. Disable then re-enable change tracking. ORA-19766: missing CHANGE keyword Cause: Syntax error. Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING ORA-19767: missing TRACKING keyword Cause: Syntax error. Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING Cause: The USING clause was specified with DISABLE CHANGE TRACKING Action: Correct the statement. ORA-19769: missing FILE keyword Cause: Syntax error. Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING ORA-19770: invalid change tracking file name Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given. Action: Specify the change tracking file name, or omit the USING clause to allow Oracle to create a default name for the change tracking file. ORA-19771: cannot rename change tracking file while database is open Cause: The ALTER DATABASE RENAME FILE command was used to rename the change tracking file, and the database is open by one or more instances. The database must be mounted, and not open, to rename the change tracking file. Action: Close the database and reissue the command. ORA-19772: change tracking file name exceeds limit of string characters Cause: The name specified for the change tracking file is too long. Action: Specify a shorter change tracking file name. ORA-19773: must specify change tracking file name Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set. Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter. ORA-19776: PROXY restore to ASM diskgroup "string" is not supported. Cause: An attempt was made to proxy restore a file to ASM diskgroup using RMAN command. This is not supported. Action: Use a different file name and reissue RMAN command. ORA-19777: ASM file string cannot be proxy backed up. Cause: An attempt was made to proxy backup a ASM file. This is not supported. Action: Use a different file name and reissue RMAN command. ORA-19800: Unable to initialize Oracle Managed Destination Cause: The name given for an Oracle managed files destination cannot be initialized. Action: , if possible, and retry the command or use a different name for destination. ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archivelog file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archivelog file creation was attempted. Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command. ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use. Action: Correct the dependency parameter definitions and retry the command. ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string) Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specfied was not valid. Action: Specify a valid number within the range. ORA-19804: cannot reclaim string bytes disk space from string limit Cause: Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit. Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archivelog deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN. ORA-19805: recid string of string was deleted to reclaim disk space Cause: The file described by the record in control file was deleted in order to reclaim disk space from flash recovery area for other operations. Action: Wait and try again. ORA-19806: cannot make duplex backups in recovery area Cause: Duplex backup to recovery area is not supported. Action: Remove duplex option and try again. ORA-19808: recovery destination parameter mismatch Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters. Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances. ORA-19809: limit exceeded for recovery files Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded. Action: The error is accompanied by 19804. See message 19804 for further details. ORA-19810: Cannot create temporary control file string in DB_RECOVERY_FILE_DEST Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST. Action: Retry the operation with a new file name. ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes Cause: An attempt was made to 1) Create backuppiece or image copy in the recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup piece or image copy in the recovery area. Action: Reissue RMAN command without KEEP options. ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use. Action: Eliminate any incompatible parameter definitions. ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST Cause: An attempt was made to change backuppiece or image copy in recovery area to UNAVAILABLE. Action: Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash. ORA-19815: WARNING: string of string bytes is string%% used, and has string remaining bytes available. Cause: DB_RECOVERY_FILE_DEST is running out of disk space. Action: One of the following: 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 2. Backup files to tertiary device using RMAN. 3. Consider changing RMAN retention policy. 4. Consider changing RMAN archivelog deletion policy. 5. Delete files from recovery area using RMAN. ORA-19816: WARNING: Files may exist in string that are not known to database. Cause: One of the following events caused this: 1. A database crash happened during file creation. 2. A backup control file was restored. 3. The control file was re-created. 4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled. Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility. Do not use messages 19817; it is used for simulating lock failure Do not use messages 19818; it is used for space reclaimation before backup ORA-19830: error from target database: string Cause: This error should be followed by other errors indicating the cause of the problem. Action: No action required. ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required Cause: This version of database was incompatible with the the indicated dbms_backup_restore package installed in the database. Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary. ORA-19851: OS error while managing auxiliary database string Cause: An OS error was received while managing the automatic auxiliary instance. Action: Check the accompanying errors. ORA-19852: error creating services for auxiliary instance string (error string) Cause: An error was received while managing the services of the auxiliary instance. Action: Check the accompanying errors. ORA-19853: error preparing auxiliary instance string (error string) Cause: An error was received while managing the automatic auxiliary instance. Action: Check the accompanying errors. ORA-19854: error obtaining connect string from target Cause: Could not obtain the connect string from the target database Action: Check the accompanying errors. ORA-19860: piece validation cannot be performed more than once Cause: The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation. Action: Do not attempt to validate the pieces more than once. ORA-19861: additional backup pieces cannot be validated in this conversation Cause: The user tried to add new pieces to the list of files being validated after the validation had already been performed. In a validation conversation, the list can only be validated once. Action: Add all the backup pieces to the list before validating, or start a new validation conversation for the remaining pieces. ORA-19862: backup pieces must be validated before accessing results Cause: The user tried to get validation results for backup pieces before the pieces were actually validated. Action: Validate the pieces before trying to access the results. ORA-19863: device block size string is larger than max allowed: string Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup. Action: Change the device BLKSIZE to be smaller than the maximum allowed. ORA-19870: error reading backup piece string Cause: This error should be followed by other errors indicating the cause of the problem. Action: See other errors actions. Do not use message 19871; it is used by RMAN client for testing previous resync time when using backup/standby control file. ORA-19880: Corrupted space header for datafile string, block string backup aborted Cause: When reading the space header block to optimize the backup of the datafile, the space header block was corrupted. Action: Fix corruption before attempting backup again. ORA-19881: Corrupted space bitmap for datafile string, block string backup aborted Cause: When reading a space bitmap block to optimize the backup of the datafile, the space bitmap block was corrupted. Action: Fix corruption before attempting backup again. ORA-19900: RESETLOGS must be specified after recovery to new incarnation Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN"s RESET DATABASE command. Action: Open the database with the RESETLOGS option. ORA-19901: database needs more recovery to create new incarnation Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN"s RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied. Action: Continue recovery. ORA-19902: incarnation key string not found Cause: The specified incarnation was not found in the control file. Action: Resubmit request with known incarnation key. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN"s LIST INCARNATION command. ORA-19903: test recovery not allowed when recovering to new incarnation Cause: Either a new incarnation was set using RMAN"s RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed. Action: Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery. ORA-19904: test recovery not allowed for datafile string Cause: The specified datafile has been restored from a backup that was taken before the last resetlogs. Recovering this datafile will require a file header update that is incompatible with test recovery. Action: Perform actual recovery. ORA-19905: log_archive_format must contain %%s, %%t and %%r Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(resetlogs id) to ensure that all archived log file names are unique. Action: Add the missing format elements to log_archive_format. ORA-19906: recovery target incarnation changed during recovery Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files. Action: If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when resetlogs is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN"s RESET DATABASE TO INCARNATION command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN"s LIST INCARNATION command. ORA-19907: recovery time or SCN does not belong to recovered incarnation Cause: A point-in-time recovery to an SCN or timestamp prior to the last resetlogs was requested. Action: Either change the specified recovery time/scn, or change the recovery destination using RMAN"s RESET DATABASE command. ORA-19908: datafile string has invalid checkpoint Cause: The specified datafile has an invalid checkpoint. Action: Restore the datafile from a backup. ORA-19909: datafile string belongs to an orphan incarnation Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a resetlogs operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information. Action: Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup. ORA-19910: can not change recovery target incarnation in control file Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed. Action: Close the database then re-issue the command. ORA-19911: datafile string contains future changes at the incarnation boundary Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation. Action: Use older backup of the file and then re-issue the command. ORA-19912: cannot recover to target incarnation string Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation. Action: Restore the latest control file from the target incarnation and retry. ORA-19913: unable to decrypt backup Cause: A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open. Action: If password-based restore was enabled for this backup, then supply the correct password using the RMAN SET DECRYPTION command. If transparent restore was enabled for this backup, then ensure that the database external security device is open. ORA-19914: unable to encrypt backup Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open. Action: If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup. ORA-19915: unable to encrypt pre-10.2 files Cause: An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted. Action: Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted. ORA-19916: %s Cause: An error occured when processing user request. Action: Do not use message 19917; it is used internally for testing purpose. ORA-19921: maximum number of string rows exceeded Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded. Action: Close some of existing and unused RMAN connections and sessions. ORA-19922: there is no parent row with id string and level string Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist. Action: This is an internal error. Contact Oracle Support. ORA-19923: the session for row with id string is not active Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died. Action: This is an internal error. Contact Oracle Support. ORA-19924: there are no row with id string Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don"t exist. Action: This is an internal error. Contact Oracle Support. ORA-19926: Database cannot be converted at this time Cause: Another CONVERT DATABASE operation is already in progress. Action: Retry CONVERT DATABASE command later. ORA-19927: CONVERT DATABASE operation cannot proceed Cause: An error occurred earlier during CONVERT DATABASE operation. Action: Retry CONVERT DATABASE command. ORA-19930: file string has invalid checkpoint SCN string Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed. Action: Ensure that the correct files are being specified for the catalog or backup operation. ORA-19931: file string has invalid creation SCN string Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed. Action: Ensure that the correct files are being specified for the catalog or backup operation. ORA-19932: control file is not clone or standby Cause: The operation failed because the control file was not mounted as standby or clone. Action: Mount the database as standby or clone and retry. ORA-19951: cannot modify control file until DBNEWID is completed Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress. Action: Wait until NID completes before attempting the operation. NLS_DO_NOT_TRANSLATE [19960,19960] ORA-19952: database should be mounted exclusively Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively. Action: Shut down the database and start it in exclusive mode. ORA-19953: database should not be open Cause: The database was open. To change the DBID, the database must be mounted exclusively. Action: Shut down the database and mount it in exclusive mode. ORA-19954: control file is not current Cause: The operation failed because a non-current, non-standby control file was mounted. Action: Make the control file current and retry. ORA-19955: only one open thread is allowed to change the DBID Cause: The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down. Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again. ORA-19956: database should have no offline immediate datafiles Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode. Action: Drop the datafiles or recover them and bring them online. ORA-19957: database should have no datafiles in unknown state Cause: The operation failed because the database had one or more datafiles that were in an unknown state. Action: Drop the datafiles or recover them and bring them online. ORA-19958: potential deadlock involving DIAG process Cause: DIAG requested a control file operation that may lead to a deadlock Action: Try last operation later when the control file is released ORA-19960: Internal use only Cause: NID usage Action: None ORA-19999: skip_row procedure was called Cause: The skip_row procedure was called which raises this error Action: Skip_row should only be called within a trigger or a procedure called by a trigger. ORA-20000: %s Cause: The stored procedure "raise_application_error" was called which causes this error to be generated. Action: Correct the problem as described in the error message or contact the application administrator or DBA for more information. ORA-21300: objects option not installed Cause: The objects option is not installed at this site. object types and other object features are, therefore, unavailable. Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle sales representative if the objects option needs to be purchased. ORA-21301: not initialized in object mode Cause: This function requires the OCI process to be initialized in object mode. Action: Specify OCI_OBJECT mode when calling OCIInitialize(). ORA-21500: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string] Cause: 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. Action: Report as a bug - the first argument is the internal error number. ORA-21501: program could not allocate memory Cause: The operating system has run out of memory. Action: Take action to make more memory available to the program. ORA-21503: program terminated by fatal error Cause: A program is in an unrecoverable error state. Action: Report as a bug. ORA-21520: database server driver not installed Cause: 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. Action: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table. ORA-21521: exceeded maximum number of connections in OCI (object mode only) Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode. Action: Close some of existing and unused connections before opening more connections. ORA-21522: attempted to use an invalid connection in OCI (object mode only) Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to dereference a REF obtained from a connection which has been terminated. Action: Ensure that the connection exists and is still valid. ORA-21523: functionality not supported by the server (object mode only) Cause: User attempted to use a functionality that the server does not support. Action: Upgrade the server ORA-21524: object type mismatch Cause: The object type of the object is different from what is specified. Action: Check the type of the object and correct it. ORA-21525: attribute number or (collection element at index) string violated its constraints Cause: Attribute value or collection element value violated its constraint. Action: 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. ORA-21526: initialization failed Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value. Action: Check that all NLS environment variables are well-formed. ORA-21527: internal OMS driver error Cause: A process has encountered an exceptional condition. This is the generic internal error number for Oracle object management services exceptions. Action: Report this as a bug to Oracle Support Services. ORA-21560: argument string is null, invalid, or out of range Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, etc. Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value. ORA-21561: OID generation failed Cause: The handles passed in may not be valid Action: Check the validity of the env, svc handles ORA-21600: path expression too long Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression. Action: User should pass in the correct path expression to locate the attribute. ORA-21601: attribute is not an object Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type. Action: User should avoid performing such operation to an attribute of built-in type. ORA-21602: operation does not support the specified typecode Cause: The user attempts to perform an operation that does not support the specified typecode. Action: User should use the range of valid typecodes that are supported by this operation. ORA-21603: property id [string] is invalid Cause: The specified property id is invalid. Action: User should specify a valid property id. Valid property ids are enumerated by OCIObjectPropId. ORA-21604: property [string] is not a property of transient or value instances Cause: Trying to get a property which applies only to persistent objects. Action: User should check the lifetime and only get this property for persistent objects. ORA-21605: property [string] is not a property of value instances Cause: Trying to get a property which applies only to persistent and transient objects. Action: User should check the lifetime and only get this property for persistent and transient objects. ORA-21606: can not free this object Cause: Trying to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified. Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE ORA-21607: memory cartridge service handle not initialized Cause: Attempt to use the handle without initializing it. Action: Initialize the memory cartridge service handle. ORA-21608: duration is invalid for this function Cause: Attempt to use a duration not valid for this function. Action: Use a valid duration - a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory. ORA-21609: memory being resized without being allocated first Cause: Attempt to resize memory without allocating it first. Action: Allocate the memory first before resizing it. ORA-21610: size [string] is invalid Cause: Attempt to resize memory with invalid size. Action: Pass in a valid size (must be a positive integer). ORA-21611: key length [string] is invalid Cause: Attempt to use an invalid key length. Action: Key length is invalid and valid range is 0 to 64 ORA-21612: key is already being used Cause: Attempt to use a key that is already used. Action: Use a new key that is not yet being used. ORA-21613: key does not exist Cause: Attempt to use a non-existent key Action: Use a key that already exists. ORA-21614: constraint violation for attribute number [string] Cause: Constraints on the attribute were violated Action: Correct the value (of the attribute) so that it satisfies constraints ORA-21615: copy of an OTS (named or simple) instance failed Cause: see following message Action: Check that no attribute value violates constraints. ORA-21700: object does not exist or is marked for delete Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete. Action: User needs to re-initialize the reference to reference an existent object or the user needs to unmark the object. ORA-21701: attempt to flush objects to different servers Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program. Action: User should avoid performing such operation. ORA-21702: object is not instantiated or has been de-instantiated in cache Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object. Action: User should check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired. ORA-21703: cannot flush an object that is not modified Cause: See the error message. Action: The object should not be flushed. ORA-21704: cannot terminate cache or connection without flushing first Cause: See the error message. Action: The transaction should be aborted or committed before terminating the cache or connection. ORA-21705: service context is invalid Cause: The service context that is supplied by the user is not valid. Action: User needs to establish the service context. ORA-21706: duration does not exist or is invalid Cause: The duration number that is supplied by the user is not valid. Action: User needs to establish the duration or use a correct predefined duration. ORA-21707: pin duration is longer than allocation duration Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters. Action: User should use a shorter pin duration or use the null duration. ORA-21708: inappropriate operation on a transient object Cause: User attempted to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking. Action: User should avoid performing such operation on a transient object. ORA-21709: cannot refresh an object that has been modified Cause: User attempted to refresh an object that has been marked for delete, update or insert (new). Action: User should unmark the object before refreshing it. ORA-21710: argument is expecting a valid memory address of an object Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object. Action: User should pass in a valid memory address of an object to the function. ORA-21779: duration not active Cause: User is trying to use a duration that has been terminated. Action: User should avoid performing such operation. ORA-21780: Maximum number of object durations exceeded. Cause: This typically happens if there is infinite recursion in the PL/SQL function that is being executed. Action: User should alter the recursion condition in order to prevent infinite recursion. ORA-22053: overflow error Cause: This operation"s result is above the range of Oracle number. Action: Decrease the input value(s) so that the result is in the range of Oracle number. ORA-22054: underflow error Cause: This operation"s result is below the range of Oracle number. Action: Increase the input value(s) so that the result is in the range of Oracle number. ORA-22055: unknown sign flag value [string] Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED. Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag. ORA-22056: value [string] is divided by zero Cause: Given value is divied by zero. Action: Modify divisor value to be non-zero. ORA-22057: bad integer length [string] Cause: The length of the integer (ie number of bytes) to be converted to or from an Oracle number is invalid. Action: Use integer length 1, 2, 4 or 8 bytes only. ORA-22059: buffer size [string] is too small - [string] is needed Cause: The buffer to hold the resulting text string is too small. Action: Provide a buffer of the required size. ORA-22060: argument [string] is an invalid or uninitialized number Cause: An invalid or uninitialized number is passed in. Action: Use a valid number. To initialize number call OCINumberSetZero(). ORA-22061: invalid format text [string] Cause: The numeric format string for converting characters to or from an Oracle number is invalid. Action: Use valid format string as documented in OCI Programmer"s Guide. ORA-22062: invalid input string [string] Cause: The text string for converting to numbers is invalid. Action: Use a valid input string as documented in OCI Programmer"s Guide. ORA-22063: reading negative value [string] as unsigned Cause: Attempt to convert a negative number to an unsigned integer. Action: Use the sign flag ORLTSB to convert a signed number. ORA-22064: invalid NLS parameter string [string] Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid. Action: Use valid format string as documented in OCI Programmer"s Guide. ORA-22065: number to text translation for the given format causes overflow Cause: Rounding done due to the given string format causes overflow. Action: Change the string format such that overflow does not occur. ORA-22130: buffer size [string] is less than the required size [string] Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small. Action: Provide a buffer of the required size. ORA-22131: hexadecimal string length is zero Cause: The given hexadecimal string length must be greater than zero. Action: Specify a length greater than zero. ORA-22132: hexadecimal string does not correspond to a valid REF Cause: The given hexadecimal string is invalid. Action: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex(). ORA-22140: given size [string] must be in the range of 0 to [string] Cause: The given resize size is invalid. Action: Ensure that the given size is in the required range. ORA-22150: variable-length array has not been initialized Cause: An un-initialized variable-length array is being operated upon. Action: Initialize the variable-length array prior to calling this function. ORA-22151: cannot resize non-zero variable-length array to zero elements Cause: Trying to resize a non-zero variable-length array to 0 elements. Action: Specify a non-zero size. ORA-22152: destination variable-length array is not initialized Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized. Action: Initialize the destination variable-length array prior to calling this function. ORA-22153: source variable-length array is not initialized Cause: The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized. Action: Initialize the destination variable-length array prior to calling this function. ORA-22160: element at index [string] does not exist Cause: Collection element at the given index does not exist. Action: Specify the index of an element which exists. ORA-22161: type code [string] is not valid Cause: Given type code is not valid. Action: Use one of the typecodes enumerated in OCITypeCode. ORA-22162: element at index [string] has been previously deleted Cause: Trying to delete a non-existent collection element. Action: Check for the existence of the element prior to calling this function. ORA-22163: left hand and right hand side collections are not of same type Cause: Left hand and right side collections are not of same type. Action: Ensure that the same collection type is passed for both left hand and right hand side of this function. ORA-22164: delete element operation is not allowed for variable-length array Cause: Trying to delete an element of a variable-length array. Action: Ensure that the collection is not a variable-length array prior to calling this function. ORA-22165: given index [string] must be in the range of [string] to [string] Cause: Given index is not in the required range. Action: Ensure that the given index is in the required range. ORA-22166: collection is empty Cause: Given collection is empty. Action: Test if collection is empty prior to invoking this function. ORA-22167: given trim size [string] must be less than or equal to [string] Cause: Given trim size is greater than the current collection size. Action: Ensure that the given size is less than or equal to the collection size prior to calling this function. ORA-22275: invalid LOB locator specified Cause: There are several causes: (1) the LOB locator was never initialized; (2) the locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only; (5) the locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator; (6) the locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator; Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2),(3), (5) and (6)pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value. ORA-22276: invalid locator for LOB buffering Cause: There are several causes: (1) the locator was never enabled for buffering (2) it is not an updated locator but is being used for a write/flush operation Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation ORA-22277: cannot use two different locators to modify the same LOB Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators. Action: When using LOB buffering, modify the LOB through one LOB locator only. ORA-22278: must update the LOB only through the LOB buffers Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed. Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command. ORA-22279: cannot perform operation with LOB buffering enabled Cause: The operation attempted is not allowed when LOB buffering is enabled. Action: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command. ORA-22280: no more buffers available for operation Cause: There are two causes: (1) All buffers in the buffer pool have been used up by previous operations (2) Attempt to flush a LOB without any previous buffered update operations. Action: For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers. ORA-22281: cannot perform operation with an updated locator Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem. Action: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command. ORA-22282: non-contiguous append to a buffering enabled LOB not allowed Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB. Action: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation. ORA-22283: filename contains characters that refer to parent directory Cause: Filename contains a path "../" which references a parent directory Action: Ensure that the filename does not contain characters which reference a parent directory. ORA-22285: non-existent directory or file for string operation Cause: Attempted to access a directory that does not exist, or attempted to access a file in a directory that does not exist. Action: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct. ORA-22286: insufficient privileges on file or directory to perform string operation Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation. Action: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file. ORA-22287: invalid or modified directory occurred during string operation Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the DBA since the last access. Action: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occured, then close the file and retry the operation with a valid directory alias as modified by your DBA. Oracle recommends that directories should be modified only during quiescent periods. ORA-22288: file or LOB operation string failed string Cause: The operation attempted on the file or LOB failed. Action: See the next error message in the error stack for more detailed information. Also, verify that the file or LOB exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the DBA. ORA-22289: cannot perform string operation on an unopened file or LOB Cause: The file or LOB is not open for the required operation to be performed. Action: Precede the current operation with a successful open operation on the file or LOB. ORA-22290: operation would exceed the maximum number of opened files or LOBs Cause: The number of open files or LOBs has reached the maximum limit. Action: Close some of the opened files or LOBs and retry the operation. ORA-22291: Open LOBs exist at transaction commit time Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time. Action: Close the LOBs before committing the transaction. ORA-22292: Cannot open a LOB in read-write mode without a transaction Cause: An attempt was made to open a LOB in read-write mode before a transaction was started. Action: Start a transaction before opening the LOB in read-write mode. Ways to start a transaction include issuing a SQL DML or SELECT FOR UPDATE command. Opening hte LOB in read-only mode does not require a transaction. ORA-22293: LOB already opened in the same transaction Cause: An attempt was made to open a LOB that already is open in this transaction. Action: Close the LOB before attempting to re-open it. ORA-22294: cannot update a LOB opened in read-only mode Cause: An attempt was made to write to or update a LOB opened in read-only mode. Action: Close the LOB and re-open it in read-write mode before attempting to write to or update the LOB. ORA-22295: cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement Cause: An attempt was made to bind data more than 4000 bytes of data to both LOB and LONG columns in the same insert or update statement. You can bind more than 4000 bytes of data to either a LONG column or one or more LOB columns but not both. Action: Bind more than 4000 bytes of data to either the LONG column or one or more LOB columns but not both. ORA-22296: invalid ALTER TABLE option for conversion of LONG datatype to LOB Cause: An attempt was made to specify ALTER TABLE options which are disallowed during conversion of LONG datatype to LOB. The only ALTER TABLE options allowed during conversion of LONG datatype to LOB are the default clause and LOB storage clause for the column being converted to LOB. Action: Remove the disallowed options. ORA-22297: warning: Open LOBs exist at transaction commit time Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time. Action: This is just a warning. The transaction was commited successfully, but any domain or functional indexes on the open LOBs were not updated. You may want to rebuild those indexes. ORA-22298: length of directory alias name or file name too long Cause: The length of directory alias name or file name given for a BFILE is too long. Action: Use a shorter alias or file name. ORA-22303: type "string"."string" not found Cause: The user is trying to obtain information for a type that cannot be found. Action: Check that the schema is correct and that the type has been created correctly. ORA-22304: input type is not an object type Cause: The user is trying to obtain the supertype information for a non-object type. Action: Pass in only an object type. ORA-22305: attribute/method/parameter "string" not found Cause: Type element with the given name is not found in the type. Action: Check to make sure that the type element exists. ORA-22306: type "string"."string" already exists Cause: The user is trying to create a type that already exists. Action: Check to make sure that the type has not been created prior to this. ORA-22307: operation must be on a user-defined type Cause: attempt to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type. Action: Check to make sure that only user-defined types are being operated on. ORA-22308: operation not allowed on evolved type Cause: An attempt was made to replace a type whose attribute definition been been altered. Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE REPLACE. ORA-22309: attribute with name "string" already exists Cause: The user is attempting to create an object type where more than one attributes have the same name. Action: Check to make sure that all attribute names are unique. ORA-22310: ALTER TYPE error. Refer to table "string"."string" for errors Cause: An invalid alter type statement was submitted. Action: Correct the errors listed in specified table and resubmit statement. ORA-22311: type for attribute "string" does not exist Cause: The type of the attribute does not exist. Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute"s type in the DDL transaction. ORA-22312: must specify either CASCADE or INVALIDATE option Cause: An attempt was made to alter a type which has a dependent type or table without specifying the CASCADE or INVALIDATE option. Action: Resubmit the statement with either the CASCADE or INVALIDATE option. Specify CASCADE if you want to cascade the type change to dependent types and tables; otherwise, specify INVALIDATE to invalidate all dependents. ORA-22313: cannot use two versions of the same type "string" Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type. Action: Check that the libraries being linked with this application and use the same versions of the type. ORA-22314: method information mismatch in ALTER TYPE Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported. Action: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods. ORA-22315: type "string" does not contain a map or order function Cause: The input type does not contain a map or order function so one cannot be returned. Action: Add a map or order function to the type or catch this error. ORA-22316: input type is not a collection type Cause: The user is trying to obtain information for collection types on a non-named collection type. Action: Use a named collection type for the function. ORA-22317: typecode number is not legal as a number type Cause: The user is trying to use a number typecode that is not valid. Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL. ORA-22318: input type is not an array type Cause: The user is trying to obtain the number of elements for a non-array type. Action: Pass in only a named collection type which is an array. ORA-22319: type attribute information altered in ALTER TYPE Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added. Action: Check that all type alterations are legal. ORA-22320: missing user version string Cause: The VERSION option is specified without a user version string. Action: Resubmit the statement with the version string following the VERSION keyword. ORA-22321: method does not return any result Cause: OCITypeResult() was called on a method that does not return any results. Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly. ORA-22322: error table "string"."string" has incorrect structure Cause: The specified error table does not have the expected table structure. Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure to create an error table, then resubmit the statement using the new error table. ORA-22323: error table "string"."string" does not exist Cause: The error table does not exist. Action: Resubmit the statement with a correct error table name. ORA-22324: altered type has compilation errors Cause: The use of the ALTER TYPE statement caused a compilation error. Action: Correct the error reported and resubmit the statement. ORA-22326: cannot change a type to FINAL if it has subtypes Cause: An attempt was made to change a type with subtypes to FINAL. Action: Drop all subtypes of the target type before changing it to FINAL. ORA-22327: cannot change a type to NOT INSTANTIABLE if it has dependent tables Cause: An attempt was made to change a type with dependent tables to NOT INSTANTIABLE. Action: Drop all dependent tables of the target type and resubmit the statement. ORA-22328: object "string"."string" has errors. string Cause: Altering the target type causes errors in its dependent object. Action: Correct the problem in the dependent object and resubmit the statement. ORA-22329: cannot alter a non-object type Cause: An attempt was made to execute ALTER TYPE on a non-object type. Action: Drop the non-object type first, then re-create it as an object type. ORA-22330: cannot alter a type that is not valid Cause: An attempt was made to perform ALTER TYPE on an invalid type. Action: Use the CREATE OR REPLACE TYPE command to modify the type. ORA-22331: cannot alter an incomplete type Cause: An attempt was made to perform ALTER TYPE on an incomplete type. Action: Use CREATE TYPE to completely define the original type before executing the ALTER TYPE. ORA-22332: a dependent object in schema "string" has errors. string Cause: Altering the target type causes errors in its dependent object. Action: Correct the problem in the dependent object and resubmit the statement. ORA-22333: cannot reset type "string"."string" due to invalid dependent types and tables Cause: An attempt was made to reset the type version with invalid dependent types and tables. Action: Use the ALTER TYPE COMPILE statement to compile all invalid dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA to upgrade all the dependent tables then resubmit the statement. ORA-22334: cannot reset type "string"."string". Dependent tables must be upgraded to latest version Cause: An attempt was made to reset the type version when the data in the dependent table has not been upgraded to the latest type version. Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement. ORA-22335: The client cannot work with an altered type Cause: A pre 8.2 client has requested a type that has been altered on the server. Action: Only 8.2 or higher clients could access altered types ORA-22336: table contained 8.0 image format, must specify INCLUDING DATA Cause: One of the following: 1) An attempt was made to alter a type with a dependent table in 8.0 image format and the NOT INCLUDING TABLE DATA option was specified. 2) An attempt was made to upgrade a table in 8.0 image format with the NOT INCLUDING DATA option specified. Action: Resubmit the statement with INCLUDING DATA option. ORA-22337: the type of accessed object has been evolved Cause: The type of the accessed object has been altered and the client"s object is based on an earlier type definition. Action: The user needs to exit application and modify application to accommodate the type change. From SQL/PLUS, reconnect and resubmit statement. ORA-22338: must specify CASCADE INCLUDING DATA when altering the final property Cause: An attempt was made to alter the final property of a type with dependent table(s) without specifying the CASCADE INCLUDING DATA . option. Action: Resubmit the statement with the CASCADE INCLUDING DATA option. ORA-22339: cannot alter to not final since its attribute column is substitutable Cause: An attempt was made to alter a type to not final when its embedded attribute is defined as substitutable in some tables. Note, this is a restriction in 9.0 version because when a type is altered to not final, column of that type is set to not substitutable at all levels; thus, it is an error if one of its embedded attribute column is already marked substitutable. Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS for all columns of non final type. Then resubmit the ALTER TYPE statement. ORA-22340: cannot string type "string"."string". Dependent tables must be upgraded to latest version Cause: An attempt was made to reset the version, drop or alter a type when the data in dependent table has not been upgraded to the latest version. Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement. ORA-22341: cannot assign supertype instance to subtype Cause: An attempt was made to assign or copy a supertype instance to a container (destination) that can only hold a subtype instance. Action: Make sure the runtime type of the source of the assignment or copy is the same type as the destination or is a subtype of the destination type ORA-22342: dependent VARRAY column exceeds the maximum inline column size Cause: An attempt was made to alter a type (add or modify attribute) which causes the size of its dependent VARRAY column to exceed the maximum inline column size. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created. Action: Specify the VARRAY column to be stored as LOB at the table level when the table is created. ORA-22343: Compilation error for type invalidated by ALTER TYPE Cause: Compilation failed for a type which was invalidated by ALTER TYPE. We throw this error and rollback the compilation effort so that the user may be able to fix whatever is causing the compilation error and try again. It is important that we do not chnage status here and modify the dependency information as this will affect the creation of versions. Action: Check what is causing teh compilation error and correct it and try again. ORA-22344: can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change. Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT FINAL change. ORA-22345: recompile type string.string before attempting this operation Cause: An attempt was made to perform an operation which requires the specified datatype to be valid, but the datatype is invalid Action: Recompile the specified type and retry the operation ORA-22346: Type has cyclical dependency. Should use CASCADE option Cause: An attempt was made to alter a type which has a cyclical dependency, with invalidate option. Action: Give CASCADE option instead of INVALIDATE ORA-22347: No changes to type specified for ALTER TYPE Cause: The ALTER TYPE does not contain any changes to the type. Action: If any change is required for the type, modify the ALTER TYPE to specify the change. Else no need for the ALTER. ORA-22369: invalid parameter encountered in method string Cause: An invalid parameter is being passed to this method of SYS.AnyType ,SYS.AnyData or SYS.AnyDataSet Action: Check the parameters being passed to this method and make sure that the parameters are allowed. ORA-22370: incorrect usage of method string Cause: This method of SYS.AnyType or SYS.AnyData or SYS.AnyDataSet is being used inappropriately. Action: Check the documentation for correct usage. ORA-22371: Table contains data of type string.string, version string, which does not exist Cause: Some of the older versions of the type may have got deleted because one or more of the types it were referencing was dropped. Action: These data could not be read as the whole ADT. Read the data at individual scalar attribute level. ORA-22600: encountered 8.0.2 (Beta) VARRAY data that cannot be processed Cause: Production Oracle8 (8.0.3 and beyond) encounters some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data. Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then re-insert the VARRAY data. There is no provided script or tool to help automate this conversion. ORA-22601: pickler TDS context [string] is not initialized Cause: Attempt to use the pickler TDS context without initializing it. Action: Use OCIPicklerTdsCtxInit to initialize the context. ORA-22602: pickler TDS handle [string] is not well-formed Cause: Attempt to use the pickler TDS handle without initializing/ constructing it. Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed. ORA-22603: cannot add an attribute to the already generated TDS handle Cause: Attempt to add an attribute to the already constructed TDS. Action: Use a TDS handle that is initialized but not yet constructed. ORA-22604: TDS handle already generated Cause: Attempt to geneate TDS that is already genearated. Action: Use a TDS handle that is initialized but not yet generated. ORA-22605: FDO handle [string] is not initialized Cause: Attempt to use an uninitialized FDO handle. Action: Use OCIPicklerFdoInit to initialize FDO handle". ORA-22606: pickler image handle [string] is not well-formed Cause: Attempt to use the image handle without initializing/ constructing it. Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed. ORA-22607: image handle already generated Cause: Attempt to geneate image that is already genearated. Action: Use a image handle that is initialized but not yet generated. ORA-22608: cannot add an attribute to the already generated image handle Cause: Attempt to add an attribute to the already constructed image. Action: Use a image handle that is initialized but not yet constructed. ORA-22609: error string during initialization of FDO Cause: Error during FDO initialization. Action: Take an action based on the specified error. ORA-22610: error while adding a scalar to the image handle Cause: Error while adding a scalar attribute to the image handle Action: Make sure image handle is initialized before adding scalar ORA-22611: TDS version is not recognized Cause: Incorrect TDS handle is passed Action: Make sure image handle is initialized with the correct TDS ORA-22612: TDS does not describe a collection TDS Cause: collection construct/access routines are being on an image but the TDS does not describe that a collection TDS Action: Make sure a collection TDS is used before invoking collection routines on the image handle ORA-22613: buflen does not match the size of the scalar Cause: buflen is incorrect Action: Make sure buflen is correct and matches the size of the scalar ORA-22614: error while construction the collection in the image Cause: Error during the construction of collection Action: Make sure image handle is initialized and OCIPicklerImageCollBegin is called to begin collection ORA-22615: attribute is not a collection Cause: collection routine is invoked upon a non-collection attribute Action: Make sure attribute is a collection ORA-22616: image is not of Oracle 8.1 format Cause: The function being invoked is applicable only for 8.1 images Action: Make sure image is of 8.1 format ORA-22617: error while accessing the image handle collection Cause: Error while accessing collection in the image handle Action: Make sure image is initialized correctly and the collection is constructed properly. ORA-22618: attribute is a BAD NULL in the image handle Cause: attribute in question is probably the attribute of a null embedded image Action: Make sure attribute number is valid or it is NULL or NOT NULL. ORA-22619: all collection elements have already been accessed Cause: Accessing a collection element after all the collection elements are already accessed Action: This function should not be invoked any more. ORA-22620: buffer size too small to hold the value Cause: Buffer size is not enough to hold the value. Most likely while doing the character set conversion, a bigger buffer is needed. Action: Pass in a bigger buffer. If the client character set format differs from that of server, doing the conversion may result in 4X expansion. ORA-22621: error transfering an object from the agent Cause: Any error returned from pickler routines on the agent side. Action: Contact Oracle Support. ORA-22625: OCIAnyData is not well-formed Cause: Attempt to use the OCIAnyData without initializing constructing it. Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is adding attributes. Use OCIAnyDataEndConstruct to complete the construction. Or use OCIAnyDataConvert to do the construction. MAke sure it is properly constructed before accessing attributes. ORA-22626: Type Mismatch while constructing or accessing OCIAnyData Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute. Action: Make sure the type supplied matches the type of object to to be constucted or accessed. ORA-22627: tc [string] must be that of object/varray/nested table Cause: Type code is not that of object/varray/nested table Action: Make sure the type code is OCI_TYPECODE_OBJECT or OCI_TYPECODE_VARRAY or OCI_TYPECODE_TABLE ORA-22628: OCIAnyData already constructed Cause: Attempt to add attributes to OCIAnyData that is already constructed. Action: Use the OCIAnyData that is initialized but not yet constructed. ORA-22629: OCIAnyData is null Cause: Attempting an operation that is not valid on null OCIAnyData Action: Make sure OCIAnyData is not null. ORA-22630: attribute [string] is null or it is not well-formed Cause: Passing an attribute that is null or not well-formed Action: Make sure the attribute is not null or is well-formed. ORA-22631: attribute [string] is is not well-formed or does not match the type Cause: Passing an attribute that is not well-formed or does not match the input type. Action: Make sure the attribute is well-formed and matches the type specified. ORA-22632: AnyDataSet parameter is not valid for the current operation Cause: The AnyDataSet parameter is null or it is somehow invalid for the current operation. Action: Check the documentation for the current operation. ORA-22633: Error freeing AnyDataSet Cause: AnyDataSet that is passed in may not be valid. Action: Check all the AnyDataSet parameters. ORA-22634: Error adding new instance to AnyDataSet Cause: Current instance in the AnyDataSet has not been fully constructed. Action: Make sure that the current instance is fully constructed before adding new instance. ORA-22800: invalid user-defined type Cause: An attempt was made to use an incomplete type as a constructor. Action: Complete the type definition before using it in a query. ORA-22801: invalid object row variable Cause: The specified object row variable is not available in the scope of name resolution. Action: Verify the specified object row variable is correct, or use an object row variable visible in scope. ORA-22803: object type contains zero attributes Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context. Action: specify a valid object type ORA-22804: remote operations not permitted on object tables or user-defined type columns Cause: An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY. Action: none ORA-22805: cannot insert NULL object into object tables or nested tables Cause: An attempt was made to insert a NULL object into an object table or a Nested Table. Action: Ensure that a non-NULL object is inserted into the table or insert an object with attributes whose values are NULL. ORA-22806: not an object or REF Cause: An attempt was made to extract an attribute from an item that is neither an object nor a REF. Action: Use an object type or REF type item and retry the operation. ORA-22807: cannot resolve to a scalar type or a collection type Cause: Invalid use of a non-scalar (for example, object type) item. Action: Change the item"s data type and retry the operation. ORA-22808: REF dereferencing not allowed Cause: An attempt was made to access an object type"s attributes by dereferencing a REF item. Action: Make the item an object type instead of a REF to an object type. ORA-22809: nonexistent attribute Cause: An attempt was made to access a non-existent attribute of an object type. Action: Check the attribute reference to see if it is valid. Then retry the operation. ORA-22810: cannot modify object attributes with REF dereferencing Cause: An attempt was made to modify the attributes an object by dereferencing a REF column in an UPDATE statement. Action: Update the table containing the object that the REF points to, or change the REF column to an object type column. ORA-22812: cannot reference nested table column"s storage table Cause: An attempt to access the nested table column"s storage table is not allowed in the given context. Action: Issue the statement against the parent table containing the nested table column. ORA-22813: operand value exceeds system limits Cause: Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size might be too big for available memory. Action: Choose another value and retry the operation. ORA-22814: attribute or element value is larger than specified in type Cause: Value provided for the object type attribute or collection element exceeded the size specified in the type declaration. Action: Choose another value and retry the operation. ORA-22816: unsupported feature with RETURNING clause Cause: RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and INSTEAD OF Triggers. Action: Use separate select statement to get the values. ORA-22817: subquery not allowed in the default clause Cause: An attempt was made to use a subquery in the column default clause expression. Action: Remove the subquery from the default clause. ORA-22818: subquery expressions not allowed here Cause: An attempt was made to use a subquery expression where these are not supported. Action: Rewrite the statement without the subquery expression. ORA-22819: scope of input value does not correspond to the scope of the target Cause: An attempt to operate on a REF value scoped to a different table than the expected one Action: Use a ref which is scoped to the expected table and retry the operation ORA-22826: cannot construct an instance of a non instantiable type Cause: An attempt was made to use a non instantiable type as a constructor. Action: None. ORA-22828: input pattern or replacement parameters exceed 32K size limit Cause: Value provided for the pattern or replacement string in the form of VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit. Action: Use a shorter pattern or process a long pattern string in multiple passes. ORA-22833: Must cast a transient type to a persistent type Cause: An attempt was made to use the transient type in the query result. Action: Cast the transient type to a structurally equivalent persistent type. ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string) Cause: An attempt was made to convert CLOB to CHAR or BLOB to RAW, where the LOB size was bigger than the buffer limit for CHAR and RAW types. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes. Action: Do one of the following: 1. Make the LOB smaller before performing the conversion, for example, by using SUBSTR on CLOB 2. Use DBMS_LOB.SUBSTR to convert CLOB to CHAR or BLOB to RAW. ORA-22850: duplicate LOB storage option specificed Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once. Action: Specify all LOB storage options only once. ORA-22851: invalid CHUNK LOB storage option value Cause: The specified CHUNK LOB storage option value must be an integer. Action: Choose an appropriate integer value and retry the operation. ORA-22852: invalid PCTVERSION LOB storage option value Cause: The specified PCTVERSION LOB storage option value must be an integer. Action: Choose an appropriate integer value and retry the operation. ORA-22853: invalid LOB storage option specification Cause: A LOB storage option was not specified Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX as part of the LOB storage clause. ORA-22854: invalid option for LOB storage index Cause: A valid LOB store index option was not specified. Action: Specify one of (INITRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index. ORA-22855: optional name for LOB storage segment incorrectly specified Cause: The optional name for LOB storage segment was specified with multiple columns in the column list. Action: Specify each column LOB storage only with optional name(s). ORA-22856: cannot add columns to object tables Cause: An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type. Action: Create a new type with additional attributes, and use the new type to create an object table. The new object table will have the desired columns. ORA-22857: cannot modify columns of object tables Cause: An attempt was made to alter the object table by modifing existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type. Action: Create a new type with the desired attribute types and use it to create an object table. The new object table will have the desired columns. ORA-22858: invalid alteration of datatype Cause: An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type. Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor. ORA-22859: invalid modification of columns Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type. Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor. ORA-22860: object type expected Cause: An attempt was made to create an object table using a non- object type, or to create a column that is a REF to a non-object type. Action: Use a valid object type in the table or column definition. ORA-22861: invalid user-defined type Cause: An attempt was made to create a column or object table of a non- existent type. Action: Specify a valid type in the table or column definition. ORA-22862: specified object identifier doesn"t match existing object identifier Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name. Action: Specify the correct object identifier or leave it out of the statement. ORA-22863: synonym for datatype string.string not allowed Cause: A synonym specification for a datatype is not supported Action: do not use the synonym for the datatype ORA-22864: cannot ALTER or DROP LOB indexes Cause: An attempt was made to ALTER or DROP a LOB index. Action: Do not operate directly on the system-defined LOB index. Perform operations on the corresponding LOB column. ORA-22865: more than one column specified Cause: An attempt was made to specify multiple columns where only one is allowed. Action: Specify a single column and retry the operation. ORA-22866: default character set is of varying width Cause: A character LOB was defined but the default character set is not fixed width. Action: Ensure that the character set is of fixed width before defining character LOBs. ORA-22868: table with LOBs contains segments in different tablespaces Cause: An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment. Action: Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace. ORA-22869: depth of type dependency hierarchy exceeds maximum limit Cause: The type dependency hierarchy was structured to have depth greater than 1024. Action: Re-structure the type dependency hierarchy to a shorter depth. ORA-22870: ALTER TYPE with REPLACE option a non-object type Cause: attempt to perform ALTER TYPE with REPLACE option a non-object type Action: drop the non-object type first, then re-create it as an object type ORA-22871: ALTER TYPE with REPLACE is not allowed for pure incomplete types Cause: An attempt to perform ALTER TYPE with REPLACE option for a pure incomplete type Action: Completely define the original type, before using the ALTER TYPE with REPLACE option. ORA-22872: OID INDEX clause not allowed on tables with primary key based object identifiers Cause: An attempt to create an OID INDEX on a table with primary key based object identifiers. Action: Remove the OID INDEX clause ORA-22873: primary key not specified for primary key based object table Cause: An attempt to create a primary key based object table without specifying a primary key Action: Specify a primary key and retry the operation ORA-22874: attribute "string" is not part of the type "string" Cause: Attribute specified in the user_defined clause is not an attribute of the REF type Action: Ensure that the name specified in the user_defined clause is the name of a valid attribute of the REF type ORA-22875: cannot drop primary key of an object table whose object identifier is primary key based Cause: An attempt to drop the primary key of an object table which has a primary key based object identifier Action: Remove the drop primary key clause ORA-22876: this user-defined type is not allowed or it cannot be used in this context Cause: An attempt to create a kind of user-defined type which is not allowed, or an attempt to create table columns or use default constructor with a type on which these are not supported. Action: Ensure that the type is permitted in this context. ORA-22877: invalid option specified for a HASH partition or subpartition of a LOB column Cause: One or more invalid options were encountered while parsing the physical attributes of a LOB partition or subpartition. Either the LOB partition is in a table partitioned using the HASH method, or the LOB subpartition is in a table subpartitioned using the HASH method. TABLESPACE is the only valid option for a HASH partition or subpartition. Action: Remove the invalid option(s). ORA-22878: duplicate LOB partition or subpartition specified Cause: An attempt was made to specify a partition or subpartition that has already been specified for the LOB column. Action: Remove the duplicate specification. ORA-22879: cannot use the LOB INDEX clause for partitioned tables Cause: An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table. Action: Remove the LOB INDEX clause. ORA-22880: invalid REF Cause: An invalid REF was accessed. Action: Modify the REF and retry the operation. ORA-22881: dangling REF Cause: The object corresponding to the REF that was accessed does not exist. Action: Ensure that the REF value is pointing to an existing object. ORA-22882: object creation failed Cause: The object cannot be created in the database. Action: Check to see if the object table exists and the object size is not too big. Then retry the operation. ORA-22883: object deletion failed Cause: The object could not be deleted from the database. Action: Check to see if the object table exists.Then retry the operation. ORA-22884: object modification failed Cause: The object could not be modified in the database. Action: Check to see if the object table exists and the object size is not too big. Then retry the operation. ORA-22885: cannot get REF to a non-persistent object Cause: An attempt was made to get a REF for something other than an object in an object table. REFs can only be taken for objects in object tables. Action: Rewrite the query to obtain REF values from object tables. ORA-22886: scoped table "string" in schema "string" is not an object table Cause: The scoped table specified for a REF column is not an object table. Action: Ensure that the scoped table is an object table.Then retry the operation. ORA-22887: type of REF column is not the same as that of its scoped table Cause: The type specified for the REF column and the type specified for the scope table are different. Action: Ensure that the types of a REF column and its scoped table are the same. ORA-22888: duplicate SCOPE clauses for a REF column Cause: Multiple SCOPE clauses were specified for a single REF column. Action: Remove the duplicate SCOPE clauses and retry the operation. ORA-22889: REF value does not point to scoped table Cause: An attempt was made to insert a REF value that does not point to the scoped table. Action: Ensure that the REF values point to the scoped table. ORA-22890: cannot specify name for REF column constraint Cause: An attempt was made to specify a constraint name for a constraint on a REF column. Action: Remove the constraint name and retry the operation. ORA-22891: cannot have multiple columns in REF constraint Cause: An attempt was made to specify multiple columns in a single REF constraint. Action: Specify separate constraints for each column and retry the operation. ORA-22892: scoped table "string" does not exist in schema "string" Cause: The scoped table specified for a REF column does not exist. Action: Ensure that the scoped table exists and retry the operation. ORA-22893: constraint can be specified only for REF columns Cause: The constraint specified does not apply to non-REF columns. Action: Remove the constraint and retry the operation. ORA-22894: cannot add constraint on existing unscoped REF columns of non-empty tables Cause: An attempt was made to add a constraint to existing unscoped REF columns of a table which contains one or more rows. Action: Remove the constraint specification or add the constraint after emptying the table. ORA-22895: referenced table "string" in schema "string" is not an object table Cause: The referenced table specified for a REF column is not an object table. Action: Ensure that the referenced table is an object table.Then retry the operation. ORA-22896: cannot have both scope and referential constraint on REF column "string" Cause: REF column has both a referential and a scope constraint. A referential constraint implies a scope constraint. Action: Remove either the referential or scope constraint and then retry the operation. ORA-22897: no scope clause specified for user-defined REF column "string" Cause: User-defined REF column does not have a scope constraint. Action: Specify a scope constraint for the user-defined REF column and retry the operation. ORA-22898: existing scope clause on "string" points to a table other than the one mentioned in the referential constraint Cause: Table mentioned in the referential integrity constraint is different from the scope table of the REF column. Action: Specify the scope table of the REF column in the referential integrity constraint and then retry the operation. ORA-22899: cannot specify both scope and rowid constraint on ref column Cause: An attempt was made to specify both a scope and a rowid constraint on a REF column. Action: Remove either the rowid or scope constraint and then retry the operation. ORA-22900: the SELECT list item of THE subquery is not a collection type Cause: The THE subquery must SELECT a nested table or VARRAY item. Action: change the subquery to SELECT a nested table or VARRAY item. ORA-22901: cannot compare nested table or VARRAY or LOB attributes of an object type Cause: Comparison of nested table or VARRAY or LOB attributes of an object type was attempted in the absence of a MAP or ORDER method. Action: define a MAP or ORDER method for the object type. ORA-22902: CURSOR expression not allowed Cause: CURSOR on a subquery is allowed only in the top-level SELECT list of a query. Action: none ORA-22903: MULTISET expression not allowed Cause: MULTISET expressions are allowed only inside a CAST to a nested table or VARRAY type. Action: put the MULTISET(subquery) expression inside a CAST to a nested table or VARRAY type. ORA-22904: invalid reference to a nested table column Cause: invalid use of a nested table column Action: remove invalid reference to the nested table column ORA-22905: cannot access rows from a non-nested table item Cause: attempt to access rows of an item whose type is not known at parse time or that is not of a nested table type Action: use CAST to cast the item to a nested table type ORA-22906: cannot perform DML on expression or on nested table view column Cause: Attempted to perform a DML on an expression or on a nested table view column where a nested table column of a base table is expected. Action: Only nested table column of a base table is allowed in the DML. ORA-22907: invalid CAST to a type that is not a nested table or VARRAY Cause: Attempted to CAST to a type that is not a nested table or VARRAY Action: Re-specify CAST to a nested table or VARRAY type. ORA-22908: reference to NULL table value Cause: The evaluation of the THE subquery or nested table column resulted in a NULL value implying a NULL table instance. The THE subquery or nested table column must identify a single non-NULL table instance. Action: Ensure that the evaluation of the THE subquery or nested table column results in a single non-null table instance. If happening in the context of an insert statement where the THE subquery is the target of an insert, then ensure that an empty nested table instance is created by updating the nested table column of the parent table"s row specifying an empty nested table constructor. ORA-22909: exceeded maximum VARRAY limit Cause: The total number of elements used in VARRAY construction exceeds the specified VARRAY limit. Action: Don"t use the more than the specified limit of elements for VARRAY construction. ORA-22910: cannot specify schema name for nested tables Cause: Table name was qualified with schema name in the nested table column"s (or attribute"s) storage clause. Action: Re-specify the nested table item"s storage clause without the schema name qualification. By default, the storage table for the nested table item is created in the same schema as the containing table. ORA-22911: duplicate storage specification for the nested table item Cause: The storage clause is specified more than once for the NESTED TABLE column. Action: Remove the duplicate storage specification. ORA-22912: specified column or attribute is not a nested table type Cause: The storage clause is specified for a column or attribute that is not a nested table column or attribute. Action: Specify a valid nested table column or attribute. ORA-22913: must specify table name for nested table column or attribute Cause: The storage clause is not specified for a nested table column or attribute. Action: Specify the nested table storage clause for the nested table column or attribute. ORA-22914: DROP of nested tables not supported Cause: Attempted to DROP a nested table. Action: nested tables cannot be explicitly dropped. nested tables can only be dropped by dropping their containing parent table. ORA-22915: cannot ALTER a nested table"s storage table to ADD/MODIFY columns Cause: any such change. Action: Columns cannot be added or modified for a nested table"s storage table. You must alter the parent table"s nested table column to ORA-22916: cannot do an exact FETCH on a query with Nested cursors Cause: Exact FETCH on a query was specified which is not allowed if the query returns any cursors. Action: Do not use an exact FETCH. ORA-22917: use VARRAY to define the storage clause for this column or attribute Cause: Not using VARRAY to define storage clause for VARRAY column or attribute. Action: Specify VARRAY before the column storage clause and resubmit statement. ORA-22918: specified column or attribute is not a VARRAY type Cause: Attemp to define a VARRAY storage clause for a column or attribute which is not VARRAY type. Action: Specify VARRAY storage clause for a VARRAY column or attribute. ORA-22919: dangling REF error or lock object failed for no wait request Cause: The error could be one of the following. The object corresponding to the REF does not exist or the object was locked by another user and the lock with nowait request failed. Action: Ensure that the REF value is pointing to an existing object or issue a lock request without the nowait option. ORA-22920: row containing the LOB value is not locked Cause: The row containing the LOB value must be locked before updating the LOB value. Action: Lock the row containing the LOB value before updating the LOB value. ORA-22921: length of input buffer is smaller than amount requested Cause: The buffer length is not big enough to hold the amount of data requested. Action: Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary. ORA-22922: nonexistent LOB value Cause: The LOB value associated with the input locator does not exist. The information in the locator does not refer to an existing LOB. Action: Repopulate the locator by issuing a select statement and retry the operation. ORA-22923: amount of data specified in streaming LOB write is 0 Cause: Trying to write LOB value via the streaming mechanism (i.e. unlimited write) but the input amount of data to stream was specified as 0. Thus, the user is trying to write 0 bytes to the LOB value. Action: Write more than 0 bytes to the LOB value. ORA-22924: snapshot too old Cause: The version of the LOB value needed for the consistent read was already overwritten by another writer. Action: Use a larger version pool. ORA-22925: operation would exceed maximum size allowed for a LOB value Cause: Trying to write too much data to the LOB value. LOB size is limited to 4 gigabytes. Action: Either start writing at a smaller LOB offset or write less data to the LOB value. ORA-22926: specified trim length is greater than current LOB value"s length Cause: The input length for which to trim the LOB value to is greater than the current length of the LOB value. Action: May not need to trim the LOB value because it"s already smaller than the trim length specified. Or, if trimming the LOB value really is required, use a smaller trim length. ORA-22927: invalid LOB locator specified Cause: There are several causes: (1) the LOB locator was never initialized; (2) the locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator; (3) the locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator; (4) trying to update the LOB in a trigger body -- LOBs in trigger bodies are read only. Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value. ORA-22928: invalid privilege on directories Cause: An attempt was made to grant or revoke an invalid privilege on a directory. Action: Only CREATE, DELETE, READ and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges. ORA-22929: invalid or missing directory name Cause: The required directory name is invalid or missing. Action: Specify a valid name. ORA-22930: directory does not exist Cause: Attempt to access a directory that does not exist. Action: Make sure the name is correct. ORA-22931: MOVE of nested table to a different tablespace not supported Cause: Attempt to move a nested table to a different tablespace. Action: Nested tables always colocate in the same tablespace as the parent. A nested table can be moved to a different tablespace only by moving its containing table to the target tablespace. ORA-22933: cannot change object with type or table dependents Cause: Attempt to replace, drop or rename an object with type or table dependents. Action: Drop depending objects or use FORCE option if available. ORA-22950: cannot ORDER objects without MAP or ORDER method Cause: an object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons. Action: Define a MAP or ORDER method for the object type ORA-22951: NULL returned by ORDER method Cause: ORDER method used to compare two object values returned NULL which is not allowed. Action: Redefine the ORDER method to not return a NULL. ORA-22952: Nested Table equality requires a map method on the element ADT Cause: Nested Table equality was tried where the element ADT did not have a map method defined on it. Action: Define a map method on the element ADT.. ORA-22953: Cardinality of the input to powermultiset exceeds maximum allowed Cause: The cardinality of the input nested table to the powermultiset should not exceed 32 elements Action: Reduce the number of elements to the input. ORA-22954: This multiset operation is not supported for this element type. Cause: The multiset operation attempted was not supported for the nested table element type. Action: Use a supported element type. ORA-22955: The cardinality parameter is not within the allowed limits Cause: The cardinality parameter has to be greater than 1 and less than or equal to the cardinality of the input. Action: Give a valid cardinality value. ORA-22956: The set contains no elements Cause: An empty set was given as input to the powermultiset function. Action: Give a non-empty set as input ORA-22957: NULL is an invalid input to powermultiset and COLLECT functions Cause: NULL was given as input to the powermultiset or COLLECT function. Action: Give a non-null value as input ORA-22958: This operation is not allowed in check constraints or triggers Cause: An invalid operation is used in a check constraint or trigger Action: Do not use the operation ORA-22970: name does not correspond to an object view Cause: Either the expression is not a view name or the name specified does not correspond to an object view. Action: Replace the expression with the name of an object view. ORA-22971: invalid datatype for PRIMARY KEY-based object identifier Cause: When creating an object view, the datatype of an expression in the WITH OBJECT OID clause is not allowed for PRIMARY KEY-based OID. Action: Replace the expression with one of appropriate scalar datatype. ORA-22972: NULL value not allowed in PRIMARY KEY-based object identifier Cause: A value constituting the PRIMARY KEY-based object identifier is NULL. Action: Ensure the expressions in MAKE_REF system function or attributes in the WITH OBJECT OID clause of an object view do not evaluate to NULL. ORA-22973: size of object identifier exceeds maximum size allowed Cause: Size of the PRIMARY KEY-based object identifier of an object view exceeds the maximum size of 4000 bytes. Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH object OID clause when creating the object view. ORA-22974: missing WITH OBJECT OID clause Cause: WITH OBJECT OID clause is not specified when creating an object view. Action: Specify the WITH OBJECT OID clause. ORA-22975: cannot create a PRIMARY KEY-based REF to this object view Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view. Action: Specify an object view that has a PRIMARY KEY-based object identifier in the MAKE_REF function. ORA-22976: incorrect number of arguments to MAKE_REF Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view. Action: Specify all the necessary arguments for MAKE_REF. ORA-22977: missing or invalid attribute Cause: Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid. Action: Specify a valid attribute of the object type of the object view. ORA-22978: only simple attribute name is allowed in the WITH OBJECT OID clause Cause: Attempted to specify a Nested attribute in the WITH OBJECT OID clause. Action: Specify a top-level attribute of the object type of the object view. ORA-22979: cannot INSERT object view REF or user-defined REF Cause: Attempt to insert an object view REF or user-defined REF in a REF column created to store system generated REF values" Action: Make sure the REF to be inserted is not from an object view or from a user-defined REF column ORA-22980: must specify a set of attributes for the WITH OBJECT OID clause Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying view or table does not have a OID. Action: Specify attributes for the WITH OBJECT OID clause to create a primary key based object identifier for the object view. ORA-22981: must specify a table/view having system generated OID Cause: The super-view is based on a table/view having the system generated OID and the sub-view must also be based on a similar table/view. Action: Specify table/view having system generated OID and retry the the operation. ORA-22982: cannot create sub-view under this view Cause: The view derives its OID from a table/view having primary key based OID and sub-views cannot be created under such views. Action: Specify view having system generated OID or a view created with the specification of attributes in the WITH OBJECT ID clause and retry the operation. ORA-22983: not a user-defined REF Cause: Attempt to use a system generated REF value where a user-defined REF value should be used. Action: Make sure the REF value is user-defined. ORA-22984: view query cannot contain references to a super view Cause: The query defining the view contains references to a super-view of the view being created. Action: Make sure that the view query does not reference a super-view. ORA-22990: LOB locators cannot span transactions Cause: A LOB locator selected in one transaction cannot be used in a different transaction. Action: Re-select the LOB locator and retry the operation. ORA-22991: insufficient space allocated for argument string Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument. Action: Allocate more space for the argument. ORA-22992: cannot use LOB locators selected from remote tables Cause: A remote LOB column cannot be referenced. Action: Remove references to LOBs in remote tables. ORA-22993: specified input amount is greater than actual source amount Cause: (1) For LOB write, the amount of data received is different from the amount that was indicated would be sent. (2) For LOB copy and loadfromfile, the end of the source LOB/FILE value was reached before the specified input amount was copied/loaded. Action: (1) will happen when using OCI"s piecewise mechanism with polling or with a callback function. Modify the code either to send the amount specified or to pass 0 as the input amount so that any amount of data can be sent. (2) will happen if the specified input amount is too large for the source LOB/FILE given the starting source offset. Either decrease the starting source offset, or decrease the amount to copy/load. ORA-22994: source offset is beyond the end of the source LOB Cause: The source offset for a LOB COPY or LOB LOADFROMFILE is beyond the end of the source LOB. Action: Check the length of the LOB and then adjust the source offset. ORA-22995: TABLESPACE DEFAULT option is invalid in this context Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts: - at the table level for a partitioned table - at the partition level for a composite partition. An attempt was made to use the TABLESPACE DEFAULT option in a different context. Action: Remove the TABLESPACE DEFAULT option. ORA-22996: NEXT extent size is smaller than LOB chunksize Cause: An attempt was made to create or alter a LOB segment so that its NEXT extent size was less than the LOB chunksize Action: Specify a NEXT extent size that is greater than or equal to the LOB chunksize ORA-22997: VARRAY | OPAQUE stored as LOB is not specified at the table level Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored as LOB at the partition/subpartition/template level. However the VARRAY|OPAQUE column was not specified to be stored as LOB at the table level when the table was created. Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table level when the table is created. Alternatively, do not specify the VARRAY | OPAQUE column to be stored as LOB at the partition/subpartition/template level if it is not specified at the table level when the table is created. ORA-22998: CLOB or NCLOB in multibyte character set not supported Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data. Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR() ORA-22999: CLOB or NCLOB data may have been corrupted Cause: CLOB or NCLOB contains invalid character data. One possible cause is that the wrong csid was specified for the external file when calling DBMS_LOB.LOADCLOBFROMFILE or DBMS_XSLPROCESSOR.READ2CLOB to load CLOB or NCLOB data from external files. Action: Reload the CLOB/NCLOB data with the correct csid specified for the external file. ORA-23290: This operation may not be combined with any other operation Cause: ALTER TABLE RENAME COLUMN/CONSTRAINT operation was given in conjunction with another ALTER TBALE Operation. This is not allowed. Action: Ensure that RENAME COLUMN/CONSTRAINT is the only operation specified in the ALTER TABLE. ORA-23291: Only base table columns may be renamed Cause: Tried to rename a column of a non-base table, like object table/ nested table/ materialized view table. Action: None. This is not allowed. ORA-23292: The constraint does not exist Cause: The given constraint name does not exist. Action: Give an existing constraint"s name. ORA-23293: Cannot rename a column which is part of a join index Cause: The column participates in a join index. Action: If you need to rename the column, you need to drop the join index. ORA-23300: %s Cause: The stored procedure "raise_system_error" was called which causes this error to be generated. Action: Correct the problem as described in the error message or contact the application administrator or DBA for more information. ORA-23301: mixed use of deferred rpc destination modes Cause: Replication catalog determined deferred RPC destinations were mixed with destination determined by other mechanisms in the same transaction. Action: Do not mix destination types in the same transaction. ORA-23302: application raised communication failure during deferred RPC Cause: An application declared a communication failure during a defered RPC. Action: Retry the application when communication is restored. ORA-23303: application raised generic exception during deferred RPC Cause: An application declared a generic failure during a defered RPC. Action: Determined by the application ORA-23304: malformed deferred rpc at arg string of string in call string, in tid string Cause: A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to dbms_defer.call Action: Be sure the number of actuals matches the count. ORA-23305: internal deferred RPC error: string Cause: An internal error occurred in deferred rpc. Action: Report the error and other information to support. ORA-23306: schema string does not exist Cause: The schema name was null or misspelled, or the schema does not exist locally. Action: Specify the schema correctly, or create it with CREATE USER. ORA-23307: replicated schema string already exists Cause: The given database already replicates the given schema. Action: Choose a different schema or a different database. ORA-23308: object string.string does not exist or is invalid Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status. Action: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in all_repobject. ORA-23309: object string.string of type string exists Cause: An object in the same namespace exists, perhaps with a different type or shape, or the same object has already been registered as an repobject in another object group. Action: Remove the offending object with the SQL DROP command, unregister the offending object with dbms_repcat.drop_master_repobject(), or reinvoke the request using TRUE for a boolean parameter such as retry or use_existing_object. ORA-23310: object group "string"."string" is not quiesced Cause: The requested operation requires the object group to be suspended. Action: Invoke suspend_master_activity at the repgroup"s masterdef, wait until the status has changed to quiesced, and then retry the original request. ORA-23312: not the masterdef according to string Cause: The group name is null, the group name is misspelled, the invocation or given database is not the masterdef, or one of the masters does not believe the invocation database is the masterdef. Action: If the given group name and masterdef were both correct, connect to the masterdef and retry the request, or relocate the masterdef at the (errant) databases using relocate_masterdef. ORA-23313: object group "string"."string" is not mastered at string Cause: The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master. Action: If the given group name was correct, connect to a current master and retry the request, make the invocation database a master with add_master_database, or use switch_mview_master if the invocation database is a materialized view site. ORA-23314: database is not a materialized view site for "string"."string" Cause: The invocation database is not a materialized view database for the given object group. Action: Connect to the desired materialized view database and retry the request, or make the invocation database a materialized view site with create_mview_repschema or create_mview_repgroup. ORA-23315: repcatlog version or request string is not supported by version string Cause: Either incompatible repcat versions are used, or a repcatlog record has been corrupted. Action: Convert the master to a compatible version of repcat or retry the request. ORA-23316: the masterdef is string Cause: The requested operation is not permitted on a masterdef site. Action: Relocate the masterdef to another master and retry the operation. ORA-23317: a communication failure has occurred Cause: The remote database is inaccessible. Action: Ensure the remote database is running, the communications network is functioning, and the appropriate database links are present. ORA-23318: a ddl failure has occurred Cause: User-supplied or system-generated ddl did not execute successfully. Action: Examine ddl, database state, repcatlog, and all_errors to determine why the failure occurred. ORA-23319: parameter value string is not appropriate Cause: The given value of a