-- --------------------------------------------------------------------------- -- DOC : Simple COLLECTION OF ORACLE "ORA-" ERRORS -- DATE : 24/12/2011 -- VERSION : 23 -- COMPILED BY : Albert -- BEST USE : USE "FIND/SEARCH" OF YOUR EDITOR TO SEARCH FOR A PARTICULAR ERROR MESSAGE OR IDENTIFIER. YOU MIGHT NEED TO 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: ======================================================================= ----- 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. 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 parameter is either null, misspelled, or not supported. Action: Refer to the documentation and use parameter values that are appropriate for the given situation. ORA-23320: the request failed because of values string and string Cause: A missing ddl record for a repcatlog record, or inconsistency in repcat views. Action: Retry the request, or make the views consistent. ORA-23321: Pipename may not be null Cause: You called dbms_pipe with a null pipe name. Action: Find out the name of the pipe and call function with non-null pipename. ORA-23322: Privilege error accessing pipe Cause: You either tried to create a pipe that already existed and belonged to someone else, or remove a pipe that you were not authorized to use, or put a message into a pipe that you were not authorized for, or get a message from a pipe that you were not authorized for. Action: You may have to use a different pipename. ORA-23323: parameter length exceeds deferred RPC limits Cause: A deferred rpc parameter was longer than the deferred rpc limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters. Action: Use smaller parameters. ORA-23324: error string, while creating deferror entry at "string" with error string Cause: The given error was encountered while attempting to create a deferor entry for the give error code and the give database. Action: Correct the cause of the given error. ORA-23325: parameter type is not string Cause: A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or dbms_defer_sys_query was called to retrieve a deferred rpc parameter from the deferred rpc queue, but the type of the parameter does not match the return type of the function. Action: Use the function corresponding to the parameter type. ORA-23326: object group "string"."string" is quiesced Cause: Either suspend_master_activity has been called before the object group has resumed normal operation or a (deferred) rpc operation was attempted while the object group was quiesced. Action: If suspend_master_activity has been called and a resume_master_activity request is pending, wait until it completes, and then reinvoke suspend_master_activity. Otherwise, resume database activity with the resume_master_activity call. ORA-23327: imported deferred rpc data does not match string of importing db Cause: Deferred rpc queues were imported from a database with a different global name or operating system than importing database. Action: Deferred rpc data should only be imported into a database with the same global name and hardware and operating system. ORA-23328: mview base table "string"."string" differs from master table "string"."string" Cause: When creating a materialized view through repcat, the materialized view base table name did not match a replicated table name at the master. Action: Change the materialized view ddl to use the same base table as the replicated table name at the master. ORA-23329: successful user-provided ddl but no materialized view "string"."string" Cause: The DDL provided by the user to create a materialized view was executed without error, but materialized view does not exist. Action: Manually back-out the DDL, and reregister with matching ddl and materialized view. ORA-23330: column group string already exists Cause: The column group was already registered in the object group. Action: Use a column group name not yet registered in the replicated object group. ORA-23331: column group string does not exist Cause: The given column group is either null, misspelled or not registered. Action: Use a registered column group. ORA-23332: group string is in use; cannot drop Cause: The given column group or priority group is being used to resolve conflicts. Action: Call dbms_repcat procedures drop_update_resolution, drop_delete_resolution, drop_unique_resolution so that the column group or priority group is no longer in use before dropping. ORA-23333: column string is already part of a column group Cause: Attempted to add a column to a column group when the column was already a member of a column group. Action: Drop the column from its existing column group before trying to add it to another. ORA-23334: column string does not exist in table or column group Cause: The given column is either null, misspelled or is not part of the given table or column group. Action: Use a column that is a member of the table or column group. ORA-23335: priority group string already exists Cause: The priority group was already registered in the object group. Action: Use a column group name not yet registered in the object group. ORA-23336: priority group string does not exist Cause: The priority group was already registered in the object group. Action: Use a priority group name not yet registered in the object group. ORA-23337: priority or value not in priority group string Cause: The specified value or priority has not been registered as part of the priority group. Action: Either specify a different value or priority that is already part of the priority group, or add the value to the priority group. ORA-23338: priority or value already in priority group string Cause: The specified value or priority has already been registered as part of the priority group. Action: Either specify a different value or priority that not already part of the priority group, or drop the value to the priority group. ORA-23339: duplicate conflict resolution information Cause: The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered. Action: Verify that additional conflict resolution information needs to be added and provide a new sequence number. If modifying existing information, the existing information must be dropped first. ORA-23340: incorrect resolution method string Cause: User function is specified when conflict resolution method was not "USER FUNCTION" or specified resolution method is not one of the predefined methods. Action: If user function is specified when conflict resolution method was not "USER FUNCTION", either reregister function with method as "USER FUNCTION" or specify a NULL user function. Otherwise Specify one of the documented supported conflict resolution methods. ORA-23341: user function required Cause: A NULL user function was specified for the "USER FUNCTION" method. Action: Provide user function name (e.g., "schema"."package"."function") that conforms to the documented user function specifications or specify one of the documented supported conflict resolution methods. ORA-23342: invalid parameter column string Cause: The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method. Action: Specify a parameter column from the specified column group that has a correct type for the conflict resolution method. ORA-23343: no match for specified conflict resolution information Cause: The specified combination of column group, sequence, conflict type has not been registered (e.g., for adding a comment). Action: Specify a combination of column group, sequence, conflict type has been registered. ORA-23344: constraint (string.string) does not exist Cause: A null, misspelled or nonexistent constraint was specified when registering a uniqueness conflict. Action: Register a named constraint for the specified table. ORA-23345: table "string"."string" not registered to collect statistics Cause: A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics. Action: Call dbms_repcat.register_statistics to register the table. ORA-23346: primary key or object ID is undefined for table or materialized view string Cause: Trying to generate replication support for a table or materialized view without a primary key (as defined by a constraint or dbms_repcat.set_columns) or an object ID. Action: For a table, add a primary key constraint or define a primary key using dbms_repcat.set_columns or use object tables. For a ROWID materialized view, set min_communication to false or use primary key or object ID materialized views. ORA-23347: datatype string for column string table string not supported Cause: The table has a column whose datatype is not supported by repcat. Action: Remove the column from the table, or alter the column to have one of the supported datatypes. ORA-23348: cannot replicate procedure string; only IN parameters supported Cause: Trying to generate replication support for a package that has a procedure with OUT or IN OUT parameters. Action: Remove the procedure from the package, or remove the OUT or IN OUT parameters from the procedure. ORA-23349: cannot generate replication support for functions Cause: Trying to generate replication support for a package that has a public function, or for a stand-alone function. Action: Remove the public function from the package, or alter the function to be a procedure. ORA-23350: maximum number of recursive calls exceeded Cause: This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts. Action: Re-execute the deferred transaction from DefError using dbms_defer_sys.execute_error ORA-23351: parameter datatype string for procedure string not supported Cause: The procedure has a parameter whose datatype is not supported by repcat. Action: Remove the parameter from the procedure, or alter the parameter to have one of the supported datatypes. ORA-23352: duplicate destination for deferred transaction Cause: A duplicate destination was specified for a deferred transaction either in a dbms_defer.call call or an earlier dbms_defer.transaction call or a dbms_defer_sys.add_default_dest call. Action: Remove the duplicate entry ORA-23353: deferred RPC queue has entries for object group "string"."string" Cause: The requested action cannot be performed until the queue is empty for the given object group Action: Use dbms_defer_sys.execute or dbms_defer_sys.delete_tran to empty the queue. ORA-23354: deferred RPC execution disabled for "string" with "string" Cause: Deferred RPC can not be executed at the destination with the specified catchup value because their propogation has been disabled. Action: Enable deferred RPC execution with the dbms_defer_sys.set_disabled call. ORA-23355: object string.string does not exist or is invalid at master site Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object at the master site, or the object does not exist as a replicated object with the appropriate status. Action: Ensure the object is valid in the master database, and is visible to the user, and, if appropriate, is a valid object in all_repobject. ORA-23356: masterdef recognizes a master which does not recognize the masterdef Cause: Possibly drop_master_repgroup was run at a master site but remove_master_databases was not run at master definition site for that master. Action: Run remove_master_databases from master definition site to remove the appropriate master (see associated error messages). ORA-23357: the propagator does not exist Cause: The propagator does not exist. Action: Register a new propagator. ORA-23358: invalid remote user Cause: The local user does not match the remote user connected via a database link. Action: Drop and recreate the identified database link with the connect-to user identical to the owner of the database link. ORA-23359: error on creating a ddl record for a repcatlog record Cause: The userid in the repcatlog record does not match the userid of the connected user. Action: Retry the operation with a different user. ORA-23360: only one materialized view for master table "string" can be created Cause: Trying to create more than one materialized view on a given master table in the same rep group. Action: Create these other materialized views in a different rep group at another site. ORA-23361: materialized view "string" does not exist at master site Cause: The materialized view does not exist at the master site for offline instantiation of the materialized view. Action: The correct procedure is to create the materialized view in a different schema at the master site, and then follow the instructions for offline instantiation of materialized views. ORA-23362: invalid user Cause: The given user does not exist. Action: none ORA-23363: mismatch of mview base table "string" at master and mview site Cause: The name of the base table of the materialized view at the master site is different from the base table at the materialized view site. This error may arise during offline instantiation of materialized views. Action: Retry offline instantiation with a materialized view name less than 24 bytes ORA-23364: Feature not enabled: Advanced replication Cause: The Advanced Replication feature is not enabled at this site. Updatable materialized views, deferred RPCs, and other replication features are, therefore, unavailable. Action: Do not attempt to use this feature. Contact an Oracle Customer Support representative if the Advanced Replication feature has been purchased but not enabled. ORA-23365: site string does not exist Cause: site specified in argument "reference_site" or argument "comparison_site" in call to "differences()" routine or "rectify()" routine does not name an existing site. Action: Make sure that database sites specified really do exist, and re-run the routine. ORA-23366: integer value string is less than 1 Cause: Value of argument "max_missing" to routine "differences()" cannot be less than 1. Value of argument "commit_rows" to routines "differences()" and "rectify()" cannot be less than 1. Action: Choose an integer value for those arguments to be 1 or greater. ORA-23367: table string is missing the primary key Cause: Table specified in argument "oname1" or "oname2" in call to "differences()" routine does not contain either a primary key or a virtual primary key (defined through dbms_repcat package under symmetric replication). Action: Make sure the tables specified have a primary key defined. ORA-23368: name string cannot be null or the empty string Cause: Argument "sname1," "sname2," "oname1," "oname2," "missing_rows_sname," "missing_rows_oname1," "missing_rows_oname2" to "differences()" or "rectify()" cannot be NULL or "" (empty string). Action: Change argument to non-null or non-empty string. ORA-23369: value of "string" argument cannot be null Cause: Argument "max_missing" to "differences()" routine cannot be NULL. Action: Legal values for "max_missing" are integers 1 or greater. ORA-23370: table string and table string are not shape equivalent (string) Cause: The tables specified are not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths are not the same. Specifically, problem is in the parentheses and is one of the following: the number of columns are not equal, datatypes of columns with same name in different tables are different, lengths of varchar2 and char columns are not equal, precision and scale of number datatypes are not equal. Action: Make sure the two tables being compared have the same number of columns, same column names, and same datatypes. ORA-23371: column string unknown in table string Cause: Some column in "array_columns" argument (or "column_list" argument) to "differences()" routine does not correspond to a column in the specified table. Action: Make sure that all the columns in either "array_columns" or "column_list" are present in the specified table. ORA-23372: type string in table string is unsupported Cause: Certain types in the table comparison utility are not supported. Action: Make sure that the types of columns in the tables to be compared are the ones supported by symmetric replication. ORA-23373: object group "string"."string" does not exist Cause: The group name was null or misspelled, or the group does not exist locally. Action: Specify the group correctly, or create it with dbms_repcat.create_master_repgroup(). ORA-23374: object group "string"."string" already exists Cause: The given database already replicates the given object group. A materialized view repgroup cannot be created at a given site where a master repgroup with the same name already exists. Action: Choose a different group or a different database. ORA-23375: feature is incompatible with database version at string Cause: A feature not compatible with the specified database was used Action: Set or raise the value of the "compatible" INIT.ORA parameter to match the necessary compatibility level. ORA-23376: node string is not compatible with replication version "string" Cause: A feature not compatible with the remote database was used Action: Upgrade the remote database and retry the operation ORA-23377: bad name string for missing_rows_oname1 argument Cause: An attempt was made to use the name of the reference site table as the name of the missing_rows_oname1 argument. Action: Provide a separately created table with a different name for missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared. ORA-23378: connection qualifier "string" is not valid for object group "string"."string" Cause: The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in create_master_repgroup. Action: Use or create a database link which contains the correct connection qualifier. ORA-23379: connection qualifier "string" is too long Cause: The maximum length of a database link, including the connection qualifier, is 128 bytes. Action: Use a shorter connection qualifier, or shorten the name of the database link ORA-23380: propagation mode "string" is not valid Cause: The specified propagation may be misspelled, or is not supported. For materialized view sites, all materialized view object groups at the same materialized view site with the same master object group must all have the same propagation method. Action: Refer to the manual on replicated data for valid propagation modes. For materialized view sites, also ensure that the propagation modes of all materialized view object groups with the same master object group are the same. ORA-23381: generated object for base object string.string@string does not exist Cause: The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support. Action: Ensure that the generated replication object(s) for the base object exist and are valid at the specified site. If the generated object(s) do not exist, then the procedure dbms_repcat.generate_replication_support() needs to be called from the master definition site for the base object. missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared. ORA-23382: materialized view repgroup "string"."string" is not registered at site string Cause: The materialized view repgroup is not currently registered at the master and so cannot be unregistered. Action: None ORA-23383: registration for materialized view repgroup "string"."string" failed at site string Cause: Insertion into local repschema table failed. Action: None ORA-23384: replication parallel push string argument out of range Cause: Specified numeric argument to dbms_defer_sys.push is invalid. Action: Fix the argument value and try again. ORA-23385: replication parallel push string argument not valid Cause: Specified string argument to dbms_defer_sys.push is invalid. Action: Fix the argument value and try again. ORA-23386: replication parallel push cannot create slave processes Cause: An error was occurred while creating slave processes for parallel push. Action: none ORA-23387: replication parallel push dequeue error Cause: An attempt to dequeue a deferred transaction failed while trying to assign a new queue batch number. Action: none ORA-23388: replication parallel push watermark error Cause: An error occurred during parallel push while trying to update the high-water-mark information in system.def$_destination. Action: none ORA-23389: obsolete procedure; drop objects and recreate using new master Cause: dbms_repcat.switch_mview_master is no longer supported. Action: Drop the objects in the object group and recreate them using the new master. ORA-23392: could not find materialized view to be associated with "string"."string" Cause: Could not find materialized view associated with a trigger or index that is being pulled from the master site. Action: Ensure that materialized view, master, and master index or trigger is registered as replicated objects. ORA-23393: the user is already the propagator Cause: The given user is already the current propagator. Action: none ORA-23394: duplicate propagator Cause: More than one valid propagator exist. Action: Unregister any duplicate propagator. ORA-23395: object "string"."string" of type "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-23396: database link "string" does not exist or has not been scheduled Cause: the database link does not exist in the schema of the replication propagator or has not been scheduled. Action: Ensure that the database link exists in the database, is accessible and is scheduled for execution. ORA-23397: global name "string" does not match database link name "string" Cause: the database link name at the local node does not match the global name of the database that the link accesses. Action: Ensure that global names is set to true and the link name matches the global name. ORA-23398: user name "string" at database link "string" does not match local user name "string" Cause: the user name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same. Action: Ensure that the user ID of the replication administration user at the local node and the user ID at the node corresponding to the database link are the same. ORA-23399: generation of replication support for "string"."string" is not complete Cause: Replication support for the specified object has not been generated or the generation process is not yet complete. Action: Ensure that replication support has been generated for the object. Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate replication support for the object. ORA-23400: invalid materialized view name "string" Cause: A null, misspelled, or badly formed materialized view name was given to dbms_mview.refresh. Action: Provide a valid materialized view name to dbms_mview.refresh. ORA-23401: materialized view "string"."string" does not exist Cause: A materialized view name was given to dbms_mview.refresh that is not in sys.snap$ or its associated views. Action: Provide a materialized view name that is in sys.snap$, all_mviews or user_mviews. ORA-23402: refresh was aborted because of conflicts caused by deferred txns Cause: There are outstanding conflicts logged in the DefError table at the materialized view"s master. Action: Resolve the conflicts in the master DefError table and refresh again after the table is empty. Alternatively, refresh with refresh_after_errors set to TRUE, which will proceed with the refresh even if there are conflicts in the master"s DefError table. Proceeding despite conflicts can result with an updatable materialized view"s changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved). ORA-23403: refresh group "string"."string" already exists Cause: Making a new refresh group when there is already a group of the same name in sys.rgroup$. Action: Choose a diifferent refresh group name. ORA-23404: refresh group "string"."string" does not exist Cause: A refresh group name was given that is not in sys.rgroup$. Action: Provide a refresh group name that is in sys.rgroup$ or dbs_rgroup. ORA-23405: refresh group number string does not exist Cause: A refresh group number was given that is not in sys.rgroup$. Action: Provide a refresh group number that is in sys.rgroup$ or dbs_rgroup. ORA-23406: insufficient privileges on user "string" Cause: The caller is not the owner of the materialized view and does not have ALTER ANY MATERIALIZED VIEW privileges. Action: Perform the operation as the owner of the materialized view or as a user with ALTER ANY MATERIALIZED VIEW privileges. ORA-23407: object name string must be shaped like "schema"."object" or "object" Cause: The object name (e.g., the rollback segment, the materialized view name, the refresh group) was incorrectly specified. Action: Retry the operation with the object name properly specified (like "schema"."object" or "object") ORA-23408: this replication operation is not supported in a mixed configuration Cause: operation is not supported if the object group is replicated at a pre-V8 node. Action: Ensure that all nodes of the replicated object group are V8. ORA-23409: could not find an unused refresh group number Cause: 1000 consecutive refresh group numbers, as defined by the rgroupseq number, were already used by rows in sys.rgroup$. Action: Alter the sequence number to be within a legal unused range and destroy unneeded refresh groups. ORA-23410: materialized view "string"."string" is already in a refresh group Cause: A materialized view of the same name is already in a refresh group. Action: Subtract the materialized view from the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group. ORA-23411: materialized view "string"."string" is not in refresh group "string"."string" Cause: The specified materialized view is not in the specified refresh group. Action: Try again with the proper materialized view and refresh group names. ORA-23412: master table"s primary key columns have changed Cause: The master table"s primary key constraint was modified after the primary key materialized view was created. Action: Drop and recreate the primary key materialized view ORA-23413: table "string"."string" does not have a materialized view log Cause: The fast refresh can not be performed because the master table does not contain a materialized view log. Action: Use the CREATE MATERIALIZED VIEW LOG command to create a materialized view log on the master table. ORA-23414: materialized view log for "string"."string" does not record rowid values Cause: A rowid materialized view is being fast refreshed, but the materialized view log does not record rowid information. Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to begin recording rowid information in the materialized view log. ORA-23415: materialized view log for "string"."string" does not record the primary key Cause: A primary key materialized view is being fast refreshed, but the materialized view log does not record primary key information. Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY command to begin recording primary key information in the materialized view log. ORA-23416: table "string"."string" does not contain a primary key constraint Cause: The master table does not constaint a primary key constraint or the primary key constraint has been disabled. Action: Create a primary key constraint on the master table or enable the existing constraint. ORA-23417: unknown materialized view type: string Cause: A fast refresh is being performed on a materialized view of an unknown or unsupported type. Action: Check all_mviews and ensure that the materialized view being refreshed a valid materialized view. ORA-23418: cannot unregister the propagator who is currently in use Cause: The propagator is currently used in propagating replication RPCs. Action: Try again later when there is no transaction active in propagating replication RPCs. ORA-23419: regenerate replication support before resuming master activity Cause: There are tables in the object group that require regeneration of replication support. Action: Check the generation_status column in the all_repobjects view. Regenerate replication support for any table in the object group with a "NEEDSGEN" status. Resume master activity. ORA-23420: interval must evaluate to a time in the future Cause: The parameter "interval" evaluates to a time earlier than SYSDATE. Action: Choose an expression that evaluates to a time later than SYSDATE. ORA-23421: job number string is not a job in the job queue Cause: There is no job visible to the caller with the given job number. Action: Choose the number of a job visible to the caller. ORA-23422: Oracle Server could not generate an unused job number Cause: Oracle Server could not generate a job number that was not used to identify another job. Action: Retry the operation. ORA-23423: job number string is not positive Cause: The given job number is less than 1. Action: Choose a positive integer. ORA-23424: materialized view "string"."string" at string not registered Cause: The specified materialized view has not be successfully registered at this site. Action: Register the materialized view manually at either the master site or the materialized view site. ORA-23425: invalid materialized view identifier string Cause: The argument provided to dbms_mview.purge_mview_from_log is an invalid materialized view identifer or it does not identify an Oracle 8 fast refreshable materialized view or the materialized view has been already purged. Action: If the materialized view is an Oracle 8 fast refreshable materialized view then provide purge_mview_from_log with its valid materialized view identifier. ORA-23426: deferred RPC queue has entries for string Cause: The requested action cannot be performed until the queue is empty for the given site/dblink Action: Use dbms_defer_sys.push, dbms_defer_sys.purge_queue or dbms_defer_sys.delete_tran to empty the queue. ORA-23427: deferred purge queue argument string out of range Cause: Specified numeric argument to dbms_defer_sys.purge_queue is invalid. Action: Fix the argument value and try again. ORA-23428: job associated instance number string is not valid Cause: A job is associated with an instance that is not running. Action: Choose a running instance for job affinity, or set force parameter to TRUE. ORA-23430: argument "string" cannot be NULL or empty string Cause: The caller has provided an argument whose value cannot be NULL or the empty string. Action: Check that the varchar2 value provided is not NULL or the empty string, and retry the call. ORA-23431: wrong state: string Cause: The routine was executed against a replicated object group that was in the wrong state. Action: Make sure that the replicated object group is in the state given in the error message. ORA-23432: master site string already exists Cause: An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group. Action: If you were trying to add this site, do nothing because it already exists; otherwise, pick the name of another site, and re-run the routine. ORA-23433: executing against wrong master site string Cause: An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine. Action: Provide an argument to the routine that correctly indicates the site against which the routine should be executing. ORA-23434: master site string not known for object group Cause: The site name given as an argument to a routine was not already known to the replicated object group. Action: Execute the dbms_offline_og.begin_instantiation() routine to add a new site to the replicated object group. ORA-23435: cannot create an updatable ROWID materialized view with LOB columns Cause: The propagation of LOB data from materialized view sites to the master site requires a primary key on the replicated table. Thus updatable ROWID materialized views that contain LOB columns are not supported. Action: Create a primary key materialized view instead of a ROWID materialized view. If the materialized view already exists, it can be converted to a primary key materialized view using the ALTER MATERIALIZED VIEW DDL command. ORA-23436: missing template authorization for user Cause: The specified template authorization does not exist. Action: Check the values for user name and refresh template name to ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view. ORA-23437: template authorization already exists for user Cause: The specified user already has been authorized to use the specified refresh group template. Action: Check the values for user name and refresh template name or query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values were passed as parameters. ORA-23438: missing refresh group template Cause: The specified refresh group template does not exist. Action: Verify that the refresh group template does not exist by querying the DBA_REPCAT_REFRESH_TEMPLATES view. ORA-23439: refresh group template already exists Cause: The specified refresh group template already exists. Action: Verify that the refresh group template exists by querying the DBA_REPCAT_REFRESH_TEMPLATES view. ORA-23440: incorrect public template value Cause: The public template parameter is not "Y", "N" or NULL. Action: Correct the value of the public template parameter. It must be "Y","N" or NULL. ORA-23441: object does not exist for refresh group template Cause: The specified object does not exist in the refresh group template. Action: Correct the object name and object type parameters. Check the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct name and type of the object. ORA-23442: object already exists for the refresh group template Cause: The specified object already exists in the refresh group template. Action: Change the object name and object type parameters. Query the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct name and type of the object. ORA-23443: missing template parameter Cause: The specified template parameter does not exist. Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name. ORA-23444: duplicate template parameter Cause: The template parameter already exists for the specified refresh group template. Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name. ORA-23445: missing template site Cause: The template site specified by the site name, user name and refresh group template name does not exist. Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites. ORA-23446: duplicate template site Cause: The template site specified by the site name, user name and refresh group template name already exists. Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites. ORA-23447: missing user parameter value Cause: The user parameter value specified by the user name, parameter name and refresh group template name does not exist. Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARMS view to query the existing user parameters. ORA-23448: duplicate user parameter value Cause: The user parameter value specified by the user name, parameter name and refresh group template name already exists. Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARMS view to query the existing user parameters. ORA-23449: missing user name Cause: The user specified by the user name parameter does not exist in the database. Action: Correct an invalid user name or create the user in the master database. Use the DBA_USERS view to select the valid database users. ORA-23450: flavor already contains object "string"."string" Cause: The flavor already contains the specified object. Action: Check that the specified object is correct. To add all columns of a table object, delete the object from the flavor and then add it again. ORA-23451: flavor string already defined for object group "string"."string" Cause: The given object group already contains a (possibly unpublished) definition of the specified flavor. Action: Check the spelling of the flavor name. Check for an unpublished flavor of the desired name. ORA-23452: flavor string of object group "string"."string" is already published Cause: The given object group already contains a (published) definition of the specified flavor. Action: Check the spelling of the flavor name. ORA-23453: requested operation is not supported on top flavor Cause: The TOP flavor has a NULL name and may not be directly defined or deleted. Action: Supply the name of a flavor other than the TOP flavor or use dbms_repcat routines to implicitly change the TOP flavor. ORA-23454: flavor string not defined for object group "string"."string" Cause: The given object group does not contain a (published) definition of the specified flavor. Action: Check the spelling of the flavor name. Ensure the flavor has been defined (and published) for the object group. ORA-23455: flavor string contains object "string" Cause: The given flavor contains the object to be dropped. Action: Purge the flavor or choose another object to drop. ORA-23456: flavor string does not contain "string" Cause: The flavor does not contain the given object, column, or attribute. Action: Either drop the flavor or choose a different object, column, or attribute. ORA-23457: invalid flavor ID string Cause: The given flavor ID is invalid. Action: Make sure this flavor has been instantiated. If the flavor ID is outside the range (-2147483647, 2147483647), contact customer support. ORA-23458: inappropriate flavor string at string Cause: The given flavor at the given database prevents the operation from succeeding. Action: Either change the database flavor or choose a different operation. ORA-23459: flavor string must contain "string" Cause: The flavor must contain the given object, column, or attribute. Action: Either choose a different database flavor or ensure the object, column, or attribute is available. ORA-23460: missing value for column string in resolution method "string" for "string"."string"."string" Cause: before resolving conflicts, some values necessary resolving conflicts are not available, or after resolving conflicts, some values necessary for re-trying of the SQL are not available Action: define appropriate flavors, provide necessary values through availability vector in USER FLAVOR FUNCTION for conflict resolution ORA-23462: flavor string in use at site string Cause: The given flavor cannot be deleted because it is being used at the given site. Action: Change the flavor of the site, or unregister it if it is a materialized view site. ORA-23463: flavor incompatible with object "string"."string" Cause: An existing flavor includes the specified object with an incompatible type. Action: Change the type of the object, or delete the flavor if it is not in use. ORA-23464: flavor lacks column string of "string"."string" Cause: The flavor includes some columns of an object group but not all the required columns. Action: Change the flavor definition to include all required columns. ORA-23465: flavor already includes column string of "string"."string" Cause: The flavor includes the specified column which is being added. Action: Check that the specified column is correct. ORA-23466: flavor requires missing object "string"."string" Cause: The flavor includes the specified object which does not exist Action: Check that the specified object name is correct, and create the object if appropriate. ORA-23467: flavor lacks object "string"."string" Cause: The flavor does not include the specified object which is being dropped. Action: Check that the specified object is correct. ORA-23468: missing string string Cause: The template is missing the object with the specified key. Action: Add the object to the template. ORA-23469: %s is different between templates Cause: The values for the specified columns are different in each template for the same key values. Action: Correct the column values to make the templates the same. ORA-23470: invalid status Cause: The status should be DELETED, INSTALLING or INSTALLED. Any other status is invalid. Action: Check that the specified status value is correct. ORA-23471: template not authorized for user Cause: The refresh template is private and the user has not been authorized to instantiate the template. Action: Authorize the user to use the template. ORA-23472: materialized view "string"."string" must be atomically refreshed Cause: Non-atomic refresh is not supported for the specified materialized view. Action: Set the value of the ATOMIC parameter to FALSE in the refresh procedure being used or remove the specified materialized view from the set of materialized views being refreshed. ORA-23473: replication RPC processing for "string"."string" is disabled Cause: The processing of replication RPCs for the object group that contains this object is disabled. This includes RPCs in the error queue. Action: Processing of replication RPCs is disabled when the object group is being offline instantiated. Wait until offline instantiation is finished. ORA-23474: definition of "string"."string" has changed since generation of replication support Cause: The current columns in the specified table and their column types do not match the columns and column types when replication support was last generated. Action: Regenerate replication support for the affected table. All flavors that include the specified table should be checked for validity. Types for any UDT columns should also be checked for validity. ORA-23475: key column string must be sent and compared Cause: The specified column is a key column and must be sent and compared during replication propagation. Action: Make sure every key column is sent and compared. ORA-23476: cannot import from string to string Cause: This object was imported from a database with a different global name than the importing database. Action: Only import this object into a database with the same global name. ORA-23477: unable to alter propagation mode for object group "string"."string" Cause: The propagation method of a materialized view object group can only be altered when no other object groups with the same master object group are sharing the materialized view site. Action: Ensure that there are no other materialized view object groups at the local site with the same master object group. ORA-23478: object group "string" is already mastered at string Cause: There is at least one other materialized view repgroup at the local site with the same group name but a different master site. Action: Ensure that all materialized view repgroups at the local site with the same group name have the same master. ORA-23480: Column string is not a top-level column of "string"."string". Cause: The column is either not a top-level column or is not present in the table or materialized view. Action: Ensure only valid top-level columns are used. ORA-23482: column string of "string"."string": object types not allowed. Cause: The column is of Object Type. Action: Ensure that all the columns are not of Object Type. ORA-23483: object "string"."string" not allowed in this operation. Cause: The specified operation does not support the given object. Action: Do not invoke the operation for this object. ORA-23484: internal internet Application Server error: string Cause: An internal error occurred in internet Application Server. Action: Report the error and other information to support. ORA-23485: Column group "string" must consist of a single numeric column only Cause: The column group doesn"t contain only one numeric column. Action: Use a column group containing a single numeric column. ORA-23487: object groups "string"."string" and "string"."string" do not have the same connection qualifier Cause: The specified two object groups do not have the same connection qualifier. Action: Do not invoke the operation on the above object groups, or ensure they have the same connection qualifier. ORA-23488: propagation mode "string" for "string" is not allowed for this operation Cause: This operation does not support the specified dblink in the above propagation mode. Action: Do not invoke the operation for this dblink, or change the propagation mode for this dblink. ORA-23489: duplicate entry "string" Cause: The specified value is duplicated in the parameter list. Action: Remove duplicated entries in the parameter list. ORA-23490: extension request "string" with status "string" not allowed in this operation Cause: The specified operation is not allowed for the extension request with the specified status. Action: Ensure the extension request has the appropriate status before retrying this operation. ORA-23491: no valid extension request at "string" Cause: The specified database does not have a valid extension request. Action: Ensure there is a valid extension request in DBA_REPEXTENSIONS view before retrying this operation. ORA-23492: no new sites for extension request "string" Cause: There is no new site with the specified extension request. Action: Ensure there is at least one new site in DBA_REPSITES_NEW view for this request before retrying this operation. ORA-23493: "string" is not a new site for extension request "string" Cause: The specified extension request does not include the specified site as a new site. Action: Ensure the specified site is a new site for this extension request before retrying this operation. ORA-23494: too many rows for destination "string" Cause: The specified destination has too many rows in system.def$_destination table. Action: Ensure the specified destination has at most two valid rows before retrying this operation. ORA-23495: serial propagation can not be used for "string" Cause: The sites involved may be in the process of adding a new site without quiescing. Action: Check the def$_destination table for this destination and try parallel propagation. ORA-23496: can not change disabled status for "string" and "string" Cause: The disabled status for this site is set internally for synchronization during adding a new master without quiescing. Action: Ensure adding a new master without quiescing finished before invoking this procedure. ORA-23497: repgroup name cannot be null Cause: The array of Repgroup names contains a null value. Action: Ensure that the array of Repgroup names is dense and is not null terminated. ORA-23498: repgroups specified must have the same masters Cause: The Repgroup names specified do not have the same masters. Action: Ensure that the Repgroup names specified have the same masters. ORA-23500: cannot switch master for a multi-tier materialized view repgroup "string"."string" Cause: An attempt was made to switch master for a materialized view repgroup when its parent repgroup is also a materialized view repgroup. This is not allowed. Action: Drop and recreate the materialized view repgroup based on a proper parent repgroup. ORA-23501: refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0 Cause: Instantiation of a refresh template is not supported for database compatibility 8.0 or less. Action: Be sure the database compatibility is 8.1 or above. ORA-23502: valid directory for offline instatiation is not specified Cause: An attempt was made to offline instantiate to a directory which is not specified or null. Action: There are two ways to specify the directory: o As a parm offline_dirpath to the API o As an init.ora parm named utl_file_dir Make sure you have specified an appropriate directory in which the offline file can be created. ORA-23503: error occurred during IAS instantiation Cause: An attempt was made to instantiate a IAS site. Error occurred during IAS instantiation. Action: See other errors on the error stack to look for the source of the problem. If the error still persists, contact Oracle Support. ORA-23504: columns added to table do not match list of columns to be added Cause: The list of columns passed as a parameter does not match the columns to be added to the table. Action: Correct the DDL string or list of columns and rexecute. ORA-23505: Object "string"."string" is missing. Cause: The specified object does not exist. Action: Check that the specified object is correct. ORA-23514: invalid or incorrect number of arguments Cause: The arguments passed to the online redefinition API were invalid or missing. Action: Call the online redefinition API with the right number of valid arguments. ORA-23515: materialized views and/or their indices exist in the tablespace Cause: An attempt was made to drop a tablespace which contains materialized views and/or their indices. Action: Drop the materialized views in this tablespace. Also, find indices belonging to materialized views in this tablespace and drop then. Then try dropping the tablespace. ORA-23531: site owner already exists in the template. Cause: Site owner for the template already exists. Action: Do not create multiple siteowners for this template. ORA-23532: tables with different synchronization mechanisms are in the same group Cause: Tables belonging to the same replication group were specified to be cached with different synchronization mechanisms. Action: Do not specify different synchronization mechanisms while caching tables belonging to the same replication group. ORA-23533: object "string"."string" can not be cached Cause: An attempt was made to cache an object which is not supported. Action: Do not cache an object which is not supported. ORA-23534: missing column in materialized view container table "string"."string" Cause: After import, the materialized view container table has missing columns. Action: Check if materialized view container table was imported correctly. ORA-23535: instantiating templates from multiple back ends is not allowed. Cause: An attempt was made to set a new non-null back end database for an iAS site. Action: Call dbms_ias_configure.set_back_end_db procedure with null dblink. Then, call the same procedure with the new non-null dblink. ORA-23536: the object "string"."string" is not cached at the middle tier as expected. Cause: The object may have been dropped or renamed at the back end after dbms_ias_inst.start_ias_inst was executed. Action: Check the validity of the object at the back end and retry the instantiation. ORA-23537: function or procedure string is not allowed to be invoked from this site. Cause: This function or procedure is restricted to the backend or middle tier site Action: Connect to the proper site before calling this function or procedure. ORA-23538: cannot explicitly refresh a NEVER REFRESH materialized view ("string") Cause: An attempt was made to explicitly refresh a NEVER REFRESH MV. Action: Do not perform this refresh operation or remove the MV(s) from the list. ORA-23539: table "string"."string" currently being redefined Cause: An attempt was made to redefine a table which is currently involved in an ongoing redefinition. Action: Do not perform this redefinition operation on this table or wait till the ongoing redefinition of the table is completed. ORA-23540: Redefinition not defined or initiated Cause: An attempt was made to continue or complete a redefinition which was not defined or initiated. Action: Define or initiate the redefinition before performing this operation. ORA-23541: tables do not match tables used while defining the redefinition Cause: An attempt was made to continue or complete a redefinition by providing different tables than those used while defining or initiating the redefinition. Action: Repeat this operation and specify the same tables as those that were specified while defining or initiating the redefinition. ORA-23542: dependent object "string"."string" already registered Cause: An attempt was made to register an already registered dependent object to an ongoing redefinition. Action: Do not attempt to register an already registered dependent object to an ongoing redefinition. ///////////////////////////////////////////////////////////////////////////// 23600-23999 Reserved for Log Based Replication PL/SQL packages ///////////////////////////////////////////////////////////////////////////// ORA-23600: cannot create PROPAGATION, string already exists Cause: The propagate_name already exists. Action: Drop the propagate_name usign DROP_PROPAGATEcommand or specify propagate_name. ORA-23601: PROPAGATION_NAME string does not exist Cause: Propagation does not exist. Action: Query DBA_PROPAGATION view to find existing propagation_name ORA-23602: Invalid streams process type string Cause: Specified streams process type is not valid. Action: Specify either capture or apply. ORA-23603: STREAMS enqueue aborted due to low SGA Cause: An attempt to enqueue a STREAMS message was aborted because ORACLE is running low on memory allotted for STREAMS. Action: Either start consuming messages by enabling any STREAMS propagation or apply which might be disabled. An alternative is to allot more memory to STREAMS, which can be done by increasing the streams_pool_size initialization parameter if one was defined or by increasing the shared_pool_size. ORA-23605: invalid value "string" for STREAMS parameter string Cause: An attempt was made to specify an invalid parameter value. Action: Specify a valid value for the parameter. Check the documentation for valid parameter values. ORA-23606: invalid object string Cause: An attempt was made to specify an invalid object. Action: Specify a valid object. ORA-23607: invalid column "string" Cause: An invalid column was specified in the column list. Action: Check the columns in the object and specify the right column name. ORA-23608: invalid resolution column "string" Cause: An invalid column was specified as the resolution column. The resolution column must belong to the list of columns specified in the "column_list" parameter. Action: Check the columns in the column_list and specify the right resolution column name. ORA-23609: unable to find directory object for directory string Cause: There was no entry in ALL_DIRECTORIES corresponding to the specified directory. Action: Grant to the current user appropriate privileges on either a new directory object or an existing directory object. ORA-23610: internal dbms_streams_tablespaces error: [string] [string] [string] [string] Cause: Streams detected an erroneous result. Action: Look for information in the session trace file and contact customer support. ORA-23611: tablespace "string" has more than one data file Cause: The specified tablespace had more than one data file and hence did not qualify as a simple tablespace. Action: Choose a self-contained tablespace with a single data file, or use a procedure that supports any tablespace. ORA-23612: unable to find tablespace "string" Cause: Either the tablespace did not exist, or the current user did not have sufficient privileges on the tablespace. Action: Grant appropriate privileges on the tablespace to the current user or choose a different tablespace. ORA-23613: Script string already exists Cause: A script for the specified invoking package already existed. Action: Complete the previous invocation or drop the previous invocation before proceeding with the current invocation. ORA-23614: Script string does not exist Cause: The named script did not exist. Action: Create the script. ORA-23615: Block number string does not exist for script string Cause: The specified block number did not exist for the script. Action: Add the block or check the block number and reexecute. ORA-23616: Failure in executing block string for script string Cause: The execution of specified block failed. Action: Check the error, rectify and rerun the block or script. ORA-23617: Block string for script string has already been executed Cause: The specified block was already executed. Action: Check the block number and reissue the command. ORA-23618: Generation of script string is not complete. Cause: Script generation for the specified script was not completed in a prior invocation. Action: Purge the specified script by calling the RECOVER_OPERATION API in the package DBMS_STREAMS_ADM and reattempt the entire operation. ORA-23619: non-Oracle system error: string Cause: A non-Oracle database has returned an error message to STREAMS when attempting to apply a DML statement. The non-Oracle system error message is a parameter to this Oracle error. Action: Corrective action may or may not be possible (depending on the non-Oracle system error). If corrective action is possible, correct the problem and try applying the transaction again. ORA-23620: bind value size too large for PL/SQL CALL operation Cause: In a PL/SQL CALL to a stored procedure, the bind string size exceeded 4K. Action: Either make the bind string size shorter (less than 4K) or use BEGIN-END to call the procedure instead of CALL. ORA-23621: Operation corresponding to script string is in progress. Cause: The script was already being run in a different session or was terminated before status for the script was updated to ERROR or EXECUTED. Action: Make sure the script is not being run in a parallel session. Then call the RECOVER_OPERATION API in the DBMS_STREAMS_ADM package with the appropriate OPERATION_MODE argument. ORA-23622: Operation string.string.string is in progress. Cause: An attempt was made to execute a procedure which was being executed in a parallel session or failed execution. Action: Query the DBA_RECOVERABLE_SCRIPT view to identify the operation that is currently in progress for the specified invoking procedure. Complete the operation before proceeding. ORA-24000: invalid value string, string should be of the form [SCHEMA.]NAME Cause: An invalid value was specified for the paramerter. Action: Specify a string of the form [SCHEMA.]NAME . ORA-24001: cannot create QUEUE_TABLE, string already exists Cause: The queue table already exists in the queueing system. Action: Drop the table first using the DROP_QUEUE_TABLE() command or specify another table. ORA-24002: QUEUE_TABLE string does not exist Cause: Queue_table not exist. Action: Query on the user view USER_QUEUE_TABLES to find out existing queue tables. ORA-24003: Queue table index string inconsistent with queue table string Cause: The queue table index has not yet been successfully imported. Action: Import the queue table index before attempting to use the queue table. If the import failed, correct the problem and try to import the queue table index again. ORA-24004: invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY Cause: Invalid column name was specified in the SORT_LIST. Action: The valid column names are ENQ_TIME and PRIORITY. ORA-24005: must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables Cause: An attempt was made to use the SQL command DROP TABLE for queue tables, but DROP TABLE is not supported for queue tables. Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure instead of the DROP TABLE command. ORA-24006: cannot create QUEUE, string already exists Cause: The queue requested to be created already exists. Action: Specify another queue name. Query USER_QUEUES for all the exisiting queues in the users"s schema. ORA-24007: invalid value string, MAX_RETRIES should be non-negative integer Cause: An invalid value was specified for MAX_RETRIES. Action: Specify a non-negative integer. ORA-24008: queue table string.string must be dropped first Cause: An error was detected when dropping a queue table in a cluster, tablespace, or schema. Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the specified queue table first; then, retry the operation. ORA-24009: invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE Cause: Invalid queue type parameter Action: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE for exception queue. ORA-24010: QUEUE string does not exist Cause: The specified queue does not exist. Action: Specify a valid queue. Query USER_QUEUES for all the valid queues. ORA-24011: cannot drop QUEUE, string should be stopped first Cause: The queue has not been stopped i.e. either enqueue or dequeue is still enabled. Action: Stop the queue first using the STOP_QUEUE command and disable it from both enqueueing and dequeueing. ORA-24012: cannot drop QUEUE_TABLE, some queues in string have not been dropped Cause: A queue exists in the queue table which has not been dropped. All queues need to be dropped first. Action: Drop all queues belonging to this queue table using the drop_queue() command. Be sure to stop the queues appropriately before dropping them. Alternately, use the force option in drop_queuetable. ORA-24013: invalid value string, RETRY_DELAY should be non-negative Cause: A negative value was specified for RETRY_DELAY. Action: Specify a non-negative value for RETRY_DELAY. ORA-24014: invalid value string, RETENTION_TIME should be FOREVER or non-negative Cause: Queue retention was specified, but the retention time was specified to be less than zero. Action: Specify the retention time to be non-negative or FOREVER. Alternately don"t specify retention. ORA-24015: cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist Cause: An invalid QUEUE_PAYLOAD_TYPE specified during create_queue_table. Action: The QUEUE_PAYLOAD_TYPE should be RAW or an object type that already exists in the database. ORA-24016: cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string Cause: An invalid object type specified for QUEUE_PAYLOAD_TYPE during create_queue_table. Action: The user should have execute priviliges on the object type specified for the queue. ORA-24017: cannot enable enqueue on QUEUE, string is an exception queue Cause: User tried to enable enqueueing to an exception queue. Action: None. ORA-24018: STOP_QUEUE on string failed, outstanding transactions found Cause: There were outstanding transactions on the queue, and WAIT was set to false, so STOP_QUEUE was unsucessful in stopping the queue. Action: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all outstanding transactions are completed. ORA-24019: identifier for string too long, should not be greater than string characters Cause: The identifier specified is too long. Action: Try again with a shorter identifier. ORA-24020: Internal error in DBMS_AQ_IMPORT_INTERNAL, string Cause: Internal Error occured in the package DBMS_AQ_IMPORT_INTERNAL. Action: Internal error, call Oracle Support. ORA-24021: queue table definition not imported for string.string Cause: The queue definition is not updated because the queue table was not imported properly Action: Import the queue table again. ORA-24022: the specified parameters has no effect on the queue Cause: The parameter combination will not cause the queue to be started or stoped. Action: None. This is just a warning. ORA-24023: Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string] Cause: Internal Error occured in the package DBMS_AQ_EXP_INTERNAL. Action: Internal error, call Oracle Support. ORA-24024: Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string] Cause: Internal Error occured in the package DBMS_AQ_IMP_INTERNAL. Action: Internal error, call Oracle Support. ORA-24025: invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type Cause: Parameter queue_payload_type has invalid value. Action: Specify a valid object type or RAW. ORA-24026: operation failed, queue string.string has errors Cause: An attempt was made to enqueue, dequeue or administer a queue which has errors. Action: Drop the queue table setting the force option to true. ORA-24027: AQ HTTP propagation encountered error, status-code string, string Cause: AQ propagation"s HTTP request to the propagation servlet at the specified address encountered an error Action: Specify a valid address in the connect string of the propagation destination dblink, the dblink user has the correct permissions, check if the AQ propagation servlet was properly installed. ORA-24028: cannot create a reciever non-repudiable single consumer queue Cause: Tried to create a reciever non-repudiable single consumer queue Action: This feature is not supported ORA-24029: operation not allowed on a single-consumer queue Cause: Tried an operation not allowed on a single-consumer queue. Action: Specify the operation on a multi-consumer queue. ORA-24030: Only one of rule or rule-set must be specified Cause: Specified both a rule and rule-set for the operation. Action: Specify only one of rule or rule-set. ORA-24031: invalid value, string should be non-NULL Cause: Parameter is NULL. Action: Specify a non NULL value for the parameter. ORA-24032: object string exists, index could not be created for queue table string Cause: Oracle AQ tried to create an index with the name specified in the error message. The index could not be created for the specified queue table because a object exists with the same name. Action: Drop the object specified in the error message and retry the command. You can also choose a different name for the queue table. ORA-24033: no recipients for message Cause: An enqueue was performed on a queue that has been set up for multiple dequeuers but there were neither explicit recipients specified in the call nor were any queue subscribers determined to be recipients for this message. Action: Either pass a list of recipients in the enqueue call or add subscribers to the queue for receiving this message. ORA-24034: application string is already a subscriber for queue string Cause: An application name that was already a subscriber for the queue was specified in the dbms_aq.subscribe call. Action: none ORA-24035: AQ agent string is not a subscriber for queue string Cause: An AQ agent that was not a subscriber for the queue was specified. Action: Check the name and/or address of the agent and retry the call. ORA-24036: invalid SORT_ORDER column string specified for queue table Cause: The create queue table command was issued with message_grouping set to TRANSACTIONAL and a sort order column other than priority. Only the priority column can be specified in the sort order for queue tables with transactional grouping. Action: Change the sort order list in the create queue table command and retry the call. ORA-24037: schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE is not the same as the schema specified in the QUEUE_TABLE parameter. Action: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE parameters and retry the command. ORA-24038: RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers and with COMPATIBLE parameter set to "8.0". Action: Either set the RETRY_DELAY to zero or upgrade the queue table to 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. ORA-24039: Queue string not created in queue table for multiple consumers Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure, or an ENQUEUE with a non-empty recipient list, was issued on a queue that was not created for multiple consumers. Action: Create the queue in a queue table that was created for multiple consumers and retry the call. NLS_DO_NOT_TRANSLATE [24040,24040] ORA-24041: propagation schedule exists for QUEUE string and DESTINATION string Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair which has an existing propagation schedule. Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and then reissue the SCHEDULE_PROPAGATION call. ORA-24042: no propagation schedule exists for QUEUE string and DESTINATION string Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination pair which has no existing propagation schedule. Action: Verify the spelling of the specified QUEUE and DESTINATION and then reissue the call with the correct spelling. ORA-24043: destination string uses a reserved name, names with AQ$_ prefix are not valid Cause: An attempt was made to specify a reserved name for a destination. Action: Enter a different value or NULL for the local destination. Then retry the operation. ORA-24044: source string and destination string object types do not match Cause: A message recipient"s queue has a different object structure than the sender"s queue. The message cannot be propagated. Action: Either remove the recipient from the subscriber"s list for the sender"s queue or create the destination queue with an object type that matches the source queue"s object type. ORA-24045: invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK] Cause: An invalid value was specified for the agent address parameter. Action: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK]. ORA-24046: protocol attribute reserved for future use Cause: The protocol attribute of the AQ agent object type is reserved for future use. Action: Do not specify the protocol attribute in the agent object type. ORA-24047: invalid agent name string, agent name should be of the form NAME Cause: An invalid value was specified for the agent name parameter. Action: Specify a string of the form NAME. Then retry the operation. ORA-24048: cannot create QUEUE_TABLE, user does not have access to AQ object types Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but the user who issued the command does not have access to internal AQ object types. Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the user access to the AQ object types. ORA-24049: invalid agent name string, names with AQ$_ prefix are not valid Cause: An attempt was made to use a reserved prefix in the agent name. Action: Enter a different value for the agent name. Then, retry the operation. ORA-24050: subscribers are not supported for exception queue string Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure was issued on a queue that was created as an EXCEPTION_QUEUE. Action: Specify a NORMAL_QUEUE in the procedure. ORA-24051: cannot propagate object type payloads that have a REF attribute Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address field in the agent type was issued on a queue whose payload has a REF attribute. Propagation of object type payloads that have a REF attribute currently is not supported. Action: Specify an agent with a NULL address field so that the agent can dequeue from the same queue. Or, change the object type definition to one that does not use REF attributes. ORA-24052: cannot propagate object type payloads with LOB attributes to an 8.0 release Cause: The recipient of a message with LOB attributes was using an Oracle 8.0 release. Propagation of LOB attributes is supported only in Oracle 8.1 and higher releases. Action: Upgrade the target release to Oracle 8.1 and retry. Or, change the object type definition to one that does not use LOBs. ORA-24053: PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative. Action: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE. ORA-24054: cannot propagate to an Oracle 8.0.3 release or lower release Cause: The recipient of a message was using an Oracle 8.0.3 release or lower release. Propagation is supported only in Oracle 8.0.4 and higher releases. Action: Upgrade the target release to Oracle 8.0.4 or higher and retry. ORA-24055: cannot delete propagation status rows that are in prepared state Cause: An attempt was made to use the internal administration procedure to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in the prepared state. Action: Wait for the propagation to complete successfully before retrying the operation. ORA-24056: internal inconsistency for QUEUE string and destination string Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table were inconsistent for the given queue and destination. Action: Contact Oracle Worldwide Support. ORA-24057: cannot define subscriber with rule for queue string Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was issued on a queue for which rule based subscribers are not supported. Rule based subscribers currently are supported only for NORMAL (persistent) multi-consumer queues created using an Oracle release 8.1.0 or higher compatible queue table. Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 or higher compatible queue table, and retry the call. Or, if the queue is a normal (persistent) multi-consumer queue, convert the queue table to Oracle 8.1.0 or higher compatibility and retry. ORA-24058: cannot downgrade QUEUE_TABLE that has propagation in a prepared state Cause: An attempt was made to downgrade the queue table when there were messages being propagated that were in the prepared state. Action: Wait for the propagation to complete before retrying the operation. ORA-24059: invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string Cause: An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting must be of the form "8.x.y" where x is the release number and y is the update number. Action: Specify a valid COMPATIBLE parameter setting, and retry the operation. ORA-24060: cannot convert QUEUE_TABLE, string already is compatible with release string Cause: The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting. Action: Choose a different COMPATIBLE parameter setting to convert the queue table to the desired compatibility. ORA-24061: cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero Cause: A non-zero value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was zero. Action: Specify a non-zero primary instance before you specify a non-zero secondary instance. ORA-24062: Subscriber table string inconsistent with queue table string Cause: The subscriber table has not yet been successfully imported. Action: Import the subscriber table before attempting to use the queue table. If the import failed, correct the problem and try to import the subscriber table again. ORA-24063: cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers Cause: An attempt was made to downgrade the queue table when there were queues on which rule based subscribers are defined. Action: Remove the rule based subscribers for all queues in this queue table and retry. ORA-24064: propagation for QUEUE string and DESTINATION string already enabled Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was enabled. Action: Make sure the QUEUE and DESTINATION are correct when you issue the ENABLE_SCHEDULE_PROPAGATION command. ORA-24065: propagation for QUEUE string and DESTINATION string already disabled Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was disabled. Action: Make sure the QUEUE and DESTINATION are correct when you issue the DISABLE_SCHEDULE_PROPAGATION command. ORA-24066: invalid privilege specified Cause: An invalid privilege is specified for granting or revoking privilege Action: Specify a valid privilege. ORA-24067: exceeded maximum number of subscribers for queue string Cause: An attempt was made to add new subscribers to the specified, but the number of subscribers for this queue has exceeded the maximum number (1024) of subscribers allowed per queue. Action: Remove existing subscribers before trying to add new subscribers. ORA-24068: cannot start queue string, queue table string is being migrated Cause: An attempt was made to start a queue in a queue table that is being migrated. Action: Complete the queue table migration, and retry the operation. ORA-24069: cannot downgrade queue table string while it is being upgraded Cause: An attempt was made to downgrade a queue table, but a previous command to upgrade the queue table has not yet completed successfully. Action: Complete the upragde of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade the queue table. ORA-24070: cannot upgrade queue table string while it is being downgraded Cause: An attempt was made to upgrade a queue table, but a previous command to downgrade the queue table has not yet completed succesfully. Action: Complete the downgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the queue table. ORA-24071: cannot perform operation string, queue table string is being migrated Cause: An attempt was made to perform an operation on a queue in a queue table that is being migrated. Action: Complete the queue table migration, and retry the operation. ORA-24072: cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table Cause: An attempt was made to upgrade or downgrade a queue table using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who executed the procedure does not own the queue. Action: Reconnect as the owner of the queue table, and then execute the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. ORA-24073: cannot specify RETENTION_TIME on exception queue string.string Cause: An attempt was made to create or alter an exception queue by specifying a non-zero RETENTION_TIME. Action: Use the default RETENTION_TIME parameter value for exception queues. ORA-24074: RETRY_DELAY and MAX_RETRIES cannot be used for exception queue %.string Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and an exception queue. Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues. ORA-24075: cannot specify agent with NULL address and non-NULL protocol Cause: An ADD_SUBSCRIBER or enqueue was attemoted with an agent that had a NULL address and a non-NULL protocol. Action: Either specify a non-NULL address or set the protocol to NULL. ORA-24076: cannot perform operation string for NON_PERSISTENT queue string.string Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue. Action: Do not specify a NON_PERSISTENT queue for these operations. ORA-24077: cannot create propagation schedule for EXCEPTION queue string.string Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Propagation schedules can be created only for NORMAL queues. Action: To propagate messages from a queue specify the queue type as NORMAL. ORA-24078: cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL Cause: A non-NULL value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was NULL. Action: Specify a non-NULL primary instance before you specify a non-NULL secondary instance. ORA-24079: invalid name string, names with AQ$_ prefix are not valid for string Cause: An attempt was made to use a reserved prefix for the object name. Action: Enter a different name for this object. Then, retry the operation. ORA-24080: unschedule_propagation pending for QUEUE string and DESTINATION string Cause: A propagation administration command was issued for a queue and destination pair whose propagation is being unscheduled. Action: Do not issue propagation administration commands for a propagation schedule on which there is a pending unschedule request. ORA-24081: compatible parameter needs to be string or greater Cause: The compatible parameter was not high enough to allow the operation. Action: shutdown and startup with a higher compatibility setting. ORA-24082: propagation may still be happening for the schedule for QUEUE string and DESTINATION string Cause: The snapshot process executing the propagation schedule did not respond to the disable propagation command. Action: Make sure that the job for the propagation schedule has been ended. ORA-24083: cannot specify remote subscribers for string QUEUE string Cause: An add_subscriber call with a non-null address field was issued on a queue which does not support remote subscribers. Remote subscribers are not supported for NON_PERSISTENT QUEUES. Action: Specify a null address field and retry the call. ORA-24084: DBLINK name in address field of agent string is not unique within the first 24 bytes Cause: Advanced Queuing requires that the agent"s dblink name should be unique within the first 24 bytes (for 8.0 compatible queuetables) Action: Specify a dblink name that is unique within the first 24 bytes or migrate to 8.1 compatible queuetables where this restriction is not there. ORA-24085: operation failed, queue string is invalid Cause: An attempt was made to enqueue, dequeue or administer a queue which is invalid. This could have occured because the payload type of the queue"s queue table was dropped. Action: Drop the queue table setting the force option to true. ORA-24086: cannot create a 8.0 compatible string queue Cause: An attempt was made to create a 8.0 compatible queue table and enable a feature that is supported only on 8.1 style queue tables Action: This feature is not supported ORA-24087: Invalid database user string Cause: An invalid database username was specified Action: Specify a valid database user ORA-24088: AQ Agent string does not exist Cause: This AQ Agent does not exist Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view for a list of valid aq agents ORA-24089: AQ Agent string already exists Cause: This AQ agent has already been created Action: Specify another agent name or use the ALTER api to modify the agent information. ORA-24090: at least one protocol must be enabled Cause: No protocol was enabled for aq agent Action: Enable one of the protocols by setting one of the enable parameters to true. ORA-24091: Destination queue string is the same as the source queue Cause: Propagation cannot be scheduled when the destination queue is the same as the source queue. Action: Specify a different destination queue. ORA-24092: invalid value string specified Cause: A queue, queue table, rule, or ruleset name that requires double quotes was specifed when the database compatibility was less than 10.0. Action: Specify a value that does not require double quotes and retry the operation. ORA-24093: AQ agent string not granted privileges of database user string Cause: The specified AQ agent does not have privileges of the specified database user Action: Specify a valid combination of AQ agent and database user. Check the DBA_AQ_AGENT_PRIVS or USER_AQ_AGENT_PRIVS view for user/agent mappings ORA-24094: invalid transformation, target type does not match that of the queue Cause: The target type of the transformation specified was different from the type of the queue. Action: Provide a valid transformation whose target type is the same as the queue type. ORA-24095: invalid transformation, source type does not match that of the queue Cause: The source type of the transformation specified was different from the type of the queue. Action: Provide valid transformation whose source type is the same as the queue type. ORA-24096: invalid message state specified Cause: Invalid value is specified for message state Action: Provide a valid message state as specified in the documentation ORA-24097: Invalid value string, string should be non-negative Cause: A negative value or NULL was specified for the parameter. Action: Specify a non negative integer. ORA-24098: invalid value string for string Cause: An Invalid value or NULL was specified for the parameter. Action: Check the documentation for valid values. ORA-24099: operation not allowed for 8.0 compatible queues Cause: The specified operation is only supported for queues with compatibility 8.1 or greater Action: Upgrade the 8.0 compatible queue to release 8.1 using DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with compatibility 8.1 ORA-24100: error in ktz testing layer Cause: There is an error in the Transaction layer test ICDs Action: none ORA-24101: stopped processing the argument list at: string Cause: One of the arguments of the requested operation contained a list of scheduler objects. While processing this list an error was encountered with the specified item. Action: Resolve the error for this element of the list and then re-issue the command with the remainder of the argument list. See the rest of the error stack to find out what the exact error is. ORA-24102: invalid prefix for generate_job_name Cause: generate_job_name was called with a prefix longer than 18 characters or a prefix ending in a digit. Action: Re-issue the command using a prefix no longer than 18 characters and not ending in a digit. ORA-24120: invalid string parameter passed to DBMS_REPAIR.string procedure Cause: An invalid parameter was passed to the specified DBMS_REPAIR procedure. Action: Specify a valid parameter value or use the parameter"s default. ORA-24121: both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure Cause: Both cascade and a block range were specified in a call to DBMS_REPAIR.CHECK_OBJECT. Action: Use either cascade or a block range, or do not use either one. ORA-24122: invalid block range specification Cause: An incorrect block range was specified. Action: Specify correct values for the BLOCK_START and BLOCK_END parameters. ORA-24123: feature string is not yet implemented Cause: An attempt was made to use the specified feature, but the feature is not yet implemented. Action: Do not attempt to use the feature. ORA-24124: invalid ACTION parameter passed to DBMS_REPAIR.string procedure Cause: An invalid ACTION parameter was specified. Action: Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION parameter. ORA-24125: Object string.string has changed Cause: An attempt was made to fix corrupt blocks on an object that has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run. Action: Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table and run DBMS_REPAIR.CHECK_OBJECT to determine whether there are any corrupt blocks to be fixed. ORA-24126: invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure Cause: CASCADE_FLAG was specified for an object that is not a table. Action: Use CASCADE_FLAG only for tables. ORA-24127: TABLESPACE parameter specified with an ACTION other than CREATE_ACTION Cause: The TABLESPACE parameter can only be used with CREATE_ACTION. Action: Do not specify TABLESPACE when performing actions other than CREATE_ACTION. ORA-24128: partition name specified for a non-partitioned object Cause: A partition name was specified for an object that is not partitioned. Action: Specify a partition name only if the object is partitioned. ORA-24129: table name string does not start with string prefix Cause: An attempt was made to pass a table name parameter without the specified prefix. Action: Pass a valid table name parameter. ORA-24130: table string does not exist Cause: An attempt was made to specify a map, repair, or sync table that does not exist. Action: Specify a valid table name parameter. ORA-24131: table string has incorrect columns Cause: An attempt was made to specify a map, repair, or sync table that does not have a correct definition. Action: Specify a table name that refers to a properly created table. ORA-24132: table name string is too long Cause: An attempt was made to specify a table name is greater than 30 characters long" Action: Specify a valid table name parameter. ORA-24141: rule set string.string does not exist Cause: An attempt to access or modify a ruleset was made, which failed because the ruleset does not exist. Action: Only access or modify existing rulesets. ORA-24142: invalid ruleset name Cause: An attempt to create a ruleset with an invalid name was made. The ruleset name can not be NULL, and can not be more than 26 characters, unless a rules_table_name is also specified, in which case the ruleset name may be up to 30 characters. Action: Retry the create with a valid ruleset name. ORA-24143: invalid evaluation context name Cause: An attempt to create a rule/ruleset on an invalid evaluation name was made. The evaluation_context can not be more than 30 characters. The evaluation context with the name specified must exist. Action: Retry the create with a valid evaluation context name. ORA-24144: rules engine internal error, arguments: [string], [string] Cause: An internal error occurred in the rules engine. This indicates that the rules engine has encountered an exception condition. Action: Please report this error as a bug. The first argument is the error and the second argument is the package. ORA-24145: evaluation context string.string already exists Cause: An evaluation context of the given name already exists Action: Specify another name for the evaluation context being created ORA-24146: rule string.string already exists Cause: A rule of the given name already exists Action: Specify another name for the rule being created. ORA-24147: rule string.string does not exist Cause: The rule of the given name does not exist Action: create the rule or specify one that exists ORA-24148: cannot drop rule string.string with dependents Cause: The rule still belongs to some rulesets, cannot be dropped Action: do not drop a rule that belongs to rulesets without force option ORA-24149: invalid rule name Cause: An attempt to create a rule with an invalid name was made. The rule name can not be NULL, and can not be more than 30 characters Action: none ORA-24150: evaluation context string.string does not exist Cause: The evaluation context of the given name does not exist Action: create the evaluation context or specify one that exists ORA-24151: no evaluation context is associated with rule string.string or rule set string.string Cause: Whening adding a rule to a rule set, either the rule or the rule set must have an evaluation context associated with it Action: do not add a rule without an evaluation context to a ruleset that does not have a default evaluation context ORA-24152: cannot drop evaluation context string.string with dependents Cause: The evaluation context still belongs to some rules or rule sets, cannot be dropped Action: do not drop an evaluation context with dependents without force option ORA-24153: rule set string.string already exists Cause: A rule set of the given name already exists Action: Specify another name for the rule set being created. ORA-24154: rule string.string already in rule set string.string Cause: a rule can be added to a rule set only once Action: do not add a rule to a rule set that already contains this rule ORA-24155: rule string.string not in rule set string.string Cause: the rule to be removed from the rule set is not in the rule set Action: do not remove a rule from a rule set that does not contain the rule ORA-24156: duplicate table alias string Cause: there is a table alias of the same name in the evaluation context Action: do not add two table aliases of the same name to an evaluation context ORA-24157: duplicate variable name string Cause: there is a variable of the same name in the evaluation context Action: do not add two variables of the same name to an evaluation context ORA-24158: invalid table alias Cause: table alias name or base table name is not specified in the table alias definiton Action: specify both alias name and alias base table in the table alias structure ORA-24159: invalid variable definiton Cause: variable name or variable type is not specified in the variable definiton Action: specify both variable name and variable type in the variable definition structure ORA-24160: name string already exists in the name value pair list Cause: there is already a name-value pair with the same name in the NVlist Action: try another name. ORA-24161: name string does not exist in the name value pair list Cause: there is not such a name-value pair in the NVlist Action: check the name-value pair exists in the NVList. ORA-24162: name value pair list is full, cannot add another entry Cause: The NVList is full (1024 elements) and cannot hold more elements Action: do not add elements to a full list. ORA-24163: dblink is not supported in rules engine DDLs Cause: the object name has a database link in it, which is not supported Action: Do not specify remote objects in rules engine DDLs. ORA-24164: invalid rule engine system privilege: string Cause: no such system privilege number for rule engine objects Action: check specfication of dbms_rule_adm for valid system privilege numbers ORA-24165: invalid rule engine object privilege: string Cause: no such object privilege number for rule engine objects Action: check specfication of dbms_rule_adm for valid object privilege numbers ORA-24166: evaluation context string.string has errors Cause: cannot resolve the table aliases and the variable types specified in the evaluation context Action: make sure all base tables exist and all variable types correct ORA-24167: incompatible rule engine objects, cannot downgrade Cause: there are rule engine objects in the database that cannot be downgraded. Action: check utlincmp.sql and remove all incompatible rules engine objects before downgrade. ORA-24168: rule string.string cannot have default evaluation context Cause: If a rule is added to a rule set with more than one evaluation contexts, it must not have an evaluation context itself. Action: Do not set the evaluation context of such rules to a not-null value ORA-24169: rule condition has unrecognized variables Cause: The rule references variables not in the evaluation context. Action: Modify the rule condition to remove illegal reference. ORA-24170: %s.string is created by AQ, cannot be dropped directly Cause: This object is created by AQ, thus cannot be dropped directly Action: use dbms_aqadm.drop_subscriber to drop the object ORA-24171: creation properties are only for internal use Cause: user specified not null creation properties when creating rules engine objects, which are not for external use Action: do not set creation properties when creating rules engine objects ORA-24172: rule set string.string has errors Cause: The rule references variables not in the evaluation context. Action: Modify the rule condition to remove illegal reference. ORA-24173: nested query not supported for rule condition Cause: user specified nested query in rule condition. Action: do not use nested query in rule condition. ORA-24180: invalid transformation expression, the transformation expression does not evaluate to the target type/attribute Cause: The transformation expression does not evaluate to the target type or the target type"s specified attribute. Action: Provide valid transformation expression which evaluates to the target type or the target type"s specified attribute. ORA-24181: The type string does not exist Cause: The source or destination type for the transformation does not exist Action: Create the type or specify one that exists ORA-24182: attribute number specified does not exist Cause: The target type of the transformation does not have the attribute number specified in the ADD_ATTRIBUTE_TRANSFORMATION command Action: check the target type definition and specify a valid attribute number ORA-24183: invalid transformation Cause: The transformation specified is invalid because the source or the target type have been dropped/modified. Action: Drop and recreate the transformation ORA-24184: transformation string.string already exists Cause: The named transformation already exists. Action: Specify another name for the transformation being created. ORA-24185: transformation string.string does not exist Cause: The specified transformation does not exist. Action: Create the transformation before using it or specify an existing transformation. ORA-24186: wrong object type, could not transform message Cause: The object type of the message to be transformed does not match the source type of the specified transfomation. Action: Specify another transformation, or specify a message of the correct type. ORA-24190: length of payload exceeds string Cause: the length of payload being taken exceeds the limit of varchar2 or raw. Action: use clob type or blob type to call get_text or get_bytes. ORA-24191: the property name string has existed Cause: the property name being set has existed. Action: use another property name. ORA-24192: the property name cannot be null Cause: the property name cannot be null. Action: make sure the property name not null. ORA-24193: the property value exceeds the valid range string Cause: the property valus being set exceeds the valid range. Action: make sure the property value is within the valid range. ORA-24194: attempt to read data in a message as the wrong type Cause: According to JMS specification, some type conversions were not allowed. Action: Make sure to use the correct READ function to retrieve message data. ORA-24195: attemp to retrieve the name list of a map message with size exceeding 1024 Cause: The GET_NAMES function returns the names in a varray with a size limit of 1024. Action: Retrieve in several smaller steps using the GET_NAMES function with OFFSET and LENGTH parameters. ORA-24196: access the message in a wrong access mode Cause: StreamMessage and BytesMessage could not be read when they were in write only mode and vice versa. Action: Change the access mode using PREPARE, CLEAR_BODY and RESET procedures. ORA-24197: JAVA stored procedure throws JAVA exceptions Cause: The JAVA stored procedure threw some exceptions that could not be catergorized. Action: Use GET_EXCEPTION procedure to see what the exception is about. ORA-24198: attempt to use an invalid operation ID Cause: An attempt was made to use an invalid operation ID to access messages. Action: Use the correct operation ID returned by PREPARE or CLEAR_BODY procedure. ORA-24199: message store is overflow Cause: An attemp was made to access too many messages at the same time. Action: Use the CLEAN procedure to clean up some of the messages. ORA-24201: duplicate publisher, publisher already added to the queue Cause: Attempted to add a publisher to the queue again. Action: Specify another publisher or user DBMS_AQADM.ALTER_PUBLISHER to alter the publisher"s properties. ORA-24202: publisher does not exist for the queue Cause: Attempted to alter or drop a non existent publisher from a queue. Action: Specify another publisher. ORA-24203: operation failed, queue table string.string has errors Cause: An operation attempt was made to a queue table which has errors. Action: Drop the queue table setting the force option to true. ORA-24230: input to DBMS_DDL.WRAP is not a legal PL/SQL unit Cause: The input supplied to DBMS_DDL.WRAP or DBMS_DDL.CREATE_WRAPPED did not specify a legal PL/SQL package specification, package body, type specification, type body, function or procedure. This error can occur if you used incorrect syntax in the CREATE OR REPLACE statement or specified a unit that cannot be wrapped (e.g., a trigger or anonymous block). Action: Provide a legal PL/SQL unit as input. ORA-24231: database access descriptor (DAD) string not found Cause: The specified Database Access Descriptor (DAD) did not exist. Action: Make sure the name of the Database Access Descriptor (DAD) is correct and the DAD exists. ORA-24232: unknown Embedded PL/SQL Gateway attribute string Cause: The specified Embedded PL/SQL Gateway attribute was not known. Action: Make sure the name of the Embedded PL/SQL Gateway attribute is correct. ORA-24233: argument passed to DBMS_UTILITY.VALIDATE is not legal Cause: One or more input arguments to the DBMS_UTILITY.VALIDATE routine was not legal. This error occurred because the object name or owner or namespace arguments (if specified) were NULL or illegal. Action: Identify and correct the illegal argument. ORA-24234: unable to get source of string "string"."string", insufficient privileges or does not exist Cause: The specified PL/SQL object in a DBMS_PREPROCESSOR subprogram did not exist or you did not have the privileges necessary to view its source. Action: Make sure the specified object exists and you have the privileges necessary to view its source. ORA-24235: bad value for object type: string Cause: The specified object type was not appropriate. Action: Make sure the specified object type is one of the following: package, package body, procedure, function, trigger, type, and type body. ORA-24236: source text is empty Cause: The input source text supplied to a DBMS_PREPROCESSOR subprogram was empty. Action: Pass a non-empty input source text as the input. ORA-24237: object id argument passed to DBMS_UTILITY.INVALIDATE is not legal Cause: This error occurred because the p_object_id argument passed to the DBMS_UTILITY.INVALIDATE routine was NULL, there was no object with the specified object id, or the user calling the routine did not have sufficient privileges to invalidate the object. Action: Correct the illegal argument. ORA-24238: object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal Cause: This error occurred because the p_plsql_object_settings argument passed to the DBMS_UTILITY.INVALIDATE routine was NULL or malformed. Action: Correct the illegal argument. ORA-24239: object could not be invalidated Cause: A call to the DBMS_UTILITY.INVALIDATE routine failed. This error occurred because the object type of the object specified by the p_object_id argument is not one of the types that can be handled by this routine. Alternately, the object was an object type specification with table dependents, or the object was the specification of the STANDARD, DBMS_STANDARD, DBMS_UTILITY package, or the body of the DBMS_UTILITY package. Action: Call DBMS_UTILITY.INVALIDATE only on supported object types. ORA-24240: invalid database access descriptor (DAD) name Cause: The specified Database Access Descriptor (DAD) name was invalid. Action: Make sure the name of the Database Access Descriptor (DAD) is valid and its length does not exceed its limit. ORA-24265: Insufficient privileges for SQL profile operation Cause: A DDL operation was attempted on a SQL profile by a session without the proper privileges. Action: Grant the user the appropriate privilege. ORA-24270: a row already exists in the string table for these parameters Cause: A call was made to create a new row in the specified table. A row already exists in the table with the specified values. Action: Delete the existing row using the appropriate API or check the parameters used to create the row. ORA-24271: translation type must be either T, S or M Cause: The translation type parameter is not a T, S or an M. A value other than T, S or M was specified. Action: Correct the translation type and reexecute the API call. ORA-24272: initialization value must be either F or T Cause: The initialization value must be either F or T. A value other than F or T was specified. Action: Correct the initialization value and reexecute the API call. ORA-24273: translation text is required if translation type is T or S Cause: If a translation type of T or S is specified, translation text must be supplied. Action: Provide translation text and reexecute the API call. ORA-24274: no row exists in the string table for these parameters Cause: A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist. Action: Create the row using the appropriate API or check the parameters used to create the new row to ensure that all specified values exist. ORA-24275: function "string" parameter "string" missing or invalid Cause: The function was called with a parameter that was null, 0 length, or had an invalid value. Action: Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation. ORA-24276: function "string" output "string" maximum value exceeded Cause: The function computed a value for the output that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype. Action: Correct the input values to produce a result that will comply with the limits as specified in the documentation. 15 ORA-24280 to ORA-28674 ORA-24280: invalid input value for parameter string Cause: The parameter has been provided a negative, out of range, or NULL input value. Action: Correct the input value such that it is valid, and is within the range as specified in the documentation. ORA-24281: invalid access past the maximum size of LOB parameter string Cause: The value of positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes. Action: Correct the input values for amount and offset such that their sum is less than or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping conditions and/or offset increments. ORA-24292: no more tables permitted in this sorted hash cluster Cause: A sorted hash cluster only supports a maximum of 2 tables Action: none ORA-24295: max key length (string) for sorted hash cluster exceeded Cause: Sorted hash clusters have a maximum key size Action: none ORA-24300: bad value for mode Cause: An undefined mode value was specified. Action: Check that the correct mode is selected and that an allowed value for that mode is specified. ORA-24301: null host specified in thread-safe logon Cause: An HDA was not specified in the logon call while running in a thread safe environment. Action: Make sure that HDA is not NULL when calling the logon routine. ORA-24302: host connection in use by another thread Cause: An attempt was made to use the host connection while it was in use by another thread. Action: Wait for another thread to finish before using this connection. ORA-24303: call not supported in non-deferred linkage Cause: One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred. Action: Use this call in deferred mode of linkage. ORA-24304: datatype not allowed for this call Cause: Data of this datatype cannot be sent or fetched in pieces. Action: Use other bind or define calls for this datatype. ORA-24305: bad bind or define context Cause: The call was executed on a cursor for which this is invalid. Action: Verify that this call is valid for this cursor. For example, Get piece information and set piece information are valid on a cursor if appropriate binds and defines have been done on this cursor. ORA-24306: bad buffer for piece Cause: A zero length buffer or a null buffer pointer was provided. Action: Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column. ORA-24307: invalid length for piece Cause: The length of the piece exceeded the maximum possible size. Action: Verify that the length of this piece and the cumulative length of all the previous pieces is not more than the desired value supplied by the application. ORA-24308: illegal define position Cause: Call to modify attributes was done for a non-existent position Action: Verify that a define has been done for this position ORA-24309: already connected to a server Cause: This server handle is already attached to a server. Action: Disconnect from the server and then retry the call to establish a connection. ORA-24310: length specified for null connect string Cause: The connect string is null, but a length was specified for it. Action: Set length to zero if connect string is null. ORA-24311: memory initialization failed Cause: Cannot initialize user memory. Action: Contact customer support. ORA-24312: illegal parameters specified for allocating user memory Cause: An illegal size or null pointer was specified for user memory. Action: Specify a legal size and a valid pointer for user memory. ORA-24313: user already authenticated Cause: A user has already been authenticated on this service handle. Action: Terminate the service context before using it for another user. ORA-24314: service handle not initialized Cause: The server context does not done exist. Action: Establish the server context in the service context. ORA-24315: illegal attribute type Cause: An illegal attribute type was specified for the handle. Action: Consult user manual to specify an attribute valid for this handle. ORA-24316: illegal handle type Cause: An illegal handle type was specified. Action: Consult user manual to specify a valid handle type. ORA-24317: define handle used in a different position Cause: A define was done with an existing handle on a different position. Action: Specify the same position as before on a re-define. ORA-24318: call not allowed for scalar data types Cause: This call is valid only for object types. Action: Verify that the data-type for this variable is an object type ORA-24319: unable to allocate memory Cause: Process was unable to allocate memory to store diagnostics. Action: Terminate other processes in order to reclaim needed memory. ORA-24320: unable to initialize a mutex Cause: An attempt to initialize a mutex failed. Action: Contact customer support. ORA-24321: inconsistent parameters passed Cause: One of the three memory function pointers is null or non-null. Action: Verify that either all the memory functions are null or non-null. ORA-24322: unable to delete an initialized mutex Cause: An attempt to delete an initialized mutex failed. Action: Contact customer support. ORA-24323: value not allowed Cause: A null value or a bogus value was passed in for a mandatory parameter. Action: Verify that all mandatory parameters are properly initialized. ORA-24324: service handle not initialized Cause: An attempt was made to use an improper service context handle. Action: Verify that the service context handle has all the parameters initialized prior to this call. ORA-24325: this OCI operation is not currently allowed Cause: An attempt was made to use a context handle outside its scope. Action: Verify that the context handle is set to a service context handle that has been converted to a logon data area for other OCI calls. The logon data area must be converted back to a service context before it can be used. ORA-24326: handle passed in is already initialized Cause: An attempt was made to pass an initialized handle. Action: Verify that the parameter passed in to retrieve a handle does not already point to a handle. ORA-24327: need explicit attach before authenticating a user Cause: A server context must be initialized before creating a session. Action: Create and initialize a server handle. ORA-24328: illegal attribute value Cause: The attribute value passed in is illegal. Action: Consult the users manual and specify a legal attribute value for the handle. ORA-24329: invalid character set identifier Cause: The character set identifier specifed is invalid Action: Specify a valid character set identifier in the OCI call. ORA-24330: internal OCI error Cause: An internal OCI error has occurred. Action: Please contact Oracle customer support. ORA-24331: user buffer too small Cause: The user buffer to contain the output data is too small. Action: Specify a bigger buffer. ORA-24332: invalid object type Cause: An invalid object type is requested for the describe call. Action: Specify a valid object type to the describe call. ORA-24333: zero iteration count Cause: An iteration count of zero was specified for the statement Action: Specify the number of times this statement must be executed ORA-24334: no descriptor for this position Cause: The application is trying to get a descriptor from a handle for an illegal position. Action: Check the position number. ORA-24335: cannot support more than 1000 columns Cause: The number of columns exceeds the maximum number supported. Action: none ORA-24336: invalid result set descriptor Cause: The result set descriptor should have valid data fetched into it before it can be converted to a statement handle Action: Fetch valid data into the descriptor before attempting to convert it into a statement handle ORA-24337: statement handle not prepared Cause: A statement cannot be executed before making preparing a request. Action: Prepare a statement before attempting to execute it. ORA-24338: statement handle not executed Cause: A fetch or describe was attempted before executing a statement handle. Action: Execute a statement and then fetch or describe the data. ORA-24339: cannot set server group name after connecting to server Cause: An attempt was made to set the server group in a server handle after connecting to the server. However, once the connection is established to a server, the server group name cannot be set anymore. Action: Attach to the server after setting the server group name in the server handle. ORA-24340: cannot support more than 255 columns Cause: The number of columns exceeds maximum supported by the server. Action: Limit your operation to 255 columns. ORA-24341: bad mode specified Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client. Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been specified at process initialization. ORA-24342: unable to destroy a mutex Cause: An attempt to destroy a mutex failed. Action: none ORA-24343: user defined callback error Cause: The only valid return value for a user defined callback function is OCI_CONTINUE or OCI_ROWCBK_DONE. Any other value will cause this error. Action: Please insure that OCI_CONTINUE or OCI_ROWCBK_DONE is returned from the user defined callback function. ORA-24344: success with compilation error Cause: A sql/plsql compilation error occurred. Action: Return OCI_SUCCESS_WITH_INFO along with the error code ORA-24345: A Truncation or null fetch error occurred Cause: A truncation or a null fetch error" Action: Please ensure that the buffer size is long enough to store the returned data. ORA-24346: cannot execute without binding variables Cause: None of the bind variables in the SQL statement are bound. Action: Please bind all the variables before the execute is done. ORA-24347: Warning of a NULL column in an aggregate function Cause: A null column was processed by an aggregate function Action: An OCI_SUCCESS_WITH_INFO is returned. ORA-24348: Update or Delete without Where Cause: An update or delete was executed without where clause Action: An OCI_SUCCESS_WITH_INFO is returned. ORA-24350: OCI call not allowed Cause: OCI used is not permitted from external procedures. Action: Refer to user manual for usage restrictions. ORA-24351: invalid date passed into OCI call Cause: A bad date was passed into one of the OCI calls. Action: Check your date bind values and correct them. ORA-24352: invalid COBOL display type passed into OCI call Cause: A bad COBOL display type was passed into one of the OCI calls. Action: Check your COBOL display type bind values and correct them. ORA-24353: user buffer too small to accommodate COBOL display type Cause: User supplied buffer for a COBOL display type was too small to accommodate fetched number. Action: Increase the allocation for COBOL display type buffer. ORA-24354: number fetched too large to fit in COBOL display type buffer. Cause: The number fetched was beyond the range that can be displayed. Action: Please check the number in the database. ORA-24355: attempt to store a negative number in an Unsigned Display type. Cause: An attempt was made to convert a negative number into an unsigned display type. Action: Please check the number in the database or change the defined datatype. ORA-24356: internal error while converting from to COBOL display type. Cause: An internal error was encountered during conversion to COBOL display type. Action: Contact customer support. ORA-24357: internal error while converting from to OCIDate. Cause: An internal error was encountered during conversion to OCIDate type. Action: Contact customer support. ORA-24358: OCIBindObject not invoked for a Object type or Reference Cause: OCIBindObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference. Action: Please invoke the OCIBindObject call for all Object Types and References. ORA-24359: OCIDefineObject not invoked for a Object type or Reference Cause: OCIDefineObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference. Action: Please invoke the OCIDefineObject call for all Object Types and References. ORA-24360: Type Descriptor Object not specified for Object Bind/Define Cause: Type Descriptor Object is a mandatory parameter for Object Types Binds and Defines. Action: Please invoke the OCIBindObject() or OCIDefineObject() call with a valid Type Descriptor Object. ORA-24361: basic bind call not invoked before invoking advanced bind call Cause: One of the basic bind calls was not invoked on this bind handle before performing an advanced bind call. Action: Please invoke the advanced bind call on this bind handle only after performing a basic bind call. ORA-24362: improper use of the character count flag Cause: When the character count flag is set, then the maximum size of the buffer in the server should be specified as a non-zero value. Action: Please use a non-zero value for the mamimum size of the buffer in the server. ORA-24363: measurements in characters illegal here Cause: Measurements in characters instead of bytes are illegal if either the server"s or client"s character set is varying width. Action: If either the client"s or server"s character set is varying width then do not use the OCI_ATTR_CHAR_COUNT attribute for the bind handle. Use OCI_ATTR_MAXDATA_SIZE instead. ORA-24364: internal error while padding blanks Cause: An internal error has occurred while attempting to blank pad string data. This error should not occur normally. Action: Contact customer support. ORA-24365: error in character conversion Cause: This usually occurs during conversion of a multibyte character data when the source data is abnormally terminated in the middle of a multibyte character. Action: Make sure that all multibyte character data is properly terminated. ORA-24366: migratable user handle is set in service handle Cause: This occurs during user authentication, a migratable user handle has been set in the service handle. Action: Service handle must not be set with migratable user handle when it is used to authenticate another user. ORA-24367: user handle has not been set in service handle Cause: This occurs during authentication of a migratable user. the service handle has not been set with non-migratable user handle. Action: Service handle must be set with non-migratable user handle when it is used to authenticate a migratable user. ORA-24368: OCI mutex counter non-zero when freeing a handle Cause: This is an internal OCI error. Action: Contact customer support. ORA-24369: required callbacks not registered for one or more bind handles Cause: No callbacks have been registered for one or more of the bind handles which are part of the RETURNING clause. Action: The bind handles which are to receive data in a DML statememt with a RETURNING clause must have their mode set as DATA_AT_EXEC and callback functions must be registered for these bind handles using OCIBindDynamic. ORA-24370: illegal piecewise operation attempted Cause: Data of a certain datatype that does not support piecewise operation is being sent or fetched in pieces. Action: Always set the piece value to OCI_ONE_PIECE for datatypes that does not support piecewise operation. ORA-24371: data would not fit in current prefetch buffer Cause: An internal OCI error has occurred. Action: Please contact Oracle customer support. ORA-24372: invalid object for describe Cause: The object to be described is not valid. It either has compilation or authorization errors. Action: The object to be described must be valid. ORA-24373: invalid length specified for statement Cause: The length specified for the statement is either 0 or too large. Action: Specify a valid length for the statement. ORA-24374: define not done before fetch or execute and fetch Cause: The application did not define output variables for data being fetched before issuing a fetch call or invoking a fetch by specifying a non-zero row count in an execute call. Action: Issue OCI define calls for the columns to be fetched. ORA-24375: Cannot use V6 syntax when talking to a V8 server Cause: V6 syntax is no longer supported in V8 server. Action: Change syntax to V7 syntax or higher. ORA-24376: cannot register/get user callback for non-environment handle Cause: A user callback registration or get was attempted on a handle which is not an environment handle. Action: Pass the environment handle to register/get user callback. ORA-24377: invalid OCI function code Cause: An invalid function code was used to register or get user callback" Action: Use a valid OCI function code. ORA-24378: user callbacks not allowed for this call Cause: An attempt was made to register a user callback for an OCI call for which it not allowed to register user callbacks. Action: Do not register user callback for this OCI call. ORA-24379: invalid user callback type Cause: An invalid type of user callback was specified. Action: Specify a valid user callback type. ORA-24380: invalid mode specification Cause: The mode parameter in an OCIU* call is invalid Action: Use only valid mode parameter ORA-24381: error(s) in array DML Cause: One or more rows failed in the DML. Action: Refer to the error stack in the error handle. ORA-24382: statement handled already executed or described Cause: The Statement handle was executed or described successfuly before. Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY. ORA-24383: Overflow segment of an IOT cannot be described Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment. Action: Use OCIDescribeAny to describe only documented objects. ORA-24384: Application context size is not initialized Cause: The size of the application context must be initialized before populating each context element. Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size ORA-24385: Application context size or index is not valid Cause: The size or index of the application context must be non-zero and non-negative. Action: Use an appropriate value for the size. ORA-24386: statement/server handle is in use when being freed Cause: This is an internal OCI error. Action: The user should reset in-use flag in statement handle before freeing the handle. ORA-24387: Invalid attach driver Cause: Trying to attach using the wrong driver Action: Relink the application in the right mode ORA-24388: Unsupported functionality in fast path mode Cause: Feature not supported in fast path mode Action: Avoid using the functionality in this mode ORA-24389: Invalid scrollable fetch parameters Cause: All the requested rows in this fetch could not be received. Action: Check the fetch orientation, scroll offset, OCI_ATTR_CURRENT_POSITION and number of rows in OCIStmtFetch2 call. If required, change some of above parameters and fetch again. ORA-24390: Unsupported scrollable cursor operation Cause: The scrollable cursor execute or fetch has failed. Action: Check the documentation for supported types, and other restrictions while using scrollable cursors. ORA-24391: invalid fetch operation Cause: Scrollable cursor operation requested with non-scrollable cursor. Action: Check if the statement was executed in the scrollable mode. Else the only acceptable orientation is OCI_FETCH_NEXT that ignores the scroll offset parameter. ORA-24392: no connection pool to associate server handle Cause: OCIServerAttach called in OCI_POOL mode but no connection pool found to associate the server handle. Action: 1) Verify that OCIConnectionPoolCreate is called before calling OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach matches with that of the connection pool database link. ORA-24393: invalid mode for creating connection pool Cause: Mode specified in OCIConnectionPoolCreate is invalid. Action: Use a valid mode. ORA-24394: invalid mode for destroying connection pool Cause: Mode specified in OCIConnectionPoolDestroy is invalid. Action: Use a valid mode. ORA-24395: cannot reinitialize non-existent pool Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle. Action: Create a connection pool prior to reinitializing it. ORA-24396: invalid attribute set in server handle Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server handle and attached in OCI_POOL mode. Connection pooling does not support non blocking mode. Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server handle while attaching in OCI_POOL mode. ORA-24397: error occured while trying to free connections Cause: An internal error occured while trying to free connections. Action: Contact customer support. ORA-24398: connection pool already exists Cause: A connection pool has already been created for the specified pool handle. Action: 1) Specify a different pool handle to create a new connection pool. 2) If you wish to modify the pool parameters, call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode. ORA-24399: invalid number of connections specified Cause: An invalid combination of minimum, maximum and increment number of connections was specified in the OCIConnectionPoolCreate call. Action: Specify a valid combination of parameters. ORA-24400: error occured while creating connections in the pool Cause: The database link specified in OCIConnectionPoolCreate might be an invalid one. Action: Specify a valid database link. ORA-24401: cannot open further connections Cause: Sufficient number of connections are not present in the pool to execute the call. No new connections can be opened as the connMax parameter supplied in OCIConnectionPoolCreate has been reached. Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and increase the value of the connMax parameter. ORA-24402: error occured while creating connections in the pool Cause: The username and password specified in OCIConnectionPoolCreate might be invalid. Action: Specify a valid username and password. ORA-24403: error occured while trying to destroy the connection pool Cause: Some connections in the pool were busy when an attempt to destroy the connection pool was made. Action: Ensure no connections from the pool are being used. ORA-24404: connection pool does not exist Cause: An attempt was made to use the connection pool before creating it. Action: Create the connection pool. ORA-24405: error occured while trying to create connections in the pool Cause: An internal error occured while creating connections in the pool. Action: Contact customer support. ORA-24406: API mode switch is disallowed when a call is in progress. Cause: A mode switch from OCI8 to OCI7 was attempted in a callback. Action: The user should perform the API mode switch either prior to initiating the top call or after the main call is done. ORA-24407: connection pool already exists Cause: A connection pool has already been created for the specified pool name. Action: Specify a different pool name to create a new connection pool. ORA-24408: could not generate unique server group name Cause: An internal error occured while generating unique server group name. Action: Contact customer support. ORA-24409: client cannot understand the object Cause: The client cannot process all the new features in the object. Action: Upgrade the client so that features like inheritance and SQLJ objects can be used. ORA-24410: scrollable cursor max size exceeded Cause: Result set size exceeded the max limits. Action: Check the documentation for allowable maximum result set size for scrollable cursors. Re-execute with a smaller expected result set size or make the cursor non-scrollable. ORA-24411: Session pool already exists. Cause: A session pool has already been created for the specified pool handle. Action: 1) Specify a different pool handle to create a new session pool. 2) If you wish to modify the pool parameters, call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode. ORA-24412: Cannot reinitialize non-existent pool Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle. Action: Create a session pool prior to reinitializing it. ORA-24413: Invalid number of sessions specified Cause: An invalid combination of minimum, maximum and increment number of sessions was specified in the OCISessionPoolCreate call. Action: Specify a valid combination of parameters. ORA-24414: Only number sessions could be started. Cause: The number of sessions specified by the minSess parameter of OCISessionPoolCreate could not be started, possibly because the value supplied was larger than that supported by the server." Action: This is a warning. Check the maximum number of sessions allowed on the server. ORA-24415: Missing or null username. Cause: Username and password must be specified when pool is created in this mode. Action: Specify a valid username and password. ORA-24416: Invalid session Poolname was specified. Cause: An attempt was made to use a Session Pool that does not exist. Action: Create a Session Pool before using it. ORA-24417: Session pool size has exceeded the maximum limit Cause: The number of sessions has exceeded the maximum size of the Session Pool. Action: This is a warning. You can tune the session pool with appropriate minimum and maximum parameters. ORA-24418: Cannot open further sessions. Cause: Sufficient number of sessions are not present in the pool to execute the call. No new sessions can be opened as the sessMax parameter supplied in OCISessionPoolCreate has been reached. Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and increase the value of the sessMax parameter. ORA-24419: Proxy sessions are not supported in this mode. Cause: A proxy session was requested for from a Session Pool which does not support proxy sessions. Action: Do not specify mode OCI_CRED_PROXY. ORA-24420: OCISessionRelease must be used to release this session. Cause: The session was retrieved using OCISessionGet, and an attempt has been made to release it using a call other than OCISessionRelease. Action: Call OCISessionRelease. ORA-24421: OCISessionRelease cannot be used to release this session. Cause: The session was not retrieved using OCISessionGet, and an attempt has been made to release it using OCISessionRelease. Action: Release the session using an appropriate call. ORA-24422: error occurred while trying to destroy the Session Pool Cause: An attempt was made to destroy the session pool while some sessions in the pool were busy. Action: Ensure that no sessions from the pool are being used OR call OCISessionPoolDestroy with mode set to OCI_SPD_FORCE. ORA-24430: Null values for sqltext and key were specified. Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key were specified. Action: Specify valid values for sqltext or key or both. ORA-24431: Statement does not exist in the cache Cause: The statement that was requested for does not exist in the statement cache. Action: Please request for a valid statement. ORA-24432: The statement that was returned is not tagged. Cause: A tagged statement was requested for, but an untagged statement has been returned. Action: This is a warning. Please modify and tag the statement as desired. ORA-24433: This statement has already been prepared using OCIStmtPrepare2. Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being reprepared using OCIStmtPrepare." Action: Please use a different statement handle. ORA-24434: OCIStmtRelease called before OCIStmtPrepare2. Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2. Action: Call OCIStmtPrepare2 before OCIStmtRelease. ORA-24435: Invalid Service Context specified. Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute. Action: Please specify the same service context that the statement was prepared with. ORA-24436: Invalid statement Handle. Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2. Action: Release the statement using OCIStmtRelease. ORA-24437: OCIStmtExecute called before OCIStmtPrepare2. Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2. Action: Call OCIStmtPrepare2 before OCIStmtExecute. ORA-24438: Invalid Authentication Handle specified. Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute. Action: none ORA-24439: success with PLSQL compilation warning Cause: A plsql compilation warning occurred. Action: Return OCI_SUCCESS_WITH_INFO along with the error code. ORA-24440: OCI Easy Install mode cannot be initialized Cause: An internal OCI error has occurred. Action: Please contact Oracle customer support. ORA-24450: Cannot pre-process OCI statement Cause: An error occured during statement pre-processing. E.g., SQL statement has invalid usage of N" or Q" literals. Action: Correct the SQL statement. ORA-24460: Native Net Internal Error Cause: Internal error . Action: This error should not normally occur. If it persists, please contact your customer service representative. ORA-24500: invalid UTF16 mode Cause: UTF16 mode is allowed only at environment handle creation time. Action: Remove UTF16 mode for functions other than OCIEnvCreate() ORA-24501: invalid UTF16 string passed in Cause: Non-UTF16 string is passed in while UTF16 string is expected Action: Check the parameter which is actually a string ORA-24502: codepoint length overflows Cause: Returned buffer has more codepoints than allowed Action: Set OCI_MAXCHAR_SIZE large enough to accommodate ORA-24503: codepoint length overflows for piecewise operation Cause: Accumulated codepoint length exceeds allowed codepoint length Action: Set OCI_MAXCHAR_SIZE large enough to accommodate ORA-24504: data length larger than expected Cause: Incoming data larger than receiving buffer Action: Set OCI_MAXDATA/MAXCHAR_SIZE appropriately or remove the setting ORA-24505: cannot change character set id on the handle Cause: Attempts to change character set id on non-environment handles Action: Only try to change character set id on environment handles ORA-24506: invalid attempt to change character set id on env handle Cause: Attempts to change character set id after other handles have been allocated from the env handle Action: Change character set id after creating environment handle but before allocating any handles from it. ORA-24507: invalid combination of character set ids Cause: Attempts to set one character set id as zero Action: Set both charset and ncharset as zero or non-zero in OCIEnvNlsCreate() ORA-24508: Buffer is not aligned correctly. Cause: Alignment error ocurred in buffer when converting between character sets. Action: Align buffer appropriately. For UTF16 buffer, pass a ub2 pointer. ORA-24750: incorrect size of attribute Cause: Transaction ID attribute size is incorrect. Action: Verify that the size parameter is correct. ORA-24752: OCI_TRANS_NEW flag must be specified for local transactions Cause: Application attempted to start a local transaction without using OCI_TRANS_NEW. Action: Use OCI_TRANS_NEW when starting local transactions. ORA-24753: local transactions cannot be detached Cause: An attempt to detach a local transaction was made. Action: Local transactions may only be committed or rolled back. ORA-24754: cannot start new transaction with an active transaction Cause: An attempt to start a new transaction was made when there was an active transaction. Action: Commit, rollback or detach the existing transaction before starting a new transaction. ORA-24755: OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported Cause: These flags are currently not supported. Action: none ORA-24756: transaction does not exist Cause: An invalid transaction identifier or context was used or the transaction has completed. Action: Supply a valid identifier if the transaction has not completed and retry the call. ORA-24757: duplicate transaction identifier Cause: An attempt was made to start a new transaction with an identifier already in use by an existing transaction. Action: Verify that the identifier is not in use. ORA-24758: not attached to the requested transaction Cause: An attempt was made to detach or complete a transaction that is not the current transaction. Action: Verify that the transaction context refers to the current transaction. ORA-24759: invalid transaction start flags Cause: An invalid transaction start flag was passed. Action: Verify that one of the following values - OCI_TRANS_NEW, OCI_TRANS_JOIN, OCI_TRANS_RESUME was specified. ORA-24760: invalid isolation level flags Cause: An invalid isolation level flag was passed. Action: Verify that only one of following values - OCI_TRANS_READONLY, OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used. ORA-24762: server failed due to unspecified error Cause: An internal error has occured in the server commit protocol. Action: Contact customer support. ORA-24763: transaction operation cannot be completed now Cause: The commit or rollback cannot be performed now because the session cannot switch to the specified transaction. Action: Retry the operation later. ORA-24769: cannot forget an active transaction Cause: Transaction identifier refers to an active transaction. Action: Verify that the identifier of an active transaction was not passed as an argument. ORA-24770: cannot forget a prepared transaction Cause: Transaction identifier refers to a prepared transaction. Action: Verify that the identifier of a prepared transaction was not passed as an argument. ORA-24771: cannot detach, prepare or forget a local transaction Cause: Service handle contains a local transaction context. Action: Verify that the transaction context does not refer to a local transaction. ORA-24772: Cannot mix tightly-coupled and loosely-coupled branches Cause: Application attempted to start a transaction with a global transaction identifier and a wrong option. Action: Verify that all branches of a global transaction are started with either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact customer support. ORA-24773: invalid transaction type flags Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified. Action: Verify that the right parameters are being used. ORA-24774: cannot switch to specified transaction Cause: The transaction specified in the call refers to a transaction created by a different user. Action: Create transactions with the same authentication so that they can be switched. ORA-24775: cannot prepare or commit transaction with non-zero lock value Cause: An attempt was made to detach the transaction with a non-zero lock value. Action: Detach the transaction with lock value set to zero and then try to prepare or commit the transaction. ORA-24776: cannot start a new transaction Cause: An attempt was made to start a new transaction when session was already attached to an existing transaction. Action: End the current transaction before creating a new transaction. ORA-24777: use of non-migratable database link not allowed Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multi threaded server process. Action: Perform the work in the local database or open a connection to the remote database from the client. If multi threaded server option is installed, connect to the Oracle instance through the dispatcher. ORA-24778: cannot open connections Cause: The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s). Action: Close the connection(s) in the session and then try to access the remote database from the migratable transaction. If the error still occurs, contact Oracle customer support. ORA-24779: detach not allowed with open remote cursor Cause: The migratable transaction tried to detach from the current session while having an open remote cursor. Action: Close any open remote cursor prior to detach. ORA-24780: cannot recover a transaction while in an existing transaction Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long). Action: Detach from the current transaction and retry the operation. ORA-24781: branches don"t belong to the same global transaction Cause: The list of xids passed into kpotxmp() don"t have the same gtrid Action: none ORA-24782: Cannot detach from a non-migratable transaction Cause: An attempt was made to detach from a non-migrateable transaction. Action: Either commit or rollback the transaction. ORA-24783: Cannot switch non-migratable transactions Cause: An attempt was made to prepare/commit a txn different from current. Action: none ORA-24784: Transaction exists Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction Action: none ORA-24785: Cannot resume a non-migratable transaction Cause: An attempt was made to resume a non-migrateable transaction. Action: none ORA-24786: separated transaction has been completed Cause: The current transaction has been completed by another process. Action: Start a new transaction ORA-24787: remote cursors must be closed before a call completes Cause: The previous operation did not close all the remote cursors it opened. Since separated transactions are enabled, this is not allowed. Action: Close all remote cursors in each call, or start a regular (non-separated) transaction. ORA-24788: cannot switch to specified transaction (server type) Cause: The transaction specified was created by a shared server and the requestor is a dedicated server, or the transaction was created by a dedicated server and the requestor is a shared server. Action: All parts of this application should connect as dedicated or as shared. ORA-24789: start not allowed in recursive call Cause: Oracle RM will not start/resume a branch in a recursive call Action: Reconsider your application stack design ORA-24790: cannot mix OCI_TRANS_RESUME and transaction isolation flags Cause: An attempt was made to change the isolation level of an existing transaction. Action: No action required ORA-24791: invalid transaction start flags Cause: An invalid transaction start flag was passed. Action: Verify that OCI_TRANS_LOOSE was not passed along with OCI_TRANS_JOIN, OCI_TRANS_RESUME. ORA-24792: cannot mix services in a single global transaction Cause: Oracle RM will not serve global (distributed) transaction requests if branches are created using different services Action: Configure clients such that those participating in the same distributed transaction use the same service name. ORA-24793: Test DTP service start and stop Cause: internal use only Action: none. ORA-24794: no active DTP service found Cause: Oracle RM will not serve global (distributed) transaction requests until DTP services are configured in RAC. It is possible that a service was stopped while transactions were in-flight. Action: Provision/Start DTP services first. ORA-24795: Illegal string attempt made Cause: An illegal attempt was made to commit/rollback current transaction Action: Use appropriate commit/rollback mechanism ORA-24801: illegal parameter value in OCI lob function Cause: One of the parameter values in the OCI lob function is illegal. Action: Check every parameter in the OCI Lob function call to make sure they are correct. Offsets should be greater than or equal to one. ORA-24802: user defined lob read callback error Cause: The only valid return value for a user defined lob read callback function is OCI_CONTINUE. Any other value will cause this error. Action: Verify that OCI_CONTINUE is returned from the user defined lob read callback function. ORA-24803: illegal parameter value in lob read function Cause: Internal error . Action: This error should not normally occur. If it persists, please contact your customer service representative. ORA-24804: Lob read/write functions called while another OCI LOB read/write streaming is in progress Cause: Internal error. Action: Wait for the ongoing LOB streaming call to finish before issuing the next server call, or use OCIBreak() abort the current LOB streaming call. ORA-24805: LOB type mismatch Cause: When copying or appending LOB locators, both source and desctination LOB locators should be of the same type. Action: Pass the same type of LOB locators for copying or appending. ORA-24806: LOB form mismatch Cause: When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB. Action: Make sure that the buffer you are using to read or write has the same form as that of the LOB. ORA-24807: LOB form mismatch Cause: When copying or appending LOBs, both source and desctination LOB locators should have the same character set form. Action: Pass locators of the same character set form for copying or appending LOBs. ORA-24808: streaming of lob data is not allowed when using lob buffering Cause: Attempted to stream lob data via the polling mode or a callback when lob buffering was enabled for the input lob locator. Action: Lob buffering is useful when reading/writing small amounts of lob data so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. If streaming of data 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 OCILobRead/OCILobWrite call. ORA-24809: amount specified will not fit in the lob buffers Cause: LOB buffering is enabled for the input lob locator so buffering will be used. However, the amount of lob data to read or write is larger than what the lob buffers can hold. Action: Either disable buffering on the input lob locator and reissue the command or pass a smaller amount. ORA-24810: attempting to write more data than indicated Cause: While writing into a LOB, more data was supplied than indicated. Action: If data is written in pieces, then make sure that you do not provide more data in the pieces (cumulatively), than you indicated. ORA-24811: less data provided for writing than indicated Cause: While writing into a LOB, less data was provided than indicated. Action: If writing data in single pieces, then make sure that the buffer length specified is big enough to accommodate tha data being provided. If data is written in pieces, then make sure that all the data has been provided before specifying OCI_LAST_PIECE. ORA-24812: character set conversion to or from UCS2 failed Cause: If the database character set is varying-width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed. Action: Contact Oracle Worldwide Support. ORA-24813: cannot send or receive an unsupported LOB Cause: An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle. Action: Use a version of the Oracle that supports the LOB on both the client and the server. ORA-24814: operation not allowed for temporary LOBs Cause: Temporary LOB locators are not allowed in the operation. For example: OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs. Action: Use OCILobLocatorAssign for temporary LOBs instead. Note that OCILobLocatorAssign can also be used for persistent LOBs, in which case it will behave the same as OCILobAssign. ORA-24815: Invalid character set form Cause: An invalid character set form was passed into an OCI LOB function. For example, the only valid cs form for OCILobCreateTemporary() is OCI_DEFAULT(0), SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2). Action: Specify a valid character set form. ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column Cause: A Bind value of length potentially > 4000 bytes follows binding for LOB or LONG. Action: Re-order the binds so that the LONG bind or LOB binds are all at the end of the bind list. ORA-24817: Unable to allocate the given chunk for current lob operation Cause: The given size is increased to accomodate the number of bytes from server due to varying width db char/nchar set. Action: Use smaller chunk sizes when you have character set conversion between client/server or perform piece-wise read or write. ORA-24850: failed to startup shared subsystem Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting up the shared subsystem. Action: Contact Oracle Customer support. ORA-24851: failed to connect to shared subsystem Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the process to the shared subsystem. Action: Contact Oracle Customer Support. ORA-24852: protocol error during statement execution Cause: An internal protocol error occurred while receiving describe data from the server during execution of a statement. Action: Contact Oracle Customer Support. ORA-24853: failed to connect thread to shared subsystem Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem. Action: Contact Oracle Customer Support. ORA-24900: invalid or unsupported mode paramater passed in call Cause: The mode parameter passed into the OCI Client Notification call is incorrect. Action: Please correct the mode parameter passed into OCI. ORA-24901: handles belonging to different environments passed into an OCI call Cause: All handles passed into an OCI call should belong to the same environment. In the call that returned this error, handles belonging to different environments were passed in. Action: Please ensure that the handle parameters in the call to come from the same OCI Environment. ORA-24902: invalid subscription name or name-length in subscription handle Cause: The subscription handle passed into the OCI call does not have a proper name or name-length attribute. Action: Please set the name and name-length attributes using the OCIAttrSet() call. ORA-24903: invalid namespace attribute passed into OCI call Cause: The subscription handle passed into the OCI call does not have a proper namespace attribute. Action: Please set the namespace attribute using the OCIAttrSet() call. ORA-24904: invalid callback attribute passed into OCI call Cause: The subscription handle passed into the OCI call does not have a proper callback attribute. Action: Please set the callback attribute using the OCIAttrSet() call. ORA-24905: invalid recepient protocol attribute passed into OCI call Cause: The subscription handle passed into the OCI call does not have a proper recepient protocol attribute. Action: Please set the recepient protocol attribute using the OCIAttrSet() call. ORA-24906: invalid recepient attribute passed into OCI call Cause: The subscription handle passed into the OCI call does not have a proper recepient attribute. Action: Please set the recepient attribute using the OCIAttrSet() call. ORA-24907: invalid pair of callback and recepient protocol attributes Cause: The subscription handle passed into the OCI call can"t have both the callback defined and a recepient protocol other than OCI_SUBSCR_PROTO_OCI at the same time. Action: Please set the appropriate callback and recepient protocol attributes using the OCIAttrSet() call. ORA-24908: invalid recipient presentation attribute Cause: The subscription handle passed into the OCI call does not have a valid recipient presentation attribute. Action: Set the recipient presentation attribute using the OCIAttrSet() call ORA-24909: call in progress. Current operation cancelled Cause: The OCI call was invoked when another call on the connection was in progress. Action: Check if the OCI call is supported when the call is in progress under special conditions; for example, if it is being used by a signal handler. NLS_DO_NOT_TRANSLATE [24910,24910] ORA-24911: Cannot start listener thread at specified port Cause: Thread already running at a different port. Action: Set the correct port in the environment handle or let the system choose the port. ORA-24912: Listener thread failed. string Cause: Thread listening for event notification exited because of an error. The error encountered is appended to the error message. Action: The client needs to be restarted. ORA-24950: unregister failed, registeration not found Cause: The registeration that was asked to be unregistered could not be found. Action: Please check the callback function name and the subscription name in the unregister call. ORA-24952: register, unregister or post has incorrect collection count Cause: The register, unregister or post function was invoked with a collection that was smaller than the size specified by the parameter to the function. Action: Please check the function"s use and ensure that the size parameter is correct. ORA-24960: the attribute string is greater than the maximum allowable length of number Cause: The user attempted to pass an attribute that is too long Action: Shorten the specified attribute and retry the operation. ORA-25000: invalid use of bind variable in trigger WHEN clause Cause: A bind variable was used in the when clause of a trigger. Action: Remove the bind variable. To access the table columns use (new/old).column_name. ORA-25001: cannot create this trigger type on views Cause: Only INSTEAD OF triggers can be created on a view. Action: Change the trigger type to INSTEAD OF. ORA-25002: cannot create INSTEAD OF triggers on tables Cause: Only BEFORE or AFTER triggers can be created on a table. Action: Change the trigger type to BEFORE or AFTER. ORA-25003: cannot change NEW values for this column type in trigger Cause: Attempt to change NEW trigger variables of datatype object, REF, nested table, VARRAY or LOB datatype which is not supported. Action: Do not change the NEW trigger variables in the trigger body. ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers Cause: WHEN clause is specified in an INSTEAD OF trigger. Action: Remove the WHEN clause when creating an INSTEAD OF trigger. ORA-25005: cannot CREATE INSTEAD OF trigger on a read-only view Cause: attempt to create an INSTEAD OF trigger on a view created with read-only option. The view cannot be updated using INSTEAD OF triggers. Action: Do not create the trigger. ORA-25006: cannot specify this column in UPDATE OF clause Cause: Attempt to create a trigger on update of a column whose datatype is disallowed in the clause, such as LOB and nested table. Action: Remove the UPDATE OF clause. ORA-25007: functions or methods not allowed in WHEN clause Cause: PLSQL function call or method invocation is not allowed in the WHEN clause when creating a trigger. Action: Remove the function call or method invocation from the WHEN clause. ORA-25008: no implicit conversion to LOB datatype in instead-of trigger Cause: When inserting or updating a view using instead-of trigger, the new value for a LOB view column is of a different datatype. Action: Specified a LOB value as the new value for the LOB view column. ORA-25009: Nested table clause allowed only for INSTEAD OF triggers Cause: Triggers on nested tables can only be created on view columns using INSTEAD OF triggers. Action: Use view nested table columns for defining nested table triggers. ORA-25010: Invalid nested table column name in nested table clause Cause: The column name specified in the nested table clause of an INSTEAD OF trigger does not correspond to a nested table column. Action: Specify a nested table column on which the trigger is to be defined. ORA-25011: cannot create trigger on internal AQ table Cause: An attempt was made to try to create a trigger on a table that is used internally to support the Advanced Queueing (AQ) feature. Action: Do not create the trigger. ORA-25012: PARENT and NEW values cannot be identical Cause: The referencing clause specifies identical values for PARENT and OLD. Action: Re-specify either the PARENT or NEW referencing value. ORA-25013: OLD and PARENT values cannot be identical Cause: The referencing clause specifies identical values for OLD and PARENT. Action: Re-specify either the OLD or PARENT referencing value. ORA-25014: cannot change the value of a PARENT reference variable Cause: Parent values can only be read and not changed. Action: Do not attempt to change a Parent variable. ORA-25015: cannot perform DML on this nested table view column Cause: DML cannot be performed on a nested table view column except through an INSTEAD OF trigger Action: Create an INSTEAD OF trigger over the nested table view column and then perform the DML. ORA-25016: cannot specify column list for insert into nested table view column Cause: A column list cannot be specified for inserts into the nested table view column. Action: Specify all the columns for insert into the nested table. ORA-25017: cannot reference NEW ROWID for movable rows in before triggers Cause: NEW ROWID was referenced in a before row trigger which is defined on an index-organized table, or a partitioned table with enabled movement of rows. The ROWID cannot be computed in a before row update trigger because it depends on the actual values of the row Action: Remove references to NEW ROWID from the trigger definition. ORA-25018: conflicting trigger string already exists Cause: Conflicting instead of DDL trigger on schema/database already exists. Action: Remove the old trigger ORA-25019: too much concurreny Cause: cannot pin the database/schema because of too much concurrency Action: try the operation later ORA-25020: renaming system triggers is not allowed Cause: renaming system triggers is not allowed Action: Drop the trigger, and create a new one for the same ORA-25100: TABLESPACE option can only be used with ALTER INDEX REBUILD Cause: The TABLESPACE option to ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name. ORA-25101: duplicate REBUILD option specification Cause: The REBUILD option to ALTER INDEX is specified more than once. Action: Specify the option at most once. ORA-25102: PARALLEL option can only be used with ALTER INDEX REBUILD Cause: The PARALLEL option to ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25103: NOPARALLEL option can only be used with ALTER INDEX REBUILD Cause: The NOPARALLEL option to ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25104: UNRECOVERABLE option can only be used with ALTER INDEX REBUILD Cause: The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25105: RECOVERABLE option can only be used with ALTER INDEX REBUILD Cause: The RECOVERABLE option to ALTER INDEX was used without the REBUILD option. Action: Use ALTER INDEX REBUILD. ORA-25106: only one of 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 an ALTER INDEX REBUILD statement. Action: Remove all but one of the PARALLEL or NOPARALLEL clauses. ORA-25107: duplicate TABLESPACE option specification Cause: the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement. Action: Remove all but one of the TABLESPACE clauses. ORA-25108: standby lock name space exceeds size limit of string characters Cause: The lock name space for the standby database exceeded the maximum string length. Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a character string of less than the specified characters. ORA-25109: standby lock name space has illegal character "string" Cause: An invalid lock name space was specified for the standby database. The lock name space for the standby database can only contain A-Z, 0-9, "_", "#", "$", "." and "@" characters. Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a valid character string. ORA-25110: NOSORT may not be used with a bitmap index Cause: An attempt was made to create a bitmap index using the NOSORT option. Action: Remove NOSORT from the CREATE BITMAP INDEX statement. ORA-25111: creation of BITMAP cluster indices is not supported Cause: An attempt was made to create a cluster index with the BITMAP attribute. Action: Remove BITMAP from the CREATE INDEX statement. ORA-25112: maximum number of BITMAP index columns is 30 Cause: Too many columns were specified for the index. Action: Create an index on fewer columns. ORA-25113: GLOBAL may not be used with a bitmap index Cause: An attempt was made to create a bitmap index using the GLOBAL option. Action: Remove GLOBAL from the CREATE BITMAP INDEX statement, and/or add a LOCAL partition descriptor if the table is partitioned. ORA-25114: invalid file number specified in the DUMP DATAFILE/TEMPFILE command Cause: An invalid file number was used in dumping a datafile or tempfile. Action: Specify a valid file number. ORA-25115: duplicate BLOCK option specification Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command. Action: Specify only one BLOCK option. ORA-25116: invalid block number specified in the DUMP DATAFILE/TEMPFILE command Cause: An invalid block number was used in dumping a datafile or tempfile. Action: Specify a valid block number. ORA-25117: MIN/MAX/Block Number expected Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command. Action: Correct the syntax. ORA-25118: invalid DUMP DATAFILE/TEMPFILE option Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command. Action: Correct the syntax. ORA-25119: LOGGING/NOLOGGING option already specified Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once. Action: Remove all but one of the logging specifications. ORA-25120: MINIMUM EXTENT option already specified Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once. Action: Remove all but one of the MINIMUM EXTENT specifications. ORA-25121: MINIMUM EXTENT value greater than maximum extent size Cause: In CREATE/ALTER TABLESPACE, the value specified for the MINIMUM EXTENT option was greater than the maximum extent size. Action: Choose a lower value for the MINIMUM EXTENT option. ORA-25122: Only LOCAL bitmap indexes are permitted on partitioned tables Cause: An attempt was made to create a global bitmap index on a partioned table. Action: create a local bitmap index instead. ORA-25123: Too many components specified in the name. Cause: Specifying more components to a name than allowed. Action: Check the name specified for the operation. ORA-25124: Database link name not allowed. Cause: Specifying a database link name when it is not permitted. Action: Check the name specified for the operation. ORA-25125: BUFFER_POOL storage option not allowed Cause: The user attempted to specify the BUFFER_POOL storage option. This option may only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX. Action: Remove this option and retry the statement. ORA-25126: Invalid name specified for BUFFER_POOL Cause: The name of the buffer pool specified by the user is invalid. The only valid names are KEEP, RECYCLE and DEFAULT. Action: Use a valid name or remove the BUFFER_POOL clause. ORA-25127: RELY not allowed in NOT NULL constraint Cause: An attempt to set RELY on for NOT NULL constraint. Action: only NORELY may be specified for a NOT NULL constraint. ORA-25128: No insert/update/delete on table with constraint (string.string) disabled and validated Cause: Try to insert/update/delete on table with DISABLE VALIDATE constraint. Action: Change the constraint"s states. ORA-25129: cannot modify constraint (string) - no such constraint Cause: the named constraint does not exist for this table. Action: Obvious ORA-25130: cannot modify primary key - primary key not defined for table Cause: Attempted to modify a primary key that is not defined for the table. Action: None ORA-25131: cannot modify unique(string) - unique key not defined for table Cause: attempted to modify a unique key that is not deined for the table. Action: None ORA-25132: UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION Cause: cannot ALTER TABLE EXCHANGE PARTITION when the partition and the table have a disabled and validated unique constraints AND the unique keys in the partion is not mutually exclusive from the rest of the table. Action: Change the constraint"s status. ORA-25133: duplicate SINGLE TABLE option specified Cause: The SINGLE TABLE option was specified more than once. Action: Specify the SINGLE TABLE option only once. ORA-25134: keyword TABLE expected Cause: The keyword TABLE is missing from the SINGLE TABLE option. Action: Place the keyword TABLE after the keyword SINGLE in the command. ORA-25135: cannot use the SINGLE TABLE option Cause: The SINGLE TABLE option is only valid for hash clusters. Action: Do not specify the SINGLE TABLE option. ORA-25136: this cluster can contain only one table Cause: An attempt was made to store more than one table in a cluster that was created with the SINGLE TABLE option. Action: Do not attempt to store more than one table in the cluster. ORA-25137: Data value out of range Cause: Value from cast operand is larger than cast target size. Action: Increase size of cast target. ORA-25138: %s initialization parameter has been made obsolete Cause: An obsolete initialization parameter has been specified Action: The system will come up, but parameters must be examined ORA-25139: invalid option for CREATE TEMPORARY TABLESPACE Cause: An invalid option appears. Action: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT LOCAL, UNIFORM ORA-25140: %s space policy cannot be specified for the string extent management Cause: An invalid option appears. Action: Make sure that for LOCAL extent management UNIFORM or AUTOALLOCATE is specified, and for DICTIONARY extent management UNIFORM or AUTOALLOCATE are not specified ORA-25141: invalid EXTENT MANAGEMENT clause Cause: An invalid option appears for EXTENT MANAGEMENT clause Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE ORA-25142: default storage clause specified twice Cause: default storage clause was specified twice for create tablespace Action: Specify it once. ORA-25143: default storage clause is not compatible with allocation policy Cause: default storage clause was specified for a tablespace with AUTOALLOCATE or UNIFORM policy Action: Omit the storage clause ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY contents Cause: An invalid option appears. Action: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY, USER ORA-25145: allocation policy already specified Cause: In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM. Action: Remove all but one of the allocation policy specifications. ORA-25146: EXTENT MANAGEMENT option already specified Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once. Action: Remove all but one of the EXTENT MANAGEMENT specifications. ORA-25147: UNIFORM SIZE value greater than maximum extent size Cause: In CREATE/ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size. Action: Choose a lower value for the UNIFORM SIZE option. ORA-25148: ONLINE option not permitted Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE on a table that is not index-organized. The ONLINE option is currently supported only for index-organized tables. Action: Remove the ONLINE option from the command. ORA-25149: Columns of UROWID type may not be indexed Cause: An attempt was made to create an index on a column of UROWID type Action: Remove the column from the list of indexed columns ORA-25150: ALTERING of extent parameters not permitted Cause: An attempt was made to alter the extent parameters for a segment in a tablespace with autoallocate or uniform extent allocation policy. Action: Remove the appropriate extent parameters from the command. ORA-25151: Rollback Segment cannot be created in this tablespace Cause: An attempt was made to create a rollback segment in a tablespace with autoallocate extent allocation policy. Action: Specify a different tablespace for the rollback segment ORA-25152: TEMPFILE cannot be dropped at this time Cause: An attempt was made to drop a TEMPFILE being used by online users Action: The TEMPFILE has been taken offline. Try again, later. ORA-25153: Temporary Tablespace is Empty Cause: An attempt was made to use space in a temporary tablespace with no files. Action: Add files to the tablespace using ADD TEMPFILE command. ORA-25154: column part of USING clause cannot have qualifier Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier. Action: Remove the qualifier. ORA-25155: column used in NATURAL join cannot have qualifier Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier. Action: Remove the qualifier. ORA-25156: old style outer join (+) cannot be used with ANSI joins Cause: When a query block uses ANSI style joins, the old notation for specifying outer joins (+) cannot be used. Action: Use ANSI style for specifying outer joins also. ORA-25157: Specified block size string is not valid Cause: An attempt was made to create a tablespace with a block size which is not supported. Action: Specify one of the valid blocksizes i.e the standard blocksize or one of (2k, 4k, 8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the platform. ORA-25158: Cannot specify RELY for foreign key if the associated primary key is NORELY Cause: RELY is specified for the foreign key contraint, when the associated primary key constraint is NORELY. Action: Change the option of the primary key also to RELY. ORA-25175: no PRIMARY KEY constraint found Cause: A PRIMARY KEY constraint must be defined for a table with this organization Action: Define a PRIMARY KEY ORA-25176: storage specification not permitted for primary key Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint for a table with this organization Action: Remove storage specification for primary key ORA-25177: UNRECOVERABLE option not permitted Cause: The UNRECOVERABLE option may not be specified for a primary key for a table with this organization Action: Remove UNRECOVERABLE option for primary key ORA-25178: duplicate PCTTHRESHOLD storage option specification Cause: The storage option PCTTHRESHOLD is specified more than once. Action: Specify storage options at most once. ORA-25179: invalid PCTTHRESHOLD storage option value Cause: The specified value must be a positive integer. Action: Specify an appropriate value. ORA-25180: PCTTHRESHOLD only valid for certain table organizations Cause: PCTTHRESHOLD can only be specified for tables with certain organizations. Action: Remove the PCTTHRESHOLD option. ORA-25181: missing ON keyword for NESTED INDEX Cause: ON keyword required to specify nested index column nest Action: Add ON keyword ORA-25182: feature not currently available for index-organized tables Cause: An attempt was made to use one or more of the following feature(s) not currently supported for index-organized tables: CREATE TABLE with LOB/BFILE/VARRAY columns, partitioning/PARALLEL/CREATE TABLE AS SELECT options, ALTER TABLE with ADD/MODIFY column options, CREATE INDEX Action: Do not use the disallowed feature(s) in this release. ORA-25183: index-organized table top index segment is in a different tablespace Cause: An attempt was made to drop a tablespace which contains an index only table"s overflow segment but not the top index segment" Action: find index-organized tables which span the tablespace being dropped and some other tablespace(s). Drop these tables. ORA-25184: column name expected Cause: A column name is not present where required by the CREATE TABLE for specifying last column to be included in the index segment of the index-organized table Action: Specify a column name where required by the syntax. ORA-25185: index column other than last can not be specified for INCLUDE clause Cause: An index column name other than the last is specified as including column Action: Specify either a column name which is not part of index-organized table primary key index , or the last key column of the primary key for the INCLUDING clause. ORA-25186: INCLUDING clause specified for index-organized table without OVERFLOW Cause: INCLUDING clause of a CREATE TABLE is an valid option only for index-organized tables with OVERFLOW clause (at creation time) or if an OVERFLOW segment already exists (at ALTER time). Action: Specify OVERFLOW clause for the index-organized table : For ALTER, perform ADD OVERFLOW first. ORA-25187: specified exceptions table form incorrect Cause: The specified table does not have the proper field definitions. Action: Specify the correct table to use. ORA-25189: illegal ALTER TABLE option for an index-organized table Cause: During ALTER of a index-organized table, the user attempted to enter one or more of the following options: TABLESPACE, ALLOCATE/DEALLOCATE EXTENT, PCTFREE/PCTUSED for IOT top index segment Action: Remove the illegal option(s). ORA-25190: an index-organized table maintenance operation may not be combined with other operations Cause: ALTER TABLE statement attempted to combine an index-organized table maintenance operation (e.g. changing physical attributes) with some other operation (e.g. ADD constraint) which is illegal Action: Ensure that a index-organized table maintenance operation is the sole operation specified in ALTER TABLE statement; ORA-25191: cannot reference overflow table of an index-organized table Cause: An attempt to directly access the overflow table of an index-organized table Action: Issue the statement against the parent index-organized table containing the specified overflow table. ORA-25192: invalid option for an index-organized table Cause: An attempt to specify one or more of the following options for an index-organized table: [NO]CACHE, NO LOGGING, CLUSTER Action: Remove the illegal option(s) ORA-25193: cannot use COMPRESS option for a single column key Cause: An attempt to use COMPRESS option on single column key Action: Remove the COMPRESS option. ORA-25194: invalid COMPRESS prefix length value Cause: The specified value must be a positive integer less than the number of key columns Action: Specify an appropriate value. ORA-25195: invalid option for index on an index-organized table Cause: An attempt to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED Action: none ORA-25196: keyword MOVE in ALTER TABLE MOVE must immediately follow
Cause: MOVE specified after one/more other ALTER options Action: Remove the illegal option(s) ORA-25197: an overflow segment already exists for the indexed-organized table Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment Action: none ORA-25198: only range, list, and hash partitioning are supported for index-organized table Cause: System, or Composite partitioning schemes are not supported yet Action: Select a different partitioning scheme ORA-25199: partitioning key of a index-organized table must be a subset of the primary key Cause: An attempt to specify a partitioning key which is not a prefix of the primary key of the index-organized table Action: Select a different partitioning key ORA-25200: invalid value string, QUEUE_NAME should be [SCHEMA.]NAME Cause: A NULL parameter was specified for QUEUE_NAME. Action: Specify a non-NULL queue name. ORA-25201: invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE Cause: An invalid value specified for parameter VISIBILITY. Action: Specify either ON_COMMIT or IMMEDIATE. ORA-25202: invalid value NULL, string should be non-NULL Cause: A NULL value was specified for the parameter. Action: Specify a non-NULL value. ORA-25203: invalid value string, DELAY should be non-negative Cause: A negative value or NULL was specified for DELAY. Action: Specify a non negative integer for DELAY. ORA-25204: invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP Cause: An invalid SEQUENCE_DEVIATION was specified. Action: Specify either the option "BEFORE" or "TOP". ORA-25205: the QUEUE string.string does not exist Cause: The specified queue does not exist. Action: Create the queue first before specifying it for enqueue or dequeue. ORA-25206: enqueue failed, enqueue to exception queue string.string not permitted Cause: An attempt was made to enqueue to an exception queue. Action: Try enqueueing to another queue. ORA-25207: enqueue failed, queue string.string is disabled from enqueueing Cause: The queue has been stopped to prevent any further enqueueing. Action: Enable the queue first by using an administrative operation. ORA-25208: RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE Cause: A relative message identifier should be specified if sequence deviation is specified as BEFORE. Action: Either specify an existing relative message identifier or don"t specify sequence deviation as BEFORE. ORA-25209: invalid value string, EXPIRATION should be non-negative or NEVER Cause: The expiration is less than zero or NULL. Action: Specify a valid value for expire_after which should be greater than or equal to zero or NEVER. ORA-25210: invalid value for RELATIVE_MSGID, no message in queue with that msgid Cause: No message inm the queue with the msgid equal to the specified RELATIVE_MSGID. Action: Try again with a valid RELATIVE_MSGID. ORA-25211: invalid DELAY specified when using sequence deviation Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message id. Action: Set the DELAY to be less than or equal to the delay of the message with the given relative message id. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue. ORA-25212: invalid PRIORITY specified when using sequence deviation Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message id. Action: Set the PRIORITY to be less than the delay of the message with the given relative message id. If the TOP option is used the prioirty must be greater than or equal to the priority of all the messages in the queue. ORA-25213: message with specified RELATIVE_MSGID has been dequeued Cause: The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued. Action: none ORA-25214: cannot specify delay or expiration for enqueue to exception queue Cause: A message was enqueued to the exception queue with either delay or expiration specified. Action: Enqueue a message without delay or expiration. ORA-25215: user_data type and queue type do not match Cause: A user tries to enqueue an object to a queue that was created for objects of different type. Action: Try enqueue again with an object of the right type. ORA-25216: invalid recipient, either NAME or ADDRESS must be specified Cause: Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list. Action: Specify a non-null NAME or ADDRESS for the recipient. ORA-25217: enqueue failed, visibility must be IMMEDIATE for queue string.string Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE. Action: Set visibility to IMMEDIATE. ORA-25218: enqueue failed, delay must be zero for queue string.string Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds. Action: Set delay to zero. ORA-25219: enqueue failed, sequence deviation not allowed for queue string.string Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified. Action: Do not specify sequence deviation. ORA-25220: enqueue failed, signature not specified for a non-repudiable queue Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature Action: Give the signature ORA-25221: enqueue failed, signature specified queue not supporting non-repudiation Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation Action: Remove the signature ORA-25222: enqueue failed, complete sender info. not provided for a queue supporting non-repudiation Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation Action: Provide the sender information ORA-25223: user_data type used is not supported Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type. Action: Enqueue the message again with data of raw or object type. ORA-25224: sender name must be specified for enqueue into secure queues Cause: An attempt was made to enqueue into a secure queue without specifying a sender name. Action: Enqueue the message with sender name specified. ORA-25225: invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED Cause: An invalid parameter has been specified for DEQUEUE_MODE. Action: Specify either REMOVE, BROWSE or LOCKED. ORA-25226: dequeue failed, queue string.string is not enabled for dequeue Cause: The queue has not been enabled for dequeue. Action: Enable the queue using START_QUEUE. ORA-25228: timeout or end-of-fetch during message dequeue from string.string Cause: User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved. Action: Try dequeue again with the appropriate WAIT_TIME or the FIRST_MESSAGE option. ORA-25229: error on transformation of message string string Cause: There was an error when transforming a message at enqueue, dequeue or propagation time. Action: Correct the transformation function. ORA-25230: invalid value string, WAIT should be non-negative Cause: A negative value has been specified for WAIT. Action: specify a non negative value or FOREVER. ORA-25231: cannot dequeue because CONSUMER_NAME not specified Cause: A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options. Action: Specify the CONSUMER_NAME in the dequeue options. ORA-25232: duplicate recipients specified for message Cause: An enqueue was performed with duplicate queue agents in the recipients parameter. Action: Remove the duplicate queue agent and retry the call. ORA-25233: invalid parameter specified for NAVIGATION Cause: An invalid parameter has been specified for NAVIGATION. Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that satisifies the criterion, NEXT_MESSAGE for dequeuing the next message that satisifies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction. ORA-25234: NEXT_TRANSACTION navigation option invalid for queue table string.string Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping. Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled. ORA-25235: fetched all messages in current transaction Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction. Action: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again. ORA-25236: buffer too small for user data Cause: The variable or buffer used for the out parameter payload is too small for the user data dequeued. Action: Increase the size of the buffer or the size of the variable. Maximum size allowed is 32K. ORA-25237: navigation option used out of sequence Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages. Action: Reset the dequeuing position using the FIRST_MESSAGE naviagtion option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION option. ORA-25238: too many recipients specified for message destination string Cause: An ENQUEUE was performed with more than 32 recipients for the given destination (address). Action: Reduce the number of recipients to 32 or less, and retry the call. ORA-25239: message ID not supplied when dequeuing from exception queue string.string Cause: An attempt was made to dequeue from a release 8.0-compatible exception queue without including a message ID in the dequeue options. Action: Check the application to ensure that the queue name has been specified correctly. If the queue name is correct supply a message ID when dequeuing from a release 8.0-compatible exception queue. Otherwise, upgrade the queue_table containing the queue to release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. ORA-25240: message ID and dequeue condition/correlation ID specified in dequeue options Cause: An attempt was made to dequeue by including both a message ID and a dequeue condition/correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either message ID or dequeue condition/correlation ID, or neither. Action: To dequeue a message, specify a message ID or a dequeue condition/correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue"s sort order, then do not specify either the message ID or dequeue condition/correlation ID in the dequeue options. ORA-25241: cannot change correlation ID from string to string without FIRST_MESSAGE option Cause: An attempt was made to change the correlation ID while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing. Action: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option. ORA-25242: cannot change subscriber name from string to string without FIRST_MESSAGE option Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing. Action: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option. ORA-25243: CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers. Action: Specify only the message id in the dequeue options to dequeue a message from an exception queue. ORA-25244: dequeue index key not found, QUEUE string, rowid string Cause: An internal error was encountered. There may be an inconsistency in the queue table index. Action: Contact your Oracle customer support representative. You may need to provide the trace file and information about reproducing the error. ORA-25245: agent name cannot be specified if address is a single-consumer queue or an exception queue Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue. Action: Do not specify the agent name. ORA-25246: listen failed, the address string is an 8.0 style exception queue Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call. Action: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list. ORA-25247: %s is not a recipient of specified message Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message id. Action: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message id. ORA-25248: duplicate agent specified in the agent list Cause: An agent was specified more than once in the agent list of the LISTEN call. Action: Remove the duplicate agent specification(s), and retry the call. ORA-25249: dequeue failed, dequeue not allowed for queue string.string Cause: An attempt was made to dequeue from a non-persistent queue. Action: Dequeue from a different queue. ORA-25250: Cannot specify a remote recipient for the message Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address. Action: Do not specify the address field or specify the queue which is the target of the enqueue ORA-25251: exceeded maximum number of recipients for message Cause: An attempt was made to issue an ENQUEUE call that exceeded the the maximum number (1024) of recipients per message. Action: Reduce the number of recipients to 1024 or less, and retry the call. ORA-25252: listen failed, the address string is a non-persistent queue Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call. Action: Specify a normal queue as address for the agent, and retry the the LISTEN call. ORA-25253: listen failed, queue string.string is not enabled for dequeue Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call. Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call. ORA-25254: time-out in LISTEN while waiting for a message Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list. Action: Try the LISTEN call with an appropriate time-out. ORA-25255: incorrect subscription string string Cause: An incorrect subscription string was specified with OCIRegister. Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE form. ORA-25256: consumer cannot be specified with a single-consumer queue or an exception queue Cause: An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue. Action: Do not specify the consumer in the subscription string. ORA-25257: consumer must be specified with a multi-consumer queue Cause: An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string. Action: Specify a consumer in the subscription string. ORA-25258: cannot register for notifications on an 8.0 style exception queue Cause: An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister. Action: Specify a normal queue or a non-persistent queue. ORA-25259: cannot specify protocol for agent Cause: The user specified the protocol attribute for an agent in the agent list. Action: Do not specify the protocol attribute of the agent object type. ORA-25260: AQ latch cleanup testing event Cause: N/A. Action: event used for AQ statistics latch cleanup testing. ORA-25261: JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation. Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation. ORA-25262: agent name cannot be NULL if address is a multi-consumer queue Cause: The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue. Action: Specify a non-NULL name for the agent. ORA-25263: no message in queue string.string with message ID string Cause: An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue. Action: Try dequeue again with a valid message ID. ORA-25264: cant get signature for this queue Cause: An attempt was made to dequeue the signature from this queue, which is not reciever non-repidiable. Action: Try dequeue again without the get signature option ORA-25265: specified signature for a queue which does not support reciever non-repudiation Cause: An attempt was made to dequeue the message from a queue which does not support reciever non-repudiation, but the signature was specified for verification Action: Try dequeue again without the signature ORA-25266: didnt try to dequeue by message id. with the signature Cause: The signature was specified for a queue, but the dequeue was not done by message id. Action: Try dequeue again by message id. ORA-25267: didnt specify the signature for a reciever non-repudiable queue Cause: The signature was not specified for a reciever non-repudiable queue Action: Try dequeue again along with the signature ORA-25268: didnt dequeue in browse mode with get signature option Cause: The dequeue was not performed in browse mode with get signature option Action: Try dequeue again in browse mode ORA-25269: cant specify sognature with get signature option Cause: The signature is not required for the dequeue with get signature option Action: Try dequeue again without the signature in dequeue options ORA-25270: sender info does not match with the actual sender of the message Cause: The sender info. and the message id. do not match Action: Try dequeue again without the signature in dequeue options ORA-25271: queue table not found for the given queue Cause: The queue table does not exist for the given queue Action: Provide the right queue name ORA-25272: Signature does not exist for the given reciever and message id. Cause: Signature does not exist for the given reciever and message id. Action: Check the message id. and the reciever"s information ORA-25273: AQ QMN process alternate cleanup event Cause: N/A. Action: event used for AQ QMN alternate cleanup mode. ORA-25274: AQ Buffered Queue event Cause: N/A. Action: event used for AQ Buffered Queue mode. ORA-25275: Test support for buffered queues Cause: internal use only Action: none. ORA-25276: table specified is not a queue table Cause: An invalid queue table name is specified. Action: Check the dictionary views to see if the table is a queue table. ORA-25277: cannot grant or revoke object privilege on release 8.0 compatible queues Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues. Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege. ORA-25278: grantee name cannot be NULL Cause: An attempt was made to specify NULL for the grantee parameter. Action: Specify a valid grantee parameter. ORA-25279: dequeue as select not supported before 8.2 Cause: Dequeue as select not supported before 8.2. Action: Dont use select condition while dequeuing ORA-25280: complete sender information not provided to non-repudiate sender Cause: complete sender information not provided to non-repudiate sender Action: Provide the complete sender information ORA-25281: complete reciever information not provided to non-repudiate reciever Cause: complete reciever information not provided to non-repudiate reciever Action: Provide the complete reciever information ORA-25282: message id. not provided for non-repudiation Cause: message id. was not provided Action: Provide the message id. ORA-25283: either agent"s name or address needed for non-repudiation Cause: neither agent"s name nor address provided for non-repudiation" Action: Provide the agent info. ORA-25284: Invalid value string for string Cause: An Invalid value or NULL was specified for the parameter. Action: Check the documentation for valid values. ORA-25285: Invalid value string for array_mode Cause: An Invalid value or NULL was specified for the array_mode. Action: Check the documentation for valid values. ORA-25286: Invalid number of elements in the message properties array Cause: Number of elements in the message properties array do not match the number of elements in the payload array. Action: Create a message property array with one element (that applies for all the elements in the payload array) or create a message property array with the same number of elements as there are in the payload array. ORA-25287: Invalid value string, string should be non-negative Cause: An Invalid value or NULL was specified for the parameter. Action: Specify a non negative integer. ORA-25288: AQ HTTP propagation encountered error, status-code number, string Cause: AQ propagation"s HTTP request to the propagation servlet at the specified address encountered an error Action: Specify a valid address in the connect string of the propagation destination dblink, the dblink user has the correct permissions, check if the AQ propagation servlet was properly installed. ORA-25289: Buffer Already Exists Cause: Buffer already exists for the specified queue. Action: None ORA-25290: Cannot complete operation on queue string with existing messages Cause: Queue already has messages. Cannot complete operation Action: Truncate the queue before adding/dropping a buffer ORA-25291: Buffer does not exist for the specified queue Cause: Buffer does not exist for the specified queue Action: Operation on the buffer cannot be performed. create the buffer ORA-25292: Buffer operations are not supported on the queue Cause: Buffer operations are not supported on the specified queue type Action: Buffered operations are only supported on to 8.1 style queues, which do not have transaction grouping. ORA-25293: Lob attributes must be null for buffered operations Cause: Enqueue of a buffered message with a non-null lob attribute was attempted Action: Set the lob attributes to null before enqueuing the buffered message ORA-25294: Cannot propagate user buffered messages to a database with version lower than 10.2 Cause: Propagation of user buffered messages was attempted to a database with version lower than 10.2. Action: Do not propagate buffered messages to the database. ORA-25295: Subscriber is not allowed to dequeue buffered messages Cause: Subscriber is only allowed to dequeue persistent messages Action: Drop the subscriber and re-create it, or dequeue only persistent messages for the subscriber ORA-25296: Queue Table string has a buffered queue string Cause: Buffered message was enqueued by specifying delay or sequence deviation. Action: Do not specify delay of sequence deviation when enqueuing buffered messages. ORA-25298: Only immediage visibility mode supported for buffered message enqueue or dequeue Cause: A visibility of dbms_aq.ON_COMMIT was supplied with the buffered message enqueue or dequeue Action: Supply a visibility of dbms_aq.IMMEDIATE ORA-25299: Invalid message delivery_mode Cause: Invalid value was specified for delivery mode Action: Specify dbms_aq.BUFFERED or dbms_aq.PERSISTENT during Enqueue or dbms_aq.BUFFERED, dbms_aq.PERSISTENT or dbms_aq.PERSISTENT_OR_BUFFERED during Dequeue and Listen. ORA-25300: Cannot drop buffer for queue with buffered subscribers Cause: Cannot drop buffer for queue with buffered subscribers Action: Either drop buffered subscribers or forcibly drop the buffer ORA-25301: Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2 Cause: Enqueue or dequeue of user buffered messages was attempted to queues in a database with version lower than 10.2. Action: Do not attempt to enqueue or dequeue user buffered messages. ORA-25302: Operation not possible for non-buffered queue string Cause: Last enqd/ackd message is only supported for buffered queues Action: The operation is not supported. ORA-25303: Buffered operation allowed only on the owner instance Cause: Operation was not performed on the owner instance. Action: Perform operation on the owner instance. ORA-25304: Cannot use priority order queues for capture LCRs Cause: Capture LCRs can only use commit time or enqueue time ordered queues. Action: Use the appropriate type of queue for captured LCRs. ORA-25305: enqueue failed, expiration must be zero for queue string.string Cause: An attempt was made to enqueue to a buffered queue with expiration greater than zero seconds. Action: Set expiration to zero. ORA-25306: Cannot connect to buffered queue"s owner instance Cause: cannot connect to the owner instance of the buffered queue Action: set listener information in REMOTE_LISTENERS or LOCAL_LISTENERS initialization parameter. ORA-25307: Enqueue rate too high, flow control enabled Cause: Subscribers could not keep pace with the enqueue rate. Action: Try enqueue after sleeping for some time. ORA-25310: Subscriber is Notification only; dequeue not supported Cause: Notification only subscribers are not allowed to dequeue. Action: Recreate subscriber if necessary. ORA-25311: %s not supported for non-persistent queue Cause: Specified QOS is not supported for non-persistent queues. Action: Specify the right QOS. ORA-25312: Cannot specify nonzero sender protocol Cause: Sender protocol was specified during an enqueue operation. Action: Specify the enqueue sender protocol as null or zero. ORA-25313: a queue may not subscribe to itself for propagation Cause: The specified subscriber had a NULL name and an address equal to the queue name. Action: Provide a valid subscriber and retry the operation. ORA-25314: a commit-time queue table cannot be migrated to 8.0 Cause: An attempt was made to migrate a commit-time queue table to an unsupported compatibility level. Action: Provide an appropriate compatibility level, and retry the operation. ORA-25315: unsupported configuration for propagation of buffered messages Cause: An attempt was made to propagate buffered messages with the database link pointing to an instance in the destination database which is not the owner instance of the destination queue. Action: Use queue to queue propagation for buffered messages. ORA-25316: Late in the current transaction to begin an Enqueue/Dequeue operation Cause: Check if the Enqueue/Dequeue operation is performed via triggers on Materialized Views which isn"t supported. Action: Triggers on materialized views aren"t supported. Workarounds are on-demand materialized views or execution of trigger code within an autonomous txn. ORA-25321: enqueue failed, user property specified but queue string.string is not an 8.1 style queue Cause: user properties can only be specified when enqueueing into 8.1 style queues. Action: Specify an 8.1 style queue or pass user property as NULL. ORA-25326: Array string operation failed for message at index string Cause: Array operation fails for the message at specified index. Look at the remainder of the error stack to see what the problem was. Action: Fix cause of error and retry array operation. ORA-25327: Array size is invalid Cause: Array size must be a positive, non-zero integer. Action: Use corrected array size and retry array operation. ORA-25328: %s argument size string is smaller than array size Cause: The size of the argument is smaller than the given array size. Action: Lower array size or use a larger sized input argument. ORA-25329: AQ array operations not allowed on 8.0 queues Cause: An array enqueue/dequeue was attempted on an 8.0 queue. Action: Use single enqueue/dequeue with this queue. ORA-25330: PL/SQL associative arrays may not be used with AQ array operations Cause: A PL/SQL associative array was provided for the payload parameter in an enqueue/dequeue array operation. Action: Use VARRAY or NESTED TABLE types with AQ array operations. ORA-25331: cannot downgrade because there are commit-time queue tables Cause: An attempt was made to downgrade a database that has commit-time queue tables. Action: Drop all commit-time queue tables before attempting the downgrade. ORA-25332: Invalid release value string for queue table compatible parameter Cause: The release level given for the queue table compatible parameter is invalid Action: Specify a valid release value for the queue table compatible parameter ORA-25333: Buffered Queue to Queue propagation did not connect to the correct instance Cause: Queue to Queue propagation for buffered messages didn"t connect to the correct instance, most likely because service was not started for the destination queue. Action: No user action is required. Propagation will start the service for the destination queue and retry. ORA-25334: Buffered propagation must restart as the destination queue was recreated/moved Cause: Buffered propagation destination queue was recreated or its ownership was moved to another instance during propagation. Action: No user action is required. Propagation will reinitialize its metadata and retry. ORA-25335: AQ array operations not allowed for buffered messages Cause: An array enqueue/dequeue was attempted for buffered messages Action: Use single enqueue/dequeue for buffered messages or an array size of one. ORA-25336: Cannot contact instance string during Streams AQ operation Cause: The specified instance was not responding to AQ requests. Action: Set parameter aq_tm_processes to a non-zero value. If the problem persists, contact Oracle Support Services. ORA-25337: Cannot propagate in queue-to-queue mode to a database with version lower than 10.2 Cause: Remote subscriber with queue_to_queue mode set to TRUE was added. The remote subscriber is on a database version lower than 10.2. Propagation was scheduled to a destination database with version lower than 10.2. Action: Remove the remote subscriber with queue_to_queue mode and add the subscriber back with queue_to_queue set to FALSE. Unschedule the queue-to-queue propagation and schedule propagation in queue-to-dblink mode. ORA-25350: maximum number of concurrent transaction branches exceeded Cause: the limit on the number of concurrent transaction branches has been reached Action: Increase the INIT.ORA parameter "transactions" and restart the system. ORA-25351: transaction is currently in use Cause: The transaction is currently used by a different session. Action: Do not switch to a transaction attached to some other session. ORA-25352: no current transaction Cause: The user session is not attached to any transaction. Action: Do not attempt to detach when there is no current transaction. ORA-25353: branch marked for deletion Cause: The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed. Action: No action is required for the branch to be deleted. ORA-25400: must replay fetch Cause: A failure occured since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches. Action: This is an internally used error message and should not be seen by the user. ORA-25401: can not continue fetches Cause: A failure occured since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches. Action: Reexecute the statement and start fetching from the beginning ORA-25402: transaction must roll back Cause: A failure occured while a transaction was active on this connection. Action: The client must roll back. ORA-25403: could not reconnect Cause: The connection to the database has been lost, and attempts to reconnect have failed. Action: Manually reconnect. ORA-25404: lost instance Cause: The primary instance has died. Action: This is an internally used error message and should not be seen by the user. ORA-25405: transaction status unknown Cause: A failure occured while a transaction was attempting to commit. Failover could not automatically determine instance status. Action: The user must determine the transaction"s status manually. ORA-25406: could not generate a connect address Cause: Failover was unable to generate an address for a backup instance. Action: Contact Oracle customer support. ORA-25407: connection terminated Cause: The connection was lost while doing a fetch. Action: This is an internally used error message and should not be seen by the user. ORA-25408: can not safely replay call Cause: The connection was lost while doing this call. It may not be safe to replay it after failover. Action: Check to see if the results of the call have taken place, and then replay it if desired. ORA-25409: failover happened during the network operation,cannot continue Cause: The connection was lost when fetching a LOB column. Action: Failover happened when fetching LOB data directly or indirectly. Please replay the top level statement. ORA-25425: connection lost during rollback Cause: The connection was lost while issuing a rollback and the application failed over. Action: The connection was lost and failover happened during rollback. If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine pending_trans$ to determine if "rollback force" is required. ORA-25426: remote instance does not support shared dblinks Cause: A shared dblink is being used to connect to a remote instance that does not support this feature because it is an older version. Action: Use a normal dblink if you need to connect to this instance. ORA-25427: cannot downgrade database links after database link data dictionary has been upgraded Cause: An attempt was made to downgrade after the upgrade of the database link data dictionary. Action: Drop the database links before attempting the downgrade. ORA-25436: invalid table alias: string Cause: An attempt to evaluate was made, which failed because one of the table values specified had an invalid alias. Action: Check the valid table aliases in the evaluation context, and try again with a valid alias. ORA-25437: duplicate table value for table alias: string Cause: An attempt to evaluate was made, which failed because some of the table values specified had the same table alias. Action: Check the table values specified, and try again with only one value per table. ORA-25438: invalid variable name: string Cause: An attempt to evaluate was made, which failed because one of the variable values specified had an invalid name. Action: Check the valid variable names in the evaluation context, and try again with a valid name. ORA-25439: duplicate variable value for variable: string Cause: An attempt to evaluate was made, which failed because some of the variable values specified had the same variable name. Action: Check the variable names specified, and try again with only one value per variable. ORA-25440: invalid table alias: string Cause: An attempt to evaluate was made, which failed because one of the column values specified had an invalid table alias. Action: Check the valid table aliases in the evaluation context, and try again with a valid name. ORA-25441: duplicate column value for table alias: string Cause: An attempt to evaluate was made, which failed because one of the column values supplied a value for a table alias, which already had a table value supplied. Action: Check the table and column values specified, and try again with either a table value or column values for each table alias. ORA-25442: too many column values for table alias: string Cause: An attempt to evaluate was made, which failed because too many column values were supplied for the specified table alias. Action: Check the column values specified, and try again with the right number of column values. ORA-25443: duplicate column value for table alias: string, column number: string Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column number. Action: Check the column values specified, and try again with only one column value for each table alias, and column number. ORA-25444: invalid ROWID: string for table alias: string Cause: An attempt to evaluate was made, which failed because an invalid ROWID was supplied for the specified table alias. Action: Check the column values specified, and try again with only one column value for each table alias, and column number. ORA-25445: invalid column number: string for table alias: string Cause: An attempt to evaluate was made, which failed because an invalid column number was supplied for the specified table alias as a part of a column value. Action: Check the column values specified, and try again with a valid column number. ORA-25446: duplicate column value for table alias: string, column: string Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column name. Action: Check the column values specified, and try again with only one column value for each table alias, and column name. ORA-25447: encountered errors during evaluation of rule string.string Cause: An attempt to evaluate was made, which failed during the evaluation of the specified rule. Action: Check the rule and the values passed to evaluate, and try again with valid values. ORA-25448: rule string.string has errors Cause: An attempt to load the specified rule failed due to errors in the rule. Action: Check the rule and retry the operation. ORA-25449: invalid variable name: string Cause: An attempt to evaluate was made, which failed because one of the attribute values specified had an invalid variable name. Action: Check the valid variable names in the evaluation context, and try again with a valid name. ORA-25450: error string during evaluation of rule set string.string Cause: The specified error occurred during evaluation of the rule set. Action: Check the error and take appropriate action. ORA-25451: too many attribute values for variable: string Cause: An attempt to evaluate was made, which failed because too many attribute values were supplied for the specified variable. Action: Check the attribute values specified, and try again with the right number of attribute values. ORA-25452: duplicate attribute value for variable: string, attribute: string Cause: An attempt to evaluate was made, which failed because duplicate attribute values were supplied for the specified variable and attribute name. Action: Check the attribute values specified, and try again with only one attribute value for each variable, and attribute name. ORA-25453: invalid iterator: string Cause: An attempt to get rule hits or to close an iterator was made, which failed because an invalid iterator was passed in. Action: Check the iterator, and try again with a valid iterator. ORA-25454: error during evaluation of rule set: string.string for iterator: string Cause: An attempt to get rule hits for an iterator was made, which failed because of an error in evaluation of the specified rule set. Action: Check the validity of the rule set and try again. ORA-25455: evaluation error for rule set: string.string, evaluation context: string.string Cause: An attempt to evaluate the specified rule set using the evaluation context specified failed due to some errors. Action: Check additional errors signalled to determine the problem. ORA-25456: rule set was modified or evaluation terminated for iterator: string Cause: An attempt to get rule hits was made, which failed because the underlying rule set was modified after the iterator was returned. Action: Try again after re-evaluating the rule set. ORA-25457: evaluation function string returns failure Cause: The specified evaluation function returned a failure during evaluation, causing evaluation to terminate. Action: Check arguments to evaluate and retry. ORA-25461: rule set not specified Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null. Action: Check the rule set name, and try again with a valid name. ORA-25462: evaluation context not specified Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null. Action: Check the evaluation context name, and try again with a valid name. ORA-25463: table alias not specified Cause: An attempt to evaluate was made, which failed because one of the table values specified had a NULL alias name. Action: Check the list of table values, and try again with a valid alias name. ORA-25464: ROWID not specified for table alias: string Cause: An attempt to evaluate was made, which failed because the table value for the specified table alias had a NULL ROWID. Action: Check the list of table values, and try again with a valid ROWID. ORA-25465: variable name not specified Cause: An attempt to evaluate was made, which failed because one of the variable values specified had a NULL variable name. Action: Check the list of variable values, and try again with a valid variable name. ORA-25466: data not specified for variable name: string Cause: An attempt to evaluate was made, which failed because the variable value for the specified variable name had NULL data. Action: Check the list of variable values, and try again with valid data. ORA-25467: table alias not specified Cause: An attempt to evaluate was made, which failed because one of the column values specified had a NULL alias name. Action: Check the list of column values, and try again with a valid alias name. ORA-25468: column name not specified for alias: string Cause: An attempt to evaluate was made, which failed because one of the column values for the specified alias name had a NULL column name. Action: Check the list of column values, and try again with a valid column name. ORA-25469: data not specified for alias: string column name: string Cause: An attempt to evaluate was made, which failed because the column value for the specified alias and column name had NULL data. Action: Check the list of column values, and try again with valid data. ORA-25470: duplicate attribute value for variable: string Cause: An attempt to evaluate was made, which failed because one of the attribute values supplied a value for a variable, which already had a variable value supplied. Action: Check the variable and attribute values specified, and try again with either a variable value or attribute values for each variable. ORA-25471: attribute name not specified for variable: string Cause: An attempt to evaluate was made, which failed because one of the attribute values for the specified variable had a NULL attribute name. Action: Check the list of attribute values, and try again with a valid attribute name. ORA-25472: maximum open iterators exceeded Cause: The open rule hit iterators in the session exceeded 2 * OPEN_CURSORS. Action: Close some rule hit iterators. ORA-25473: cannot store string in rule action context Cause: The user attempted to put unsupported data types, such as LOBs and evolved ADTs, into the rule action context. Action: Use only supported data types in rule action context. ORA-25500: database is not open Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command. Action: Open the database and retry this command. ORA-25501: ALTER SYSTEM QUIESCE RESTRICTED command failed Cause: Database resource manager failed to change plan. Action: Look at the alert logs to see detailed description of the error. ORA-25502: concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER SYSTEM UNQUIESCE command running in the system. Action: Contact the database administrator who is responsible for the concurrent command. ORA-25503: cannot open database because the database is being quiesced Cause: Database cannot be opened because the system is being or has been quiesced. Action: Open the database after the system has been quiesced. ORA-25504: the system is already in quiesced state Cause: Cannot quiesce the system because the system is already quiesced. Action: none ORA-25505: the system is not in quiesced state Cause: Cannot unquiesce the system because the system is not in quiesced state. Action: none ORA-25506: resource manager has not been continuously on in some instances Cause: Cannot quiesce the system because resource manager has not been continuously on since startup in this or some other instances. Action: none ORA-25507: resource manager has not been continuously on Cause: Cannot quiesce the system because resource manager has not been continuously on since startup. Action: none ORA-25508: database is not mounted Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE command. Action: Mount the database and retry this command. ORA-25509: operation on "string"."string".string not allowed Cause: A column has been added to a replicated table, but replication support processing has not completed. Action: Wait until replication support processing has completed before updating the column ORA-25526: bad format of _DB_MTTR_SIM_TARGET: string Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR. Action: Alter the value of _DB_MTTR_SIM_TARGET. ORA-25527: bad format of _DB_MTTR_SIM_TARGET Cause: One value in _DB_MTTR_SIM_TARGET is empty. Action: Set the value of _DB_MTTR_SIM_TARGET properly. ORA-25528: too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET. Action: Alter the value of _DB_MTTR_SIM_TARGET. ORA-25530: FAST_START_MTTR_TARGET is not specified Cause: An attempt to start MTTR advisory was made, which failed because FAST_START_MTTR_TARGET was not specified. Action: Set FAST_START_MTTR_TARGET. ORA-25531: MTTR specified is too small: string Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory. Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR. ORA-25532: MTTR specified is too large: string Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too large for MTTR advisory. Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR. ORA-25533: FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified Cause: An attempt to start MTTR advisory was made, which failed because either FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL was specified. Action: Set FAST_START_IO_TARGET and LOG_CHECKPOINT_INTERVAL to 0. ORA-25534: _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified Cause: An attempt to start MTTR advisory was made, which failed because _MEAN_TIME_TO_CLUSTER_AVAILABILITY was specified. Action: No action required. ORA-25950: missing where clause in join index specification Cause: An attempt to create a join index was made, which failed because no valid where clause was found. Action: Ensure that a where clause with valid join conditions is specified in the create index statement. ORA-25951: join index where clause cannot contain OR condition Cause: An attempt to create a join index was made, which failed because there was an OR branch in the where clause. Action: Reformulate the where clause without using ORs. ORA-25952: join index must only contain inner equi-joins Cause: An attempt to create a join index was made, which failed because it included a predicate which wasn"t an equi-inner join. Action: Remove the inappropriate predicate. ORA-25953: join index cannot be a functional index Cause: An attempt to create a join index was made, which failed because a functional index was requested or necessary (such as is the case for indexing columns using timezone). Action: Remove any functional indexing columns. ORA-25954: missing primary key or unique constraint on dimension Cause: An attempt to create a join index was made, which failed because one or more dimensions did not have an appropriate constraint matching the join conditions. Action: Ensure that the where clause is correct (contains all of the constraint columns) and that an enforced constraint is on each dimension table. ORA-25955: all tables must be joined in the where clause Cause: An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause. Action: Ensure that the where clause contains all from clause tables. ORA-25956: join index cannot be created on tables owned by SYS Cause: An attempt to create a join index was made, which failed because one of the tables was owned by SYS. Action: Ensure that no join index related table is owned by SYS. ORA-25957: join index where clause cannot contain cycles Cause: An attempt to create a join index was made, which failed because the where clause contains a cycle. Action: Ensure that the where clause is in the form of a star or snowflake schema. ORA-25958: join index where clause predicate may only contain column references Cause: An attempt to create a join index was made, which failed because a predicate in the where clause contained something other than a simple column. Action: Ensure that the where clause only contains columns. ORA-25959: join index must be of the bitmap type Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used. Action: Make the index a bitmap index. ORA-25960: join index cannot be based on a temporary table Cause: An attempt to create a join index was made, which failed because one of the tables was temporary. Action: Ensure no underlying tables are temporary. ORA-25961: join index prevents dml cascade constraint operation Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time. Action: Drop the join index or remove the constraint. ORA-25962: join index prevents multitable insert or merge Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index. Action: Drop the join index. ORA-25963: join index must be created on tables Cause: An attempt to create a join index was made, which failed because the from clause contains non table object. Action: Ensure that the from clause only contains tables. ORA-25964: column type incompatible with join column type Cause: The datatype of the join column is incompatible with the datatype of the joined column. Action: Select a compatible datatype for the join column. ORA-25965: fact table must be included in the from clause Cause: An attempt to create a join index was made, which failed because the from clause does not contain the fact table. Action: Ensure that the from clause contains the fact table. ORA-25966: join index cannot be based on an index organized table Cause: An attempt to create a join index was made, which failed because one of the tables was an index organized table. Action: Ensure no underlying tables are index organized. ORA-26000: partition load specified but table string is not partitioned Cause: The Loader control file contains a PARTITION clause but the table being loaded is not partitioned. Action: Remove the partition specification from the SQL*Loader control file and retry the load. ORA-26001: Index string specified in SORTED INDEXES does not exist on table string Cause: A nonexistent index was specified in the SORTED INDEXES clause. Action: Do not specify as a SORTED INDEX. ORA-26002: Table string has index defined upon it. Cause: Parallel load was specified into a table which has index defined upon it. Action: Drop index(es) defined upon table, or don"t use parallel load, or use SKIP_INDEX_MAINTENANCE option. ORA-26003: parallel load not supported for index-organized table string. Cause: Parallel load is not supported for index-organized tables. Action: load the index-organized table without the PARALLEL option. ORA-26004: Tables loaded through the direct path may not be clustered Cause: User attempted to load a clustered table via the direct path. Action: Use the conventional path. ORA-26005: Invalid handle for direct path load Cause: In direct path load, the handle passed in does not match the type listed. Action: Verify the handle and type are correct. ORA-26006: Incorrect bind variable in column string"s sql expression - string Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names. Action: Verify all the input arguments are listed in the expression as bind variables, and all the bind variables are listed as input arguments to the expression. Or verify that there were no errors in executing the OCI statements when getting the bind variable list. ORA-26007: invalid value for SETID or OID column Cause: The value passed in a Direct Path API stream for a column containing a SETID or OID has an invalid value. SETIDs and Object IDs must be either 16 bytes of RAW data or 32 bytes of hexidecimal characters. Action: Regenerate the Direct Path API stream with a valid value for the SETID column. ORA-26008: Invalid syntax or bind variable in SQL string for column string. string Cause: See following error message for more information. A SQL string cannot have quoted strings improperly terminated. A bind variable in a SQL string cannot have a length of 0, cannot exceed maximum length of 30 characters, and cannot be missing a double quote. Action: Fix the SQL string. See following error for more information. ORA-26010: Column string in table string is NOT NULL and is not being loaded Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected. Action: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file. ORA-26011: Cannot load type string into column string in table string Cause: A column can only store data of type declared for that column. And a substitutable column can only store data of valid subtypes of the supertype declared for that column. Action: Check that the type or subtype specified is valid for that column. ORA-26013: List allocated may not be big enough Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed. Action: Contact Oracle Customer Support. ORA-26014: unexpected error on string string while retrieving string string Cause: The SQL error was returned from an OCIStmtExecute call. Action: Correct the SQL error that was returned. ORA-26015: Array column string in table string is not supported by direct path Cause: User attempted to load an array column via the direct path. Action: Use the conventional path. ORA-26017: global indexes not allowed for direct path load of table partition string Cause: Global indexes are defined on a table when direct path loading a single partition of the table. Action: none ORA-26018: Column string in table string does not exist Cause: Column specified in the loader control file does not exist. Action: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is wrong. ORA-26019: Column string in table string of type string not supported by direct path Cause: The Specified column of SQL column type %s is not supported by the direct path loader. Action: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL. ORA-26020: index string.string loaded successfully with string keys Cause: Non-partitioned index information put to loader log file. Action: None. Information only. ORA-26021: index string.string partition string loaded successfully with string keys Cause: Partitioned index information put to loader log file. Action: None. Information only. ORA-26022: index string.string was made unusable due to: Cause: A Non-partitioned index was made index unusable due to the error displayed below this error. Action: Depending on the error, either rebuild the index, or drop and re-create it. ORA-26023: index string.string partition string was made unusable due to: Cause: A partition of a partitioned index was made index unusable due to error displayed below this error. Action: Depending on the error, either rebuild the index partition, or drop and re-create the entire index. ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment * was in unusable state prior to the beginning of the load. Action: Informational only. User will need to either rebuild the index * or index partition, or re-create the index. ORA-26025: SKIP_INDEX_MAINTENANCE option requested Cause: User requested that index maintenance be skipped on a direct path load. Action: The listed index was put into Index Unusable state due to the user requesting that index maintenance be skipped. Either rebuild the index or index partitions, or drop and re-create the index. ORA-26026: unique index string.string initially in unusable state Cause: A unique index is in IU state (a unique index cannot have * index maintenance skipped via SKIP_UNUSABLE_INDEXES). Action: Either rebuild the index or index partition, or use * SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. ORA-26027: unique index string.string partition string initially in unusable state Cause: A partition of a unique index is in IU state (a unique index * cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES). Action: Either rebuild the index or index partition, or use * SKIP_INDEX_MAINTENANCE if the client is SQL*Loader. ORA-26028: index string.string initially in unusable state Cause: An index is in IU state prior to the beginning of a direct * path load, it cannot be maintained by the loader. Action: Either rebuild the index, re-create the index, or use either * SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only). ORA-26029: index string.string partition string initially in unusable state Cause: A partition of an index is in IU state prior to the beginning * of a direct path load, it cannot be maintained by the loader. Action: Either rebuild index partition, re-create the index, or use either * SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (Sql*Loader only). ORA-26030: index string.string had string partitions made unusable due to: Cause: A logical index error occurred on a partitioned index which * affected one or more index partitions, which are listed below * this message. Action: The affected index partitions will have to be re-built, or, the * entire index dropped and re-created. ORA-26031: index maintenance error, the load cannot continue Cause: A index errror occurred during the index maintenance phase of * a direct path load. The load cannot continue. See error message * below this message. Action: See action for the error message which follows this one. ORA-26032: index string.string loading aborted after string keys Cause: An index error occurred during direct-load of an index-organized table. * Loading had to be aborted. No rows were loaded. Action: Check the key just following the number of keys mentioned above. * This key caused the index problem mentioned in an earlier message. * ORA-26033: column string.string encryption properties differ for source or target table Cause: The source and destination columns did not have the same * encryption properties. Action: For security reasons, check that the source and target table have * the same encryption properties. * ORA-26034: Column string does not exist in stream Cause: Column specified in the column list does not exist in the stream. Action: Make sure the column exists or remove it from the list. ORA-26035: Error attempting to encrypt or decrypt column Cause: An error occurred while attemping to encrypt or decrypt * a database column. Action: Verify correct encryption key was specified. * ORA-26036: subpartition load specified but table string is not subpartitioned Cause: The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned. Action: Remove the subpartition specification from the SQL*Loader control file and retry the load. ORA-26040: Data block was loaded using the NOLOGGING option Cause: Trying to access data in block that was loaded without * redo generation using the NOLOGGING/UNRECOVERABLE option Action: Drop the object containing the block. ORA-26041: DATETIME/INTERVAL datatype conversion error Cause: The column could not be converted from DATETIME * datatype to internal DATETIME/CHARACTER datatype. Action: Contact Oracle Customer Support. ORA-26045: REF column string expects string arguments; found string. Cause: The number of arguments for the REF column is incorrect. Action: Specify the correct number of input arguments for REFs. 1. Unscoped system-generated REFs can have exactly 1 or 2 input arguments. a) It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through OCI_DIRPATH_EXPR_REF_TBLNAME. b) It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME. 2. Scoped system-generated REFs can have 1 or 2 input arguments. Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it"s still accepted. 3. Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments. Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it"s still accepted. ORA-26046: REF column string expects scoped table name string; user passed in string. Cause: The scoped table name passed in by the user does not match the name in the schema. Action: Specify the correct table name for the scoped REF column. ORA-26048: Scoped REF column has wrong table name. Cause: The scoped table name passed in by the user does not match the name in the schema. Action: Specify the correct table name for the scoped REF column. ORA-26049: Unscoped REF column has non-existent table name. Cause: The table name passed in by the user does not exist in the schema. Action: Specify a valid table name for the unscoped REF column. ORA-26050: Direct path load of domain index is not supported for this column type. Cause: Direct path can not load a domain index of that column type. Action: Drop the index and try again or load using conventional path. ORA-26051: internal error parsing packed decimal format string Cause: A packed decimal field with a non-zero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field"s precision and scale specifications. Direct path loader encountered an error in creating this format string. Action: Examine the packed decimal field"s precision and scale specifications and make sure that they contain valid values. ORA-26052: Unsupported type number for SQL expression on column string. Cause: The direct path api does not support a SQL expression on a column of that type. Action: Make sure the types are correct. ORA-26053: Row was not loaded due to conversion error. Cause: The current row was not loaded due to a conversion error. Action: Continue with the load anyways. 260xx - 260xx Direct Path API ORA-26054: Direct Path Context prepared for a different mode than operation requested. Cause: The user prepared the direct path context for one operation (Load, Unload, Convert), but then tried to perform a different operation. Action: Make sure the direct path context mode and operation matches. ORA-26055: Invalid buffer specified for direct path unload Cause: The user specified a zero length or null buffer to be used for the Direct Path Unload operation. Action: Specify a valid buffer and length. ORA-26056: Requested direct path operation on a view is not supported. Cause: User attempted to unload or load from/into a view via direct path. Action: Unload from or load into a normal table. ORA-26057: Conversion is not necessary for this direct path stream. Cause: User attempted to convert a direct path stream that does not require conversion. Action: Load the stream without conversion it. ORA-26058: unexpected error fetching metadata for column string in table string Cause: The direct path API encountered an unexpected error while retrieving metadata for a column. Action: Contact Oracle support. ORA-26059: Data is too large for column string Cause: The direct path API encountered a column that can not be loaded because the input data is too large for a column. Action: Make the target column larger. ORA-26060: Can not convert type identifier for column string Cause: The direct path API encountered a type identifier for a column that can not be loaded because a mapping can not be found for the input value. Action: Verify the input data. ORA-26061: Concurrent direct unloads is not allowed. Cause: User attempted a direct unload when another is still in progress. Action: Complete the current direct unload before starting another. ORA-26062: Can not continue from previous errors. Cause: User attempted to continue a direct path load after receiving an error which indicates the load can not continue. Action: Address the original error that was returned. ORA-26063: Can not flashback to specified SCN value - Wrap: string Base: string. Cause: User specified an SCN which occurs before the last time the table definition was modified. Action: Specify a more recent SCN. ORA-26064: Invalid SCN specified - Wrap: string Base: string. Cause: User specified an invalid SCN. Action: Specify a valid SCN. ORA-26065: check constraint cannot reference column, string, in direct path load Cause: An enabled check constraint was found on a column stored as a lob. Action: Either disable the check constraint before loading the table data * using the direct path mode, or use the conventional path mode * instead. ORA-26076: cannot set or reset value after direct path structure is allocated Cause: Client attempted to set or reset the number of rows in a direct path * structure after it has already been allocated and initialized. * Attributes used is one of the following: * - OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array * - OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache * (default is 0) * - OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be * disabled on overflow (default is FALSE) Action: Set the following attributes before: * - OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array * - OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare * - OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare ORA-26077: direct path column array is not initialized Cause: Client attempted to allocate a column array for a direct path * function context before allocating a column array for the * table-level direct path context. Action: Allocate the table-level direct path context"s column array * via OCIHandleAlloc before allocating column arrays for * direct path function contexts. ORA-26078: file "string" is not part of database being loaded Cause: A parallel load file was specified which is not part * of the database. Action: Check filename and pathname for correctness. ORA-26079: file "string" is not part of table string.string Cause: A parallel load file was specified which is not in the * tablespace of the table being loaded. Action: Check to make sure that the specified parallel load file * is in the tablespace of the table being loaded. ORA-26080: file "string" is not part of table string.string partition string Cause: A parallel load file was specified which is not in the * tablespace of the table (partition, subpartition) being loaded. * When a partitioned table is being loaded, the file must be * in the tablespace of every partition or subpartition * (i.e. each (sub)partition must be in the same tablespace). Action: Specify a different parallel load file, or no file at all. ORA-26082: load of overlapping segments on table string.string is not allowed Cause: Client application is attempting to do multiple direct path load * operations on the same table, but the segments overlap. Action: Check the partition names (subname attribute of the direct path * context) being loaded. Make sure you are not loading a table, * and a partition of the same table. Make sure you are not * loading a partition, and a sub-partition within the same * partition. ORA-26083: unsupported direct path stream version string Cause: The stream version requested is not supported by the server. Action: Check to make sure that the VERSION attribute of the direct * stream is not being set to an invalid value. ORA-26084: direct path context already finished Cause: An OCIDirPathLoadStream operation was attempted after * OCIDirPathFinish was called. Once a direct path operaton * has been finished, no more data can be loaded. Action: Check program logic to make sure OCIDirPathLoadStream is * not called after OCIDirPathFinish. ORA-26085: direct path operation must start its own transaction Cause: A direct path operation is being attempted within a transaction * that has already been started. Action: Commit the transaction and Prepare the direct path operation again. ORA-26086: direct path does not support triggers Cause: A direct path operation is being attempted on a table which * has enabled triggers. Action: Disable the triggers on the table and try again. ORA-26088: scalar column "string" must be specified prior to LOB columns Cause: All scalar columns (i.e. non-LOB and non-LONG columns) must be * specified by the client of the direct path API prior to * specifying any LOB columns. Action: Specify all scalar columns prior to specifying any LOB columns. ORA-26089: LONG column "string" must be specified last Cause: A client of the direct path API specified a LONG column to be * loaded, but the LONG column was not the last column to be * specified. Action: Specify the LONG column last. ORA-26090: row is in partial state Cause: A direct path operation is being finished or a data save request * has been made, but the table for which the request is being made * on has a row in partial state. The row must be completed before * the segment high water marks can be moved. Action: Either complete the row, or abort the direct path operation. ORA-26091: requested direct path operation not supported Cause: A direct path operation was requested that is not supported Action: Do not use that operation. Currently, UNLOAD is not supported. ORA-26092: only LONG or LOB types can be partial Cause: A column which is not a LONG or LOB had the * OCI_DIRPATH_COL_PARTIAL flag associated with it. * Only LONG or LOB type columns can be loaded in pieces. Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column. ORA-26093: input data column size (number) exceeds the maximum input size (number) Cause: The user attempted to specify a column size (%d) that exceeded * the maximum allowable input size (%d)." Action: Make sure the input column metadata matches the column definition. ORA-26094: stream format error: input column overflow Cause: An input stream contained data for more input columns * than specified by the client of the direct path API. Action: Make sure that the stream being loaded is for the * correct table. Check initialization sequence. ORA-26095: unprocessed stream data exists Cause: Either a OCIDirPathLoadStream call was made which provided * more stream data prior to the server being able to fully * process the stream data that it already has, or a * OCIDirPathFinish call was made when the server had * unprocessed stream data. Action: Most likely an application mis-use of the direct path API. * Make sure that the stream is not being reset inadvertently * prior to any previous stream data being processed, or, that * OCIDirPathFinish is not being called prematurely (i.e. stream * pushed, error encountered and LoadStream not called to process * the remainder of the stream before Finish is called.) ORA-26096: transfer size too small for row data (number bytes required) Cause: Either the transfer buffer size specified, or the default * transfer buffer size (if you did not specify a size), is * too small to contain a single row of the converted row data. Action: Set the transfer buffer size attribute of the direct path * context to be larger. ORA-26097: unsupported conversion for column string (from type number to type number) Cause: The direct path api does not support the required conversion. Action: Make sure the types are correct. * ORA-26098: direct path context is not prepared Cause: A direct path api function was called with a direct path * context which has not been prepared. Action: Make sure all necessary attributes in the direct path * context have been set, and the context is prepared via * OCIDirPathPrepare. ORA-26099: direct path context is already prepared Cause: OCIDirPathPrepare was called with a context that has already * been prepared. Action: Free the direct path context, set necessary attributes, and * call OCIDirPathPrepare. ORA-26101: tablespace # in file header is string rather than string for file string Cause: The tablespace number in the file header is inconsistent with that in the control file. Action: Check if the control file has been migrated correctly. Retry with the correct control file and data file. ORA-26102: relative file # in file header is string rather than string for file string Cause: The relative file number in the file header is inconsistent with that in the control file. Action: Check if the control file has been migrated correctly. Retry with the correct control file and data file. ORA-26103: V6 or V7 data file used to create control file Cause: The file header of the referenced file is in V6 or V7 format. Action: Either remove the file from the create control file command, or somehow migrate the file header to V8 format. ORA-26500: error on caching "string"."string" Cause: Attempt to cache the replication information which is unavailable in the catalog for the object. Action: Use dbms_reputil.sync_up_rep to validate the replication catalog, or use dbms_reputil.make_internal_pkg to validate internal package. ORA-26501: RepAPI operation failure Cause: An external RepAPI operation failed. Action: consult detail error message. ORA-26502: error resignal Cause: An internal service failed and signalled an error" Action: consult detail error message. ORA-26503: internal RepAPI operation failure on object string.string Cause: An unexpected internal RepAPI failure was detected Action: Contact Oracle support. ORA-26504: operation not implemented Cause: The caller requested a RepAPI operation that was not implemented Action: Do not issue this call. ORA-26505: unexpected internal null Cause: An internal buffer control structure was NULL Action: Verify that sufficient memory resources are available to RepAPI. ORA-26506: null global context Cause: An internal buffer control structure was NULL Action: Verify that sufficient memory resources are available to RepAPI. ORA-26507: null master connection Cause: The master connection handle was or became invalid. Action: Verify that the master connection is valid. ORA-26508: null materialized view connection Cause: The client connection handle was or became invalid. Action: Verify that the client connection is valid. ORA-26509: null materialized view control structure Cause: An internal materialized view control structure could not be obtained. Action: Check that the owner and users provided are correct. ORA-26510: materialized view name: "string" is greater than max. allowed length of string bytes Cause: The specified materialized view name was too long. Action: Shorten the materialized view name. ORA-26511: master table "string.string" not found Cause: A RepAPI operation was attempted against a non-existent or invalid master table Action: Verify that the master table object exists. ORA-26512: error pushing transaction to def$error Cause: An unexpected error occurred while sending an def$error rpc to the master site Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary. ORA-26513: push error: master proc. string$RP.string failed for trans:string seq:string Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master. Action: Notify master site system adminstrator or DBA. ORA-26514: object "string.string" not found Cause: The specified object was expected but not found. Action: Verify that the specified object exists and is valid. ORA-26515: no master log available for "string.string" Cause: The specified master log was not found or available for the named table. Action: Create the master log at the master site or correct any problems that may exist with the log. ORA-26516: no push transaction acknowledgement Cause: RepAPI was unable to confirm that the last pushed transaction was successfully commited by the master site. Action: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction. ORA-26517: materialized view control entry for "string.string" was not found Cause: The specified materialized view catalog control reocrd was not found. Action: Verify that the local materialized view catalog is valid and that the local materialized view is properly defined. ORA-26518: push queue synchronization error detected Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism. Action: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transactionIDs and is not accidently generating non-unique values. ORA-26519: no memory available to allocate Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area. Action: Shutdown one or more local applications to attempt to free heap memory and retry the RepAPI operation. ORA-26520: internal memory failure Cause: An internal memory error was detected. Action: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem. ORA-26521: rpc initialization error Cause: An error occurred during the initialization of a PL/SQL rpc. Action: Verify that the procudure to be invoked exists and is valid at the master site and is executable by the RepAPI user. ORA-26522: rpc execution error Cause: An error occurred during the execution of a PL/SQL rpc. Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked rpc. ORA-26523: rpc termination error Cause: An error occurred during the termination of a PL/SQL rpc. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory. Action: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted. ORA-26524: nls subsystem initialization failure for product=string, facility=string Cause: The NLS product/facility error message file could not be located or properly initialized. Action: Check that the error message directory and file(s) have been properly installed. ORA-26525: session connection attempt failed for string (@string) Cause: A connection could not be established to the specified database using the provided connection string. Action: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working. ORA-26526: materialized view sql ddl parse/expansion failed for string.string Cause: The client sql materialized view definition query could not be properly parsed by the master Oracle site. Action: Check that materialized view ddl sql is compatible with the currently connected version of Oracle and does not violate any of the RepAPI sql limitations or restrictions. ORA-26527: local store callback init phase failed for "string.string" Cause: The client callback failed during its INIT phase for the named object. Action: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support. ORA-26528: local store callback proc phase failed for "string.string" Cause: The client callback failed during its PROC phase for the named object. Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support. ORA-26529: local store callback term phase failed for "string.string" Cause: The client callback failed during its TERM phase for the named object. Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error state and notify Oracle support. ORA-26530: unable to build materialized view refresh control list Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog. Action: Verify that the named materialized view(s) are properly defined and valid. ORA-26532: replication parallel push simulated site failure Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site. Action: Do not enable the event for normal operation. ORA-26534: collision: tranID number ignored and purged Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site. Action: See the action section for E_QUEUESYNC (26518). ORA-26535: %ud byte row cache insufficient for table with rowsize=number Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site. Action: Increase the RepAPI row buffer size or reduce the width of the replicated tables. ORA-26536: refresh was aborted because of conflicts caused by deferred transactions Cause: There are outstanding conflicts logged in the DEFERROR table at the materialized view"s master site. Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master"s DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view"s changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved. ORA-26563: renaming this table is not allowed Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has beencreated. Action: If desired, unregister the replicated table with dbms_repcat.drop_master_repobject, or use the recommended procedure to rename the master table of a materialized view. ORA-26564: %s argument is not of specified type Cause: User passed type of the given argument number doesn"t match with the type of the argument in the stored arguments. Action: Invoke correct type procedure (i.e. get_XXX_arg) ORA-26565: Call to _arg made before calling dbms_defer.call Cause: User invoked _arg procedure before starting a deferred call Action: Invoke various procedures in the correct order. ORA-26566: Couldn"t open connect to string Cause: Failed to open connection using given dblink Action: Make sure that the dblink is valid and remote m/c is up. ORA-26571: %s.string.string: number of arguments (string) does not match replication catalog Cause: number of arguments does not match replication catalog Action: examine total number of arguments for the rpc call ORA-26572: %s.string.string: argument string does not match replication catalog Cause: the (rpc) call is corrupted Action: examine total number of arguments and each argument for the rpc call ORA-26575: remote database does not support replication parallel propagation Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation. Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above. ORA-26576: cannot acquire SR enqueue Cause: An attempt to acquire the SR enqueue in exclusive mode failed. Action: none ORA-26577: PRESERVE TABLE can not be used when dropping old style materialized view string.string Cause: The materialized view consists of a view and a container table. Action: Drop the materialized view without PRESERVE TABLE option. ORA-26650: %s background process string might not be started successfully Cause: An error occurred during creation of a capture or apply background process. Action: Please review V$Capture and V$Apply_coordinator views for the status of these processes. Please also check the trace file for more information. ORA-26660: Invalid action context value for string Cause: The value specified in the action context is invalid for use in STREAMS. Action: Check that the type and value are correct. ORA-26662: unable to process STREAMS Data Dictonary information for object Cause: The database is unable to process STREAMS Data Dictionary for this object. Action: Check that the compatibility for the database supports the object, and check the trace file for information about the object. ORA-26663: error queue for apply process string must be empty Cause: The error queue for this apply process contains error entries. Action: Execute or delete errors in the error queue. ORA-26664: cannot create STREAMS process string Cause: An attempt was made to create a STREAMS process when another was being created concurrently. Action: Wait for the creation of the other STREAMS process to finish before attempting to create the STREAMS process. ORA-26665: STREAMS process string already exists Cause: An attempt was made to create a STREAMS process that already exists. Action: Either specify another STREAMS process or remove the existing STREAMS process. ORA-26666: cannot alter STREAMS process string Cause: An attempt was made to alter a STREAMS process that is currently running. Action: Stop the STREAMS process and reissue the command. ORA-26667: invalid STREAMS parameter string Cause: An attempt was made to specify an invalid parameter. Action: Check the documentation for valid parameters. ORA-26668: STREAMS process string exists Cause: An attempt to remove the component failed because it is associated with the STREAMS process. Action: Either remove the process manually or specify the "cascade" option in dbms_streams_adm.remove_queue. ORA-26669: parameter string inconsistent with parameter string Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value. Action: Check the documentation for valid parameter values. ORA-26670: STREAMS option requires COMPATIBLE parameter to be string or higher Cause: Streams requires compatibility to be 9.2.0 or higher. Action: Shut down and restart with an appropriate compatibility setting. ORA-26671: maximum number of STREAMS processes exceeded Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached. Action: Remove existing STREAMS processes and retry the operation. ORA-26672: timeout occurred while stopping STREAMS process string Cause: Timeout occurred while waiting for a STREAMS process to shut down. Action: Retry the operation. If the error persists, try stopping the process with the FORCE option, or contact Oracle Support Services. ORA-26673: duplicate column name string Cause: An attempt was made to specify a duplicate column name in an LCR. Action: Remove the duplicate column and retry the operation. ORA-26674: Column mismatch in "string.string" (LCR: string type=string; DB: string type=string) Cause: The columns in the LCR were not the same or not found in the database table. Action: Alter the database table. ORA-26675: cannot create Streams capture process string Cause: Streams capture process could not be created because one or more parameters contain invalid value. Action: Refer to trace file for more details. ORA-26676: Table "string.string" has string columns in the LCR and string columns in the replicated site Cause: The number of columns in the LCR was not the same as the the replicated site. Action: Alter the table structure ORA-26677: Streams downstream capture process string cannot proceed Cause: Database global name has been set to a value which is same as the source database name of the downstream capture process. Action: Change database global name to a value other than the source database name for the downstream capture. ORA-26678: Streams capture process must be created first Cause: Must create Streams capture process before attempting this operation. Action: Create a Streams capture process, then retry the operation. ORA-26679: operation not allowed on LOB or LONG columns in LCR Cause: Certain operations on LOB/LONG columns of the LCR through rule-based transformations, DML handlers, or error handlers were not allowed. Action: Do not perform restricted operations on LOB or LONG columns in LCRs. See the documentation for operations that are restricted on LOB/LONG columns in LCRs. ORA-26680: object type not supported Cause: The specified object type is not supported. Action: Retry with a supported object type. ORA-26681: command type not supported Cause: The specified command type is not supported. Action: Retry with a supported command type. ORA-26682: invalid value for publication_on Cause: The publication_on parameter should be either "Y" or "N" Action: Retry with a proper value for publication_on. ORA-26683: invalid value for value_type Cause: The value_type parameter should be either "OLD" or "NEW" Action: Retry with proper value_type. ORA-26684: invalid value for value_type Cause: The value_type parameter should be one of "OLD", "NEW" or "*" Action: Retry with proper value_type. ORA-26685: cannot apply transactions from multiple sources Cause: Transactions from multiple sources were sent to the same apply process. Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process. ORA-26686: cannot capture from specified SCN Cause: An attempt was made to specify an invalid SCN. Action: Retry with a valid SCN. ORA-26687: no instantiation SCN provided for "string"."string" in source database "string" Cause: Object SCN was not set. If the object is a table, then both fields will be filled, for example "SCOTT"."EMP". If the object is a schema, only one field will be set, for example "SCOTT"."". And if the object is the entire database, no fields will be set, for example ""."". Action: Set the SCN by calling DBMS_APPLY_ADM.SET_%_INSTANTIATION_SCN ORA-26688: missing key in LCR Cause: Metadata mismatch, or not enough information in the user generated LCR. Action: Alter the database object, or provide all defined keys in the LCR. ORA-26689: column datatype mismatch in LCR Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object. Action: Alter the database object. ORA-26690: datatype not supported at non-Oracle system Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying. ORA-26691: operation not supported at non-Oracle system Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised. Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying. ORA-26692: invalid value string, string should be in string format Cause: The parameter specified was not in the correct format. Action: Specify the parameter value in the correct format. ORA-26693: STREAMS string process dropped successfully, but error occurred while dropping rule set string Cause: An attempt to drop an unused rule set failed after dropping the STREAMS proccess successfully. Action: Check existence of rule set and manually drop if necessary. ORA-26694: error while enqueueing into queue string.string Cause: An error occurred while enqueueing a message. Action: If the situation described in the next error on the stack can be corrected, do so. ORA-26695: error on call to string: return code string Cause: A locking related call failed. Action: Try the call again after fixing the condition indicated by the return code. ORA-26696: no streams data dictionary for object with number string and version number string from source database string Cause: An attempt to access the database object failed because the data dictionary for the object was either never populated or it was purged. Action: Make sure the streams data dictionary is created by calling DBMS_CAPTURE_ADM.PREPARE_%_INSTANTIATION. ORA-26697: LCR contains extra column "string" Cause: The LCR contained more columns than the replicated table. Action: Alter the database object. ORA-26698: %s did not have a string rule set Cause: The STREAMS client does not have a rule set of the indicated type. Action: Verify that the Streams client has a rule set of the specified type, and retry the operation. ORA-26699: STREAMS message consumer string already exists Cause: An attempt was made to create a STREAMS message consumer that already exists. Action: Either specify another STREAMS message consumer or remove the existing STREAMS message consumer. ORA-26701: STREAMS process string does not exist Cause: An attempt was made to access a STREAMS process which does not exist. Action: Check with the relevant security views for the correct name of the object. ORA-26705: cannot downgrade capture process after Streams data dictionary has been upgraded Cause: An attempt was made to downgrade a capture process after it has upgraded the Streams data dictionary. Action: Drop the capture process before attempting the downgrade. ORA-26706: cannot downgrade capture process Cause: An attempt was made to downgrade a capture process that has a higher version than the downgrade release version. Action: Drop the capture process after capture has finished consuming all the redo logs before attempting the downgrade. ORA-26708: remote DDL not supported by STREAMS : dblink string Cause: The apply process attempted to apply a DDL LCR via a dblink. This is not supported. Action: Do not attempt to apply DDL LCRs via a dblink. If possible, filter out DDL LCRs before applying. ORA-26709: Streams RFS restart Cause: Remote file server (RFS) process was restarted to reflect a change in DOWNSTREAM_REAL_TIME_MINE option of the Streams capture process. Action: No action required. This is an informational message only. ORA-26710: incompatible version marker encountered during Capture Cause: Capture process cannot mine redo from a version higher than the current software release version. Action: Drop and recreate the capture process. ORA-26711: remote table does not contain a primary key constraint Cause: The master table for remote apply does not constain a primary key constraint or the primary key constraint has been disabled. Action: Create a primary key constraint on the master table or enable the existing constraint. ORA-26712: remote object is "string"."string"\@"string" Cause: See the preceding error message to identify the cause. This message names the remote object, usually a table or view, for which an error occurred when Streams tried to access it for remote apply. Action: See the preceding error message. ORA-26713: remote object does not exist or is inaccessible Cause: Streams replication could not access the named table or view at a remote database to apply changes. Action: Confirm that the given remote table or view exists and is accessible through the given database link. When using a Heterogeneous Services database link to access a non-Oracle system, it may be necessary to check administration details for network connections at the non-Oracle system. ORA-26714: User error encountered while applying Cause: An error was encountered while applying. Action: Query the dba_apply_error view to determine the error and take the appropriate action. ORA-26715: time limit reached Cause: The specified time limit was reached for the STREAMS process. Action: Restart the STREAMS process, increasing the TIME_LIMIT parameter if necessary. ORA-26716: message limit reached Cause: The specified message limit was reached for the Capture process. Action: Restart the Capture process, increasing the MESSAGE_LIMIT parameter if necessary. ORA-26717: SCN limit reached Cause: The specified SCN limit was reached for the STREAMS process. Action: Change the MAXIMUM_SCN parameter, then restart the STREAMS process. ORA-26718: transaction limit reached Cause: The specified transaction limit was reached for the Apply process. Action: Restart the Apply process, increasing the TRANSACTION_LIMIT parameter if necessary. ORA-26721: enqueue of the LCR not allowed Cause: An apply process attempted to enqueue an LCR with a LONG column. This is not supported. Action: Modify rules or unset the enqueue destination to prevent LCRs with LONG columns from being enqueued by the apply process. ORA-26723: user "string" requires the role "string" Cause: The user was not granted the specified role required to proceed. Action: Grant the specified role to the user. ORA-26724: only SYS is allowed to set the Capture or Apply user to SYS. Cause: The Capture or Apply user was specified as SYS by a user other than SYS. Action: Set SYS as the Capture or Apply user while logged in as SYS. ORA-26725: cannot downgrade apply handlers Cause: An attempt was made to downgrade apply handlers that are not associated with a local database object, or the apply handlers are associated with a specific apply process. Action: Drop the associated apply handlers before attempting the downgrade. ORA-26726: logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible Cause: An attempt was made to set the logical standby database and DOWNSTREAM_REAL_TIME_MINE option of the Streams capture process on the same database. Action: Do not attempt to set the DOWNSTREAM_REAL_TIME_MINE option for a Streams capture process on a logical standby database. Do not attempt to make a database logical standby if there exists a Streams capture process with the DOWNSTREAM_REAL_TIME_MINE parameter set to Y. ORA-26727: Cannot alter queue_to_queue property of existing propagation. Cause: The queue_to_queue property was specified for an existing propagation. Action: Pass NULL for the queue_to_queue argument. ORA-26730: %s "string" already exists Cause: An attempt to use FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE failed because the item in question already exists. Action: Remove the object if appropriate and re-attempt the operation. ORA-26731: %s "string" does not exist Cause: A FILE GROUP, FILE GROUP VERSION, or FILE GROUP FILE was specified that does not exist. Action: Make sure the object exists and re-attempt the operation. ORA-26732: invalid file group string privilege Cause: The specified privilege number that was specified is invalid. Action: Check specification of dbms_file_group for valid privileges. ORA-26733: timed-out waiting for file group lock Cause: The procedure waited too long while getting a lock to perform a file group repository operation. Action: Retry the operation. ORA-26734: different datafiles_directory_object parameter must be specified Cause: The attempted operation involved datafiles platform conversion which required the datafiles_directory_object parameter to be specified for placing the converted data files. Action: Retry the operation after specifying a valid datafiles_directory_object parameter. This directory must be different from the directory objects for any of the datafiles for the specified file group version. ORA-26735: operation not allowed on the specified file group version Cause: One or more datafiles or export dump file(s) were missing from the specified file group version. Action: Retry the operation after adding all the data files and Data Pump dump file(s) to the specified version. ORA-26736: Data Pump error Cause: A Data Pump error occurred when the procedure performed a File Group Repository operation. Action: Check the error stack and trace file for error details. ORA-26737: version string already has an export dump file Cause: A Data Pump dump file was added to a file group version that already has a dump file. Action: Remove the existing dump file if appropriate, and retry the operation. ORA-26738: %s "string" is not empty Cause: The FILE GROUP or FILE GROUP VERSION being dropped contained objects. Action: Remove the child objects, then retry the operation. ORA-26740: cannot downgrade because there are file groups Cause: An attempt was made to downgrade a database that has file groups. Action: Drop all file groups before attempting the downgrade. ORA-26741: cannot assemble lobs Cause: An attempt was made to assemble lobs, but the compatibility of the source database for the LOB information is lower than 10.2.0. Action: Set ASSEMBLE_LOBS to FALSE in the DML or error handler while this handler is processing LOB information from a source database with a compatibility level lower than 10.2.0. ORA-26742: Maximum number of ignored transactions exceeded Cause: An attempt was made to add more than the allowed number of ignored transactions. Action: Please clear the current list of ignored transactions. ORA-26744: STREAMS capture process "string" does not support "string"."string" because of the following reason: string Cause: STREAMS capture encountered a table with an unsupported property. The most common reason is an unsupported column data type. Action: Revise the Capture rules to skip over the table in question. One way might be to add a negative rule excluding changes from the unsupported table from being captured. Also query the DBA_STREAMS_UNSUPPORTED view to determine which tables are not supported by STREAMS and for what reason. Consider adding negative rules for any tables that may be captured, but are present in this view. For potential workarounds to certain unsupported properties, see Metalink. ORA-26745: cursors (string) are not sufficient Cause: The maximum number of open cursors was too small for Streams Apply. Action: Increase the value of open_cursors. ORA-26746: DDL rule "string"."string" not allowed for this operation Cause: A DDL rule was specified for this operation. Action: Specify a non-DDL rule for this operation. ORA-26747: The one-to-many transformation function string encountered the following error: string Cause: The specified transformation function encountered an error. Action: Ensure that the function does not process or return DDL LCRs. Also ensure that the function does not return NULL. ORA-26748: The one-to-one transformation function string encountered the following error: string Cause: The specified transformation function encountered an error. Action: Ensure that the function does not return an LCR that has a different type from the LCR which was passed to the function. Also ensure that the function does not return NULL. For DDL transformation functions, creating and returning a new DDL LCR is not allowed. ORA-26752: Unsupported LCR received for "string"."string" Cause: Streams capture process received an LCR with unsupported operation from LogMiner. Action: If this object is listed in DBA_STREAMS_UNSUPPORTED view, modify rules to prevent changes made to this object from getting captured. ORA-26753: Mismatched columns found in "string.string" Cause: The columns in the LCR were not the same as the table in the database. Action: Alter the database table. ORA-26754: cannot specify both one-to-one transformation function string and one-to-many transformation function string Cause: Both a one-to-one transformation function and a one-to-many transformation function were specified for a rule. Action: Remove either the one-to-one transformation function, or the one-to-many transformation function. ORA-26761: Standby Redo Logs not available for real time mining Cause: Standby Redo Logs required for real time mining by downstream capture process were not available. Action: Check the configuration of Standby Redo Logs and retry the operation at a later time. To start the capture process without real time mining property, reset DOWNSTREAM_REAL_TIME_MINE parameter of the capture process and retry the operation. ORA-26762: Cannot autogenerate name for parameter string because of the following reason: string Cause: An error was encountered while attempting to generate a name for a parameter which was passed a NULL value. Action: If possible, fix the error, otherwise specify the parameter name explicitly. ORA-26763: invalid file type "string" Cause: An invalid file type was specified for the ASM file. Action: Check documentation for valid ASM file types. ORA-26764: invalid parameter "string" for local capture "string" Cause: An invalid parameter was specified for the local capture process. Action: Check documentation for valid parameters. ORA-26765: invalid parameter "string" for downstream capture "string" Cause: An invalid parameter was specified for the downstream capture process. Action: Check documentation for valid parameters. ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer Cause: sbtinit returned an error, additional information indicates error Action: verify that vendor"s storage subsystem product is operating correctly ORA-27001: unsupported device type Cause: the specified device type is supported on this platform Action: check V$BACKUP_DEVICE for supported device types ORA-27002: function called with invalid device structure Cause: internal error, aditional information indicates which function encountered error Action: check for trace file and contact Oracle Support ORA-27003: cannot open file on device allocated with NOIO option Cause: internal error, a file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error Action: check for trace file and contact Oracle Support ORA-27004: invalid blocksize specified Cause: internal error, blocksize specified is incorrect for the device on which file is being created, aditional information indicates blocksize specified, and the function that encountered the error Action: check for trace file and contact Oracle Support ORA-27005: cannot open file for async I/O on device not supporting async Cause: internal error, a file is being opened for async I/O on a device that does not support async I/O, additional information indicates which function encountered error Action: check for trace file and contact Oracle Support ORA-27006: sbtremove returned error Cause: additional information indicates error returned by sbtremove, and the function that encountered the error Action: verify that vendor"s storage subsystem product is operating correctly ORA-27007: failed to open file Cause: sbtopen returned error, additional information indicates error returned from sbtopen, and the function that encountered the error Action: verify that vendor"s storage subsystem product is operating correctly ORA-27008: function called with invalid file structure Cause: internal error, aditional information indicates which function encountered error Action: check for trace file and contact Oracle Support ORA-27009: skgfwrt: cannot write to file opened for read Cause: internal error Action: check for trace file and contact Oracle Support ORA-27010: skgfwrt: write to file failed Cause: sbtwrite returned error, additional information indicates error returned from sbtwrite Action: verify that vendor"s storage subsystem product is operating correctly ORA-27011: skgfrd: cannot read from file opened for write Cause: internal error Action: check for trace file and contact Oracle Support ORA-27012: skgfrd: read from file failed Cause: sbtread returned error, additional information indicates error returned from sbtread Action: verify that vendor"s storage subsystem product is operating correctly ORA-27013: skgfqdel: cannot delete an open file Cause: internal error Action: check for trace file and contact Oracle Support ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR Cause: Failure of sltln in skgfqpini Action: Check additional return error for more information. ORA-27015: skgfcls: failed to close the file Cause: sbtclose returned error, additional information indicates error returned from sbtclose Action: verify that vendor"s storage subsystem product is operating correctly ORA-27016: skgfcls: sbtinfo returned error Cause: additional information indicates error returned from sbtinfo Action: verify that vendor"s storage subsystem product is operating correctly ORA-27017: skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH) Cause: media handle string length exceeds SSTMXQMH Action: verify that vendor"s storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is atleast 64 (the limit specified for sbtinfo). additional information indicates the media handle string length returned by sbtinfo, and the limit (SSTMXQMH) ORA-27018: BLKSIZE is not a multiple of the minimum physical block size Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform. Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size. ORA-27019: tape filename length exceeds limit (SBTOPMXF) Cause: length of tape filename provided to sequential I/O OSD functions is too long Action: additional information indicates in which function this error is encountered, the length of filename provided, and the limit on filename ORA-27020: named devices not supported Cause: the platform or the specified device type does not support named devices Action: do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to see what device types and names (if any) are available. ORA-27021: sequential file handle must be specified Cause: The filename which will be passed to sbtopen was not specified. Action: Specify a filename and continue. If this is a backup set being created via Recovery Manager, use the "format" option to specify the backup piece handle name. ORA-27022: skgfqsbi: could not allocate memory for media manager Cause: Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup/restore services. Action: Increase the amount of memory available to the Oracle process and retry the backup/restore. ORA-27023: skgfqsbi: media manager protocol error Cause: The media management software which is linked with Oracle to provide backup/restore services did not provide its function pointer structure to Oracle. Action: This is an internal error in the media management product. Contact the media management vendor. ORA-27024: skgfqsbi: sbtinit2 returned error Cause: sbtinit2 returned an error. This happens during a backup or restore operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27025: skgfqsbi: invalid media manager context area size Cause: The media management software requested a context area size which is greater than the maximum allowable size. Action: This is an internal error in the media management product. Contact the media management vendor. ORA-27026: skgfrls: sbtend returned error Cause: sbtend returned an error. This happens during a backup or restore operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27027: sbtremove2 returned error Cause: sbtremove2 returned an error. This happens when deleting a backup file. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27028: skgfqcre: sbtbackup returned error Cause: sbtbackup returned an error. This happens when creating a backup file during a backup operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27029: skgfrtrv: sbtrestore returned error Cause: sbtrestore returned an error. This happens when retrieving a backup file during a restore operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27030: skgfwrt: sbtwrite2 returned error Cause: sbtwrite2 returned an error. This happens while writing a backup file during a backup operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27031: mirror resilvering functions not supported Cause: internal error Action: check for trace file and contact Oracle Support ORA-27032: failed to obtain file size limit Cause: getrlimit system call returned an error Action: check errno ORA-27033: failed to obtain file size limit Cause: ulimit system call returned an error Action: check errno ORA-27034: maximum length of ORACLE_SID exceeded Cause: too many characters in the ORACLE_SID string Action: rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system ORA-27035: logical block size is invalid Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum Action: block size specified is returned as additional information, check init.ora parameters, additional information also indicates which function encountered the error ORA-27036: translation error, unable to expand file name Cause: additional information indicates sltln/slnrm error, and also indicates which function encountered the error Action: check additional information ORA-27037: unable to obtain file status Cause: stat system call returned an error, additional information indicates which function encountered the error Action: check errno ORA-27038: created file already 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-27039: create file failed, file size limit reached Cause: an attempt was made to create a file that exceeds the process"s file size limit, additional information indicates which function encountered the error Action: raise the file size limit ORA-27040: file create error, unable to create file Cause: create system call returned an error, unable to create file Action: verify filename, and permissions ORA-27041: unable to open file Cause: open system call returned an error, additional information indicates which function encountered the error Action: check errno ORA-27042: not enough space on raw partition to fullfill request Cause: internal error, file too large for raw partition, additional information indicates which function encountered the error Action: check for trace file and contact Oracle Support ORA-27043: unable to seek to beginning of file Cause: seek system call failed, additional information indicates which function encountered the error Action: check errno 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 ORA-27045: unable to close the file Cause: close system call failed, additional information indicates which function encountered the error Action: check errno ORA-27046: file size is not a multiple of logical block size Cause: file size as indicated by stat is not correct, additional information indicates which function encountered the error Action: verify that the file has not been overwritten or truncated ORA-27047: unable to read the header block of file Cause: read system call failed, additional information indicates which function encountered the error Action: check errno ORA-27048: skgfifi: file header information is invalid Cause: possibly trying to use a non-database file as a database file Action: verify that file is a database file ORA-27049: unable to seek to and read the last block Cause: an attempt was made to seek to and read the last block in file, additional information indicates which function encountered error Action: check errno ORA-27050: function called with invalid FIB/IOV structure Cause: internal error, aditional information indicates which function encountered error Action: check for trace file and contact Oracle Support ORA-27052: unable to flush file data Cause: fsync system call returned error, additional information indicates which function encountered the error Action: check errno ORA-27053: blocksize in file header not a multiple of logical block size Cause: the logical block size is invalid, additional information indicates the logical block size and the blocksize in the file header Action: use a different logical block size, or do not reuse file ORA-27054: NFS file system where the file is created or resides is not mounted with correct options Cause: The file was on an NFS partition and either reading the mount tab file failed or the partition wass not mounted with the correct mount option. Action: Make sure mount tab file has read access for Oracle user and the NFS partition where the file resides is mounted correctly. For the list of mount options to use refer to your platform specific documentation. ORA-27056: could not delete file Cause: unlink system call returned error Action: check errno ORA-27057: cannot perform async I/O to file Cause: internal error, query is being asked about async vector I/O when the file does not support async I/O Action: check for trace file and contact Oracle Support ORA-27058: file I/O question parameter is invalid Cause: internal error, invalid query is being asked Action: check for trace file and contact Oracle Support ORA-27059: could not reduce file size Cause: ftruncate system call returned error Action: check errno ORA-27060: could not set close-on-exec bit on file Cause: fcntl system call returned error Action: check errno ORA-27061: waiting for async I/Os failed Cause: aiowait function returned error Action: check errno ORA-27062: could not find pending async I/Os Cause: There should have been some async I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be either because of an Oracle bug or the vendor OS bug or due to a NFS server not responding Action: check Oracle trace file, OS message files and contact Oracle Support ORA-27063: number of bytes read/written is incorrect Cause: the number of bytes read/written as returned by aiowait does not match the original number, additional information indicates both these numbers Action: check errno ORA-27064: cannot perform async I/O to file Cause: internal error, asked to perform async I/O when IOV indicates that it cannot be performed on the file Action: check for trace file and contact Oracle Support ORA-27065: cannot perform async vector I/O to file Cause: internal error, asked to perform async vector I/O when it cannot be performed on the file Action: check for trace file and contact Oracle Support ORA-27066: number of buffers in vector I/O exceeds maximum Cause: internal error, number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers Action: check for trace file and contact Oracle Support ORA-27067: size of I/O buffer is invalid Cause: internal error, buffer size is either 0, or greater than SSTIOMAX or not a multiple of logical block size, additional information indicates where in function the error was encountered and the buffer size Action: check for trace file and contact Oracle Support ORA-27068: I/O buffer is not aligned properly Cause: internal error, buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer Action: check for trace file and contact Oracle Support ORA-27069: attempt to do I/O beyond the range of the file Cause: internal error, the range of blocks being read or written is outside the range of the file, additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file Action: check for trace file and contact Oracle Support ORA-27070: async read/write failed Cause: aioread/aiowrite system call returned error, additional information indicates starting block number of I/O Action: check errno ORA-27071: unable to seek to desired position in file Cause: lseek system call returned error, additional information indicates block number in file to which seek was attempted Action: check errno ORA-27072: File I/O error Cause: read/write/readv/writev system call returned error, additional information indicates starting block number of I/O Action: check errno ORA-27073: Trying to close a file which has async I/Os pending to be dequeued Cause: internal error, the file is being closed but not all async I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file Action: check for trace file and contact Oracle Support ORA-27074: unable to determine limit for open files Cause: The getrlimit() system call returned an error. Action: Check errno. ORA-27075: SSTMOFRC constant too large Cause: internal error Action: check for trace file and contact Oracle Support ORA-27076: unable to set limit for open files Cause: The setrlimit() system call returned an error. Action: Check errno. ORA-27077: too many files open Cause: internal error, the number of files opened through skgfofi has reached the limit Action: Check for trace file and contact Oracle Support. ORA-27078: unable to determine limit for open files Cause: The getrlimit() system call returned an error. Action: Check errno. ORA-27080: too many files open Cause: The number of files opened has reached the system limit. Action: Check the error, and set system configuration values. ORA-27081: unable to close the file Cause: The close() system call failed. Action: Check errno. ORA-27083: waiting for async I/Os failed Cause: The aio_waitn() library call returned an error. Action: Check errno. ORA-27084: unable to get/set file status flags Cause: The fcntl() system call with F_GETFL/F_SETFL flag returned an error. Action: Check errno. ORA-27086: unable to lock file - already in use Cause: the file is locked by another process, indicating that it is currently in use by a database instance. Action: determine which database instance legitimately owns this file. ORA-27087: unable to get share lock - file not readable Cause: share lock request was made on a file not open for read access. Action: file must be open read-only or read-write to get a share lock. ORA-27088: unable to get file status Cause: file not open or file descriptor is invalid. Action: none ORA-27089: unable to release advisory lock Cause: release of file lock failed Action: see errno ORA-27091: unable to queue I/O Cause: read/write/readv/writev system call returned error, additional information indicates starting block number of I/O Action: check errno ORA-27092: size of file exceeds file size limit of the process Cause: an attempt was made to open a file that exceeds the process"s file size limit (ulimit), additional information shows the current limit (logical blocks) and the size of the file (logical blocks) Action: increase the processes file size limit (ulimit) and retry ORA-27093: could not delete directory Cause: rmdir system call returned error Action: check errno ORA-27094: raw volume used can damage partition table Cause: A raw device with VTOC information was provided as a database file. Action: Make sure the disk partition that is provided to Oracle does not start at sector 0 ORA-27100: shared memory realm already exists Cause: Tried to start duplicate instances, or tried to restart an instance that had not been properly shutdown Action: Use a different instance name, or cleanup the failed instance"s SGA ORA-27101: shared memory realm does not exist Cause: Unable to locate shared memory realm Action: Verify that the realm is accessible ORA-27102: out of memory Cause: Out of memory Action: Consult the trace file for details ORA-27103: internal error Cause: internal error Action: contact Oracle support ORA-27120: unable to removed shared memory segment Cause: shmctl() call failed Action: check permissions on segment, contact Oracle support ORA-27121: unable to determine size of shared memory segment Cause: shmctl() call failed Action: check permissions on segment, contact Oracle support ORA-27122: unable to protect memory Cause: mprotect() call failed Action: contact Oracle support ORA-27123: unable to attach to shared memory segment Cause: shmat() call failed Action: check permissions on segment, contact Oracle support ORA-27124: unable to detach from shared memory segment Cause: shmdt() call failed Action: contact Oracle support ORA-27125: unable to create shared memory segment Cause: shmget() call failed Action: contact Oracle support ORA-27126: unable to lock shared memory segment in core Cause: insufficient privileges to lock shared memory segment in core Action: make sure process is running with necessary privileges. ORA-27127: unable to unlock shared memory segment Cause: insufficient privileges to unlock shared memory segment Action: make sure process is running with necessary privileges. ORA-27128: unable to determine pagesize Cause: sysconf() call failed Action: contact Oracle support ORA-27140: attach to post/wait facility failed Cause: The program attempted to initialize the post/wait facility, but the facility could not be attached. Action: Check for additional errors and contact Oracle Support. ORA-27141: invalid process ID Cause: process operation attempted using invalid process ID Action: contact Oracle Support ORA-27142: could not create new process Cause: OS system call Action: check errno and if possible increase the number of processes ORA-27143: OS system call failure Cause: OS system call failed Action: check errno and contact Oracle support ORA-27144: attempt to kill process failed Cause: OS system call error Action: check errno and contact Oracle Support ORA-27145: insufficient resources for requested number of processes Cause: OS system call error Action: check errno and contact Oracle Support ORA-27146: post/wait initialization failed Cause: OS system call failed Action: check errno and contact Oracle Support ORA-27147: post/wait reset failed Cause: OS system call failed Action: check errno and contact Oracle Support ORA-27148: spawn wait error Cause: OS system call failed Action: check errno and contact Oracle Support ORA-27149: assignment out of range Cause: internal error, requested conversion too large for type Action: contact Oracle Support ORA-27150: attempt to notify process of pending oradebug call failed Cause: OS system call Action: check errno contact Oracle Support ORA-27151: buffer not large enough to hold process ID string Cause: internal error Action: contact Oracle Support ORA-27152: attempt to post process failed Cause: OS system call failed Action: check errno and contact Oracle Support ORA-27153: wait operation failed Cause: OS system called failed Action: check errno contact Oracle Support ORA-27154: post/wait create failed Cause: internal error, multiple post/wait creates attempted simultaneously Action: check errno and contact Oracle Support ORA-27155: could not execute file Cause: OS system call failed Action: check errno and contact Oracle Support ORA-27156: request for process information failed Cause: internal error Action: contact Oracle Support ORA-27157: OS post/wait facility removed Cause: the post/wait facility for which the calling process is awaiting Action: check errno and contact Oracle Support ORA-27158: process control failure Cause: Oracle was unable to set the specified process control. Action: Consult the Oracle Administrator"s Guide. ORA-27159: failure setting process scheduling priority Cause: Oracle was unable to set the scheduling priority desired. Action: Consult the Oracle Administrator"s Guide. ORA-27160: process requested to perform operation Cause: The current process was requested to perform an operation by another process. Action: This is used internally; no action is required. ORA-27161: request for Oracle binary information failed Cause: The program was unable to get information about the Oracle binary. Action: Check for additional errors and contact Oracle support. ORA-27162: thread creation failed Cause: The program was unable to create a thread. Action: Check errno and contact Oracle support. ORA-27163: out of memory Cause: The program ran out of memory when allocating a temporary data structure. Action: Increase the amount of memory on the system. ORA-27164: tried to join detached thread Cause: The program tried to join a detached thread. Action: This is an internal error; contact Oracle support. ORA-27165: tried to join thread that does not exist Cause: The program tried to join a thread that does not exist. Action: This is an internal error; contact Oracle support. ORA-27166: tried to join current thread Cause: A thread in the program tried to join itself. Action: This is an internal error; contact Oracle support. ORA-27190: skgfrd: sbtread2 returned error Cause: sbtread returned an error. This happens while reading a backup file during a restore operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27191: sbtinfo2 returned error Cause: sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager"s catalog. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27192: skgfcls: sbtclose2 returned error - failed to close file Cause: sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27193: sbtinfo2 did not return volume label Cause: sbtinfo2 did not return the volume label information for the backup file that was just created. Action: This is an internal error in the media management product. Contact the media management vendor. ORA-27194: skgfdvcmd: sbtcommand returned error Cause: sbtcommand returned an error. This happens when an rman SEND command is issued. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27195: proxy copy not supported Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy. Action: Re-run the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy. ORA-27196: skgfpbk: sbtpcbackup returned error Cause: sbtpcbackup returned an error. This happens when a proxy backup is begun. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27197: skgfprs: sbtpcrestore returned error Cause: sbtpcrestore returned an error. This happens when a proxy restore is begun. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27198: skgfpvl: sbtpcvalidate returned error Cause: sbtpcvalidate returned an error. This happens during a proxy backup or restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27199: skgfpst: sbtpcstatus returned error Cause: sbtpcstatus returned an error. This happens during a proxy backup or restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27200: skgfpgo: sbtpcstart returned error Cause: sbtpcstart returned an error. This happens during a proxy backup or restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27201: skgfpcm: sbtpccommit returned error Cause: sbtpccommit returned an error. This happens during a proxy backup or restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27202: skgfpen: sbtpcend returned error Cause: sbtpcend returned an error. This happens during a proxy backup or restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27203: skgfpqb: sbtpcquerybackup returned error Cause: sbtpcquerybackup returned an error. This happens during a proxy backup. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27204: skgfpqr: sbtpcqueryrestore returned error Cause: sbtpcqueryrestore returned an error. This happens during a proxy restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27205: skgfpcn: sbtpccancel returned error Cause: sbtpccancel returned an error. This happens during a proxy restore. Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. ORA-27206: requested file not found in media management catalog Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog. Action: Retry the command with a different file. ORA-27207: syntax error in device PARMS - parentheses mismatch or missing Cause: User-supplied PARMS value has incorrect syntax. Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn ORA-27208: syntax error in device PARMS - environment variable value missing Cause: User-supplied PARMS value has incorrect syntax. Action: Retry the command with correct syntax: ENV=(var1=val1,var2=val2,..) ORA-27209: syntax error in device PARMS - unknown keyword or missing = Cause: User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword. Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn ORA-27210: syntax error in device PARMS Cause: User-supplied PARMS value has incorrect syntax. Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn ORA-27211: Failed to load Media Management Library Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for error code. Action: Retry the command with proper media library. Or re-install Media management module for Oracle. ORA-27212: some entrypoints in Media Management Library are missing Cause: media library does not have one of the following entrypoints : sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, sbtinit Action: Retry the command with proper media library. ORA-27213: failed to unload Media Management Library Cause: dlclose for media library returned error. See Additional Additional information for error code. Action: contact Oracle Support. ORA-27214: skgfrsfe: file search failed Cause: The FindNextFile function returned unxpected error. Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed. ORA-27215: skgfgsmcs: sbtinfo2 returned unknown file Cause: During an sbtinfo2() call, the media management software returned information about an unknown backup file. Action: Contact the media management vendor. ORA-27216: skgfgsmcs: sbtinfo2 returned a malformed response Cause: The media management software returned a malformed response during an sbtinfo2() call. Action: Contact the media management vendor. ORA-27230: OS system call failure Cause: OS system call failed Action: check errno and contact Oracle support ORA-27250: OS system call failure Cause: OS system call failed Action: check errno and contact Oracle support ORA-27300: OS system dependent operation:string failed with status: string Cause: OS system call error Action: contact Oracle Support ORA-27301: OS failure message: string Cause: OS system call error Action: contact Oracle Support ORA-27302: failure occurred at: string Cause: OS system call error Action: contact Oracle Support ORA-27303: additional information: string Cause: OS system call error Action: contact Oracle Support ORA-27365: job has been notified to stop, but failed to do so immediately Cause: The job specified in the stop_job command cannot be stopped immediately(because it is rolling back or blocked on a network operation), but it has been notified to stop. This means it will be stopped as soon as possible after its current uninterruptable operation is done. Action: No action is required for the job to be stopped, but calling stop_job with force (if you have the privilege) may cause the job to be stopped sooner. ORA-27366: job "string.string" is not running Cause: An attempt was made to stop a job that was not running. Action: Verify the status of the job. If the job is running but this message is still being returned, contact Oracle support. ORA-27367: program "string.string" associated with this job is disabled Cause: An attempt was made to run a job whose program has been disabled. Action: Reenable the program before running the job. ORA-27369: job of type EXECUTABLE failed with exit code: string Cause: A problem was encountered while running a job of type EXECUTABLE. The cause of the actual problem is identified by the exit code. Action: Correct the cause of the exit code and reschedule the job. ORA-27370: job slave failed to launch a job of type EXECUTABLE Cause: The scheduler ran into an error when the job slave tried to start a job of type EXECUTABLE. The rest of the error stack will provide more detailed information on what the exact problem was. Action: Correct the problem specified in the error stack and reschedule the job. ORA-27371: jobs of type EXECUTABLE are not supported on this platform Cause: The user tried to create a job or program of type EXECUTABLE on a platform where such jobs are not supported. Action: Switch to a different platform or create a different type of job or program. ORA-27372: length of action and arguments exceeds platform limit string Cause: The total length of the job or program action and the arguments exceeds the platform limit specified. Action: Reduce the total length by specifying fewer and/or shorter arguments ORA-27373: unknown or illegal event source queue Cause: The source queue specified for the event based job or event based schedule was either not found or was of the wrong type. Action: Check if the queue exists. If it does make sure it is a multiple consumer queue and it is a post 8.1 compatible queue. Single consumer queues and old-style queues cannot be used as event source queues. ORA-27374: insufficient privileges on event source queue Cause: The job owner had insufficient privileges on the event source queue that was specified for the job. Action: The job owner has to have dequeue privileges on event source queue or he has to have manage queue or dequeue any queue system privileges. Make sure one of these privileges is granted. ORA-27375: valid agent name must be specified for secure queues Cause: The queue specified for the event based job or schedule was a secure queue and either no agent name was specified or an invalid agent name was specified. Action: If no agent name was specified, retry the call with a valid agent name. If the agent name was valid, check if the agent is currently subscribed to the queue and, in the case of jobs, check is the agent has been authorized to act as the job owner. ORA-27376: event condition cannot be NULL Cause: A null event condition was passed in for an event based job or schedule. This is not allowed. Action: Pass in a legal event condition. ORA-27377: windows cannot have event based schedules Cause: Event based schedules for windows are currently not supported. Action: Use a time-based schedule instead. ORA-27378: cannot stop jobs of type EXECUTABLE on this platform Cause: An attempt was made to stop a job of type EXECUTABLE on a platform where the stop operation was not supported. Action: If the attempt to stop the job was made with the FORCE option set to FALSE, try again but change the FORCE option to TRUE. ORA-27399: job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege Cause: The owner of a job of type EXECUTABLE does not have the CREATE EXTERNAL JOB system privilege. Action: Grant the CREATE EXTERNAL JOB system privilege to the job owner or create another job in a schema which does have the CREATE EXTERNAL JOB system privilege. ORA-27411: empty string is not a valid repeat interval. Cause: An empty string "" was provided as a repeat interval for a window or a schedule. Action: Specify a valid repeat interval, e.g., "FREQ=DAILY;BYHOUR=8;BYMINUTE=0;BYSECOND=0" for a job that executes daily at 8am. ORA-27412: repeat interval or calendar contains invalid identifier: string Cause: The calendar string or calendar definition for the repeat interval of a job, schedule or window contained an unsupported keyword or reference to an undefined calendar. Action: Correct the repeat interval such that it no longer contains the invalid keyword. ORA-27413: repeat interval is too long Cause: The repeat interval consisted of a calendar string larger than the maximum size allowed. Action: Use a shorter calendar string for the repeat interval. ORA-27414: Invalid BY value type Cause: The type of BY value was not allowed for the frequency specified Action: Ommit BY values of this type or alter the frequency ORA-27415: repeat interval or calendar must start with the FREQ= clause Cause: The specified calendar string for the repeat interval did not start with the frequency clause. Action: Create a repeat interval that starts with a frequency clause, e.g. "FREQ=YEARLY;BYMONTH=FEB" ORA-27416: BYDAY= clause in repeat interval or calendar contains an invalid weekday Cause: The BYDAY clause of the repeat interval contained a value that doesn"t properly represent a weekday. Action: Use the correct three letter abbreviations for weekdays, e.g. MON for Monday and FRI for Friday. ORA-27417: BYWEEKNO clause is only supported when FREQ=YEARLY Cause: A repeat interval or calendar contained a BYWEEKNO clause with a frequency other than yearly. Action: Remove the BYWEEKNO clause or change the frequency to yearly. ORA-27418: syntax error in repeat interval or calendar Cause: The repeat interval or calendar definition could not be recognized as a valid syntax. Action: Specify a valid repeat interval. ORA-27419: unable to determine valid execution date from repeat interval Cause: The specified repeat interval contained conflicting clauses that made it impossible to ever find a matching date, e.g., "FREQ=YEARLY;BYMONTH=FEB;BYMONTHDAY=31". Alternatively, the scheduler reached its maximum number of attempts to try to find a valid execution date. This occurs when theoretically there is a valid execution date far in the future, but the scheduler took too many attempts to determine this date. Action: Remove the conflicting clauses, or simplify the repeat interval so that it is easier to determine the next execution date. ORA-27421: usage of string not supported in a calendar definition Cause: The calendar definition contained a clause that is specific for a repeat interval Action: Specify a valid calendar definition. ORA-27431: chain string.string has a user-managed rule set Cause: An attempt was made to modify a rule set that is not managed by the Scheduler. Action: Modify the rule set directly using the dbms_rule_adm package or create another chain without specifying a rule set. ORA-27432: step string does not exist for chain string.string Cause: The step specified does not exist for the given chain. Action: Reissue the command using a step that exists for this chain. ORA-27433: cannot alter state of step string for job string.string to string Cause: The step cannot be changed to the requested state. The state of a running step cannot be changed. A step which is running or has already run cannot be run again. Action: Wait until the step has finished running. ORA-27434: cannot alter chain step job string.string.string Cause: A step job of a running chain cannot be altered, only stopped or dropped. Action: Stop or drop the chain step job or alter the running chain step instead. ORA-27435: chain job terminated abnormally Cause: A chain job has ended abnormally. The error code for the running chain could not be retrieved. Action: No action necessary. The job will run again when it is scheduled to. ORA-27451: %s cannot be NULL Cause: An attempt was made to set a NOT NULL scheduler attribute to NULL. Action: Reissue the command using a non-NULL value for the specified attribute. ORA-27452: %s is an invalid name for a database object. Cause: An invalid name was used to identify a database object. Action: Reissue the command using a valid name. ORA-27453: %s is an invalid job or program argument name. Cause: An invalid job or program argument name was specified. Action: Reissue the command using a valid name for this argument. ORA-27454: argument name and position cannot be NULL Cause: The name or position of a program or job argument was defined as NULL. Action: Reissue the command providing either a valid argument name or valid argument position. ORA-27455: Only "SYS" is a valid schema for a string. Cause: A non-SYS schema was specified for an object that must be in the SYS schema. Action: Reissue the command, leaving out the schema name or using the schema name of SYS. ORA-27456: not all arguments of program "string.string" have been defined Cause: The number_of_arguments attribute of the named program did not match the actual number of arguments that have been defined. Action: Define as many arguments as the number of arguments, or change the number of arguments. ORA-27457: argument string of job "string.string" has no value Cause: No value was provided for the job argument with the specified position. Action: Provide a value for the job argument using any of the set_job_xxxx_value() routines. Or, when using a named program, specify a default value for the corresponding argument of the program. ORA-27458: A program of type PLSQL_BLOCK cannot have any arguments. Cause: An attempt was made to create or enable a program of type PLSQL_BLOCK with arguments. This is not allowed. Action: Change the number of arguments to zero, or change the type of the program. ORA-27459: A program of type EXECUTABLE must have character-only arguments. Cause: A program of type EXECUTABLE was created or enabled with one or more arguments of non-character datatypes. Action: Change the arguments to be of character-only datatypes. ORA-27460: cannot execute disabled job "string.string" Cause: An attempt was made to run a job that is disabled. Action: Enable the job and then reschedule the job. ORA-27461: The value for attribute string is too large. Cause: The value that was provided for the specified attribute was too large. Action: Reissue the command using a smaller or shorter value. ORA-27463: invalid program type string Cause: An invalid program type was specified. Action: Reissue the command using a valid program type. ORA-27464: invalid schedule type string Cause: An invalid schedule type was specified. Action: Reissue the command using a valid schedule type. ORA-27465: invalid value string for attribute string Cause: An invalid value was provided for the specified attribute. Action: Reissue the command using a valid value for this attribute. ORA-27467: invalid datatype for string value Cause: The value provided for the named scheduler attribute was of an invalid datatype. Action: Reissue the command using a value of the correct datatype. ORA-27468: "string.string" is locked by another process Cause: An attempt was made to read or modify the state of the named scheduler object when another process was also updating the same object and held the lock. Action: Retry the operation. Scheduler locks are held for a very short duration. If the error persists, contact Oracle Support. ORA-27469: %s is not a valid string attribute Cause: A non-existant attribute was specified. Action: Reissue the command using a valid attribute for that specific scheduler object. ORA-27470: failed to re-enable "string.string" after making requested change Cause: A change was made to an enabled scheduler object that caused it to become disabled. Action: Alter the object so that it becomes valid and then enable it. ORA-27471: window "string.string" is already closed Cause: An attempt was made to close a window that was not open. Action: No action required. ORA-27472: invalid metadata attribute string Cause: An invalid metadata attribute was specified. Action: Reissue the command using a valid metadata attribute. ORA-27473: argument string does not exist Cause: An argument which was specified does not exist. Action: Reissue the command using an argument name defined by the program or using a valid argument position. ORA-27474: cannot give both an argument name and an argument position Cause: An argument was specified using both a name and a position. Action: Reissue the command using either the argument name or the argument position but not both. ORA-27475: "string.string" must be a string Cause: An object of the wrong type was specified. For example, a table could have been passed to the drop_job() procedure. Action: Reissue a different command applicable to this object type or reissue the same command using an object of the valid type. ORA-27476: "string.string" does not exist Cause: A database object was specified that does not exist. Action: Reissue the command using an object that exists or create a new object and then reissue this command. ORA-27477: "string.string" already exists Cause: An attempt was made to create an object with a name that has already been used by another object in the same schema. Action: Reissue the command using a different name or schema. ORA-27478: job "string.string" is running Cause: An attempt was made to drop a job that is currently running. Action: Stop the job and then reissue the command, or reissue the command specifying the force option to stop the job first. ORA-27479: Cannot string "string.string" because other objects depend on it Cause: An attempt was made to drop or disable a scheduler object that has jobs associated with it without specifying the force option. Action: Alter the associated jobs so they do not point to the scheduler object being dropped or disabled and then reissue the command. Alternatively reissue the command specifying the force option. If the force option is specified and a scheduler object is being dropped, all associated jobs will be disabled. ORA-27480: window "string" is currently open Cause: An attempt was made to drop a window that is currently open, or to manually open a window while another window is already open. Action: Close the window that is open and then reissue the command, or reissue the command while setting the force option to TRUE. ORA-27481: "string.string" has an invalid schedule Cause: An attempt was made to enable a job or window that has an invalid schedule. Action: Alter the schedule of the job or window so that it is valid and then reissue the enable command. ORA-27483: "string.string" has an invalid END_DATE Cause: An attempt was made to enable a job or window that has an invalid end_date. Either the end_date is before the start_date or the end_date is in the past. Action: Alter the job or window so that the end date becomes valid (possibly null) and then reissue the command. ORA-27484: Argument names are not supported for jobs without a program. Cause: An attempt was made to set or reset a job argument by using the name of the argument. Identifying job arguments by their name is only supported in combination with jobs that are based on programs. Jobs that are not using a program cannot have named arguments. Action: Use argument position instead of name and then issue the command again. ORA-27485: argument string already exists at a different position Cause: An attempt was made to create or replace an argument with a name that is already used by an argument at a different position. Action: Use a different name for the argument or drop or alter the argument which already exists with this name and then reissue the command. ORA-27486: insufficient privileges Cause: An attempt was made to perform a scheduler operation without the required privileges. Action: Ask a sufficiently privileged user to perform the requested operation, or grant the required privileges to the proper user(s). ORA-27487: invalid object privilege for a string Cause: The granted object privilege is not valid for the specified scheduler object. Action: Check the scheduler documentation to verify which object privileges can be granted on which scheduler objects. ORA-27488: unable to set string because string was/were already set Cause: An attempt was made to set an object"s attribute even though one or more conflicting attributes of the same object had already been set. Action: Set the other conflicting attributes to NULL and then reissue the command. ORA-27489: unable to process job "string.string" from job class "string" Cause: An error was encountered while processing the named job from the specified job class. Action: Resolve the error for this job and then reissue the command. See the next error message on the stack to find out what the error for the job is. ORA-27490: cannot open disabled window "string.string" Cause: The user tried to open a disabled window. Action: Enable the window and then try to open it again. ORA-27491: repeat_interval and start_date cannot both be NULL Cause: An attempt was made to set both repeat_interval and start_date to equal NULL for a Scheduler window or schedule. Action: If either repeat_interval or start_date is set to equal NULL, the other should be set to a non-NULL value. ORA-27500: inter-instance IPC error Cause: This is an operating system/cluster interconnect error. Action: Check the extra information and contact Oracle Support Services. ORA-27501: IPC error creating a port Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27502: IPC error deleting OSD context Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27503: IPC error attempting to cancel request Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27504: IPC error creating OSD context Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27505: IPC error destroying a port Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27506: IPC error connecting to a port Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27507: IPC error disconnecting from a port Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27508: IPC error sending a message Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27509: IPC error receiving a message Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27510: IPC error waiting for a request to complete Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27512: IPC error posting a process Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27513: parameter string contains invalid value string Cause: The program could not identify the value as an IP address. Action: Change the value to be a valid IP address. ORA-27542: Failed to unprepare a buffer prepared for remote update Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27543: Failed to cancel outstanding IPC request Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27544: Failed to map memory region for export Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27545: Fail to prepare buffer for remote update Cause: This is an operating system/cluster interconnect error. Action: Check the value of errno and contact Oracle Support Services. ORA-27546: Oracle compiled against IPC interface version string.string found version string.string Cause: A misconfiguration or installation error occurred. Action: Install the IPC library for this release of Oracle. ORA-27547: Unable to query IPC OSD attribute string Cause: This is an operating system-dependent IPC error. Action: Contact Oracle support Services. ORA-27548: Unable to unprepare IPC buffer Cause: This is an operating system-dependent IPC error. Action: Contact Oracle support Services. ORA-27550: Target ID protocol check failed. tid vers=number, type=number, remote instance number=number, local instance number=number Cause: The local Oracle Real Application Cluster instance and remote instance are running with incompatible implementation of the inter-instance IPC protocol library. A misconfiguration or installation error occurred. Action: Check additional error messages in the alert log and the process trace file. ORA-28000: the account is locked Cause: The user has entered wrong password consequently for maximum number of times specified by the user"s profile parameter FAILED_LOGIN_ATTEMPTS, or the DBA has locked the account Action: Wait for PASSWORD_LOCK_TIME or contact DBA ORA-28001: the password has expired Cause: The user"s account has expired and the password needs to be changed Action: change the password or contact the DBA ORA-28002: the password will expire within string days Cause: The user"s account is about to about to expire and the password needs to be changed Action: change the password or contact the DBA ORA-28003: password verification for the specified password failed Cause: The new password did not meet the necessary complexity specifications and the password_verify_function failed Action: Enter a different password. Contact the DBA to know the rules for choosing the new password ORA-28004: invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string Cause: The password verification function does not have the required number and type of input/output arguments and/or the return argument Action: Check the manual to find out the format of the password verification function ORA-28005: invalid logon flags Cause: The flags are not properly set or conflicting flags are set in making calls Action: Call the function with appropriate flags set. ORA-28006: conflicting values for parameters string and string Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set Action: Set one value to UNLIMITED explicitly ORA-28007: the password cannot be reused Cause: The password cannot be reused for the specified number of days or for the specified nunmber of password changes Action: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement ORA-28008: invalid old password Cause: old password supplied is wrong; Hence user cannot be authenticated using old password Action: Supply the correct old password for authentication ORA-28009: connection as SYS should be as SYSDBA or SYSOPER Cause: connect SYS/ is no longer a valid syntax Action: Try connect SYS/ as SYSDBA or connect SYS/ as SYSOPER ORA-28010: cannot expire external or global accounts Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired Action: Try to expire the password of the user that has database password ORA-28011: the account will expire soon; change your password now Cause: The user"s account is marked for expiry; the expiry period is unlimited. Action: Change the password or contact the DBA. ORA-28012: Manual commit not allowed here Cause: An attempt was made to commit a non-autonomous transaction from within a change password trigger or password verification routine Action: Remove the COMMIT from the password trigger or password verification routine ORA-28020: IDENTIFIED GLOBALLY already specified Cause: The IDENTIFIED GLOBALLY clause was specified twice. Action: Use only one IDENTIFIED GLOBALLY clause. ORA-28021: cannot grant global roles Cause: A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain. Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority. ORA-28022: cannot grant external roles to global user or role Cause: A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles. Action: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee. ORA-28023: must revoke grants of this role to other user(s) first Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role. Action: Use REVOKE to revoke the role from other users or roles first. ORA-28024: must revoke grants of external roles to this role/user Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted - these must be revoked, since external roles cannot be granted to global users or roles. Action: Use REVOKE to revoke the external roles from the user or role to be ALTERed. ORA-28025: missing or null external name Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name. Action: Provide a valid external name. ORA-28026: user with same external name already exists Cause: The external name specified for the user being created or altered already exists for another user. Action: External names must be unique among users. Specify another. ORA-28027: privileged database links may be used by global users Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link. Action: Either change the user to a global user or try to use a different database link. ORA-28028: could not authenticate remote server Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow. Action: Consult the network security service documentation on how to properly configure the remote server. ORA-28029: could not authorize remote server for user string Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package. Action: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access. ORA-28030: Server encountered problems accessing LDAP directory service Cause: Unable to access LDAP directory service Action: Please contact your system administrator ORA-28031: maximum of string enabled roles exceeded Cause: The user attempted to enable too many roles. Action: Enable fewer roles. ORA-28035: Cannot Get Session Key for Authentication Cause: Client and server cannot negotiate shared secret during logon Action: User should not see this error. Please contact your system administrator ORA-28037: Cannot Get Session Key for RACF Authentication Cause: Client and server cannot negotiate shared secret during logon Action: User should not see this error. Please contact your system administrator ORA-28038: disallow O2LOGON Cause: turn off O2LOGON Action: none ORA-28039: cannot validate Kerberos service ticket Cause: The Kerberos service ticket provided was invalid or expired Action: Provide a valid, unexpired service ticket. ORA-28040: No matching authentication protocol Cause: No acceptible authentication protocol for both client and server Action: Administrator should set SQLNET_ALLOWED_LOGON_VERSION parameter on both client and servers to values that matches the minimum version supported in the system. ORA-28041: Authentication protocol internal error Cause: Authentication protocol failed with an internal error Action: none ORA-28042: Server authentication failed Cause: Server failed to authenticate itself to the client Action: Confirm that the server is a valid database server. ORA-28043: invalid bind credentials for DB-OID connection Cause: The Database password stored in the wallet did not match the one in OID . Action: Use DBCA to reset the database password so that it is the same in database wallet and in OID. ORA-28044: unsupported directory type Cause: The database tried to work with a directory which is not OID. Action: Enterprise User Security works only with Oracle Internet Directory. Update the ldap.ora file to reflect an appropriate OID. ORA-28045: SSL authentication between database and OID failed Cause: Server failed to authenticate itself to the Directory. Action: Make sure the sqlnet.ora used is pointing to the wallet with the right certificate. ORA-28046: Password change for SYS disallowed Cause: REMOTE_LOGIN_PASSWORDFILE is set to SHARED, prohibiting SYS password changes. Action: Change setting of REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE or NONE. ORA-28047: database is not a member of any enterprise domain in OID Cause: An enterprise user login was attempted on a database that is not a member of any enterprise domain in OID. Action: An administrator should put the database into an enterprise domain in OID, and then the user should reconnect. ORA-28048: database is a member of multiple enterprise domains in OID Cause: An enterprise user login was attempted on a database that is a member of multiple enterprise domains in OID. Action: An administrator should put the database into only one enterprise domain in OID, and then the user should reconnect. ORA-28049: the password has expired Cause: The enterprise user"s password has expired and the password needs to be changed. Action: change the password in the directory or contact the directory administrator. ORA-28051: the account is locked Cause: The enterprise user has consecutively entered the wrong password for maximum number of times specified in the realm"s password policy profile. Action: Contact the directory administrator. ORA-28052: the account is disabled Cause: The enterprise user"s account in the directory has been disabled. Action: Contact the directory administrator. ORA-28053: the account is inactive Cause: The enterprise user"s account in the directory is currently not active. Action: Contact the directory administrator. ORA-28054: the password has expired. string Grace logins are left Cause: The enterprise user"s password has expired. The user is able to login because he has gracelogins left. Action: change the password in the directory or contact the directory administrator. ORA-28055: the password will expire within string days Cause: The enterprise user"s password is about to expire. Action: Change the password in the directory or contact the directory administrator. ORA-28100: policy function schema string is invalid Cause: The schema was dropped after the policy associated with the function had been added to the object. Action: Drop the policy and re-create it with a policy function owned by a valid user. Or re-create the user and the policy function under the new user. ORA-28101: policy already exists Cause: A policy with the same name for the same object already exists. Action: Check if the policy has already been added or use a different policy name. ORA-28102: policy does not exist Cause: Try to drop/enable/refresh a non-existent policy. Action: Correct the policy name argument. ORA-28103: adding a policy to an object owned by SYS is not allowed Cause: Try to add a policy to a table or a view owned by SYS. Action: You can not perform this operation. ORA-28104: input value for string is not valid Cause: Input value for the argument is not valid Action: specify a valid argument value. ORA-28105: cannot create security relevant column policy in an object view Cause: Security relevant column argument is not null in policy creation for an object view Action: none ORA-28106: input value for argument #string is not valid Cause: Input values for the argument is missing or invalid. Action: Correct the input values. ORA-28107: policy was disabled Cause: Try to flush a disabled policy. Action: If the policy is supposed to be enforced, it must be enabled. ORA-28108: circular security policies detected Cause: Policies for the same object reference each other. Action: Drop the policies ORA-28109: the number of related policies has exceeded the limit of 16 Cause: Too many policies are involved in the same objects. Action: Drop one or more policies. Or combine a few of them into one. ORA-28110: policy function or package string.string has error Cause: The policy function may have been dropped, or is no longer valid. Action: Check the status of the function and correct the problem. Or re-create the policy with a valid function. ORA-28111: insufficient privilege to evaluate policy predicate Cause: Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access. Action: Grant appropriate privileges to the policy function owner. ORA-28112: failed to execute policy function Cause: The policy function has one or more error during execution. Action: Check the trace file and correct the errors. ORA-28113: policy predicate has error Cause: Policy function generates invalid predicate. Action: Review the trace file for detailed error information. ORA-28115: policy with check option violation Cause: Policy predicate was evaluated to FALSE with the updated values. Action: none ORA-28116: insufficient privileges to do direct path access Cause: Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies. Action: Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully. ORA-28117: integrity constraint violated - parent record not found Cause: try to update/insert a child record with new foreign key values, but the corresponding parent row is not visible because of fine-grained security in the parent. Action: make sure that the updated foreign key values must also visible in the parent ORA-28118: policy group already exists Cause: try to create a policy group that already exists Action: none ORA-28119: policy group does not exist Cause: try to drop a policy group that does not exist Action: none ORA-28120: driving context already exists Cause: try to create a driving context that already exists Action: none ORA-28121: driving context does not exist Cause: try to drop a driving context that does not exist Action: none ORA-28132: Merge into syntax does not support security policies. Cause: Merge into syntax currently does not support a security policy on the destination table. Action: use the insert / update DML stmts on the table that has a security policy defined on it. ORA-28134: object cannot have fine-grained access control policy Cause: Only tables, views, or synonyms of tables or views may have VPD policies Action: none ORA-28137: Invalid FGA audit Handler Cause: An invalid audit handler was specified. Action: Specify a valid audit handler. ORA-28138: Error in Policy Predicate Cause: An invalid policy predicate was specified. Action: Please specify a valide policy Predicate for the FGA policy ORA-28139: Maximum allowed Fine Grain Audit Policies Exceeded Cause: A maximum of 256 policies can be enabled on an object Action: Drop or disable an existing policy before creating more ORA-28140: Invalid column specified Cause: Column name specified during policy creation is invalid Action: Please specify a valid column name. Object columns are not supported ORA-28141: error in creating audit index file Cause: ORACLE was not able to create the file being used to hold audit file names. Action: Examine the directory pointed to by the initialization parameter "audit_file_dest." Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory and not a file. 3. The directory is accessible and writable to the ORACLE user. ORA-28142: error in accessing audit index file Cause: ORACLE was not able to access the file being used to hold audit file names. Action: Make sure the file exists in the directory pointed to by the initialization parameter "audit_file_dest" and is readable by the ORACLE user. ORA-28150: proxy not authorized to connect as client Cause: A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client. Action: Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER ... GRANT CONNECT command. ORA-28151: more than one user name specified for command Cause: More than one user name was specified for an ALTER USER command. Action: Try the command again with only one user name. ORA-28152: proxy user "string" may not specify initial role "string" on behalf of client "string" Cause: A proxy user attempted to specify an initial role for a client, but the client does not possess the role. Action: Change the proxy user so that it does not specify the role or grant the role to the client. ORA-28153: Invalid client initial role specified: "string" Cause: A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid. Action: Connect again as the client specifying a valid role. ORA-28154: Proxy user may not act as client "string" Cause: A proxy user may not assume the identity of a privileged user in order to limit the privileges that a proxy may possess. Action: Execute the statement again specify a client other than a privileged user. ORA-28155: user "string" specified as a proxy is actually a role Cause: A user specified in an AUDIT BY ON BEHALF OF is actually a role. Action: Execute the statement again with a valid proxy user. ORA-28156: Proxy user "string" not authorized to set role "string" for client "string" Cause: A proxy user has not been granted the right to use a role on behalf of a client. Action: Execute the command ALTER USER GRANT CONNECT THROUGH PROXY to grant the needed role. ORA-28157: Proxy user "string" forbidden to set role "string" for client "string" Cause: A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER GRANT CONNECT THROUGH WITH ALL ROLES EXCEPT Action: Execute the command ALTER USER GRANT CONNECT THROUGH PROXY to grant the needed role. ORA-28163: GRANT already specified Cause: The GRANT clause was specified twice. Action: Use only one GRANT clause. ORA-28164: REVOKE already specified Cause: The REVOKE clause was specified twice. Action: Use only one REVOKE clause. ORA-28165: proxy "string" may not specify password-protected role "string" for client "string" Cause: A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed. Action: Attempt to activate a different role or change the role administratively so that there is no password. ORA-28166: duplicate rolename in list Cause: The name of a role was specified more than once in a list. Action: Repeat the command specifying the role once. ORA-28168: attempted to grant password-protected role Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client. Action: Either specify a role that does not have a password or alter the role so that a password is not required. ORA-28169: unsupported certificate type Cause: The type of certificate from which the server is to extract the credentials of the client is not supported. Action: Specify a supported type. ORA-28170: unsupported certificate version Cause: The version of the certificate from which the server is to extract the credentials of the client is not supported. Action: Specify a supported version. ORA-28171: unsupported Kerberos version Cause: the version the Kerberos ticket which the server is to use to validate the identity of the client is not supported. Action: Specify a supported version. ORA-28172: distinguished name not provided by proxy Cause: A client user is to be identified using a distinguished name, but none was provided by the proxy user. Action: Provide a distinguished name. ORA-28173: certificate not provided by proxy Cause: A client user is to be identified using a certificate but none was provided by the proxy user. Action: Provide a certificate. ORA-28174: Kerberos ticket not provided by proxy Cause: A client user is to be authenticated using a Kerberos ticket but none was provided by the proxy user. Action: Provide a Kerberos ticket. ORA-28175: incorrect certificate type Cause: the type of certificate provided by the proxy user to identify a client user does not match the type that is required. Action: Provide a certificate of the correct type. ORA-28176: incorrect certificate version Cause: the version of certificate provided by the proxy user to identify a client user does not match the version that is required. Action: Provide a certificate of the correct version. ORA-28177: incorrect Kerberos ticket version Cause: the version of Kerberos ticket provided by the proxy user to authenticate a client user does not match the version that is required. Action: Provide a Kerberos ticket of the correct version. ORA-28178: password not provided by proxy Cause: A client user is to be authenticated using a database password but none was provided by the proxy user. Action: Provide a password. ORA-28179: client user name not provided by proxy Cause: No user name was provided by the proxy user for the client user. Action: Either specify a client database user name, a distinguished name or an X.509 certificate. ORA-28180: multiple authentication methods provided by proxy Cause: More than one authentication method was specified by the proxy user for the client user. Action: Specify only one of the following: a client database user name, a distinguished name or an X.509 certificate. ORA-28181: proxy "string" failed to enable one or more of the specified initial roles for client "string" Cause: Attempt to enable specified initial roles after logon resulted in failure. Action: Check that the initial roles are valid, granted to client, and not password protected. ORA-28182: cannot acquire Kerberos service ticket for client Cause: An attempt to use a Kerberos forwardable ticket granting ticket to obtain a Kerberos service ticket failed. Action: Check that the Kerberos forwardable ticket granting ticket belongs to the client, is valid, and that the key distribution center is available. ORA-28183: proper authentication not provided by proxy Cause: A client user must be authenticated but no authentication credentials were provided by the proxy user. Action: Provide some form of authentication credentials. ORA-28184: global user cannot have proxy permissions managed in the directory Cause: The client name specified was a global user. Action: Use ALTER USER to change the type of user (from IDENTIFIED GLOBALLY to something else, such as IDENTIFIED BY password or IDENTIFIED EXTERNALLY). ORA-28200: IDENTIFIED USING already specified Cause: The IDENTIFIED USING clause was specified twice. Action: Use only one IDENTIFIED USING clause. ORA-28201: Not enough privileges to enable application role "string" Cause: An attempt to enable application role outside the scope of the designated package Action: Enable the role directly or indirectly using the designated package ORA-28221: REPLACE not specified Cause: User is changing password but password verification function is turned on and the original password is not specified and the user does not have the alter user system privilege. Action: Supply the original password. ORA-28231: no data passed to obfuscation toolkit Cause: A NULL value was passed to a function or procedure. Action: Make sure that the data passed is not empty. ORA-28232: invalid input length for obfuscation toolkit Cause: Length of data submitted for encryption or decryption is not a multiple of 8 bytes. Action: Make sure that the length of the data to be encrypted or decrypted is a multiple of 8 bytes. ORA-28233: double encryption not supported Cause: The obfuscation toolkit does not support the encryption of already-encrypted data. Action: Do not attempt to encrypt already-encrypted data. ORA-28234: key length too short Cause: The key specified is too short for the algorithm. DES requires a key of at least 8 bytes. Triple DES requires a key of least 16 bytes in two-key mode and 24 bytes in three-key mode. Action: Specify a longer key. ORA-28235: algorithm not available Cause: The encryption algorithm desired is not available. Action: Run the installer to install the needed algorithm in Oracle Advanced Security. ORA-28236: invalid Triple DES mode Cause: An unknown value was specified for the mode in which triple DES encryption is to run. Action: Specify a valid value. See the package declaration for a list of valid values. ORA-28237: seed length too short Cause: The seed specified for the key generation routine must be at least 80 characters. Action: Specify a longer seed. ORA-28238: no seed provided Cause: A NULL value was passed in as the seed to be used in generating a key. Action: Provide a non-NULL value for the seed. ORA-28239: no key provided Cause: A NULL value was passed in as an encryption or decryption key. Action: Provide a non-NULL value for the key. ORA-28261: CURRENT_USER can not be used in PLSQL Definer"s Right procedure. Cause: An attempt to retrieve CURRENT_USER using SYS_CONTEXT PLSQL interface. Action: Use a SQL statement to query CURRENT_USER inside a DR procedure. ORA-28262: global_context_pool_size has invalid value. Cause: Parameter global_context_pool_size has a value less than the minimum required value (10K). Action: Please specify a value for the init.ora parameter global_context_pool_size which is atleast 10k. ORA-28263: Insufficient memory in global context pool Cause: Allocations for the global context heap exceeded the value set in init.ora. Action: Increase the value of global_context_pool_size parameter in init.ora or clear usused global context. ORA-28264: Client identifier is too long Cause: The length of the client identifier is longer than 64 Action: Set a client identifier whose length is less than 64. ORA-28265: NameSpace beginning with "sys_" is not allowed Cause: Namespace beginning with "sys_" is not allowed. Action: Use a namespace that does not begin with "sys_". ORA-28267: Invalid NameSpace Value Cause: Context NameSpace conflicts with reserved key words or a secure Namespace is not allowed for this type of Application Context. Action: Use a valid namespace. ORA-28268: Exceeded the maximum allowed size for Context information in a session Cause: The maximum size specified by the _session_context_size init.ora parameter was exceeded. Action: Please change the value for _session_context_size in the init.ora file. ORA-28270: Malformed user nickname for password authenticated global user. Cause: An attempt to login as password-auuthenticated global user with a malformed user nickname. Action: Make sure the nickname is valid and re-login. ORA-28271: No permission to read user entry in LDAP directory service. Cause: ORACLE server does not have read permission on user nickname"s X.500 user entry. Action: Make sure ORACLE server is using right SSL credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are right. ORA-28272: Domain policy restricts password based GLOBAL user authentication. Cause: Domain policy does not allow password-authenticated GLOBAL users. Action: Make sure ORACLE server is using right SSL credentials to connect to LDAP directory services. Make sure orclDBAuthTypes attributes within Oracle enterprise domain object is either set to PWD or ALL. ORA-28273: No mapping for user nickname to LDAP distinguished name exists. Cause: ORACLE server cannot map the given user nickname to LDAP distinguished name. Action: Make sure user entries in LDAP are correctly provisioned with correct user nickname attribute values. ORA-28274: No ORACLE password attribute corresponding to user nickname exists. Cause: LDAP user entry corresponding to user nickname does not have a ORACLE password attribute or the attribute is not initialized. Action: Make sure user entries in LDAP are correctly provisioned with correct ORACLE password attribute values. ORA-28275: Multiple mappings for user nickname to LDAP distinguished name exist. Cause: The given user nickname maps to more than one LDAP distinguished name. Action: Make sure user nickname is unique within the enterprise. ORA-28276: Invalid ORACLE password attribute. Cause: The ORACLE password attribute of a user entry has an invalid format. Action: Make sure ORACLE password attribute value is RFC-2307 compliant. ORA-28277: LDAP search, while authenticating global user with passwords, failed. Cause: The LDAP search for finding the appropriate user entry and ORACLE password failed. Action: Make sure LDAP directory service is up and running. ORA-28278: No domain policy registered for password based GLOBAL users. Cause: No policy about password authenticated GLOBAL users has been registered. Action: Add attribute orclDBAuthTypes to the database server"s Enterprise domain. ORA-28279: Error reading ldap_directory_access init parameter. Cause: ldap_directory_access parameter is not specified corrrectly. Action: Make sure spfile.ora has ldap_directory_access set correctly. Possible correct values are PASSWORD, SSL and NONE. ORA-28280: Multiple entries for ORACLE database password exist. Cause: The ORACLE password attribute of a user entry has multiple entries of ORACLE database password. Action: Make sure ORACLE password attribute has one entry for ORACLE Database password. ORA-28290: Multiple entries found for the same Kerberos Principal Name Cause: Multiple user entries has been configured with the same krbPrincipalName Action: Modify enterprise user"s entry to assign its Kerberos principal name Make sure the user entries in LDAP are provisioned correctly. ORA-28291: No Kerberos Principal Value found. Cause: Oracle server fails to get value of krbPrincipalName attribute Action: Make sure user entries are correctly provisioned with correct Kerberos principal value ORA-28292: No Domain Policy registered for Kerberos based authentication Cause: The enterprise domain entry is not configured for Kerberos based global authentication. Action: Modify orclDBAuthType of the database server"s enterprise domain entry and assign it "ALL" or "KRB5" ORA-28293: No matched Kerberos Principal found in any user entry Cause: Oracle server fails to find the principal in the user search base Action: Make sure the user search base is correct. Use ESM to configure the enterprise user its Kerberos principal name ORA-28300: No permission to read user entry in LDAP directory service. Cause: ORACLE server does not have read permission on user entries. Action: Make sure ORACLE server is using right credentials to connect to LDAP directory services. Make sure permissions for LDAP user entries are configured correctly. ORA-28301: Domain Policy hasn"t been registered for SSL authentication. Cause: An attempt was made to authenticate with SSL, but the database enterprise domain was not configured for SSL authentication. Action: Modify orclDBAuthType of the server"s enterprise domain entry and assign it "ALL" or "SSL". ORA-28302: User does not exist in the LDAP directory service. Cause: An attempt was made to authenticate with SSL using the user"s certificate, but there was no user entry in the LDAP server that matched the user"s Distinguished Name. Action: Add an user entry whose DN matches the user"s PKI DN in the LDAP directory. ORA-28330: encryption is not allowed for this data type Cause: Data type was not supported for column encryption. Action: none ORA-28331: encrypted column size too long for its data type Cause: column was encrypted and for VARCHAR2, the length specified was > 3932; for CHAR, the length specified was > 1932; for NVARCHAR2, the length specified was > 1966; for NCHAR, the length specified was > 966; Action: Reduce the column size. ORA-28332: cannot have more than one password for the encryption key Cause: More than one password was specified in the user command. Action: none ORA-28333: column is not encrypted Cause: An attempt was made to rekey or decrypt an unencrypted column. Action: none ORA-28334: column is already encrypted Cause: An attempt was made to encrypt an encrypted column. Action: none ORA-28335: referenced or referencing FK constraint column cannot be encrypted Cause: encrypted columns were involved in the referential constraint Action: none ORA-28336: cannot encrypt SYS owned objects Cause: An attempt was made to encrypt columns in a table owned by SYS. Action: none ORA-28337: the specified index may not be defined on an encrypted column Cause: Index column was either a functional, domain, or join index. Action: none ORA-28338: cannot encrypt indexed column(s) with salt Cause: An attempt was made to encrypt index column with salt. Action: Alter the table and specify column encrypting without salt. ORA-28339: missing or invalid encryption algorithm Cause: Encryption algorithm was missing or invalid in the user command. Action: Must specify a valid algorithm. ORA-28340: a different encryption algorithm has been chosen for the table Cause: Existing encrypted columns were associated with a different algorithm. Action: No need to specify an algorithm, or specify the same one for the existing encrypted columns. ORA-28341: cannot encrypt constraint column(s) with salt Cause: An attempt was made to encrypt constraint columns with salt. Action: Encrypt the constraint columns without salt. ORA-28342: integrity check fails on column key Cause: Encryption metadata may have been improperly altered. Action: none ORA-28343: fails to encrypt data Cause: data or encryption metadata may have been improperly altered or the security module may not have been properly setup Action: none ORA-28344: fails to decrypt data Cause: data or encryption metadata may have been improperly altered or the security module may not have been properly setup Action: none ORA-28345: cannot downgrade because there exists encrypted column Cause: An attempt was made to downgrade when there was an encrypted column in the system. Action: Decrypt these columns before attempting to downgrade. ORA-28346: an encrypted column cannot serve as a partitioning column Cause: An attempt was made to encrypt a partitioning key column or create partitioning index with encrypted columns. Action: The column must be decrypted. ORA-28347: encryption properties mismatch Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but encryption properties were mismatched. Action: Make sure encrytion algorithms and columns keys are identical. The corresponding columns must be encrypted on both tables with the same salt and non-salt flavor. ORA-28348: index defined on the specified column cannot be encrypted Cause: An attempt was made to encrypt a column which is in a functional index, domain index, or join index. Action: drop the index ORA-28349: cannot encrypt the specified column recorded in the materialized view log Cause: An attempt was made to encrypt a column which is already recorded in the materialized view log. Action: drop the materialized view log ORA-28350: cannot encrypt the specified column recorded in CDC synchronized change table Cause: An attempt was made to encrypt a column which is already recorded in CDC synchronized change table. Action: drop the synchronized change table ORA-28353: failed to open wallet Cause: The database was unable to open the security module wallet due to an incorrect wallet path or password It is also possible that a wallet has not been created. Type mkwallet from command line for instructions. Action: Execute the command again using the correct wallet password or verfying a wallet exists in the specified directory. If necessary, create a new wallet and initialize it. ORA-28354: wallet already open Cause: The security module wallet has already been opened. Action: none ORA-28356: invalid open wallet syntax Cause: The command to open the wallet contained improper spelling or syntax. Action: If attempting to open the wallet, verify the spelling and syntax and execute the command again. ORA-28357: password required to open the wallet Cause: A password was not provided when executing the open wallet command. Action: Retry the command with a valid password. ORA-28358: improper set key syntax Cause: The command to set the master key contained improper spelling or syntax. Action: If attempting to set the master key for Transparent Database Encryption, verify the spelling and syntax and execute the command again. ORA-28359: invalid certificate identifier Cause: The certificate specified did not exist in the wallet. Action: Query the V$WALLET fixed view to find the proper certificate identifier for certificate to be used. ORA-28361: master key not yet set Cause: The master key for the instance was not set. Action: Execute the ALTER SYSTEM SET KEY command to set a master key for the database instance. ORA-28362: master key not found Cause: The required master key required could not be located. This may be casued by the use of an invalid or incorrect wallet. Action: Check wallet location parameters to see if they specify the correct wallet. Also, verify that an SSO wallet is not being used when an encrypted wallet is intended. ORA-28363: buffer provided not large enough for output Cause: A provided output buffer is too small to contain the output. Action: Check the size of the output buffer to make sure it is initialized to the proper size. ORA-28364: invalid wallet operation Cause: The command to operate the wallet contained improper spelling or syntax. Action: Verify the spelling and syntax and execute the command again. ORA-28365: wallet is not open Cause: The security module wallet has not been opened. Action: Open the wallet. ORA-28366: invalid database encryption operation Cause: The command for database encryption contained improper spelling or syntax. Action: Verify the spelling and syntax and execute the command again. ORA-28367: wallet does not exist Cause: The Oracle wallet has not been created or the wallet location parameters in sqlnet.ora specifies an invalid wallet path. Action: Verify that the WALLET_LOCATION or the ENCRYPTION_WALLET_LOCATION parameter is correct and that a valid wallet exists in the path specified. ORA-28368: cannot auto-create wallet Cause: The database failed to auto create an Oracle wallet. The Oracle process may not have proper file permissions or a wallet may already exist. Action: Confirm that proper directory permissions are granted to the Oracle user and that neither an encrypted or obfuscated wallet exists in the specified wallet location and try again. ORA-28500: connection from ORACLE to a non-Oracle system returned this message: Cause: The cause is explained in the forwarded message. Action: See the non-Oracle system"s documentation of the forwarded message. ORA-28501: communication error on heterogeneous database link Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system. Action: See the documentation for the non-Oracle system for an explanation of the second error message. ORA-28502: internal communication error on heterogeneous database link Cause: A communication error internal to ORACLE"s heterogeneous services has occurred. Action: Contact Oracle customer support. ORA-28503: bind value cannot be translated into SQL text for non-Oracle system Cause: A SQL statement used bind variables on a Heterogenous Services database link to a non-Oracle system, but the non-Oracle system does not support bind variables. Action: Change your SQL statement so that it does not use bind variables. ORA-28504: ROWID not found in ROWID cache for heterogeneous database link Cause: The ROWID cache for Heterogeneous Services held no entry that corresponds to the specified ROWID. The ROWID entry may have been overwritten in the ROWID cache. Action: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the Heterogenous Services initialization parameter HS_ROWID_CACHE_SIZE. ORA-28505: cannot get non-Oracle system capabilities from string Cause: ORACLE was unable to retrieve capability information for the non-Oracle system connected through a heterogeneous database link. This capability information should be stored in data dictionary tables viewable with the HS_CLASS_CAPS or HS_INST_CAPS data dictionary views. Action: Contact the DBA to check the server data dictionary table named in the error message. If table contents are incorrect, the DBA should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. ORA-28506: parse error in data dictionary translation for string stored in string Cause: A reference to an ORACLE data dictionary table or view name on a heterogeneous database link to a non-Oracle system could not be translated. The ORACLE data dictionary tables shown with view HS_CLASS_DD contain invalid SQL for the data dictionary translation. Action: Contact customer support of the agent vendor. ORA-28507: error in data dictionary view string Cause: The initialization parameter table for the Heterogeneous Services was not available, or its structure (number of columns or column types) was incorrect. Action: Verify correct installation of the following Heterogeneous Services" initialization parameter views: HS_CLASS_INIT and HS_INST_INIT. If these views are not available, make sure you ran the script CATHS.SQL in the $ORACLE_HOME/rdbms/admin directory. ORA-28508: invalid value string for Heterogeneous Services initialization parameter string Cause: The specified Heterogeneous Services initialization parameter had an invalid value when attempting to connect to a non-Oracle system. Action: Check the Heterogeneous Services and agent documentation to determine acceptable values ORA-28509: unable to establish a connection to non-Oracle system Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system. Action: Check the Net8 service name definition in the following places: -- the USING clause of the CREATE DATABASE LINK statement -- the TNSNAMES.ORA file -- the Oracle Names Server The following are possible reasons for name mismatches: -- The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in the TNSNAMES.ORA file or in the Oracle Names Server. -- The protocol-specific information in the service name definition must match the protocol-specific definition of the responding listener. -- The SID= in the service name definition (in the TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener. ORA-28510: heterogeneous database link initialization failed Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system. Action: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly. ORA-28511: lost RPC connection to heterogeneous remote agent using SID=string Cause: A fatal error occurred in one of the following places: -- the connection between the ORACLE server and the agent -- the heterogeneous services remote agent itself -- the connection to the non-Oracle system This error occurred after communication had been established successfully. Action: Check for network problems and remote host crashes. The problem is probably in the agent software. If so, contact a customer support representative of the agent vendor. ORA-28512: cannot get data dictionary translations from string Cause: ORACLE was unable to retrieve data dictionary translation information for the non-Oracle system connected through a heterogeneous database link. This data dictionary translation information should be stored in data dictionary tables viewable with the HS_CLASS_DD or HS_INST_DD data dictionary views. Action: Ask your DBA to check the server data dictionary table named in the error message. If table contents are incorrect, the DBA should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. ORA-28513: internal error in heterogeneous remote agent Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link. Action: Make a note of how the error was produced and contact the customer support representative of the agent vendor. ORA-28514: heterogeneous database link initialization could not convert system date Cause: The system date was not retrievable. Action: Verify that the ORACLE server"s host machine and operating system are operational. This error should not occur unless low level system functions are failing. ORA-28515: cannot get external object definitions from string Cause: ORACLE was unable to retrieve definitions of distributed external procedures or remote libraries registered for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is malformed. Action: Verify that the ORACLE server"s Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. ORA-28518: data dictionary translation has illegal translation type Cause: A data dictionary translation definition, either in the ORACLE server data dictionary or in data dictionary content uploaded from a Heterogeneous Services agent, specified an illegal translation type code. Legal values are "T" or "t" for "translate", "M" or "m" for "mimic". Information on the exact data dictionary translation causing the error is written to a trace (*.TRC) file for the ORACLE instance and to the ORACLE instance"s alert log. This error occurs when a Heterogeneous Services agent uploads data dictionary content to an ORACLE server on the first connection from the server to the agent. Action: Contact the customer support of the agent vendor. ORA-28519: no heterogeneous data dictionary translations available Cause: The ORACLE server"s data dictionary did not define data dictionary translations for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled. Action: Ask a DBA to resolve this problem. The easiest solution is to enable automatic self-registration by setting the ORACLE server"s HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact the customer support representative of the agent vendor. ORA-28520: error initializing heterogeneous data dictionary translations Cause: ORACLE was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly. Action: Verify that the ORACLE server"s Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the ORACLE server, verify that the script has been run. If both scripts were executed and the error persists, contact the customer support representative of the agent vendor. ORA-28521: no heterogeneous capability information available Cause: The ORACLE server"s data dictionary did not contain capability definitions for the connected non-Oracle system, and automatic self-registration (data dictionary upload) was disabled. Action: Ask a DBA to resolve this problem. The easiest resolution is to enable automatic self-registration by setting the ORACLE server"s HS_AUTO_REGISTER initialization parameter to TRUE. An alternative is to load the Heterogeneous Services data dictionary with information specific for the non-Oracle system by executing a SQL script supplied by the agent vendor. If the script is run and the error persists, contact the customer support representative of the agent vendor. ORA-28522: error initializing heterogeneous capabilities Cause: ORACLE was unable to retrieve capability definitions for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is formed incorrectly. Action: Verify that the ORACLE server"s Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHS.SQL script in the $ORACLE_HOME/rdbms/admin directory. If the connected agent, identified by FDS_CLASS_NAME, requires a custom installation script for the ORACLE server, verify that the script has been run. If both scripts were executed and the error persists, contact the customer support representative of the agent vendor. ORA-28523: ORACLE and heterogeneous agent are incompatible versions Cause: An operation on a database link attempted to connect to a non-Oracle system, but the ORACLE instance and the agent process for the non-Oracle system are incompatible. Action: Ask your DBA to confirm configuration of both the ORACLE instance and the agent. Additional information on the version incompatibility is logged in trace (*.TRC) files, the ORACLE instance and the agent, and in the ORACLE instance"s alert log. Check the documentation for your agent to find out which releases of the Oracle Server are supported. ORA-28525: unable to create Heterogeneous Services error message text Cause: Incorrect arguments were passed into the error message creation routine. Action: Contact Oracle customer support. ORA-28526: invalid describe information returned to Heterogeneous Services Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services" non-Oracle system agent. Action: Contact customer support of the agent vendor. ORA-28527: Heterogeneous Services datatype mapping error Cause: Either an Oracle datatype could not be mapped to a non-Oracle datatype, or a non-Oracle datatype could not be mapped to an Oracle datatype. These mappings are defined as capability definitions in the ORACLE server"s data dictionary. Action: Verify that the ORACLE server"s data dictionary has been initialized with correct capability definitions for the connected FDS_CLASS_NAME and FDS_INST_NAME. If table contents are incorrect, a DBA should restore all data dictionary content for this FDS_CLASS_NAME and/or FDS_INST_NAME. It usually is sufficient to delete all current data dictionary content for this class and/or instance and initiate a new connection to let the connected agent upload new data dictionary content to the server. If the error persists contact the customer support representative of the agent vendor. ORA-28528: Heterogeneous Services datatype conversion error Cause: Either an Oracle datatype could not be converted to a non-Oracle datatype, or a non-Oracle datatype could not be converted to an Oracle datatype. The following are possible reasons for for the conversion failure: -- overflow problems (in the case of numbers) -- length limitations (in the case of character strings) -- invalid values passed into the conversion routines Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it may not be possible to convert the value. ORA-28529: invalid or missing parameter in Net8 service name definition Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names Server. Action: Ask your DBA to make sure the information in the Net8 service definition is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent"s documentation. ORA-28530: Heterogeneous Services initialization error in NLS language ID Cause: Heterogeneous Services was unable to initialize an NLS language ID. Both the ORACLE server and the Heterogeneous Services agent for the connected non-Oracle system must have language IDs. Action: Contact Oracle customer support. ORA-28533: Heterogeneous Services coercion handling error Cause: The Heterogeneous Services encountered an error in coercion handling. The HS can, if the agent vendor so chooses, perform extra processing on SQL statements that contain implicit coercions or that contain coercion functions such as TO_CHAR, TO_NUMBER or TO_DATE. This functionality is controlled by coercion-related capabilities. HS logic reports this error when it encounters an error in one of these capability definitions. Action: The capability table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and agent vendor and get the correct set of capabilities installed. ORA-28534: Heterogeneous Services preprocessing error Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the HS could encounter errors when it attempts to do the preprocessing. If it does then this error will be signaled. Action: The capability table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and agent vendor and get the correct set of capabilities installed. ORA-28535: invalid Heterogeneous Services context Cause: A Heterogeneous Services agent"s driver module called an HS service routine with an invalid HS context value. This probably is a logic error in the driver. Action: Contact Oracle customer support or your agent vendor. ORA-28536: error in processing Heterogeneous Services initialization parameters Cause: An error described by a subsequent error message prevented successful processing of Heterogeneous Services initialization parameters from the ORACLE server data dictionary. Action: Check server data dictionary views HS_CLASS_INIT, HS_INST_INIT, and HS_ALL_INITS. Look for conditions which could produce the error identified in the error message immediately following this one. ORA-28537: no more result sets Cause: This error code is used internally within Oracle Transparent Gateway and Heterogeneous Services code and should not be reported to a client program. Action: Contact Oracle customer support. ORA-28538: result set not found Cause: The client program tried fetching from a result set that is not open anymore. Many gateways will, on execution of a stored procedure, automatically close all result sets that were returned by any previously executed stored procedure. Action: Check the documentation for the gateway that you are using and see if it will automatically close currently open result sets each time a stored procedure is executed. Then check if your client program is doing anything that violates this rule. If it is, fix your program. If it is not then contact Oracle customer support. ORA-28539: gateway does not support result sets Cause: The client program tried executing a stored procedure that returns one or more result sets through a gateway that does not have result set support. Action: Check the documentation for the gateway that you are using and see if it supports result sets returned from stored procedures. If it does not, then the only way of accessing such stored procedures is to upgrade to a version of the gateway that does support result sets (if such a version exists). If the gateway does have result set support and you are still seeing this error then contact Oracle customer support. ORA-28540: internal result set error Cause: A protocol error internal to Heterogeneous Services or Transparent Gateway code has occurred. Action: Contact Oracle customer support. ORA-28541: Error in HS init file on line number. Cause: A syntax error occurred in the gateway initialization file. Action: Check gateway init file to correct the syntax error. For further information, check the error message in the gateway trace file. ORA-28542: Error in reading HS init file Cause: Reading the gateway init file generated an error. Action: Check the gateway initialization file name to see that the gateway initialization file acctually exists. Check the ifile parameter to see that it points to the correct location. ORA-28543: Error initializing apply connection to non-Oracle system Cause: Attempt to initialize connection to non-Oracle for heterogeneous replication failed. Action: Check if the listener used to connect to the gateway is up and is correctly configured. Make sure that the database link used has been configured correctly and, if a tnsnames alias has been used in the database link definition, make sure that the configuration of the entry in tnsnames.ora has been done correctly. ORA-28544: connect to agent failed, probable Net8 administration error Cause: Net8 reported a failure to make a RSLV connection or a protocol mode error when the Oracle server attempted to establish communication with a Heterogeneous Services agent or an external procedure agent. This usually is due to an administration error in setting up Net8 service definitions in TNSNAMES.ORA or LISTENER.ORA: A basic network connection is opened, but it connects to a program which does not use the appropriate protocol. This often is a sign that the connection goes to the wrong program. Action: Check Net8 administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID. -- Check LISTENER.ORA on the agent"s host machine to assure that the service name or SID refers to the correct agent executable in its (PROGRAM=...) clause. -- Confirm in TNSNAMES.ORA or the equivalent service definition that sevice "extproc_connection_data" does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=). ORA-28545: error diagnosed by Net8 when connecting to an agent Cause: An attempt to call an external procedure or to issue SQL to a non-Oracle system on a Heterogeneous Services database link failed at connection initialization. The error diagnosed by Net8 NCR software is reported separately. Action: Refer to the Net8 NCRO error message. If this isn"t clear, check connection administrative setup in tnsnames.ora and listener.ora for the service associated with the Heterogeneous Services database link being used, or with "extproc_connection_data" for an external procedure call. ORA-28546: connection initialization failed, probable Net8 admin error Cause: A failure occurred during initialization of a network connection from the Oracle server to a second process: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Net8 administrative setup for database links or external procedure calls. The most frequent specific causes are: -- Database link setup for an Oracle-to-Oracle connection instead connects to a Heterogeneous Services agent or an external procedure agent. -- Database link setup for a Heterogeneous Services connection instead connects directly to an Oracle server. -- The extproc_connection_data definition in tnsnames.ora connects to an Oracle instance instead of an external procedure agent. -- Connect data for a Heterogeneous Services database link, usually defined in tnsnames.ora, does not specify (HS=). -- Connect data for an Oracle-to-Oracle database link, usually defined in tnsnames.ora, specifies (HS=). Action: Check Net8 administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID. -- Check LISTENER.ORA on the connection end point"s host machine to assure that this service name or SID connects to the correct program. -- Confirm in TNSNAMES.ORA or the equivalent service definition that service "extproc_connection_data" does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=). ORA-28547: connection to server failed, probable Oracle Net admin error Cause: A failure occurred during initialization of a network connection from a client process to the Oracle server: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Oracle Net administrative setup for database links or external procedure calls. The most frequent specific causes are: -- The connection uses a connect string which refers to a Heterogeneous Services agent instead of an Oracle server. -- The connection uses a connect string which includes an (HS=) specification. Action: Check Oracle Net administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the client connection to the ORACLE server uses the correct service name or SID. -- Check LISTENER.ORA on the connection end point"s host machine to assure that this service name or SID refers to the correct server. -- Confirm in TNSNAMES.ORA or the equivalent service definition that the connect string does NOT contain (HS=). ORA-28550: pass-through SQL: cursor not found Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor. Action: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call. ORA-28551: pass-through SQL: SQL parse error Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement. Action: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system. ORA-28552: pass-through SQL: call flow error Cause: A pass-through SQL function was called in an invalid order. Action: Correct program flow by changing the order of API calls to match the flow described in the manual. ORA-28553: pass-through SQL: invalid bind-variable position Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text. Action: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system. ORA-28554: pass-through SQL: out of cursors Cause: The maximum number of open cursors has been exceeded. Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function. ORA-28555: pass-through SQL: required parameter missing or NULL Cause: An attempt was made to pass a NULL value to a non-NULL parameter. Action: Use a non-NULL value for the parameter. ORA-28556: authorization insufficient to access table Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns. Action: Contact the DBA for the non-Oracle system. The DBA can grant permission to access the privileged table or columns. ORA-28557: unknown string for database link to non-Oracle system Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. ORACLE requires these names to configure the heterogeneous database link. Action: Contact the DBA to check setup of the connection and the Heterogeneous Services agent. ORA-28558: HS_FDS_CONNECT_STRING undefined for non-Oracle system Cause: A database link to a non-Oracle system had no HS_FDS_CONNECT_STRING initialization parameter in the ORACLE server"s data dictionary for Heterogeneous Services. Without this parameter, the connection could not be completed. Action: Contact your DBA to verify correct setup of an HS_FDS_CONNECT_STRING entry in the ORACLE Heterogeneous Services data dictionary. ORA-28559: FDS_CLASS_NAME is string, FDS_INST_NAME is string Cause: An associated error was reported in another message, and this message supplies supplementary information to assist diagnosis of that error. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the ORACLE data dictionary that direct operation of Heterogeneous Services on a database link to a non-Oracle data store. Action: Use the FDS_CLASS_NAME and FDS_INST_NAME values to check ORACLE data dictionary contents when necessary to diagnose the cause of the associated error. ORA-28560: error in configuration of agent process Cause: An ORACLE server invoked a function not supported by the connected agent (Heterogeneous Services or external procedures). The most probable cause is incorrect Net8 setup, resulting in use of the wrong agent executable. Action: Check Net8 administration in the following ways: -- When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct SID. -- Check LISTENER.ORA on the agent"s host machine to assure that this SID refers to the correct agent executable in its (PROGRAM=...) clause. ORA-28561: unable to set date format on non-Oracle system Cause: Initialization of a Heterogeneous Services connection to set the date format to be used on the connected non-Oracle system. Action: If the Oracle data dictionary supplies a value for the HS_NLS_DATE_FORMAT parameter, confirm that this value is formatted correctly by the rules of the non-Oracle system. Also check for additional information in log and trace files generated by the Heterogeneous Services agent. ORA-28575: unable to open RPC connection to external procedure agent Cause: Initialization of a network connection to the extproc agent did not succeed. This problem can be caused by network problems, incorrect listener configuration, or incorrect transfer code. Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA, or check Oracle Names Server. ORA-28576: lost RPC connection to external procedure agent Cause: of this error is abnormal termination of the invoked "C" routine. If this is not the case, check for network problems. Correct the problem if you find it. If all components appear to be normal but the problem persists, the problem could be an internal logic error in the RPC transfer code. Contact your customer support representative. Action: First check the 3GL code you are invoking; the most likely ORA-28577: argument string of external procedure string has unsupported datatype string Cause: While transferring external procedure arguments to the agent, an unsupported datatype was detected. Action: Check your documentation for the supported datatypes of external procedure arguments. ORA-28578: protocol error during callback from an external procedure Cause: An internal protocol error occurred while trying to execute a callback to the Oracle server from the user"s 3GL routine. Action: Contact Oracle customer support. ORA-28579: network error during callback from external procedure agent Cause: An internal network error occurred while trying to execute a callback to the Oracle server from the user"s 3GL routine. Action: Contact Oracle customer support. ORA-28580: recursive external procedures are not supported Cause: A callback from within a user"s 3GL routine resulted in the invocation of another external procedure. Action: Make sure that the SQL code executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, such as triggers calling external procedures, PL/SQL procedures calling external procedures, etc. ORA-28581: protocol error while executing recursive external procedure Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure. Action: Contact Oracle customer support. ORA-28582: a direct connection to this agent is not allowed Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example: "SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIAS". This type of connection is not allowed. Action: When executing the CONNECT statement, make sure your database link or network alias is not pointing to a Heterogeneous Option agent or an external procedure agent. ORA-28583: remote references are not permitted during agent callbacks Cause: A Heterogeous Services agent issued a callback to the Oracle server which attemted to to access a remote system. This is not supported. Action: Make sure that SQL code issued by Heterogeneous Services agents does not reference a database link. ORA-28584: heterogeneous apply internal error Cause: The apply slave process encountered an error while trying to apply changes through a gateway to a non-Oracle system. Action: Make sure that the apply database link is correctly configured and that the gateway listener and the non-Oracle system are correctly set up and are up and running. If everything is configured correctly and the problem still occurs, contact Oracle customer support. errors 28590 - 28599 are reserved for the HS agent control utility ORA-28590: agent control utility: illegal or badly formed command Cause: The user has issued an unrecognized or syntactically incorrect command. Action: Refer to documentation and correct the syntax of the command. ORA-28591: agent control utility: unable to access parameter file Cause: The agent control utility was unable to access its parameter file. This could be because it could not find its admin directory or because permissions on directory were not correctly set. Action: The agent control utility puts its parameter file in either the directory pointed to by the environment variable AGTCTL_ADMIN or in the directory pointed to by the environment variable TNS_ADMIN. Make sure that at least one of these environment variables is set and that it points to a directory that the agent has access to. ORA-28592: agent control utility: agent SID not set Cause: The agent needs to know the value of the AGENT_SID parameter before it can process any commands. If it does not have a value for AGENT_SID then all commands will fail. Action: Issue the command SET AGENT_SID and then retry the command that failed. ORA-28593: agent control utility: command terminated with error Cause: An error occurred during the processing of the command. There could be several causes. A SET or an UNSET command could have been issued after the agent was started. This is illegal. The user may have attempted to start two agents with the same SID value or the user could have attempted to shutdown an agent that is no longer running. Action: If the user wishes to issue a SET or an UNSET command, he should make sure the agent is shutdown first by issuing the SHUTDOWN command. ORA-28594: agent control utility: invalid parameter name Cause: The user tried to set or unset an invalid agent parameter. Action: Refer to documentation and correct the parameter name. ORA-28595: Extproc agent : Invalid DLL Path Cause: The path of DLL supplied for the extproc execution is invalid. Action: Check if the DLL path is set properly using the EXTPROC_DLLS environment variable. errors 28600 - 28620 are reserved for bitmap indexes ORA-28601: invalid [no]MINIMIZE option Cause: user didn"t type this alter table MINIMIZE RECORDS_PER_BLOCK or alter table NOMINIMIZE RECORDS_PER_BLOCK Action: reenter correct sql command ORA-28602: statement not permitted on tables containing bitmap indexes Cause: table has bitmap indexes and user is minimizing or nominimizing records_per_block Action: drop all bitmap indexes before changing records_per_block ORA-28603: statement not permitted on empty tables Cause: table is empty and statement does not work on empty tables Action: try statement after loading your data ORA-28604: table too fragmented to build bitmap index (string,string,string) Cause: The table has one or more blocks that exceed the maximum number of rows expected when creating a bitmap index. This is probably due to deleted rows. The values in the message are: (data block address, slot number found, maximum slot allowed) Action: Defragment the table or block(s). Use the values in the message to determine the FIRST block affected. (There may be others). ORA-28605: bitmap indexes cannot be reversed Cause: user tried to create reverse bitmap index Action: don"t do this; it is not supported ORA-28606: block too fragmented to build bitmap index (string,string) Cause: The block(s) exceed the maximum number of rows expected when creating a bitmap index. This is probably due to maximum slot allowed set too low. The values in the message are: (slot number found, maximum slot allowed) Action: alter system flush shared_pool; update tab$ set spare1 = 8192 where obj# = (select obj# from obj$ where NAME= AND owner# = ; commit; ORA-28611: bitmap index is corrupted - see trace file for diagnostics Cause: Validate Index detected bitmap corruption in its argument index Action: Drop this bitmap index and create a new one. ORA-28650: Primary index on an IOT cannot be rebuilt Cause: An attempt is made to issue alter index rebuild on IOT-TOP Action: Use Alter table MOVE to reorganize the table(IOT) ORA-28651: Primary index on IOTs can not be marked unusable Cause: An attempt is made to mark IOT-TOP unusable thru ALTER INDEX Action: Remove the option UNUSABLE ORA-28652: overflow segment attributes cannot be specified Cause: During ALTER MOVE ONLINE of a index-organized table, the user attempted to enter one or more of the following options: OVERFLOW, PCTTHRESHOLD,INCLUDING. Action: Remove the illegal option(s). ORA-28653: tables must both be index-organized Cause: Attempt to exchange a non IOT table/partition with a partition/table respectively Action: Ensure that non-partitioned and partitioned tables are both index-organized. ORA-28654: table and partition not overflow compatible Cause: If one of the tables (partitioned/non-partitioned) has overflow data segment and the other one doesn"t. Action: Ensure that non-partitioned and partitioned tables both have overflow data segment or neither one does. ORA-28655: Alter table add overflow syntax error Cause: Syntax error Action: Check the syntax. ORA-28656: incomplete attribute specification Cause: The attribute specification is not done for all partitions" Action: Specify the storage attributes either for ALL partitions or NONE NLS_DO_NOT_TRANSLATE [28657,28657] ORA-28658: This operation is supported only for Index-Organized tables Cause: Attempt to perform some IOT specific operation on a non-IOT Action: don"t do this. This is not supported ORA-28659: COMPRESS must be specified at object level first Cause: Attempt to specify COMPRESS at partition level without first specifying at the table level Action: Specify COMPRESS at table level. Use ALTER TABLE xxx MODIFY DEFAULT ATTRIBUTES COMPRESS ... ORA-28660: Partitioned Index-Organized table may not be MOVEd as a whole Cause: Attempt to MOVE partitioned IOT as a whole Action: don"t do this. This is not supported ORA-28661: Object already has COMPRESS clause specified Cause: Attempt to specify compress for iot/index which already has a compression clause. Action: This is a "create time only" attribute ORA-28662: IOT index and overflow segments must share the same LOGGING attribute Cause: Attempt to specify LOGGING for one segment and NOLOGGING for the other segment. Action: don"t do that ORA-28663: Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW Cause: Attempt to specify LOGGING for a Alter Table Add Overflow. Action: don"t do that ORA-28664: a partitioned table may not be coalesced as a whole Cause: User attempted to coalesce a partitioned IOT using ALTER TABLE COALESCE statement, which is illegal Action: Coalesce the table a partition at a time (using ALTER TABLE MODIFY PARTITION COALESCE) ORA-28665: table and partition must have same compression attribute Cause: User attempted to EXCHANGE a compression enabled partition with a compression disabled table or vice versa OR the # of columns compressed is different for table and partition Action: Make sure the compression attributes match If they don"t, fix it using ALTER TABLE MOVE [PARTITION] COMPRESS ORA-28666: option not allowed for an index on UROWID column(s) Cause: User attempted to build a REVERSE or COMPRESSED or GLOBAL partitioned index on UROWID column(s) Action: Build the index without these options ORA-28667: USING INDEX option not allowed for the primary key of an IOT Cause: User attempted to define storage attributes for the primary key index of an Index-Organized table with USING INDEX clause. All the storage attribute defined for the (IOT)table applies to the primary key index and a separate USING INDEX clause is not required. Action: Remove the USING INDEX clause and specify all attributes directly for the table ORA-28668: cannot reference mapping table of an index-organized table Cause: An attempt to directly access the mapping table of an index-organized table Action: Issue the statement against the parent index-organized table containing the specified mapping table. ORA-28669: bitmap index can not be created on an IOT with no mapping table Cause: User attempted to create a bitmap index on an index-organized table without a mapping table. Action: Enable bitmap indexes on the Index-organized table by creating a mapping table using "ALTER TABLE .. MOVE MAPPING TABLE". ORA-28670: mapping table cannot be dropped due to an existing bitmap index Cause: User attempted to drop the mapping table with NOMAPPING option when the IOT has one or more bitmap indexed. Action: Drop the bitmap index(es) before dropping the mapping table. ORA-28671: UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole Cause: User attempted to UPDATE BLOCK REFERENCES on a partitioned index using ALTER INDEX UPDATE BLOCK REFERENCES statement, which is illegal. Action: Issue a partition level operation with ALTER INDEX .. PARTITION .. UPDATE BLOCK REFERENCES ORA-28672: UPDATE BLOCK REFERENCES may not be used on a global index Cause: User attempted to UPDATE BLOCK REFERENCES on a global partitioned or non-partitioned index. This feature is not supported for non-partitioned or global partitioned index on a partitioned IOT and a global partitioned index on a non-partitioned IOT. Action: Use online index [partition] rebuild to fix the block references ORA-28673: Merge operation not allowed on an index-organized table Cause: User attempted merge operation on an index-organized table. Merge is not supported on a IOT . Action: Use updates and inserts on index-organized table . ORA-28674: cannot reference transient index-organized table Cause: An attempt was made to directly access a transient table created created on behalf of a index-organized table partition maintenance operation. Action: Issue the statement against the associated permanent index-organized table. Skip Headers Oracle® Database Error Messages 10g Release 2 (10.2) Part Number B14219-01 Home Book List Contents Index Master Index Contact Us -------------------------------------------------------------------------------- Previous Next View PDF 16 ORA-29250 to ORA-32775ORA-29250: Invalid index specifed in call to dbms_sql.bind_array Cause: An invalid index was specified in a call to bind_array of dbms_sql. The index may have been null or of an improper value. Action: Correct the index value by modifying your PL/SQL program and try the bind_array call again. ORA-29251: Index1 is greater than Index2 in call to dbms_sql.bind_array Cause: The value of index1 was greater than the value for index2 in the call to bind_array. This is illegal since the elements of the table that will be bound are those with indexes greater than or equal to index1 and less than or equal to index2. Action: Correct the value of the two indexes and try the call to again bind_array. ORA-29252: collection does not contain elements at index locations in call to dbms_sql.bind_array Cause: The bound table does not contain elements at both index locations in call to bind_array of dbms_sql. This is illegal. Both index locations must contain elements. In other words tab.exists(index1) and tab.exists(index2) must both return true. Action: Either modify the two indexes or the contents of the table and try the call again. ORA-29253: Invalid count argument passed to procedure dbms_sql.define_array Cause: The count argument specified in the call to procedure define_array of package dbms_sql had an invalid value. Invalid values are negative numbers and nulls. The argument must be a positive integer. Action: Correct your PL/SQL program so that only valid arguments are passed to define_array and try again. ORA-29254: Invalid lower_bound argument passed to procedure dbms_sql.define_array Cause: The lower_bound argument specified in the call to procedure define_array had an invalid value. Legal values are all integers (both positive and negative) including zero. The null value is illegal. Action: Correct your PL/SQL program so that only valid arguments are passed to define_array and try again. ORA-29255: Cursor contains both bind and define arrays which is not permissible Cause: Both define_array and bind_array have been called on this cursor. This is illegal. It is not possible for a cursor to both contain array binds and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and array binds to bind PL/SQL tables to non-select queries. Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the kind of cursor at hand. ORA-29256: Cursor contains both regular and array defines which is illegal Cause: Both define_array and define_column have been called on this cursor. This is illegal. It is not possible for a cursor to both contain regular and array defines. The semantics of this setting are nonsensical. Array defines are used to move data from select queries into PL/SQL tables and regular defines to move data from select queries into PL/SQL variables. Action: Modify your PL/SQL program to only perform calls to one of the two functions depending on the situation at hand. ORA-29257: host string unknown Cause: The specified host was unknown. Action: Check the spelling of the host name or the IP address. Make sure that the host name or the IP address is valid. ORA-29258: buffer too small Cause: The input or output buffer was too small for the operation. Action: Increase the size of the buffer and retry the operation. ORA-29259: end-of-input reached Cause: The end of the input was reached. Action: If the end of the input is reached prematurely, check if the input source terminates prematurely. Otherwise, close the connection to the input. ORA-29260: network error: string Cause: A network error occurred. Action: Fix the network error and retry the operation. ORA-29261: bad argument Cause: A bad argument was passed to the PL/SQL API. Action: Check the arguments passed to the PL/SQL API and retry the call. ORA-29262: bad URL Cause: An improperly formed URL was passed to the PL/SQL API. Action: Check the URL and retry the call. ORA-29263: HTTP protocol error Cause: A HTTP protocol error occured during the HTTP operation. Action: Check the HTTP server that the HTTP operation was performed to make sure that it follows the HTTP protocol standard. ORA-29264: unknown or unsupported URL scheme Cause: The URL scheme was unknown or unsupported. Action: Check the URL to make sure that the scheme is valid and supported. ORA-29265: HTTP header not found Cause: The requested HTTP header was not found. Action: Check to make sure that the requested HTTP header is present. ORA-29266: end-of-body reached Cause: The end of the HTTP response body was reached. Action: If the end of the HTTP response is reached prematurely, check if the HTTP response terminates prematurely. Otherwise, end the HTTP response. ORA-29267: illegal call Cause: The call to the PL/SQL API was illegal at the current stage of the operation. Action: Retry the call at a different stage of the operation. ORA-29268: HTTP client error string Cause: The HTTP response indicated that the HTTP client error occurred. Action: Fix the HTTP client error and retry the HTTP request. ORA-29269: HTTP server error string Cause: The HTTP response indicated that the HTTP server error occurred. Action: Fix the HTTP server error and retry the HTTP request. Contact the admistrator of the HTTP server when necessary. ORA-29270: too many open HTTP requests Cause: Too many HTTP requests were opened. Action: End some HTTP requests and retry the HTTP request. ORA-29271: not connected Cause: The network connection was not made while the network operation was attempted. Action: Retry the network operation after the network connection is made successfully. ORA-29272: initialization failed Cause: The UTL_HTTP package failed to initialize. Action: Free up some memory or other system resources and retry the operation. ORA-29273: HTTP request failed Cause: The UTL_HTTP package failed to execute the HTTP request. Action: Use get_detailed_sqlerrm to check the detailed error message. Fix the error and retry the HTTP request. ORA-29274: fixed-width multibyte character set not allowed for a URL Cause: The character set used as an encoding of the URL is a fixed-width multibyte character set and is not allowed for a URL. Action: Use the corresponding variable-width multibyte character set for the URL instead. ORA-29275: partial multibyte character Cause: The requested read operation could not complete because a partial multibyte character was found at the end of the input. Action: Ensure that the complete multibyte character is sent from the remote server and retry the operation. Or read the partial multibyte character as RAW. ORA-29276: transfer timeout Cause: Timeout occurred while reading from or writing to a network connection. Action: Check the remote server or the network to ensure that it responds within the timeout limit. Or increase the timeout value. ORA-29277: invalid SMTP operation Cause: The SMTP operation was invalid at the current stage of the SMTP transaction. Action: Retry the SMTP operation at the appropriate stage of the SMTP transaction. ORA-29278: SMTP transient error: string Cause: A SMTP transient error occurred. Action: Correct the error and retry the SMTP operation. ORA-29279: SMTP permanent error: string Cause: A SMTP permanent error occurred. Action: Correct the error and retry the SMTP operation. ORA-29280: invalid directory path Cause: A corresponding directory object does not exist. Action: Correct the directory object parameter, or create a corresponding directory object with the CREATE DIRECTORY command. ORA-29281: invalid mode Cause: An invalid value was specified for file open mode. Action: Correct the mode to be one of the values: "r","a", or "w". ORA-29282: invalid file ID Cause: A file ID handle was specified for which no corresponding open file exists. Action: Verify that the file ID handle is a value returned from a call to UTL_FILE.FOPEN. ORA-29283: invalid file operation Cause: An attempt was made to read from a file or directory that does not exist, or file or directory access was denied by the operating system. Action: Verify file and directory access privileges on the file system, and if reading, verify that the file exists. ORA-29284: file read error Cause: An attempt to read from a file failed. Action: Verify that the file exists, and that it is accessible, and that it is open in read mode. ORA-29285: file write error Cause: Failed to write to, flush, or close a file. Action: Verify that the file exists, that it is accessible, and that it is open in write or append mode. ORA-29286: internal error Cause: A fatal error occurred while allocating PL/SQL session memory. Action: Verify that the PL/SQL session is connected and that adequate memory resources are available. ORA-29287: invalid maximum line size Cause: An invalid maximum line size value was specified. Action: Correct the maximum line size to be in the range [1, 32767]. ORA-29288: invalid file name Cause: A NULL or zero length file name was specified. Action: Correct the file name to be a nonzero length string. ORA-29289: directory access denied Cause: A directory object was specified for which no access is granted. Action: Grant access to the directory object using the command GRANT READ ON DIRECTORY [object] TO [username];. ORA-29290: invalid offset specified for seek Cause: An attempt was made to seek past the end of the file, or both the absolute and relative offsets were NULL, or absolute offset was less than zero. Action: If specifying an absolute offset, ensure it is in the range [0, ], or if specifying a relative offset, ensure it is no greater than the current byte position plus the number of bytes remaining in the file. ORA-29291: file remove operation failed Cause: A file deletion attempt was refused by the operating system. Action: Verify that the file exists and delete privileges granted on the directory and the file. ORA-29292: file rename operation failed Cause: A file rename attempt was refused by the operating system either because the source or destination directory does not exist or is inaccessible, or the source file isn"t accessible, or the destination file exists. Action: Verify that the source file, source directory, and destination directory exist and are accessible, and that the destination file does not already exist. ORA-29293: A stream error occurred during compression or uncompression. Cause: The stream state was discovered to be invalid during compression or uncompression, or an invalid compression quality was requested or a NULL or invalid compression parameter was detected. Action: Verify that quality is within the range [0,9] and that valid input source data exists. ORA-29294: A data error occurred during compression or uncompression. Cause: An error occurred while compressing or uncompressing input source. Action: Verify that source data is a valid compressed or uncompressed data set. ORA-29295: invalid mime header tag Cause: An error occurred while scanning string for mime header tag Action: Verify that source data is a valid mime header string, in the format: =????= ORA-29296: invalid encoded string Cause: An error occurred while decoding the input string Action: Verify that source data is a valid encoded string. ORA-29297: The compressed representation is too big Cause: The compressed output is too big to return. Action: Do not attempt to compress source data. ORA-29298: Character set mismatch Cause: The character set mode in which the file was opened did not match the character set of the read or write operation. Action: Use the correct UTL_FILE read and write procedures which coorespond to the character set mode in which the file was opened. ORA-29299: Invalid handle for piecewise compress or uncompress Cause: The process program opened too many handles, and the specified handle was either uninitialized or outside a valid range. Action: Close some handles and verify that the specified handle is opened or within a valid range. ORA-29300: ORACLE error, tablespace point-in-time recovery Cause: Another ORACLE error occured in the DBMS_PITR package. Action: See the text of the error message for a description of the error. ORA-29301: wrong DBMS_PITR package function/procedure order Cause: The DBMS_PITR package function/procedure was called in an incorrect order. Action: Restart tablespace point-in-time recovery with a correct procedure. ORA-29302: database is not open clone Cause: The database was not opened as a clone database. Action: Mount the database clone and open the database. ORA-29303: user does not login as SYS Cause: The user did not log in as SYS to perform tablespace point-in-time recovery in a clone database. Action: Log in as SYS and restart tablespace point-in-time recovery. ORA-29304: tablespace "string" does not exist Cause: The selected tablespace does not exist in the database. Action: Check the list of tablespaces in V$TABLESPACE and select a valid tablespace. ORA-29305: cannot point-in-time recover tablespace "string" Cause: An attempt was made to ALTER the tablespace to be read only. Action: Check if the tablespace is SYSTEM or with online rollback segment. ORA-29306: datafile string is not online Cause: The selected datafile was not online. Action: Bring the the datafile online and rename it if necessary. ORA-29307: datafile string error, string Cause: The datafile is not ready for tablespace point-in-time recovery. Action: Check the correct tablespace point-in-time recovery procedure. ORA-29308: view TS_PITR_CHECK failure Cause: Some objects which crossed the boundary of the recovery set were not allowed in the tabelspace point-in-time recovery. Action: Query TS_PITR_CHECK and resolve the boundary crossing objects. ORA-29309: export dump file was generated by different version of DBMS_PITR package Cause: The version of DBMS_PITR is different from the version of the cloned database. Action: Load the version of DBMS_PITR which matches the version of the cloned database. ORA-29310: database is not open, or opened as a clone Cause: Either the database was not open, or an attempt was made to open it as a cloned database. Action: Open the production database instead. ORA-29311: export dump file was not generated by this database, string does not match Cause: The export dump files were imported to an incorrect database. Action: Open the correct production database and try the import again. ORA-29312: changes by release string cannot be used by release string, type: string Cause: A point-in-time tablespace was chosen to perform the recovery, but the current database is not compatible with the database that was used to create the point-in-time tablespace. Action: Choose a point-in-time and retry the operation. ORA-29313: tablespace "string" cannot be imported twice Cause: This is an internal error. Action: Contact your database administrator. ORA-29314: tablespace "string" is not OFFLINE FOR RECOVER nor READ ONLY Cause: Tablespace clean SCN is either 0 or invalid. Action: ALTER the tablespace OFFLINE FOR RECOVER. ORA-29315: tablespace "string" has been recreated Cause: An attempt was made to recover a tablespace to a point-in-time before it was recreated. Action: Choose a different point in time for recovery. ORA-29316: datafile string been imported twice Cause: This is an internal error. Action: Contact your database administrator. ORA-29317: datafile string does not exist Cause: The specified datafile could not be found in the production database. Action: Copy the datafile from the clone database. ORA-29318: datafile string is online Cause: The datafile is online. Action: Take the datafile offline. ORA-29319: datafile string is not correct Cause: An incorrect datafile was copied to the production database. The datafile information in the export dump file differs with the information in the datafile in the production database. Action: Copy the datafile from the clone database to the production database. ORA-29320: datafile header error Cause: An error occured during reading datafile header. Action: Copy the correct datafile from the clone database to the production database, then retry the operation. ORA-29321: too many datafiles added since the point-in-time Cause: Too many datafiles were added to the recovery set since the point-in-time recovery. Action: Divide the recovery set into smaller subsets and retry. ORA-29322: SCN string size too long -- maximum size 58 bytes/characters Cause: Too many characters in specifying the SCN string Action: Remove all unnecessary characters. Only 15 characters are required for both the hex and decimal representation of the 48 bit SCN. ORA-29323: ALTER DATABASE SET COMPATIBILITY command not supported by string Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances do not support dynamic compatible setting change. Action: No action required. ORA-29324: SET COMPATIBILITY release string format is wrong Cause: It should be of the form x.x.x Action: Use the correct format. ORA-29325: SET COMPATIBILITY release number lower than string Cause: The SET COMPATIBILITY release compatibility release number was lower than the current compatible setting. Action: Specify a higher release number. ORA-29326: SET COMPATIBILITY release number higher than string Cause: The ALTER DATABASE SET COMPATIBILITY command failed because one or more instances had a lower release number. Action: Specify a lower release number. ORA-29327: unsupported client compatibility mode used when talking to the server Cause: The client compatibility mode is higher than the version of the server. Action: Using SET COMPATIBILITY command, specify the same release number as the server. ORA-29328: too many datafiles in this tablespace "string" Cause: Too many datafiles in this bitmap tablespace. ORACLE does not support at this moment. Action: Call Oracle Support. ORA-29329: Table not of type XMLType Cause: Table is not XMLType table Action: Ensure table is a XMLType table ORA-29330: Source script length too big Cause: Source script length exceeded the maximum size of 4 Gigabytes. Action: Make sure source script length is not greater than 4 Gigabytes. ORA-29335: tablespace "string" is not read only Cause: The tablespace is not read only. Action: Make the tablespace read only and retry the operation. ORA-29336: Internal error [string] [string] from DBMS_PLUGTS Cause: Internal error from package DBMS_PLUGTS. Action: Call Oracle Support. ORA-29337: tablespace "string" has a non-standard block size (string) Cause: The tablespace has a non-standard block size and making such a tablespace read-write is not permitted. Action: Use some other mechanism to import the data ORA-29338: datafile string is in an undesired state (string, string) Cause: The referred datafile is not in a state ready for tablespace copy operation. For example, the datafile may be offline. The datafile needs to be ONLINE, and either READ ONLY or READ WRITE. Action: Put the datafile into the desired state. ORA-29339: tablespace block size string does not match configured block sizes Cause: The block size of the tablespace to be plugged in or created does not match the block sizes configured in the database. Action: Configure the appropriate cache for the block size of this tablespace 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-29340: export file appears to be corrupted: [string] [string] [string] Cause: This is caused either by a corrupted export file or by an Oracle internal error. Action: Make sure the export file used for transportable tablespace is not corrupted. If the error still occurs, call Oracle support. ORA-29341: The transportable set is not self-contained Cause: The set of objects in the set of tablespaces selected are not self-contained. Action: Consider using different export options, or removing some of the pointers that caused the violation, or selecting a different set of tablespaces. ORA-29342: user string does not exist in the database Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database. Action: Consider either creating the user in the database or map the user to a different user via FROM_USER and TO_USER import options. ORA-29343: user string (mapped from user string) does not exist in the database Cause: The referred user is one of the owners of data in the pluggable set. This user does not exist in the database. Action: Consider either creating the user or map the original user to a different user. ORA-29344: Owner validation failed - failed to match owner "string" Cause: The system failed to match the referred owner. There are two cases that this may occur. (1) This user owns data in the transportable set, but this user is not specified in the TTS_OWNERS list of the import command line option, assuming that TTS_OWNERS is specified. (2) This user is specified in the TTS_OWNER list, but this user does not own any data in the transportable set. Action: Retry import with a different OWNER list. ORA-29345: cannot plug a tablespace into a database using an incompatible character set Cause: Oracle does not support plugging a tablespace into a database using an incompatible character set. Action: Use import/export or unload/load to move data instead. ORA-29346: invalid tablespace list Cause: the tablespace list supplied to dbms_tts.transport_set_check PL/SQL routine is in an incorrect format. Action: Check the manual and use the correct format. ORA-29347: Tablespace name validation failed - failed to match tablespace "string" Cause: The system failed to match the referred tablespace. There are 2 cases that this may happen. (1) This tablespace is in the transportable set, but it is not specified in the TABLESPACES list of the import command line option, assuming that TABLESPACES is specified. (2) This tablespace is in the TABLESPACES list, but it is not in the transportable set. Action: Retry the operation with the correct TABLESPACES list. ORA-29348: You must specify the datafiles to be plugged in Cause: The datafiles to be plugged in are not specified. Action: Specify the datafiles via the import DATAFILES command line option. ORA-29349: tablespace "string" already exists Cause: Tried to plug-in a tablespace which already exists. Action: Drop the offending tablespace if possible. Otherwise use a different method (e.g., import/export) to move data. ORA-29351: can not transport system, sysaux, or temporary tablespace "string" Cause: The referred tablespace is either the system tablespace, the sysaux tablespace, or a temporary tablespace. Action: Do not include this tablespace in the transportable set. ORA-29352: event "string" is not an internal event Cause: The DBMS_SYSTEM.WAIT_FOR_EVENT procedure was called with an event name that is not an internal event. Action: Check the list of events from X$KSLED and verify the event name parameter passed to the WAIT_FOR_EVENT procedure. ORA-29353: The transportable list is too long. Cause: The transportable list exceeds the buffer size of 32767. Action: Reduce the list of tablespaces to transport. ORA-29355: NULL or invalid string argument specified Cause: The named argument was either invalid or specified as a NULL Action: Specify non-null, valid arguments. ORA-29356: These parameters can be specified only for directives that refer to consumer groups Cause: The below parameters were specified as an argument to procedure CREATE_PLAN_DIRECTIVE or UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER.where the GROUP_OR_SUBPLAN argument is a resource plan. "ACTIVE_SESS_POOL_P1", "QUEUEING_P1", "PARALLEL_DEGREE_LIMIT_P1", "SWITCH_P1", "SWITCH_P2", "SWITCH_P3", "MAX_EST_EXEC_TIME", "UNDO_POOL" Action: Specify these parameters only for consumer group directives. ORA-29357: object string already exists Cause: The name specified as argument to procedure CREATE_PLAN, CREATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER was already in use. Action: Specify an unused name. ORA-29358: resource plan string does not exist Cause: An invalid plan name was specified as an argument to procedure UPDATE_PLAN of package DBMS_RESOURCE_MANAGER. Action: Specify an existing plan name. ORA-29359: invalid method name string specified for resource plan string Cause: An invalid method was specified as an argument to procedure CREATE_PLAN or UPDATE_PLAN of package DBMS_RESOURCE_MANAGER. Action: Specify a valid method name. ORA-29360: retry operation. Too much concurrent activity Cause: An attempt was made to revoke the switch consumer group privilege from a user for his/her initial consumer group but someone is modifying the user in another session. Action: Retry the operation later. ORA-29361: value string is outside valid range of 0 to 100 Cause: An invalid value was specified for a plan directive parameter. Action: Specify a value between 0 and 100 inclusive. ORA-29362: plan directive string, string does not exist Cause: A non-existent plan directive was specified for procedure UPDATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. Action: Specify an existing plan directive for update. ORA-29363: plan directive string, string is mandatory and cannot be modified or deleted Cause: An attempt was made to modify a mandatory plan directive. Action: Do not attempt to modify mandatory plan directives because they are required by the Resource Manager and cannot be modified. ORA-29364: plan directive string, string already exists Cause: An attempt was made to create a plan directive that already exists. Action: Retry the create operation using different values. ORA-29365: parameters string and string cannot both be set Cause: An attempt was made to set both parameters. Action: Only set one of parameters or neither of them. ORA-29366: invalid CONSUMER_GROUP argument specified Cause: An invalid consumer group name was specified. Action: Specify a non-NULL, valid consumer group name. ORA-29367: object string does not exist Cause: A non-existent object name was specified as an argument to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER. Action: Specify a valid plan or consumer group name. ORA-29368: consumer group string does not exist Cause: An non-existent consumer group was specified. Action: Specify an existing consumer group. ORA-29369: invalid method name string specified for consumer group string Cause: An invalid method name was specified as an argument to procedure CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER. Action: Specify a valid method name. ORA-29370: pending area is already active Cause: An attempt was made to activate a pending area that is already active. Action: Wait until the pending area is no longer active; then, retry the operation. ORA-29371: pending area is not active Cause: An attempt was made to make changes without creating a pending area. Action: Invoke procedure CREATE_PENDING_AREA before making any changes. ORA-29372: identifier string is too long; it must be less than string characters Cause: An attempt was made to specify an identifier that is more than 30 characters long. Action: Use an identifier that is 30 characters or less in length. ORA-29373: resource manager is not on Cause: An attempt was made to execute an operation that cannot be executed with the resource manager being off Action: Turn on the resource manager and try again. ORA-29374: resource plan string in top-plan string has no plan directives Cause: A plan was created in the pending area that is an orphan or stand-alone. Action: Create plan directives if needed. Otherwise, delete the plan. ORA-29375: sum of values string for level string, plan string exceeds string Cause: The sum of plan directive parameter values for the specified plan level exceeded 100. Action: Alter the values for the level so that they sum to 100. ORA-29376: number of consumer groups string in top-plan string exceeds string Cause: The number of consumer groups in the specified top-plan is more than 32. Action: Change the top-plan to have no more than 32 consumer groups. ORA-29377: consumer group string is not part of top-plan string Cause: OTHER_GROUPS was not included as part of the specified top-plan. Each top plan must include the built-in consumer group OTHER_GROUPS. Action: Create a plan directive with the argument GROUP_OR_SUBPLAN being OTHER_GROUPS somewhere in the top-plan. ORA-29378: invalid consumer group mapping priorities Cause: The mapping priorities were not unique integers within the valid range. Action: Set the mapping priorities to unique integers within the documented range. ORA-29379: resource plan string is involved in a loop in top-plan string Cause: A loop was discovered while validating a top-plan. Action: Check the plans that have the specified plan as a GROUP_OR_SUBPLAN, and remove the plan directive that causes the loop. ORA-29380: resource plan string is currently active and cannot be deleted Cause: An attempt was made to delete an active plan in the pending area. No changes can be made to active plans. Action: Delete the plan when it is not in use. ORA-29381: plan/consumer_group string referred to by another plan and cannot be deleted Cause: An attempt was made to delete a plan or consumer group that is referred to by another plan. Action: Remove all plan directives that have the plan or consumer group as GROUP_OR_SUBPLAN; then delete the plan or consumer group. ORA-29382: validation of pending area failed Cause: Invalid changes were attempted in the pending area. Action: See documentation and the error messages that follow this one. ORA-29383: all leaves of top-plan string must be consumer groups Cause: An attempt was made to create or modify the specified top-plan but it has some plans as leaves. Action: To identify which plans and/or plan directives need to be modified, look at all plans that have no plan directives. Then, alter the top-plan so that all its leaves are consumer groups. ORA-29384: number of children for plan string exceeds string Cause: An attempt was made to create or modify the specified plan, but the plan has more than 32 children. Action: Make sure the specified plan points to no more than 32 distinct nodes. ORA-29385: cannot create plan directive from string to string Cause: An attempt was made to create a plan directive from a plan to itself. Action: Make sure the arguments PLAN and GROUP_OR_SUBPLAN to procedure CREATE_PLAN_DIRECTIVE of package DBMS_RESOURCE_MANAGER are different. ORA-29386: plan or consumer group string is mandatory and cannot be deleted or modified Cause: An attempt was made to delete or modify the specified mandatory plan or consumer group. Action: Do not attempt to delete or modify mandatory plans and consumer groups. ORA-29387: no top-plans found in the pending area Cause: The VALIDATE_PENDING_AREA procedure found that either the intended top-plan(s) are involved in a loop or there are no top-plans. Action: Check all edges going from a subplan to the intended top-plan. Make sure the top plan does not have any plan referring to it. ORA-29388: plan/consumer_group string is part of more than one top-plan Cause: An attempt was made to delete a subtree that includes a plan or consumer group that is part of more than one top-plan as part of procedure DELETE_PLAN_CASCADE or package DBMS_RESOURCE_MANAGER. Such a plan or consumer group cannot be deleted. Action: Check the ancestors of the plan or consumer group and make sure it is only part of the top-plan that includes the subtree being deleted. ORA-29389: too many errors during validation Cause: The number of errors detected during validation is too high. Action: Perform the necessary actions to remove some errors, and retry validation. ORA-29390: some resource plans are not part of any top-plan Cause: An attempt was made to create or modify some plans in the pending area that are not part of any top-plan Action: Remove these plans are try validation again. ORA-29391: %s and string must be mandatory to create a mandatory plan directive Cause: An attempt was made to create a mandatory plan directive where either PLAN or GROUP_OR_SUBPLAN or both were not mandatory Action: Recreate these objects as mandatory and then create the plan directive. ORA-29392: cpu parameters for level string for plan string must be zero Cause: The cpu parameters for the specified level had a non-zero value, which is not a valid value for the plan"s current cpu policy. Action: Change the cpu level parameters for the specified level to zero or change the plan cpu policy. ORA-29393: user string does not exist or is not logged on Cause: An invalid user name was specified as argument to procedure SET_INITIAL_CONSUMER_GROUP of package DBMS_RESOURCE_MANAGER or SWITCH_CONSUMER_GROUP_FOR_USER of package DBMS_SYSTEM or the specified user was not logged on. Action: Specify a valid user name. ORA-29394: session id string and serial# string do not exist Cause: Invalid session id and serial# were specified as arguments to procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package DBMS_SYSTEM. Action: Specify valid values from the view V$SESSION. ORA-29395: cannot set the initial consumer group to string Cause: An attempt was made to set the initial consumer group of a user to OTHER_GROUPS. Action: OTHER_GROUPS is for the resource manager"s internal use. Specify another consumer group. ORA-29396: cannot switch group to string Cause: An attempt was made to switch the consumer group of a user or a session to OTHER_GROUPS. Action: OTHER_GROUPS is for the resource manager"s internal use. Specify another consumer group. ORA-29397: cannot grant/revoke switch privilege for string Cause: An attempt was made to grant or revoke the privilege to switch to OTHER_GROUPS. Action: OTHER_GROUPS is for the resource manager"s internal use. Specify another consumer group. ORA-29398: invalid privilege name specified Cause: An invalid privilege name was specified as an argument to procedure GRANT_SYSTEM_PRIVILEGE or REVOKE_SYSTEM_PRIVILEGE of package DBMS_RESOURCE_MANAGER_PRIVS. Action: Specify a valid privilege name. ORA-29399: user string does not have privilege to switch to consumer group string Cause: An attempt was made to set the initial consumer group of the specified user but the user does not have the privilege to switch to that group. Action: Grant the privilege to switch to the consumer group to the user and then set the initial group. ORA-29400: data cartridge error string Cause: An error has occurred in a data cartridge external procedure. This message will be followed by a second message giving more details about the data cartridge error. Action: See the data cartridge documentation for an explanation of the second error message. ORA-29500: NAMED keyword is invalid in CREATE JAVA CLASS Cause: A NAMED keyword was specified in the CREATE JAVA CLASS statement. NAMED keywords are valid only in CREATE JAVA SOURCE or RESOURCE statements. Action: Remove the NAMED keyword from the CREATE JAVA CLASS statement. ORA-29501: invalid or missing Java source, class, or resource name Cause: The required name for a Java source, class, or resource was invalid or missing. Action: Specify a valid name. ORA-29502: NAMED keyword required in CREATE JAVA RESOURCE Cause: The name for a Java resource was not specified. The name must be specified with the NAMED keyword. Action: Specify a valid name with the NAMED keyword. ORA-29503: SCHEMA keyword not valid with NAMED keyword Cause: SCHEMA and NAMED keywords were used together in the same CREATE JAVA command, but only one may be used in a CREATE JAVA command. Action: Remove either the NAMED or the SCHEMA keyword. ORA-29504: invalid or missing schema name Cause: The required schema name was invalid or missing. Action: Specify a valid schema name. ORA-29505: AS keyword is invalid in CREATE JAVA CLASS or RESOURCE Cause: The AS keyword was used in CREATE JAVA CLASS or RESOURCE. The AS keyword is valid only in CREATE JAVA SOURCE. Action: Use the USING keyword in CREATE JAVA CLASS or RESOURCE. ORA-29506: invalid query derived from USING clause Cause: The USING clause did not form a valid query. Action: Correct the USING clause. ORA-29507: query derived from USING clause found zero or many rows Cause: The USING clause defined a query that either did not return any values, or returned more than one value. Action: Correct the USING clause. ORA-29508: query derived from USING clause did not select a value of type string Cause: The USING clause did not form a query that selects a value of the type specified by the term following the USING keyword. Action: Correct the USING clause. ORA-29509: incorrectly formed Java binary class definition Cause: An attempt was made to create a Java class using data expected to be in binary (Java .class) format. The data was found not to be in this format, or to be incorrectly formed. Action: Correct the definition data. ORA-29510: name, string.string, already used by an existing object Cause: A CREATE JAVA command attempted to create a source, class, or resource object with a name that is already in use. Action: Drop the existing object that is using the desired name, or use a different name for the new object. ORA-29511: could not resolve Java class Cause: A CREATE AND RESOLVE NOFORCE JAVA CLASS command specified definition data that could not be resolved, or resolution failed for some referenced class. Action: Remove the NOFORCE option or remove impediments to resolution. ORA-29512: incorrectly formed name resolver specification Cause: A name resolver was not specified in the required form: (( , ) ...) Action: Correct the specification. ORA-29513: referenced class name too long Cause: An attempt was made to import a .class file containing a class name of length greater than %d. The .class file could not be imported because the referenced class name was too long. Action: Shorten the referenced class name in the .class file. ORA-29514: class name contains illegal character Cause: An attempt was made to import a .class file containing a character that cannot be converted to the server character set. The .class file could not be imported because of the illegal character. Action: Correct the illegal character in the .class file. ORA-29515: exit called from Java code with status string Cause: Java code included a call to java.lang.Runtime.exitInternal. Action: Do not include this call unless non-local exit is desired. ORA-29516: Aurora assertion failure: string Cause: An internal error occurred in the Aurora module. Action: Contact Oracle Worldwide Support. ORA-29517: recursive resolution failed for a referenced class Cause: An attempt to resolve a referenced class failed. Action: Review the errors for referenced classes and complete the necessary actions to correct them. ORA-29518: name string resolved to an object in schema string that is not a Java class Cause: A referenced name was resolved to an object that is not a Java class. Action: Adjust name resolver or add missing Java class. ORA-29519: name string resolved via a synonym in schema string to a class with a different name Cause: A referenced name was resolved to a synonym, which translated to a class whose name does not match the referenced name. Action: Adjust name resolver or add missing Java class. ORA-29520: name string resolved to a class in schema string that could not be accessed Cause: An attempt to access a referenced class failed. Action: Adjust authorizations or name resolution. ORA-29521: referenced name string could not be found Cause: Name resolution failed to find an object with the indicated name. Action: Adjust name resolver or add missing Java class. ORA-29522: authorization error for referenced name string.string Cause: An attempt was made to resolve a class that is not authorized to use the indicated referenced class. Action: Adjust authorizations or name resolution. ORA-29523: authorization error for unknown referenced name Cause: An attempt was made to resolve a class that is not authorized to use a referenced class. The name of the referenced class could not be determined. Action: Adjust authorizations or name resolution. ORA-29524: wrong types of arguments in call to "string" Cause: A method was called with argument(s) of incompatible type(s). Action: Adjust caller. ORA-29525: referenced name is too long: "string" Cause: An attempt was made to create a class that references a name longer than 4000 characters. The class could not be created because the name is too long. Action: Adjust the definition. ORA-29526: created Java class string"string" Cause: An informational message, not an error. Action: None. ORA-29527: created Java source string"string" Cause: An informational message, not an error. Action: None. ORA-29528: invalid Java call in trigger string Cause: The Java method specified in trigger does not exist or cannot be called as used. Action: Adjust trigger definition. ORA-29529: invalid function or method call string in trigger string Cause: The function or method specified in Java trigger call expression could not be resolved. Action: Adjust trigger definition. ORA-29530: could not create shortened name for string Cause: Insert into shortened name translation table failed. Action: Retry the insert. ORA-29531: no method string in class string Cause: An attempt was made to execute a non-existent method in a Java class. Action: Adjust the call or create the specified method. ORA-29532: Java call terminated by uncaught Java exception: string Cause: A Java exception or error was signaled and could not be resolved by the Java code. Action: Modify Java code, if this behavior is not intended. ORA-29533: attempt to overwrite class or resource string while defining or compiling string.string Cause: A class or resource defined by a SQLJ source conflicted with an existing object. Action: Remove existing object, or modify SQLJ source. ORA-29534: referenced object string.string could not be resolved Cause: Name resolution determined that the indicated object is referenced but could not be resolved. Action: Correct name resolver or address resolution problems in the referenced class, or correct compilation problems in its source. ORA-29535: source requires recompilation Cause: The reason the current class object was invalid is recorded with the source object from which it was compiled. Action: Inspect errors in the source object and take the necessary corrective actions. ORA-29536: badly formed source: string Cause: An attempt was made to create a Java source object with text that could not be parsed adequately to determine the class(es) defined by it. Action: Correct errors in source. ORA-29537: class or resource cannot be created or dropped directly Cause: An attempt was made to create or drop a Java class or resource that is known to result from compilation of an existing Java source object. Action: Act on the class or resource by acting on the source, or change the source so that it no longer defines the class or resource. ORA-29538: Java not installed Cause: An attempt was made to use a Java command when Java is not installed. Action: Install Java, or do not use the command. ORA-29539: Java system classes already installed Cause: An attempt was made to use the CREATE JAVA SYSTEM command in a database where the Java system classes already are installed. Action: Use CREATE OR REPLACE JAVA SYSTEM. ORA-29540: class string does not exist Cause: Java method execution failed to find a class with the indicated name. Action: Correct the name or add the missing Java class. ORA-29541: class string.string could not be resolved Cause: An attempt was made to execute a method in a Java class that had not been previously and cannot now be compiled or resolved successfully. Action: Adjust the call or make the class resolvable. ORA-29542: class string already defined by source string Cause: An attempt was made to create a Java source object that would define a class that is already defined by a different Java source object. Action: Either drop the old source or modify the new source. ORA-29543: Java command string not yet implemented Cause: An attempt was made to use a Java command that is not yet implemented. Action: Do not use the command. ORA-29544: invalid type Cause: The type argument in a call to a Java export or import command did not have a recognized value. Action: Correct the value. ORA-29545: badly formed class: string Cause: An attempt was made to create a Java class object with bytecodes that were rejected by the Java verifier. Action: It is possible that an attempt was made to create the Java class from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using "-" in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver. ORA-29546: badly formed resource: string Cause: An attempt was made to create a Java resource object with data that was rejected by the Java verifier. Action: Correct the data. ORA-29547: Java system class not available: string Cause: An attempt was made to use a command that requires a Java system class that was not yet present or was invalid. Action: Load the system classes, or do not use the command. ORA-29548: Java system class reported: string Cause: A command that uses a Java system class was aborted due to an error reported by the Java system class. Action: Correct the error that was reported. ORA-29549: class string.string has changed, Java session state cleared Cause: A class in use by the current session was redefined or dropped, invalidating the current Java session state and requiring that it be cleared. Action: No action required. ORA-29550: Java session state cleared Cause: The Java state in the current session became inconsistent and was cleared. Action: No action required. ORA-29551: could not convert string to Unicode Cause: A string in the database character set could not be converted to Unicode, as required for use by Java. Action: Correct the string. ORA-29552: verification warning: string Cause: An attempt was made to create a Java class object with bytecodes that caused the Java verifier to issue a warning. Action: It is possible that the Java class was created from a damaged class file, in which case the CREATE should be reattempted with a correct class file. It is also possible that the message is the result of using "-" in the resolver so that the verifier could not check the correctness of some code. In that case, the class needs to be created with a resolver. ORA-29553: class in use: string.string Cause: An attempt was made to modify a Java class that is in use in the current call. Action: Correct the code in use in this call. ORA-29554: unhandled Java out of memory condition Cause: The session encountered an out of memory condition in Java from which it could not recover. Java session state was cleared. Action: No action required. ORA-29555: Java source, class or resource is not allowed here Cause: A Java source, class, or resource was specified in an inappropriate place in a statement. Action: Make sure the name is correct or remove it. ORA-29556: object type has changed Cause: A database object name that named a Java source, class, or resource now names an object of a different type. Action: No action required. ORA-29557: Java system class string cannot be modified Cause: A command was attempted that would have modified a Java system class. Action: No action required. ORA-29558: JAccelerator (NCOMP) not installed. Refer to Install Guide for instructions. Cause: JAccelerator (NCOMP) is not installed. Action: Please refer to the Post-installation Tasks section in the Database Install Guide for instructions on how to install JAccelerator (NCOMP). ORA-29655: USING clause is incompatible with its supertype Cause: The USING clause of a type has to be the same as its supertype or compatible with it. Action: Make sure the USING clause is compatible with its supertype. ORA-29656: Invalid option for USING Cause: The class has to implement the required interface for the value of the option for USING. Action: Make sure the USING clause is supported. ORA-29657: class defined in EXTERNAL NAME clause is used in another subtype Cause: The supertype has an existing type that has the same value for the EXTERNAL NAME. Action: Make sure the EXTERNAL NAME clause is unique among subtypes. ORA-29658: EXTERNAL NAME clause is not compatible with its supertype Cause: The EXTERNAL NAME clause of the type is not a subclass of the supertype EXTERNAL NAME. Action: Make sure the EXTERNAL NAME clause of the type is a subclass of the EXTERNAL NAME of its supertype. ORA-29659: SQLJ Object Type validation failed to get default connection Cause: Unable to connect using the JDBC default connection. Action: No action required. ORA-29660: Unable to find the class defined in the EXTERNAL NAME clause Cause: The class is not loaded in the database. Action: Make sure the EXTERNAL NAME corresponds to a loaded class in the the database. ORA-29661: Unable to find the superclass of the defined in the EXTERNAL NAME Cause: The class is not loaded in the database. Action: Make sure the superclass of the EXTERNAL NAME is loaded in the the database. ORA-29662: Unable to find a field that matches one or more of the attributes Cause: The EXTERNAL NAME option of one or more attributes do not match any fields in the defined class. Action: Make sure the EXTERNAL NAME option of each attribute matches a field in the defined in the defined class. ORA-29663: Unable to find a method that matches one or more of the functions Cause: The EXTERNAL NAME option of one or more functions do not match any method in the defined class. Action: Make sure the EXTERNAL NAME option of each function matches a method in the defined in the defined class. ORA-29664: Unable to generate the helper class for the defined type Cause: The helper class used for supporting SQLJ Object Type is not generated. Action: No Action is required. ORA-29665: Java thread deadlock detected Cause: The Java VM has detected a thread deadlock. Action: Modify the Java program to avoid the deadlock condition. ORA-29701: unable to connect to Cluster Manager Cause: Connect to CM failed or timed out. Action: Verify that the CM was started. If the CM was not started, start it and then retry the database startup. If the CM died or is not responding, check the Oracle and CM trace files for errors. ORA-29702: error occurred in Cluster Group Service operation Cause: An unexpected error occurred while performing a CGS operation. Action: Verify that the LMON process is still active. Also, check the Oracle LMON trace files for errors. ORA-29703: error occurred in global enqueue service operation Cause: An unexpected error occurred while performing a global enqueue service operation. Action: Check oracle trace files for errors. ORA-29704: cannot specify ACTIVE_INSTANCE_COUNT in 8.1.5 or earlier release Cause: The ACTIVE_INSTANCE_COUNT parameter was specified when one of the instances in the cluster was running Oracle 8.1.5 or an earlier release. Action: Restart the instance without specifying the ACTIVE_INSTANCE_COUNT parameter. Or, upgrade all instances to Oracle 8.1.6 or later release and then specify the parameter. ORA-29705: ACTIVE_INSTANCE_COUNT is string which is incompatible with the value in other instances Cause: The value of the ACTIVE_INSTANCE_COUNT parameter must be the same in all Oracle cluster database instances. Action: Check your initialization parameter files in all instances and ensure that the ACTIVE_INSTANCE_COUNT parameter has the same value. Then restart the instance. ORA-29706: incorrect value string for parameter ACTIVE_INSTANCE_COUNT Cause: The ACTIVE_INSTANCE_COUNT parameter must be set to 1 in a two node cluster database configuration or unspecified if a secondary instance is not needed. Action: Check your initialization parameter files and correct the value of the ACTIVE_INSTANCE_COUNT parameter. If you are configuring a two node primary/secondary cluster database, set this value to 1. Otherwise, do not specify any value for the parameter. ORA-29707: inconsistent value string for initialization parameter string with other instances Cause: The value of the initialization parameter in error must be identical on all Oracle cluster database instances and was not. Action: Check your INIT.ORA files on all instances and ensure that the initialization parameters in error have the same value. ORA-29740: evicted by member string, group incarnation string Cause: This member was evicted from the group by another member of the cluster database for one of several reasons, which may include a communications error in the cluster, failure to issue a heartbeat to the control file, etc. Action: Check the trace files of other active instances in the cluster group for indications of errors that caused a reconfiguration. ORA-29741: IMR active for some, but not all members of cluster Cause: The IMR feature is not active for this instance, but is active for another instance in the cluster database. Action: Ensure that all instances have the same value for the _imr_active init.ora parameter ORA-29746: Cluster Synchronization Service is being shut down. Cause: The administrator has shut down the Cluster Synchronization Service daemon. This error message is intended to be informative to users on the status of the service. Action: Check the log file of the Cluster Synchronization Service daemon to verify the state of the service. ORA-29760: instance_number parameter not specified Cause: The init.ora file did not contain a value for the instance_number which is required to identify this instance to other instances of the database running on the same cluster Action: Assign a value to the instance_number parameter in the init.ora parameter file ORA-29800: invalid name for operator Cause: The name specified for the operator is incorrect. Action: Specify a correct name for the operator. ORA-29801: missing RETURN keyword Cause: The RETURN keyword has not been specified. Action: Specify the RETURN keyword or check the SQL statement. ORA-29802: missing CONTEXT keyword Cause: The CONTEXT keyword has not been specified. Action: Specify the CONTEXT keyword or check the SQL statement. ORA-29803: missing ANCILLARY keyword Cause: The ANCILLARY keyword has not been specified. Action: Specify the ANCILLARY keyword or check the SQL statement. ORA-29804: missing DATA keyword Cause: The DATA keyword has not been specified. Action: Specify the DATA keyword or check the SQL statement. ORA-29805: missing COLUMN keyword Cause: Keyword COLUMN is expected . Action: Either specify the COLUMN keyword or specify another option. ORA-29806: specified binding does not exist Cause: The operator binding which has been specified does not exist. Action: Ensure that the operator binding that has been specified does exist. ORA-29807: specified operator does not exist Cause: The operator which has been specified does not exist. Action: Ensure that the operator that has been specified does exist. ORA-29808: specified primary operator binding does not exist Cause: The specified binding for the primary operator does not exist. Action: Ensure that the specified binding for the primary operator exists. ORA-29809: cannot drop an operator with dependent objects Cause: The operator which is being dropped has some dependent objects. Action: Either drop the dependent objects first and then issue the DROP OPERATOR command or specify the FORCE option with DROP OPERATOR. ORA-29810: inadequate operator privileges Cause: The user does not have the appropriate privileges to perform the specified operation on the operator. Action: Grant the appropriate privileges to the user and then reissue the statement. ORA-29811: missing STATISTICS keyword Cause: This is not a valid option with the ASSOCIATE command. Action: Specify STATISTICS keyword after the ASSOCIATE command. ORA-29812: incorrect object name specified Cause: The specified name is not a valid name. Action: Specify the correct name of the object with for which an association needs to be defined. ORA-29813: non-supported object type with associate statement Cause: The type of object specified is not supported with the associate statistics statement. Action: Use a valid object type with the associate command. ORA-29814: expecting USING or DEFAULT keyword Cause: Expecting the USING or DEFAULT keyword after the names of object(s). Action: Provide the USING or DEFAULT keyword. ORA-29815: object being associated is not present Cause: The object for which the association is being defined is not present. Action: Ensure that all the objects for which the association is being defined are present. ORA-29816: object being disassociated is not present Cause: Object which is being disassociated is not present. Action: Ensure that the object which needs to be disassociated is present. ORA-29817: non-supported option with disassociate statement Cause: The type of object specified is not supported with the disassociate statistics statement. Action: Use a object type which is supported with the disassociate command. ORA-29818: column name not properly specified Cause: Name of the column should contain the table and the column name. Action: Specify a valid column name. ORA-29819: cannot associate default values with columns Cause: User tried to associate DEFAULT values with columns which is not a valid option . Action: Specify a valid option. ORA-29820: the statistics type is not present Cause: The statistics type which is being associated with object(s) is not present. Action: Ensure that the type which contains the statistics functions is present. ORA-29821: specified primary operator does not exist Cause: The specified primary operator does not exist. Action: Check the primary operator and the signature specified. ORA-29822: selectivity cannot be specified for the type of object Cause: User tried to associate selectivity with index or indextypes which is not allowed . Action: Specify a valid option. ORA-29823: object being analyzed is not a table Cause: The object being analyzed is not a table and is not supported Action: Specify only a supported option. ORA-29824: operator is invalid Cause: The operator is invalid. Action: Drop and recreate the operator. ORA-29825: invalid name for indextype Cause: Indextype name or Indextype schema name has invalid characters. Action: Verify that the name has valid characters and it is not a reserved word. ORA-29826: keyword FOR is missing Cause: FOR keyword must be provided with Create Indextype statement. Action: Use FOR keyword and provide relevant operator information. ORA-29827: keyword USING is missing Cause: USING keyword and corresponding implementation details must be provided. Action: Provide USING keyword and relevant implementation details with Create Indextype statement. ORA-29828: invalid name for implementation type Cause: Implementation type or Implementation schema name is invalid. Action: Verify that the name has valid characters and it is not a reserved word. ORA-29829: implementation type does not exist Cause: The implementation type specified with USING clause could not be found. Action: Check to see if the type exists and the user has EXECUTE privilege on this type. ORA-29830: operator does not exist Cause: The operator could not be found. Action: Verify that the operator exists and the user has EXECUTE privilege for this operator. ORA-29831: operator binding not found Cause: The specified binding for the operator is not available from the operator schema object. Action: Verify that the operator with the specified binding exists. ORA-29832: cannot drop or replace an indextype with dependent indexes Cause: One or more indexes are dependent upon the indextype. Action: Drop all the indexes which are dependent upon the indextype before dropping the indextype itself. ORA-29833: indextype does not exist Cause: There is no indextype by the specified name. Action: Use public views for the indextypes to see if an indextype by the specified name has been created. ORA-29834: REF datatype not supported with operators Cause: The user specified a REF datatype which is not supported in CREATE OPERATOR. Action: Reissue the CREATE OPERATOR statement without the REF datatype. ORA-29835: ODCIGETINTERFACES routine does not return required interface(s) Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the interface(s) required by the current usage. Action: Ensure that the ODCIGetInterfaces routine returns the name(s) of the required interface(s). ORA-29836: failed to validate referenced operators Cause: One of the operators referenced cannot be compiled. Action: Try to recompile the operators which are referenced by this indextype. Use USER_INDEXTYPE_OPERATORS view to find out the referenced operators. ORA-29837: insufficient privileges to execute implementation type Cause: User does not have privileges to execute the implementation type. Action: The owner of the implementation type must grant appropriate privileges to the user. ORA-29838: insufficient privileges to execute the operator(s) Cause: User does not have privileges to execute one of the operators. Action: The owner of the operators must grant appropriate privileges to the user . ORA-29839: failed to validate implementation type Cause: Implementation type cannot be compiled. Action: Try to compile the implementation type. ORA-29840: indextype and implementation type are not in same schema Cause: Indextype and implementation type are in different schema. Action: Put the indextype and implementation type in the same schema. ORA-29841: invalid option for ALTER INDEXTYPE Cause: The user specified an invalid option with the ALTER INDEXTYPE command Action: Choose a valid option with the ALTER INDEXTYPE command ORA-29842: option not supported with the version string of the indextype interface Cause: User specified an option which is not supported with the version of the indextype interface provided Action: User should either not request for this option or should provide an implementation type that implements the correct version of the indextype interface. ORA-29843: indextype should support atleast one operator Cause: User attempted to drop all the operators from the indextype Action: Do not drop all the operators from the indextype ORA-29844: duplicate operator name specified Cause: User attempted to add an operator name to an indextype which is already supported by the indextype Action: Remove the duplicate operator and retry the command ORA-29845: indextype does not support local domain index on string partitioned table Cause: User specified a create local domain index statement using an indextype that does not support local domain indexes on tables partitioned with the given method Action: Use a different indextype or build a global domain index ORA-29846: cannot create a local domain index on a string partitioned table Cause: User specified a create local domain index statement on a table partitioned using a method not supported by domain indexes Action: Build a global domain index on the partitioned table ORA-29847: cannot create a local domain index on a partitioned index-organized table Cause: User specified a create local domain index statement on a partitioned index-organized table Action: Build a global domain index on the partitioned index-organized table ORA-29848: error occurred in the execution of ODCIINDEXMERGEPARTITION routine Cause: Failed to successfully execute the ODCIIndexMergePartition routine. Action: Check to see if the routine has been coded correctly. ORA-29849: error occurred in the execution of ODCIINDEXSPLITPARTITION routine Cause: Failed to successfully execute the ODCIIndexSplitPartition routine. Action: Check to see if the routine has been coded correctly. ORA-29850: invalid option for creation of domain indexes Cause: The user specified an invalid option like ASC, DESC, SORT or a parallel clause, partitioning clause or physical attributes clause. Action: Choose one of the valid clauses for creation of domain indexes. ORA-29851: cannot build a domain index on more than one column Cause: User attempted to build a domain index on more than one column. Action: Build the domain index only on a single column. ORA-29852: keyword IS is missing Cause: IS keyword must be specified with Create Index statement for domain indexes. Action: Use IS keyword and then specify the indextype name. ORA-29853: keyword UNIQUE may not be used in creating domain indexes Cause: An attempt was made to create a domain index with the UNIQUE attribute. Action: Remove UNIQUE from the CREATE INDEX statement. ORA-29854: keyword BITMAP may not be used in creating domain indexes Cause: An attempt was made to create a domain index with the BITMAP attribute. Action: Remove BITMAP from the CREATE INDEX statement. ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine Cause: Failed to successfully execute the ODCIIndexCreate routine. Action: Check to see if the routine has been coded correctly. ORA-29856: error occurred in the execution of ODCIINDEXDROP routine Cause: Failed to successfully execute the ODCIIndexDrop routine. Action: Check to see if the routine has been coded correctly. ORA-29857: domain indexes and/or secondary objects exist in the tablespace Cause: An attempt was made to drop a tablespace which contains secondary objects and/or domain indexes. Action: Drop the domain indexes in his tablespace. Also, find the domain indexes which created secondary objects in this tablespace and drop them. Then try dropping the tablespace. ORA-29858: error occurred in the execution of ODCIINDEXALTER routine Cause: Failed to successfully execute the ODCIIndexAlter routine. Action: Check to see if the routine has been coded correctly. ORA-29859: error occurred in the execution of ODCIINDEXTRUNCATE routine Cause: Failed to successfully execute the ODCIIndexTruncate routine. Action: Check to see if the routine has been coded correctly. ORA-29860: cannot truncate a table with domain indexes marked LOADING Cause: The table has domain indexes defined on it that are marked LOADING. Action: Wait to see if the ongoing index DDL ends and the index state changes from LOADING state. Else ,drop the domain indexes marked as LOADING with the FORCE option. ORA-29861: domain index is marked LOADING/FAILED/UNUSABLE Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation. Action: Wait if the specified index is marked LOADING Drop the specified index if it is marked FAILED Drop or rebuild the specified index if it is marked UNUSABLE. ORA-29862: cannot specify FORCE option for dropping non-domain index Cause: A DROP INDEX FORCE was issued for a non-domain index. Action: Reissue the command without the FORCE option. ORA-29863: warning in the execution of ODCIINDEXCREATE routine Cause: A warning was returned from the ODCIIndexCreate routine. Action: Check to see if the routine has been coded correctly Check user specified log tables for greater detail. ORA-29864: analyzing domain indexes marked LOADING/FAILED not supported Cause: Tried to analyze a domain index which was marked as LOADING or FAILED. Action: If the index was marked LOADING, wait till it is marked valid before retrying the analyze. If index was marked FAILED, drop it OR rebuild it and retry the analyze. ORA-29865: indextype is invalid Cause: The indextype is invalid. Action: Drop and recreate the indextype. ORA-29866: cannot create domain index on a column of index-organized table Cause: Tried to create a domain index on a column of an index-organized table. Action: Do not attempt to create a domain index on columns of an index-organized table. ORA-29867: cannot create a domain index on a LONG column Cause: The user attempted to create a domain index on a column of LONG datatype. Action: Do not create a domain index on a LONG column. ORA-29868: cannot issue DDL on a domain index marked as LOADING Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index in a LOADING state. Action: Wait till the index operation completes OR issue a DROP INDEX FORCE to drop the index. ORA-29869: cannot issue ALTER without REBUILD on a domain index marked FAILED Cause: Tried to issue a DROP/ALTER on a domain index in a FAILED state. Action: Truncate the table to mark the index as valid OR do ALTER INDEX REBUILD to rebuild the index. ORA-29870: specified options are only valid for altering a domain index Cause: Specified the ONLINE or PARAMETERS clause with a non-domain index. Action: Reissue the statement with the correct syntax for alter. ORA-29871: invalid alter option for a domain index Cause: The user specified an invalid option for altering a domain index. Action: Reissue the alter statement with a valid option. ORA-29872: parameters clause cannot be combined with the specified options Cause: The user combined PARAMETERS clause with other alter index options. Action: Reissue the statement with the correct syntax for alter. ORA-29873: warning in the execution of ODCIINDEXDROP routine Cause: A waring was returned from the ODCIIndexDrop routine. Action: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details. ORA-29874: warning in the execution of ODCIINDEXALTER routine Cause: A waring was returned from the ODCIIndexAlter routine. Action: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details. ORA-29875: failed in the execution of the ODCIINDEXINSERT routine Cause: Failed to successfully execute the ODCIIndexInsert routine. Action: Check to see if the routine has been coded correctly. ORA-29876: failed in the execution of the ODCIINDEXDELETE routine Cause: Failed to successfully execute the ODCIIndexDelete routine. Action: Check to see if the routine has been coded correctly. ORA-29877: failed in the execution of the ODCIINDEXUPDATE routine Cause: Failed to successfully execute the ODCIIndexUpdate routine. Action: Check to see if the routine has been coded correctly. ORA-29878: warning in the execution of ODCIINDEXTRUNCATE routine Cause: A warning was returned from the ODCIIndexTruncate routine. Action: Check to see if the routine has been coded correctly Check the user defined warning log tables for greater details. ORA-29879: cannot create multiple domain indexes on a column list using same indextype Cause: An attempt was made to define multiple domain indexes on the same column list using identical indextypes. Action: Check to see if a different indextype can be used or if the index can be defined on another column list. ORA-29880: such column list already indexed using another domain index and indextype Cause: An attempt was made to create multiple domain indexes on a column list using indextypes which do not have disjoint operators. Action: Check to see if the operator sets for the indextypes can be made disjoint. ORA-29881: failed to validate indextype Cause: Indextype cannot be compiled. Action: Try to compile the indextype which is referenced by the domain index. ORA-29882: insufficient privileges to execute indextype Cause: User does not have privileges to execute the indextype. Action: The owner of the indextype must grant appropriate privileges to the user. ORA-29883: cannot create a domain index on column expressions Cause: User specified an expression in the column list. Action: Specify only simple columns in the column list for domain index. ORA-29884: domain index is defined on the column to be dropped Cause: An ALTER TABLE DROP COLUMN was issued on a column on which a domain index exists. Action: Drop the domain index before attempting to drop the column. ORA-29885: domain index is defined on the column to be modified Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which a domain index exists. Action: Drop the domain index before attempting to modify the column. ORA-29886: feature not supported for domain indexes Cause: Feature is not supported for domain indexes. Action: No action required. ORA-29887: cannot support row movement if domain index defined on table Cause: An ALTER TABLE ENABLE ROW MOVEMENT was issued on a table which has a domain index defined on it. Action: Drop the domain index if you want to enable row movement and then reissue the command. ORA-29888: cannot create domain index on a table with row movement enabled Cause: A create domain index statement was issued on a table that has row movement enabled. Action: Disable the row movement in the table and then reissue the create domain index statement. NLS_DO_NOT_TRANSLATE[29889,29889] ORA-29890: specified primary operator does not have an index context Cause: The primary operator does not have an index and scan contexts. Action: Create the primary operator with a context clause. NLS_DO_NOT_TRANSLATE[29891,29891] ORA-29892: indextypes with array DML do not support the given data type Cause: The user specified a REF or a LONG datatype which is not supported in CREATE/ALTER INDEXTYPE WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE). Action: Reissue the CREATE/ALTER INDEXTYPE statement without the REF or LONG datatype. ORA-29893: indextypes without column data do not need the given data type Cause: WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE) option and WITHOUT COLUMN DATA option conflicted in an alter indextype statement Action: Reissue the ALTER INDEXTYPE statement without the conflict. ORA-29894: base or varray datatype does not exist Cause: One of the base and varray datatypes specified in WITH ARRAY DML (DATA_TYPE, VARRAY_TYPE) clause could not be found. Action: Check to see if the datatype exists and the user has EXECUTE privilege on this datatype. ORA-29895: duplicate base datatype specified Cause: User attempted to add a base datatype to an indextype with ARRAY DML which is already supported by the indextype Action: Remove the duplicate base datatype and retry the command ORA-29896: Length of PARAMETER string longer than string characters Cause: An attempt was made to specify a parameter value that is longer than the allowed maximum. Action: Reduce the parameter value length. ORA-29900: operator binding does not exist Cause: There is no binding for the current usage of the operator. Action: Change the operator arguments to match any of the existing bindings or add a new binding to the operator. ORA-29901: function underlying operator binding does not exist Cause: The function underlying the operator binding does not exist. Action: Ensure that the function corresponding to the operator invocation exists. ORA-29902: error in executing ODCIIndexStart() routine Cause: The execution of ODCIIndexStart routine caused an error. Action: Examine the error messages produced by the indextype code and take appropriate action. ORA-29903: error in executing ODCIIndexFetch() routine Cause: The execution of ODCIIndexFetch routine caused an error. Action: Examine the error messages produced by the indextype code and take appropriate action. ORA-29904: error in executing ODCIIndexClose() routine Cause: The execution of ODCIIndexClose routine caused an error. Action: Examine the error messages produced by the indextype code and take appropriate action. ORA-29905: method string does not exist in type string.string Cause: A required method with the required signature does not exist in the specified type. Action: Add the required method to the type. ORA-29906: indextype string.string does not exist Cause: The indextype does not exist. Action: Create the indextype. ORA-29907: found duplicate labels in primary invocations Cause: There are multiple primary invocations of operators with the same number as the label. Action: Use distinct labels in primary invocations. ORA-29908: missing primary invocation for ancillary operator Cause: The primary invocation corresponding to an ancillary operator is missing. Action: Add the primary invocation with the same label as the ancillary operator. ORA-29909: label for the ancillary operator is not a literal number Cause: The label used for invoking the ancillary operator is not a literal number. Action: Use a literal number as the label. ORA-29910: invalid callback operation Cause: Encountered an invalid callback operation. Action: Ensure that all the callbacks executed from callouts are valid in the statement context. ORA-29911: null scan context returned by ODCIIndexStart() routine Cause: The ODCIIndexStart() routine returned a null scan context Action: Ensure that the ODCIIndexStart() routine returns a non-null scan context. ORA-29913: error in executing string callout Cause: The execution of the specified callout caused an error. Action: Examine the error messages take appropriate action. ORA-29914: ODCIGETINTERFACES routine does not return required stream version Cause: The ODCIObjectList returned by the ODCIGetInterfaces routine does not contain the required stream version for external tables. Action: Ensure that the ODCIGetInterfaces routine returns the required stream version. ORA-29915: cannot select FOR UPDATE from collection operand Cause: Collection operands cannot be updated Action: Remove FOR UPDATE clause ORA-29917: cannot lock a table which gets its rows from a collection operand Cause: Tables which gets its rows from a collection operand cannot be locked Action: Don"t lock the table ORA-29918: cannot create domain indexes on temporary tables Cause: An attempt was made to create a domain index on a temporary table Action: Either create another type of index on the temporary table or change the table from temporary to a permanent table ORA-29925: cannot execute string Cause: The specified function does not exist or does not have an appropriate signature. Action: Implement the function with the appropriate signature. ORA-29926: association already defined for the object Cause: The object for which the association is being defined, already has a statistics type associated with it. Action: Disassociate the object and then associate the object. ORA-29927: error in executing the ODCIStatsCollect / ODCIStatsDelete routine Cause: The ODCIStatsCollect / ODCIStatsDelete function is causing an error. Action: Check the ODCIStatsCollect / ODCIStatsDelete function. ORA-29928: duplicate default selectivity specified Cause: The keyword DEFAULT SELECTIVITY can only be specified once. Action: Remove the duplicate keyword. ORA-29929: missing SCAN Keyword Cause: The scan context is not specified. Action: Supply the SCAN keyword. ORA-29930: COMPUTE ANCILLARY DATA specified without the INDEX CONTEXT clause Cause: The COMPUTE ANCILLARY DATA option was specified without the WITH INDEX CONTEXT clause. Action: Specify the WITH INDEX CONTEXT option. ORA-29931: specified association does not exist Cause: One or more of the object(s) that have been specified to be disassociated, do not have an association defined for them. Action: Verify the objects which have an association defined and issue the disassociate command again. ORA-29932: the type being dropped is a statistics type Cause: Some objects have defined their statistics methods in the type being dropped. Action: First drop the relevant associations using the DISASSOCIATE command and then retry the DROP command, or use the FORCE option with DROP TYPE command. ORA-29933: object being disassociated has some user defined statistics stored Cause: There are some user defined statistics collected for the object being disassociated. Action: First delete the user defined statistics and then reissue the DISASSOCIATE command or specify the FORCE option with DISASSOCIATE. ORA-29934: index specified for association is not a domain index Cause: The user issued an ASSOCIATE STATISTICS command with an index which is not a domain index. Action: Issue an ASSOCIATE STATISTICS WITH INDEXES command on a domain index only ORA-29935: missing FROM keyword Cause: The keyword FROM is missing. Action: Specify the FROM keyword or check the SQL statement. ORA-29936: NULL association is allowed only with a column or an index Cause: User tried to use the ASSOCIATE command with a schema object other than a column or an index Action: Specify the NULL clause only with a column or an index ORA-29950: warning in the execution of ODCIINDEXMERGEPARTITION routine Cause: A warning was returned from the ODCIIndexMergePartition routine. Action: Check to see if the routine has been coded correctly Check user specified log tables for greater detail. ORA-29951: warning in the execution of ODCIINDEXSPLITPARTITION routine Cause: A warning was returned from the ODCIIndexSplitPartition routine. Action: Check to see if the routine has been coded correctly Check user specified log tables for greater detail. ORA-29952: cannot issue DDL on a domain index partition marked as LOADING Cause: Tried to issue a DROP/ALTER/TRUNCATE on a domain index partition in a LOADING state. Action: Wait till the index partition operation completes OR issue a DROP INDEX FORCE to drop the index OR issue a ALTER TABLE DROP PARTITION to drop the partition. ORA-29953: cannot issue DDL on a domain index partition marked as FAILED Cause: Tried to issue a DROP/ALTER on a domain index partition in a FAILED state. Action: do ALTER INDEX REBUILD PARTITION to rebuild the index partition OR ALTER TABLE TRUNCATE PARTITION to mark the index partition as valid. ORA-29954: domain index partition is marked LOADING/FAILED/UNUSABLE Cause: An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation. Action: Wait if the specified index partition is marked LOADING Rebuild the specified index partition if it is marked FAILED or UNUSABLE. ORA-29955: error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine Cause: Failed to successfully execute the ODCIIndexExchangePartition routine. Action: Check to see if the routine has been coded correctly. ORA-29956: warning in the execution of ODCIINDEXEXCHANGEPARTITION routine Cause: A warning was returned from the ODCIIndexExchangePartition routine. Action: Check to see if the routine has been coded correctly Check user specified log tables for greater detail. ORA-29957: cannot create a function-based domain index on a string table Cause: User specified an unsupported create function-based domain index statement. Action: Issue the create function-based domain index statement only on supported types of tables. ORA-29958: fatal error occurred in the execution of ODCIINDEXCREATE routine Cause: Failed to successfully execute the ODCIIndexCreate routine. Action: Check to see if the routine has been coded correctly. ORA-29959: error in the execution of the string routine for one or more of the index partitions Cause: An error occurred during execution of the routine for one or more of the index partitions Action: Check the *_IND_PARTITIONS view to see which partitions are marked FAILED. Rebuild or Truncate the FAILED index partitions ORA-29960: line string, string Cause: The ODCIIndex DDL routine has put a warning message into table SYS.ODCI_WARNINGS$ Action: Check the warning message ORA-29961: too many warnings occurred in the execution of ODCIIndex DDL routine Cause: The number of warnings during the ODCIIndex DDL routine is too high. Action: Query table SYS.ODCI_WARNINGS$ to get more warning messages ORA-29962: fatal error occurred in the execution of ODCIINDEXALTER routine Cause: Failed to successfully execute the ODCIIndexAlter routine. Action: Check to see if the routine has been coded correctly. ORA-29963: missing BINDING keyword Cause: Keyword BINDING is expected . Action: Specify the BINDING keyword or check the SQL statement. ORA-29964: missing ADD or DROP keyword Cause: One of the keywords ADD or DROP is expected. Action: Specify the ADD or DROP keyword or check the SQL statement. ORA-29965: The specified binding does not exist Cause: The binding specified in the DROP BINDING clause is not a valid binding for this operator. Action: Specify an existing binding for this op in DROP BINDING clause. ORA-29966: The only binding of an operator cannot be dropped Cause: This operator only has one binding. It cannot be dropped using Alter Operator Drop Binding. Action: If you wish to drop the entire operator, call Drop Operator. ORA-29967: Cannot drop an operator binding with dependent objects Cause: The operator binding that is being dropped has dependent objects. Action: Either drop the dependent objects first and then issue the ALTER OPERATOR DROP BINDING command or specify the FORCE option with ALTER OPERATOR DROP BINDING. ORA-29968: No primary operator bindings found for ancillary binding #string Cause: At least one ancillary binding of the specified operator could not be validated because all of its associated primary operator bindings have been dropped. Action: Either drop the ancillary binding whose primary operators are missing, or drop the entire operator, if this is the only binding. This binding cannot be re-validated. ORA-29970: Specified registration id does not exist Cause: An incorrect regid value was passed to dbms_chnf procedure. Action: pass the correct regid value. ORA-29971: Specified table name not found or does not have any registrations Cause: The database could not locate the passed in table name Action: CHeck the table name passed in. ORA-29972: user does not have privilege to change/ create registration Cause: User passed in an incorrect or someone else"s regid/ handle. Action: Check the passed in regid/ reg handle ORA-29973: Unsupported query or operation during change notification registration Cause: The user attempted to register an unsupported query type or an unsupported operation like a DML/DDL for change notification. Action: Please check the statement being executed and refer to the documentation. ORA-29974: Internal event for PL/SQL debugging Cause: None Action: none ORA-29975: Cannot register a query in the middle of an active transaction Cause: User tried to register a query within an uncommitted transction. Action: Commit the transaction and retry. ORA-30000: missing either trim specification or char expression in TRIM Cause: Since FROM is specified in TRIM function, either trim specification (TRAILING, HEADING, BOTH) or trim character or both must be specified. Action: Add either trim specification (TRAILING, HEADING, BOTH) or trim character or both. ORA-30001: trim set should have only one character Cause: Trim set contains more or less than 1 character. This is not allowed in TRIM function. Action: Change trim set to have only 1 character. ORA-30002: SYS_CONNECT_BY_PATH function is not allowed here Cause: SYS_CONNECT_BY_PATH function is called at places other than select list. Action: Remove calls to SYS_CONNECT_BY_PATH function at places other than select list. ORA-30005: missing or invalid WAIT interval Cause: A non-zero integer must be specified for wait interval (in seconds) after the WAIT keyword. Action: Correct the syntax and retry. ORA-30006: resource busy; acquire with WAIT timeout expired Cause: The requested resource is busy. Action: Retry the operation later. ORA-30011: Error simulated: psite=string, ptype=string Cause: error generated for testing purposes. Action: None. ORA-30012: undo tablespace "string" does not exist or of wrong type Cause: the specified undo tablespace does not exist or of the wrong type. Action: Correct the tablespace name and reissue the statement. ORA-30013: undo tablespace "string" is currently in use Cause: the specified undo tablespace is currently used by another instance. Action: Wait for the undo tablespace to become available or change to another name and reissue the statement. ORA-30014: operation only supported in Automatic Undo Management mode Cause: the operation is only supported in automatic undo mode. Action: restart instance in Automatic Undo Management mode before retrying operation. ORA-30015: previously offlined undo tablespace "string" is still pending Cause: the current operation is not allowed because an undo tablespace containing active transactions is pending from a previous SWITCH UNDO operation. The operation will be allowed again after all transactions in the previous undo tablespace are committed. Action: Wait for all previous transactions to commit before reissuing the current statement. ORA-30016: undo tablespace "string" is already in use by this instance Cause: the specified undo tablespace is currently used by this instance. The operation failed. Action: If the specified undo tablespace name is wrong, reissue the statement with the correct name. ORA-30017: segment "string" is not supported in string Undo Management mode Cause: the type of the specified undo segment is incompatible with the current undo management mode of the instance. Action: Check the undo segment name and the undo management mode and reissue statement if necessary. ORA-30018: Create Rollback Segment failed, USN string is out of range Cause: the system runs out of undo segment number. Too many undo segments exist. Action: drop some of the unused undo segments and retry operation. ORA-30019: Illegal rollback Segment operation in Automatic Undo mode Cause: This operation only allowed in Manual Undo mode. Action: restart instance in Manual Undo_Management mode and retry operation. ORA-30020: UNDO_MANAGEMENT=AUTO needs Compatibility string or greater Cause: Auto undo management mode not allowed in specified compatibility release Action: restart instance in correct compatibility release ORA-30021: Operation not allowed on undo tablespace Cause: This operation is not allowed on undo tablespaces Action: Check the tablespace name and reissue command if necessary ORA-30022: Cannot create segments in undo tablespace Cause: Cannot create segments in undo tablespace Action: Check the tablespace name and reissue command ORA-30023: Duplicate undo tablespace specification Cause: Cannot create more than one undo tablespace during database creation Action: Modify the command to contain only one undo tablespace ORA-30024: Invalid specification for CREATE UNDO TABLESPACE Cause: You have specified an clause that should not used with CREATE UNDO TABLESPACE Action: Drop the clause from the command and reissue it. ORA-30025: DROP segment "string" (in undo tablespace) not allowed Cause: Explicit DROP operation is not allowed on undo tablespace segments Action: Check the undo segment name and reissue statement if necessary. ORA-30026: Undo tablespace "string" has unexpired undo with string(sec) left, Undo_Retention=string(sec) Cause: Tried to drop a tablespace that contains unexpired undo information Action: lower setting of UNDO_RETENTION or wait a while before reissue command to drop undo tablespace ORA-30027: Undo quota violation - failed to get string (bytes) Cause: the amount of undo assigned to the consumer group of this session has been exceeded. Action: ask DBA to increase undo quota, or wait until other transactions to commit before proceeding. ORA-30028: Automatic Undo Management event for NTP testing Cause: test events for internal use only Action: none. ORA-30029: no active undo tablespace assigned to instance Cause: the current instance does not have an active undo tablespace assigned to execute transactions. Action: ask DBA to create an undo tablespace, online the undo tablespace and then retry operation. ORA-30030: suppress resumable related error message Cause: none Action: This event is to be used if the errors 30031 and 30032 wish to be suppressed. ORA-30031: the suspended (resumable) statement has been aborted Cause: DBA or the user aborted the execution of the suspended statement in the resumable session Action: none ORA-30032: the suspended (resumable) statement has timed out Cause: A correctible error was signaled in the resumable session and the error was not cleared within the timeout interval. Action: Fix the correctible error within the timeout. Default is 2 hours. Or increase the (resumable) timeout. ORA-30033: Undo tablespace cannot be specified as default user tablespace Cause: It is incorrect to specify undo tablespace as default user tablespace Action: Check the tablespace name and reissue the command ORA-30034: Undo tablespace cannot be specified as temporary tablespace Cause: Undo tablespace cannot be specified as default temporary tablespace for the user Action: Check the tablespace name and reissue the command ORA-30035: Undo tablespace cannot be specified as default temporary tablespace Cause: Undo tablespace cannot be specified as default temporary tablespace for the database Action: Check the tablespace name and reissue the command ORA-30036: unable to extend segment by string in undo tablespace "string" Cause: the specified undo tablespace has no more space available. Action: Add more space to the undo tablespace before retrying the operation. An alternative is to wait until active transactions to commit. ORA-30037: Cannot perform parallel DML after a prior DML on the object Cause: Attempt to perform parallel DML after another DML on the same object in the same transaction. Action: Use bitmap segments to perform multiple (parallel) DML operations on the same object. Or commit before issueing the DML ORA-30038: Cannot perform parallel insert on non-partitioned object Cause: Attempt to perform parallel insert on a non-partitioned object after a previous DML on the object in the same transaction. Action: Commit before issueing the insert. ORA-30039: Cannot drop the undo tablespace Cause: Cannot drop an undo tablespace that is in use Action: Switch to a different undo tablespace and then try to drop ORA-30040: Undo tablespace is offline Cause: Cannot operate on an offlined undo tablespace Action: Online the undo tablespace and redo the operation ORA-30041: Cannot grant quota on the tablespace Cause: User tried to grant quota on an undo or temporary tablespace Action: Check the tablespace name and reissue the command ORA-30042: Cannot offline the undo tablespace Cause: Cannot offline an undo tablespace that is in use Action: Switch to a different undo tablespace and then try to offline ORA-30043: Invalid value "string" specified for parameter "Undo_Management" Cause: the specified undo management mode is invalid Action: Correct the parameter value in the initialization file and retry the operation. ORA-30044: "Retention" can only specified for undo tablespace Cause: An attempt was made to specify retention for a non-undo tablespace. Action: Modify the CREATE TABLESPACE statement. ORA-30045: No undo tablespace name specified Cause: If Create Database has the datafile clause, then undo tablespace name has to be specified, unless using OMF. Action: Specify the undo tablespace name. ORA-30046: Undo tablespace string not found in control file. Cause: The specified undo tablespace is not present in the control file. Action: Modify the CREATE CONTROLFILE statement that created the current control file to include undo tablespace(s) and reissue the statement. ORA-30047: Internal event for kti tracing Cause: internal use only Action: none ORA-30048: Internal event for IMU auto-tuning Cause: internal use only Action: none ORA-30049: Internal event for TA enq tracing Cause: internal use only Action: none ORA-30051: VERSIONS clause not allowed here Cause: A VERSIONS clause was specified when it was not allowed. Action: Do not use the VERSIONS clause ORA-30052: invalid lower limit snapshot expression Cause: The lower limit snapshot expression was below the UNDO_RETENTION limit. Action: Specify a valid lower limit snapshot expression. ORA-30053: invalid upper limit snapshot expression Cause: The upper limit snapshot expression is greater than the SQL statement read snapshot. Action: Specify a valid upper limit snapshot expression. ORA-30054: invalid upper limit snapshot expression Cause: The upper limit snapshot expression is less than the lower limit snapshot expression. Action: Specify a valid upper limit snapshot expression. ORA-30055: NULL snapshot expression not allowed here Cause: The snapshot expression is NULL. Action: Specify a non-NULL snapshot expression. ORA-30060: Internal event for RECO tracing Cause: internal use only Action: none ORA-30061: Internal Event for Savepoint Tracing Cause: internal use only Action: none ORA-30062: Test support for ktulat latch recovery Cause: internal use only Action: none. ORA-30063: Internal Event to Test NTP Cause: none Action: none ORA-30064: Test support for two phase read only optimization Cause: internal use only Action: none. ORA-30065: test support for row dependencies Cause: internal use only Action: none. ORA-30066: test support - drop rollback segment wait Cause: internal use only Action: none. ORA-30067: Internal Event to turn on nested debugging info Cause: none Action: none. ORA-30068: Internal Event to turn on nested Cause: none Action: none. ORA-30069: Auto Undo-Management Error simulation - test site = string Cause: test events for internal use only. Action: none. ORA-30071: conversion between datetime/interval and string fail Cause: An error occurs during a conversion between datetime/interval and string data type due to one of the following reasons: - The buffer is too short to hold the result. - The format string is bad. Action: none ORA-30072: invalid time zone value Cause: The value specified for the time zone string, which appears in ALTER SESSION statement, environment variable ORA_SDTZ, or a datetime factor, is not valid. Action: none ORA-30073: invalid adjustment value Cause: The value is none of the followings: "ADJUST", "NO_ADJUST", "ANSI_DATE", "ADJUST_WITH_ANSI_DATE". "NO_ADJUST" is the default value. Action: set it to one of the three values ORA-30074: GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed Cause: try to GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE. Action: Do not GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE. ORA-30075: TIME/TIMESTAMP WITH TIME ZONE literal must be specified in CHECK constraint Cause: User is trying to create a constraint on a time or timestamp with or without time zone column without explicitly specifying the time zone. Action: Use time or timestamp with time zone literals only. ORA-30076: invalid extract field for extract source Cause: The extract source does not contain the specified extract field. Action: none ORA-30077: illegal casting between specified datetime types Cause: Cannot cast between the specified datetime types. Action: none ORA-30078: partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals Cause: An attempt was made to use a time/timestamp expression whose format does not explicitly have time zone on a TIME/TIMESTAMP or TIME/TIMESTAMP WITH TIME ZONE column. Action: Explicitly use TIME/TIMESTAMP WITH TIME ZONE literal. ORA-30079: cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns Cause: An attempt was made to alter database timezone with TIMESTAMP WITH LOCAL TIME ZONE column in the database. Action: Either do not alter database timezone or first drop all the TIMESTAMP WITH LOCAL TIME ZONE columns. ORA-30081: invalid data type for datetime/interval arithmetic Cause: The data types of the operands are not valid for datetime/interval arithmetic. Action: none ORA-30082: datetime/interval column to be modified must be empty to decrease fractional second or leading field precision Cause: datetime/interval column with existing data is being modified to decrease fractional second or leading field precisions. Action: Such columns are only allowed to increase the precisions. ORA-30083: syntax error was found in interval value expression Cause: A syntax error was found during parsing an interval value value expression. Action: Correct the syntax. ORA-30084: invalid data type for datetime primary with time zone modifier Cause: When a time zone modifier is specified, the data type of datetime primary must be one of the following: TIME, TIME WITH TIME ZONE, TIMESTAMP, TIMESTAMP WITH TIME ZONE. Action: none ORA-30085: syntax error was found in overlaps predicate Cause: A syntax error was found during parsing an overlaps predicate. Action: Correct the syntax. ORA-30086: interval year-month result not allowed for datetime subtraction Cause: An attempt was made to specify interval year to month as the result of datetime subtraction. Action: This is not allowed currently due to unclear specification in SQL Standards for this interval type. Change the interval type to interval day to second and resubmit statement. ORA-30087: Adding two datetime values is not allowed Cause: An attempt was made to add two datetime values. Action: This addition is not allowed. ORA-30088: datetime/interval precision is out of range Cause: The specified datetime/interval precision was not between 0 and 9. Action: Use a value between 0 and 9 for datetime/interval precision. ORA-30089: missing or invalid Cause: A (YEAR, MONTH, DAY, HOUR, MINUTE, SECOND) is expected but not found, or a specified the in an is more significant than its . Action: none ORA-30100: internal error [number] Cause: An internal error has occurred. Action: Contact Oracle Worldwide Support and report the error. ORA-30101: unknown parameter name "string" Cause: You have misspelled the parameter name. Action: Spell the parameter name correctly. ORA-30102: "string" is not in the legal range for "string" Cause: The value of the parameter is not within the legal range. Action: Refer to the manual for the allowable values for this parameter. ORA-30103: "string" contains an illegal integer radix for "string" Cause: An illegal integer radix specification was found. Action: Only "d", "h", "D", and "H" may be used as radix specifications. ORA-30104: "string" is not a legal integer for "string" Cause: The value is not a valid integer. Action: Specify only valid integers for this parameter. ORA-30105: "string" is not a legal boolean for "string" Cause: The value is not a valid boolean. Action: Refer to the manual for allowable boolean values. ORA-30106: reserved for future use Cause: None. Action: None. ORA-30107: parameter name abbreviation "string" is not unique Cause: The abbreviation given was not unique. Action: Use a longer abbreviation to make the parameter name unique. ORA-30108: invalid positional parameter value "string" Cause: An invalid positional parameter value has been entered. Action: Remove the invalid positional parameter. ORA-30109: could not open parameter file "string" Cause: The parameter file does not exist. Action: Create an appropriate parameter file. ORA-30110: syntax error at "string" Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. ORA-30111: no closing quote for value "string" Cause: A quoted string was begun but not finished. Action: Put a closing quote in the proper location. ORA-30112: multiple values not allowed for parameter "string" Cause: You attempted to specify multiple values for a parameter which can take only one value. Action: Do not specify more than one value for this parameter. ORA-30113: error when processing file "string" Cause: A problem occurred when processing this file. Action: Examine the additional error messages and correct the problem. ORA-30114: error when processing from command line Cause: A problem occurred when processing the command line. Action: Examine the additional error messages and correct the problem. ORA-30115: error when processing an environment variable Cause: A problem occurred when processing an environment variable. Action: Examine the additional error messages and correct the problem. ORA-30116: syntax error at "string" following "string" Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. ORA-30117: syntax error at "string" at the start of input Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. ORA-30118: syntax error at "string" at the end of input Cause: A syntax error was detected. Action: Change the input so that the correct syntax is used. ORA-30119: unable to obtain a valid value for "string" Cause: No valid value was obtained for this parameter. Action: Rerun the application and enter a valid value. ORA-30120: "string" is not a legal oracle number for "string" Cause: The value is not a valid oracle number. Action: Refer to the manual for allowable oracle number values. ORA-30121: "string" is not an allowable value for "string" Cause: The value is not a legal value for this parameter. Action: Refer to the manual for allowable values. ORA-30122: value "string" for "string" must be between "number" and "number" Cause: The value of the parameter is not within the legal range. Action: Specify a value that is within the legal range. ORA-30129: invalid function argument received Cause: A function received an invalid argument Action: Check function calls, make sure correct arguments are being passed. ORA-30130: invalid parameter key type received Cause: A function received an invalid parameter key type Action: Check parameter key types in function calls ORA-30131: number of keys being set exceeds allocation Cause: Number of parameter keys being set exceeds allocation Action: Reduce the number of keys being set or increase allocation ORA-30132: invalid key index supplied Cause: The key index specified was not within bounds Action: Change key index to ensure it lies within bounds ORA-30133: reserved for future use Cause: None. Action: None. ORA-30134: reserved for future use Cause: None. Action: None. ORA-30135: OCI Thread operation fails Cause: An OCI Thread function call has failed. Action: Check the function call to make sure that the correct parameters are being passed and take the apropriate action. ORA-30150: Invalid argument passed to OCIFile function Cause: An invalid argument is passed to the OCIFile function. The most common cause is that a NULL pointer is passed where a non-NULL pointer is expected. Action: Make sure that the values passed as arguments are valid. Esp check for NULL pointers. ORA-30151: File already exists Cause: Tried to open a file with OCI_FILE_EXCL flag and the file already exists. Action: OCIFile is supposed throw this exception in this case. ORA-30152: File does not exist Cause: The OCIFile function requires the file to exist, but it does not. Action: Make sure that the file exists. ORA-30153: An invalid File Object is passed to the OCIFile function Cause: An invalid File Object is passed to the OCIFile function. Action: Make sure that the file object is a valid one. Create a new file object by calling OCIFileOpen if needed. ORA-30154: The memory address given as buffer for OCIFileRead/Write is invalid Cause: An invalid memory address is given as the buffer pointer for OCIFileRead/Write. Action: Make sure that the required memory is allocated and pass a valid memory address as buffer pointer. ORA-30155: An I/O Error occured during an OCIFile function call Cause: An I/O error occurred at the system level. Action: This is a system error and the action will depnd on the error. ORA-30156: Out of disk space Cause: The disks associated with the underlying file system are full. Action: Create more disk space. ORA-30157: An invalid argument was given to operating system call Cause: The OS call was called with an invalid argument. Action: Check the values passed. If unsuccessful to solve the problem contact ORACLE support. ORA-30158: The OCIFileWrite causes the file to exceed the maximum allowed size Cause: There is no space to write to the file. Its size is at the maximum limit. Action: Up to the user. ORA-30159: OCIFileOpen: Cannot create the file or cannot open in the requested mode Cause: The create flag was specified in OCIFileOpen such that the file was to be created. But unable to do so. Or the file already exists and the permissions on it doesn"t allow the file to be opened in in the requested open mode Action: Check whether the user has permissions to create the specified file or if the file exists whether the permissions on it allow the requested open mode. ORA-30160: Unable to access the file Cause: The function was unable to access the existing the file. Action: Check if the user has the required permissions on the file. ORA-30161: A system error occurred during the OCIFile function call Cause: A system error occured while executing the OCIFile function. Action: Depend on the error. ORA-30162: The OCIFile context is not initialzed Cause: The function OCIFileInit need to be called before calling any other OCIFile function to initialize the OCIFile context. Action: Call the function OCIFileInit need to be called before calling any other OCIFile function. ORA-30163: The thread safety initialization failed Cause: The call to SlgInit failed in OCIFileInit. Action: Contact support ORA-30175: invalid type given for an argument Cause: There is an argument with an invalid type in the argument list. Action: Use the correct type wrapper for the argument. ORA-30176: invalid format code used in the format string Cause: There is an invalid format code in the format string. Action: Replace the invalid format code with a valid one. ORA-30177: invalid flag used in a format specification Cause: There is an invalid flag in a format specification. Action: Replace the invalid flag with a valid one. ORA-30178: duplicate flag used in a format specification Cause: There is a duplicate flag in a format specification. Action: Remove the duplicate flag. ORA-30179: invalid argument index used in a format code Cause: Zero or negative argument index or index not following (." Action: Replace the invalid argument index with a valid one. ORA-30180: argument index is too large Cause: An argument index exceeds actual number of arguments supplied. Action: Fix format string or pass additional arguments. ORA-30181: integer in argument index is not immediately followed by ) Cause: Missing closing parenthesis in argument index. Action: Fix the format specification. ORA-30182: invalid precision specifier Cause: Period in format specification not followed by valid format. Action: Replace the invalid precision specifier with a valid one. ORA-30183: invalid field width specifier Cause: Invalid field width supplied. Action: Replace the invalid field width with a valid one. ORA-30184: argument type not compatible with a format code Cause: Bad argument type given for a format code. Action: Make format and arguments be compatible. ORA-30185: output too large to fit in the buffer Cause: The buffer is not large enough to hold the entire output string. Action: Fix the buffer size and length passed in. ORA-30186: "\" must be followed by four hexdecimal characters or another "\" Cause: In the argument of SQL function UNISTR, a "" must be followed by four hexdecimal characters or another "" Action: Fix the string format ORA-30187: reserved for future use Cause: None. Action: None. ORA-30188: reserved for future use Cause: None. Action: None. ORA-30189: reserved for future use Cause: None. Action: None. ORA-30190: reserved for future use Cause: None. Action: None. ORA-30191: missing argument list Cause: No argument list supplied. Action: Modify the argument list to have at least OCIFormatEnd in it. ORA-30192: reserved for future use Cause: None. Action: None. ORA-30193: reserved for future use Cause: None. Action: None. ORA-30194: reserved for future use Cause: None. Action: None. ORA-30195: reserved for future use Cause: None. Action: None. ORA-30196: reserved for future use Cause: None. Action: None. ORA-30197: reserved for future use Cause: None. Action: None. ORA-30198: reserved for future use Cause: None. Action: None. ORA-30199: reserved for future use Cause: None. Action: None. ORA-30200: Wrong NLS item was passed into OCINlsGetInfo() Cause: The item is not supported NLS item Action: Correct the item number passed to OCINlsGetInfo(). ORA-30201: Unable to load NLS data object Cause: It may be caused by invalid NLS environment setting Action: Check your NLS environment setting such as ORA_NLS33 ORA-30202: NULL pointer to OCIMsgh was passed to OCIMsg function Cause: The NULL pointer was passed. Action: Check your value of OCIMsgh pointer. ORA-30203: Cannot open mesage file Cause: The message may not exist in your system. Action: Check your message for the given product and facility. ORA-30204: buffer is not large enougth Cause: The destination buffer is not large enough for storing converted data. Action: Check the size of the destination buffer. ORA-30205: invalid Character set Cause: The specified character set is invalid. Action: Check if the character set ID is valid. ORA-30331: summary does not exist Cause: A non-existant summary name was specified. Action: Check the spelling of the summary name. ORA-30332: container table already in use by other summary Cause: Another summary is already using this table as a container table. Action: Select another table or materialized view as the container table for this summary. ORA-30333: dimension does not exist Cause: The dimension named in a dimension DDL statment does not exist. Action: Check the spelling of the dimension name. ORA-30334: illegal dimension level name Cause: A level name in a dimension ddl statement did not conform to SQL identifier rules. Action: Use a level name that begins with a letter, consists of only letters, digits, and underscores and contains no more than 30 characters. ORA-30335: JOIN KEY clause references a level not in this hierarchy Cause: The level name specified with the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not reference a level in the hierarchy that contains the JOIN KEY clause. *Acction: Check the spelling of the level name. Action: none ORA-30336: no child for specified JOIN KEY Cause: The level specified in the REFERENCES portion of a JOIN KEY clause in a dimension DDL statement does not have a child level. Action: Check the spelling of the level name referenced in the JOIN KEY clause. If the referenced level is the first level in the hierarchy, you need not and must not specify a JOIN KEY clause. ORA-30337: multiple JOIN KEY clauses specified for the same parent level Cause: Multiple JOIN KEY clauses were specified for a given parent level in a dimension hierarchy. Action: Match up each JOIN KEY clause with the level it references in the hierarchy. Eliminate the redundant JOIN KEY clause. ORA-30338: illegal dimension hierachy name Cause: An illegal dimension hierarchy name was specified in a dimension DDL statement. Action: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system. ORA-30339: illegal dimension attribute name Cause: An illegal dimension attribute name was specified in a dimension DDL statement. Action: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system. ORA-30340: illegal dimension name Cause: An illegal dimension name was specified in a dimension DDL statement. Action: Make sure the name begins with a letter, contains only letters, digits and underscore and contains no more than 30 characters. If you qualify the name with the owner name, make sure the owner name conforms with the requirements for an owner name on your system. ORA-30341: dropped level has references Cause: An attempt was made to drop a level using the default or RESTRICT option in a dimension while references to that level remain in the dimension. References can occur in hierarchies and attributes within the dimension. Action: First remove any referenes to the level prior to dropping it, or specify the CASCADE option with the DROP LEVEL clause. ORA-30342: referenced level is not defined in this dimension Cause: A reference to a level not defined within the dimension was found. Action: Check the spelling of the level name. ORA-30343: level name is not unique within this dimension Cause: Two or more levels were defined with the same name. Action: Check the spelling of the level names. ORA-30344: number of child cols different from number of parent level cols Cause: The number of child columns specified in a JOIN KEY clause is not the same as the number of columns in the specified parent level. Action: Check the child columns and the columns in the definition of the referenced parent level and correct the discrepency. ORA-30345: circular dimension hierarchy Cause: A circularity was found the dimension hierarchy. Action: Check the hierarchy for a level name that occurs more than once. ORA-30346: hierarchy name must be unique within a dimension Cause: The same name was used for more than one hierarchy in a dimension. Action: Check the spelling of the hierarchy name. ORA-30347: a table name is required to qualify the column specification Cause: A table name was omitted in a column specification where where the column must be qualified by the table name. Action: Qualify the column with the table name. ORA-30348: ADD and DROP cannot both be specified Cause: One or more ADD clauses were found in the same ALTER DIMENSION statement with one or more DROP clauses. Action: Separate your ADD operations into one ALTER DIMENSION statement and your DROP operations into another. ORA-30349: specified dimension hierarchy does not exist Cause: A hierarchy name was encountered that is not defined within the dimension. Action: Check the spelling of the hierarchy name. ORA-30350: specified dimension attribute does not exist Cause: An attribute name was encountered that is not defined within the dimension. Action: Check the attribute name spelling. ORA-30351: query rewrite does not currently support this expression Cause: A complex expression was specified that is is not currently supported by query rewrite. Action: Reduce the complexity of the expression. ORA-30352: inconsistent numeric precision or string length Cause: The SELECT expression was of a different numeric precision or string length than the corresponding container column. Therefore, query rewrite cannot guarantee results that are identical to the results obtained with the un-rewritten query. Action: Correct the precision or string length difference, specify the WITH REDUCED PRECISION option, or disable the REWRITE option on the materialized view. ORA-30353: expression not supported for query rewrite Cause: The select clause referenced UID, USER, ROWNUM, SYSDATE, CURRENT_TIMESTAMP, MAXVALUE, a sequence number, a bind variable, correlation variable, a set result,a trigger return variable, a parallel table queue column, collection iterator, etc. Action: Remove the offending expression or disable the REWRITE option on the materialized view. ORA-30354: Query rewrite not allowed on SYS relations Cause: A SYS relation was referenced in the select clause for a materialized view with query rewrite enabled. Action: Remove the reference to the SYS relation from the select clause or disable the REWRITE option on the materialized view. ORA-30355: materialized view container does not exist Cause: A DROP TABLE command was issued directly against the materialized view container table. Action: Use the DROP MATERIALIZED VIEW command to clean up the residual meta data for the materialized view. Then use the CREATE MATERIALIZED VIEW statement to recreate the materialized view. Thereafter, use the DROP MATERIALIZED VIEW command rather than the DROP TABLE command to drop a materialized view. ORA-30356: the specified refresh method is not supported in this context Cause: The refresh method that was specified is not currently supported. Action: Specify a different refresh method or change the context to enable support of the chosen refresh method. ORA-30357: this PL/SQL function cannot be supported for query rewrite Cause: The statement referenced a PL/SQL function that is not marked DETERMINISTIC. Action: Perform one of the following actions: - Remove the use of the PL/SQL function. - Mark the PL/SQL function as DETERMINISTIC. - Disable the REWRITE option on the materialized view. The function should be marked DETERMINISTIC only if it always returns the same result value for any given set of input argument values, regardless of any database state or session state. Do not mark the function as DETERMINISTIC if it has any meaningful side-effects. ORA-30358: summary and materialized view are not in same schema Cause: An internal Oracle error occured. Action: Report the problem through your normal support channels. ORA-30359: Query rewrite is not supported on SYS materialized views Cause: An attempt was made to enable the REWRITE option on a materialized view in the SYS schema. Action: Create the materialized view in a different schema or disable the REWRITE option. ORA-30360: REF not supported with query rewrite Cause: The statement contained a REF operator. Repeatable behavior cannot be guaranteed with the REF operator. Therefore, query rewrite cannot support the REF operator. Action: Remove the reference to the REF operator or disable the REWRITE option on the materialized view. ORA-30361: unrecognized string type Cause: An internal Oracle error occured. Action: Report the problem through your normal support channels. ORA-30362: dimension column cannot be a sequence Cause: The dimension statement referenced a column that is a sequence. Action: Remove the reference to the sequence. ORA-30363: columns in a dimension column list must be in the same relation Cause: The dimension statement contained a column list where the columns are not all from the same relation. Action: Specify the list of columns using only columns from a single relation. ORA-30364: this level has the same set of columns as another Cause: The level definition contained the same set of columns as another level. Action: Eliminate the redundant level definition. ORA-30365: left relation in the JOIN KEY clause cannot be same as right Cause: The relation of the child columns on the left side of the JOIN KEY clause was the same as that of the parent level on the right side. Action: Remove the JOIN KEY clause. It is not required or allowed when the child and the parent are in the same relation. ORA-30366: child JOIN KEY columns not in same relation as child level Cause: The relation of the child columns on the left side of the JOIN KEY clause differed from that of that child level. Action: Specify the correct child columns in the JOIN KEY clause. ORA-30367: a JOIN KEY clause is required Cause: A JOIN KEY clause was omitted in a dimension statement. A JOIN KEY clause is required when the child level and the parent level are not in the same relation. Action: Specify a JOIN KEY clause to indicate how the relation of the child level joins to the relation of the parent level. ORA-30368: ATTRIBUTE cannot determine column in a different relation Cause: An ATTRIBUTE clause in a dimension statement specified a determined column on the right that is in a different relation than that of the level on the left. Action: Specify attibutes only for those dimension levels that functionally determine other columns within the same relation. ORA-30369: maximum number of columns is 32 Cause: A list of columns was specified using more than 32 columns. Action: Specify the list using no more than 32 columns. ORA-30370: set operators are not supported in this context Cause: A set operator such as UNION, UNION ALL, INTERSECT, or MINUS was encountered in an unsupported context, such as in a materialized view definition. Action: Re-specify the expression to avoid the use of set operators. ORA-30371: column cannot define a level in more than one dimension Cause: A column was used in the definition of a level after it had already been used to define a level in a different dimension. Action: Reorganize dimension levels and hierarchies into a single dimension such that no column is used to define levels in different dimensions. There is no limit on the number of levels or hierarchies you can place in a dimension. A column can be used to define any number of levels provided all such levels are in the same dimension and provided no two levels contain identical sets of columns. ORA-30372: fine grain access policy conflicts with materialized view Cause: A fine grain access control procedure has applied a non-null policy to the query for the materialized view. Action: In order for the materialized view to work correctly, any fine grain access control procedure in effect for the query must return a null policy when the materialized view is being created or refreshed. This may be done by ensuring that the usernames for the creator, owner, and invoker of refresh procedures for the materialized view all receive a null policy by the user-written fine grain access control procedures. ORA-30373: object data types are not supported in this context Cause: An object data type was encountered in an unsupported context. Action: Re-specify the expression to avoid the use of objects. ORA-30374: materialized view is already fresh Cause: If the materialized view is fresh, ORACLE ignores the ALTER MATERIALIZED VIEW RELY FRESH command, and issues this error message. Action: None ORA-30375: materialized view cannot be considered fresh Cause: If the materialized view is invalid or unusable, it cannot be considered fresh with the ALTER MATERIALIZED VIEW CONSIDER FRESH command. Action: None ORA-30376: prevent sharing of a parsed query of an explain rewrite session Cause: Explain rewrite generates a shared cursor after parsing the user query. Raising this error will prevent the cursor from being shared. Action: None ORA-30377: table string.MV_CAPABILITIES_TABLE not found Cause: You have used the DBMS_MVIEW.EXPLAIN_MVIEW() API before you have defined the MV_CAPABILITIES_TABLE. Action: Invoke the admin/utlxmv.sql script after connecting to the desired schema. ORA-30378: MV_CAPABILITIES_TABLE is not compatible with Oracle version Cause: One or more column definitions in the MV_CAPABILITIES_TABLE is either missing or incompatible with the current Oracle version. Action: Connect to the appropriate schema, DROP TABLE MV_CAPABILITIES_TABLE and recreate it by invoking the admin/utlxmv.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_MVIEW() API. ORA-30379: query txt not specified Cause: You have attempted use DBMS_MVIEW.EXPLAIN_REWRITE() API using an empty query text argument Action: Input a valid SQL query ORA-30380: REWRITE_TABLE does not exist Cause: You have used the DBMS_MVIEW.EXPLAIN_REWRITE() API before you have created the REWRITE_TABLE. Action: Create it using the admin/utlxrw.sql script after connecting to the desired schema ORA-30381: REWRITE_TABLE is not compatible with Oracle version Cause: One or more column definitions in the REWRITE_TABLE is either missing or incompatible with the current Oracle version. Action: Connect to the appropriate schema, DROP TABLE REWRITE_TABLE and recreate it by invoking the admin/utlxrw.sql script prior to invoking the DBMS_MVIEW.EXPLAIN_REWRITE() API. ORA-30382: DROP MATERIALIZED VIEW string.string operation is not complete Cause: The drop materialized view operation got an unexpected error while dropping summary object. Action: Issue the drop materialized view command again ORA-30383: specified dimension level does not exist in the attribute Cause: An attribute level was encountered that is not defined within the attribute. Action: Check the attribute level name spelling. ORA-30384: specified column name does not exist in the attribute Cause: A column was encountered that is not defined within the attribute. Action: Check the attribute column name spelling. ORA-30385: specified attribute relationship ("string" determines "string") exists Cause: The specified attribute relationship has already been declared in one of the attribute clauses Action: Remove the duplicate attribute relationship ORA-30386: invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE Cause: Either the source or destination statement is NULL Action: Verify both source and destination statement are valid ORA-30387: invalid rewrite mode for REWRITE_EQUIVALENCE API Cause: The specified rewrite mode is not supported by REWRITE_EQUIVALENCE API Action: Verify the rewrite mode is supported by REWRITE_EQUIVALENCE API ORA-30388: name of the rewrite equivalence is not specified Cause: The name of the rewrite equivalence is NULL Action: Input a valid rewrite equivalence name ORA-30389: the source statement is not compatible with the destination statement Cause: The SELECT clause of the source statement is not compatible with the SELECT clause of the destination statement Action: Verify both SELECT clauses are compatible with each other such as numbers of SELECT list items are the same and the datatype for each SELECT list item is compatible ORA-30390: the source statement is not equivalent to the destination statement Cause: the set of rows returned by the source SQL text is not the same as the set of rows returned by the destination SQL text Action: Make sure both source and destination statement return the same number of rows ORA-30391: the specified rewrite equivalence does not exist Cause: the specified rewrite equivalence does not exist Action: Verify the rewrite equivalence has been created ORA-30392: the checksum analysis for the rewrite equivalence failed Cause: the given checksum does not match with that generated from the source and destination statements. Action: Verify the create safe rewrite equivalence statement to see if it has been modified. ORA-30393: a query block in the statement did not rewrite Cause: A query block with a REWRITE_OR_ERROR hint did not rewrite Action: Verify the rewrite equivalence has been created ORA-30394: source statement identical to the destination statement Cause: The source statement was identical to the destination statement Action: Make sure both source and destination statements are not identical ORA-30395: dimension options require the COMPATIBLE parameter to be string or greater Cause: The following materialized view options require 10.1 or higher compatibility setting: o dimension attribute extended level syntax ATTRIBUTE LEVEL DETERMINES Action: Shut down and restart with an appropriate compatibility setting. ORA-30396: rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater Cause: Query rewrite equivalence APIs require 10.1 or higher compatibility setting: o DBMS_ADVANCED_REWRITE.DECLARE_REWRITE_EQUIVALENCE o DBMS_ADVANCED_REWRITE.ALTER_REWRITE_EQUIVALENCE o DBMS_ADVANCED_REWRITE.DROP_REWRITE_EQUIVALENCE o DBMS_ADVANCED_REWRITE.VALIDATE_REWRITE_EQUIVALENCE Action: Shut down and restart with an appropriate compatibility setting. // ORA-30397: multiple JOIN KEY clauses specified for the same child level Cause: Multiple JOIN KEY clauses were specified for a given child level in a dimension hierarchy. Action: Eliminate the redundant JOIN KEY clauses. ORA-30398: illegal JOIN KEY clause Cause: A JOIN KEY clause was specified that did not conform to certain requirements. A JOIN KEY clause connecting a child level with its non-immediate ancestor level is allowed only when that child level and its ancestor level satisfy the following conditions: 1. The immediate parent of the child level must be a skip level. 2. The child level cannot be a skip level. 3. The ancestor level must be a non-skip level. 4. The ancestor level must be the nearest non-skip level to the child level in the hierarchy. Action: Modify the JOIN KEY clause so that it satisfies the conditions mentioned above. ORA-30399: a skip level must have at least one column that allows NULL values Cause: A SKIP clause cannot be specified with a level when all of the columns that make up the level have NOT NULL constraints. Action: Drop the SKIP clause. ORA-30400: identical JOIN KEY clauses Cause: Two JOIN KEY clauses with identical child keys and parent levels were specified. Action: Eliminate the redundant JOIN KEY clause. ORA-30401: JOIN KEY columns must be non-null Cause: The dimension statement failed because the column(s) in the JOIN KEY clause permitted NULL values. The JOIN KEY columns are related to the columns of the dimension"s skip levels in one or both of the following ways: 1. A skip level is defined over one or more of the JOIN KEY columns. 2. The attribute clauses of a skip level determine one or more of the JOIN KEY columns. Action: Modify the JOIN KEY columns so that they do not allow NULL values. ORA-30430: list does not contain any valid summaries Cause: List is empty or does not contain the names of existing summaries Action: Verify that the list of names passed to refresh contains the name of at least one existing summary object ORA-30431: refresh method must be ANY or INCREMENTAL or FORCE_FULL, not string Cause: An invalid refresh method was specified Action: Verify that the refresh method is one of "ANY" or "INCREMENTAL" or "FORCE_FULL" ORA-30432: summary "string.string" is in INVALID state Cause: The summary is in INVALID state and cannot be refreshed Action: none ORA-30433: "string.string" is not a summary Cause: There is no such summary, therefore it cannot be refreshed Action: Verify the correct name of the summary ORA-30434: refresh method must be one of FC?AN, not "string" Cause: An invalid refresh method was specified Action: Verify that the refresh method is one of "FC?AN" ORA-30435: job_queue_processes must be non-zero in order to refresh summaries Cause: The server must be started with parameter "job_queue_processes" greater than zero Action: Correct the value of job_queue_processes and restart the server instance ORA-30436: unable to open named pipe "string" Cause: The refresh process was unable to open a named pipe to the job queue process usually because of insufficient system resources Action: This is an internal error. Notify ORACLE technical support ORA-30437: all job queue processes have stopped running Cause: All of the job queue processes used by refresh have stopped for some reason. At least one job queue process must be running in order to refresh summaries. Action: This is an internal error. Notify ORACLE technical support ORA-30438: unable to access named pipe "string" Cause: The refresh process was unable to access a named pipe to the job queue process after it successfully opened the pipe. This usually indicates an internal or operating system error condition. Action: This is an internal error. Notify ORACLE technical support ORA-30439: refresh of "string.string" failed because of string Cause: The refresh job queue process encountered an error and is reporting it. The accompanying text of the message indicates cause of the error Action: Varies, depending upon the reported cause. ORA-30440: can"t fast refresh;refresh complete or set event 30441 for partial refresh Cause: Both DML and direct-load are performed against detail tables. Fast refresh can only process direct-load inserts. Action: Refresh complete or set event 30441 to enable partial refresh with only direct-load inserts ORA-30442: can not find the definition for filter string Cause: For the specified filterid parameter, there is no corresponding filter definition found in the advisor repository Action: Use a valid filterid geneated by the create_filter function ORA-30443: definition for filter string"s item string is invalid Cause: The specified filter is invalid. It contains at least one invalid filter item. If a filter item has a string list, it becomes illegal when the string list cannot be successfully parsed. If the filter item contains a range definition, and the lower bound of the range is greater than the higher bound, the item also becomes invalid. Action: Remove the illegal filter with the purge_filter sub-program and redefine a correct filter ORA-30444: rewrite terminated by the sql analyzer Cause: The sql analyzer terminates the rewrite process Action: This is an internal error. Notify ORACLE technical support ORA-30445: workload queries not found Cause: No workload queries in the advisor repository can satifiy the specified filter Action: Redefine a new filter or load additional workload queries that can satisfy the specified filter ORA-30446: valid workload queries not found Cause: None of the specified queries can be successfully parsed. The error may come from many sources: SQL syntax error, the owner specified by the load_workload subprograms do not match the real user who generates the SQL statement Action: Only load valid SQL statements into the advisor repository. Make sure the statements can be parsed with privilege of the owner as specified in the owner parameter of the load_workload() subprogram. ORA-30447: internal data for run number string is inconsistent Cause: Users should not explicitly modify summary advisor"s internal tables. Such modifications may cause inconsistency in the internal tables and result in this error. Action: Users can call the DBMS_OLAP.PURGE_RESULTS subprogram to remove the inconsistent data from summary advisor"s internal tables ORA-30448: internal data of the advisor repository is inconsistent Cause: Users should not explicitly modify summary advisor"s internal tables. Such modifications may cause inconsistency in the internal tables and result in this error. Action: This is an internal error. Notify ORACLE technical support ORA-30449: syntax error in parameter string Cause: The syntax for the specified parameter is incorrect Action: Check ORACLE documentation for the correct syntax ORA-30450: refresh_after_errors was TRUE; The following MVs could not be refreshed: string Cause: One or more errors occurred during a refresh of multiple summaries. Action: The number_of_failures parameter returns the count of how many failures occurred. The trace logs for each refresh operation describe the each individual failure in more detail ORA-30451: internal error Cause: An internal error was detected by the summary refresh subsystem, and aborted the refresh operation Action: Notify ORACLE support. ORA-30452: cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X) Cause: Incremental refresh of summaries requires a COUNT(X) column in order to incrementally refresh AVG(X). It requires both SUM(X) and COUNT(X) columns in order to in refresh STDDEV(X) or VARIANCE(X) Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. ORA-30453: summary contains AVG without corresponding COUNT Cause: Incremental refresh of summaries with AVG(X) requires a COUNT(X) column to be included in the summary definition Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. ORA-30454: summary contains STDDEV without corresponding SUM & COUNT Cause: Incremental refresh of summaries with STDDEV(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. ORA-30455: summary contains VARIANCE without corresponding SUM & COUNT Cause: Incremental refresh of summaries with VARIANCE(X) requires COUNT(X) and SUM(X) columns to be included in the summary definition Action: Make sure that the required columns are part of the summary definition if incremental refresh capability is desired. ORA-30456: "string.string" cannot be refreshed because of insufficient privilege Cause: The user lacks one or more permissions that are required in order to refresh summaries. Action: Make sure that the user is granted all required privileges. ORA-30457: "string.string" cannot be refreshed because of unmnanaged NOT NULL columns in container Cause: The container object for the summary contains one or more unmanaged columns do not allow nulls, and which do not specify a default valur for those columns. Action: Make sure that default values are specified for all NOT NULL columns that are not part of the summary definition. ORA-30458: "string.string" cannot be refreshed because the refresh mask is string Cause: An attempt was made to incrementally refresh a summary that is not incrementally refreshable. Action: Do not attempt to incrementally refresh the summary; use full refresh instead. ORA-30459: "string.string" cannot be refreshed because the refresh method is NONE Cause: An attempt was made to refresh a summary whose refresh method is NONE Action: Summaries whose refresh method is NONE (NEVER REFRESH) cannot be refreshed. Alter the summary to change the default refresh method from NONE to some other value. ORA-30460: "string.string" cannot be refreshed because it is marked UNUSABLE Cause: An attempt was made to refresh a summary which is UNUSABLE Action: Determine why the summary is UNUSABLE, re-enable it, and retry the refresh. ORA-30461: "string.string" cannot be refreshed because it is marked DISABLED Cause: An attempt was made to refresh a summary which is DISABLED Action: Determine why the summary is DISABLED, re-enable it, and retry the refresh. ORA-30462: unsupported operator: string Cause: An attempt was made to refresh a summary containing an unsupported operator Action: Verify that all columns of the summary contain expressions that are refreshable. ORA-30463: "string" is not a detail table of any summary Cause: The list of tables passed to refresh_dependent contains at least one invalid table name. That table is not a detail table of any summary and is therefore an invalid input to refresh_dependent Action: Verify the correct name of all tables in the list ORA-30464: no summaries exist Cause: A call was made to refresh_all_mviews, but no summaries exist. At least one summary must exist before calling refresh_all_mviews Action: Create one or more summaries ORA-30465: supplied run_id is not valid: string Cause: There are three possible causes: The specified run_id does not exist; the run_id was created by another user other than the current user; the run_id has already been used. Action: Call DBMS_OLAP.CREATE_ID to create a new id ORA-30466: can not find the specified workload string Cause: The specified workload_id is not valid Action: Use a valid workload_id or DBMS_OLAP.WORKLOAD_ALL ORA-30467: internal data for filter number string is inconsistent Cause: Users should not explicitly modify summary advisor"s internal tables. Such modifications may cause inconsistency in the internal tables and result in this error. Action: Users can call the DBMS_OLAP.PURGE_FILTER subprogram to remove the inconsistent data from summary advisor"s internal tables ORA-30475: feature not enabled: string Cause: The specified feature is not enabled. Action: Do not attempt to use this feature. ORA-30476: PLAN_TABLE does not exist in the user"s schema Cause: Estimate_Summary_Size uses Oracle SQL "EXPLAIN PLAN" command to estimate cardinality of the specified select-clause. This requires a table called the PLAN_TABLE in the user"s schema. For more information refer to the SQL Reference Manual. Action: Create the PLAN_TABLE as described for EXPLAIN PLAN. On most systems a script utlxplan.sql will create this table. ORA-30477: The input select_clause is incorrectly specified Cause: The input select-clause parameter to Estimate_Summary_Size is incorrectly specified and cannot be compiled. Action: Check the syntax of the select-clause. ORA-30478: Specified dimension does not exist Cause: the specified dimension to be verified does not exist Action: Check the spelling of the dimension name ORA-30479: Summary Advisor error string Cause: An error has occurred in the Summary Advisor package This message will be followed by a second message giving more details about the nature of the error. Action: See the Summary Advisor documentation for an explanation of the second error message. ORA-30483: window functions are not allowed here Cause: Window functions are allowed only in the SELECT list of a query. And, window function cannot be an argument to another window or group function. Action: none ORA-30484: missing window specification for this function Cause: All window functions should be followed by window specification, like () OVER () Action: none ORA-30485: missing ORDER BY expression in the window specification Cause: Either the ORDER BY expression is mandatory for this function, or there is an aggregation group without any ORDER by expression. Action: none ORA-30486: invalid window aggregation group in the window specification Cause: If the window specification is specified using RANGE option and there are multiple ORDER BY expressions, then the aggregation group cannot contain any expression (It can only have CURRENT ROW, UNBOUNDED PRECEDING, or UNBOUNDED FOLLOWING). First end point (bound) cannot be UNBOUNDED FOLLOWING and second end point cannot be UNBOUNDED PRECEDING. If the first end point is CURRENT ROW, then second end point can only be CURRENT ROW or /UNBOUNDED FOLLOWING. If the first end point is FOLLOWING, then second end point can only be /UNBOUNDED FOLLOWING. Action: none ORA-30487: ORDER BY not allowed here Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY Action: none ORA-30488: argument should be a function of expressions in PARTITION BY Cause: The argument of the window function should be a constant for a partition. Action: none ORA-30489: Cannot have more than one rollup/cube expression list Cause: GROUP BY clause has more than one rollup/cube expression list. Action: Modify the query such that only one rollup/cube expressions appear per sub-query. ORA-30490: Ambiguous expression in GROUP BY ROLLUP or CUBE list Cause: An expression in the GROUP BY ROLLUP or CUBE list matches an expression in the ordinary GROUP BY expression list Action: Remove the expression from either ordinary GROUP BY expression list or ROLLUP or CUBE expression list ORA-30493: The percentile value should be a number between 0 and 1. Cause: A percentile value for PERCENTILE_CONT or PERCENTILE_DISC function is specified out of range. Action: Specify a value from [0,1]. ORA-30500: database open triggers and server error triggers cannot have BEFORE type Cause: An attempt was made to create a trigger that fires before the database is open or before server errors, but these types of triggers are not supported. Action: Do not attempt to create a trigger that fires before the database is open or before server errors. ORA-30501: instance shutdown triggers cannot have AFTER type Cause: An attempt was made to create a trigger that fires after an instance shutdown, but this type of trigger is not supported. Action: Do not attempt to create a trigger that fires after an instance shutdown. ORA-30502: system triggers cannot have INSERT, UPDATE, or DELETE as triggering events Cause: An attempt was made to create a system trigger with INSERT, UPDATE, or DELETE triggering events, but this type of trigger is not supported because a system trigger does not have a base table. Action: Do not attempt to create a system trigger with INSERT, UPDATE, or DELETE triggering events. ORA-30503: system triggers cannot have a REFERENCING clause Cause: An attempt was made to use a REFERENCING clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table. Action: Do not use a REFERENCING clause with a system trigger. ORA-30504: system triggers cannot have a FOR EACH ROW clause Cause: An attempt was made to use a FOR EACH ROW clause with a system trigger, but this type of trigger is not supported because a system triggers does not have a base table. Action: Do not use a FOR EACH ROW clause with a system trigger. ORA-30505: system triggers should not reference a column in a WHEN clause Cause: An attempt was made to use a WHEN clause to reference a column with a system trigger, but this type of trigger is not supported because a system trigger does not have a base table. Action: Change the WHEN clause to an appropriate clause. ORA-30506: system triggers cannot be based on tables or views Cause: An attempt was made to base a system trigger on a table or a view. Action: Make sure the type of the trigger is compatible with the base object. ORA-30507: normal triggers cannot be based on a schema or a database Cause: An attempt was made to base a normal trigger on a schema or a database, but normal triggers can be based only on tables or views. Action: Make sure the type of the trigger is compatible with the base object. ORA-30508: client logon triggers cannot have BEFORE type Cause: An attempt was made to create a trigger that fires before logon. This type of trigger is not supported. Action: Do not attempt to create a trigger that fires before logon. ORA-30509: client logoff triggers cannot have AFTER type Cause: An attempt was made to create a trigger that fires after logoff. This type of trigger is not supported. Action: Do not attempt to create a trigger that fires after logoff. ORA-30510: system triggers cannot be defined on the schema of SYS user Cause: An attempt was made to define a system trigger on the schema of SYS user. This type of trigger is not supported currently. Action: Do not attempt to create a system trigger defined on the schema of SYS user. ORA-30511: invalid DDL operation in system triggers Cause: An attempt was made to perform an invalid DDL operation in a system trigger. Most DDL operations currently are not supported in system triggers. The only currently supported DDL operations are table operations and ALTER?COMPILE operations. Action: Remove invalid DDL operations in system triggers. ORA-30512: cannot modify string.string more than once in a transaction Cause: An attempt was made to modify an object more than once in a transaction. This error is usually caused by a DDL statement that fires a system trigger that tries to modify the same object. It can also happen when an attempt is made to perform more than one DDL operation on a queue table in the same transaction without issuing a commit between operations. Action: Do not create system triggers that might modify an already modified object. Also, do not specify more than one DDL operation on a queue table in the same transaction. ORA-30513: cannot create system triggers of INSTEAD OF type Cause: Only BEFORE or AFTER triggers can be created on system events. Action: Change the trigger type to BEFORE or AFTER. ORA-30514: system trigger cannot modify tablespace being made read only Cause: A beofre trigger tries to modify a tablespace which is being made READ ONLY as the part of DDL oepration Action: Modify the trigger to avoid modifications to the objects in the same tablespace as the one which is being made read only, or use autonomous transactions to commit modifications ORA-30515: suspend triggers cannot have BEFORE type Cause: An attempt was made to create a trigger that fires before execution suspended. This type of trigger is not supported. Action: Do not attempt to create a trigger that fires before execution suspended. ORA-30516: database role change triggers cannot have BEFORE type Cause: An attempt was made to create a trigger that fires before the role change completed. This type of trigger is not supported. Action: Do not attempt to create a trigger that fires before the role change completes. ORA-30550: index depends on a package/function spec/body which is not valid Cause: the functional indexes depends on some invalid/non-existent package/function spec/body Action: verify that all the package/functions which the index depends on exist and are valid ORA-30551: The index depends on a package/type body which does not exist Cause: the functional indexes depends on a package/type body which does not exist Action: create the package/type body ORA-30552: The package/procedure/function cannot be changed Cause: The package/procedure/function is deterministic and some object depends on it Action: Drop the other object which depends on the package/function/procedure you are trying to change ORA-30553: The function is not deterministic Cause: The function on which the index is defined is not deterministic Action: If the function is deterministic, mark it DETERMINISTIC. If it is not deterministic (it depends on package state, database state, current time, or anything other than the function inputs) then do not create the index. The values returned by a deterministic function should not change even when the function is rewritten or recompiled. ORA-30554: function-based index string.string is disabled Cause: An attempt was made to access a function-based index that has been marked disabled because the function on which the index depends has been changed. Action: Perform one of the following actions: -- drop the specified index using the DROP INDEX command -- rebuild the specified index using the ALTER INDEX REBUILD command -- enable the specified index using the ALTER INDEX ENABLE command -- make the specified index usable using the ALTER INDEX UNUSABLE command ORA-30555: global index partitioning key is an expression Cause: An attempt was made to use an expression as a partitioning key in an index. Action: Do not attempt to use an expression as index partitioning key. ORA-30556: functional index is defined on the column to be modified Cause: An ALTER TABLE MODIFY COLUMN was issued on a column on which a functional index exists. Action: Drop the functional index before attempting to modify the column. ORA-30557: function based index could not be properly maintained Cause: The user updated a column on which a function based index is present which was not successfully updated Action: Determine the error in updating the index and fix the problem ORA-30558: internal error [string] in function based index Cause: This is an internal error. Action: Contact Worldwide support with the exact error text. ORA-30563: outer join operator (+) not allowed in select-list Cause: An attempt was made to reference (+) in select-list. Action: Do not use the operator in select-list. ORA-30564: Index maintainence clause not allowed for ADD partition to RANGE partitioned tables Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD partition to a HASH partitioned table or ADD subpartition to a composite partitioned table. Action: Remove clause and reissue operation ORA-30565: Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES was specified more than once. Action: Remove all but one of the INVALIDATE or UPDATE GLOBAL INDEXES clause and reissue the statement ORA-30566: Index maintainence clause not allowed for this command Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is not allowed for this command Action: Remove clause and reissue operation ORA-30567: name already used by an existing log group Cause: The specified log group name has to be unique. Action: Specify a unique name for the log group. The name cannot be the same as any other log group, constraint, or cluster hash expression. ORA-30568: cannot drop log group - nonexistent log group Cause: The specified in alter table drop log group is incorrect or nonexistent. Action: Reenter the statement using the correct log group name. ORA-30569: data type of given column is not supported in a log group Cause: An attempt was made to include a column with one of these unsupported data types: LONG, VARRAY, nested table, object, LOB, FILE, or REF in a log group. Action: Change the column data type or remove the log group. Then retry the operation. ORA-30570: SEGMENT SPACE MANAGEMENT option already specified Cause: In CREATE TABLESPACE, the SEGMENT SPACE MANAGEMENT option was specified more than once. Action: Remove all but one of the SEGMENT SPACE MANAGEMENT specifications. ORA-30571: invalid SEGMENT SPACE MANAGEMENT clause Cause: An invalid option appears for SEGMENT SPACE MANAGEMENT clause. Action: Specify one of the valid options: AUTO, MANUAL. ORA-30572: AUTO segment space management not valid with DICTIONARY extent management Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used with a DICTIONARY extent management clause. Action: Either specify LOCAL extent management or remove the AUTO SEGMENT SPACE MANAGEMENT specification. ORA-30573: AUTO segment space management not valid for this type of tablespace Cause: in CREATE TABLESPACE, the AUTO SEGMENT SPACE MANAGEMENT was used while creating an UNDO or TEMPORARY tablespace. Action: Remove the AUTO SEGMENT SPACE MANAGEMENT clause. ORA-30574: Cannot create rollback segment in tablespace with AUTO segment space management Cause: A rollback segment is being created in a tablespace that was created with AUTO segment space management. Action: Create the rollback segment in a different tablespace. ORA-30575: ConText Option not installed Cause: Oracle executable doesn"t have ConText Option linked in Action: get the correct version of Oracle ORA-30576: ConText Option dictionary loading error Cause: ConText dictionary tables may be corrupted Action: not a user error ORA-30625: method dispatch on NULL SELF argument is disallowed Cause: A member method of a type is being invoked with a NULL SELF argument. Action: Change the method invocation to pass in a valid self argument. ORA-30645: reject limit out of range Cause: Reject limit specifies the number of records rejected before terminating a table scan. The range is a either a number between 1..100000 or UNLIMITED if no limit is intended. Action: Change the token representing the reject limit to either a number in the range of 0 and 100000 or the keyword UNLIMITED. ORA-30646: schema for external table type must be SYS Cause: A schema other then SYS was specified for the TYPE Action: For this version of oracle server always use schema name SYS. ORA-30647: error retrieving access parameters for external table string.string Cause: an error occurred when fetching the access parameters for the specified external table. Action: If the access parameter is a query which returns a CLOB, check EXTERNAL_TAB$ to make sure the query is correct. ORA-30649: missing DIRECTORY keyword Cause: DEFAULT DIRECTORY clause missing or incorrect. Action: Provide the DEFAULT DIRECTORY. ORA-30653: reject limit reached Cause: the reject limit has been reached. Action: Either cleanse the data, or increase the reject limit. ORA-30654: missing DEFAULT keyword Cause: DEFAULT DIRECTORY clause not specified or incorrect. Action: Provide the DEFAULT DIRECTORY. ORA-30655: cannot select FOR UPDATE from external organized table Cause: A select for update on an external table was attempted. Action: Don"t do it! ORA-30656: column type not supported on external organized table Cause: Attempt to create an external organized table with a column of type LONG, LOB, BFILE, ADT, or VARRAY. Action: These column types are not supported, change the DDL. ORA-30657: operation not supported on external organized table Cause: User attempted on operation on an external table which is not supported. Action: Don"t do that! ORA-30658: attempt was made to create a temporary table with EXTERNAL organization Cause: An attempt was made to create an External Organized Temporary table. This is not supported. Action: Don"t do that! ORA-30659: too many locations specified for external table Cause: An attempt was made to create an External Organized table with more than the maximum allowable (32767) locations specified. Action: Don"t do that, use fewer location clauses. Either consider concatenating the input files, or, creating two external tables with the input files split between them. ORA-30676: socket read or write failed Cause: A problem kept a socket from reading or writing the expected amount of data. More specific information is not available. Action: Try re-establishing a connection. You may need to restart whatever program is at the other end of the socket that failed, or you may need to have some problem on your network fixed. ORA-30677: session is already connected to a debugger Cause: An attempt to connect a session to a debugger could not proceed because the session is already connected to some debugger. Action: Either use the option to force a connection or first disconnect the session from its existing debugger. ORA-30678: too many open connections Cause: An attempt to open a connection failed because too many are already open by this session. The number of allowed connections varies as some may be in use through other components which share the same pool of allowed connections. Action: Retry after closing some other connection. The number of connections supported is currently not adjustable. ORA-30679: JDWP-based debugging not supported in this configuration Cause: An attempt to open a debugging connection failed because this server configuration cannot support the required asynchronous socket traffic detection. Action: This feature will not work under this server configuration. Either the feature is not supported on this platform at all, or is available only through use of a protocol=tcp dispatcher in shared-server configurations. Please consult the platform-specific documentation and "readme" material. ORA-30680: debugger connection handshake failed Cause: A problem occurred when trying to establish a debugger connection. This might indicate that the port specified as the location of the debugger is actually being used by some other type of application. Action: Correct the host or port specifications if they are incorrect, and verify that the debugger is properly waiting for a connection. ORA-30681: improper value for argument EXTENSIONS_CMD_SET Cause: An improper parameter value was provided in a call to DBMS_DEBUG_JDWP.CONNECT_TCP. Action: Correct the indicated parameter value and try again. ORA-30682: improper value for argument OPTION_FLAGS Cause: An improper parameter value was provided in a call to DBMS_DEBUG_JDWP.CONNECT_TCP. Action: Correct the indicated parameter value and try again. ORA-30683: failure establishing connection to debugger Cause: An error was indicated when trying to establish a connection to a debugger. Usually a TNS error will display along with this message to further explain the problem, although this TNS error will likely be hidden if you choose to trap the error. Action: Correct the indicated parameter value and try again. ORA-30685: package version is not compatible with Oracle version Cause: The installed version of the package from which this error is raised is not compatible with this release of Oracle. Action: Install a compatible version of the package"s spec and body. ORA-30686: no dispatcher accepted TCP/IP connection request Cause: A connection had to be routed through a local socket rather than a dispatcher. When this occurs, shared servers are less beneficial because the session that owns the socket cannot relinquish the process until the socket is closed. The most likely cause is that no dispatcher is configured for protocol=tcp. Action: To improve the scalability of your configuration, configure a dispatcher for protocol=tcp. To route these particular connections through a particular set of dispatchers, you can specify presentation=kgas. However, if you haven"t done so, any protocol=tcp dispatcher will be used. ORA-30687: session terminated by debugger Cause: Your program"s execution has been stopped by the debugger. This can occur because of an explicit request to do so sent by the debugger, or because the debugger disconnected without first telling Oracle to let your program continue to run after the disconnection. To stop your program completely, Oracle needs to fully terminate the process. Action: This is in response to a debugger request; it is not an error. No action required. ORA-30688: maximum program calling depth exceeded Cause: Your program contains a set of calls that are too deep to be handled. Only transitions between the different execution engines (SQL, PL/SQL, and Java) count in reaching this limit; calls within the same engine don"t count. Action: Restructure your program so as to not call so deeply. Perhaps some recursion can be replaced with iteration. ORA-30689: improper value for ORA_DEBUG_JDWP Cause: An improper value was used for ORA_DEBUG_JDWP when trying to establish a connection to a debugger. The value either did not conform to the format of ORA_DEBUG_JDWP or was too long. Action: Correct the value for ORA_DEBUG_JDWP and try again. ORA-30690: timeout occurred while registering a TCP/IP connection for data traffic detection Cause: A timeout occurred while registering a TCP/IP connection for data traffic detection. Action: Retry the operation later. ORA-30691: failed to allocate system resources while registering a TCP/IP connection for data traffic detection Cause: System resources ran out while registering a TCP/IP connection for data traffic detection. Action: Retry the operation later. ORA-30695: JDWP message format problem Cause: A message passed from one software subcomponent to another using the JDWP protocol appears invalidly formatted. Action: This is an internal error. Contact ORACLE Support Services. ORA-30725: JDWP-based debugging is not yet available Cause: This feature is not yet available for use. Action: Please wait for a future release. ORA-30726: cannot specify referenced column list here Cause: An attempt was made to specify a referenced column list for a referential constraint involving a REF column. Action: Remove the referenced column list specification. ORA-30727: duplicate referential constraint for a REF column Cause: Multiple referential constraints were specified for a single REF column. Action: Remove the duplicate referential constraint and retry the operation. ORA-30728: maximum number of columns exceeded Cause: Adding referential constraint on a REF column requires the the creation of an additional column. Action: Drop some columns and retry the operation. ORA-30729: maximum number of columns exceeded Cause: Adding scope or referential constraint on a REF column requires the creation of additional columns if the target table"s object identifier is primary key based. Action: Drop some columns and retry the operation. ORA-30730: referential constraint not allowed on nested table column Cause: An attempt was made to define a referential constraint on a nested table column. Action: Do not specify referential constraints on nested table columns. ORA-30731: scope constraint not allowed on nested table column when the nested table is being created Cause: An attempt was made to define a scope constraint on a nested table column when the nested table is being created. Action: Do not specify a scope constraint on a nested table column when creating it. Instead, specify it using the ALTER TABLE statement. ORA-30732: table contains no user-visible columns Cause: An attempt was made to query on a system table which has no user-visible columns. Action: Do not query on a system table that has no user-visible columns. ORA-30733: cannot specify rowid constraint on scoped ref column Cause: An attempt was made to specify rowid constraint on a scoped REF column. Action: Remove the rowid constraint and then retry the operation. ORA-30734: cannot specify scope constraint on ref column with rowid Cause: An attempt was made to specify scope constraint on a REF column with the rowid constraint. Action: Remove the scope constraint and then retry the operation. ORA-30735: cannot create multiple subtables of the same type under a supertable Cause: An attempt was made to create under a supertable (superview), a subtable(subview) of the same type as another existing subtable (subview). Action: Drop the existing subtable(subview) and retry the operation. ORA-30736: objects in a table or view hierarchy have to be in the same schema Cause: An attempt was made to create a subtable(subview) under a supertable(superview) located in another schema. Action: Connect as schema owner of the superobject and retry the operation. ORA-30737: cannot create subtable of a type which is not a subtype of the type of the supertable Cause: An attempt was made to create a subtable(subview) of a type which is not a subtype of the type of the super object. Action: Change the type of the subtable to be a subtype of the superobject"s type and then retry the operation. ORA-30738: object "string" does not exist in schema "string" Cause: The specified object does not exist. Action: Ensure that the specified object exists and retry the operation. ORA-30739: cannot drop a table that has subtables Cause: The user tried to drop a table that has subtables defined under it. Action: Drop all subtables before trying this operation. ORA-30740: cannot grant UNDER privilege on this object Cause: The user tried to grant UNDER privilege on an object that is not one of the following : non final object type, object table of non final type, object view of non final type. Action: Ensure that the UNDER privilege is granted on a valid object. ORA-30741: WITH HIERARCHY OPTION can be specified only for SELECT privilege Cause: The user tried to specify WITH HIERARCHY OPTION for a privilege other than SELECT privilege. Action: Ensure that the HIERARCHY OPTION is specified only with the SELECT privilege ORA-30742: cannot grant SELECT privilege WITH HIERARCHY OPTION on this object Cause: The user tried to grant SELECT privilege WITH HIERARCHY OPTION on an object that is not one of the following : object table of non final type, object view of non final type. Action: Ensure that the SELECT privilege WITH HIERARCHY OPTION is granted on a valid object. ORA-30743: "string" is not an object view Cause: The specified object is not an object view. Action: Specify an object view and retry the operation. ORA-30744: "string" is not an object table Cause: The specified object is not an object table. Action: Specify an object table and retry the operation. ORA-30745: error occured while trying to add column "string" in table "string" Cause: The user tried to add a subtype which tried to alter the tables dependent on the supertype. Action: Ensure that the table will not exceed the columnlimit on adding this subtype. ORA-30746: error occured while trying to drop column "string" in table "string" Cause: The user tried to drop a subtype with VALIDATE option which tried to check for stored instances of the type in the stated table Action: Delete all instances of this subtype and then drop the type. ORA-30747: cannot create substitutable tables or columns of non final type string.string Cause: The user tried to create substitutable table or column of a non final type. This operation is not currently supported. Action: Change the statement to create a non substitutable table/column. ORA-30748: column string already enabled to store objects of type string.string Cause: The user is trying to enable a column to store instances of a type for which it is already enabled. Action: None ORA-30749: column string not enabled to store objects of type string.string Cause: The user is trying to disable a column from storing instances of a type for which it is already enabled. Action: None ORA-30750: cannot enable column string to store objects of type string.string Cause: The user is trying to enable a column to store instances of a subtype. The error is raised due to one of the following : Action: Fix the cause of the error and retry the operation. ORA-30751: cannot disable column string from storing objects of type string.string Cause: The user is trying to drop a type from being stored in a substitutable column or table. This error is raised due to one of the following reasons : - the column is enabled to store instances of some subtype of the type being dropped. - the column is enabled to store instances of only one type Action: Fix the cause of the error and retry the operation. ORA-30752: column or table string is not substitutable Cause: The user is performing an operation that is not allowed on non substitutable column or table. Action: None. ORA-30753: column or table string is substitutable Cause: The user is performing an operation that is not allowed on substitutable column or table. Action: None. ORA-30754: column or table string stores objects of only one type Cause: The user is trying to perform an operation that is not allowed on object column or table that is enabled to store instances of a single type. Action: None ORA-30755: error during expansion of view hierarchy Cause: There was an error while trying to expand a view hierarchy. This could be due to invalid subviews (or subviews with errors) Action: Ensure that all subviews are valid e.g. alter view ... compile and retry the operation. ORA-30756: cannot create column or table of type that contains a supertype attribute Cause: The user tried to create a column or table of an object type that contains a supertype attribute. This is not supported because it leads to infinite recursion in our current storage model. Note that creating a column of a type implies that we create columns corresponding to all subtype attributes as well. Action: Change the type definition to contain a supertype REF attribute instead of the supertype object attribute. ORA-30757: cannot access type information Cause: Either a subtype was created and operations performed with this new type while the session was in progress, or the type information was unpinned from the object cache. Action: Commit necessary changes, end the user session, reconnect again and re-try the object operations. If problem persists, contact your Oracle Support representative. ORA-30765: cannot modify scope for an unscoped REF column Cause: An attempt was made to modify the scope for an unscoped REF column. Action: Use an ALTER TABLE ADD SCOPE FOR command instead. ORA-30766: cannot modify scope for a REF column with a REFERENCES constraint Cause: An attempt was made to modify the scope for a REF column with a REFERENCES constraint. Action: Drop the REFERENCES constraint, and retry the operation. ORA-30767: OID type mismatch Cause: An attempt was made to modify the scope for a REF column to a table whose object identifier"s type is different from that of the original scoped table. Action: none ORA-30768: Cannot evaluate pipelined function Cause: Pipelined functions can only be used in a TABLE expression in the from clause. Action: Use a non-pipelined function instead. ORA-30770: Cannot specify storage options for fixed size opaque type Cause: Storage clause was specified during table creation for a fixed size opaque type. Action: Do not provide storage option clause. ORA-30771: Cannot add more than one referential constraint on REF column "string" Cause: Multiple referential constraints were specified for a single REF column. Action: Remove the additional referential constraints and retry the operation. ORA-30772: opaque types do not have default constructors Cause: Constructor invocation did not succeed, since no user-defined constructors were defined for the opaque type, and since opaque types do not have default constructors. Action: Add user-defined constructors to opaque type, or specify a member or static method for the opaque type. ORA-30926: unable to get a stable set of rows in the source tables Cause: A stable set of rows could not be got because of large dml activity or a non-deterministic where clause. Action: Remove any non-deterministic where clauses and reissue the dml. ORA-30927: Unable to complete execution due to failure in temporary table transformation Cause: In memory temporary tables we create are aged out of shared pool before we are able to grab them again. Action: Reduce activities that use a lot of shared pool space or wait for a while, then retry. ORA-30928: Connect by filtering phase runs out of temp tablespace Cause: It is probably caused by the fact that there is a loop in the data. Action: Please retry the query with the NO_FILTERING hint. If the same error still occurs, then increase temp tablespace. ORA-30929: ORDER SIBLINGS BY clause not allowed here Cause: ORDER SIBLINGS BY clause is specifed in a query which doesn"t have CONNECT BY clause. Action: Remove ORDER SIBLINGS BY clause or add CONNECT BY clause. ORA-30930: NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn Cause: CONNECT_BY_ISCYCLE was specifed in a query which does not have the NOCYCLE keyword. Action: Remove CONNECT_BY_ISCYCLE or add NOCYCLE. ORA-30931: Element "string" cannot contain mixed text Cause: XML elements must be declared mixed to contain multiple text nodes Action: Declare this element type as mixed in its schema ORA-30932: Reference node "string" not contained in specified parent node "string" Cause: When using a reference node, it must have the specified parent node Action: Use a node in the specified parent as the reference ORA-30933: Element "string" may not appear at this point within parent "string" Cause: The ordering specified by the content model of the parent does not allow for this element to occur at this position. Action: Reorder the child elements to conform with the content model of the parent element ORA-30934: "string" (string node) cannot be inserted in parent "string" (string node) Cause: The schema does not allow a child node of this type to be inserted into a parent node of this type. For example, only element nodes may only be inserted into a document Action: Insert only child nodes that make sense for this node type ORA-30935: XML maxoccurs value (string) exceeded Cause: An attempt was made to insert more than maxoccurs values into a schema-based XML document. Action: Do not insert more than maxoccurs values into the document. ORA-30936: Maximum number (string) of "string" XML node elements exceeded Cause: An attempt was made to insert more than the allowed number of elements (specified by the maxoccurs facet) into an XML document. Action: Do not attempt to add more than the maximum number of elements to XML documents. ORA-30937: No schema definition for "string" (namespace "string") in parent "string" Cause: The schema definition for the parent node being processed does not allow for the specified child node in its content model. Note that any typecasting via xsi:type must occur before the schema definitions for the new type can be used. Action: Only insert elements and attributes declared in the schema. Check to make sure that xsi:type (if used) is specified first. ORA-30938: No prefix defined for namespace "string" (particle string) Cause: An XML namespace mapping (xmlns:=) must be defined for each particle (element or attribute) stored in an schema-constrained XMLType document. Action: Add an xmlns attribute definition (attribute name="xmlns:prefix" and value="namespace URL") to the current XMLType document. The safest place to add this attribute is in the root node of the document to ensure that the mapping will be in scope. ORA-30939: Order violation: Element "string" may not follow element "string" Cause: The XML schema specifies a content model that is sequential, where the order of nodes in the instance must follow the order specified by the schema, and this instance relies on the schema validity to avoid maintaining instance order information Action: Insert elements only in the order specified in the schema ORA-30940: Cannot resolve prefix "string" for QName node "string" Cause: An attempt was made to store a QName value without having a valid namespace in scope for that prefix. Action: Declare the namespace for the prefix used ORA-30941: Cannot specify empty URI for non-default namespace "string" Cause: An attempt was made to insert a namespace declaration for a non-default namespace using an empty URI string. Action: Specify a non-empty URI for namespace declarations other than the default namespace. ////// Errors 30942 to 30950 reserved for XML Schema Evolution ORA-30942: XML Schema Evolution error for schema "string" table string column "string" Cause: The given XMLType table/column which conforms to the given schema had errors during evolution. For more information, see the more specific error below this one Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action ORA-30943: XML Schema "string" is dependent on XML schema "string" Cause: Not all dependent schemas were specified and/or the schemas were not specified in dependency order, i.e., if schema S1 is dependent on schema S, S must appear before S1. Action: Include the previously unspecified schema in the list of schemas and/or correct the order in which the schemas are specified. Then retry the operation. ORA-30944: Error during rollback for XML schema "string" table string column "string" Cause: The given XMLType table/column which conforms to the given schema had errors during a rollback of XML schema evolution. For more information, see the more specific error below this one Action: Based on the schema, table and column information in this error and the more specific error below, take corrective action ORA-30945: Could not create mapping table "string" Cause: A mapping table could not be created during XML schema evolution. For more information, see the more specific error below this one Action: Ensure that a table with the given name does not exist and retry the operation ORA-30946: XML Schema Evolution warning: temporary tables not cleaned up Cause: An error occurred after the schema was evolved while cleaning up temporary tables. The schema evolution was successful Action: If the user needs to remove the temporary tables, use the mapping table to get the temporary table names and drop them. ///// End of XML Schema Evolution errors (30942 to 30950 reserved) ORA-30951: Element or attribute at Xpath string exceeds maximum length Cause: An attempt was made to insert a node of length exceeding the maximum length (specified by the maxLength facet) into an XML document. Action: Do not attempt to add a node exceeding the maximum length to XML documents. ORA-30952: illegal configuration of HTTP/HTTPS in xdbconfig.xml Cause: An attempt was made to update xdbconfig.xml when either 1) a value was specified for http2-port but not for http2-protocol (or vice versa), OR 2) http-port and http2-port were set to the same value. Action: Specify values for both elements http2-port and http2-protocol, AND set different values for http-port and http2-port. ORA-30953: XML minoccurs value (string) violated Cause: An attempt was made to delete more than the required minimum number of elements (specified by the minoccurs facet) from an XML document. Action: Do not attempt to delete more than the required minimum number of elements that must be present from the XML document. ////// Errors 30955 to 30989 reserved for XML Index ORA-30956: invalid option for XML Index Cause: Unexpected error. Action: File a bug. ORA-30957: cannot downgrade because there are XML indexes Cause: An attempt was made to downgrade a database that has XML indexes. Action: Drop all XML indexes before attempting the downgrade. ORA-30959: The indexed column is not stored in CLOB. Cause: An attempt was made to create an XML Index on an OR-XMLType column. Action: Re-create the XML Index on a CLOB-XMLType column. ORA-30960: The entity is neither an XPATH nor a NAMESPACE. Cause: The given string had invalid syntax. Action: Check the syntax for XPATH and NAMESPACE. ORA-30961: internal SQL statement is too long Cause: unexpected internal error Action: File a bug and provide the test case. ORA-30962: inconsistent ODCI input arguments Cause: unexpected internal error Action: File a bug and provide the test case. ORA-30963: The indexed column is not of XMLType. Cause: An attempt was made to create an XML Index on a non-XMLType column. Action: Re-create the XML Index on an XMLType column. ORA-30964: The XML Index was not usable. Cause: The domain index for XML was not created properly. The Path Table is missing. Action: Drop and re-create the XML Index. ORA-30965: fragment does not fit into the VARCHAR2 VALUE column Cause: The fragment size exceeded the max size. Action: Re-create the XML Index with values stored in CLOB. ORA-30966: error detected in the XML Index layer Cause: Unexpected error. Action: File a bug. ORA-30967: operation directly on the Path Table is disallowed Cause: illegal operation on secondary objects of a domain index Action: Try appropriate operation on the domain index. ORA-30968: invalid XPATH or NAMESPACE option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30969: invalid syntax for PARAMETERS Cause: An attempt was made to specify an invalid option. Action: Check and use valid options. ORA-30970: option not supported for XML Index Cause: An attempt was made to specify an invalid option. Action: Check and use valid options. ORA-30971: illegal operation on the Path Table Cause: An attempt was made to use an unsupported option. Action: Use the appropriate command on the XML Index. ORA-30972: invalid ALTER INDEX option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30973: invalid Path Table option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30974: invalid Path Id Index option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30975: invalid Order Key Index option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30976: invalid Parent Order Key Index option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30977: invalid Value Index option for XML Index Cause: An attempt was made to use an unsupported option. Action: Use the appropriate option. ORA-30978: The XML Index is not locally partitioned. Cause: An attempt was made to create a global partitioned XML Index. Action: Do not attempt to create global partitioned XML Index or to maintain a non-local partitioned XML Index. ORA-30979: Partitioned XML Index not yet supported. Cause: An attempt was made to create a partitioned XML Index. Action: Do not attempt to create partitioned XML Index. ORA-30980: Invalid Input. Cause: The input to the function is not valid. Action: Make sure the input is valid (both syntactically as well as semantically). ///// End of XML Index (30955 to 30989 reserved) ORA-30990: insufficient privileges to change owner of resource string Cause: An attempt was made to change the field of an XML DB resource without sufficient privileges to do so. Action: Switch to SYS before performing the ownership change, or have the intended recipient of the resource perform the transfer. ORA-30991: cannot use DOM to add special attribute to schema-based parent Cause: An attempt was made to add or remove an xsi:schemaLocation, xsi:noNamespaceSchemaLocation, xsi:type, or xsi:nil attribute to or from a schema-based XML node using DOM. Action: Use the updateXML operator instead of DOM. ORA-31000: Resource "string" is not an XDB schema document Cause: The given schema URL does not refer to a registered XDB schema Action: Make sure the specified schema has been registered in XDB ORA-31001: Invalid resource handle or path name "string" Cause: An invalid resource handle or path name was passed to the XDB hierarchical resolver. Action: Pass a valid resouce handle or path name to the hierarchical resolver. ORA-31002: Path name string is not a container Cause: XDB expected the given path name to represent a container. Action: Pass a path name or resource handle that represents a container. ORA-31003: Parent string already contains child entry string Cause: An attempt was made to insert a duplicate child into the XDB hierarchical resolver. Action: Insert a unique name into the container. ORA-31004: Length string of the BLOB in XDB$H_INDEX is below the minimum string Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum. Action: Set the value of the init.ora parameter db_block_size to at least 2K. For XDB to run at its fastest, set db_block_size to 8K. ORA-31005: Path name length string exceeds maximum length string Cause: The length of a path name passed to the XDB hierarchical resolver exceeded the maximum length. Action: Choose a shorter path name. ORA-31006: Path name segment length string exceeds maximum length string Cause: The length of a path name segment passed to the XDB hierarchical resolver exceeded the maximum length of a path name segment. Action: Choose a shorter path name segment. ORA-31007: Attempted to delete non-empty container string/string Cause: An attempt was made to delete a non-empty container in the XDB hierarchical resolver. Action: Either perform a recursive deletion, or first delete the contents of the container. ORA-31009: Access denied for property string Cause: An attempt was made to access a property you don"t have access to Action: Check the ACL to see what privileges you have for this property ORA-31010: XML element index string exceeds maximum insertion index string Cause: An attempt was made to insert an XML element at an invalid index location in the node. Action: Choose a new index that falls within the allowed range. ORA-31011: XML parsing failed Cause: XML parser returned an error while trying to parse the document. Action: Check if the document to be parsed is valid. ORA-31012: Given XPATH expression not supported Cause: XPATH expression passed to the function is currently unsupported. Action: Check the xpath expression and change it to use a supported expression. ORA-31013: Invalid XPATH expression Cause: XPATH expression passed to the function is invalid. Action: Check the xpath expression for possible syntax errors. ORA-31014: Attempted to delete the root container Cause: An attempt was made to delete the root container in the hierarchical index. Action: Do not delete the root container. ORA-31015: Attempted to insert entry without name Cause: An attempt was made to insert an entry into the hierarchical resolver without a child name. Action: Supply a child name and try inserting again. ORA-31016: Attempted to delete entry without name Cause: An attempt was made to delete an entry from the hierarchical resolver without a child name. Action: Supply a child name and try deleting again. ORA-31017: Error generating unique OID for XML document Cause: An error occurred while generating a globally unique OID for storing an XML document. Action: none ORA-31018: Error deleting XML document Cause: The XMLType object pointed to by the given REF could not be deleted because either the REF was invalid or it pointed to a non-existent table. Action: Either use FORCE deletion or supply a valid REF. ORA-31019: Recursive deletion snapshot too old for string/string Cause: Changes were made to the structure of a directory while it was being recursively deleted. Action: Try deleting the directory again. ORA-31020: The operation is not allowed, Reason: string Cause: The operation attempted is not allowed Action: See reason and change to a valid operation. ORA-31021: Element definition not found Cause: The element definition was not found. Action: Supply the definition for the element or use a defined element. ORA-31022: Element not found Cause: The element was not found. Action: Make sure the specified element exists. ORA-31023: Index size error Cause: The index is greater than the allowed value. Action: Make sure the index is less than allowed value. ORA-31025: Invalid document element Cause: An attempt was made to replace the data at an invalid index number in the XML document Action: Supply a correct occurrence number and try again. ORA-31027: Path name or handle string does not point to a resource Cause: An attempt was made to retrieve a resource based on a path name or resource handle that points to an entity other than a resource. Action: Do not attempt to retrieve a resource based on that path name or resource handle. ORA-31028: Resource metadata length string exceeded maximum length string Cause: An attempt was made to insert resource metadata that exceeded the maximum length of that type of metadata. Action: Keep resource metadata within its allowed length. ORA-31029: Cannot bind to unsaved resource Cause: An attempt was made to bind to a resource that had not been saved to disk. Action: Bind only to saved resources. ORA-31030: Unable to retrieve XML document Cause: The resource had an invalid (dangling) REF to an XML document. Action: Rebind the resource using a valid XMLType REF. ORA-31033: Requested number of XML children string exceeds maximum string Cause: An attempt was made to add more than the maximum number of allowable children in an XML element. Action: Redefine the schema to allow breaking up of the children among siblings. ORA-31035: Could not bind locked resource to path string/string Cause: An attempt was made to bind an existing resource to a new location in the hierarchy, but a lock could not be obtained on the resource. Action: Commit or roll back the transaction that has the lock on the resource. ORA-31037: Invalid XML attribute name string Cause: The attribute name in the XML document did not match anything in the associated schema. Action: Supply only schema-defined or XML standard attributes. ORA-31038: Invalid string value: "string" Cause: The text in the XML document did not represent a valid value given the datatype and other constraints in the schema. Action: Ensure that the specified value in XML documents is valid with respect to the datatype and other constraints in the schema. ORA-31039: XML namespace length string exceeds maximum string Cause: The length of the disk-formatted XML namespace exceeded the maximum. Action: Keep XML namespace declarations below the maximum length. ORA-31040: Property string: XML type (string) not compatible with internal memory type (string) Cause: The XML datatype given is inconsistent with the database datatype, and a conversion cannot be made. Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas, or contact Oracle support. ORA-31041: Property string: Memory type (string) not compatible with database type (string) Cause: The memory type associated with this property is mapped to an incompatible database type, and a conversion cannot be made. Action: This is an internal error, generally resulting from corruption of the compiled XML schema. Re-register schemas, or contact Oracle support. ORA-31042: Too many properties in type "string" Cause: The type can only have the same number of properties (elements and attributes) as a table can have columns. Action: Modify the XML schema to move properties into subelements that are not inlined. ORA-31043: Element "string" not globally defined in schema "string" Cause: The specified element name has not been defined at the top level of the XML schema (i.e. globally). Elements must be defined globally to be the root of an XMLType object. Action: Check the XML schema definition to make sure the specified element name has been defined at the top level. ORA-31044: Top-level prefix length string exceeds maximum string Cause: An attempt was made to save to disk a top-level XML namespace prefix whose length exceeded the maximum. Action: Do not define XML namespace prefixes that exceed the maximum length. ORA-31045: Cannot store more than string extras outside the root XML node Cause: An attempt was made to store more than the maximum number of XML extras (e.g. comments and processing instructions) either before or after the document"s root node. Action: Keep the number of extras outside the root node below the maximum. ORA-31046: Incorrect argument(s) specified in the operator Cause: One or more of the arguments specified in the operator in the query are incorrect Action: Correct the arguments specified in the operator ORA-31047: Could not retrieve resource data at path string Cause: An error occurred while retrieving the contents and/or metadata of a resource. Action: Contact Oracle customer support. ORA-31048: Unsaved resources cannot be updated Cause: An attempt was made to update a resource that was never saved to disk. Action: Perform a resource insertion instead. ORA-31050: Access denied Cause: The requested access privileges have not been granted to the current user. User must be granted privileges prior to resource access. Action: Check the set of requested access privileges to make sure that they are included in the set of access privilges granted to the user. ORA-31051: Requested access privileges not supported Cause: The requested access privileges are not supported for the specified resource. Action: Ensure that the set of requested access privileges are valid access privileges for the specified resource. ORA-31052: Cannot delete ACL with other references Cause: The requested deletion of an ACL resource cannot proceed. The ACL is in use by other resources. Action: Remove the resources that are making reference to the ACL in question and try again. ORA-31053: The value of the depth argument in the operator cannot be negative Cause: The value of the depth argument passed to the primary operator is not a positive integer Action: Pass a positive value of the depth argument ORA-31054: The string operator cannot have an ancillary operator Cause: An ancillary operator was used with an operator which does not does not support ancillary operators Action: Remove the ancillary operator in the query ORA-31055: A null XMLType element cannot be inserted into RESOURCE_VIEW Cause: The element which is being inserted into the RESOURCE_VIEW is NULL Action: Specify a non-null XMLType element to insert into RESOURCE_VIEW ORA-31056: The document being inserted does not conform to string Cause: The XMLType element being inserted into the RESOURCE_VIEW does not conform to the specified Schema Action: Insert an element which conforms to the specified Schema ORA-31057: Display Name of the element being inserted is null Cause: The Display Name of the element which is being inserted into the RESOURCE_VIEW is null Action: Specify the Display Name and insert the element into RESOURCE_VIEW ORA-31058: cannot modify read-only XOBs Cause: Read-Only XOBs cannot be modified. Action: Use only read operations on such a XOB. ORA-31059: Cannot insert root XML document node if it already exists Cause: An attempt was made to insert a root node into an XML document that already had a root node. Action: Call the appropriate replace function to replace the node instead of inserting it anew. ORA-31060: Resource at path string could not be deleted Cause: An error occurred while deleting the named resource. The specific error can be found one lower on the error stack. Action: Look at the next error on the stack and take approprate action. ORA-31062: Cannot delete an unsaved resource Cause: An attempt was made to delete a resource that had not been saved to disk. Action: Delete only saved resources. ORA-31064: Cannot instantiate abstract element or property [string] Cause: An attempt was made instantiate an abstract element. Action: Use only read operations on such elements. ORA-31065: Cannot modify read-only property [string] Cause: An attempt was made to modify an immutable XML node. Action: Use only read operations on such properties. ORA-31066: Insertion of string into string creates a cycle Cause: An attempt was made to insert a link into the XDB hierarchy that would create a cycle in the tree. Action: Ensure that links to existing resources do not cause cycles. ORA-31067: XML nodes must be updated with valid nodes and of the same type Cause: An attempt was made to use updateXML to update an XML node with a node of another type. Action: Ensure that the node specified by the XPath matches the type of new data provided. ORA-31068: updateXML expected data format [string] instead of [string] Cause: An attempt was made to use updateXML to update data with a node of the incorrect type. Text and attribute nodes must be updated with string data, whereas element nodes must be updated with XMLType data. Action: Use CREATEXML or getStringVal to coerce the new data to the proper format. ORA-31069: Cannot apply typed changes to non-schema-based XMLType nodes Cause: An attempt was made to insert, delete, or update a non-schema-based XMLType node using an XML schema definition. Action: Make changes to non-typed nodes only by referencing their tag names. ORA-31070: Invalid database user ID string Cause: An attempt was made set an invalid user ID into an XDB resource metadata property. Action: Verify the validity of the user ID and try again. ORA-31071: Invalid database username or GUID string Cause: An attempt was made to set an invalid username or GUID into an XDB resource metadata property. Action: Verify the validity of the username or GUID and try again. ORA-31072: Too many child nodes in XMLType fragment for updateXML Cause: An attempt was made to pass an XMLType fragment with multiple children as new data for the updateXML operator. Action: Extract the desired child from the XMLType before passing it to updateXML as the desired new XML node. ORA-31073: Resource not retrieved using path name Cause: An attempt was made to access the path name of a resource that was either never saved to disk or was loaded using a method other than with its path name. Action: Perform path name operations only on resources obtained using a path name. ORA-31074: XML comment length string exceeds maximum string Cause: The length of the disk-formatted XML comment exceeded the maximum. Action: Keep outer XML comments declarations below the maximum length. ////// 31075 - 31099 reserved for XML Schema Compiler ORA-31075: invalid string declaration in XML Schema Cause: The XML schema contains an invalid declaration identified by the message. Action: Fix the identified error and try again. ORA-31076: required attribute "string" not specified Cause: The XML schema does not specify a required attribute. Action: Specify a value for the required attribute. ORA-31077: invalid attribute "string" specified Cause: The XML schema specifies an invalid attribute. Action: Remove specification of the invalid attribute. ORA-31078: error in SQL mapping information Cause: There is an error in the SQL type and table specification within the XML Schema. Action: Ensure that all specified SQL types and tables are valid and compatible with the corresponding XML types. ORA-31079: unable to resolve reference to string "string" Cause: The identified type or attribute or element could not be resolved. Action: Make sure that the name corresponds to a valid XML (simple/complex) type or attribute or element and try again. ORA-31080: type not specified for attribute or element "string" Cause: The identified attribute or element does not have a type. Action: Make sure that every attribute and element has a valid type specification. ORA-31081: name not specified for global declaration Cause: The XML schema does not specify the name for the global declaration of attribute or element or simpleType or complexType. Action: Specify names for all global declarations. ORA-31082: invalid attribute "string" specified in declaration of "string" Cause: The XML schema specifies an invalid attribute. Action: Remove specification of the invalid attribute. ORA-31083: error while creating SQL type "string"."string" Cause: An error occurred while trying to create the SQL type based on the specification of a complex type. Action: Fix the identified error and try again. ORA-31084: error while creating table "string"."string" for element "string" Cause: An error occurred while trying to create the table based on the declaration for the identified element. Action: Fix the identified error and try again. ORA-31085: schema "string" already registered Cause: An attempt was made to register a schema with the same URL as a previously registered schema. Action: Register the schema with a different URL. ORA-31086: insufficient privileges to register schema "string" Cause: An attempt was made to register a schema without sufficient privileges. Action: Make sure that the user has sufficient privileges to register the schema. ORA-31087: insufficient privileges to delete schema "string" Cause: An attempt was made to delete a schema resource without sufficient privileges. Action: Make sure that the user has sufficient privileges to delete the schema. ORA-31088: object "string"."string" depends on the schema Cause: An attempt was made to delete a schema which has dependent objects. Action: Either drop the dependent objects prior to deleting the schema or use the CASCADE or FORCE options. ORA-31089: schema "string" does not target namespace "string" Cause: The schema document contains references (via include and import definitions) to other schemas that do not belong to valid namespaces. Action: Make sure that all schemas referenced via include definitions target the same namespace as the parent schema. Further make sure that the namespace specified in the import definition matches the actual target namespace of the specified schema. ORA-31090: invalid database schema name "string" Cause: The XML schema document contains an invalid database schema name For example, the value of attribute SQLSchema Action: Make sure that all database user/schema names specified in the XML schema document refer to existing database users/schemas. ORA-31091: empty string specified as a SQL name Cause: The XML schema document contains a null SQL name. For example, the values of attributes SQLName, SQLType, defaultTable. Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. Otherwise, remove such attributes from the schema and try again. ORA-31092: invalid SQL name "string" Cause: The XML schema document contains an invalid SQL name. For example, the values of attributes SQLName, SQLType, defaultTable. Action: Make sure that all names of SQL schema objects specified in the XML schema document are valid SQL names. This implies that the database length and other restrictions on names be satisfied. ORA-31093: null or invalid value specified for parameter : string Cause: The argument value passed for the given parameter is null or invalid. Action: Make sure that all the input argument values are valid. ORA-31094: incompatible SQL type "string" for attribute or element "string" Cause: The SQL type information provided in the XML schema is not compatible with the XML datatype for the specified attribute or element. Action: Make sure that the specified SQL types are compatible with the declared XML datatypes. ORA-31095: cannot generate string : "string.string" already exists Cause: The type/table name specified in the XML schema document cannot be generated because it is already being used. Action: Use different names for types/tables or use the NOGEN mode so that schema compiler does not generate new types/tables. ORA-31096: validation failed for schema Cause: The XML Schema could not be validated. Action: Make sure that the SQLType and other datatype mapping is valid. ORA-31097: Hierarchical Index not empty Cause: An attempt was made to rebuild the hierarchical index which is not empty. Action: Delete all rows in the hierarchical index and then rebuild it. ORA-31099: XDB Security Internal Error Cause: An XDB Security internal error has occurred. Action: Contact Oracle Support. ////// 31100 - 31110 reserved for WebDAV compliant resource locks ORA-31100: XDB Locking Internal Error Cause: An XDB Locking Internal error has occurred. Action: Contact Oracle Support. ORA-31101: Token "string" not given while locking resource "string" Cause: Locking attempted on resource when the pricipal already owns a lock given by the token above. Action: Reattempt the lock with the token. ORA-31102: Already locked in exclusive mode. Cannot add lock. Cause: The resource is already locked in exclusive mode. Cannot add another lock. Action: Unlock the existing lock. ORA-31103: Resource locked in shared mode. Cannot add exclusive lock Cause: The resource is locked in shared mode. Cannot add a shared lock. Action: Try locking in shared mode or unlocking the existing lock. ORA-31104: Cannot find lock with token "string" on "string" for unlock Cause: The lock may have been unlock or it may have expired. Action: No action needed. Unlock already successful. ORA-31105: User does not own lock "string" Cause: The lock to be unlocked is not owned by the user. Action: none ORA-31107: Action failed as resource "string" is locked by name lock Cause: Lock requests cause the whole request URI to be locked Action: Supply lock token or unlock the lock ORA-31108: Action failed as resource string is locked Cause: Delete/Rename failed because of an existing lock Action: Do lockdiscovery to find the lock and delete it. ORA-31109: Action failed as parent resource string is locked Cause: Delete/Rename failed because of an lock on parent resource Action: Do lockdiscovery to find the lock and delete it. ORA-31110: Action failed as resource string is locked by name Cause: Delete/Rename failed because one of the children is locked. Action: Do lockdiscovery to find the lock and delete it. ORA-31111: table string cannot be hierarchically enabled Cause: Trigger _xdb_pitrigger already exists Action: Delete all rows in the hierarchical index and then rebuild it. ORA-31112: fail to string for string port using xdb configuration Cause: port number for the defined presentation is not valid Action: Either the port number is already in use or it is protected. Specify another port number. ORA-31113: XDB configuration may not be updated with non-schema compliant data Cause: An attempt was made to update the XDB configuration resource with non-schema or non-schema compliant data. Action: Check the document to make sure it is schema based and schema compliant. ORA-31114: XDB configuration has been deleted or is corrupted Cause: The XDB configuration resource has been deleted or corrupted. Action: Reinstall XDB, or reinsert a valid configuration document. ORA-31115: XDB configuration error: string Cause: An error related to XDB configuration has occurred. Action: Make sure the configuration resource contains valid data. ORA-31116: Tablespace not specified correctly Cause: XDB cannot be moved to the specified tablespace. Action: Specify a valid tablespace. ORA-31117: Table "string"."string" is not resource metadata enabled Cause: This table does not have a RESID column for resource metadata Action: Use disable/enable_hierarchy to enable resource metadata ORA-31121: The string operator can not be FALSE Cause: The value of the operator that is specified is FALSE Action: Specify an operator that evaluates to TRUE ORA-31122: The string operator has incorrect RHS value Cause: The right hand side value that has been specified for the operator does not evaluate to TRUE Action: Specify value on the right hand side that evaluate to TRUE ////// 31151 - 31189 reserved for XML Schema Compiler ORA-31151: Cyclic definition encountered for string: "string" Cause: The schema definition for this type has cycles. Action: Remove cyclic definition and re-compile schema. ORA-31153: Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/" Cause: This prefix is reserved for XDB extended schema URLs and cannot be used in a user specified URL. Action: Modify the prefix to a different one. ORA-31154: invalid XML document Cause: The XML document is invalid with respect to its XML Schema. Action: Fix the errors identified and try again. ORA-31155: attribute string not in XDB namespace Cause: The specified attribute should be prefixed with XDB"s namespace. Action: Ensure that all XDB specified attributes are prefixed with XDB"s namespace and try again. ORA-31157: Invalid Content-Type charset Cause: HTTP Content-Type header had a charset that Oracle does not understand. Action: Fix the Content-Type header in the HTTP request. ORA-31158: schema "string" currently being referenced Cause: The specified schema URL is currently being referenced by the same session. This could happen because of PLSQL XMLType variables still in scope. Action: Ensure all references to this schema in this session are released and try the operation again. ORA-31159: XML DB is in an invalid state Cause: XML DB"s internal tables are in an invalid state, probably because the database was not upgraded or the upgrade was not successful Action: Ensure that the database is upgraded successfully. If the problem persists, contact Oracle Support ORA-31160: max substitution group size string exceeded by "string" (string) for head element "string" (string) Cause: The maximum limit on nested substitution groups has been exceeded by an element. Action: Delete specified schema and re-register it after removing the offending substitution element. ORA-31161: element or attribute "string" cannot be stored out of line Cause: An element or attribute of a simple type has SQLInline=false Action: Remove the SQLInline=false qualification for the offending element or attribute ORA-31162: element or attribute "string" has no SQLType specified Cause: Schema registration was invoked with GENTYPES=false without specifying a SQLType for some element or attribute Action: Specify a SQLType for the offending element or attribute and register the schema again ORA-31163: element or attribute "string" has invalid attribute value "string" (should be "string") Cause: An element or attribute for a complextype derived by restriction has an attribute whose value is different from that in the base type Action: Remove the mismatched attribute values from the offending element or attribute ORA-31164: cannot load object-relational XML attribute using direct path Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column contains a type with subtypes. This type of attribute cannot be loaded with direct path. Action: Perform the load with conventional path mode. ORA-31165: cannot load object-relational XML attribute using direct path Cause: The table being loaded contains a xml column with object-relational storage. The xmltype column either contains an out-of-line partitioned table or the table itself is partitioned by one of the attributes of xmltype. This type of table cannot be loaded with direct path. Action: Perform the load with conventional path mode. ORA-31167: XML nodes over 64K in size cannot be inserted Cause: An attempt was made to insert an XML Text Node with a size greater than 64K. This is not supported. Action: Create text nodes under 64K. ORA-31168: Node localname and namespace values should be less than 64K Cause: An attempt was made to specify an XML Node with localname or namespace value greater than or equal to 64K. This is not supported. Action: Node localnames and namespace values should be under 64K. ORA-31180: DOM Type mismatch in invalid PL/SQL DOM handle Cause: The specified PL/SQL DOM handle is referencing a DOM Node whose DOM Type that does not match the one available in the session. This could happen because the pl/sql handle was reused, or the original document is no longer available. Action: Ensure that the pl/sql handle for the target node is valid and try the operation again. ORA-31181: PL/SQL DOM handle accesses node that is no longer available Cause: The specified pl/sql handle is referencing a node in a DOM Document that is no longer available. Action: Ensure that the pl/sql handle for the target node is valid and try the operation again. ORA-31182: Too many PL/SQL DOM handles specified Cause: An attempt was made to create a PL/SQL DOM handle that exceeded the maximum allowable number of PL/SQL DOM handles. Action: Free PL/SQL DOM handles and try the operation again. ORA-31183: Node type string cannot be converted to desired type Cause: The given node"s type cannot be converted correctly for this operation. For example, a DOM Element cannot be converted to Document Fragment Action: Pass a valid node type for the conversion. ORA-31185: DOM Nodes do not belong to the same DOM Document Cause: The specified PL/SQL DOM Node does not belong to the parent DOM Document of the referring DOM Node. Action: Ensure that both the DOM Nodes are part of the same DOM Document. ORA-31186: Document contains too many nodes Cause: Unable to load the document because it has exceeded the maximum allocated number of DOM nodes. Action: Reduces the size of the document. ORA-31187: Cannot Add Node "string" (type="string") to Simple Type Node "string" Cause: Trying to add attribute/element nodes to a simple type against the schema definition. Simple types can have only special attribute like namespaces, xsi:nil etc. Action: Use a valid node for the operation. ORA-31190: Resource string is not a version-controlled resource Cause: Either one of the following is the cause: - Checkout is requested for a resource that isn"t under version control". Only version-controlled resource can be checked out. - Checkout is requested for a row of a non-versioned table. Action: put the resource under version-control before checking out. ORA-31191: Resource string is already checked out Cause: Either one of the following is the cause: - Checkout is requested for a resource that is already checked out to the workspace by the same of different user. Action: checked in the resource from the workspace before checking out ORA-31192: Resource string has not been checked out Cause: Either one of the following is the cause: - Checkin or uncheckout is requested for a resource that has not been checked out to the workspace by any user in a workspace Action: checked in the resource from the workspace before checking out ORA-31193: This versioning feature isn"t supported for resource string Cause: Either one of the following is the cause: - Container cannot be put under version-controlled. Action: Avoid using these features. ORA-31194: Resource string is already deleted Cause: Access a version-controlled resource that is already deleted. Action: Remove the cyclic definitions in the type and retry compilation. ORA-31195: XML node "string" (type=string) does not support this operation Cause: The given node"s type is not supported for this operation. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations. Action: Use a valid node type for the operation. ORA-31196: XML nodes over string in size cannot be printed Cause: An attempt was made to use an XML Text Node with a size greater than 64K, or an XML Comment Node with a size greater than 4K. These cannot be printed. For example, trying to add children to an attribute node, or passing in a document node as a child, are unsupported operations. Action: Use getClobVal() or getStringVal() to print the Document. ORA-31197: Error in processing file string Cause: An error occurred while operating on the specifed file. The possible causes are the file header is corrupt or check the next error on stack Action: Ensure that the specified file is correct. Look at the next error on the stack and take appropriate action. ORA-31198: Mismatch in number of bytes transferred due to non-binary mode Cause: An error occurred while reading the specifed file. The most probable cause is that the transfer was initiated in ASCII mode. Action: Ensure that the transfer mode is set to BINARY ORA-31199: Warning in processing file string Cause: A warning was raised while operating on the specifed file. However, the current operation was completed successfully. Action: This is primarily an informational message. Look at the next error on the stack to obtain further information. ////////////////////////// DBMS_LDAP & OiD messages ORA-31201: DBMS_LDAP: generic error: string Cause: There has been an error in the DBMS_LDAP package. Action: Please report the error number and description to Oracle Support. ORA-31202: DBMS_LDAP: LDAP client/server error: string Cause: There is a problem either on the LDAP server or on the client. Action: Please report this error to the LDAP server administrator or your Database administrator. ORA-31203: DBMS_LDAP: PL/SQL - Init Failed. Cause: There has been an error in the DBMS_LDAP Init operation. Action: Please check the host name and port number, or report the error number and description to Oracle Support. ORA-31204: DBMS_LDAP: PL/SQL - Invalid LDAP Session. Cause: There has been an error in the DBMS_LDAP bind operation. Action: Please check the session handler that you use for binding, or report the error number and description to Oracle Support. ORA-31205: DBMS_LDAP: PL/SQL - Invalid LDAP Auth method. Cause: There has been an error in the DBMS_LDAP bind operation. Action: Please check the authentication credentials that you use for binding, or report the error number and description to Oracle Support. ORA-31206: DBMS_LDAP: PL/SQL - Invalid LDAP search scope. Cause: There has been an error in the DBMS_LDAP search operation. Action: Please check the search scope that you use for search, or report the error number and description to Oracle Support. ORA-31207: DBMS_LDAP: PL/SQL - Invalid LDAP search time value. Cause: There has been an error in the DBMS_LDAP search operation. Action: Please check the search time value that you use for search, or report the error number and description to Oracle Support. ORA-31208: DBMS_LDAP: PL/SQL - Invalid LDAP Message. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the LDAP message that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31209: DBMS_LDAP: PL/SQL - LDAP count_entry error. Cause: There has been an error in the DBMS_LDAP count_entry operation. Action: Please check the LDAP count_operation, or report the error number and description to Oracle Support. ORA-31210: DBMS_LDAP: PL/SQL - LDAP get_dn error. Cause: There has been an error in the DBMS_LDAP get_dn operation. Action: Please check the LDAP get_dn, or report the error number and description to Oracle Support. ORA-31211: DBMS_LDAP: PL/SQL - Invalid LDAP entry dn. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the entry dn that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31212: DBMS_LDAP: PL/SQL - Invalid LDAP mod_array. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the LDAP mod_array that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31213: DBMS_LDAP: PL/SQL - Invalid LDAP mod option. Cause: There has been an error in the DBMS_LDAP populate_mod_array operation. Action: Please check the LDAP mod option that you use for LDAP populate_mod_array operation, or report the error number and description to Oracle Support. ORA-31214: DBMS_LDAP: PL/SQL - Invalid LDAP mod type. Cause: There has been an error in the DBMS_LDAP populate_mod_array operation. Action: Please check the LDAP mod type that you use for LDAP populate_mod_array operation, or report the error number and description to Oracle Support. ORA-31215: DBMS_LDAP: PL/SQL - Invalid LDAP mod value. Cause: There has been an error in the DBMS_LDAP populate_mod_array operation. Action: Please check the LDAP mod value that you use for LDAP populate_mod_array operation, or report the error number and description to Oracle Support. ORA-31216: DBMS_LDAP: PL/SQL - Invalid LDAP rdn. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the LDAP rdn value that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31217: DBMS_LDAP: PL/SQL - Invalid LDAP newparent. Cause: There has been an error in the DBMS_LDAP rename_s operation. Action: Please check the LDAP newparent value that you use for LDAP rename_s operation, or report the error number and description to Oracle Support. ORA-31218: DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn. Cause: There has been an error in the DBMS_LDAP rename_s operation. Action: Please check the LDAP deleteoldrdn value that you use for LDAP rename_s operation, or report the error number and description to Oracle Support. ORA-31219: DBMS_LDAP: PL/SQL - Invalid LDAP notypes. Cause: There has been an error in the DBMS_LDAP explode_dn or explode_rdn operation. Action: Please check the LDAP notypes value that you use for LDAP explode_dn or explode_rdn operation, or report the error number and description to Oracle Support. ORA-31220: DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet location. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the LDAP sslwrl value that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31221: DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the LDAP sslpasswd value that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31222: DBMS_LDAP: PL/SQL - Invalid LDAP SSL authentication mode. Cause: There has been an error in the DBMS_LDAP operation. Action: Please check the LDAP sslauth value that you use for LDAP operation, or report the error number and description to Oracle Support. ORA-31223: DBMS_LDAP: cannot open more than string LDAP server connections Cause: An attempt was made to open more than the maximum allowed LDAP server connections. Action: Free unused connections. ORA-31224: DBMS_LDAP: invalid LDAP session Cause: An attempt was made by a PL/SQL module to use an LDAP session which is not valid and might have already been closed. Action: Check the LDAP session handle in PL/SQL module involving DBMS_LDAP. ORA-31225: DBMS_LDAP: invalid BER_ELEMENT Cause: An attempt was made by a PL/SQL module to use a BER_ELEMENT which is not valid and might have already been freed. Action: Check the BER_ELEMENT in PL/SQL module involving DBMS_LDAP. ORA-31226: DBMS_LDAP: MOD_ARRAY size limit exceeded Cause: An attempt was made by a PL/SQL module to add an element beyond the MOD_ARRAY size limit. Action: Increase the MOD_ARRAY size limit in PL/SQL module involving DBMS_LDAP. ORA-31227: DBMS_LDAP: invalid LDAP MESSAGE handle Cause: An attempt was made by a PL/SQL module to use an LDAP MESSAGE handle which is not valid and might have already been freed. Action: Check the LDAP MESSAGE handle in PL/SQL module involving DBMS_LDAP. ORA-31228: DBMS_LDAP: invalid MOD_ARRAY Cause: An attempt was made by a PL/SQL module to use a MOD_ARRAY which is not valid and might have already been freed. Action: Check the MOD_ARRAY in PL/SQL module involving DBMS_LDAP. ORA-31229: DBMS_LDAP: invalid input parameter Cause: An invalid argument has been passed by a PL/SQL module to a DBMS_LDAP subprogram Action: Check the input argument to the DBMS_LDAP subprogram in PL/SQL module involving DBMS_LDAP. ORA-31230: DBMS_LDAP: unable to dynamically allocate additional memory Cause: An error occured during dynamic memory allocation from session heap. Action: Verify that adequate memory resources are available. ORA-31231: DBMS_LDAP: invalid PROPERTY_SET Cause: An attempt was made by a PL/SQL module to use a PROPERTY_SET which is not valid and might have already been freed. Action: Check the PROPERTY_SET in PL/SQL module involving DBMS_LDAP. ORA-31232: DBMS_LDAP: invalid MOD_PROPERTY_SET Cause: An attempt was made by a PL/SQL module to use a MOD_PROPERTY_SET which is not valid and might have already been freed. Action: Check the MOD_PROPERTY_SET in PL/SQL module involving DBMS_LDAP. ORA-31398: DBMS_LDAP: Shared servers are not supported. Cause: The session executing functions from the DBMS_LDAP package is being handled by a shared server in the Database. Action: Use dedicated database sessions to execute functions in the DBMS_LDAP package. ORA-31399: Cannot contact LDAP server string at port number Cause: The LDAP server specified could not be contacted. This can happen if the server is down or inaccessible. Action: Contact the administrator of the LDAP server ////////////////////////// End of DBMS_LDAP & OiD messages ORA-31401: change source string is not an existing change source Cause: The caller did not use the name of an existing change source. The name given does not match the name of any existing change source. Action: Check the spelling of the change source name. Choose an existing change source. ORA-31402: unrecognized parameter string Cause: Unrecognized parameter was detected. Action: Check for too many parameters in the call. ORA-31403: change table string already contains a column string Cause: Issued ALTER_CHANGE_TABLE with an add operation but a column by this name already exists in the specified table. Action: Check the names and call the procedure again. ORA-31404: all input parameters are null Cause: All input parameters are null. At least one property must be altered. Action: Call the procedure again, making sure that all the required parameters have been specified. Ensure that at least one parameter is not null. Refer to user documentation for the correct way of calling this procedure. ORA-31405: cannot make changes while change set string is advancing Cause: The change set is currently advancing. Change sources related to an advancing change set cannot be altered. Change tables related to the advancing change set cannot be created, altered or dropped. Some or all the parameters of the change set cannot be altered while the set is advancing. Action: Wait until the change set has finished advancing, then reissue the command. If altering the change set, only the advance_enable parameter can be altered during an advance. ORA-31406: change source string is referenced by a change set Cause: The operation cannot complete because this change source is referenced by one or more change sets. Action: Drop the change sets first, then re-issue the command. May have to drop some change tables before the change sets are dropped. ORA-31407: end_date must be greater than the begin_date Cause: The end data of the change set is earlier than the begin date. The end date must always be later in time than the begin date, so that the duration between the begin and end dates is a positive amount of time. Action: Change the begin date and/or the end date, so that the end date is later than the begin date. ORA-31408: invalid value specified for begin_scn or end_scn Cause: The begin_scn was not greater than zero. The end_scn was less than zero. The end_scn was less than the begin_scn. Action: Check the values of both begin_scn and end_scn. Correct them to make sure that they form a legal SCN range. An end_scn value of zero indicates an infinite scn range. ORA-31409: one or more values for input parameters are incorrect Cause: One or more of the inputs to the procedure had invalid values. Action: Identify the bad parameter(s) and supply correct values to the procedure. ORA-31410: change set string is not an existing change set Cause: Could not find an existing change set by this name. Action: Check the spelling of the change set name. Call the procedure again, passing the correct change set name. ORA-31411: change set string is referenced by a change table Cause: The operation cannot be performed because the change set contains one or more change tables. Action: You will need to drop the change table(s) first, then repeat the operation ORA-31412: change set string is disabled and cannot be advanced Cause: The specified change set is disabled. The change set needs to be enabled for the operation to succeed. Action: Determine why the change set is disabled and correct this condition. Alter the change set specifying "y" for advance_enable then retry the operation. ORA-31413: change set string is currently being advanced Cause: An advance operation is in progress for this change set and we only allow one at a time. Action: Since the change set is currently being advanced, the best action is to wait for it to finish advancing. Only one caller at a time can advance the change set. Check for the cause of long running advance operations. ORA-31414: error(s) occurred during change table advance Cause: One or more errors occurred during the advance operation. Action: Check the log file(s) for a more detailed report of the underlying errors. ORA-31415: change set string does not exist Cause: Specified change set does not exist or the user does not have access to the publications in that change set. The name specified did not match the name of any existing change set. Certain privileges are required to access the publications within that change set. Action: Check the name and call the procedure again, with the name of an existing change set. Contact the publisher or database administrator if user privileges are required to access the publications in the change set. ORA-31416: invalid SOURCE_COLMAP value Cause: A source_colmap value of "y" was specified for an asynchronous change table. Action: Specify a source_colmap parameter value of "n" and call the procedure again. ORA-31417: column list contains control column string Cause: Reserved column name was specified in a column list or column type parameter. Action: Control columns are selected with separate parameters. If you did not want a control column, then change the name of the specified column so that it does not conflict with a reserved column name. ORA-31418: source schema string does not exist Cause: Trying to create a synchronous change table and the source schema did not match any existing schema names in the database. Action: Specify the name of an existing schema. ORA-31419: source table string does not exist Cause: When creating a synchronous change table, the underlying source table must exist when the procedure is called. In this case, the source table did not exist. Action: Specify the name of an existing table. ORA-31420: unable to submit the purge job Cause: When creating the first change table, a purge job is submitted to the job queue. Submission of this purge job failed. Action: Make sure that job queue processes are enabled and are currently running. If this does not solve the problem, contact Oracle. ORA-31421: change table does not exist Cause: Specified change table does not exist. Action: Recheck the name, and call the procedure again using an existing change table. ORA-31422: owner schema string does not exist Cause: Value specifed for the owner parameter does not contain the name of an existing schema in the database. Action: Recheck the name, and call the procedure again using an existing schema name. ORA-31423: change table string does not contain column string Cause: Issued ALTER_CHANGE_TABLE with a drop operation and the specified column does not exist in the change table. Action: Recheck the names, and call the procedure again. ORA-31424: change table has active subscriptions Cause: The change table is subscribed to, so it cannot be dropped. Action: Do not drop a change table while there are active subscribers. If this is an emergency, use the FORCE parameter. This will forcibly drop the change table out from under all subscribers. ORA-31425: subscription does not exist Cause: The subscription either did not exist or did not belong to this user. Action: Call the function again with a valid subscription name. ORA-31426: cannot modify active subscriptions Cause: The subscription was already activated so that additional calls to SUBSCRIBE were prohibited. Action: Subscribe to all the desired tables and columns before activating the subscription. Ensure that the correct subscription name is specifed. ORA-31427: publication string already subscribed Cause: The subscription already contained this publication. Action: Check the values of subscription_name and publication_id. Check any other subscribe calls to see if they subscribe to columns that are shared among more than one publication on the same source table. Do not attempt to subscribe to the same publication more than once in the same subscription. Use the publication_id variant of the SUBSCRIBE call if needed to specify precise publications. ORA-31428: no publication contains all the specified columns Cause: One or more of the specifed columns cannot be found in a single publication. Action: Change the subscription request to select only columns that are in the same publication. Consult the USER_PUBLISHED_COLUMNS view to see current publications. ORA-31429: subscription has not been activated Cause: The called procedure required an activated subscription. Action: Check the subscription name and correct if necessary. Call the ACTIVATE_SUBSCRIPTION procedure for this subscription and then reissue the original command. ORA-31430: subscriber view exists Cause: A view that is already in use was specified for the subscriber view. Action: Call the SUBSCRIBE procedure using a different subscriber view name. ORA-31431: all source tables must belong to the synchronous change set Cause: Not all of the source tables belong to the synchronous change set. Action: Check the spelling of the source tables. Make sure that all of the source tables belong to the synchronous change set. ORA-31432: invalid source table Cause: Either the schema_name.source_table did not exist or it did not belong to this subscription. Action: Check the spelling of the schema_name and source_table. Verify that the specifed table exists in the specifed schema and is subscribed to by the subscription. ORA-31433: subscriber view does not exist Cause: The subscription did not contain this subscriber view. Action: Recheck the name, and specify the name of an existing subscriber view. ORA-31434: purge is currently running Cause: Called the PURGE procedure while a purge job was currently running. Action: Wait for purge to complete before reissueing this command. ORA-31435: an error occurred during the purge operation Cause: An error occurred during the purge operation Action: Check the logfile for a more detailed report of the underlying errors. ORA-31436: duplicate change source string Cause: A change source by the specifed name already exists. Action: Recreate the change source with a unique name. ORA-31437: duplicate change set string Cause: A change set by the specified name already exists. Action: Recreate the change set with a unique name. ORA-31438: duplicate change table string Cause: A change table by the specified name already exists. Action: Recreate the change table with a unique name. ORA-31439: subscription is already active Cause: The subscription is already active. Action: Check name and retry. ORA-31440: change set string is empty and cannot be advanced Cause: User attempted to advance a change set which does not contain any change tables. Without change tables, a change set cannot be advanced. Action: Create change tables in the change set, then retry the advance. ORA-31441: table is not a change table Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a table that is not a CHANGE table. This can also occur when a CHANGE table object has been orphaned. CHANGE tables can become orphaned after a CREATE_CHANGE_TABLE failure or an incomplete DROP_CHANGE_TABLE. Action: Check spelling. If error was due to an incorrect name, then retry the procedure using the correct name. To drop a table that is not a CHANGE table, or an orphaned CHANGE table, use the DROP TABLE DDL command instead. ORA-31442: operation timed out while acquiring lock on string Cause: CDC attempted to acquire a lock on the resource, but the operation timed out. Action: Retry the operation later. ORA-31443: deadlock detected while acquiring lock on string Cause: CDC attempted to acquire a lock on the resource, but encountered a deadlock. Action: Contact Oracle corporation ORA-31444: parameter error while acquiring lock on string Cause: CDC attempted to acquire a lock on the resource, but encountered a problem passing parameters to the lock manager. Action: Contact Oracle corporation ORA-31445: invalid lock handle while acquiring lock on string Cause: CDC attempted to acquire a lock on the resource, but encountered a invalid lock handle, which did not correspond to any existing handle. Action: Contact Oracle corporation ORA-31446: this session does not own the lock handle for string Cause: CDC attempted to acquire a lock on the resource, does not own the the lock associated with the lock. This is an internal error. Action: Contact Oracle corporation ORA-31447: cannot create change tables in the SYS schema Cause: Attempted to create a change table in the SYS schema. This is not allowed. Action: Use a different existing schema and retry the command. ORA-31448: invalid value for change_source Cause: The specified value was not a valid name for a Change Source. Action: Specify a valid name and retry the command. ORA-31449: invalid value for change_set_name Cause: The specified value was not a valid name for a Change Set. Action: Specify a valid name and retry the command. ORA-31450: invalid value for change_table_name Cause: The specified value was not a valid name for a Change Table. Action: Specify a valid name and retry the command. ORA-31451: invalid value string for capture_values, expecting: OLD, NEW, or BOTH Cause: The specified value was not a valid option for a capture_values. Action: Specify a valid option and retry the command. ORA-31452: invalid value string for parameter, expecting: Y or N Cause: The specified value was not Y or N. Action: Specify Y or N for the parameter and retry the command. ORA-31453: invalid value string for parameter, expecting: Y, N, or NULL Cause: The specified value was not Y, N or NULL. Action: Specify Y, N or NULL for the parameter and retry the command. ORA-31454: invalid value string for operation parameter, expecting: ADD or DROP Cause: The specified value was not ADD or DROP. Action: Specify ADD or DROP and retry the command. ORA-31455: nothing to ALTER Cause: The specified column list is NULL and all optional control columns are "N". Action: Specify one or more columns to ALTER. ORA-31456: error executing a procedure in the DBMS_CDC_UTILITY package Cause: An internal attempt to invoke a procedure within the DBMS_CDC_UTILITY package failed. Action: Check the trace logs for more information. Ensure that the package has been installed successfully. Try issuing a DESCRIBE command from SQL on the package. If it fails, then try reinstalling the package. If it succeeds then try invoking one of the procedures from SQL. ORA-31457: maximum length of description field exceeded Cause: The maximum number of characters permitted in the description field was exceeded. Action: The maximum length of the description field is 30 characters. Ensure the length does not exceed this value and retry the command. ORA-31458: an internal error occurred Cause: This is an internal error. Action: Contact Oracle Worldwide Customer Support and report the error. ORA-31459: system triggers for DBMS_CDC_PUBLISH package are not installed Cause: One or more required system triggers are not installed. These triggers are required for the proper operation of Change Data Capture. Operations on Change tables cannot continue. Action: Install or reenable the triggers, or reinstall the package. ORA-31460: logfile location string is not an existing directory Cause: The directory specification for logfile location for the change source, does not correspond with an existing directory, or the directory was not accessible. Action: 1. Create the directory if it does not exist. If the directory does exist, change the file system permissions so the directory can be accessed. OR 2. perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles ORA-31461: logfile location string contains no files that match pattern string Cause: The directory specification for logfile location for the change source, does not contain any files whose names pattern-match the logfile_suffix. Action: 1. Make sure that the logfile location contains logfiles whose names match the logfile_suffix pattern for the change set. OR 2. perform ALTER CHANGE SOURCE and change the logfile_suffix such that it matches the names of existing logfiles in the directory ORA-31462: internal error while accessing metadata Cause: An unexpected internal error occurred while CDC was accessing its internal Metadata. Action: Contact Oracle Corporation ORA-31463: logfile location string is an empty directory Cause: The directory specification for logfile location for the change source, is an empty directory Action: 1. Make sure it is the correct location of the logfiles. If it is, make sure the directory contains logfiles. OR 2. perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles ORA-31464: target table for the change table no longer exists Cause: User tried to drop a change table but its underlying storage table (that contains the change data) has been dropped. Action: Contact Oracle Corporation ORA-31465: cannot obtain a lock on the subscription Cause: A timeout occurred while trying to place a lock on the subscription. Another session had already acquired the lock on the subscription. Action: Ensure the subscription name is correct and correct it if necessary. If it is already correct, try the operation again after the session holding the lock has released it. ORA-31466: no publications found Cause: Did not find any publications that matched the input parameters or the user does not have the privileges to access the specified publication. Action: Check the input parameters on the call to SUBSCRIBE. Validate that the proposed source table has been published by checking the USER_PUBLICATIONS view for that source table. Contact the publisher if user privileges are required to access the publication. Retry the command with correct security or publication information. ORA-31467: no column found in the source table Cause: The OBJECT_ID flag was set to "Y" on the call to CREATE_CHANGE_TABLE and change table belongs to the synchronous change set. The corresponding object column was not detected in the source table. Action: Create the change table with the OBJECT_ID flag set to "N" or investigate why the object column is not in the source table and add it to the source table. ORA-31468: cannot process DDL change record Cause: The change set has stop_on_ddl enabled and was trying to process a DDL change record. Action: Check the alert log to find out what the DDL record contained. Make any necessary changes to the change tables. Call ALTER_CHANGE_SET with recover_after_error and remove_ddl set to "Y". ORA-31469: cannot enable Change Data Capture for change set string Cause: The change set has reached the specified limit that was set up by the CREATE_CHANGE_SET command. Action: Check the alert log to find out whether capture, apply or both reached the limit. Once apply reaches its limit, the change set is permanently disabled. Create a new change set with new limits to continue capturing data. ORA-31470: asynchronous change tables must contain the RSID$ column Cause: If creating an asynchronous change table, the RSID was set to "N". If altering an asynchronous change table with an operation parameter of "DROP" RSID was set to "Y". Action: When creating asynchronous change tables, always specify "Y" for the RSID parameter. When altering asynchronous change tables always specify "N" for RSID. ORA-31471: invalid OBJECT_ID value Cause: An object_id value of "y" was specified for an asynchronous change table. Action: Specify an object_id parameter value of "n" and call the procedure again. ORA-31472: Importing Change Data Capture version string.string is too new Cause: An attempt was made to Import a file that was exported by a newer version of Oracle than the target instance. Action: If possible, re-export the file using a version of export that matches the import target. Objects can not be imported into previous versions of Oracle that did not support them. ORA-31475: redo log catalog contains no metadata for the source table Cause: While advancing a change set, an CDC attempted to query the LogMiner dictionary system tables to obtain the columns from the source table. The query returned no rows. This may be because none of the redo logs contains a catalog, or it may be an internal error. Action: First, verify that the source system contains the source table. execute dbms_logmnr_d.build procedure to populate the redos log with logminer dictionary information. If this has been done and the problem persists, then contact Oracle Corporation ORA-31476: a change table data column is missing from the source table Cause: While advancing a change set, an CDC determined that at least one of the data columns in a change table does not match the name of any of the columns in the source table. The source table column listis stored in dictionary table SYSTEM.LOGMNR_OBJ$ Action: Make sure that all of the data columns of the change table have the same names as the corresponding columns in the source table, and that all the columns exist in the source table. ORA-31477: could not detach LogMiner session during cleanup Cause: Failure during detach from a LogMiner session during advance of an asynchronous change set. This is an internal error. This exception is raised when a previous exception occurred during the internal protocol with LogMiner, after which Change Data Capture attempted to detach the LogMiner session as part of recovery. The detach session also failed Action: Contact Oracle Corporation ORA-31478: could not detach LogMiner session after change set advance Cause: Failure during detach from a LogMiner session after successful advance of an asynchronous change set. This is an internal error. This exception is raised when an asynchronous change set has been successfully advanced but CDC was unable to detach from the LogMiner session Action: Contact Oracle Corporation ORA-31479: could not create LogMiner session Cause: Failure during create of a new LogMiner session while advancing an asynchronous change set. This is an internal error. Action: Contact Oracle Corporation ORA-31480: staging database and source database cannot be the same Cause: A CDC API call specified a source database name that matched the staging database on which the CDC API call is being executed. Action: Make sure that the CDC API call is being executed from the staging database and that the source database is correctly specified. The source database and staging database need to be different databases. ORA-31481: change source string is not a HotLog change source Cause: A change source was specified that was not a HotLog change source, but a HotLog change source was required. Action: Correct the call to supply a HotLog change source. ORA-31482: invalid option for non-distributed Hotlog change source Cause: A CDC API call specified enabled_source = "Y" on a non-Distributed HotLog change source. Action: Specify a Distributed HotLog change source. ORA-31483: cannot have spaces in the parameter string Cause: The specifed parameter contained at least 1 space character. Action: Check the value of the specified parameter. Remove the spaces and reissue the CDC API call. ORA-31484: source database version must be at least 9.2.0.6 or greater Cause: The source database is not at version 9.2.0.6 or higher. Action: Upgrade the source database to 9.2.0.6 or higher. ORA-31485: invalid database link Cause: The database link used to connect from a staging database to a source database was invalid. The database link may not exist, may not be accessible to the current user, or may have been redefined since the Distributed HotLog change source was originally created. Action: Make sure that there is a database link to the source_database for the Distributed HotLog change source. Make sure this database link is accessible to the current user. ORA-31486: cannot support column string in this configuration Cause: The specified column cannot be used in a Distributed HotLog configuration when the source database version is 9.2.0.6 or 10.1.0.0. Action: Remove the specified column from the CREATE_CHANGE_TABLE or ALTER_CHANGE_TABLE CDC API call. ORA-31487: cannot support begin dates or end dates in this configuration Cause: The specified values cannot be used in a Distributed HotLog configuration. Action: Remove the specified values from the CREATE_CHANGE_SET CDC API call. ORA-31488: cannot support change set string in this configuration Cause: Change sources with the hot mine option enabled are limited to 1 change set. The system detected an existing change set so a second one can not be created. Action: Associate the change set with a different change source. ORA-31490: could not attach to LogMiner session Cause: Failure during attach to a LogMiner session while advancing an asynchronous change set. This is an internal error. Action: Contact Oracle Corporation ORA-31491: could not add logfile to LogMiner session Cause: Failure during add logfile to a LogMiner session while advancing an asynchronous change set. This is an internal error. Action: Contact Oracle Corporation ORA-31492: could not set session parameters for LogMiner session Cause: Failure during set parameters for a LogMiner session while advancing an asynchronous change set. This is an internal error. Action: Contact Oracle Corporation ORA-31493: could not prepare session for LogMiner session Cause: Failure during prepare session for a LogMiner session while advancing an asynchronous change set. This is an internal error. Action: Contact Oracle Corporation ORA-31494: could not activate a LogMiner session Cause: Failure during activation of a LogMiner session while advancing an asynchronous change set. This is an internal error. Action: Contact Oracle Corporation ORA-31495: error in synchronous change table on "string"."string" Cause: There was an error originating from this synchronous change table. One possible cause is that schema redefinition has occurred on the source table and one or more columns in the change table are now a different type than corresponding source columns. Another possible cause is that there is a problem accessing the synchronous change table. Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop and recreate the synchronous change table. ORA-31496: must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables Cause: An attempt was made to use the SQL command DROP TABLE for change tables, but DROP TABLE is not supported for change tables. Action: Use the DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE procedure instead of the DROP TABLE command. ORA-31497: invalid value specified for first_scn Cause: The first_scn was not greater than zero or was less than the previous value of first_scn. Action: Check the value of first_scn. Correct it to make sure it is an integer greater than zero and greater than any previous value for this change source. ORA-31498: description and remove_description cannot both be specified Cause: The description and remove_description parameters were both specified. Action: Check the values of description and remove_description. Correct call to only supply one of these values. ORA-31499: null value specified for required parameter string Cause: A null value was specified for a parameter that requires an explicit value. Action: Correct call to supply a value for this parameter. ORA-31500: change source string is not a ManualLog change source Cause: A change source was specified that is not a ManualLog change source, but a ManualLog change source is required. Action: Correct call to supply a ManualLog change source. ORA-31501: change source string is not an AutoLog change source Cause: A change source was specified that was not an AutoLog change source, but an AutoLog change source was required. Action: Correct call to supply an AutoLog change source. ORA-31502: invalid number supplied for supplemental_processes Cause: The caller supplied an invalid value for supplemental_processes. The value must be a positive integer. Action: Correct call to supply a positive integer value for supplemental_processes. ORA-31503: invalid date supplied for begin_date or end_date Cause: The caller supplied an invalid value for begin_date or end_date. The value must be a valid date value. Action: Correct call to supply a valid date value for begin_date and/or end_date. ORA-31504: cannot alter or drop predefined change source Cause: The caller attempted to alter or drop one of the predefined change sources HOTLOG_SOURCE or SYNC_SOURCE. Action: Do not attempt to alter or drop a predefined change source or correct call to supply the name of a user-created change source. ORA-31505: cannot alter or drop predefined change set Cause: The caller attempted to alter or drop the predefined change set SYNC_SET. Action: Do not attempt to alter or drop the predefined change set or correct call to supply the name of a user-created change set. ORA-31506: duplicate subscription name string Cause: A subscription by the specifed name already exists. Action: Recreate the subscription with a unique name. ORA-31507: %s parameter value longer than maximum length string Cause: A value was specified for a parameter that was longer than the maximum permitted length. Action: Correct the call to supply a shorter value for this parameter that fits within the maximum length. ORA-31508: invalid parameter value for synchronous change set Cause: A parameter value was specified that is not supported for synchronous change sets. Action: Correct the call to supply only valid parameter values for a synchronous change set. Synchronous change sets only support the default values for the following parameters: begin_scn, end_scn, begin_date, end_date, stop_on_ddl, supplemental_processes. ORA-31509: publication does not exist Cause: The specified publication did not exist or the specified subscription subscribed to a publication that no longer exists. Action: Recheck the publication or subscription specified. Either call the procedure again with an existing publication or create a new subscription that only subscribes to existing publications. ORA-31510: name uses reserved prefix CDC$ Cause: A name was specified that starts CDC$. The name prefix CDC$ is reserved for use by Oracle Corporation. Action: Change the name so it does not start with characters CDC$ ORA-31511: name exceeds maximum length of 30 characters Cause: A name was supplied that exceeds the maximum length of 30 characters. Action: Change the name so it does not exceed 30 characters ORA-31512: name cannot contain double quotation marks Cause: A name containing a double quotation mark was supplied. Subscription names cannot contain the double quotation mark. Action: Change the name so it has no double quotation marks ORA-31513: unsupported column type specified in change table Cause: A source column of an unsupported type was specified for inclusion in a change table. Columns types of LOB or LONG are not currently supported for change capture. Action: Change the column list so that it does not include columns of LOB or LONG types. ORA-31514: change set string disabled due to capture error Cause: This change set has encountered a capture error and was disabled. Action: Contact the change set"s publisher to request that the capture error be resolved. Subscriptions using this change set cannot be activated or have their subscription windows extended or purged until the capture error is resolved. ORA-31515: CDC change source string already exists Cause: A Change Data Capture change source intended for import already existed. Action: Either verify that the existing change source has the desired characteristics or drop the existing change source and perform the import again. ORA-31516: CDC change set string already exists Cause: A Change Data Capture change set intended for import already existed. Action: Either verify that the existing change set has the desired characteristics or drop the existing change set and perform the import again. ORA-31517: CDC change table string.string already exists Cause: A Change Data Capture change table intended for import already existed. Action: Either verify that the existing change table has the desired characteristics or drop the existing change table and perform the import again. ORA-31518: change column string already exists in CDC change table string.string Cause: A column in a Change Data Capture change table intended for import was already present in the change table. Action: Either verify that the change table contains the desired columns or drop the change table and perform the import again. ORA-31519: CDC subscription string already exists Cause: A Change Data Capture subscription intended for import already existed. Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again. ORA-31520: CDC subscription string already subscribes to publication ID string Cause: A Change Data Capture subscription intended for import already subscribed to a publication. Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again. ORA-31521: CDC subscription string already subscribes to publication ID string column string Cause: A Change Data Capture subscription intended for import already subscribed to a published column. Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again. ORA-31522: could not find Streams object string for CDC change set string Cause: An underlying Streams capture, apply, or queue was missing for an imported Change Data Capture change set. Action: Drop the imported change set because it is invalid. Retry the import, ensuring that STREAMS_CONFIGURATION=y is specified. ORA-31523: could not find change source string for CDC change set string Cause: The change source was missing for an imported Change Data Capture change set. Action: Drop the imported change set because it is invalid. Verify that the schema containing the missing change source was included in the original export. If needed, perform the export again, including the schema of the missing change source. ORA-31524: could not find change set string for CDC change table string.string Cause: The change set was missing for an imported Change Data Capture change table. Action: Drop the imported change table because it is invalid. Verify that the schema containing the missing change set was included in the original export. If needed, perform the export again, including the schema of the missing change set. ORA-31525: could not find column string in CDC change table string.string Cause: A column was missing for an imported Change Data Capture change table. Action: It is likely that this table existed before the import operation and import did not overwrite it. Determine whether the imported change table should supercede the original table. If so, drop the original table and retry the import. If not, the change table must have a different name in order to be imported. ORA-31526: could not find source table string.string for CDC change table string.string Cause: The source table was missing or was not set up correctly for an imported Change Data Capture change table. A synchronous change table requires the source table to exist and have the Change Data Capture trigger defined on it. An asynchronous change table requires table rules to be defined for the source table. Action: Drop the imported change table because it is invalid. Verify that the schema containing the source table was included in the original export. If needed, perform the export again, including the schema of the source table. If change table is asynchronous, ensure that STREAMS_CONFIGURATION=y is specified for the import. ORA-31527: could not find source column string for CDC change table string.string Cause: A source column was missing for an imported Change Data Capture change table. Action: Drop the imported change table because it is invalid. Verify that the schema containing the source table was included in the original export. If needed, perform the export again, including the schema of the missing source table. ORA-31528: could not find change set string for CDC subscription string Cause: The change set was missing for an imported Change Data Capture subscription. Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing change set was included in the original export. If needed, perform the export again, including the schema of the missing change set. ORA-31529: could not find publication for CDC subscriber view string.string Cause: A publication was missing for an imported Change Data Capture subscription. Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing publication was included in the original export. If needed, perform the export again, including the schema of the missing publication. ORA-31530: could not find published column string for CDC subscriber view string.string Cause: A published column was missing for an imported Change Data Capture subscription. Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing published column was included in the original export. If needed, perform the export again, including the schema of the missing published column. ORA-31531: could not find column string in CDC subscriber view string.string Cause: A column was missing in a subscriber view for an imported Change Data Capture subscription. Action: It is likely that this view existed before the import operation and import did not overwrite it. Determine whether the imported subscriber view should supercede the original view. If so, drop the original view and retry the import. If not, the subscriber view must have a different name in order to be imported. ORA-31532: cannot enable change source string Cause: The change source cannot be enabled when there is no change table created in any of the change sets associated with the change source. Action: Add a change table to a change set before enabling the the change source. ORA-31533: only one change set (string) is allowed in change source Cause: A Distributed HotLog change source can contain at most one change set. Action: Create a new change source and create the change set in the new change source. ORA-31534: Change Data Capture string publisher string is missing DBA role Cause: The publisher does not have the DBA role, which is required by the Change Data Capture operation. Action: Grant the DBA role the Change Data Capture publisher. ORA-31535: cannot support change source string in this configuration Cause: Each database can only have one change source with hot mine option enabled. The system detected an existing hot mine change source in the database, therefore, a second hot mine change source cannot be created. Action: Remove the existing change source and create this new change source again. ORA-31536: cannot support encrypted column string in the source table Cause: One of the columns specified in the parameter COLUMN_TYPE_LIST was an encrypted column in the source table Action: remove the encrypted column in the parameter COLUMN_TYPE_LIST ORA-31600: invalid input value string for parameter string in function string Cause: A NULL or invalid value was supplied for the parameter. Action: Correct the input value and try the call again. ORA-31601: Function string cannot be called now that fetch has begun. Cause: The function was called after the first call to FETCH_xxx. Action: Correct the program. ORA-31602: parameter string value "string" in function string inconsistent with string Cause: The parameter value is inconsistent with another value specified by the program. It may be inconsistent with the object type associated with the OPEN context, or it may be of the wrong datatype (a boolean rather than a text string or vice versa). Action: Correct the program ORA-31603: object "string" of type string not found in schema "string" Cause: The specified object was not found in the database. Action: Correct the object specification and try the call again. ORA-31604: invalid string parameter "string" for object type string in function string Cause: The specified parameter value is not valid for this object type. Action: Correct the parameter and try the call again. ORA-31605: the following was returned from string in routine string: LPX-number: string Cause: An LPX routine (XML/XSL processing) returned an internal error number to its PL/SQL wrapper routine in facility KUX which provides the implementation for package UTL_XML. Action: Look up the LPX error number and follow its corrective action. ORA-31606: XML context number does not match any previously allocated context Cause: A method in package UTL_XML was called with an invalid XML context handle. All handles must have previously been allocated by UTL_XML.XMLINIT. Action: Always call XMLINIT before any other methods in pkg. UTL_XML. ORA-31607: function string is inconsistent with transform. Cause: Either (1) FETCH_XML was called when the "DDL" transform was specified, or (2) FETCH_DDL was called when the "DDL" transform was omitted. Action: Correct the program. ORA-31608: specified object of type string not found Cause: The specified object was not found in the database. Action: Correct the object specification and try the call again. ORA-31609: error loading file "string" from file system directory "string" Cause: The installation script initmeta.sql failed to load the named file from the file system directory into the database. Action: Examine the directory and see if the file is present and can be read. ORA-31610: cannot call this function from a non-master process Cause: Called a Data Pump process model function from a process which is not a master process. Action: Create a master process first. Then call the function from the master process. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31612: Allocation of process descriptor failed. Cause: During creation of a master process or a worker process, a failure occurred allocating a process descriptor for the process. Action: Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31613: Master process string failed during startup. Cause: The master process whose name is listed failed during startup. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31614: routine string received this error from string: string Cause: The call to the specified routine failed and the specific error text is included in this error message (the last %s string). Action: Correct inputs to the specified routine. ORA-31615: routine string received this error: string Cause: The specified routine failed and the specific error text is included in this error message (the last %s string). Action: Correct inputs to the specified routine. ORA-31616: unable to write to dump file "string" Cause: Export was unable to write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system. Action: Take appropriate action to restore the device. ORA-31617: unable to open dump file "string" for write Cause: Export was unable to open the export file for writing. This message is usually followed by device messages from the operating system. Action: Take appropriate action to restore the device. ORA-31618: dump file size too small Cause: The value specified for the FILESIZE parameter or the VOLUMESIZE parameter was too small to hold the header information for the export file, plus any data. Action: Increase the value of the FILESIZE or VOLUMESIZE parameter. ORA-31619: invalid dump file "string" Cause: Either the file was not generated by Export or it was corrupted. Action: If the file was indeed generated by Export, report this as an Import bug and submit the export file to Oracle Customer Support. ORA-31620: file or device "string" cannot be specified for string operation Cause: There was an inappropriate use of file or device in the current operation. Action: Correct operation or job setup. ORA-31621: error creating master process Cause: Setup to create a master process failed. Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31622: ORACLE server does not have string access to the specified file Cause: An attempt was made to read or write files within protected directories. Action: Correct the file/directory permissions and try the call again. ORA-31623: a job is not attached to this session via the specified handle Cause: An attempt to reference a job using a handle which is invalid or no longer valid for the current session. Action: Select a handle corresponding to a valid active job or start a new job. ORA-31624: A job cannot be modified after it has started. Cause: The user attempted to change the definition of a Data Pump job through filters, transforms or parameters after it had started. These changes can only be made while defining a job. Action: Stop the current job and rerun it with the correct definition. ORA-31625: Schema string is needed to import this object, but is unaccessible Cause: An error occurred when attempting to import objects. The schema specified is needed to import this object, but access to this schema is not available. Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31626: job does not exist Cause: An invalid reference to a job which is no longer executing, is not executing on the instance where the operation was attempted, or that does not have a valid Master Table. Refer to any following error messages for clarification. Action: Start a new job, or attach to an existing job that has a valid Master Table. ORA-31627: API call succeeded but more information is available Cause: The user specified job parameters that yielded informational messages. Action: Call DBMS_DATAPUMP.GET_STATUS to retrieve additional information. ORA-31628: error getting worker process exception Cause: Attempt to get a worker process exception failed. Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31629: unable to allocate additional memory Cause: A dynamic memory allocation failure occurred. Action: Report this problem to a database administrator. ORA-31630: a job name is required to attach a job for user string Cause: No job name was supplied for an attach and the user has either no jobs executing or mutiple jobs executing. Action: Provide a job name for attach to use in selecting an executing job, or to use for restarting a stopped job. ORA-31631: privileges are required Cause: The necessary privileges are not available for operations such as: restarting a job on behalf of another owner, using a device as a member of the dump file set, or ommiting a directory object associated with any of the various output files. Refer to any following error messages for additional information. Action: Select a different job to restart, try a different operation, or contact a database administrator to acquire the needed privileges. ORA-31632: master table "string.string" not found, invalid, or inaccessible Cause: A Master Table is required but no such table exists, or the content is not consistent with that of a valid Master Table, or the table is not accessible. Refer to any following error messages for clarification. Action: Make sure a valid Master Table exists, and eliminate any problems indicated by the following error messages. ORA-31633: unable to create master table "string.string" Cause: Job creation failed because a Master Table and its indexes could not be created, most commonly due to the pre-existance of a table with the same name (job name) in the user schema. Refer to any following error messages for clarification. Action: Select a different job name, DROP the existing table, or eliminate any problems indicated by the following error messages. ORA-31634: job already exists Cause: Job creation or restart failed because a job having the selected name is currently executing. This also generally indicates that a Master Table with that job name exists in the user schema. Refer to any following error messages for clarification. Action: Select a different job name, or stop the currently executing job and re-try the operation (may require a DROP on the Master Table). ORA-31635: unable to establish job resource synchronization Cause: A lock used in synchronizing Data Pump resources during job creation and deletion could not be obtained during job creation. This indicates that a process for some other Data Pump job has not released the lock due to an internal error. Action: Eliminate the processes for any failed Data Pump job and try to create the new job again. If the error continues to occur, contact Oracle Customer Support and report the error. ORA-31636: session is already attached to job string for user string Cause: The session executing the attach is already attached to the specified job. Action: Select a different job or create a new session. ORA-31637: cannot create job string for user string Cause: Unable to create or restart a job. Refer to any following or prior error messages for clarification. Action: Eliminate the problems indicated. ORA-31638: cannot attach to job string for user string Cause: Unable to attach a job to a session. Refer to any following or prior error messages for clarification. Action: Eliminate the problems indicated. ORA-31639: unexpected data found Cause: The Master Table or Data Pump file contents appear invalid. The table or file may not have been produced by a Data Pump job, or they may have been corrupted. Action: Select a different job name (Master Table) or replace the table or file with one produced by Data Pump. ORA-31640: unable to open dump file "string" for read Cause: Import was unable to open the export file for reading. This message is usually followed by device messages from the operating system. Action: Take appropriate action to restore the device. ORA-31641: unable to create dump file "string" Cause: Export was unable to create the specified file with write enabled. Action: Check the file name and file system for the source of the error. ORA-31642: the following SQL statement fails: string Cause: An internal error was generated from package DBMS_METADATA. Action: Contact Oracle Customer Support and report the error. ORA-31643: unable to close dump file "string" Cause: Export or Import was unable to close the dump file. This message is usually followed by device messages from the operating system. Action: Take appropriate action to restore the device. ORA-31644: unable to position to block number string in dump file "string" Cause: Export or Import was unable to position its file pointer to a specific block within the dump file. This message is usually followed by device messages from the operating system. Action: Take appropriate action based on the device messages. ORA-31645: unable to read from dump file "string" Cause: Import could not read from the dumpfile, probably because of a device error. This message is usually followed by a device message from the operating system. Action: Take appropriate action to restore the device. ORA-31648: Timeout before master process string finished initialization. Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31649: Master process string violated startup protocol. Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31650: timeout waiting for master process response Cause: After creating the job infrastructure and sending the initial message to the master process, it failed to respond in the allotted time and most likely aborted during startup. Action: Retry the open or attach request. Contact Oracle Customer Support if the problem persists. ORA-31651: communication error with master process - detaching job Cause: Unexpected failure trying to communicate with the master process. Action: Attach again and retry operation. Contact Oracle Customer Support if the problem persists. ORA-31652: command response message was invalid type - detaching job Cause: Something horribly wrong with the command/response protocol. Action: Reattach and retry operation. Contact Oracle Customer Support if the problem persists. ORA-31653: unable to determine job operation for privilege check Cause: Failure trying to determine the operation of the current job in order to test for appropriate privileges. Action: Retry in case it"s an intermittent failure. If it still fails, detach, reattach, and retry the call. Contact Oracle Customer Support if the problem persists. ORA-31654: unable to convert file or volume size as specified to a number Cause: File or volume size specification has an error the prevents it from being converted into a numeric value. Action: Fix the call. ORA-31655: no data or metadata objects selected for job Cause: After the job parameters and filters were applied, the job specified by the user did not reference any objects. Action: Verify that the mode of the job specified objects to be moved. For command line clients, verify that the INCLUDE, EXCLUDE and CONTENT parameters were correctly set. For DBMS_DATAPUMP API users, verify that the metadata filters, data filters, and parameters that were supplied on the job were correctly set. ORA-31656: cannot use TABLESPACE_EXPR filter with transportable mode Cause: A TABLESPACE_EXPR metadata filter was supplied for for a transportable mode import job. Transportable mode import does not support the subsetting of tablespaces from a dump file set. Action: Remove the filter expression. ORA-31657: data filter name can not be defaulted Cause: A null data filter name was supplied. Action: Fix the call to specify a data filter name. ORA-31658: specifying a schema name requires a table name Cause: The caller specified a schema name but neglected to specify a corresponding table name. Action: Fix the call to include a table name. ORA-31659: status message was invalid type - detaching job Cause: Message from the master process on the status queue had an invalid message type, indicating a failure in the protocol. Action: Reattach and retry the operation. Contact Oracle Customer Support if the problem persists. ORA-31660: metadata filter name can not be defaulted Cause: A null metadata filter name was supplied. Action: Fix the call to specify a metadata filter name. ORA-31661: there are no metadata transform values of type VARCHAR2 Cause: The specified metadata transform value was an invalid type. Action: Fix the call to specify a valid metadata transform value. ORA-31662: metadata transform name can not be defaulted Cause: A null metadata transform name was supplied. Action: Fix the call to specify a metadata transform name. ORA-31663: metadata remap name can not be defaulted Cause: A null metadata remap name was supplied. Action: Fix the call to specify a metadata remap name. ORA-31664: unable to construct unique job name when defaulted Cause: The job name was defaulted, and the name creation algorithm was unable to find a unique job name for this schema where the table name (for the master table) didn"t already exist. Action: Specify a job name to use or delete some of the existing tables causing the name conflicts. ORA-31665: mode can only be defaulted for IMPORT and SQL_FILE operations Cause: The job mode can not be null except for IMPORT and SQL_FILE operations. Action: Fix the call to specify the job mode. ORA-31666: Master process string had an unhandled exception. Cause: A Data Pump process model master process had an unhandled exception condition. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31667: parameter name can not be defaulted Cause: A null was supplied for the parameter name. Action: Fix the call by providing a valid parameter name. ORA-31668: Timeout before worker process string finished initialization. Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31669: Worker process string violated startup protocol. Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31670: Username argument must be specified and non-null. Cause: Called change user with a NULL username or a null string. Action: Specify a valid username argument. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31671: Worker process string had an unhandled exception. Cause: A Data Pump process model worker process had an unhandled exception condition. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31672: Worker process string died unexpectedly. Cause: A Data Pump process model worker process died unexpectedly, so PMON is cleaning up the process. Action: Check your system for problems. Check the trace file for the process, if one was created, for any additional information. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31673: worker process interrupt for normal exit by master process Cause: A worker process was requested to clean up and exit because the master process is doing a normal exit. Action: If this error occurs from a Data Pump client (e.g. expdp or impdp). it means that the master process for the operation exited prematurely. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31674: worker process interrupt for unhandled exception in master process Cause: A worker process was requested to clean up and exit because an unhandled exception occurred in the master process. Action: If this error occurs from a Data Pump client (e.g. expdp or impdp), it means that the master process for the operation had an unhandled exception. Check the log file for the operaton and the trace file for the master process for any additional information. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31675: worker process interrupt for unexpected death of master process Cause: A worker process was requested to clean up and exit (signaled by PMON, doing cleanup because the master process died unexpectedly). Action: If this error occurs from a Data Pump client (e.g. expdp or impdp), it means that the master process for the operation died unexpectedly. Check the log file for the operaton and the trace file for the master process for any additional information. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31676: illegal value for number of workers, string Cause: Called create worker processes with an illegal number of workers specified. Action: Make sure that the number of workers value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp) and you specified the parallel parameter, try the operation again with a smaller value for the parallel parameter. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31679: Table data object string has long columns, and longs can not be loaded/unloaded using a network link Cause: Table data objects that contain long columns can not be selected over a network link. Action: Export this table to a file and then import the same table from the file. ORA-31686: error creating worker processes Cause: Setup to create worker processes failed. Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31687: error creating worker process string with worker id string Cause: Attempt to create the listed worker process failed. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31688: Worker process string failed during startup. Cause: The worker process whose name is listed failed during startup. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31689: illegal value for base worker id, string Cause: Called create worker processes with an illegal base worker id value specified. Action: Make sure that the base worker id value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31690: Process name buffer size must be specified and must be greater than 0. Cause: Called get worker exception and either specified NULL or 0 for the buffer size argument. Action: Be sure to specify a buffer size that is big enough to hold the worker process name (e.g. 30 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31691: The worker received message number string from the MCP, which is invalid. Cause: Bad code. Action: Fix mcp code and reissue export/import command. ORA-31692: The following SQL statement failed trying to insert a row into the Master table: string Cause: Bad code. Action: Fix code and reissue export/import command. ORA-31693: Table data object string failed to load/unload and is being skipped due to error: string Cause: Table failed to load or unload due to some error. Action: Check load/unload error, correct problem and retry command. ORA-31694: master table string failed to load/unload Cause: Master table failed to load or unload. Action: Check load/unload error, correct problem and retry command. ORA-31695: Inconsistent master table on restart. The following SQL statement returned string identical objects. string Cause: Master table on restart has the same object inserted multiple times. Action: Restart not possible, reissue original export/import. ORA-31696: unable to export/import string using client specified string method Cause: Table attributes prevent client specified method for exporting or importing data. Action: Use default "DATA_ACCESS" parameter value. ORA-31697: aborting operation at process order number string Cause: User asked for it. Action: Don"t ask for it. ORA-31698: Error stack buffer size must be specified and must be greater than 0. Cause: Called get worker exception and either specified NULL or 0 for the error stack size argument. Action: Be sure to specify am error stack buffer size that is big enough to hold the error stack string (e.g. 4096 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-31700: Very long string supplied for AUDIT_SYSLOG_LEVEL parameter Cause: Very long string supplied for AUDIT_SYSLOG_LEVEL in init.ora Action: Use a valid facility.level such as "local1.notice" as described in syslog"s manual pages ORA-31901: the current operation was cancelled by the user Cause: The user requested to cancel current operation Action: No action is necessary ORA-32001: write to SPFILE requested but no SPFILE specified at startup Cause: An alter system command or an internal self tuning mechanism requested a write to the SPFILE but no SPFILE was used to startup the instance Action: Create an SPFILE and re-start the instance using the SPFILE. ORA-32002: cannot create SPFILE already being used by the instance Cause: A create spfile command is trying to write to an SPFILE that was used to startup the instance. Action: Specify a different SPFILE name ORA-32003: error occured processing parameter "string" Cause: An error occured while parsing the parameter file. Action: See additional errors to determine the root cause. ORA-32004: obsolete and/or deprecated parameter(s) specified Cause: One or more obsolete and/or parameters were specified in the SPFILE or the PFILE on the server side. Action: See alert log for a list of parameters that are obsolete. or deprecated. Remove them from the SPFILE or the server side PFILE. ORA-32005: error while parsing size specification [string] Cause: The value specified for an alter operation on a size parameter is not valid Action: Correct the value and retry the operation ORA-32006: %s initialization parameter has been deprecated Cause: A deprecated parmeter was specified at startup Action: Consult Oracle documentation to find new parameters to use instead. ORA-32007: internal Cause: A parameter error occured. Action: Call Oracle support. ORA-32008: error while processing parameter update at instance string Cause: An error occured while processing a parameter on a remote instance. Action: See accompanying error messages. ORA-32009: cannot reset the memory value for instance string from instance string Cause: Memory resets of local parameters are only allowed. Action: Retry the query for the local instance if needed. ORA-32010: cannot find entry to delete in SPFILE Cause: The SPFILE did not contain the sid.parameter entry. Action: Change the sid and/or the parameter. ORA-32011: cannot restore SPFILE to location already being used by the instance Cause: A restore operation trying to write to an SPFILE that was used to startup the instance. Action: Specify a different SPFILE name ORA-32012: failure in processing system parameters from restored SPFILE Cause: Failure during processing of parameters from restored SPFILE Action: Further diagnostic information should be in the error stack. ORA-32013: failure in verifying parameters from the restored SPFILE Cause: Failure during processing of parameters from restored SPFILE. It could be that restore image of the SPFILE is corrupted. Action: Further diagnostic information should be in the error stack. ORA-32014: error processing parameter "string" from the SPFILE restore image Cause: Failure during processing of parameters from restored SPFILE. It could be that restore image of the SPFILE is corrupted. Action: Further diagnostic information should be in the error stack. ORA-32015: unable to restore SPFILE Cause: Failure during SPFILE restore. It could be that the restore destination is not valid. Action: Further diagnostic information should be in the error stack. ORA-32016: parameter "string" cannot be updated in SPFILE Cause: Database is mounted. Action: Unmount the database to update the parameter in the SPFILE ORA-32017: failure in updating SPFILE Cause: A failure occured while updating the SPFILE. Action: See associated errors. ORA-32018: parameter cannot be modified in memory on another instance Cause: Parameter adjustment can take a very long time Action: Modify the parameter individually on each instance using the SID clause of the alter system command ORA-32019: The parameter SPFILE cannot be updated in the server parameter file. Cause: An attempt was made to update the parameter SPFILE in the server parameter file. Action: Convert the server parameter file into a parameter file and then add the parameters needed and recreate the server parameter file. ORA-32020: SID=* clause needed to modify this parameter Cause: The parameter did not have the same value on all RAC instances. Action: Retry the command by specifying SID=* ORA-32021: parameter value longer than string characters Cause: An attempt was made to alter a parameter value but the number of characters in the parameter value was longer than the allowed maximum. For a list parameter, one of the values in the list was longer than the allowed maximum. Action: Reduce the parameter value length and retry the command. For the DISPATCHERS parameter, use listener aliases to reduce value length. ORA-32022: parameter value longer than string characters Cause: An attempt was made to alter a parameter value but the combined length of all the parameter values was more than the allowed maximum. Action: Reduce the parameter value length and retry the command. For the DISPATCHERS parameter, use listener aliases to reduce value length. ORA-32024: invalid directory specified for audit_file_dest parameter Cause: Either the directory does not exist or it is not writable. Action: Retry the command by specifying a valid directory or granting appropriate directory permissions. ORA-32025: %s.string is not a table or view object. Cause: An attempt was made to set the audit table to a non-table object or a non-view object. Action: Specify a valid table or view object for the audit table option. ORA-32026: %s.string has fewer columns compared to string table. Cause: An attempt was made to set the audit table to a table or view object that has fewer columns compared to the base audit table. Action: Specify a valid table or view object for the audit table option. ORA-32027: There is no string column with the matching type in string.string. Cause: An attempt was made to set the audit table to a table or view object that does not have a column with the same name and type as the one in the audit table. Action: Specify a valid table or view object for the audit table option. ORA-32028: Syslog facility or level not recognized Cause: Syslog facility or level did not conform to the standard facility or level provided in the syslog.h file Action: Specify a facility or level such as "LOCAL1.NOTICE" which conforms to the syslog.h file ORA-32031: illegal reference of a query name in WITH clause Cause: forward or recursive reference of a query name in WITH clause is not allowed. Action: Correct query statement, then retry. ORA-32032: free temporary object number not available Cause: Too many queries using temp table transformation are currently being run to use up all temporay object numbers. Action: Turn off temporary table transformation or wait, then retry ORA-32033: unsupported column aliasing Cause: column aliasing in WITH clause is not supported yet Action: specify aliasing in defintion subquery and retry ORA-32034: unsupported use of WITH clause Cause: Inproper use of WITH clause because one of the following two reasons: 1. nesting of WITH clause within WITH clause not supported yet 2. For a set query, WITH clause can"t be specified for a branch. 3. WITH clause can"t sepecified within parentheses. Action: correct query and retry ORA-32035: unreferenced query name defined in WITH clause Cause: There is at least one WITH clause query name that is not referenced in any place. Action: remove the unreferenced query name and retry ORA-32036: unsupported case for inlining of query name in WITH clause Cause: There is at least one query name which is inlined more than once because it"s definition query is too simple and references another query name. This is currently unsupported yet. Action: remove such query name and retry ORA-32037: unsupported use of LEVEL in membership condition Cause: An attempt was made to use LEVEL in membership condition with subquery that is not supported. Action: Rewrite query to avoid using LEVEL in membership condition ORA-32050: %s operation failed Cause: A mapping operation failed. Action: Check FMON trace files for errors. ORA-32051: mapping service not available Cause: The mapping service was never started or previously failed to start properly. Action: Set FILE_MAPPING to TRUE if it is not currently set. Otherwise, check FMON trace files for an ORA-32052 error. ORA-32052: failed to start mapping service Cause: The mapping service failed to start properly. Action: Check FMON trace files for errors. ORA-32053: operation not supported Cause: Mapping libraries do not support operation. Action: Check whether mapping libraries are available and whether operation is supported by the libraries. ORA-32054: lost communication with FMPUTL process Cause: Lost communication with mapping utility. Action: Check FMON and FMPUTL trace files for errors. ORA-32055: invalid file type Cause: Invalid file type used when mapping files. Action: Specify one of expected file types. ORA-32056: invalid number of extents Cause: Invalid number of extents used for map operation. Action: Specify a non-negative number of extents. ORA-32057: invalid lock mode Cause: An invalid mode was used for a lock operation. Action: Specify one of expected lock modes. ORA-32058: operation restricted to SYSDBA users Cause: Operation requires SYSDBA priviliges. Action: Connect to the database as SYSDBA. ORA-32059: deadlock detected on mapping structures Cause: Mapping structures already locked by the same session. Action: Unlock mapping structures before proceeding with current operation. ORA-32060: channel failure Cause: Channel failure between foreground and background process. Action: Check foreground trace files for errors. ORA-32100: operation invalid on transient object Cause: Trying to perform an operation on transient object which is is valid only on persistent objects Action: Make sure object is persistent ORA-32101: cannot create OCI Environment Cause: An OCI Environment could not be created for OCCI Action: Insure that the parameters to the creatEnvironment method are valid ORA-32102: invalid OCI handle Cause: An invalid OCI handle is passed to an OCI call. Action: This is an internal OCCI Error. Please contact customer support. ORA-32103: error from OCI call Cause: An error code other than OCI_ERROR is returned from an OCI call. Action: This is an internal OCCI Error. Please contact customer support. ORA-32104: cannot retrieve OCI error message Cause: Error message after an OCI call could not be retrieved. Action: This is an internal OCCI Error. Please contact customer support. ORA-32106: array fetch not allowed without setBuffer on all columns Cause: The setBuffer method was not called for all column postions and the next method was called to fetch more than one row. Action: Call the setBuffer method for all column positions if next is to to be called to fetch more than one row. ORA-32107: internal OCI memory allocation failure Cause: Memory could not be allocated from an OCI heap. Action: Increase the process memory size. ORA-32108: max column or parameter size not specified Cause: The max column or parameter size is not specified. Action: Specify the max size by setMaxColumnSize or setMaxParamSize. ORA-32109: invalid column or parameter position Cause: An invalid column or parameter position is specified. Action: Specify a valid column or position number. ORA-32110: Connection not specified Cause: A null connection was passed. Action: Pass a valid, non-null connection. ORA-32113: Null object passed Cause: Null object was passed. Action: Pass a non-null object. ORA-32114: Cannot perform operation on a null LOB Cause: The LOB instance on which the operation was attempted was null. Action: Use a valid, non-null LOB instance to perform this operation. ORA-32116: Buffer size is less than amount specified Cause: The buffer size specified for the LOB read or write operation was less than the amount to be read or written. Action: The buffer size must be equal to or greater than than the amount to be read from or written to the LOB. ORA-32117: Source LOB is null Cause: The source LOB instance on which the operation was attempted was null. Action: Use a valid, non-null source LOB instance for this operation. ORA-32118: Cannot perform operation on a null FILE Cause: The FILE instance on which the operation was attempted was null. Action: Use a valid, non-null FILE instance to perform this operation. ORA-32120: Buffer size is less than amount specified Cause: The buffer size specified for the FILE read or write operation was less than the amount to be read or written. Action: The buffer size must be equal to or greater than than the amount to be read from or written to the FILE. ORA-32121: Source FILE is null Cause: The source FILE instance on which the operation was attempted was null. Action: Use a valid, non-null source FILE instance for this operation. ORA-32123: Attribute number is out of range Cause: The attribute number passed is greater than the total number of attributes of the described object. Action: Pass the attribute number within the allowable range. ORA-32124: Illegal attribute passed Cause: The attribute passed is not applicable for the described object. Action: Pass a valid attribute. ORA-32125: Attribute type is not appropriate Cause: The return type of the get method does not match the type of the attribute being passed. Action: Call the appropriate get method. ORA-32126: Cannot perform operations on a null REF Cause: The REF instance on which the operation was attempted was null. Action: Use a valid, non-null REF instance to perform this operation. ORA-32127: REFs do not belong to any connection Cause: Neither of the REFs being compared had associated connection information. Action: Atleast one of the REFs being compared must be associated with a valid connection. ORA-32128: setDataBuffer called after fetch has started Cause: Fetch from result set has already started and the setDataBuffer call was made. Action: Call the setDataBuffer method before calling the next() method. ORA-32129: cannot get information about this column Cause: The setDataBuffer method was called to get information about this column. Therfore, the current method cannot be called. Action: Use the information from the buffers specifed in the setDataBuffer call. ORA-32130: invalid offset/index refrenced in Bytes Cause: The offset/index is out of range of valid data locations in Bytes offsets. Action: Insure that offsets or index is within the range of Bytes object. ORA-32131: bind data type cannot be changed Cause: The setXXX method is called again with a different data type than originally specified, or the setXXX method is called for a subsequent iteration without being called before the first iteration. Action: Call the setXXX method with the same data type as done before the first iteration. If no setXXX method was called for this parameter postion the first iteration, then make sure that a setXXX method is called before the first addIteration method is called. ORA-32132: maximum iterations cannot be changed Cause: The setMaxIterations is called after a setXXX method has been called. Action: Call the setMaxIterations method before calling any setXXX methods. ORA-32133: Cannot get stream from LOB/FILE Cause: An open stream exists on the the LOB/FILE on which the operation was attempted. Action: Close the stream before getting another. ORA-32134: Cannot assign LOBs Cause: An open stream exists on the target LOB. Action: Close the stream on the target LOB before assigning the LOBs. ORA-32135: Cannot assign FILEs Cause: An open stream exists on the target FILE. Action: Close the stream on the target FILE before assigning the FILEs. ORA-32136: Cannot perform operation on an invalid stream Cause: The LOB/FILE from which the stream was obtained had been nullified or destroyed. Action: Use a valid stream. ORA-32139: Cannot write to the stream Cause: A write was performed after the last buffer was written. Action: Close this stream and get a new stream to perform the write. ORA-32140: cannot peform this operation on stream Cause: Either a read is attempted from a stream oi write mode, or a write is attempted on a stream in read mode. Action: Check the status of the stream to find out the valid operations that can be performed. ORA-32141: get method does not match the type of the parameter Cause: The getXXX method called on the Statement object does not match the type of the bind parameter. Action: Call the getXXX method that is the same as the type of the parameter. ORA-32142: maximum number of iterations exceeded Cause: The addIteration exceeds the maximum number of iterations set by the the setMaxIterations method. Action: Increase the maximum number of allowed iterations. ORA-32143: Environment not specified Cause: A null environment was passed. Action: Pass a valid, non-null environment. ORA-32144: Cannot perform operation on a null interval Cause: The interval involved in this operation is null. Action: Use valid, non-null interval instance to perform this operation. ORA-32145: Environment not specified Cause: The interval on which the operation was attempted was null and no environment was specified. Action: Specify non-null environment or perform the operation on a non null instance. ORA-32146: Cannot perform operation on a null date Cause: The date involved in this operation is null. Action: Use valid, non-null date instance to perform this operation. ORA-32147: Environment not specified Cause: The date on which the operation was attempted was null and no environment was specified. Action: Specify non-null environment or perform the operation on a non null instance. ORA-32150: Cannot perform operation on a null timestamp Cause: The timestamp involved in this operation is null. Action: Use valid, non-null timestamp instance to perform this operation. ORA-32151: Environment not specified Cause: The timestamp on which the operation was attempted was null and no environment was specified. Action: Specify non-null environment or perform the operation on a non null instance. ORA-32152: Cannot perform operation on a null number Cause: The number involved in this operation is null. Action: Use valid, non-null number instance to perform this operation. ORA-32153: Environment not specified Cause: The number on which the operation was attempted was null and no environment was specified. Action: Specify non-null environment or perform the operation on a non null instance. ORA-32154: Anydata context not specified Cause: A null anydata context was passed. Action: Pass a valid, non-null anydata context. ORA-32155: Anydata not specified Cause: A null anydata was passed. Action: Pass a valid, non-null anydata. ORA-32156: Cannot perform operation on stream Cause: This operation is not applicable to streams obtained from LOBs. Action: none ORA-32158: Invalid type passed Cause: An inapplicable type was passed to this call. Action: Pass an applicable type. ORA-32159: Cannot set prefetch options for a null Type Cause: A null Type name was passed. Action: Pass an non-null Type name. ORA-32161: Cannot perform piecewise fetch Cause: Zero amount was passed and buffer size was less than LOB size Action: Specify a larger buffer or use Stream ORA-32162: Read/Write SQL method not registered Cause: readSQL/writeSQL method was NULL or was not registered Action: Register readSQL/writeSQL by calling put method in Map ORA-32163: Method called on Invalid Environment type Cause: A non-XA call made on an XA Environment or XA call made on non-XA Environment Action: Make sure Environment type is OK ORA-32164: Method called on Invalid Connection type Cause: A non-XA call made on an XA Connection or XA call made on non-XA Connection Action: Make sure Connection type is OK ORA-32165: Cannot get XA environment Cause: Incorrect dbname string was passed or the XA connection has not been opened Action: Pass the correct dbname string or check if the XA connection is open ORA-32166: Cannot get XA connection Cause: Incorrect dbname string was passed or the XA connection has not been opened Action: Pass the correct dbname string or check if the XA connection is open ORA-32167: No payload set on the Message Cause: An attempt was made to enqueue a message without setting a payload on it. Action: Set a payload on the message before calling the send method. ORA-32168: Cannot perform operation on a null AnyData Cause: The AnyData instance on which the operation was attempted was null. Action: Use a valid, non-null AnyData instance to perform this operation. ORA-32300: cannot drop a secondary materialized view "string"."string" Cause: An attempt was made to drop a materialized view of a nested table column"s storage table. Action: Drop the materialized view that contains the nested table column. This will implicitly drop all secondary materialized views. ORA-32301: object-relational materialized views must be primary key based Cause: An attempt was made to create an object-relational materialized view that is not primary key based. Action: Create the materialized view with the PRIMARY KEY keyword. ORA-32302: object materialized views must be object ID based Cause: An attempt was made to create an object materialized view that is not object ID based. Action: Create the materialized view using the OF clause but omit any ROWID or PRIMARY KEY clauses. ORA-32303: mviews with user-defined types cannot reference multiple master sites Cause: For materialized views with user-defined types, the definition query cannot reference tables from different master sites. Action: Do not create materialized views with user-defined types referencing multiple master sites. ORA-32304: materialized views with user-defined types cannot use prebuilt table Cause: An attempt was made to create a materialized view with the ON PREBUILT TABLE option. Action: Do not create the materialized view with the ON PREBUILT TABLE option. ORA-32305: RepAPI materialized views with user-defined types are not supported Cause: An attempt was made to create a RepAPI materialized view with user-defined types. Action: Do not create a RepAPI materialized view with user-defined types. ORA-32306: updatable materialized views with user-defined types must use SELECT * Cause: An attempt was made to create an updatable materialized view with user-defined types where the definition query did not use SELECT * at the topmost level. Action: Rewrite the definition query so that SELECT * is used at the topmost level. ORA-32307: must use FROM ONLY clause when referencing an object table Cause: An attempt was made to create a materialized view whose definition query references object tables without the FROM ONLY clause. Action: Rewrite the definition query to use the FROM ONLY clause for all the object tables in the query. ORA-32308: object materialized views must use SELECT * Cause: An attempt was made to create an object materialized view where the definition query did not use SELECT * at the topmost level. Action: Rewrite the definition query so that SELECT * is used at the topmost level. ORA-32309: object mview type "string"."string" does not match the master table type Cause: An attempt was made to create an object materialized view whose type does not match the type of the master object table. Action: Redefine the type so that it matches the type of the master object table. ORA-32310: object materialized views must select from an object table Cause: An attempt was made to create an object materialized view whose definition query did not select from an object table. Action: Rewrite the definition query to select from an object table. ORA-32311: materialized view definition query selects an unsupported user-defined type Cause: An attempt was made in the definition query to select an embedded user-defined type, function returning a user-defined type, or a function whose arguments are user-defined types. Action: Rewrite the definition query to exclude these unsupported user-defined types. ORA-32312: cannot refresh a secondary materialized view "string"."string" Cause: An attempt was made to refresh a materialized view of a nested table column"s storage table. Action: Refresh the materialized view that contains the nested table column. This will implicitly refresh all secondary materialized views. ORA-32313: REFRESH FAST of "string"."string" unsupported after PMOPs Cause: A Partition Maintenance Operation (PMOP) has been performed on a detail table, and the specified materialized view does not support fast refersh after PMOPs. Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API. ORA-32314: REFRESH FAST of "string"."string" unsupported after deletes/updates Cause: One or more deletes or updates has been performed on one or more of the detail tables referenced by the specified materialized view. This materialized view does not support fast refresh after deletes or updates. Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after deletes or updates using the DBMS_MVIEW.EXPLAIN_MVIEW() API. ORA-32315: REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load Cause: One or more of the materialized view logs on the detail tables referenced by the specified materialized view omits the sequence number option. Such a log cannot be used to refresh a materialized view after deletes or updates and direct path insert. Action: Use REFRESH COMPLETE. Note: you can use the DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view logs omit the sequence number option. ORA-32316: REFRESH FAST of "string"."string" unsupported after mixed DML Cause: One or more of the materialized view logs on the detail tables referenced by the specified materialized view omits the sequence number option. Such a log cannot be used to refresh a materialized view after deletes or updates have been performed on multiple detail tables. Action: Use REFRESH COMPLETE. Note: you can use the DBMS_MVIEW.EXPLAIN_MVIEW() API to determine which materialized view logs omit the sequence number option. ORA-32317: cannot run a job from a job Cause: An attempt was made to execute a job from within another job. Action: Do not submit jobs that run other jobs. ORA-32318: cannot rename a materialized view Cause: Renaming a materialized view or its base table is not supported. Action: Do not rename the base table of a materialized view. ORA-32319: Cannot use direct loader log to FAST REFRESH materialized view "string"."string" Cause: The direct loader log might have been dropped Action: Need to do complete refresh ORA-32320: REFRESH FAST of "string"."string" unsupported after container table PMOPs Cause: A Partition Maintenance Operation (PMOP) has been performed on the materialized view, and no materialized view supports fast refersh after container table PMOPs. Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after PMOPs using the DBMS_MVIEW.EXPLAIN_MVIEW() API. ORA-32321: REFRESH FAST of "string"."string" unsupported after detail table TRUNCATE Cause: A detail table has been truncated and no materialized view supports fast refersh after a detail table has been truncated Action: Use REFRESH COMPLETE. Note: you can determine why your materialized view does not support fast refresh after TRUNCATE using the DBMS_MVIEW.EXPLAIN_MVIEW() API. ORA-32322: PCT refresh of "string"."string" not allowed the sequence of DMLs/PMOPs Cause: A table join dependent on another table on which PCT refresh is enabled has changed Action: Use REFRESH FORCE which will pick the best possible refresh method on the materialized view ORA-32330: invalid operation on online redefinition interim table "string"."string" Cause: An invalid operation was performed on an interim table which was being used for online redefinition of a table. Action: Do not perform any unsupported operation on the interim table. ORA-32331: type "string"."string" is incompatible with the master site Cause: A type used by the materialized view was found to be incompatible with its coressponding type on the master site. This could be because the type does not exist on the master site or has been evolved to a different version from that on the materialzied view site. Action: Make sure that the types used by the materialized view are the same on both the materialized view and master sites. ORA-32332: cannot refresh materialized view "string"."string" as type evolution has occured Cause: The types used by the materialized view or its master tables have been evolved. Action: Ensure that the types used by the materialized view have been evolved to the same version at both the master and materialized sites. Then, before refreshing the materialized view, evolve the materialized view using ALTER MATERIALIZED VIEW. ORA-32333: disable table scn update for Materialized view Cause: an event is set for disabling table scn update to prevent deadlock situation. (bug 1376209) Action: disable null refresh and/or base table scn update for Materialized view ORA-32334: cannot create prebuilt materialized view on a table already referenced by a MV Cause: the table on which the materialized view is created as prebuilt is already referenced by a materialized view Action: create the materialized view on a different table ORA-32335: dimension must have at least one level Cause: An level-less dimension is not allowed. Action: Do not drop the only level of a dimension. ORA-32336: cannot use USING NO INDEX to create materialized view "string"."string" Cause: The USING NO INDEX option was specified to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view. Action: Do not use the USING NO INDEX option to create an updatable primary key based materialized view, an index-organized materialized view or an object-id materialized view. ORA-32337: cannot alter materialized view with pending changes refresh on commit Cause: There are some pending changes in the detail tables Action: Execute an on-demand refresh on the materialized view to synchronize the data between the materialized view and the detail tables and then issue an ALTER MATERIALIZED VIEW statement. ORA-32338: on commit refresh grab all the detailed tables Cause: an event is set to let on-commit MV refresh to grab all the detailed tables, no matter whether they have modified or not. Action: none ORA-32339: cannot alter materialized view with the PMOP Cause: the materialized view is not allowed to have destructive PMOPS such as DROP, TRUNCATE and EXCHANGE (sub)partition. The UGA flag of i_am_a_refresh should be set first. Action: execute set_i_am_a_refresh first before alter materialized view with the PMOP. ORA-32340: cannot tune the materialized view definition Cause: Due to constructs in the materialized view definition, it could not be tuned to be fast-refreshable or rewriteable. Action: Execute DBMS_MVIEW.EXPLAIN_MVIEW to determine the cause. ORA-32341: The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string" Cause: The dependent object(s) of the materialized view may have changed. The materialized view may no longer be valid. Action: Execute ALTER MATERIALIZED VIEW COMPILE and to determine the status of the materialized view in catalog views. ORA-32342: The EXPLAIN_MVIEW facility failed to explain the materialized view statement Cause: An error exists in the materialized view definition. As a result, the materialized view statement could not be explained. Action: Check the syntax of the statement. If it is a CREATE MATERIALIZED VIEW statement, then also check the PARAMETERs specified for the materialized view. ORA-32343: let MVIEW engine know that it is IMPORT from 9i or earlier Cause: N/A. Action: Set this event only under the supervision of Oracle development. Not for general purpose use. ORA-32344: cannot create a secondary materialized view with synonym as base table Cause: It is not supported to create a secondary materialized view with synonym in the FROM clause. Action: Removed the synonym(s) from the statement. ORA-32345: fail to refresh the materialized view string.string due to the changed synonym Cause: The definition of one or more synonyms in the from clause have changed. The structure of the materialized view has become invalid. Action: Restore the synonym(s) or drop the materialized view and recreate it again. ORA-32400: cannot use object id columns from materialized view log on "string"."string" Cause: The materialized view log either does not have object id columns logged, or the timestamp associated with the object id columns is more recent than the last refresh time. Action: A complete refresh is required before the next fast refresh. Add object id columns to the materialized view log, if required. ORA-32401: materialized view log on "string"."string" does not have new values Cause: Materialized view log on the indicated table does not have new values information. Action: Add new values to materialized view log using the ALTER MATERIALIZED VIEW LOG command. ORA-32403: cannot use new values from mv log on "string"."string" Cause: The materialized view log either does not have new values logged, or the timestamp associated with the new values columns is more recent than the last refresh time. Action: Perform a complete refresh is required before the next fast refresh. ORA-32404: snapshot log uses Change Data Capture which is not enabled for this database Cause: A snapshot log that utilizes Change Data Capture is being imported to a database where Change Data Capture has not been enabled. Action: First enable Change Data Capture on the database then retry the import. ORA-32405: cannot alter tablespace for existing materialized view log Cause: The tablespace specification for the existing materialized view log cannot be altered or changed. Action: remove the tablespace clause from the statement. ORA-32406: cannot alter partitioning for existing materialized view log Cause: The partitioning specification for the existing materialized view log cannot be altered or changed. Action: remove the partitioning clause from the statement. ORA-32407: cannot exclude new values when materialized view log includes new values Cause: The excluding new values specification for the existing materialized view log cannot be accepted when including new values is the current option. Action: change excluding new values clause. ORA-32408: materialized view log on "string"."string" already has new values Cause: The materialized view log on the indicated table already has new values. Action: No action required. ORA-32409: materialized view log on "string"."string" already excludes new values Cause: The materialized view log on the indicated table already excludes new values. Action: No action required. ORA-32411: materialized view definition query exceeds the maximum length Cause: The materialized view definition query exceeds the 64K limit. Action: Change the materialized view definition query so that it does not exceed the maximum length of 64K. ORA-32412: encrypted column "string" not allowed in the materialized view log Cause: The materialized view log being created/altered is to capture an encrypted column of the base table. Action: Do not capture the encrypted column. ORA-32500: Dirname "string" cannot exceed "number" characters Cause: Path name too long Action: Use shorter pathname than maximum specified for dirname. ORA-32501: Writing SGA to file failed Cause: Underlying OSDs encountered an error Action: Check additional information. slercerrno contains errno. ORA-32502: Cannot execute command. Flash Freeze is not in effect Cause: This command can only be issued after a flash freeze Action: Refer to instructions for flash freeze and Oracle diagnostics. ORA-32503: Mapping SGA from file failed Cause: Underlying OSDs encountered an error Action: Check additional information. slercerrno contains errno. ORA-32504: expecting one of string, string, string, or string but found string Cause: illegal value specified for create watchpoint mode Action: specify one of the expected modes ORA-32505: too many watchpoints Cause: too many watchpoints created Action: increase appropriate initialization parameters ORA-32506: expecting one of string, string, or string but found string Cause: invalid arguments provided Action: provide one of the expected arguments ORA-32507: expecting string but found string Cause: invalid arguments to command Action: provide one of the expected arguments ORA-32508: no such watchpoint id Cause: invalid watchpoint id Action: use oradebug show to list valid watchpoint ids ORA-32509: watchpoint was already deleted Cause: trying to delete an already deleted watchpoint Action: use oradebug show to list valid watchpoint ids ORA-32510: cannot create watchpoint on unreadable memory Cause: trying to create watchpoint on invalid address Action: provide a different valid address ORA-32511: cannot create watchpoint in memory needed by watchpointing code Cause: overlap exists between requested memory range to watch and internal memory structures that watchpointing operations need Action: provide a different address range ORA-32512: type "string" is unknown Cause: trying to dump an invalid type name Action: specify a known type ORA-32514: cannot dump multiple "string" types: structure size is unknown Cause: trying to dump an invalid address Action: provide a different valid address ORA-32515: cannot issue ORADEBUG command; waited number ms for process string Cause: The process targeted to execute the ORADEBUG command was busy executing another ORADEBUG command for a time greater than the timeout value specified. Action: Increase the timeout value. ORA-32516: cannot wait for ORADEBUG command completion; waited number ms for process string Cause: The execution of the ORADEBUG command took longer than the the timeout value specified. Action: Increase the timeout value. ORA-32517: cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms Cause: The process targeted to execute the ORADEBUG command was busy executing another ORADEBUG command. But, because the total wait time for all targeted processes exceeded the maximum wait time, the ORADEBUG command was not issued to the target process. Action: Increase the timeout value. ORA-32518: cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms Cause: The total wait time for all targeted processes exceeded the maximum wait time, therefore the wait for the targeted process to finish executing the ORADEBUG command was aborted. Action: Increase the timeout value. ORA-32550: Replacement occured despite hint to the contrary Cause: This should never be signalled; it"s internal. Action: Report to Oracle support. ORA-32575: Explicit column default is not supported for modifying views Cause: Default keyword was used to modify views. Action: Use implicit default - omitting column-value pair. ORA-32576: missing TYPE keyword Cause: keyword TYPE is missing. Action: Use TYPE keyword. ORA-32577: username must be SYS or SYSTEM Cause: A user name of SYS or SYSTEM was not specified when providing a password in the CREATE DATABASE statement. Action: Only passwords for the SYS and SYSTEM users can be provided in the CREATE DATABASE statement. Re-issue the statement with passwords for users SYS or SYSTEM. ORA-32578: password for SYS already specified Cause: A password for the SYS user was specified twice in the CREATE DATABASE statement. Action: Re-issue the CREATE DATABASE statement with only one password for the SYS user. ORA-32579: password for SYSTEM already specified Cause: A password for the SYSTEM user was specified twice in the CREATE DATABASE statement. Action: Re-issue the CREATE DATABASE statement with only one password for the SYSTEM user. ORA-32580: both SYS and SYSTEM passwords must be provided Cause: Passwords for both the SYS and SYSTEM users were not provided in the CREATE DATABASE statement. If one of the passwords was provided, then both should be provided. Action: Re-issue the CREATE DATABASE statement with a password for both the SYS and SYSTEM users. ORA-32581: missing or invalid password Cause: An incorrect password was provided for the SYS or SYSTEM user in the CREATE DATABASE statement. Action: Re-issue the CREATE DATABASE statement with a valid password. ORA-32582: table function with left correlation to a table cannot also be left outer-joined to the table Cause: A table function T2 contains a reference to a table T1. T2 is also left outer-joined to T1. This is not allowed. Action: Remove the reference to T1 from T2 or remove the left outer-join specification (+). ORA-32583: query passed to table function has wrong number of elements in select list Cause: The query used as an input to a table function which takes a a ref cursor as argument has wrong number of elements in the select list which does not correspond to the elements in ref cursor. The ref cursor mentioned here refers to the one referenced in order by parition clauses. This is not allowed. Action: Make sure that the select list of the query matches the ref cursor columns as defined in the function. ORA-32584: missing LOG keyword Cause: keyword LOG is missing. Action: Use LOG keyword. ORA-32585: duplicate specification of a supplemental log attribute Cause: In a create/alter DDL a supplemental log attribute is specified more than once. Action: Rewrite the Create/Alter DDL such that it has a single occurence of any supplemental log attribute. ORA-32586: multiple specification of a supplemental logging attribute Cause: The primary key, unique index, foreign key or all column supplemental logging attribute can be specified at most once in a create/alter ddl. Action: Rewrite the Create/Alter DDL with single occurence of the offending supplemental logging attribute. ORA-32587: Cannot drop nonexistent string supplemental logging Cause: specified supplemental log attribute does not exist. Action: None ORA-32588: supplemental logging attribute string exists Cause: specified supplemental logging attribute exits. Action: retry the alter/create ddl after removing this supplemental logging attribute. ORA-32589: unable to drop minimal supplemental logging Cause: Minimal supplemental logging could not be dropped as one of primary key, foreign key, unique or all column supplemental logging is enabled at the database level. Action: Use V$DATABASE to determine the databasewide supplemental logging directives. Minimal supplemental logging could be dropped if and only if no other databasewide supplemental logging directives are enabled. ORA-32590: log group specification not allowed here Cause: Supplemental log specification is not allowed in the statement. Action: Remove the supplemental log specification from the statement. ORA-32591: connect string too long Cause: The connect string specified for the database link was more than 2000 characters. Action: Specify a connect string less than 2000 chracters. ORA-32592: all columns in log group can not be no log columns Cause: A supplemental log group must have at least one column of scalar type that is not marked as no log. Action: Redefine the supplemental log group with at least one column of scalar type that is not marked as no log. ORA-32593: database supplemental logging attributes in flux Cause: there is another process actively modifying the database wide supplemental logging attributes. Action: Retry the DDL or the LogMiner dictionary build that raised this error. ORA-32594: invalid object category for COMMENT command Cause: The object category specified is not a valid object for which to use the COMMENT command. Action: Retry the COMMENT command by specifying an accepted object category. (ie, Table, Operator, Indextype, etc.) ORA-32600: RETENTION and PCTVERSION cannot be used together Cause: cannot use both RETENTION and PCTVERSION together. Action: Use either RETENTION or PCTVERSION. ORA-32601: value for retention cannot be provided Cause: cannot give a value for Retention Period. Action: do not provide the value for parameter. ORA-32602: FREEPOOLS and FREELIST GROUPS cannot be used together Cause: cannot use both FREEPOOLS and FREELIST GROUPS together. Action: Use either FREEPOOLS or FREELIST GROUPS. ORA-32603: invalid FREEPOOLS LOB storage option value Cause: The specified FREEPOOLS LOB storage option value must be an integer. Action: Choose an appropriate integer value and retry the operation. ORA-32604: invalid REBUILD option Cause: Keyword FREEPOOLS expected after the REBUILD keyword. Action: User must specify FREEPOOLS keyword. ORA-32605: invalid REBUILD option Cause: cannot rebuild freepools while creating table with lob column. Action: User must not specify REBUILD... in this context. ORA-32606: missing NAV keyword in MODEL clause Cause: The NAV keyword was specified where it is expected. Action: Specify the NAV keyword or check the SQL statement. ORA-32607: invalid ITERATE value in MODEL clause Cause: The specified ITERATE value must be a 4 byte positive integer. Action: Choose an appropriate value and retry the operation. ORA-32608: missing INCREMENT or DECREMENT keyword in FOR loop Cause: INCREMENT or DECREMENT keyword was not specifiedi where it is expected. Action: Specify the INCREMENT or DECREMENT keyword or check the SQL statement. ORA-32609: missing REFERENCE keyword in MODEL clause Cause: The REFERENCE keyword was not specified where it is expected. Action: Specify the REFERENCE keyword or check the SQL statement. ORA-32610: missing SINGLE REFERENCE or DIMENSION keyword in MODEL clause Cause: SINGLE REFERENCE or DIMENSION keyword was not specified where it is expected. Action: Specify the applicable keywords or check the SQL statement. ORA-32611: incorrect use of MODEL CV operator Cause: CV function was used outside a dimension expression, in UNTIL condition, or with non-dimensional arguments. Action: Check the SQL statement and rewrite if necessary. ORA-32612: invalid use of FOR loop Cause: The MODEL FOR loop was used where it is not allowed. FOR loops are not allowed in complex dimensional predicates, on the right hand side of rules, or in the until condition. Action: Check the SQL statement and rewrite if necessary. ORA-32613: not a MODEL cell Cause: The operator requires a MODEL cell as operand. Action: Specify MODEL cell as operand, check SQL statement. ORA-32614: illegal MODEL SELECT expression Cause: An expression other than MODEL aliases, constants, or expressions of the two is specified in the MODEL SELECT clause. Action: Reformulate the query, perhaps nesting inside another SELECT. ORA-32615: incorrect use of MODEL IS ANY predicate Cause: IS ANY predicate is used outside dimension expression or with non-dimensional or different dimensional arguments. Action: Check the SQL statement and rewrite if necessary. ORA-32616: missing DIMENSION BY keyword in MODEL clause Cause: The DIMENSION keyword was not pecified where it is expected. Action: Specify the DIMENSION keyword or check the SQL statement. ORA-32617: missing MEASURES keyword in MODEL clause Cause: The MEASURES keyword was not specified where it is expected. Action: Specify the MEASURES keyword or check the SQL statement. ORA-32618: incorrect use of MODEL PREVIOUS function Cause: The MODEL PREVIOUS function was used outside of MODEL "ITERATE UNTIL" clause, or was nested. Action: Check the SQL statement and rewrite if necessary. ORA-32619: incorrect use of MODEL ITERATION_NUMBER Cause: ITERATION_NUMBER was used outside of an iterated MODEL. Action: Check the SQL statement and rewrite if necessary. ORA-32620: illegal subquery within MODEL rules Cause: A subquery was used illegally within the MODEL rule. Action: Check the SQL statement and rewrite if necessary. ORA-32621: illegal aggregation in UNTIL iteration condition Cause: An aggregate function was used in UNTIL condition. Action: Check the SQL statement and rewrite if necessary. ORA-32622: illegal multi-cell reference Cause: Multi-cell reference was specified on a measure expression without an aggregate function. Action: Use an aggregate function on the measure expression or qualify the cell reference. ORA-32623: incorrect use of MODEL PRESENT* functions Cause: A PRESENT* function (IS PRESENT, PRESENTV, PRESENTNNV) was used in a measure expression. Action: Check the SQL statement and rewrite if necessary. ORA-32624: illegal reordering of MODEL dimensions Cause: The expressions to qualify dimensions were specified in an incorrect order within a cell reference. Action: Reorder dimension expressions in the cell reference. ORA-32625: illegal dimension in cell reference predicate Cause: A non-positional dimension was referenced in the predicate. Action: Check the SQL statement and rewrite if necessary. ORA-32626: illegal bounds or increment in MODEL FOR loop Cause: FOR loop allows only numeric and datetime without timezone type for bounds. Only constants of interval and numeric types are allowed as increment/decrement expressions. Action: Check the SQL statement and rewrite if necessary. ORA-32627: illegal pattern in MODEL FOR LIKE loop Cause: The FOR LIKE pattern had zero or more than one wild characters. Action: Simplify the pattern to have a single wildcard character. ORA-32628: invalid nesting of MODEL cell reference Cause: MODEL cell reference was nested too deeply. Action: Avoid deep nesting of cell references and rewrite if necessary. ORA-32629: measure used for referencing cannot be updated Cause: A measure used in nested referencing is updated by a MODEL rule in the automatic order MODEL. Action: Modify the SQL statement or use sequential order MODEL. ORA-32630: multiple assignment in automatic order MODEL Cause: A MODEL cell was updated on the same measure in multiple MODEL rules. Multiple assignment is not allowed in automatic order MODELs as it causes in ambiguity and nondeterminism. Action: Use sequential order MODEL or rewrite the rule to avoid this. ORA-32631: illegal use of objects in MODEL Cause: An object column was used as a MODEL column. Object types are not allowed as partition by, dimension by or measure expressions. Action: Check the SQL statement and rewrite if necessary. ORA-32632: incorrect subquery in MODEL FOR cell index Cause: An illegal subquery was specified in MODEL FOR cell index. A subquery used in a MODEL FOR cell index can not have subqueries, correlation, binds and references to WITH tables. Action: Check the SQL statement and rewrite if necessary. ORA-32633: MODEL subquery FOR cell index returns too many rows Cause: Subquery in MODEL FOR cell index returned more than the allowed maximum. Action: Split the rule into multiple ones. ORA-32634: automatic order MODEL evaluation does not converge Cause: Evaluation using automatic rule ordering did not reach a convergence point. Action: Modify the rules or use sequential order instead. ORA-32635: not a single cell reference predicate Cause: A predicate that is not a single cell reference predicate was specified where a single cell reference predicate was expected. A single cell reference predicate is either a constant expression or a predicate of the form Action: Make sure that the predicate is a proper single cell reference. In some cases, you might have to put explicit type conversion operators (or casts) on the constant expression. ORA-32636: Too many rules in MODEL Cause: The number of rules (possibly after rule unfolding) exceeded the maximum number of rules allowed. Action: Reduce the number of rules. ORA-32637: Self cyclic rule in sequential order MODEL Cause: A self-cyclic rule was detected in the sequential order MODEL. Sequential order MODELs cannot have self cyclic rules to guarantee that the results do not depend on the order of evaluation of the cells that are updated or upserted. Action: Use ordered rule evaluation for this rule. ORA-32638: Non unique addressing in MODEL dimensions Cause: The address space defined for the MODEL (partition by and dimension by expressions) do not uniquely identify each cell. Action: Rewrite the MODEL clause. Using UNIQUE SINGLE REFERENCE option might help. ORA-32639: Aggregate functions on reference MODELs are not allowed Cause: An aggregate function was specified on the cells of a reference MODEL. Action: Check the SQL statement and rewrite if necessary. ORA-32640: FOR LIKE loops are not allowed for multi-byte character types Cause: FOR LIKE loops was specified for a multi-byte character type. Action: Check the SQL statement and rewrite if necessary. ORA-32641: invalid expression in MODEL rule ORDER BY clause Cause: An invalid expression was specified in the MODEL rule ORDER BY clause where only expressions of dimension and measure columns and reference MODEL cell references are allowed Action: Modify the order by clause in the MODEL rule. ORA-32642: non-unique cell values from the ORDER BY clause Cause: The MODEL rule ORDER BY clause did not generate unique values for all cells that satisfy the predicates in the left side of the rule. Action: Modify the rule ORDER BY clause in the MODEL rule. ORA-32643: invalid use of window function in MODEL rule Cause: The window functions can not be used in SQL Model rules that have FOR-loops on the left side or aggregates on the right side. Action: Modify the MODEL rule. ORA-32644: this function is not allowed outside of MODEL clause Cause: A function allowed only within the MODEL clause is used outside of MODEL clause. Action: Rewrite the SQL statement. ORA-32690: Hash Table Infrastructure ran out of memory Cause: Not enough memory. Action: Increase memory. ORA-32695: HTI: Not enough memory Cause: Memory is not enough. Action: Increase memory. ORA-32696: HTI: No free slot Cause: There is not enough memory. Action: Increase memory. ORA-32700: error occurred in DIAG Group Service Cause: An unexpected error occurred while performing a DIAG Group Service operation. Action: Verify that the DIAG process is still active. Also, check the Oracle DIAG trace files for errors. ORA-32730: Command cannot be executed on remote instance Cause: DIAG is not registered with DIAG Group Service Action: Issue the command without the cluster database syntax ORA-32731: Another Parallel Oradebug session is in progress Cause: Another session for Parallel Oradebug is in progress with the database Action: Issue the command later when the current session finishes ORA-32732: Parallel Oradebug session is aborted Cause: Group reconfiguration is occurring among DIAGs Action: Issue the command later when group reconfiguration completes ORA-32733: Error occurred when executing Parallel Oradebug Cause: Error is encountered during executing command at local node Action: Check alert log and DIAG trace file for error detail ORA-32734: Error occurred when sending Oradebug command to remote DIAGs Cause: IPC communication problem encountered Action: Check IPC communication between DIAGs and issue the command again ORA-32735: DIAG process is not running in the instance Cause: DIAG process is not alive Action: Check error in DIAG trace file and issue the command again when DIAG is restarted ORA-32736: Hang analysis aborted due to wrong message type Cause: DIAG received wrong message. Action: Check DIAG trace files for errors. ORA-32737: Hang analysis aborted due to failed memory allocation Cause: DIAG couldn"t allocate buffer for remote copy. Action: Check DIAG trace files for errors. ORA-32738: Hang analysis aborted due to failed memory copy Cause: DIAG couldn"t copy buffer to remote node. Action: Check DIAG trace files for errors. ORA-32739: Hang analysis aborted due to failed heap re-grow Cause: DIAG couldn"t re-grow the heap for wait-for-graphs. Action: Check DIAG trace files for errors. ORA-32740: The requested operation cannot be proceeded Cause: Operation was aborted because instance termination was in progress. Action: Retry later after restarting the instance. ORA-32741: Hang analysis already going on Cause: Hang analysis was already in process globally or for the instance. Action: Wait for the current operation to complete and re-run the command. ORA-32742: Hang analysis initialize failed Cause: Hang analyzer was not able to allocate memory to initialize. Action: Check the trace files. ORA-32743: command cannot be executed on remote instance Cause: The database was not mounted in SHARED mode. Action: Mount the database in SHARED mode. ORA-32761: Turn off Temp LOB Ref Count Feature Cause: None Action: Turn off the whole temp lob ref count feature ORA-32762: Turn on Temp LOB Ref Count Tracing Cause: None Action: Check Trace file for debug info ORA-32763: Turn off N-Pass Temp LOB cleanup Cause: None Action: Facilitate debugging and testing //////////////////////////// SQL function on LOBs Error numbers 32766 to 32770 are reserved for SQL function on LOBs //////////////////////////// ORA-32766: instr with negative offset: use varchar semantics on LOBs Cause: The current varchar behavior is different. e.g. instr("abcd", "cd", -2, 1) returns 3, whereas instr(to_clob("abcd"), "cd", -2, 1) returns 0, (i.e. no match), because the reverse search starts from offset -2, which points to "c" and moving backward, i.e. "d" is ignored. This is symmetric to instr("dcba","dc",2,1), which returns 0. Action: ORACLE uses the same varchar semantics on LOBs (instr). Using the same example, instr(to_clob("abcd"), "cd", -2, 1) will return 3 as in the varchar case. ORA-32767: No server connection for this operation Cause: The client side sql or plsql function operation requires a connection to the server, but currently no client/server connection existed. Action: Establish a client/server connection. ORA-32771: cannot add file to bigfile tablespace Cause: An attempt was made to add the second file to a bigfile tablespace. Action: Do not use this command with bigfile tablespace. ORA-32772: BIGFILE is invalid option for this type of tablespace Cause: An attempt was made to create a bigfile tablespace that is dictionary managed or locally managed with manual segment-space management. Action: Either change the tablespace type to locally managed with automatic segment-space management, or create a SMALLFILE tablespace instead. ORA-32773: operation not supported for smallfile tablespace string Cause: An attempt was made to perform an operation which is supported only for bigfile tablespaces, e.g. resize tablespace. Action: Use the appropriate clause of the ALTER DATABASE DATAFILE command instead. ORA-32774: more than one file was specified for bigfile tablespace string Cause: More than one datafile or tempfile was specified in CREATE TABLESPACE command for a bigfile tablespace. Action: Change command to contain only one file or create a smallfile tablespace instead. ORA-32775: cannot change size attributes of read only tablespace string Cause: An attempt was made to change size attributes of a tablespace that is read only. Action: Change the tablespace to read/write and retry the operation. 17 ORA-32800 to ORA-32848 ORA-32800: internal error string Cause: An unexpected error occurred. Action: Contact Oracle Support Services. ORA-32801: invalid value string for string Cause: An invalid value was specified for a parameter. Action: Specify a valid value for the parameter. ORA-32802: value for string must be string Cause: An invalid value was specified for a parameter. Action: Specify the value as indicated by the message. ORA-32803: value for string cannot be altered Cause: An attempt was made to alter a value that cannot be altered. Action: Retry the operation without altering the indicated value. ORA-32804: invalid value string, string should have form string Cause: A value specified for a parameter has the incorrect form. Action: Specify a string of the correct form. ORA-32805: identifier for string too long, maximum length is string characters Cause: An identifier string exceeded the maximum allowed length. Action: Specify a string whose length is less than the maximum allowed length. ORA-32806: value for string is too long, maximum length is string Cause: A value exceeded it"s maximum allowed length. Action: Specify a value whose length is less than the maximum allowed length. ORA-32807: message system link string already exists Cause: A message system link of the specified name already exists. Action: Specify a different name. ORA-32808: message system link string does not exist Cause: A message system link of the specified name does not exist. Action: Specify a message system link name that already exists. ORA-32809: foreign queue string is already registered Cause: The foreign queue has already been registered for this message system link (NAME@MSGLINK). Action: Specify a different name that is not being used for this message system link. ORA-32810: foreign queue string is not registered Cause: The foreign queue (NAME@MSGLINK) has not been registered for this message system link. Action: Specify the name of a registered foreign queue. ORA-32811: subscriber string already exists Cause: The specified subscriber identifier already exists. Action: Specify a different identifier. ORA-32812: subscriber string does not exist Cause: The specified subscriber identifier does not exist. Action: Specify an existing subscriber identifier. ORA-32813: propagation schedule string already exists Cause: The specified propagation schedule identifer already exists. Action: Specify a different identifier. ORA-32814: propagation schedule string does not exist Cause: The specified propagation schedule identifier does not exist. Action: Specify a schedule identifier that already exists. ORA-32815: message system link string is referenced by a foreign queue Cause: An attempt was made to remove a message system link currently referenced by one or more registered foreign queues. Action: Unregister all foreign queues using this message system link and retry the operation. ORA-32816: foreign queue string is referenced by a subscriber or schedule Cause: An attempt was made to unregister a foreign queue currently referenced by one or more subscribers or propagation schedules. Action: Remove all subscribers and propagation schedules using this foreign queue and retry the operation. ORA-32817: message system link string is not configured with a log queue for string Cause: An attempt was made to add a propagation subscriber but the message system link was not configured with a log queue for the indicated propagation type. Action: Alter the message system link to configure the link with a log queue for this propagation type. ORA-32818: AQ queue string does not exist Cause: An operation was attempted where the specified AQ queue does not exist. Action: Specify the name of an existing AQ queue. ORA-32819: AQ queue string must be a normal queue Cause: An operation was attempted where the specified AQ queue exists but is not a normal queue. Action: Specify the name of an AQ queue which was created as a normal queue (NORMAL_QUEUE). ORA-32820: subscriber queue and exception queue must use same message system link Cause: An operation was attempted for INBOUND propagation where the specified subscriber queue and exception queue reference different message system links. Action: Specify an exception queue that is a registered foreign queue of the same message system link as the subscriber queue. ORA-32821: subscriber queue and exception queue must have same payload type Cause: An operation was attempted for OUTBOUND propagation where the AQ queues used for the subscriber queue and exception queue have different payload types. Action: Specify an exception queue that has the same payload type as the subscriber queue. ORA-32822: subscriber string is marked for removal Cause: An administration operation was attempted for a subscriber which is marked for removal. If attempting to remove a subscriber, the Messaging Gateway agent is not running or is running but unable to remove the subscriber at this time. Action: Do not issue propagation administration commands for a subscriber for which removal is pending. Wait for the subscriber to be removed by the agent or issue REMOVE_SUBSCRIBER with the FORCE option to force the subscriber to be removed. ORA-32823: subscriber exists for queue string and destination string Cause: An attempt was made to create a propagation subscriber when one already exists for the specified queue and destination pair. Action: Specify a different queue and destination pair, or remove the subscriber using that pair and retry the operation. ORA-32824: schedule exists for source string and destination string Cause: An attempt was made to create a propagation schedule when one already exists for the specified source and destination pair. Action: Specify a different source and destination pair, or remove the schedule using that pair and retry the operation. ORA-32825: Messaging Gateway agent has not been started Cause: An attempt was made to shut down the Messaging Gateway agent when it is not started. Action: No action required. ORA-32826: Messaging Gateway agent has already been started Cause: An attempt was made to start the Messaging Gateway agent when it is already started. Action: No action required. ORA-32827: Messaging Gateway agent must be shut down Cause: An operation was attempted that requires the Messaging Gateway agent to be shut down. Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to show a NOT_STARTED status, and retry the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway state if the agent fails to shut down after a reasonable time period. ORA-32828: Messaging Gateway agent must be running Cause: An operation was attempted that requires the Messaging Gateway agent to be started and responsive. Action: Issue STARTUP, wait for MGW_GATEWAY view to show a RUNNING status, and retry the operation. ORA-32829: Messaging Gateway agent cannot be shut down while it is starting Cause: An attempt was made to shut down the Messaging Gateway agent when it is in the process of starting and initializing. Action: Wait for MGW_GATEWAY view to show a RUNNING status and retry the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway state if the agent fails to start after a reasonable time period. ORA-32830: result code string returned by Messaging Gateway agent Cause: The Messaging Gateway agent terminated abnormally due to an unexpected error. Action: Review the Messaging Gateway log file for further information regarding the problem. Resolve the problem and start the Messaging Gateway agent. Contact Oracle Support Services if the problem cannot be resolved. ORA-32831: timed out trying to acquire administration lock Cause: A timeout occurred when attempting an administration operation. Either an administration operation was attempted while the Messaging Gateway agent was starting and initializing, or two administration operations were attempted at the same time. Action: Retry the operation. If the Messaging Gateway agent is starting, wait for MGW_GATEWAY view to show a RUNNING status and retry the operation. ORA-32832: failure string trying to acquire administration lock Cause: An unexpected error occurred trying to acquire administration lock. Action: Retry the operation. Contact Oracle Support Services if the error persists. ORA-32833: failure string trying to release administration lock Cause: An unexpected error occurred trying to release administration lock. Action: Contact Oracle Support Services if the error persists. ORA-32834: Messaging Gateway agent user has not been set Cause: A Messaging Gateway agent user has not been configured. Action: Create a database user having role MGW_AGENT_ROLE and issue DB_CONNECT_INFO to configure an agent user. ORA-32835: database user string does not exist Cause: The specified database user does not currently exist. Action: Create the user and grant all necessary privileges and roles. ORA-32836: database user string must be granted role string Cause: The specified database user does not have a required role. Action: Grant the user the indicated role. ORA-32837: invalid configuration state string Cause: The specified configuration state is invalid. Action: Remove and re-create the configured entities. Contact Oracle Support Services if the problem cannot be identified or resolved. ORA-32838: exceeded maximum number of properties Cause: An attempt was made to alter a property list where the number of properties in the resulting list exceeds the maximum allowed. Action: Order the elements of the alter list differently so the number of elements in the resulting list is less than the maximum. ORA-32839: property string is reserved, names with MGWPROP$_ prefix are not valid Cause: An attempt was made to specify a reserved name for a property name. Action: Use a non-reserved name. ORA-32840: property name cannot be NULL Cause: An attempt was made to use NULL for a property name. Action: Specify a non-NULL name. ORA-32841: invalid value for property string Cause: An attempt was made to specify an invalid value for a property. Action: Specify a valid property value. ORA-32842: value for property string cannot be altered Cause: An attempt was made to alter a property that cannot be altered. Action: Retry the operation without altering the indicated property. ORA-32843: value for string is outside the valid range of string to string Cause: A value was specified that is not in the valid range. Action: Specify a value within the indicated range. ORA-32844: exceeded maximum number of string values Cause: An attempt was made to add a value of the specified type but the maximum number of such values has been reached. Action: No action required. ORA-32845: Messaging Gateway agent is already running Cause: An attempt was made to start the Messaging Gateway agent when an agent instance is already running. Action: Shut down the Messaging Gateway agent currently running, verify the agent process has been terminated, and start the Messaging Gateway agent. ORA-32846: Messaging Gateway agent cannot be started; status is string Cause: An attempt to start the Messaging Gateway agent failed due to the indicated agent status. A BROKEN status indicates a problem that requires user intervention before the agent can be started. Action: Review the MGW_GATEWAY view and the Messaging Gateway log file for further information. Resolve the problem and start the Messaging Gateway agent. Contact Oracle Support Services if the problem cannot be resolved. ORA-32847: operation is not supported on this platform Cause: An attempt was made to perform an operation that is not supported on this platform. Action: Switch to a platform on which the operation is supported. ORA-32848: foreign queue DOMAIN required for JMS unified connections Cause: A DOMAIN was not specified when registering a foreign queue for a messaging system link that is configured to use the JMS unified messaging model. Action: Specify a non-NULL value for the DOMAIN parameter. Skip Headers Oracle® Database Error Messages 10g Release 2 (10.2) Part Number B14219-01 Home Book List Contents Index Master Index Contact Us -------------------------------------------------------------------------------- Previous Next View PDF 18 ORA-33000 to ORA-37999ORA-33000: (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of string. Cause: The AGGMAP was already compiled by a more recent version of the product than was being used to execute this command. Action: Recompile the AGGMAP in the current version. ORA-33002: (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number. Cause: The user specified a floor argument greater than the ceiling argument. Action: Adjust the floor and ceiling arguments so that the floor is less than the ceiling. OBSOLETE, please remove this ORA-33003: (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP. Cause: The user tried to specify a dimension in a dataflow-related clause in an aggmap which is already in another RELATION statement, DIMENSION statement, or possibly dimensioning the AGGMAP, or they specified a composite or conjoint dimension, or an object which is not a dimension Action: Remove the conflicting reference or specify a valid object ORA-33004: (XSAGDNGL01) workspace object is not a relationship array. Cause: A RELATION clause in the AGGMAP named a workspace object that is not a relation. Action: Name a valid self-relation in the RELATION statement. ORA-33005: (XSAGDIMBREAK) Invalid breakout for dimension workspace object. Cause: The user specified something that was not a valid dimension or relation on a BREAKOUTDIM line in an aggmap. This might be because the object was not a valid relation, was not over the specified dimension or was multidimensional Action: Use a valid relation instead ORA-33006: (XSAGDNGL02) The relation workspace object is not related to itself. Cause: A relation was named in a RELATION clause of the AGGMAP that is not a self-relation. Action: Name a valid self-relation in the RELATION statement. ORA-33008: (XSAGDNGL03) The relation workspace object is not a relation over a base dimension of AGGMAP workspace object. Cause: A relation was named in a RELATION clause of the AGGMAP that is not a relation for a base dimension of the AGGMAP. Action: Name a valid self-relation in the RELATION statement, that is, one that has a dimension that dimensions the AGGMAP. ORA-33009: (XSAGDNGLPREC) In AGGMAP workspace object, PRECOMPUTE may only be specified either for the entire AGGMAP or for individual RELATION statements. Cause: PRECOMPUTE was specified both as a line in the AGGMAP and on at least one of the RELATION lines, or it was specified more than once as a line of the AGGMAP. Action: Remove either the PRECOMPUTE line, or the PRECOMPUTE specification for all of the RELATION lines. ORA-33010: (XSAGDNGL04) Relation workspace object is duplicated in the AGGMAP workspace object. Cause: Two RELATION statements in the AGGMAP reference the same relation object. Action: Remove the duplicate RELATION statement. ORA-33012: (XSAGDNGL05) AGGMAP workspace object contains invalid syntax. Cause: A line in the AGGMAP contains invalid syntax. Action: Change the line to have valid syntax. ORA-33014: (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object. Cause: Operator variables cannot have the rollup dimension as one of their base dimensions. Action: Modify the definition of the operator variable so that the current rollup dimension is not one of its bases. ORA-33016: (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name. Cause: An invalid argument was supplied to the OPERATOR clause in the relation statement. Action: Fix the OPERATOR clause so that it specifies either a valid variable name or a valid operator. ORA-33018: (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string. Cause: An operator variable was supplied whose data type is not TEXT. Action: Change the operator clause to reference a TEXT variable. ORA-33022: (XSAGDNGL10) The measure dimension workspace object must be a TEXT or ID base dimension that does not dimension AGGMAP workspace object, but is in the same analytic workspace. Cause: A MEASUREDIM was supplied in the AGGMAP that was not acceptable. Action: Modify the MEASUREDIM clause to specify a valid dimension. ORA-33024: (XSAGDNGL11) AGGMAP workspace object contains duplicate information. Cause: The aggmap contains multiple instances of a clause that can only be specified once. Action: Remove the extra clause. ORA-33030: (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements. Cause: The AGGMAP either specified multiple PROTECT statements not on a RELATION line, or specified PROTECT statements both independently and on RELATION lines. Action: Correct the AGGMAP to have valid syntax. ORA-33036: (XSAGDNGL17) ARGS option workspace object must be a TEXT variable. Cause: An ARGS value had a non-text data type. Action: Use a text variable for ARGS. ORA-33046: (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause. Cause: The AGGMAP contained multiple SCREENBY clauses. Action: Remove one of the SCREENBY clauses from the AGGMAP. ORA-33048: (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension. Cause: The AGGMAP contains incompatible RELATION statements. Action: Remove one of the RELATION statements from the AGGMAP. ORA-33050: (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace. Cause: The user attempted to aggregate a variable in another analytic workspace. Action: Create an AGGMAP in the other analytic workspace to aggregate that variable. ORA-33052: (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables. Cause: The user attempted to aggregate a variable with different dimensions than the AGGMAP. This is only possible with undimensioned AGGMAPs. Action: Create a new undimensioned AGGMAP. ORA-33058: (XSAGDNGL28) In AGGMAP workspace object, error code string is greater than the maximum error code of number. Cause: The user specified an invalid ERRORMASK value. Action: Remove the invalid value from the ERRORMASK list. ORA-33060: (XSAGDNGL29) In AGGMAP workspace object, the value for the ERRORLOG MAX option must be greater than 0. Cause: The user specified an ERRORLOG MAX of 0 or a negative number. Action: Adjust the AGGMAP so that it uses a positive number. ORA-33064: (XSAGDNGL31) In AGGMAP workspace object, the hierarchy dimension QDR workspace object cannot refer to the related dimension of the relation. Cause: The user specified an invalid hierarchy dimension qualified data reference. Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. ORA-33066: (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation. Cause: The user specified an invalid qualified data reference for the hierarchy dimension. Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. ORA-33068: (XSAGDNGL33) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must specify a positive dimension offset. Cause: The user specified an invalid qualified data reference for the hierarchy dimension. Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. ORA-33070: (XSAGDNGL34) In AGGMAP workspace object, all QDRs of dimension workspace object must map to the same dimension position. Cause: The user specified two conflicting hierarchy dimension qualified data references. Action: Adjust the AGGMAP so that it uses a consistent qualified data reference. ORA-33072: (XSAGDNGL35) In AGGMAP workspace object, the hierarchy dimension QDR over dimension workspace object must be specified for every relation dimensioned by that hierarchy dimension. Cause: Multiple dimensions share the same hierarchy dimension, but it is only qualified within a subset of the AGGMAP relations. Action: Adjust the AGGMAP so that it uses consistent qualified data references. ORA-33074: (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object. Cause: The hierarchy dimension offset is an invalid dimension position. Action: Adjust the AGGMAP so that it uses valid qualified data references. ORA-33076: (XSAGDNGL37) In AGGMAP workspace object, the value "number" is not a valid value of dimension workspace object. Cause: The hierarchy dimension offset is an invalid dimension position. Action: Adjust the AGGMAP so that it uses valid qualified data references. ORA-33078: (XSAGDNGL39) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must refer to a dimension. Cause: The user specified an invalid qualified data reference for the hierarchy dimension. Action: Adjust the AGGMAP so that it uses a valid dimension value qualified data reference. ORA-33080: (XSAGDNGL40) In AGGMAP workspace object, you cannot reference dimension workspace object with both a RELATION statement and a DIMENSION statement. Cause: The user included both RELATION and DIMENSION statements in the AGGMAP referring to the same AGGMAP. Action: Remove one of the conflicting clauses. ORA-33082: (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET"s base dimension. Cause: The VALUESET statement specified a scalar valueset but did not include a qualified data reference to specify the parent. Action: Add a qualified data reference specifying the parent to the VALUESET statement. ORA-33084: (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object. Cause: The VALUESET line referred to a dimensioned valueset. Action: Use a non-dimensioned valueset to limit the status of the dimensioned one. ORA-33086: (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension. Cause: The specified AGGMAP was dimensioned by a conjoint dimension. Action: Use the CHGDFN command to change the conjoint to a composite dimension. ORA-33092: (XSAGCOMP04) number is not the name of a MODEL in any attached analytic workspace. Cause: An invalid model name was attached to an AGGMAP. Action: Remove the model from the AGGMAP or create a model with that name. ORA-33094: (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting. Cause: formulas likely refer to each other recursively or with a great deal of depth. Action: eliminate recursion and flatten formula trees. ORA-33098: (APABBR01) A value of "string" is not valid for the workspace object option. Cause: An inappropriate value was specified for the named option. Action: Set a legal value for the option. ORA-33100: (APABBR02) Value "number" is not valid for the workspace object option. Cause: An inappropriate value was specified for the named option. Action: Set a legal value for the option. ORA-33213: (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values. Cause: The user specified a BEFORE or AFTER clause specifying a position in the range of SESSION dimension values. Action: Do not use a position clause, or specify a position before the first SESSION value. ORA-33214: (CINSERT02) The workspace object dimension is too large. Cause: The dimension has too many values. Action: Deleted values can still take up space in the dimension and cause this error. Try removing the deleted values by exporting the dimension to EIF and reimporting it with the REPLACE DELETE option. ORA-33215: (CINSERT07) You cannot add session-only values to the workspace object dimension. Cause: The user tried to add a SESSION dimension value while a spreadsheet spreadsheet cursor was open. Action: Try adding the SESSION value while the cursor is not active. ORA-33217: (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE. Cause: Only UNIQUE concat dimensions can have custom member values. Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry. ORA-33218: (CINSERT04) %K is not a valid value for the workspace object dimension. Values for this dimension can have at most number significant digits after rounding to number decimal places. Cause: The user attempted to insert a value that had too many digits into a NUMBER dimension. For instance, the user might have tried to insert the value 99999 (5 digits) into a dimension with data type NUMBER(4). Action: Use a smaller number for the dimension value, or define a new dimension with a larger precision and replace the old dimension with the new one. ORA-33219: (CINSERT05) %K cannot be added to workspace object because it is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object. Cause: A value cannot be added to a dimension if it conflicts with an existing value in a unique concat dimension containing this dimension. Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, or either of the duplicate values could be renamed to make them UNIQUE. ORA-33223: (CMOVE03) You cannot move a session-only dimension value. Cause: The user named a SESSION dimension value in the MAINTAIN MOVE command. Action: Do not try to MAINTAIN MOVE session-only dimension values. ORA-33247: (CRENAME03) %K is already a value of the dependent UNIQUE concat dimension workspace object, from leaf dimension workspace object. Cause: A value cannot be renamed in a dimension if the new value conflicts with an existing value in a unique concat dimension containing this dimension. Action: The concat(s) causing the conflict could be CHGDFNed to NOT UNIQUE, or either of the duplicate values could be changed to make them UNIQUE. ORA-33261: (DBERRLEN) Analytic workspace string extension number truncated at number bytes while trying to read at number. Cause: Either an internal error or a mistaken user has truncated the AW Action: Export any data if possible and restore from backup ORA-33262: (DBERR01) Analytic workspace string does not exist. Cause: The analytic workspace requested does not seem to be in the current database Action: Check that you are in the correct schema and have access to the requested AW. ORA-33263: Could not create analytic workspace string Cause: A serious error was encountered while trying to set up the tables for the named analytic workspace. Possibilities include a tablespace that can"t be written to, corrupted metadata about which AWs exist, bogus tables with names the code expects to be able to use, or the remains of a partially removed AW. Action: There should be another error on the error stack. Consult it to determine what is causing the problem and remove that table. ORA-33265: (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number. Cause: The blocksize of the containing tablespace didn"t match database cache size. Action: Change either size to make them consistent, or set olap_page_pool_size to 0 to allow automatic OLAP pool management when compatibility is greater than 10.2. ORA-33267: (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it Cause: An attempt was made to access the specified analytic workspace"s LOB table. The OLAP option detected the table had fine-grained security applied to it. The OLAP option requires full access to this table to operate correctly. Action: Remove the fine-grained access control. ORA-33269: while operating on "string" Cause: Error is raised to inform user what object was being worked on when an error occurred during the creation of an AW. It should always be signaled with 33263 Action: See error#33263 ORA-33270: (DBERR05) Analytic workspace string already exists. Cause: The AW CREATE command was passed the name of an analytic workspace that already exists Action: Specify a different name. ORA-33274: (DBERR07) Timed out while trying to lock analytic workspace string for string. Cause: A lock operation that was supposed to happen very quickly was taking too long. It can be due to another session being stopped while holding that lock, another session crashing while holding that lock, or an internal error. Action: If another session is stopped, resume that session to let it release the lock. If another session has crashed, wait for a few minutes while PMON or SMON process is recovering that lock. Contact Oracle OLAP Support if none of the situations above apply. ORA-33278: (DBERR09) Analytic workspace string cannot be attached in RW or EXCLUSIVE mode until the changes made and updated in MULTI mode are committed or rolled back. Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in MULTI mode. Action: Either try attaching the workspace is RO or MULTI mode or commit or roll back the transaction before trying to attach the workspace in RW or EXCLUSIVE mode. ORA-33280: (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back. Cause: There are still changes to this analytic workspace that were updated and not committed when the workspace was attached in RW or EXCLUSIVE mode. Action: Either try attaching the workspace is RO, RW, or EXCLUSIVE mode or commit or roll back the transaction before trying to attach the workspace in MULTI mode. ORA-33282: (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock. Cause: Trying to wait for the workspace to become available caused a deadlock. Action: Release an analytic workspace that some other user might be waiting for before proceeding to attach this analytic workspace in this mode. ORA-33284: (DBERR12) Analytic workspace string cannot be opened in MULTI mode before converting it by the latest version of string. Cause: The AW is stored in 9i format. Action: Convert the AW to a later format ORA-33288: (DBERR15) Another user has incompatible access to analytic workspace string, and the wait timeout has expired. Cause: An attempt to access an analytic workspace conflicted with another user"s access, and the timeout specified has elapsed. Action: Wait until the conflicting user is done. ORA-33290: (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode. Cause: An attempt to access an analytic workspace conflicted with another user"s access, and no timeout was specified Action: Wait until the conflicting user is done. ORA-33292: (DBERR18) insufficient permissions to access analytic workspace string using the specified access mode. Cause: You do not have sufficient permissions to access this analytic workspace in the desired mode. Action: Ask the owner of the schema or OLAP DBA to grant you sufficient permissions to access the {SCHEMA}.AW${AWNAME} table (for example, SCOTT.AW$FOO table). ORA-33297: (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string. Cause: The user attempted to attach an old OLAP Services analytic workspace that cannot be converted by this version of OLAP Services. Action: Either create a new analytic workspace or try using a version of OLAP Services compatible with the one that created this analytic workspace. ORA-33298: (AWUPG01) Analytic Workspace string is already in the newest format allowed by the current compatibility setting Cause: User ran the DBMS_AW.CONVERT procedure on an Analytic Workspace that was created in or previously upgraded to the current compatibility mode. Action: If upgrading the Analytic Workspace is necessary, upgrade the database instance and then re-run DBMS_AW.CONVERT. If the new features offered by upgrading the Analytic Workspace are not required, then no action is needed. ORA-33302: (DBVALID01) SEVERE ERROR: Record number multiply used. Cause: The AW VALIDATE command has detected an error in the structure of the analytic workspace. This error will result in the corruption of one or more objects Action: Export what you can of the analytic workspace. ORA-33304: (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space. Cause: This is a benign message. The AW VALIDATE command found an analytic workspace has some inaccessible space. Action: Either nothing, or export and recreate the analytic workspace ORA-33305: (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number) Cause: This is a benign message. The AW VALIDATE command found an analytic workspace has some inaccessible space. Action: Either nothing, or export and recreate the analytic workspace ORA-33306: (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string. Cause: The AW VALIDATE command does not support read-only access. Action: Attach the analytic workspace read/write and try again. ORA-33308: (DBVALID04) SEVERE ERROR: Record number used but not allocated Cause: The AW VALIDATE command has detected a problem that will result in corruption of the analytic workspace. There is no corruption yet. Action: Export and recreate the analytic workspace. ORA-33309: (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number) Cause: The AW VALIDATE command has detected a problem that will result in corruption of the analytic workspace. There is no corruption yet. Action: Export and recreate the analytic workspace. ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable. Cause: User attempted to delete a variable, but some partitioned variable was defined to use that variable as the target of one of its external partitions. Action: DELETE the partitioned variable or CHGDFN DROP PARTITION the the external partition from the partitioned variable, then delete the target variable. ORA-33315: (XSDELDENTANON) You cannot delete workspace object while looping over unnamed composite workspace object. Cause: While looping over the named anonymous composite, an attempt was made to delete an object which is dimensioned by it. Action: Delete the object outside of a loop over the dimension. ORA-33332: (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again. Cause: There is no currently active analytic workspace. The command that generated the error requires an active analytic workspace to operate on. Action: Execute an AW ATTACH or AW CREATE command to establish an active workspace. ORA-33334: (DSSEXIST04) Analytic workspace string is not attached. Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled. Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name . ORA-33336: (DSSEXIST04A) Analytic workspace string is not attached. Cause: The specified analytic workspace is currently not attached to the session, or the name is misspelled. Action: Attach the analytic workspace with the AW ATTACH command, or correct the spelling of the name . ORA-33338: (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace. Cause: The command requires a non-temporary analytic workspace to operate on. Action: Specify an analytic workspace other than EXPTEMP. ORA-33413: (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction. Cause: Export of a compressed composite to an EIF file or lob failed because one or more of the bases had some values that were not in the current status. This can be caused either by a LIMIT command or a PERMIT READ restriction on the dimension. Action: Either set the base dimensions" statuses to ALL and remove their PERMIT READ programs, or export using the NOAGGR keyword. ORA-33425: (EIFMAKEF15) CAUTION: Exporting NTEXT objects using string for the EIF file character set can cause loss of data. To preserve all NTEXT data, export using the UTF8 character set for the EIF file. Cause: The user exported an object with data type NTEXT, but the EIF file that will result from the EXPORT command is not written in Unicode. Because no non-Unicode file can represent all possible Unicode data, it is possible that some data will be lost when converting from the Unicode NTEXT object to the EIF file. The EIF file will be written in the character set indicated by the "nls_charset" argument of the EXPORT command, or, if no such argument is present, in the database character set. Action: If the user is certain that the contents of the NTEXT object can be represented in the specified character set, then no action is necessary. Otherwise, the user can add "nls_charset "UTF8"" to the EXPORT command string. This will result in the EIF file being written in UTF8 Unicode, which can represent all the data contained in NTEXT objects. ORA-33427: (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT. Cause: User attempted to export an object whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The object will be exported as a TEXT object instead. Action: No action needed. ORA-33429: (EIFMAKEF17) CAUTION: NTEXT expression will be exported with type TEXT. Cause: User attempted to export an expression whose data type is NTEXT, but but the EIFVERSION option indicates a version of Express / Oracle OLAP that does not support the NTEXT data type. The expression will be exported as a TEXT object instead. Action: No action needed. ORA-33443: (ESDREAD14) Discarding compiled code for workspace object because analytic workspace string is not attached. Cause: A program used an analytic workspace name in a qualified object name. The named analytic workspace is not attached at program run time. Action: No action necessary. The program will be automatically recompiled. It is likely that the recompile will fail with an appropriate exception code, in which case the signaled condition should be corrected and the program re-run. ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent. Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to non-partition-dependent variables at compile time but refer to partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled. Action: None needed. ORA-33447: (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent. Cause: Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to partition-dependent variables at compile time but refer to non-partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled. Action: None needed. ORA-33448: (ESDREAD04) Discarding compiled code for workspace object because number now has string data, whereas it had string data when the code was compiled. Cause: The datatype of the specified variable has changed. Action: None needed. ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled. Cause: The partitioning method (LIST, RANGE, or CONCAT) or the partition dimension of the partition template is sufficiently different from what it was when the code was compiled that the code must be recompiled. Action: None needed. ORA-33450: (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled. Cause: The dimensionality of the specified object has changed. Action: None needed. ORA-33452: (ESDREAD06) Discarding compiled code for workspace object because number is now dimensioned by workspace object. It was dimensioned by workspace object when the code was compiled. Cause: The dimensionality of the specified object has changed. Action: None needed. ORA-33454: (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled. Cause: The specified object has changed. Action: None needed. ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program. Cause: The type of the specified object has changed. Action: None needed. ORA-33458: (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled. Cause: The type of the specified object has changed. Action: None needed. ORA-33460: (ESDREAD10) Discarding compiled code for workspace object because object workspace object is not in analytic workspace string. Cause: The specified object is not in the same analytic workspace it was in when the compiled object was compiled. Action: None needed. ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string. Cause: The specified object was not in the same analytic workspace it was when the compiled object was compiled Action: None needed. ORA-33468: (ESDREAD13) Discarding compiled code for workspace object because number is no longer a surrogate of dimension workspace object. Cause: When the compiled code was saved, the specified object was a surrogate of a certain dimension. Now the specified object is a surrogate of a different dimension. Action: No action needed; program automatically recompiles. ORA-33557: (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it. Cause: User tried to insert or delete a value of the specified dimension while some loop over that dimension was active. The loop could be an explicit FOR or ACROSS loop, or a natural expression evaluation or OLAP_TABLE loop. Also, it could be a loop over the dimension itself or over a derived dimension (like a composite or partition template) or dimension alias that includes it. The insert or delete could be explicitly caused by the MAINTAIN command. It is also possible that the user attempted to assign a value to a variable or partition dimensioned by a composite during a loop over that composite using a qualified data reference (QDR), and that the exception was generated by the engine"s attempt to insert a new position in the composite to hold the new value. Action: Move the dimension maintenance or QDR-based variable assignment outside the dimension loop. ORA-33558: (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value. Cause: A LIMIT or MAINTAIN was attempted on the named language dimension while the boolean option LOCK_LANGUAGE_DIMS was set to YES. Action: SET LOCK_LANGUAGE_DIMS to NO and retry the MAINTAIN or LIMIT. ORA-33625: (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object. Cause: User used the APPEND keyword on a CONCAT target in a FILEREAD, SQL FETCH or SQL SELECT command. Action: APPENDing a value to one of the CONCATs leaves automatically appends to the CONCAT. ORA-33883: (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target. Cause: User gave the TEMPORARY keyword in the definition of an external partition whose target variable was previously defined. Action: Any storage characteristics of the external partition are determined by the target variable. These attributes should be set when the target is defined, not when the external partition is defined. ORA-33911: (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string. Cause: User attempted to define an object that requires a certain compatibility setting in an AW that has not been upgraded to that compatibility level. Action: Make sure that the database is running in the appropriate compatibility mode, and upgrade the AW. ORA-33918: (MAKEDCL33) You cannot define a surrogate of dimension workspace object because it is a string. Cause: Not all kinds of dimensions can have surrogates. The user attempted to define a surrogate of a prohibited kind of dimension. Action: Do not attempt to define a surrogate on this dimension. ORA-33920: (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER. Cause: The user attempted to define a surrogate without specifying a valid data type. Action: Specify the data type (ID, NTEXT, TEXT, NUMBER, or INTEGER) in the definition of the surrogate. ORA-33922: (MAKEDCL35) You cannot define a surrogate of dimension workspace object because it is a time dimension. Cause: The user attempted to define a surrogate on a dimension that has type DAY, WEEK, MONTH, or YEAR. Action: Do not attempt to define a surrogate on this dimension. ORA-33998: (MODCOMP12) You cannot use both workspace object and workspace object as model dimensions, because workspace object is a surrogate of workspace object. Cause: The user attempted to include both a dimension and its surrogate in the DIMENSION statement of a model. Action: Use either the dimension or the surrogate in the DIMENSION statement of the model, but not both. ORA-34000: (MODCOMP13) You cannot use both workspace object and workspace object as model dimensions, because they are both surrogates of dimension workspace object. Cause: The user attempted to include two dimension surrogates of the same dimension in the DIMENSION statement of a model. Action: Use either of the two surrogates in the DIMENSION statement of the model, but not both. ORA-34001: (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension. Cause: Either two concat dimensions which share a common leaf dimension, or a concat and one of its leaves where both specified in the DIMENSION statement(s). Action: Do not specify overlapping concat dimensions, or any leaves of specified concat dimensions. ORA-34019: (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE. Cause: User attempted to MAINTAINT ADD or DELETE a list value from a RANGE or CONCAT partition template. Action: Partitioning in a RANGE or CONCAT partition template cannot be changed using the MAINTAIN command. ORA-34021: (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object. Cause: User attempted to MAINTAINT ADD or DELETE a list value from a LIST partition template, but didn"t specify which partition to add to or delete from. Action: Specify the partition: maintain (template) add to partition (partitionname) (values) or maintain (template) delete from partition (partitionname) (values) ORA-34059: (MSEXECUT12) You cannot delete non session-only dimension values from unique concat dimension workspace object. Cause: The user tried to apply MAINTAIN DELETE to a non-SESSION value. Action: Only use MAINTAIN DELETE to remove SESSION values from a concat dimension. ORA-34061: (MSEXECUT11) Session-only values cannot be added to non-unique concat dimension workspace object, or any of its base dimensions. Cause: Only UNIQUE concat dimensions can have custom member values. Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry. ORA-34141: (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object. Cause: User used the ASSIGN keyword on a DIMENSION target in a FILEREAD, SQL FETCH or SQL SELECT command. Action: To create a new dimension value in a FILEREAD, SQL FETCH or SQL SELECT command, use the APPEND keyword. ORA-34143: (MXCGPUT02) You cannot assign values to SURROGATE workspace object because it is type INTEGER. Cause: The user attempted to assign a value to a dimension surrogate whose data type is INTEGER. INTEGER surrogates, like INTEGER dimensions, cannot have values assigned to them. They can only be referenced by position. Action: Do not attempt to assign values to an INTEGER surrogate. Values will automatically appear and disappear from the INTEGER surrogate as positions are added to or removed from the underlying dimension. ORA-34145: (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object. Cause: User used the APPEND keyword on a SURROGATE target in a FILEREAD, SQL FETCH or SQL SELECT command. Action: To assign a value to a SURROGATE in a FILEREAD, SQL FETCH or SQL SELECT command, use the ASSIGN keyword. ORA-34164: (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue. Cause: A local relation or valueset has become invalid, most probably because an object used by the currently executing program has been deleted. Action: This is an internal error that should be referred to Oracle technical support. ORA-34177: (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it. Cause: User attempted to CHGDFN DELETE a partition template, but some partitioned variable had data in the partition specified for deletion. Action: Drop the partitions that are causing the problem, then retry. ORA-34179: (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE. Cause: User specified an object that is not a partition template where a partition template is required. Action: Supply the name of a partition template. ORA-34181: (MXCHGDCL21) workspace object is not a partitioned VARIABLE. Cause: User specified an object that is not a partitioned variable in a place where a partitioned variable is required. Action: Supply the name of a partitioned variable. ORA-34183: (MXCHGDCL22) Partition number already exists. Cause: User attempted to ADD a partition that already existed to a partitioned variable. Action: None required - the partition already exists. ORA-34210: (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it. Cause: The user attempted to redefine a conjoint dimension as a composite, but the conjoint has one or more surrogates defined. A dimension that has surrogates cannot be redefined as a composite. Action: Either delete all surrogates for the dimension, or do not attempt to redefine the dimension as a composite. ORA-34243: (MXDCL11) You can only use the string keyword when defining a COMPOSITE. Cause: User supplied the COMPRESSED keyword when defining an object that was not a COMPOSITE. Action: If the intent is to create a compressed composite, make sure that the object type is COMPOSITE. Otherwise, remove the COMPRESSED keyword from the command string and rerun. ORA-34260: (MXDCL25) You cannot use number to dimension a string because it is, or involves, a dimension composite. Use the composite"s bases instead. Cause: The user attempted to use a COMPOSITE in the dimension list of an object that does not allow for such dimensions. Action: Use the base dimensions of the COMPOSITE in the dimension list. ORA-34276: (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension. Cause: The user attempted to use NUMBER(Precision) or NUMBER(Precision, Scale) as the datatype in a definition for some object other than a DIMENSION or VARIABLE, such as a FORMULA or PROGRAM. This error can also be produced in cases where a NUMBER data type is not allowed at all. Action: Use the NUMBER type without specifying a precision or scale. If a NUMBER data type is not allowed at all, this fix will only change the exception message to something more specific. ORA-34279: (MXDCL37) CONCAT can only be used when defining a DIMENSION. Cause: The CONCAT keyword was used incorrectly. Action: Retry the command without the CONCAT keyword. ORA-34286: (MXDCL53) workspace object cannot be used in this context because it is a string. Cause: User specified a dimension composite, conjoint, or partition template in a place where that kind of dimension is not allowed. For instance, a relation cannot be dimensioned by a composite, and only a variable can dimensioned by a partition template. Action: Usually, the offending dimension can be replaced with its bases. For instance, a relation cannot be dimensioned by a a composite of PRODUCT and GEOG, but it can be dimensioned by both PRODUCT and GEOG instead. ORA-34296: (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale). Cause: The user attempted to define a NUMBER dimension without specifying a precision. The proper format for declaring a number dimension is NUMBER(Precision) or NUMBER(Precision, Scale). NUMBER with no precision or scale is not allowed. Action: Use NUMBER(Precision) or NUMBER(Precision, Scale) to specify the datatype of a NUMBER dimension. ORA-34342: (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it. Cause: This is an informational message that reminds you that you may not save changes to the specified analytic workspace. Action: None, unless it was desired to save changes to the analytic workspace. In that case, detach and reattach the analytic workspace read-write. ORA-34344: (MXDSS03) Analytic workspace string is not attached. Cause: The command attempted to operate on an analytic workspace that is not currently attached, or the name of the analytic workspace is misspelled. Action: Attach the analytic workspace or correct the spelling. ORA-34346: (MXDSS04) The string analytic workspace cannot be detached. Cause: The specified analytic workspace is an internal workspace and may not be detached by the user. Action: Specify a different analytic workspace to detach. ORA-34348: (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace. Cause: The command attempted to operate on an internal analytic workspace used by the system. Action: Specify a different analytic workspace. ORA-34350: (MXDSS06) string is an open analytic workspace. Cause: The specified analytic workspace is currently in use. Action: The desired action requires an analytic workspace that is not currently in use. ORA-34357: (MXDSS10) string is not an alias of analytic workspace string. Cause: User attempted to use AW UNALIAS on a non-existent alias. Action: Make sure that the command specified the correct analytic workspace and alias. The alias must have been assigned (using AW ALIAS) during the current session and must not have been removed by a previous AW UNALIAS or AW DETACH command. ORA-34358: (MXDSS14) number other users reading Cause: Used for AW LIST output formatting when %d > 1 Action: None ORA-34359: (MXDSS11) string appears twice in the alias list. Cause: User included the same name twice in the alias list of an AW ALIAS or AW UNALIAS command. Action: Remove the duplicate name and try again. ORA-34360: (MXDSS15) number other users writing Cause: Used for AW LIST output formatting when %d > 1 Action: None ORA-34361: (MXDSS12) number other user reading Cause: Used for AW LIST output formatting when %d == 1 Action: None ORA-34363: (MXDSS13) number other user writing Cause: Used for AW LIST output formatting when %d == 1 Action: None ORA-34481: (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object. Cause: User attempted to use the MAINTAIN command with some keyword other than ADD or DELETE on a partition template. Action: It is not possible to MAINTAIN a partition template, except to add or delete values of a partition list. ORA-34487: (MXMAINT08) You cannot string values of non-unique concat dimension workspace object. Cause: The specified MAINTAIN operation can only be applied to UNQUE concats. Action: Use the CHGDFN command to change the concat dimension to UNIQUE and retry. ORA-34489: (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE. Cause: The user attempted to use the MAINTAIN command on a dimension surrogate. The MAINTAIN command can only be used with real dimensions, not surrogates. Action: Use the MAINTAIN command to modify the underlying dimension of the surrogate instead. ORA-34514: (MXOPERR) You cannot string string data in the expression that begins with "string". Cause: The user attempted an invalid operation. Action: none ORA-34656: (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax Cause: A SQL UPDATE or DELETE statement tried to use the CURRENT of syntax with a WHERE clause containing multiple conditions. Action: When using the CURRENT OF syntax make sure it is the only condition in the WHERE clause. ORA-34719: (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion Cause: When character set conversion happens between TEXT and NTEXT 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. Note: This message is the OLAP equivalent of ORA-12713. ORA-34722: (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string Cause: Some operation required a string to be converted into a different character set, but the string contained characters that didn"t exist in the new character set. Action: Choose different character sets. ORA-34726: (NLSCHARSET06) CAUTION: String truncated during character set conversion from string to string Cause: Some operation required a string to be converted into a different character set. The string required more bytes in the new encoding, and exceeded some byte limit on its allowable length, causing some characters to be removed from the end of the string. Action: If the byte limit is due to using the ID datatype, consider using the CHAR datatype instead. If the byte limit is due to the limit of 4000 bytes per line of CHAR data, break the long line up into multiple lines. ORA-34802: (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled. Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. The current operation is aborted, and the Analytic Workspace detached. Action: Change the called SQL procedure to avoid the ROLLBACK ORA-34840: (OPCREATE01) The string option must be declared with datatype string. Cause: An attempt was made to declare the option with the wrong datatype. Action: Declare the option with the correct datatype. ORA-34841: (OPCREATE02) The string option must be declared with the READONLY attribute. Cause: An attempt was made to declare the option without the READONLY attribute. Action: Declare the option READONLY. ORA-34871: (PERMIT06) Session-only value "value" of workspace object has been deleted because a PERMIT change has revealed a duplicate value. Cause: Execution of a PERMIT command revealed a permanent dimension or surrogate value having the same name as the SESSION value. Action: If the SESSION value is still needed, add it with a different name. ORA-34896: (PPMONTHS00) At least 12 month names must be given. Only number were provided. Cause: There must be at least one name for each month. Not enough names were provided. Action: Provide at least 12 names. ORA-34897: (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option. Cause: There is at least one blank line in the string populating the MONTHNAMES option. We do not allow blank month names. Action: Remove the blank line(s) from the string. ORA-34900: (PPWKDAYS00) At least 7 day names must be given. Only number were provided. Cause: There must be at least one name for each day. Not enough names were provided. Action: Make sure there are at least 7 names in the string. ORA-34901: (PPWKDAYS01) Blank lines are not allowed in the DAYNAMES option. Cause: There is at least one blank line in the string populating the DAYNAMES option. We do not allow blank day names. Action: Remove the blank line(s) from the string. ORA-35016: (QFCHECK00) The analytic workspace and EIF file definitions of workspace object have a mismatched type. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35017: (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35018: (QFCHECK01) The analytic workspace and EIF file definitions of workspace object have a mismatched data type. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35019: (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35020: (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35021: (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35022: (QFCHECK03) The analytic workspace and EIF file definitions of workspace object have a mismatched relation. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35023: (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35024: (QFCHECK04) The analytic workspace and EIF file definitions of workspace object have mismatched time dimension attributes. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35026: (QFCHECK05) The analytic workspace and EIF file definitions of workspace object have a mismatched ALIASOF dimension. Cause: Importing from an EIF file or LOB into an existing Analytic Workspace object failed because the definition of the existing object was too different from the definition of the object in the EIF file or LOB. Action: Import the object into an Analytic Workspace that does not already contain an object with the same name. ORA-35062: (QFGET01) Duplicate files found for extension number number of EIF file string. Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and found two EIF extension files with the same name (differing at most by the case used in the final name component. Action: Delete, rename or move any files that are not to be read by IMPORT. ORA-35066: (QFGET03) Extension number number is missing for EIF file string. Cause: IMPORT searched the directories specified in EIFEXTENSIONPATH and could not find the appropriately numbered extension file. Action: Move the missing file into one of the searched directories. ORA-35071: (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string. Cause: User attempted to import from an EIF file that was created by a newer version of the product into an AW that was created by a older version of the product. Action: Make sure that the compatibility mode parameter in the init.ora of the importing instance specifies a version that is at least as high as the parameter was in the exporting instance. Then, convert the AW to the latest storage format and reexecute the import command. Alternatively, change the EIFVERSION option of the exporting instance to a lower number, recreate the EIF file, and import the new file. ORA-35074: (QFHEAD02) EIF file string cannot be read by this version of string. Cause: The EIF file was created with an internal version number indicating it may contain objects that are not compatible with the current Oracle OLAP version, or the EIF file is in an obsolete format. Action: If possible, set EIFVERSION in the exporting instance to a lower number, recreate the EIF file, and import the new file. ORA-35076: (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string. Cause: IMPORT could not recognize the character set specification in the EIF file. Action: Check the imported text data. If it was not imported correctly, recreate the EIF file with a character set supported by the current Oracle version. ORA-35078: (QFHEAD05) An EIF extension file header for string is not in the correct format. Cause: An EIF extension file in multi-file IMPORT did not contain correct header information. Action: Check to be sure that EIFEXTENSIONPATH is set correctly and that all the extension files for the current IMPORT were created by the same EXPORT command as the main EIF file. ORA-35095: (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated. Cause: The data in the EIF file was exported from a dimension with wider values than the target dimension will accommodate. Action: Change the definition of the target dimension, or check to be sure that multiple values from the target dimension have not become identical during the import process. This could cause data loss as data from later dimension values overstores data imported earlier. ORA-35180: (SNSYN103) The format of the OUTFILE command is: OUTFILE [APPEND] {EOF | TRACEFILE | filename [NOCACHE] [NLS_CHARSET name]} Cause: The user specified incorrect syntax for the OUTFILE command. Action: none ORA-35276: (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ] Cause: The user used incorrect syntax for the ALLOCATE command. Action: Correct the calling syntax. ORA-35280: (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #] Cause: The user used incorrect syntax for the AGGREGATE command. Action: Correct the calling syntax. ORA-35282: (SNSYN166) The format of the AGGREGATE function is: AGGREGATE(varname USING aggmap-name [COUNTVAR intvar-name] [FORCECALC]) Cause: The user used incorrect syntax for the AGGREGATE function. Action: Correct the calling syntax. ORA-35578: (SQLOUT11) SQL cursor "number" cannot be used with CURRENT OF syntax Cause: The CURRENT OF syntax in the WHERE clause tried to use a cursor that was not declared with the FOR UPDATE [ of ] SQL syntax. Action: Add the FOR UPDATE [ OF ] SQL syntax to the cursor specified. ORA-35587: (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels. Cause: The nesting of table functions with the PREDMLCMD token populated with an OLAP DML expression that use the embedded SQL support to access another table function which contains a table functions with the PREDMLCMD token filled in with an OLAP DML expression that uses the embedded SQL support. Action: Reduce the level of nesting between table functions and OLAP DML embedded SQL support. ORA-35756: (VCTODT02) "number" is not a valid date because number is out of range for a year. Cause: n"%1p" Action: none ORA-35810: (XSINPUTERR) The command has requested more input than was supplied in the command string. Cause: The command required input that was not supplied in the string. Action: Reexecute the command with the required input. ORA-35917: (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string. Cause: User attempted to apply the HIDE command to a model in an AW that has not been upgraded to the necessary compatibility level. Action: Make sure that the database is running in the appropriate compatibility mode, and upgrade the AW. ORA-35952: (XSSPFC01) The string dimension workspace object and the string dimension workspace object must have the same number of values in status for SPFCEXEC method number. Cause: This method requires the named dimensions to have the same number of values in status, but the user provided statuses of different lengths. Action: Relimit the dimensions so that their status lengths are the same. ORA-36154: (XSMXAGGR01) workspace object is not a data variable. Cause: An object was specified on the Aggregate command line that was not a variable Action: Specify a variable instead ORA-36155: (XSMXAGGRFROM) workspace object must be a variable or formula of a similar data type to workspace object to be used with FROM, or a TEXT variable or formula to be used with FROMVAR. Cause: The user specified an illegal variable for use with FROM or FROMVAR on the AGGREGATE command line Action: Specify a legal variable instead ORA-36157: (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword. Cause: The user specified AUTOCOMMIT but not AUTOUPDATE on the AGGREGATE command line, which is illegal Action: Either also specify AUTOUPDATE or don"t specify AUTOCOMMIT ORA-36160: (XSMXAGGR04) You cannot use string on scalar VARIABLE workspace object. Cause: The user tried to run the AGGREGATE or AGGCOUNT command or function on a scalar variable. Action: Specify a dimensioned variable instead ORA-36161: (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR. Cause: The user specified the same variable as both an aggregation variable and a COUNTVAR Action: Specify a different COUNTVAR ORA-36162: (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string. Cause: The user specified a non-INTEGER variable as a COUNTVAR for aggregation Action: Redefine the COUNTVAR to be an INTEGER ORA-36163: (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time. Cause: The user named several variables to be AGGREGATED within a call to the AGGREGATE function. Action: The AGGREGATE function should be used to produce a single numeric value from aggregating a single variable. The AGGREGATE command can be used to precompute aggregations of several different variables. ORA-36164: (XSMXAGGR07) When using the COUNTVAR clause, the number of variables to be aggregated (number) must match the number of COUNTVAR variables (number). Cause: The user specified a COUNTVAR clause to the AGGREGATE command, but the number of COUNTVAR variables specified did not match the number of variables to be aggregated Action: Specify a separate COUNTVAR for each variable ORA-36165: (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property. Cause: An attempt was made to add the $COUNTVAR property to a variable which already had an AGGCOUNT, or vice versa. Action: Delete the already existing $COUNTVAR property or AGGCOUNT first. ORA-36166: (XSMXAGGR08) workspace object is not a VARIABLE. Cause: An attempt was made to perform an AGGREGATE or other action on an object which is not a variable. Action: Specify a variable instead. ORA-36167: (XSAGGRFORM) workspace object is an illegal AGGMAP for aggregating a FORMULA. Cause: The user attempted to aggregate a FORMULA using an AGGMAP that is not valid for aggregating FORMULAs. The AGGMAP must specify PRECOMPUTE(NA) for all relation lines and must not specify any caching. Action: Correct the AGGMAP so it is legal for aggregating a FORMULA. ORA-36168: (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object Cause: The user specified a COUNTVAR variable which is missing at least one dimension of the aggregation variable Action: Specify a COUNTVAR variable which has at least as many base dimensions as the aggregation variable ORA-36170: (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string. Cause: The user specified a WEIGHT variable or formula which wasn"t numeric or boolean Action: Specify a numerical or boolean weight instead ORA-36174: (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA. Cause: The user specified something that was not a variable, a relation or a formula as a weight for AGGREGATE Action: Specify a valid variable, relation or formula instead ORA-36176: (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE. Cause: The user specified an illegal relation as a weight. The relation might have been multidimensional, not a self-relation, or not a relation over one of the bases of the aggregation variable. Action: Specify a valid self relation over one of the bases of the aggregation variable. ORA-36178: (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command. Cause: The user used the ALLOCMAP command to define the AGGMAP, so the AGGMAP can only be used with the ALLOCATE command, or the AGGMAP has no contents attached to it. Action: Use the AGGMAP command to define the AGGMAP. ORA-36179: (XSNOAGM) No AGGMAP was specified for VARIABLE workspace object. Cause: The user used the AGGREGATE command without specifying an AGGMAP on the command line, with a variable which had no $AGGMAP property. Action: Specify an AGGMAP on the AGGREGATE command line, or add the $AGGMAP property to the variable in question. ORA-36180: (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object. Cause: When using AGGREGATE, only simple permissions and permissions on base dimensions are valid. Action: Remove the permissions clause from the variable causing problems. ORA-36181: A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it. Cause: The user attempted to add both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties to a single variable. Action: Remove the existing property before applying the new one. ORA-36182: (XSAGGR09) Could not locate a value for variable number in measure dimension workspace object. Cause: A measure dimension was supplied in the AGGMAP, but a position for the variable was not found in it. Action: Add a position for the variable in the measure dimension. ORA-36184: (XSAGGR10) You do not have sufficient permissions for the variable workspace object. Cause: The user lacked the permissions necessary for the aggregation variable. Action: Remove the restricting permissions from the variable or base dimension. ORA-36185: (XSAGGR11) workspace object does not have any AGGCOUNT information. Cause: User attempted an operation (such as the AVERAGE aggregation operator or the AGGCOUNT function) that requires a variable to have AGGCOUNT information on a variable that does not. Action: Define the variable using the WITH AGGCOUNT clause, or use the CHGDFN ADD AGGCOUNT command to enable AGGCOUNT for the variable. ORA-36188: (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support. Cause: Either someone improperly changed the COUNTVAR variable, or AGGREGATE has an error. Action: Set the COUNTVAR variable to NA before starting AGGREGATE. If you previously set the COUNTVAR variable to NA, then contact Oracle OLAP technical support. ORA-36198: (XSAGGR33) The AGGREGATE operator string does not require a weight, but ARGS variable workspace object specified workspace object as a weight. Cause: The ARGS variable specified a weight even though one is not needed. Action: Modify the ARGS variable so that it does not specify a weight for that operation. ORA-36200: (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one. Cause: The given operator requires a WEIGHT specification, but the ARGS variable did not supply one. Action: Modify the ARGS variable to specify a weight for the operation. ORA-36202: (XSAGOP01) "number" is not a valid aggregation operator. Cause: An invalid string was provided for an aggregation operator. Action: Check the spelling of the operator to make sure you are specifying a valid one. ORA-36204: (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN. Cause: An invalid NAOPERATOR was specified. Action: Specify HFIRST, HLAST or HEVEN. ORA-36206: (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST. Cause: An invalid REMOPERATOR was specified. Action: Specify one of the legal operators. ORA-36208: (XSAGOP05N) In AGGMAP workspace object, you can only specify NAOPERATOR string with the PROPORTIONAL or EVEN operators, not string. Cause: The user specified an NAOPERATOR when you were not using PROPORTIONAL or EVEN. Action: Remove the NAOPERATOR clause from the RELATION line. ORA-36210: (XSAGOP05R) In AGGMAP workspace object, you can only specify the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN operators, not string. Cause: The user specified a REMOPERATOR without using PROPORTIONAL, EVEN, or HEVEN. Action: Remove the REMOPERATOR clause from the RELATION line. ORA-36212: (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string. Cause: The user specified MIN, MAX, FLOOR, or CEILING when using an operator other than PROPORTIONAL. Action: Remove the incorrect argument from the RELATION line. ORA-36220: (XSLPDSC01) All dimensions in LIST number are also in the IGNORE clause. Cause: One of the dimension lists in the dimension loop descriptor had no base dimensions except those in the IGNORE list. This leaves no dimensions for looping over. Action: Fix the dimension loop descriptor. ORA-36221: (XSLPDSC02) LIST number and LIST number have different base dimensions. Cause: The base dimensions of the dimension lists given in the loop descriptor do not match. Action: Ensure that each dimension list has the same set of looping base dimensions. If necessary, use IGNORE within a lists to discard base dimensions that should not be looped. ORA-36222: (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object Cause: An IGNORE or DENSE list in a dimension loop descriptor included the dimension twice, included two different valuesets of the dimension, or includes the dimension and a valueset of the dimension. Action: Only use the dimension or a valueset of the dimension once in an IGNORE or DENSE list. ORA-36223: (XSLPDSC04) object workspace object in IGNORE or DENSE list has illegal type Cause: An IGNORE or DENSE list in a dimension loop descriptor included and object that was not a dimension or a valueset, was a conjoint dimension, or was a dimensioned valueset. Action: Only use simple dimensions and undimensioned valuesets in the IGNORE or DENSE list. ORA-36224: (XSLPDSC05) workspace object is not a loop dimension Cause: An IGNORE or DENSE list in a dimension loop descriptor referenced a dimension (or a valueset of a dimension) that was not a base dimension of the loop dimension list. Action: Remove the dimension or valueset from the IGNORE or DENSE list. ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP. Cause: The AGGMAPINFO function was called with an object that is not an AGGMAP. Action: Modify the call to AGGMAPINFO to specify an AGGMAP object. ORA-36260: (XSAGHIERPART00) Aggregating from partition %J to partition %J over hierarchy workspace object creates an increase in sparsity. Cause: In the partition creation / aggmap creation a situation developed such that when aggregating over a particular dimension of the aggmap a partition boundary was crossed such that the sparsity of the target partition included dimensions that were not in the sparsity of the source partition. Since the process of aggregation always densifies rather than sparsifying this is an extremely suboptimal design and it is not supported by the aggregate system. Action: Set up your partitioning such that for any partition boundary the source and target partitions of the aggregation will always move towards denser partitions. For any child (c) and any parent (p) where (c) and (p) are in different partitions it must be the case that the parent partition contains no dimension in the composite that the child partition does not contain in its composite. ORA-36261: (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J. Cause: The partitioning scheme was such that while aggregating there exists a cell (m) such that both one of its descendants and one of its ancestors are both in the referenced partition, while (m) is in a different partition. Action: Change the partitioning scheme. ORA-36266: (XSCGMDLAGG00) Invalid context for the AGGREGATION function Cause: The AGGREGATION function was used outside of the MODEL context. Action: Use AGGREGATION only in a model. ORA-36267: (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference. Cause: A dimension qualification was specified for a valueset with no dimensions. Action: Remove the qualification. ORA-36268: (XSCGMDLAGG01) "string" is not a valid dimension value. Cause: The AGGREGATION parameter list included a value that does not exist in the MODEL dimension that contains the target of the AGGREGATION Action: Specify only values from the appropriate MODEL dimension ORA-36269: (XSCGMDLAGG10) "workspace object" does not exist or is not a dimension. Cause: A nonexistent or invalid object was specified as a QDR dimension. Action: Specify existing dimensions only. ORA-36270: (XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values. Cause: One or more duplicate values appeared in the AGGREGATION parameter list. Action: Remove the duplication. ORA-36271: (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object. Cause: A QDR dimension was specified that does not appear in the valueset"s dimension list. Action: Specify only dimensions in the valueset"s dimension list. ORA-36272: (XSCGMDLAGG04) "workspace object" is not a valid operator for the AGGREGATION function. Cause: An invalid AGGREGATION operator was specified. Action: Correct the invalid operator. ORA-36273: (XSCGMDLAGG12) Dimension workspace object appears more than once in the QDR. Cause: A dimension was specified more than once in the QDR. Action: Remove the duplication. ORA-36274: (XSCGMDLAGG05) The operator used in this equation needs a weight variable. Cause: An invalid weight variable was specified. Action: Correct the invalid weight variable. ORA-36275: (XSCGMDLAGG13) string is not a valid workspace object. Cause: A value was specified that does not exist in the QDR dimension. Action: Specify an existing value. ORA-36276: (XSCGMDLAGG06) The current operator does not need a weight variable. Cause: A weight variable was specified in a context that does not support it. Action: Remove the weight variable. ORA-36278: (XSCGMDLAGG07) workspace object does not exist or is not valueset. Cause: A nonexistent or invalid object was specified where a valueset is required. Action: Specify an existing valueset only. ORA-36280: (XSCGMDLAGG08) Valueset workspace object does not contain values of any dimension of the current model. Cause: AGGREGATION specified a valueset of a dimension not listed in a DIMENSION statement for the current model. Action: Add the valueset"s dimension to the model"s DIMENSION list, or choose a different valueset. ORA-36290: (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support dimensions of type NUMBER. Cause: The user tried to export a NUMBER dimension to an EIF file with the EIFVERSION option set to a number less than 80000. Versions previous to that eversion do not support NUMBER dimensions. Action: A NUMBER dimension cannot be used in a version of older than 9.2.0. If the EXPORT file is going to be read by version 9.2.0 or higher, set EIFVERSION to a number greater than or equal to 80000 and execute the EXPORT command again. ORA-36312: (PHYS00) workspace object must be a dimension or dimensioned variable. Cause: The user specified an invalid OLAP object while attempting to use the PHYSICAL function Action: Specify a valid object ORA-36314: (PHYS01) workspace object must be a dimension, relation or variable. Cause: The user specified an invalid OLAP object while attempting to use the PHYSICAL command Action: Specify a valid object ORA-36316: (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another. Cause: The user specified an invalid relation while attempting to use the PHYSICAL command Action: Specify a valid relation ORA-36341: (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template) Cause: Bad syntax Action: Correct syntax ORA-36342: (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap] Cause: The syntax for the CLEAR command was invalid. Action: Modify your syntax using the correct format. ORA-36376: (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero. Cause: A calculation in the current AGGREGATE command attempted to divide by zero as a result of an AVERAGE, WAVERAGE, HAVERAGE or HWAVERAGE operation. Action: Either fix the data, or set DIVIDEBYZERO to YES to return NA instead of signaling an error. ORA-36378: (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object. Cause: While running AGGREGATE in threaded mode, you attempted to specify a WEIGHT variable in another analytic workspace. Action: Use a weight variable from the same analytic workspace as the aggmap and rollup variable. ORA-36380: (AGGRECURSE) AGGREGATE was called recursively, which is not allowed. Cause: A model, NATRIGGER, or other object called the AGGREGATE function or command while another AGGREGATE function or command was already in progress. Action: Modify your objects so that they do not need to have two AGGREGATE commands or functions executing at once. ORA-36389: (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J. Cause: The user is attempting to use partitions as a means of sparsity control, however they have set up their partitions in a manner that simply makes no sense. It is a simple fact that during aggregation data becomes more dense, not less dense, and yet their partitions indicate the opposite. Action: Modify the partition template add the specified dimension into the source composite, or removing it from the target composite. ORA-36391: (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object. Cause: The user specified objects whose dimensionality didn"t match Action: Break up the CLEAR command into multiple commands where the dimensionality of the objects matches ORA-36392: (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP. Cause: The user didn"t specify an AGGMAP with the CLEAR command Action: Specify the AGGMAP used to aggregate the variable being cleared ORA-36393: (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword. Cause: The user didn"t use the ALL keyword when using CHANGES or CACHE Action: Specify the ALL keyword ORA-36394: (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive. Cause: The user attempted to CLEAR an AGGMAP using a directive other than CACHE Action: Amend the CLEAR line to only use the CACHE keyword with AGGMAPs. ORA-36398: (XSSPROP01) Property name "number" is invalid because only system-reserved property names can begin with "$". Cause: The user attempted to add a property which starts with $ but is not a reserved property name Action: Remove the $ from the property name ORA-36399: (XSSPROPDTYPE) The data type of property string must be string. Cause: The used tried to set a system-reserved property on an OLAP object to a value with an illegal datatype Action: Set the property with the proper datatype ORA-36400: (XSSPROP02) workspace object is not a valid variable name. Cause: Not a valid variable name Action: Change to a valid variable name ORA-36401: (XSSPROPOTYPE) Property string may only be applied to objects of type string. Cause: The user applied a reserved property name to an incorrect object type Action: Apply the property to the correct object ORA-36402: (XSSPROP03) The property "$string" requires a leading "$" because it is a system-reserved property name. Cause: The user tried to specify a property name which is reserved, but did not use a leading $ Action: Either add a leading $ or choose another property name ORA-36403: (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object. Cause: The user tried to specify an illegal value for a special property Action: Specify a legal value. ORA-36404: (XSSPROP04) Property string cannot be applied to an undimensioned (scalar) TEMPORARY variable. Cause: The user applied a reserved property name to an incorrect object type Action: Apply the property to the correct object ORA-36405: (XSSPROP05) Property ignored for object workspace object: Cause: A property was ignored during import. Action: Refer to the message that follows this one and correct the error it describes. ORA-36406: (VCACHE00) "number" is an invalid value for the VARCACHE option. The only permissible values are "SESSION", "VARIABLE", and "NONE". Cause: The user tried to assign an invalid value to the VARCACHE option Action: Assign one of the valid values ORA-36410: (VCACHE03) "number" is an invalid value for the $VARCACHE property. The only permissible values are "DEFAULT", "SESSION", "VARIABLE", and "NONE". Cause: The user tried to assign an invalid value to the $VARCACHE property on a variable Action: Assign one of the valid values ORA-36608: (XSAGHOVERFLOW) The depth of the hierarchies encountered while processing a composite dimension in AGGREGATE caused a counter overflow. Cause: The depth of the hierarchies that are part of a composite exceeded 4 billion levels during the merge. Action: Reduce the number of levels in the hierarchies, reduce the number of dimensions in the composite, or do not aggregate over all dimensions at once. ORA-36610: (XSLMS00) Unable to locate a message file for OLAP message: value Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace failed to retrieve a user message. Action: Contact support. ORA-36612: (XSLMS01) invalid OLAP message number: value Cause: An internal OLAP DML program in the EXPRESS Analytic Workspace attempted to retrieve a non-existent message. Action: Contact support. ORA-36618: (XSAGMODDIM00) workspace object is not a valid model for AGGMAP ADD. Cause: The model failed one of the following tests: 1) only one dimension (aside from LAG/LEAD dimensions); 2) assignment to dimension values only; 3) a single simple solution block; 4) no time-series functions with variable step values. Action: Edit the model so that it conforms to the above requirements. ORA-36628: (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object. Cause: The dimension of the model must match a hierarchy of the aggmap. Action: Add a RELATION statement to the AGGMAP for that dimension. ORA-36630: (XSDUNION00) An empty base dimension list was specified in the concat dimension definition. Cause: An empty concat dimension list was specified. Action: Specify a valid list of dimensions when defining a concat dimension. ORA-36632: (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE. Cause: Attempt was made to CHGDFN a concat, which is already non-unique, to NOT UNIQUE. Action: Since the concat is already non-unique, this command is unnecessary. ORA-36634: (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base. Cause: The user cannot specify INTEGER base dimensions when defining a concat dimension. Action: Change the datatype of the INTEGER base dimension, or omit it from the concat. ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition. Cause: Base dimensions of a unique concat must have TEXT or ID datatypes. Action: Specify a valid list of dimensions when defining a unique concat dimension. ORA-36636: (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension. Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat. Action: CHGDFN any dependent unique concat dimensions to NOT UNIQUE and retry. ORA-36637: (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object. Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat. Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry. ORA-36638: (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object. Cause: A non-unique concat dimension cannot be used as a base of a dependent unique concat. Action: CHGDFN any non-unique concat base dimensions to UNIQUE and retry. ORA-36639: (XSDUNION18) UNIQUE cannot be applied to this concat dimension because leaves workspace object and workspace object share the value number. Cause: Unique concat base dimensions cannot contain duplicate values. Action: Use MAINTAIN RENAME to change one of the duplicate values and retry. ORA-36640: (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype. Cause: Base dimensions of a unique concat must have TEXT or ID datatypes. Action: none ORA-36641: (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values. Cause: The UNIQUE keyword was not specified in the concat dimension definition, and is required if any of its base dimensions contain custom member values. Action: Define the concat as UNIQUE, or remove all base custom member values. ORA-36642: (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object. Cause: Duplicate concat leaf dimension was found. Action: Remove duplicate concat base dimensions and retry. ORA-36643: (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values. Cause: Only UNIQUE concat dimensions can have custom member values or base dimensions which contain custom member values. Action: Remove all custom member values from the concat and all of its bases, and retry. ORA-36644: (XSDUNION07) Concat dimension workspace object contains a previously detected leaf dimension. Cause: Concat dimension contains a previously detected leaf dimension. Action: none ORA-36646: (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension. Cause: UNIQUE keyword was used with an invalid object. Action: Retry without the UNIQUE keyword. ORA-36648: (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE. Cause: Attempt to change a concat dimension to UNIQUE, but it is already UNIQUE. Action: none ORA-36650: (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number. Cause: Unique concat base dimensions cannot contain duplicate values. Action: Use MAINTAIN RENAME to change one of the duplicate values and retry. ORA-36652: (XSDUNION11) workspace object is not a string type dimension. Cause: The CHGDFN BASE ADD command is only valid for concat dimensions. Action: none ORA-36664: (XSDPART02) You must specify a partitioning method and one or more partition dimensions when defining a PARTITION TEMPLATE. Cause: User tried to define a PARTITION TEMPLATE without a PARTITION BY clause. Action: Add a PARTITION BY clause. ORA-36665: (XSDPART03) workspace object is not in the dimension list of the PARTITION TEMPLATE. Cause: While defining a partition template, user attempted to specify a partition dimension that is not a dimension of the partition template itself. Action: Choose a partition dimension from among the dimensions of the partition template. ORA-36666: (XSDPART04) workspace object is not a concat dimension. Cause: User tried to define a partition template with PARTITION BY CONCAT(... dim ...) where dim is not a concat dimension. Action: Only concat dimensions can serve as partition dimensions with CONCAT partitioning. Choose a different partition dimension. ORA-36667: (XSDPART05) string is not a legal CONCAT partition. Cause: User attempted to use RANGE or LIST syntax in defining a CONCAT partition template. Action: Use CONCAT partition syntax. ORA-36668: (XSDPART06) string is not a legal RANGE partition. Cause: User attempted to use CONCAT or LIST syntax in defining a RANGE partition template. Action: Use RANGE partition syntax. ORA-36669: (XSDPART07) string is not a legal LIST partition. Cause: User attempted to use RANGE or CONCAT syntax in defining a LIST partition template. Action: Use LIST partition syntax. ORA-36670: (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions. Cause: User attempted to define a partition template partitioned by an INTEGER or NTEXT dimension or a concat containing an NTEXT leaf. Action: Either pick a different partition dimension, or redefine the dimension to use a different datatype. ORA-36671: (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used. Cause: User attempted to define a range partition template with a concat partition dimension, and the concat had two leaf dimensions with different datatypes. Action: Pick a different partition dimension. ORA-36672: (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension. Cause: User attempted to define a RANGE or LIST partition template with more than one partition dimension. Action: Remove all but one of the dimensions from the PARTITION BY RANGE(...) or PARTITION BY LIST(...) clause of the partition template definition. ORA-36673: (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format. Cause: When defining a RANGE partition template with a concat dimension for the partition dimension, the user attempted to define a range using the format of a concat dimension value. Action: Use just the leaf value. Instead of "VALUES LESS THAN ", just say, "VALUES LESS THAN value". ORA-36674: (XSDPART12) Invalid dimension value starting at string. Cause: When defining a RANGE or LIST partition template, the user specified an invalid value in a VALUES LESS THAN or VALUES clause. An "invalid value" can be one of two things: a value whose datatype does not match the partition dimension"s datatype, or a non-constant value. Action: Modify the offending VALUES LESS THAN or VALUES phrase. ORA-36676: (XSDPART14) Missing dimension list for string. Cause: User attempted to define a CONCAT partition template, and didn"t supply a list of dimensions for one of the partition definitions. Action: Give a dimension list for each partition. ORA-36677: (XSDPART15) Duplicate value in value lists of number and number Cause: In a LIST PARTITION TEMPLATE definition, a value appeared in more than one value list, or more than once within a single value list. Action: List each value only once. ORA-36678: (XSDPART16) workspace object is missing from one or more partition dimension lists. Cause: In the definition of a partition template, one of the partitions had a dimension list that did not contain all the dimensions of the partition template. Action: Add the offending dimension to the partition"s dimension list, or delete it from the partition template"s dimension list. If using CONCAT partitioning and the missing dimension is a partition dimension, add to the partition dimension list any leaf of the partition dimension or any concat of leaves of the partition dimension. ORA-36679: (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object. Cause: In the definition of a CONCAT partition template, one of the partitions was dimensioned by a dimension that is "concat-related" to a partition dimension, meaning it shares some leaves with the partition dimension, but it contained some leaves that are not in the partition dimension. Action: Either modify the dimensionality of the partition template to include a concat dimension that contains all the desired leaves, or pick a different dimension for the partition. ORA-36680: (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE. Cause: In the definition of a partition template, one of the partitions was dimensioned by a dimension that was not given in the dimension list of the partition template. Action: Remove the offending dimension from the partition"s dimension list, or add it to the partition template"s dimension list. ORA-36681: (XSDPART19) Partitions string and string are out of order. Cause: In the definition of a range partition template, a partition with a lower range boundary was listed after a partition with a higher range boundary. Action: Alter the order of the partition definition list. ORA-36682: (XSDPART20) Partition name string appears twice. Cause: User gave a list of AW partitions in which some partition name appeared twice. Action: Remove all but the first instance of the partition name from the list. ORA-36683: (XSDPART21) Partition string dimensioned by more than one composite. Cause: It is illegal to define a partition template in which one of the partitions is dimensioned by more than one composite. Action: Make sure that the partition template being defined has at most one composite per partition. ORA-36684: (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object Cause: User attempted to rename a value of a dimension that serves as the partition dimension of some RANGE or LIST partition template. Action: It is not possible to rename values in such a dimension without deleting all RANGE and LIST partition templates that are partitioned by it. ORA-36685: (XSDPART23) Only CONCAT partition templates can be subpartitioned. Cause: User attempted to define a RANGE or LIST partition template with one or more partitions dimensioned by another partition template. Action: Use only regular dimensions and composites to dimension each partition of the RANGE or LIST template. ORA-36686: (XSDPART24) Value number is not in partition number. Cause: User attempted to reorganize a list partition template by removing a value from some partition"s list, but the value was not in the list. Action: Ensure that the given values match the given partition. ORA-36688: (NTEXTCNV00) Error during conversion from TEXT to NTEXT. Cause: An unknown character set conversion error occurred when converting a TEXT value to an NTEXT value. Action: Unknown. ORA-36690: (NTEXTCNV01) Error during conversion from NTEXT to TEXT. Cause: An unknown character set conversion error occurred when converting an NTEXT value to a TEXT value. Action: Unknown. ORA-36691: (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string. Cause: The user called the UNISTR function on a string that had an invalid escape sequence. The only valid escape sequences in UNISTR are 1.) an escape-escape sequence, and 2.) an escape, followed by exactly four hexadecimal digits. Action: Make sure that all escape sequences in UNISTR arguments are exactly four hexadecimal digits. To represent codepoints whose value is less than 0x1000, use preceding zeros. WRONG: 0x10; RIGHT: 0x0010. ORA-36692: (XSRELTBL00) The format of the HIERHEIGHT command is: HIERHEIGHT relation1[(dimension dimvalue, ...)] into relation2 [using relation3 | a | d] [levelorder lovs] [inhierarchy {variable | valueset}]. Cause: The user input the wrong format/object types Action: Make sure number of arguments and all object types are correct. ORA-36694: (XSRELTBL01) The value cannot be added to dimension workspace object. Cause: Unknown. Action: Check the context and permission for dimension maintenance. ORA-36696: (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation. Cause: An ineligible dimension was specified in the Qualified Data Reference Action: Do not attempt to qualify this dimension. ORA-36698: (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation. Cause: The named dimension was not in the relation"s dimension list. Action: Select only dimensions that are in the relation"s dimension list. ORA-36700: (XSRELTBL04) Dimension workspace object cannot be qualified more than once. Cause: The same dimension was specified more than once in the QDR. Action: Specify each QDR dimension only once. ORA-36702: (XSRELTBL05) The format of the HIERHEIGHT function is: HIERHEIGHT(relation [,] level) level >= 1. Cause: The HIERHEIGHT function was specified incorrectly. Action: Make sure the format is correct. ORA-36704: (XSRELTBL06) workspace object should be dimensioned by workspace object. Cause: The level relation is not dimensioned by the source relation dimension. Action: Make sure the level relation has the correct definition. ORA-36706: (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension. Cause: The destination relation has the wrong definition. Action: Make sure the destination relation has the correct dimensions. ORA-36708: (XSMXALLOC00) Variable workspace object must be dimensioned to be used by the ALLOCATE command. Cause: The user supplied an undimensioned (scalar) variable to the ALLOCATE command. Action: Use a dimensioned variable. ORA-36710: (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object. Cause: The user attempted to execute ALLOCATE with mismatching TARGET and TARGETLOG variables Action: Use TARGET and TARGETLOG variables with matching dimensionality. ORA-36712: (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE. Cause: The user specified an invalid source or basis relation on the ALLOCATE command line. Action: Modify the relation to be a one-dimensional self-relation. ORA-36714: (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object. Cause: The user specified a TARGETLOG variable that had a different data type from the TARGET variable. Action: Use TARGETLOG and TARGET variables with an identical data type. ORA-36718: (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object. Cause: The user did not have sufficient permissions to run the ALLOCATE command Action: Change to a user ID with the appropriate permissions, or use objects that you have permission to use. ORA-36720: (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command. Cause: The user used the AGGMAP command to define the AGGMAP, so either the AGGMAP can only be used with the AGGREGATE command, or the AGGMAP has no contents attached to it. Action: Use the ALLOCMAP command to define the AGGMAP. ORA-36722: (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE. Cause: The user requested that source values be modified during the allocation, but that is not possible when using a formula source. Action: Either use a VARIABLE source or remove the SOURCEVAL specification for your ALLOCMAP. ORA-36726: (XSALERR00) The character "character" is not a valid format specifier for the ALLOCATE error log. Cause: The user specified an invalid formatter in the ALLOCERRLOGHEADER or ALLOCERRLOGFORMAT options. Action: Correct the option to have a valid format. ORA-36728: (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded. Cause: The user specified an ERRORLOG MAX value in the ALLOCMAP, but more errors were encountered while performing the allocation. Action: Either set ERRORLOG NOSTOP, reduce the allocation errors, or increase the ERRORLOG MAX setting ORA-36735: A value exceeded the MAX specification Cause: . Action: none ORA-36740: A CHILDLOCK was detected in your valueset Cause: . Action: none ORA-36761: (XSLANGDM01) Analytic workspace string already contains a dimension (%J) with the string property. Cause: An attempt was made to apply this property to more than one dimension in the AW. Action: Remove the property from the named dimension and try the command again. ORA-36762: (XSLANGDM02) You cannot modify the string property of %J because analytic workspace string is attached in MULTI mode. Cause: An attempt was made to add or delete a $DEFAULT_LANGUAGE property in an AW attached in multiwriter mode. Action: Attach the AW in a different mode. ORA-36763: (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT. Cause: An attempt was made to turn a variable into its own AGGCOUNT. Action: Select a different AGGCOUNT variable. ORA-36764: (XSAGGCNTMOVE02) AGGCOUNT variable workspace object must be of type INTEGER, not string. Cause: An attempt was made to create a non-INTEGER AGGCOUNT. Action: Select an INTEGER AGGCOUNT variable. ORA-36765: (XSAGGCNTMOVE03) A string aggregation variable cannot have a string AGGCOUNT. Cause: The specified AGGCOUNT variable did not have the same permanence as the aggregation variable. Action: Select an AGGCOUNT variable with the same TEMPORARY or PERMANENT attribute as the aggregation variable. ORA-36766: (XSAGGCNTMOVE04) workspace object cannot be used as an AGGCOUNT because it has an AGGCOUNT. Cause: The specified AGGCOUNT variable had its own AGGCOUNT Action: Select a different variable, or remove the AGGCOUNT using CHGDFN. ORA-36767: (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it. Cause: The specified AGGCOUNT variable had its own permissions distinct from those on the aggregation variable. Action: Select a different AGGCOUNT variable, or remove the permissions. In some cases this may require an UPDATE before the command can succeed. ORA-36768: (XSAGGCNTMOVE06) An aggregation variable and its AGGCOUNT must have the same base dimensions. Cause: An AGGCOUNT variable was specified with different base dimensions than the aggregation variable. Action: Select an AGGCOUNT variable with exactly the same base dimensions as the aggregation variable. ORA-36778: (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace. Cause: Ran out of temporary tablespace storage. Action: Increase the amount of temporary tablespace storage. ORA-36779: (XSPGPOOLOUT) Invalid parameter value. Olap_page_pool_size must be between must be between 2097152 and 2147483647. Olap_page_pool_size remain unmodified. Cause: Specified value for olap_page_pool_size out of range. Action: NONE. ORA-36800: (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP Cause: The OLAP table function given used more than one LOOP statement. Action: It is currently impossible to specify more than one LOOP composite, either remove one of the statements (and loop densely over relevant dimensions), or create a new composite that encompasses both loops and have a single loop statement refer to that. ORA-36802: (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP. Cause: There is no limitmap on the table function and either the datamap does not contain a fetch, or it errored before the fetch was called. Action: Check the datamap for errors, make sure that it executes a fetch statement, if it is not intended to execute the fetch then make sure that the table function has a valid limitmap. ORA-36804: (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP. Cause: Invalid LIMITMAP syntax, or the name resolution failure of an ANALYTIC WORSKPACE OBJECT. Action: Check the syntax of the limit map, check that the OLAP_TABLE function refers to a valid analytic workspace, check that all analytic workspace objects within the limitmap actually exist within the analytic workspace ORA-36806: (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string. Cause: The limitmap refers to a matching of ADT attribute to AW object, but the ADT attribute is not an element of the specified ADT table. Most commonly this is a typo. Action: Add the attribute to the ADT, correct the LIMITMAP, or remove the reference from the LIMITMAP. ORA-36808: (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields. Cause: The limitmap has a levelrel clause which has a different number of values in the list to the right of the FROM than it has to the left. Action: Change the limitmap so that there is a 1:1 mapping of adt and aw elements. ORA-36810: (XSTBLFUNC05) Analytic workspace object number does not exist. Cause: The limitmap refers to a non-existent aw object. Action: Change the limitmap or define the object ORA-36812: (XSTBLFUNC06) Invalid Syntax at "?". Cause: The limitmap has a question mark character outside the context of a string. Action: Fix the limitmap ORA-36814: (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16). Cause: Datatype of column used in ROW2CELL clause of a LIMITMAP is not RAW(16). Action: Change datatype to RAW(16). ORA-36815: (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY. Cause: The OLAP_TABLE aw_attach parameter was set to DURATION QUERY. Action: Change the OLAP_TABLE aw_attach parameter to DURATION SESSION. ORA-36816: (XSTBLFUNC09) The workspace object dimension is of datatype string which does not support custom member upserts. Cause: Custom members were attempted to be added via an upsert to a dimension that does not support them Action: Disable the AW Hash optimization for this query ORA-36820: (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP. Cause: Invalid LIMITMAP syntax. Action: Correct the syntax of the limit map. ORA-36830: (XSLMGEN00) AW name cannot be NA Cause: A NA was passed as the AW name Action: Pass in a valid AW name ORA-36831: (XSLMGEN01) View token cannot be NA Cause: A NA was passed as the view token Action: Pass in a valid view token ORA-36832: (XSLMGEN02) View token cannot be greater than 4000 bytes Cause: A view token was greater than 4000 bytes Action: Pass in a view token less than 4000 bytes ORA-36833: (XSLMGEN03) View token cannot be blank Cause: A blank was passed as the view token Action: Pass in a valid view token ORA-36834: (XSLMGEN04) Column tag is greater than 30 bytes Cause: A value greater than 30 bytes was passed as the column tag Action: Pass in a column tag of 30 bytes or less ORA-36835: (XSLMGEN05) Dimension string.string!string hierarchy string level string is missing a COLUMNNAME property value Cause: The COLUMNNAME property has no value Action: Add a value to COLUMNNAME property ORA-36836: (XSLMGEN06) Dimension string.string!string hierarchy string level string is missing a PHYSICALNAME property value Cause: The PHYSICALNAME property has no value Action: Add a value to PHYSICALNAME property ORA-36837: (XSLMGEN07) Dimension string.string!string is missing a COLUMNNAME property value Cause: The COLUMNNAME property has no value Action: Add a value to COLUMNNAME property ORA-36838: (XSLMGEN08) Dimension string.string!string attribute string is missing a COLUMNNAME property value Cause: The COLUMNNAME property has no value Action: Add a value to COLUMNNAME property ORA-36839: (XSLMGEN09) Cube string.string!string measure string is missing a COLUMNNAME property value Cause: The COLUMNNAME property has no value Action: Add a value to COLUMNNAME property ORA-36840: (XSLMGEN10) Cube string.string!string has no measures Cause: The cube has no measures Action: Add a measure to the cube ORA-36841: (XSLMGEN11) Dimension string.string!string was not found Cause: The view token referenced a dimension that does not exist Action: Pass in a dimension that does exist ORA-36842: (XSLMGEN12) Hierarchy string.string!string.string was not found Cause: The view token referenced a hierarchy that does not exist Action: Pass in a hierarchy that does exist ORA-36843: (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value Cause: The property PHYSICALNAME has no value Action: Populate the property PHYSICALNAME with a value ORA-36844: (XSLMGEN14) Dimension string.string!string is missing a string property value Cause: The dimension is missing a required property Action: Check dimension property values ORA-36845: (XSLMGEN15) Owner is greater than 30 bytes Cause: The owner passed is greater than 30 bytes Action: Pass in an owner that is 30 bytes or less ORA-36846: (XSLMGEN16) AW name is greater than 30 bytes Cause: The AW name passed is greater than 30 bytes Action: Pass in an AW name that is 30 bytes or less ORA-36847: (XSLMGEN17) AW name is blank Cause: The AW name passed is blank Action: Pass in an AW name that has a value ORA-36848: (XSLMGEN18) Dimension string.string!string is missing a COLUMNNAME property value Cause: The COLUMNNAME property has no value Action: Add a value to COLUMNNAME property ORA-36849: (XSLMGEN19) AW owner does not match View token owner Cause: The AW owner does not match the View token owner Action: Match AW ower to View token object owner ORA-36850: (XSLMGEN20) View token string is not correct Cause: The view token is not correct Action: Check view token syntax for errors ORA-36861: (XSTFRC01) SQL Cache ID parameter is invalid or missing. Cause: SQL Cache ID parameter is required to identify SQL cache to query Action: Supply a valid SQL Cache ID. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error. ORA-36862: (XSTFRC02) Column number for this SQL Cache must be between 1 and number. Specified column number number is invalid. Cause: Column Map references a column number that is greater than the maximum column number in SQL Cache Action: Reference a correct column number. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error. ORA-36863: (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP. Cause: Invalid COLUMNMAP syntax. Action: Check the syntax of the column map. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error. ORA-36871: (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP. Cause: The object cannot define a column in LIMITMAP most likely because it is of a wrong type such as, for example, a Worksheet. Action: Remove the reference from the LIMITMAP. ORA-36872: (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified. Cause: Column type can only be used with implicitly-specified table functions Action: Remove column type from reference from the LIMITMAP or remove the explicit table function data type specification. ORA-36873: (XSTFDSC03) Column type must be specified explicitly. Cause: Missing column type specification. Action: Please, make sure to specify a column type in COLUMN MAP. Normally, users should not call OLAP Random Access Cursor table function themselves and therefore should not encounter this error. ORA-36874: (XSTFDSC04) Expression string cannot be used to define a column in a LIMITMAP. Cause: The expression cannot define a column in LIMITMAP most likely because it is of a wrong type such as, for example, a Worksheet. Action: Remove the reference from the LIMITMAP. ORA-36875: (XSTFDSC05) LIMITMAP is missing or is not a string literal. Cause: Table functions that have an automatic ADT require LIMITMAP to be a string literal. Action: Either specify ADT for the table function or specify LIMITMAP as a string literal. ORA-36881: (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP. Cause: Using the ROW2CELL function outside of the LIMITMAP. Action: Remove use of the ROW2CELL function. ORA-36882: (XSSRF01) The second parameter of an AW single row function cannot be NULL. Cause: The second parameter of the AW single row function was NULL Action: Pass a valid OLAP DML expression as the second parameter of the AW single row function ORA-36883: (XSSRF02) The first parameter of an AW single row function cannot be NULL. Cause: The first parameter of the AW single row function was NULL Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is the first parameter of the AW single row function. ORA-36884: (XSSRF03) The value of the first parameter of the AW single row function is incorrect. Cause: The column specified in the LIMITMAP ROW2CELL clause was not the first parameter of the AW single row function. Action: Make sure the column specified in the LIMITMAP ROW2CELL clause is the first parameter of the AW single row function. ORA-36885: (XSSRF04) Error rewriting OLAP DML expression. Column name too big Cause: The column name specified in the OLAP DML expression was larger than 30 bytes. Action: Make sure the column name specified in the OLAP DML expression is less than or equal to 30 bytes. ORA-36886: (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes Cause: The rewritten OLAP DML expression was larger than the output buffer. Action: Create a smaller OLAP DML expression. ORA-36887: (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column. Cause: The column name passes does not exist. Action: Only reference columns that exist. ORA-36902: (XSAGDNGL43) In AGGMAP workspace object, the MODEL workspace object is not a model over a base dimension of the AGGMAP. Cause: Model may include equations others than dimension values, or blocks other than simple blocks. Action: Make sure model only includes the simple blocks with dimension values. ORA-36904: (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP. Cause: Before the current relation, dynamic model exists. Action: Make sure the dynamic model is the last statement. ORA-36908: (XSAGDNGL46) In AGGMAP workspace object, MODEL workspace object has the repeating dimension with the previous model. Cause: two models use the same dimension. Action: merge the equations in the two models. ORA-36910: (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy. Cause: The model attempted to edit a child node in the relation hierarchy. Action: Remove this attempt from the model definition. ORA-36912: (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous. Cause: The aggmap contained a simultaneous model. Action: Change the model definition so that it is no longer simultaneous. ORA-36913: (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension. Cause: The object refered to by the LOAD_STATUS clause of the aggmap wasn"t an undimensioned valueset over the related dimension Action: Change the aggmap definition so that it doesn"t refer to an invalid object ORA-36914: (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS valueset workspace object contains both a child and it"s ancestor. Cause: The LOAD_STATUS valueset is not allowed to contain both a dimension value and an ancestor of that value. Action: Perform a limit remove ancestors on the valueset and confirm that the result matches the intended load. ORA-36920: (XSVPMVTOPART01) workspace object cannot become anonymous because it has properties. Cause: The OLAP DML command would result in a named object becoming an anonymous object, but the object had one or more properties associated with it. Action: Remove the properties using the PROPERTY command. In some cases an UPDATE may be required before the command can proceed. ORA-36921: (XSVPMVTOPART02) workspace object and workspace object are not in the same analytic workspace. Cause: The OLAP DML command requires certain objects to be in the same analytic workspace, and the command string specified objects from two different analytic workspaces. Action: If more than one analytic workspace is attached to the session, make sure that the object names given in the command are unique across all attached analytic workspaces. Use qualified object names (QON"s) if necessary. ORA-36922: (XSVPMVTOPART03) workspace object is the target of an external partition of a partitioned variable. Cause: An attempt was made to perform some prohibited operation on a variable which is itself a partition of some other variable. Action: If desired, use the CHGDFN command to DROP the partition from the partitioned variable, and then run the command again. ORA-36923: (XSVPMVTOPART04) workspace object is not a LIST or RANGE PARTITION TEMPLATE. Cause: The user ran a command that only operates on a LIST or RANGE partition template (or a variable dimensioned by a LIST or RANGE partition template) on some other kind of analytic workspace object. Action: Rerun the command on a LIST or RANGE partition template or a variable dimensioned by a LIST or RANGE partition template. ORA-36924: (XSVPMVTOPART05) workspace object is not in a COMPOSITE. Cause: The OLAP DML command expected that the variable would be dimensioned by a composite containing the specified dimension, the specified dimension within a composite. Action: Rerun the command on some variable is dimensioned by a composite containing the specified dimension. ORA-36930: Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed. Cause: ROLLBACK past the UPDATE of one of the attached Analytic Workspaces was called. A recursive Oracle OLAP call cannot be made until the control returns to the initial OLAP call and the affected Analytic Workspaces detached. Action: Change the called SQL procedure to avoid the ROLLBACK ORA-36950: (XSFCAST22) The list of string values cannot have more than number members. You supplied number. Cause: There are more than the maximum number of OFFSET or PERIODICITY values. Action: Remove some of the values. ORA-36951: (XSFCAST28) The ALLOCLAST parameter cannot be set to YES unless PERIODICITY specifies more than one cycle. Cause: ALLOCLAST was set to YES when PERIODICITY specified a single value rather than a list of nested cycles. Action: Set ALLOCLAST to FALSE (the default), or specify more than one value for PERIODICITY (in the form of a parenthesized list). ORA-36952: (XSFCAST23) You cannot specify a cycle number when querying the string forecasting option. Cause: A cycle number was specified in a call to FCQUERY to retrieve forecast data not related to a cycle. Action: Remove the cycle specification from the call to FCQUERY. ORA-36954: (XSFCAST24) The cycle number must be between 1 and number. You specified number. Cause: A cycle number less than 1 or greater than the maximum value was specified in a call to FCQUERY. Action: Specify a number in the indicated range. ORA-36956: (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values. Cause: More OFFSET values were specified than PERIODICITY values. Action: Supply only as many OFFSETs as there are PERIODICITY values. ORA-36958: (XSFCAST26) The OFFSET value for cycle number cannot be greater than the cycle"s PERIODICITY, which is number. You specified number. Cause: The OFFSET for a cycle exceeded the PERIODICITY for that cycle. Action: Supply an OFFSET less than or equal to the PERODICITY for the corresponding cycle. ORA-36960: (XSFCAST27) The value of the string expression must be an odd number. You specified number. Cause: An even number was given for an option that requires an odd number. Action: Supply an odd number or let the option default. ORA-36961: Oracle OLAP is not available. Cause: The user attempted to utilize functionality found only in Oracle OLAP, but OLAP has not been enabled in the executable. Action: Install the Oracle OLAP option ORA-36962: (XSRELTBL08) string is not a valid workspace object. Cause: The specified value does not exist in the dimension. Action: Specify an existing value of the dimension. ORA-36964: (XSRELTBL09) workspace object is not a valid level relation. Cause: The specified level relation was not consistent with the parentage hierarchy. Action: Fix one or both of the relations involved so that all parents are at a higher level than their children. ORA-36966: (XSRELTBL10) workspace object must be a dimension. Cause: The qualified object must be a dimensions. Action: Remove the named object from the QDR. ORA-36968: (XSRELTBL11) workspace object must be a relation. Cause: An object other than a RELATION was specified as source or destination. Action: Specify RELATION objects. ORA-36970: (XSRELTBL12) workspace object must be a self-relation. Cause: The specified source relation was not a self-relation. Action: Specify a self-relation as the source. ORA-36972: (XSRELTBL13) Relation workspace object must be dimensioned by workspace object. Cause: Destination relation is not dimensioned by source relation dimension. Action: Give a correct destination relation. ORA-36974: (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy. Cause: The named variable had either the wrong data type or the wrong dimensions. Action: Specify a BOOLEAN variable dimensioned by all the dimensions of the hierarchy. ORA-36975: (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object. Cause: USING was omitted from the HIERHEIGHT command, or specified a relation containing values of a different dimension than the LEVELORDER valueset. Action: Provide a USING clause naming a relation containing values from the correct level dimension. -------------------------------------------------------------- ORA-36976: (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset. Cause: Command format is not correct. Action: Check the object type and number, and give the correct format. ORA-36977: (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels. Cause: The user specified a hierarchy with more than 126 levels. Action: Decrease the number of levels in the hierarchy. ORA-36978: (XSRELGID01) workspace object must be a self-relation. Cause: Source relation is not a self-relation. Action: Specify a self-relation as the source relation. ORA-36980: (XSRELGID02) Variable workspace object must have a numeric data type. Cause: The destination variable does not have a numeric data type. Action: Make sure the variable is numeric. ORA-36982: (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status. Cause: Destination variable/relation does not have enough dimensionality to hold the result from the multi-dimensional source relation. Action: Either limit the status of hierarchy dimensions or redefine the destination variable/relation with the extended dimensionality ORA-36986: (XSRELGID05) Relation workspace object must be dimensioned by workspace object. Cause: The destination relation is not dimensioned by the dimension of the source relation. Action: Redefine the destination relation or choose another relation with the correct dimensionality. ORA-36988: (XSRELGID06) The related dimension of relation workspace object must be of type NUMBER. Cause: The related dimension of the destination relation has the wrong data type. Action: Redefine the destination relation or choose another relation whose related dimension is of type NUMBER. ORA-36990: (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension. Cause: The level relation is not dimensioned by a level dimension. Action: Redefine the level relation or choose another relation with the correct dimensionality. ORA-36991: (XSRELGID08) The level relation and level order valueset provide inconsistent level mappings. Cause: There is a conflict between the hierarchy/level relation and the level order valueset. Action: Choose objects that do not conflict. ORA-36992: (XSRELGID09) A level relation is needed to produce a surrogate dimension gid. Cause: A level relation was not specified. Action: Specify a level relation. ORA-36993: (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object. Cause: not a surrogate dimension, or the surrogate dimension is not based on the level dimension. Action: modify/change the surrogate dimension. ORA-36994: (XSRELGID11) The SURROGATE DIMENSION workspace object must be numeric. Cause: The surrogate dimension is not numeric Action: Change the surrogate dimension as numeric ORA-36995: (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity. Cause: more than 1 hierarchies in the current computing scope. Action: use inhierarchy to limit ORA-36996: (XSRELGID13) Valueset workspace object should be defined over dimension workspace object. Cause: Valueset doesn"t match the dimension Action: Change the valueset"s dimension ORA-36997: (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified. Cause: no level relation exists with level order valueset. Action: provide the level relation. ORA-36998: (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions. Cause: either level order valueset or level relation has wrong level dimension. Action: choose the correct level dimension ORA-36999: (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id. Cause: use variable/relation gid without providing the source relation Action: use the surrogate or provide the source relation ORA-37000: (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object. Cause: The user specified an object which is not alias dimension of the first dimension Action: Specify an alias dimension of the first dimension ORA-37001: You have one or more attached but unupdated analytic workspaces. Cause: The user has attempted to shut down OLAP, but they have active analytic workspaces whose changes have not been saved. Action: Either issue the update command to update the AWs, or pass TRUE as the force parameter to dbms_aw.shutdown() ORA-37002: Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support. Cause: A severe error occurred while initializing OLAP. Action: Contact support (and possibly OLAP development) for help in debugging the issue. ORA-37003: (AWLISTALL01) number readers Cause: used in AW(LISTALL) output formatting when %d is 0 Action: none ORA-37004: (AWLISTALL02) number reader Cause: used in AW(LISTALL) output formatting when %d is 1 Action: none ORA-37005: (AWLISTALL03) number readers Cause: used in AW(LISTALL) output formatting when %d is > 1 Action: none ORA-37006: (AWLISTALL04) number writers Cause: used in AW(LISTALL) output formatting when %d is 0 Action: none ORA-37007: (AWLISTALL05) number writer Cause: used in AW(LISTALL) output formatting when %d is 1 Action: none ORA-37008: (AWLISTALL06) number writers Cause: used in AW(LISTALL) output formatting when %d is > 1 Action: none ORA-37010: (XSACQUIRE_DIFFAW) When using the CONSISTENT WITH clause, all objects must come from the same analytic workspace. Cause: The ACQUIRE command cannot keep objects from several workspaces consistent with each other Action: Omit the CONSISTENT WITH clause or make sure all objects being acquired belong to the same analytic workspace. ORA-37011: (XSACQUIRE_LOCKED) Object workspace object is locked by another user. Cause: Could not acquire (or acquire consistent) the object since it is locked by another user Action: Try to acquire this object later ORA-37012: (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out. Cause: Could not acquire (or acquire consistent) the object for a while since it is locked by another user Action: Try to acquire this object later ORA-37013: (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock. Cause: Waiting to acquire the object would cause a deadlock Action: Release some other object that another user is waiting for and try to acquire this object again. ORA-37014: (XSACQUIRE_ACQUIRED) Object workspace object is already acquired. Cause: The object is already acquired Action: Do not try to acquire this object again ORA-37015: (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC. Cause: The object is listed in with resync list and no resync list. Such usage is ambiguous as to the user"s intent on preserving or not preserving private changes. Action: Do not list the object both with and without RESYNC ORA-37016: (XSACQUIRE01) You must specify objects to acquire for the ACQUIRE command. Cause: A list of objects to acquire with or without resync is missing Action: Specify the list of objects to acquire ORA-37018: (XSACQUIRE03) Multiwriter operations are not supported for object workspace object. Cause: Multiwriter presently does not work for this object type Action: Attach the AW in RW or EXCLUSIVE modes to modify this object. ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode. Cause: The workspace for an object is not in multiwriter mode. Hence, no multiwriter operations are allowed on the objects in the workspace Action: Attach the workspace in the multiwriter mode or do not use multiwriter commands with it. ORA-37021: (XSMULTI02) Object workspace object is not acquired. Cause: The object must be acquired for this multiwriter operation Action: Do not use this multiwriter operation on an object that is not acquired ORA-37023: (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object. Cause: One cannot update an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target. Action: Include the maintained dimension in the update list ORA-37026: (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object. Cause: One cannot resync an object if it is dimensioned by a maintained dimension without updating that dimension or if the object is a relation and the dimension is its target. Action: Include the maintained dimension in the update list ORA-37027: (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension. Cause: When one resyncs an object that is dimensioned by a composite dimension, the composite dimension is resynced automatically, dropping all new tuples. This cannot be done, however, if the automatic resync of the composite dimension might cause data in an object that shares the composite dimension to become NA. Action: Resync both objects together. Alternatively, you can try to acquire the other object (that will ensure that the composite dimension is locked in the latest generation and will not be resynced when resyncing the first object), resync the first object, and release the other object. ORA-37028: (XSMLTRESYNC03) Object workspace object cannot be resynced without modified object workspace object because they share a modified dimension map. Cause: When one resyncs an object that is dimensioned by a dimension map, the dimension map is resynced automatically, dropping all changes. This cannot be done, however, if the automatic resync of the dimension map might cause data in an object that shares the dimension map to become NA. Action: Resync both objects together. Alternatively, you can try to acquire the other object (that will ensure that the dimensions map is locked in the latest generation and will not be resynced when resyncing the first object), resync the first object, and release the other object. ORA-37030: (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED. Cause: One cannot maintain a dimension in a multiwriter AW if it is not acquired. Action: Acquire the dimension first. ORA-37031: (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode. Cause: DELETE is allowed in multiwriter mode only for SESSION dimension members Action: Attach the AW in a R/W mode and perform the DELETE operation ORA-37032: (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode. Cause: User attempted to add or remove values from a LIST partition template"s lists while the AW containing the partition template was attached in multiwriter mode. Action: Do the maintenance in read only or read-write mode. ORA-37035: (XSMLTDCL01) You can only DEFINE SESSION objects in analytic workspace string because it is attached in MULTI mode. Cause: Persistent object definition in multiwriter mode is not allowed. Action: Do all persistent object definitions in read-write mode. ORA-37036: (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode. Cause: One cannot delete objects in an analytic workspace attached in MULTI mode. Action: Do all object in read-only or read-write mode. ORA-37037: (XSMLTDCL03) You cannot RENAME objects in analytic workspace string because it is attached in MULTI mode. Cause: One cannot rename objects in an analytic workspace attached in MULTI mode. Action: Do all persistent object maintenance in read-write mode. ORA-37038: (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode. Cause: One cannot used CHGDFN command on objects in an analytic workspace attached in MULTI mode. Action: Do all persistent object maintenance in read-write mode. ORA-37039: (XSMLTDCL05) You cannot maintain triggers in analytic workspace string because it is attached in MULTI mode. Cause: One cannot use TRIGGER command on objects in an analytic workspace attached in MULTI mode. Action: Do all persistent object maintenance in read-write mode. ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user. Cause: Some object required locking a composite, concat, dimension map, or internal partition, which is locked by another user Action: Try to acquire this object later ORA-37041: (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out. Cause: Some object required locking a composite, concat, dimension map, or internal partition, which could not be locked for a while since it is locked by another user Action: Try to acquire this object later ORA-37042: (XSACQUIRE_DEP_DEADLOCK) Cannot wait to acquire composite, concat, dimension map, or internal partition workspace object since doing so would cause a deadlock. Cause: Some object required locking a composite, concat, dimension map, or internal partition, which would cause a deadlock Action: Release some other object that another user is waiting for and try to acquire this object again. ORA-37043: (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or internal partition workspace object cannot be locked since another user has committed a new one already. Cause: Some object required locking a composite, concat, dimension map, or internal partition in the present generation, which is not possible since a newer generation already exists. Action: Try to acquire the main object with resync ORA-37044: (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync. Cause: Could not acquire the object without resync because another user has committed a newer version of it already. Action: Try to acquire this object with resync parameter ORA-37050: (XSMLTDCL06) You cannot use the RELATION command with workspace object because analytic workspace string is attached in MULTI mode. Cause: One cannot use the RELATION command on objects in an analytic workspace attached in MULTI mode. Action: Change the default relation when the analytic workspace is attached in RW or Exclusive mode. ORA-37060: (XSMCSESS08) number is not a valid custom member in dimension workspace object. Cause: No custom member or invalid custom member Action: Create the custom member or use the correct custom member ORA-37069: You may not execute a parallel OLAP operation against the EXPRESS AW. Cause: A parallel OLAP command attempted to execute against EXPRESS. Action: Contact Oracle support. Users should not see this message. ORA-37070: You may not execute OLAP DML programs in a parallel query session. Cause: The user attempted to execute a DML program inside of a parallel query session, perhaps in parallel aggregate Action: Adjust the job so that a program does no need to be executed, or disable parallelism ORA-37071: You may not execute a parallel OLAP operation against updated but uncommitted AW string. Cause: The user attempted to use a parallel feature against an AW which they updated but which has not been committed Action: Commit the current changes ORA-37072: (XSMCSESS00) Object workspace object has the wrong type. Cause: The object is not of the object type specified in the APPLY clause Action: Specify the correct object type ORA-37073: (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object. Cause: Applied relation has the different dimension from the dimension currently being maintained Action: Maintain relation dimension ORA-37074: (XSMCSESS02) Variable workspace object has no default aggmap. Cause: The applied variable has no default aggmap Action: Use variable with the default aggmap or aggmap directly ORA-37075: (XSMCSESS03) You cannot rename a session-only dimension value. Cause: The user tried to apply MAINTAIN RENAME to a SESSION value. Action: Delete the old value and add a new one with the desired name. ORA-37076: (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute. Cause: The user tried to add a SESSION value to a dimension type that does not support SESSION values. Action: Use a dimension of one of the listed types. ORA-37077: (XSMCSESS05) Object workspace object is specified more than once. Cause: The same object name was given more than once in the apply clause or in the step dimension list. Action: Remove the repetitions. ORA-37078: (XSMCSESS06) The dimension being maintained (workspace object) cannot also be used as a step dimension. Cause: The dimension being maintained was named as a step dimension. Action: Remove this dimension from the list of step dimensions. ORA-37079: (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE. Cause: The current aggmap may be for ALLOCATE Action: Choose the correct aggmap for AGGREGATE only. ORA-37080: Advice requested for hierarchy with too many levels Cause: A request was made for advice on a hierarchy with more levels than are supported. Action: Only request advice for hierarchies with less than 32 levels. ORA-37082: Invalid percent Cause: A request was made for advice with an illegal percent value. Action: Request between 0 and 100 percent precomputation. ORA-37083: Invalid object string Cause: A request was made for advice with an illegal object name. Action: Request using valid object names. ORA-37084: Output valueset string must match string"s dimensionality Cause: A request was made for advice for a relation with different dimensionality from the output valueset. Action: Request using objects that have the same dimensionality. ORA-37086: %s is not a valueset Cause: An operation was attempted that supports only valuesets as precompute expressions in an aggmap, yet a different kind of precompute expression was used. Action: Replace this limit expression with an equivalent valueset and retry the operation. General precompute expressions are deprecated. ORA-37100: (XSUNCOMMITTED) You have one or more updated but uncommitted analytic workspaces. Cause: The user has attempted to shut down OLAP, but they have active analytic workspaces whose changes have not been saved. Action: Issue the commit command. ---- 37101 - 37110 are reserved for partitioned variables ---- ORA-37101: (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE. Cause: User attempted to define or reference an AW object with the "all internal" phrase or internal / external partition list, but the object was not a variable, was not dimensioned by a partition template, or was an already existing target of an external partition. Action: Eliminate phrases specific to partitioned variables from the definition string, or dimension the variable by a partition template. ORA-37102: (XSVPART02) Invalid partition name string. Cause: The user gave an invalid partition name. When defining a partitioned variable, this message indicates that the partition name does not exist in the partition template. In any other context, it indicates that the partitioned variable or partition template does not have a partition with the given name. Action: Supply a valid partition name. ORA-37103: (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition. Cause: User attempted to define a partitioned variable with an external partition, but the target of the external partition had incorrect dimensionality or datatype. Action: Pick a different target variable. The target variable must be dimensioned by exactly the same dimensions, composites, and partition templates, in the same order, as are specified in the partition template, and must have the exact same datatype (including width, precision, and scale) as the partitioned variable itself. ORA-37104: (XSVPART04) A partitioned variable must be dimensioned by a single partition template only. Cause: User attempted to define a partitioned variable with more than one partition templates, or a partition template and one or more other dimensions, in the dimension list. Action: Use only a partition template in the dimension list of the variable. All dimensions of the variable must be included in the definition of the partition template. ORA-37105: (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions. Cause: User attempted to create an external partition on a partitioned variable, but the variable was dimensioned by a RANGE or LIST partition template. Action: Declare the partition INTERNAL instead of EXTERNAL, or use a CONCAT partition template in place of the RANGE or LIST partition template. ORA-37106: (XSVPART06) Invalid partition name number. Cause: The user gave an invalid partition name. Action: Supply a valid partition name. ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace object. Cause: Some action attempted to write data to a partitioned variable, but the variable didn"t have a partition for that data. This can result from a partition template that does not assign all possible dimension values to some subcube, or from a partitioned variable that does not have a partition for one of the partitions defined by the partition template. Action: Make sure that the cell being written is assigned to some partition by the partition template, and that the variable has an actual partition associated with the partition of the template. Use the CHGDFN template DEFINE... command to define new partitions within the template, and the CHGDFN variable ADD... command to add new partitions to the variable. Alternatively, the PARTWRITEERR can be set to false, in which case data being written to a non-existent partition will be silently discarded. ORA-37108: (XSVPART08) workspace object has an AGGCOUNT, but workspace object does not. Cause: An attempt was made to add a partition to a partitioned variable. Either the partition was defined WITH AGGCOUNT and the partitioned variable was not, or the partitioned variable was defined WITH AGGCOUNT and the partition was not. Action: Use CHGDFN ADD AGGCOUNT or CHGDFN DROP AGGCOUNT to either add or remove an AGGCOUNT from either the partition or the partitioned variable. ORA-37111: Unable to load the OLAP API sharable library: (string) Cause: This happens if: (1) the OLAP API sharable library is missing. (2) a sharable library upon which the OLAP API sharable library depends is missing. (3) the OLAP API sharable library is the wrong version. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support. ORA-37112: OLAP API requires Oracle 9.2 or later Cause: The version of the OLAP API jar files that you used requires Oracle version 9.2 or later. Action: Ensure that the URL with which the JDBC connection was opened is correct. If the RDBMS instance is running in compatibility mode for a version older than 9.2, it must be upgraded to at least 9.2.0.0.0 to be used with this version of the OLAP API. ORA-37113: OLAP API initialization error: (string) Cause: OLAP API initialization failed. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support. ORA-37114: OLAP API bootstrap error: (string) Cause: OLAP API bootstrapping failed. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support. ORA-37115: New OLAP API history is not allowed Cause: If there are active OLAP API sessions, it is not allowed to start a new OLAP API history by setting _olapi_history_retention parameter to true. Action: Wait until all active OLAP API sessions terminate before resetting _olapi_history_retention parameter to true. ORA-37116: OLAP API table function error: (string) Cause: OLAP API table function failed. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support. ORA-37117: olapi history retention has been disabled Cause: Under certain circumstances, for example, when the database is read only, olapi history retention is not possible because it requires updating persistent tables from time to time. If olapi history retention has been disabled, setting _olapi_history_retention parameter to true has no effect. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Customer Support. ORA-37118: The OLAP API library was not preloaded. Cause: In shared-server mode, the OLAP API library should be loaded during process initialization to ensure that the C++ virtual table addresses are identical in all shared-server processes. The OLAP API session was executing in a process in which the library had not been loaded. Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to SHARED_SERVER or ALWAYS, restart the instance, and try again. ORA-37119: Incompatible OLAP API library load address Cause: The OLAP API session was executing in a process in which the OLAP API sharable library was loaded which was at a different address than the process in which the OLAP API session originated. Action: Set option _XSOLAPI_LOAD_AT_PROCESS_START to ALWAYS, restart the instance, and try again. ORA-37120: MDX string is null Cause: MDX parser received a null string for syntax analysis. Action: Prepare a non-null and well-formed MDX query string and try again. ORA-37121: AW Spreadsheet invalidated Cause: While this cursor was open, a command was issued that changed the underlying data to become inconsistent. Action: Perform the query again, avoid performing dimension maintenance and cache clears during spreadsheet processing. ORA-37122: AW Session cache disabled Cause: A SQL Spreadsheet was attempted while the AW Session cache was disabled. Action: Enable the session cache and perform the query again. ORA-37126: (XSCCOMP01) The COMPRESSED COMPOSITE workspace object can only be used as a base of a single variable. Cause: The user attempted to DEFINE a variable dimensioned by a COMPRESSED COMPOSITE, but that COMPRESSED COMPOSITE is already being used by another VARIABLE. Action: Create a second COMPRESSED COMPOSITE for the second VARIABLE or add a measure dimension to the first variable. ORA-37127: (XSCCOMP02) The COMPRESSED COMPOSITE workspace object must be last in the dimension list. Cause: The user attempted to DEFINE a variable dimensioned by a COMPRESSED COMPOSITE, but gave a slower varying dimension in the dimension list. Action: Put the COMPRESSED COMPOSITE last in the dimension list when defining the VARIABLE. ORA-37128: (XSCCOMP03) It is not possible to PARTITION over a base of a COMPRESSED COMPOSITE. Cause: The user attempted to use a base of a COMPRESSED COMPOSITE as a partitioning dimension. Action: Choose a dense dimension as the partition base. ORA-37129: (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE. Cause: The AGGMAP was defined with a MODEL statement after a RELATION statement over a base of the COMPRESSED COMPOSITE. Action: Change the AGGMAP so that the MODEL statements appear before the RELATION statements. ORA-37130: (XSCCOMP05) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because you must specify AGGINDEX OFF when there is a PRECOMPUTE clause on a RELATION over base workspace object. Cause: A PRECOMPUTE clause was specified in the AGGMAP for a RELATION over a base of a COMPRESSED COMPOSITE, but AGGINDEX was ON Action: Remove the PRECOMPUTE clause from the AGGMAP, or add AGGINDEX OFF ORA-37131: (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE. Cause: The user specified an aggregation OPERATOR that is not supported by COMPRESSED COMPOSITES. Action: Use a MODEL for the calculation, or use an uncompressed COMPOSITE. ORA-37132: (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE. Cause: The status of the specified dimension did not include all detail cells. Action: Add all detail cells to the status of the dimension and reissue the AGGREGATE command. ORA-37133: (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access. Cause: The user attempted to store a value into to a variable dimensioned by a compressed composite, and the variable had previously been precomputed using the AGGREGATE command. Once the AGGREGATE command is run on a variable dimensioned by a compressed composite, it becomes read-only until the computed values are removed with the CLEAR command. Action: Run the CLEAR AGGREGATES command to remove the computed values from the variable and then rerun the failed operation. Note that CLEAR AGGREGATES will remove all the data computed during the last AGGREGATE command on this variable. ORA-37134: (XSCCOMP09) You cannot add new values to workspace object because it includes positions for precomputed aggregate values. Cause: The user attempted to create a new position in a compressed composite, either directly (using MAINTAIN MERGE or MAINTAIN ADD) or by storing a value into the variable dimensioned by the compressed composite. This is not allowed when the variable has been precomputed using the AGGREGATE command. Once the AGGREGATE command is run on a variable dimensioned by a compressed composite, the compressed composite becomes read-only until the computed values are removed with the CLEAR command. Action: Run the CLEAR AGGREGATES command to remove the computed values from the variable and then rerun the failed operation. Note that CLEAR AGGREGATES will remove all the data computed during the last AGGREGATE command on this variable. ORA-37135: (XSCCOMP10) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. The RELATION statement for dense dimension workspace object must precede RELATION statements over the bases of the COMPRESSED COMPOSITE. Cause: The user ran AGGREGATE on a variable dimensioned by a COMPRESSED COMPOSITE using an illegal AGGMAP. The AGGMAP contained a RELATION statement over some base of the COMPRESSED COMPOSITE followed by a RELATION over some other dimension of the variable. Action: Change the order of the RELATION statements in the AGGMAP. ORA-37136: (XSCCOMP11) Cannot ROLLUP dimension workspace object which is a base of COMPRESSED COMPOSITE workspace object, use AGGREGATE instead. Cause: The user ran ROLLUP on a variable dimensioned by a COMPRESSED COMPOSITE. Action: Instead of using ROLLUP, generate an aggmap and use AGGREGATE ORA-37137: (XSCCOMP12) You cannot CHGDFN workspace object because it is a COMPRESSED COMPOSITE. Cause: The user tried to CHGDFN a compressed composite Action: If the change is desired then delete the old composite and create a new one. ORA-37138: (XSCCOMP13) You cannot delete values from workspace object because it is an aggregated COMPRESSED COMPOSITE. Cause: The user tried to MAINTAIN DELETE from an aggregated COMPRESSED COMPOSITE. Action: In order to perform this sort of maintenance the composite must first be cleared. This can be done by running the CLEAR AGGREGATES command on the variable dimensioning the composite. Note that this will remove all data computed during the last AGGREGATE command. ORA-37139: (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause. Cause: The user tried to AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE with an AGGMAP that included a PROTECT clause. Action: Modify the aggmap or create a new aggmap that does not include a PROTECT clause and reaggregate. ORA-37140: (XSCCOMP15) Cannot AGGREGATE partitioned variable workspace object using AGGMAP workspace object because you cannot use the base of a COMPRESSED COMPOSITE as a partition dimension. Cause: The user tried to run aggregate on a partitioned variable with a partition dimension that is a base of a COMPRESSED COMPOSITE. Action: Repartition the data, drop the partition dimension from the aggmap, or don"t use COMPRESSED COMPOSITES. ORA-37141: (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure. Cause: The schema and analytic workspace name for the MDQUERY cursor declaration were incorrectly specified. Action: Specify the schema and awname as a host variable name preceded by a colon, or as a text literal string of the form "SCHEMA.AWNAME" or "*.*" (quotes optional). ORA-37142: (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected. Cause: The user specified a host variable that was not of the correct type. Action: Choose a different host variable. ORA-37143: (XSSQLMDQ03) string is not a valid analytic workspace name. Cause: The user specified an analytic workspace name not qualified by a schema name, or one or both components of the name exceed the maximum length Action: Specify a schema-qualified analytic workspace name with components no longer than 30 characters long. ORA-37144: (MDQUERY01) string is not a valid metadata object type for MDQUERY. Cause: The user specified an unrecognized first argument to MDQUERY Action: Specify a recognized object type (CUBE or DIMENSION) ORA-37145: (XSTTS_PLAT) Cannot transport analytic workspace across platforms. Cause: The user attempted to transport a tablespace containing an analytic workspace from one platform to another. Action: Use export/import to move an analytic workspace across platforms. ORA-37150: line string, column string, string Cause: MDX syntax error was found in MDX query string. Action: Check the error message details and make the corrections. ORA-37151: MDX parser initialization error Cause: MDX parser initialization failed Action: Please report this to Oracle Support Services. ORA-37152: MDX query error: (string) Cause: An exception occurred while MDX query was processed. Action: Check the error message details and try again. ORA-37153: unknown exception caught: (case string) Cause: An unknown exception was caught while MDX query was processed. Action: Please report it to Oracle Support Services. ORA-37154: OLAP API initialization error: (case string) Cause: OLAP API initialization failed. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Support Services. ORA-37155: OLAP API bootstrap error: (case string) Cause: OLAP API bootstraping failed. Action: Ensure that Oracle is properly installed with the OLAP option. If the RDBMS has been patched, review the patch log for errors. If the problem persists, report it to Oracle Support Services. ORA-37156: (string) Cause: unknown Action: Check the error message details. ORA-37157: MDX syntax error was found in MDX query string but error text was missing Cause: This happened because the message file was missing. Action: Make sure that the message file xsous.msb is located in $ORACLE_HOME/olap/mesg and rerun your MDX query. ORA-37158: Bad clob or varray IN-args: (case string) Cause: When in clob or varray mode, the PL/SQL mappings of OLAP API"s IDL interface methods were executed blindly with null clob/varray or non-null clob/varray containing garbages. Action: Do not blindly execute them as doing so does not make sense unless you understand how OLAP API works internally. ORA-37171: dimension sources not specified Cause: The user passed an empty or null collection to DBMS_AW.ADVISE_SPARSITY Action: Specify a valid set of dimension sources ORA-37172: illegal dimension type Cause: The user specified an invalid member of the DIMTYPE field in the dimension sources argument Action: Specify one of the valid enumerated values in DBMS_AW ORA-37173: null dimension source data Cause: The user specified NULL for one of the members of the dimension sources argument Action: Specify a value ORA-37174: source SQL must be a SELECT statement Cause: The user specified an INSERT, UPDATE, DELETE or other type of SQL statement Action: Specify a SQL SELECT statement instead ORA-37175: column string is not a column of source data Cause: A dimension column was specified which did not exist in the input data Action: Specify one of the columns of the input data ORA-37176: argument string is not valid for the sparsity advisor Cause: An invalid argument was passed to the advisor Action: Specify a TABLE, VIEW or SELECT statement instead ORA-37177: column string does not have any leaf values Cause: The specified dimension column or fact table did not contain any leaf values Action: Populate the source data ORA-37178: column string has no values Cause: The specified dimension column did not contain any values Action: Populate the source data ORA-37179: expected at least one column for dimension string, got string Cause: Not enough columns were specified for the dimension Action: Specify more source columns, or change the dimension to another type ORA-37180: expected exactly one column for dimension string, got string Cause: Expected a single source column for the dimension. Either none or more than one was specified. Action: Specify exactly one column, or change the dimension to another type ORA-37181: expected exactly string columns for dimension string, got string Cause: Expected a certain number of source columns for the dimension. Either none or the wrong number of columns was specified. Action: Specify the right number of columns, or change the dimension to another type ORA-37182: you may only specify one dimension to partition Cause: The user passed a DIMENSION_SOURCE_T to ADVISE_SPARSITY which specified partitioning on more than one dimension Action: Remove all but one of the partitioning requests ORA-37183: illegal value string for PARTBY Cause: The user passed a value other than PARTBY_DEFAULT, PARTBY_NONE or PARTBY_FORCE to DBMS_AW.ADVISE_SPARSITY *Acton: Supply a legal value instead Action: none ORA-37184: illegal value string for ADVMODE Cause: The user passed a value other than ADVICE_DEFAULT, ADVICE_FAST or ADVICE_FULL to DBMS_AW.ADVISE_SPARSITY *Acton: Supply a legal value instead Action: none ORA-37185: length of string (string) exceeds maximum (string) Cause: The user passed an excessively long value Action: Specify a legal value ORA-37600: (XSPGERRPERMDETACH) Parallel updating analytic workspace string failed Cause: Unexpected error occurred to parallel update servers. Action: Check the error underneath and act accordingly. AW may need to be detached. ORA-37601: (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace. Cause: Ran out of temporary tablespace storage. Action: Increase the amount of temporary tablespace storage. ORA-37602: (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace. Cause: Ran out of temporary tablespace storage. Action: Increase the amount of temporary tablespace storage. ORA-37603: (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace. Cause: Ran out of temporary tablespace storage. Action: Increase the amount of temporary tablespace storage. ORA-37999: Serious OLAP error: string. Please contact Oracle Technical Support. Cause: Something unexpected occurred in the OLAP system Action: Contact Oracle technical support 19 ORA-38029 to ORA-39962 ORA-38029: object statistics are locked Cause: An attept was made to modify optimizer statistics of the object. Action: Unlock statistics with the DBMS_STATS.UNLOCK_TABLE_STATS procedure on base table(s). Retry the operation if it is okay to update statistics. ORA-38101: Invalid column in the INSERT VALUES Clause: string Cause: INSERT VALUES clause refers to the destination table columns Action: none ORA-38102: Invalid column in the INSERT WHERE Clause: string Cause: INSERT WHERE clause refers to the destination table columns Action: none ORA-38103: Invalid column in the UPDATE SET Clause: string Cause: UPDATE SET clause refers to the source table columns in the LHS Action: none ORA-38104: Columns referenced in the ON Clause cannot be updated: string Cause: LHS of UPDATE SET contains the columns referenced in the ON Clause Action: none ORA-38105: Delete not yet supported when Update row-migration is possible Cause: When Update Row-Migration is possible, Delete in MERGE is not yet supported Action: none ORA-38201: assert if pin during flush Cause: internal use only Action: enables checking for bugs in upper layers when there is a pin on a buffer or there are users for buffer and we are trying to flush the object associated with the buffer ORA-38303: invalid option for PURGE TABLESPACE Cause: Either a token other than USER was found following the tablespace name or some text was found following USER . Action: Place nothing or only USER after the tablespace name ORA-38304: missing or invalid user name Cause: A valid user name was expected. Action: Specify a valid user name. ORA-38305: object not in RECYCLE BIN Cause: Trying to Flashback Drop an object which is not in RecycleBin. Action: Only the objects in RecycleBin can be Flashback Dropped. ORA-38306: this object is not recoverable standalone Cause: Trying to flashback drop an object other than of type TABLE. Action: Only tables are recoverable. ORA-38307: object not in RECYCLE BIN Cause: Trying to Purge the object which is not in RecycleBin. Action: Only the objects in RecycleBin can be PURGEDED. ORA-38309: object not purgable Cause: An attempt was made to purge an object that is either not purgable or else dependent upon some other object. Action: Cannot purge this object. ORA-38310: cannot purge tablespace for other users Cause: An attempt was made to purge the tablespace for a different user by a user who does not have system DBA priviledges. Action: Cannot purge the tablespace for some other user. ORA-38311: cannot purge objects owned by other users Cause: An attempt was made to purge an object which is owned by some other user. Action: Cannot purge this object. ORA-38312: original name is used by an existing object Cause: An attempt was made to recover an object preserving the original name, but that name is taken up by some other object. Action: use the RENAME clause to recover the object with a different name. ORA-38401: synonym string not allowed Cause: An attempt was made to use a synonym for a data type of an attribute or a table alias. Action: Use the object name instead of the synonym. ORA-38402: invalid name: empty string or spaces in the name Cause: There were spaces in the name. Action: Remove spaces in the name or use quotes around the name. ORA-38403: attribute set name may not be longer than 22 characters Cause: The attribute set name was longer than 22 characters. Action: Choose a name that has 22 or fewer characters. ORA-38404: schema extension not allowed for the attribute set name Cause: There was a schema extension for the attribute set name. Attribute sets are always created in the current schema and thus schema extended names are not allowed. Action: Create the attribute set from the appropriate schema. ORA-38405: quotes not allowed in the attribute set name Cause: The attribute set name contained quotes. Action: Remove quotes in the attribute set name. ORA-38406: attribute set string already exists Cause: An attribute set with a matching name already exists in the current schema. Action: Drop the existing attribute set or choose a different name. ORA-38407: The ADT associated with the attribute set already exists. Cause: The Abstract type (ADT) with the same name as the attribute set already exists in the current schema. Action: Create the attribute set for the existing ADT or drop the ADT. ORA-38408: The ADT "string" does not exist in the current schema. Cause: An attempt was made to create the attribute set from a nonexistent ADT. Action: Make sure that the ADT with the same name as the attribute set exists in the current schema. ORA-38409: invalid name or option for the attribute set: string Cause: An invalid name or option was used for the attribute set. Action: Set serveroutput ON and repeat the operation for additional information. ORA-38410: schema extension not allowed for the table name Cause: An attempt was made to use a schema extended name for the table storing expressions. Action: The table storing expressions and the corresponding attribute set should be created in the same schema. ORA-38411: invalid datatype for the column storing expressions Cause: An attempt was made to create an expression column from a column of invalid datatype. Action: Create a VARCHAR2 or CHAR column to store expressions in a table. ORA-38412: Expression set column string does not exist. Cause: The column storing expressions does not exist. Action: Pass a valid name for the column storing expressions. ORA-38413: elementary attribute name may not be longer than 32 characters Cause: An attempt was made to create an elementary attribute with a name longer than 32 characters. Action: Use a shorter name for the elementary attribute. ORA-38414: invalid datatype for the attribute string Cause: The datatype specified for the attribute was invalid. Action: If the datatype is an ADT, make sure that the ADT exists and the current user has execute permissions to it. ORA-38415: invalid name or datatype for the attribute: string Cause: An invalid name or datatype was used for the attribute. Action: Set serveroutput ON and repeat the operation for additional information. ORA-38416: A stored attribute may not be longer then 300 characters. Cause: An attempt was made to create a stored or indexed attribute longer than 300 characters. Action: A predicate with such attribute may not be indexed. It will be evaluated as sparse predicate. ORA-38417: attribute set string does not exist Cause: An attempt was made to use an attribute set that does not exist. Action: Create the attribute set or choose an existing attribute set. ORA-38418: ADT associated with the attribute set string does not exist Cause: The ADT with the same name as the attribute set was not found in the current schema. Action: Drop the attribute set and recreate it. ORA-38419: invalid identifier in attribute : string Cause: An identifier used in the stored/indexed attribute sub-expression was not defined or was invalid. Action: Create all the required elementary attributes and user-defined functions and try again. ORA-38420: invalid stored attribute sub-expression: string Cause: The sub-expression used for the stored expression was invalid. Action: Set serveroutput ON and repeat the operation for additional information. ORA-38421: attribute string already exists Cause: An attribute with a matching name (or form) already exists in the attribute set. Action: Drop the existing attribute or choose a different name for the new attribute. ORA-38422: invalid datatype for the attribute: string Cause: An attempt was made to create an attribute with invalid datatype. Action: If the data type of the attribute is an ADT, make sure that the type exists. ORA-38423: Attribute set created from an ADT may not be extended. Cause: An attempt was made to add an elementary attribute to an attribute set created from an ADT. Action: Create a new attribute set and add all the required elementary attributes one at a time. ORA-38424: no attribute set currently assigned to the expression set Cause: An attempt was made to un-assign an attribute set from an expression set when there is no attribute set assigned to it. Action: No action is required. ORA-38425: attribute set used for an index object may not be unassigned Cause: An attempt was made to un-assign an attribute set from an expression set when there is an Expression Filter index defined on the column. Action: Drop the index before un-assigning the attribute set. ORA-38426: attribute set assigned to an expression set may not be dropped Cause: An attempt was made to drop an attribute set when it is still associated with an expression set. Action: Un-assign the attribute set from the expression set before dropping it. ORA-38427: attribute string does not exist Cause: An attempt was made to use an attribute set that does not exist. Action: Create the attribute set. ORA-38428: too many attributes selected for indexing Cause: An attempt was made to create an expression filter index with more than 490 indexed attributes. Action: Remove some of the indexed attributes. Make sure that the default indexed attributes associated with the attribute set combined with the indexed attributes specified in the Create Index Parameters clause are less than or equal to 490. ORA-38429: invalid datatype for a stored attribute: string Cause: The (resulting) datatype for the attribute was not appropriate for storing. Action: Choose a stored attribute that has a resulting datatype of NUMBER, VARCHAR2, CHAR or DATE. ORA-38430: Operation "string" not supported in the current release. Cause: An attempt was made to perform an unsupported operation. Action: Do not use the operation. ORA-38431: could not evaluate subexpression "string" for rowid "string" Cause: Either the expression was not a valid SQL-WHERE clause format or it had references to nonexistent schema objects. Action: Correct the expression. ORA-38432: EVALUATE operator only allowed on an expression column Cause: An attempt was made to use the EVALUATE operator on a column not configured as a column storing expressions. Action: Assign an attribute set to the column. ORA-38433: index "string" could not be maintained due to "string" Cause: The error was caused by the recursive operation. Action: Fix the error and retry. ORA-38434: could not evaluate expression "string" Cause: Either the expression was not in a valid SQL-WHERE clause format or it had references to nonexistent schema objects or there is a missing attribute value. Action: Set serveroutput ON for more details. ORA-38435: missing elementary attribute value or invalid name-value pairs Cause: The second argument to the EVALUATE operator had either a missing attribute or an invalid value for an attribute. Action: Try again after fixing the error. ORA-38436: attribute set used for an Expression set may not be modified. Cause: An attempt was made to add an elementary attribute to an attribute set assigned to an expression set. Action: Un-assign the attribute set and try again. ORA-38437: The ADT "string" may not contain any user methods. Cause: An attempt was made to create an attribute set from an ADT that has one or more user methods. Action: Drop the ADT and recreate it with no user methods. ORA-38438: getVarchar not possible due to "string" datatype in the attribute set Cause: An attempt was made to use the getVarchar API when the attribute set has one or more non-scalar types. Action: Use AnyData conversion to encode the data item. ORA-38439: invalid operation "string" Cause: An attempt was made to use an invalid operation. Action: Use one of the following operations : ADD, DROP ORA-38440: attribute set string does not exist Cause: An attempt was made to copy an attribute set that is not accessible from the current schema. Action: Grant execute permissions on the corresponding ADT to the current user and try again. ORA-38441: System could not derive the list of STORED and INDEXED attributes. Cause: The attribute set was created without default index parameters. Action: Specify the default index parameters for the attribute set or include a valid PARAMETERS clause for the CREATE INDEX command. ORA-38442: The ADT "string" is not in a valid state. Cause: An attempt was made to use an ADT that is not in a valid state. Action: Check the INCOMPLETE field in the user_types catalog view to make sure that the ADT is in a valid state. Drop the invalid ADT and recreate the corresponding attribute set. ORA-38443: An attribute set should be assigned to the expression set for statistics collection. Cause: An attempt was made to collect statistics for an expression set with no attribute set assigned to it. Action: Assign an attribute set to the expression set before collecting the statistics. ORA-38444: statistics do not exist for the expression set Cause: An attempt was made to clear the statistics that do not exist. Action: No action was required. ORA-38445: TOP clause not allowed with no statistics Cause: An attempt was made to use the TOP parameters clause with no statistics available for the expression set. Action: Collect statistics for the expression set and try again. ORA-38446: Error with embedded ADT "string" in the attribute set. Cause: The embedded ADT has errors. Action: Set serveroutput ON for additional information. ORA-38447: Type required for the embedded ADT attribute "string" is missing Cause: Object type required for the embedded ADT was missing. Action: Set serveroutput ON for additional information. ORA-38448: Indexing predicates with "string" operator is not supported. Cause: An unsupported operator was used in the exf$indexoper array. Action: Choose the operators from this list : =, <, >, <=, >=, !=, is null, is not null, nvl, and between. ORA-38449: table "string" does not exist or is not accessible Cause: An attempt was made to create a table alias for a table that does not exist or is not accessible. Action: Grant select privileges on the table to the current user. ORA-38450: error computing a stored attribute for the expression set. Cause: Either values for one of the attributes was incorrect or a stored attribute was invalid due to broken dependencies. Action: Correct the input. ORA-38451: index is in an inconsistent state Cause: One or more secondary objects used to maintain the index did not exist Action: Drop the index and recreate it. ORA-38452: Expression Filter index name may not be longer than 25 characters Cause: An attempt was made to use a name longer than 25 characters for the Expression Filter index. Action: Choose a name that has 25 or fewer characters ORA-38453: ExpFilter index should be created in the same schema as the base table. Cause: An attempt was made to create the Expression Filter index in a schema other than that of the base table. Action: Create the index in the same schema as the base table. ORA-38454: attribute set not defined for the column being indexed Cause: An attempt was made to create an Expression Filter index on a column with no attribute set association. Action: Assign an attribute set to the expression set column begin indexed. ORA-38455: Expression Filter index should be created by the owner. Cause: An attempt was made to create the Expression Filter index by a user who is not the owner of the index. Action: Create the index using owner"s privileges. ORA-38456: The attribute set "string" is in an inconsistent state. Cause: The attribute set was in an inconsistent state due to broken dependencies. Action: Set serveroutput ON for more details. The attribute set may not be reused after this error. ORA-38457: The attribute "string" is not a valid XMLType attribute. Cause: An attempt was made to use a non-XMLType attribute to configure XPath filtering. Action: Use an attribute of sys.XMLType datatype to configure XPath filtering. ORA-38458: invalid operation "string" for XPATH_FILTER_PARAMETERS Cause: An attempt was made to use an invalid operation. Action: Use one of the following operations : ADD, DROP. ORA-38459: XML Tag "string" not found for the XMLType attribute "string" Cause: An Attempt was made to use a non-existent XML Tag. Action: Correct the name of the XML Tag or the XMLType attribute. ORA-38460: filtering based on datatype "string" not supported for XML Tags Cause: An attempt was made to configure XPath filtering with an XML Tag of unsupported datatype. Action: Leave the XML Tag out of filter parameters. It will be processed as sparse predicate ORA-38461: XML Tag "string" already exists for the XMLType attribute "string" Cause: An attempt was made to create a duplicate XML Tag. Action: Choose a different XML Tag. ORA-38462: invalid attribute list Cause: The input was missing an attribute list or had null values for the attribute names. Action: Correct the input. ORA-38463: invalid XML Tag list Cause: The input was missing a tag list or had null values for the tag names. Action: Correct the input. ORA-38464: expression set is not empty. Cause: An attempt was made to assign an attribute set to a non-empty expression set. Action: Use FORCE = "TRUE" to validate all the existing expressions. ORA-38465: failed to create the privilege checking trigger due to: string Cause: Creation of the trigger failed due to the error listed in the message. Action: Set serveroutput ON for more information. ORA-38466: user does not have privileges to CREATE/MODIFY expressions Cause: An attempt was made to INSERT or UPDATE a column storing expression without appropriate permissions. Action: Appropriate privileges on the expression set should be granted by the owner of the expression set. ORA-38467: user cannot GRANT/REVOKE privileges to/from himself Cause: An attempt was made to GRANT or REVOKE privileges to or from the current user. Action: The the to_user or from_user field should be different from the user performing the operation. ORA-38468: column "string" is not identified as a column storing expressions. Cause: An attempt was made to grant permission on a nonexistent expression set. Action: Make sure that the table and the column exist and an attribute set is associated with the column. ORA-38469: invalid privilege for an expression set: string Cause: An attempt was made to use an invalid privilege. Action: See documentation for a valid privilege. ORA-38470: cannot revoke a privilege that was not granted. Cause: An attempt was made to revoke a privilege that had not been granted. Action: Check catalog views to see if the user has the privilege. ORA-38471: ROWIDs for table aliases cannot be null Cause: An attempt was made to pass a null value for the table alias attribute in the data item, which is not permitted. Action: Pass a valid rowid value for the table alias. ORA-38472: VARCHAR representation of the data item is too long. Cause: The VARCHAR representation of data item was too long. Action: Use the EVALUATE operator with AnyData argument instead. ORA-38473: cannot drop a type used for Expression Filter attribute set Cause: An attempt was made to drop an ADT that was used to maintain an attribute set for the Expression Filter. Action: Query USER_EXPFIL_ATTRIBUTE_SETS view to see the dependency. ORA-38474: attribute set may not have attributes of TABLE COLLECTION type. Cause: An attempt was made to create an attribute with a TABLE COLLECTION type. Action: Use VARRAYs instead of table collection, if possible. ORA-38475: The attribute set and the associated ADT are out of sync. Cause: The ADT was directly modified by CREATE or ALTER operations. Action: Drop the attribute set and recreate it from scratch. ORA-38476: abstract type used for an Attribute set may not be modified. Cause: An attempt was made to alter a type (ADT) that is used to maintain an attribute set of an Expression set. Action: Do not modify the ADT directly. Use DBMS_EXPFIL APIs instead. ORA-38477: attribute set cannot be derived from an evolved type or a subtype. Cause: An attempt was made to create an attribute set from an evolved ADT or a subtype. Action: The ADT used for the attribute set cannot be an evolved type or a subtype. ORA-38478: creation of system trigger EXPFIL_DROPOBJ_MAINT failed Cause: The creation of the system trigger EXPFIL_DROPOBJ_MAINT failed due to missing Expression Filter dictionary tables. Action: Try a clean installation again. If this error is ignored, the Expression Filter dictionary could have some stale entries. ORA-38479: creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed Cause: The creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed due to missing Expression Filter dictionary tables. Action: Try a clean installation again. If this error is ignored, the user will be able to evolve ADTs associated with the attribute set, thus causing spurious errors. ORA-38480: creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed. Cause: The creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed due to errors in SYS.EXF$DBMS_EXPFIL_SYSPACK package. Action: Try a clean installation again. If this error is ignored, a RENAME of the expression table may cause the EVALUATE queries to fail. ORA-38481: ADT "string" is used for a dependent object. Cause: An attempt was made to create an attribute set from an ADT which is used by one or more dependent objects. Action: Use a new ADT instead. ORA-38482: no elementary attributes defined in the attribute set Cause: An attempt was made to use an empty attribute set. Action: Create one or more elementary attributes for the attribute set. ORA-38483: invalid FUNCTION/PACKAGE/TYPE name: "string" Cause: An attempt was made to use an invalid name format. Action: The function/package/type name should be specified in the following format [owner.]object_name ORA-38484: FUNCTION/PACKAGE/TYPE string does not exist Cause: Attempt was made to use a object that does not exist. Action: Query ALL_OBJECT view to ensure that the object exists. ORA-38485: invalid object type for the user-defined function Cause: An attempt was made to use an invalid object as a function. Action: Valid object types are FUNCTION / PACKAGE / TYPE ORA-38486: FUNCTION/PACKAGE/TYPE already exists for the attribute set Cause: An attempt was made to add a duplicate function to the list. Action: Use a different object name. ORA-38487: FUNCTION/PACKAGE/TYPE "string" not allowed in the expression Cause: An attempt was made to use an un-approved function in the expression. Action: Add the function to the corresponding attribute set ORA-38488: attribute set already assigned to the column storing expressions Cause: An attempt was made to reassign an attribute set to an expression column. Action: Query USER_EXPFIL_EXPRESSION_SETS view to find the attribute set assigned the expression set ORA-38489: predicate table creation failed due to: ORAstring Cause: Predicate table creation failed due to the reported error. Action: Set serveroutput ON for additional information ORA-38490: invalid name: quotes do not match Cause: The quotes in the name did not match. Action: Correct the name to match the quotes. ORA-38491: could not evaluate subexpression for rowid "string" Cause: Either the expression was not in a valid SQL-WHERE clause format or it had references to nonexistent schema objects. Action: Correct the expression. ORA-38492: invalid ALTER INDEX parameters clause "string" Cause: An invalid parameters clause was specified with the ALTER INDEX command. Action: See documentation for a valid list of parameters. ORA-38493: feature not enabled : Expression Filter index Cause: An attempt was made to create an Expression Filter index in Standard Edition. Action: Do not attempt to use this feature. ORA-38494: column in the table alias and an attribute have matching names Cause: One of the attributes in the set has the same name as the name of one of the columns in the table configured for table alias. Action: If possible, use a different name for the attribute. ORA-38495: data type for the stored attribute string is inconsistent. Cause: The actual data type for the stored attribute configured for the Expression Filter index object did not match the data type recorded in the Expression Filter dictionary. Action: Delete the attribute from the default index attributes and recreate it. ORA-38496: Expression Filter index is not in a valid state Cause: An attempt was made to REBUILD an Expression Filter index that was not valid. Action: Use DEFAULT keyword in the parameters clause to rebuild the index from defaults or drop and recreate the index. ORA-38497: Expression Filter index does not exist Cause: Index with a matching name does not exist or the index was not created using ExpFilter indextype. Action: Identify the correct index using the Expression Filter catalog views ORA-38498: invalid stored attribute for the index object : string Cause: The expression filter index object has a stored or indexed attribute that had broken dependencies. Action: Make sure that all the identifiers used in the attribute are valid. ORA-38499: expression set already configured for stored/indexed attributes Cause: The expression set already had a list of stored and indexed attributes. Additional attributes cannot be specified in the CREATE INDEX parameters clause. Action: Remove TOP, STOREATTRS and INDEXATTRS clauses from the parameters clause or clear the expression set statistics using DBMS_EXPFIL.INDEX_PARAMETERS API. ORA-38500: %s Cause: There was a generic error Action: See documentation for further information. ORA-38501: sub-query not allowed in the expression Cause: An attempt was made to use a sub-query in the expression. Action: Do not use sub-queries in the expressions. ORA-38502: invalid XML tag: string Cause: An attempt was made to use an invalid XML tag for the index. Action: Correct the XML tag and retry. ORA-38503: index already defined using the parameters Cause: An attempt was made to modify the index parameters after the index creation. Action: Drop the index and retry. ORA-38504: this operator not allowed with the configured attribute set Cause: An attempt was made to use the operator binding with an attribute set containing more than one (table alias) attribute. This is not permitted. Action: Use a different operator binding. ORA-38505: invalid default value for the attribute Cause: An attempt was made to use an invalid default value or a default that is larger than 100 characters. Action: Specify a correct default value. ORA-38601: FI Not enough memory for frequent itemset counting: string Cause: The memory size did not satisfy the minimum memory requirement. Action: In workarea_size_policy="manual" mode, set _fic_area_size to a reasonably larger value. Or, In workarea_size_policy="auto" mode, this error should never happen. ORA-38602: FI invalid input cursor Cause: The input cursor did not return exactly two columns for transactional input format or the input cursor didn"t have consistent data types for horizontal input format Action: For transactional input format, specify that the input cursor returns exactly two columns: one for transaction-id, one for item-id. For horizontal input format, make sure the input cursor"s columns have the same data types. ORA-38603: FI including & excluding cursor can only return one column Cause: The including & excluding cursor did not return exactly one column. Action: Specify that the cursor return only one column: item-id. ORA-38604: FI including & excluding cursor item-id type must match input cursor item-id type Cause: The including & excluding cursor item-id type did not match input cursor item-id type Action: Specify that the item-id type of the cursors match each other. ORA-38605: FI not enough memory(stringK) for candidate generation(stringK) Cause: There was insufficient available memory for candidate generation. Action: In workarea_size_policy="manual" mode, set _fic_area_size to a reasonably larger value. Or, in workarea_size_policy="auto" mode, set pga_aggregate_target to a reasonably larger value. ORA-38606: FI support threshold not between [0, 1] Cause: The user inputed a support threshold not in the range of [0, 1]. Action: The user should adjust the input value in the range of [0, 1]. ORA-38607: FI minimum and maximum itemset length not between [1, string] Cause: The inputed minimum or maximum itemset length exceed the internal maximum itemset length or less than 1. Action: The user should adjust the input value not larger than the internal maximum itemset length and not less than 1. ORA-38608: FI itemset minimum-length(string) should not be greater than maximum length(string) Cause: The user inputed minimum length is more than maximum length. Action: The user should adjust the input values to make the minimum length less than or equal to the maximum length. ORA-38609: FI Not enough memory for tree counting, requires at least stringKB Cause: The memory size did not satisfy the minimum memory requirement for tree counting. Action: In workarea_size_policy="manual" mode, set _fic_area_size to a reasonably larger value. Or, In workarea_size_policy="auto" mode, this error should never happen. ORA-38610: FI "string" name prefix is reserved for frequent itemset counting Cause: An error occurred because DBMS_FREQUENT_ITEMSET and prefix ORA_FI are reserved for the DBMS_FREQUENT_ITEMSET package"s internal use. Action: Do not re-define functions with names starting with DBMS_FREQUENT_ITEMSET package or ORA_FI. ORA-38611: FI input cursor"s item type is not supported Cause: The input cursor"s item type is not number or character type Action: Redefine the input cursor so that item type is number or character type. ORA-38612: FI item length cannot exceed half of one database block. Cause: The item"s length was more than half of one database block. Action: Redefine the data type of the item column so that its maximum length is less than half of one database block. ORA-38620: DT expressions in input cursor do not have an alias name Cause: Expressions in input cursor do not have an alias name. Action: Add an alias name for the expression. ORA-38621: Decision Tree maximum depth setting not between [2, 20] Cause: The user specified a max tree depth not in the range of [2, 20]. Action: The user should adjust the input value to be in the range of [2, 20]. ORA-38622: Decision Tree not enough memory, requires at least stringKB Cause: The memory size did not satisfy the minimum memory requirement for decision tree building. Action: In workarea_size_policy="manual" mode, set _dtree_area_size to a reasonably larger value. Or, In workarea_size_policy="auto" mode, please raise pga_aggregate_target to a reasonably larger value. ORA-38700: Limit of string flashback database logs has been exceeded. Cause: The maximum number of flashback database log files was exceeded. Action: DB_FLASHBACK_RETENTION_TARGET may be set to high. Modify it to a smaller value. ORA-38701: Flashback database log string seq 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-38702: Cannot update flashback database log file header. Cause: Could not write to the flashback database log file. Action: Restore access to the file. ORA-38703: Type string in header is not a flashback database log file. Cause: A corrupt flashback database log file header was read. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38704: Checksum error in flashback database log file header. Cause: The flashback database log file header contained a checksum that does not match the value calculated from the file header as read from disk. This means the file header was corrupt. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38705: Expected block size string does not match string in log header. Cause: When the flashback log file header was read, the block size in the control file did not match the block size contained in the header. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38706: Cannot turn on FLASHBACK DATABASE logging. Cause: An ALTER DATABASE FLASHBACK ON command failed. Other messages in the alert log describe the problem. Action: Fix the problem and retry. ORA-38707: Media recovery is not enabled. Cause: An ALTER DATABASE FLASHBACK ON command failed because media recovery was not enabled. Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG command and then retry the command. ORA-38708: not enough space for first flashback database log file Cause: An ALTER DATABASE FLASHBACK ON command failed because there was not enough space in the Recovery Area for the first flashback database log file. Action: Make more space in the Recovery Area. For example, this can be done by increasing the value of DB_RECOVERY_FILE_DEST_SIZE. ORA-38709: Recovery Area is not enabled. Cause: An ALTER DATABASE FLASHBACK ON command failed because the Recovery Area was not enabled. Action: Set DB_RECOVERY_FILE_DEST to a location and retry. ORA-38710: Flashback log version string is incompatible with ORACLE version string. Cause: The flashback database log file was rejected because it appeared to be written by an incompatible version of Oracle. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38711: Corrupt flashback log block header: block string Cause: A corrupt Flashback Database log file block header was read. More information was dumped to the trace file. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38712: Corrupt flashback log record header: block string, offset string. Cause: A corrupt flashback database log record header was read. Either the record type or length were incorrect. More information was dumped to the trace file. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38713: Flashback Database logging is already turned on. Cause: An ALTER DATABASE FLASHBACK ON command had no effect because flashback database logging was already on. Action: No action required. ORA-38714: Instance recovery required. Cause: An ALTER DATABASE FLASHBACK ON command failed because the database either crashed or was shutdown with the ABORT option. Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option. ORA-38715: Invalid log number specified in the DUMP FLASHBACK command. Cause: An invalid log number was used when dumping a flashback database log file. Action: Specify a valid flashback database log number. ORA-38716: Must supply an integer for the TYPE option. Cause: An invalid value was specified for TYPE in the DUMP FLASHBACK command. Action: Specify an integer value. ORA-38717: Invalid DUMP FLASHBACK option. Cause: An invalid option was specified in the DUMP FLASHBACK command. Currently the only options allowed are: DBA, TYPE, and LOGICAL. Action: Retry the command with the correct options. ORA-38718: Invalid thread number specified in the DUMP FLASHBACK command. Cause: An invalid thread number was used in dumping the flashback database log files for a thread. Action: Specify a valid thread number. ORA-38719: Invalid DUMP FLASHBACK object. Cause: An invalid object was specified in a DUMP FLASHBACK command. Currently the only objects allowed are: LOGFILE or THREAD. Action: Retry the command with the correct options. ORA-38720: Missing log file number. Cause: A log file number was missing in a DUMP FLASHBACK LOGFILE command. Action: Supply a valid log file number. ORA-38721: Invalid file number. Cause: An invalid file number was specified in the DBA clause of a DUMP FLASHBACK command. Action: Supply a valid file number. ORA-38722: ON or OFF expected. Cause: The ALTER DATABASE FLASHBACK command was specified without the ON or OFF keyword. Action: Retry the command with the ON or OFF keyword. ORA-38723: Invalid SCN expression. Cause: The SCN keyword was specified in a FLASHBACK DATABASE command but the SCN expression was invalid. Action: Retry the command using a valid SCN number. ORA-38724: Invalid option to the FLASHBACK DATABASE command. Cause: An invalid option was specified to the FLASHBACK DATABASE command. Valid options are: SCN or TIMESTAMP. Action: Correct the syntax and retry the command. ORA-38725: specified name "string" does not match actual "string" Cause: The database name specified in a FLASHBACK DATABASE command did not match the name of the currently mounted database. Action: Correct the database name spelling or DISMOUNT the mounted database and mount the correct database. ORA-38726: Flashback database logging is not on. Cause: A FLASHBACK DATABASE command was tried but flashback database logging has not been enabled. Action: Flashback database logging must be enabled via the ALTER DATABASE FLASHBACK ON command before a FLASHBACK DATABASE command can be tried. If the database must be taken back in time then a restore and incomplete recovery must be performed. ORA-38727: FLASHBACK DATABASE requires a current control file. Cause: The control file being used is a backup control file. Action: FLASHBACK DATABASE cannot be used with a backup control file. If the database must be taken back in time then a restore and an incomplete recovery must be performed. ORA-38728: Cannot FLASHBACK DATABASE to the future. Cause: An SCN or time stamp provided in a FLASHBACK DATABASE command was in the future. Action: Supply a proper SCN or time stamp and retry the command. ORA-38729: Not enough flashback database log data to do FLASHBACK. Cause: There was not enough flashback database log data to do the FLASHBACK DATABASE. Action: If the database must be taken back in time then a restore and incomplete recovery must be performed. ORA-38730: Invalid SCN/TIMESTAMP expression. Cause: The expression supplied in a FLASHBACK DATABASE command was invalid. Action: Retry the command using a valid number or time stamp expression. ORA-38731: Expected version string does not match string in log header. Cause: The version of the flashback database log file header was corrupt. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38732: Expected file size string does not match string. Cause: The file size indicated in the control file did not match the file size contained in the flashback log file header. The flashback database log file was corrupt. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38733: Physical size string less than needed string. Cause: A flashback database log file shrank in size. This was likely to have been caused by operator or operating system error. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38734: Flashback log is inconsistent; belongs to another database. Cause: The database ID in the flashback database log file did not match the database ID in the control file. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38735: Wrong log number string in flashback log file header. Cause: The log file number in the flashback database log file did not match the control file. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38736: Wrong thread number string in flashback log file header. Cause: The thread number in the flashback database log file did not match the control file. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38737: Expected sequence number string doesn"t match string Cause: The flashback database log is corrupted or is an old version. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38738: Flashback log file is not current copy. Cause: A check of flashback database log file header at database open found that the flashback database log appeared to be an incorrectly restored backup. Flashback database log files cannot be backed up and restored. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38739: Flashback log file is more recent than control file. Cause: The control file change sequence number in the flashback database log file was greater than the number in the control file. This implies that the wrong control file was 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: FLASHBACK DATABASE can only be used with the current control file. If it is not available, then a restore and an incomplete recovery must be performed instead. ORA-38740: Usable blocks value string is not valid. Cause: A flashback database log file header contained a usable blocks value greater than the file size. The flashback database log file file is corrupt. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38741: Formatted blocks value string is not valid. Cause: The formatted blocks value in the flashback database log file was greater than the file size. The flashback database log file was corrupt. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38742: Flashback log file has incorrect log reset status. Cause: The flashback database log file header had log reset data that was different than the control file. The log was probably an incorrectly restored backup. Flashback database logs cannot be backed up. Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead. ORA-38743: Time/SCN is in the future of the database. Cause: The Time/SCN provided in a FLASHBACK DATABASE command was in the future of the database. Action: Retry the command with a correct Time/SCN or RECOVER the database. ORA-38744: file string is not the same file seen at start of flashback Cause: A different copy of the file was accessed the last time FLASHBACK DATABASE looked at the file header. A backup of the file was restored or the meaning of the file name changed during FLASHBACK DATABASE. Action: Ensure the correct file is available, then retry FLASHBACK DATABASE. ORA-38746: error occurred while restoring data block (file# string, block# string) Cause: An error occurred during a FLASHBACK DATABASE command. See other errors on error stack. Action: Investigate why the error occurred. It may be that the flashback database log data is corrupt. If so, a restore and an incomplete recovery must be performed instead. ORA-38747: corrupt before image (file# string, block# string) Cause: A corrupt data block before image was encountered during a FLASHBACK DATABASE command. Action: The flashback log data is probably corrupt. If so, a restore and an incomplete recovery must be performed instead. ORA-38748: cannot flashback data file string - file is in use or recovery Cause: An attempt to do FLASHBACK DATABASE found that the file was not available for recovery. Either it was online and the database was open in some instance, or another process was currently doing media recovery or flashback on the file. Action: Do not do FLASHBACK DATABASE. ORA-38749: A media recovery has been started. Cause: An attempt was made to start a FLASHBACK DATABASE in the same session as a media recovery. Action: Complete or cancel the first media recovery session. ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher. Cause: An attempt was made to use a dispatcher process for FLASHBACK DATABASE. Memory requirements disallow this recovery method. Action: Connect to the instance via a dedicated server process to perform FLASHBACK DATABASE. ORA-38752: file string does not exist Cause: During an RMAN FLASHBACK DATABASE conversation, a file was listed which was not part of the database. The RMAN conversation was aborted. Action: Retry the conversation with the appropriate file numbers. ORA-38753: Cannot flashback data file string; no flashback log data. Cause: An attempt to perform a FLASHBACK DATABASE failed because the file does not have enough flashback log data to cover the time to flash back. Either the file did not have flashback generation enabled for it, or had flashback generation turned off for it some time during the time span of the flashback. Action: The file cannot be flashed back. The file must be taken offline or the tablespace dropped before continuing with the FLASHBACK DATABASE command. ORA-38754: FLASHBACK DATABASE not started; required redo log is not available Cause: A FLASHBACK DATABASE command did not start. A redo log needed for the recovery part of FLASHBACK DATABASE could not be found or accessed. Action: See trace files for details of the problem. ORA-38755: Flashback is already turned on for this tablespace. Cause: An attempt was made to turn on flashback database logging for a tablespace that already has flashback turned on. Action: No action required. ORA-38756: Flashback is already turned off for this tablespace. Cause: An attempt was made to turn off flashback database logging for a tablespace that already has flashback off. Action: No action required. ORA-38757: Database must be mounted and not open to FLASHBACK. Cause: An attempt to Flashback a database was made when the database was not mounted or was already open. Action: Mount the database and retry the FLASHBACK command. ORA-38758: cannot flashback data file string; restored since last recovery Cause: An attempt to do FLASHBACK DATABASE found that the file was restored since the last standby recovery. The file cannot be flashed back. Action: The file must be taken offline before continuing with the FLASHBACK DATABASE command. ORA-38759: Database must be mounted by only one instance and not open. Cause: An attempt to turn on or off Flashback Database logging was made when the database was open or mounted by more than one instance. Action: Mount the database in only one instance and retry the command. ORA-38760: This database instance failed to turn on flashback database Cause: Database flashback is on but this instance failed to start generating flashback data. Look in alert log for more specific errors. Action: Correct the error or turn off database flashback. ORA-38761: redo log sequence string in thread string, incarnation string could not be accessed Cause: A redo log needed for the recovery portion of FLASHBACK could not be read or opened. The FLASHBACK operation failed. Action: Restore the log and retry the FLASHBACK command. ORA-38762: thread string redo log with scn string could not be found Cause: A redo log needed for the recovery portion of FLASHBACK could not be found. The FLASHBACK operation failed. Action: Restore the log and retry the FLASHBACK command. ORA-38763: flashback not started; enabled threads have changed Cause: A FLASHBACK DATABASE command did not start. The set of enabled threads changed during the time to flash back. Action: The flashback cannot be performed. Perform a restore and an incomplete recovery instead. ORA-38764: flashback not started; datafile string enabled threads are different Cause: A FLASHBACK DATABASE command did not start. The datafile was restored from a backup taken when the enabled threads were different than at the time of the flashback. Action: The flashback cannot be performed. Perform a restore and an incomplete recovery instead. ORA-38765: Flashed back database cannot be opened read-only. Cause: A complete recovery was performed after a database flashback but the database was not opened for read-write access, or a FLASHBACK DATABASE command failed. Action: If a complete recovery was performed after a database flashback, open the database for read-write access. If a FLASHBACK DATABASE command failed, fix what caused the command to fail and retry the command, or recover and open the database for read-write access. ORA-38766: cannot flashback data file string; file resized smaller Cause: An attempt to do FLASHBACK DATABASE found that the file was shrunk during the time to flash back. Action: The file cannot be flashed back. The file must be taken offline or the tablespace dropped before continuing with the FLASHBACK DATABASE command. ORA-38767: flashback retention target parameter mismatch Cause: The value of parameters DB_FLASHBACK_RETENTION_TARGET must be same in all instances. All databases must have same flashback retention target parameters. Action: Check DB_FLASHBACK_RETENTION_TARGET values in all instances. ORA-38768: resizing datafile string failed Cause: An operating system error occurred when Flashback Database tried to shrink (resize) a datafile. Flashback shrinks a file in order to undo the effects of a file expand, for example, an autoextension of the file. Action: Recover the database to return it to its previous state, or fix the cause of the operating system error and retry the Flashback. If that is not possible, then the file can be taken offline and the Flashback command retried. The file will have to be restored from a backup and rolled forward. ORA-38769: FLASHBACK DATABASE failed after modifying data. Cause: A FLASHBACK DATABASE command failed after modifying the the database. Look in the alert log for more information about the failure. Action: Recover the database to return it to its previous state, or fix the cause of the error and retry the Flashback. ORA-38770: FLASHBACK DATABASE failed during recovery. Cause: A FLASHBACK DATABASE command successfully restored the database but failed during the recovery step. Look in the alert log for more information about the failure. Action: Fix the error and then recover the database to the same SCN or timestamp used in the FLASHBACK DATABASE command. ORA-38771: unnamed datafile(s) added to control file by flashback recovery Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile that could not be added to the control file. An entry has been added to the control file for the new datafile, but with the file name UNNAMEDnnnn, where nnnn is the file number. Related error messages provide the file names that were originally used to create the files. Action: Rename the file in the control file, or use the ALTER ALTER DATABASE CREATE DATAFILE command to create a file suitable for recovery. If the file is not going to be recovered, then take it offline with the FOR DROP option. The recovery step of Flashback can be resumed by entering a RECOVERY command with the same SCN or timestamp as used in the FLASHBACK DATABASE command. For example, RECOVER AUTOMTAIC DATABASE UNTIL CHANGE . ORA-38772: cannot add datafile "string" - file could not be created Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile and could not recreate the file. 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. ORA-38773: cannot add data file "string" - file already part of database Cause: The recovery step of FLASHBACK database encountered the creation of a datafile and could not create the file because the file name is already in use in the database. The control file file entry for the file is "UNNAMEDnnnnn". Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file with a different name. ORA-38774: cannot disable media recovery - flashback database is enabled Cause: An attempt was made to disable media recovery while flashback database was enabled. Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable flashback database, then disable media recovery. ORA-38775: cannot disable flash recovery area - flashback database is enabled Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while flashback database was enabled. Flashback database requires DB_RECOVERY_FILE_DEST to be set. Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable flashback database, then disable the flash recovery area. ORA-38776: cannot begin flashback generation - flash recovery area is disabled Cause: During a database mount, the RVWR process discovered that the flash recovery area was disabled. DB_RECOVERY_FILE_DEST must have been set null or removed from the INIT.ORA file while the database was unmounted. Action: Flashback database requires the flash recovery area to be enabled. Either enable the flash recovery area by setting the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters, or turn off flashback database with the ALTER DATABASE FLASHBACK OFF command. ORA-38777: database must not be started in any other instance. Cause: A command was attempted that required the database to be mounted in this instance and not started in any other instance. Standby database recovery through a RESETLOGS and ALTER DATABASE OPEN RESETLOGS require that the database be started in only one instance if flashback database logging is enabled. Action: Ensure that the no other instances are started. Then retry the command. ORA-38778: Restore point "string" already exists. Cause: The restore point name of the CREATE RESTORE POINT command already exists. A restore point name must be unique. Action: Either use a different name or delete the existing restore point with the same name. ORA-38779: cannot create restore point - too many restore points. Cause: The maximum number of restore points already have been created. Action: Delete some existing restore point and retry the operation. ORA-38780: Restore point "string" does not exist. Cause: The restore point name of the DROP RESTORE POINT command does not exist. Action: No action required. ORA-38781: cannot disable media recovery - have guaranteed restore points Cause: An attempt was made to disable media recovery while there is at least one guaranteed restore point. Action: Drop all guaranteed restore points and then disable media recovery. ORA-38782: cannot flashback database to non-guaranteed restore point "string" Cause: An attempt was made to flashback database to a non-guaranteed restore point while flashback database is off. You can only flashback a database to guaranteed restore point when flashback database is not on. Action: Consider picking a guaranteed restore point to flashback the database to, if there is one. ORA-38783: Instance recovery required. Cause: An attempt was made to create a restore point when the database is in mount mode but it was not shutdown cleanly before it was mounted. In order to create a restore point when the database is mounted, the database must be shutdown cleanly before it is mounted. Action: Consider one of the following: 1. Create the restore point after opening the database. 2. Open the database, shut it down cleanly, mount the database, and retry creating the restore point. ORA-38784: Cannot create restore point "string". Cause: An attempt to create a restore point failed. See other errors on the error stack for the specific reason. Action: Fix the problem and retry. ORA-38785: Media recovery must be enabled for guaranteed restore point. Cause: Media recovery is not enabled. Media recovery must be enabled in order to create a guaranteed restore point. Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG statement and then retry the command. ORA-38786: Flash recovery area is not enabled. Cause: An attempt was made to perform a command that requires Flash recovery area to be enabled. Action: Set DB_RECOVERY_FILE_DEST to an appropriate location and retry. ORA-38787: Creating the first guaranteed restore point requires mount mode when flashback database is off. Cause: While flashback database is not on, an attempt was made to create the first guaranteed restore point while the database is open. Action: Mount the database and retry. ORA-38788: More standby database recovery is needed Cause: An attempt was made to create a restore point or a guaranteed while a physical standby database is not cleanly checkpointed. Action: Perform more standby database recovery via managed standby database recovery. Cancel managed recovery and retry the command. ORA-38790: BEFORE must be specified with RESETLOGS Cause: The FLASHBACK DATABASE command included the RESETLOGS parameter but not the BEFORE parameter. Action: Retry the command with TO BEFORE RESETLOGS. ORA-38791: flashback did not start because file string was not in a valid incarnation Cause: Flashback could not be started because a file was checkpointed or fuzzy at a point where the file can neither be restored nor recovered to our restore target. In order for a file to be brought to the restore target, the file has to be in one of the incarnations along the ancestral path from the current incarnation to the restore incarnation. Action: Manually restore or recover the file to a point where it is in one of the incarnations along the ancestral path from the current incarnation to the restore incarnation. ORA-38792: encountered unknown flashback record from release string Cause: A Flashback Database logfile contains a record written by a future Oracle release and is unknown by this release. Action: The given release of Oracle must be installed in order to use these flashback database log files. ORA-38793: cannot FLASHBACK the database to a future SCN/time Cause: The Flashback Database target SCN/timestamp is greater than the current database SCN/timestamp and the database incarnation is not the last opened incarnation. Action: If the target SCN/timestamp is in the current incarnation or a child incarnation whose branch point is after the current database SCN then RECOVER DATABASE to the target SCN/time. If the target SCN/timestamp is in a child incarnation whose branch point is prior to the current database SCN then FLASHBACK DATABASE to before the branch point. Next use RMAN to reset the database to the child incarnation. Finally, RECOVER DATABASE to the target SCN/time. ORA-38794: Flashback target time not in current incarnation Cause: The Flashback Database target timestamp is not in the database"s current incarnation or any of its ancestors. Action: Use a different target timestamp or use RMAN to reset the database to the appropriate incarnation. ORA-38795: warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below Cause: Flashback Database 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 is that Flashback Database had to add a file back to the control file but could not restore the file"s contents. Action: If a backup is available, restore the backup, online the file, and recover the database to the original flashback target scn or timestamp. If a backup is not available, but the redo from the file creation to the target scn or timestamp is available, then create the file using the ALTER DATABASE CREATE DATAFILE command, bring the file online, and recover the database to the original flashback target scn or timestamp. ORA-38796: Not enough flashback database log data to undo FLASHBACK. Cause: There was not enough flashback log data to undo the flashback so a flashback was not started. Action: It is still possible to get to the restore target by doing a flashback until the resetlogs branch point of the restore target is reached. This can be done by executing multiple "flashback to before resetlogs" commands, or by doing a flashback to the exact time or SCN of the desired resetlogs branch point. Note that this flashback cannot be undone should an error occur. The only option is to complete the flashback. ORA-38797: Full database recovery required after a database has been flashed back Cause: An attempt was made to recover some datafiles or tablespaces of a database after the database had been flashed back. In order to recover control file and all datafiles correctly, full database recovery is required after a database has been flashed back. Action: Recover the whole database instead. ORA-38798: Cannot perform partial database recovery Cause: See other other messages on error stack for the cause. Action: See other other messages on error stack for the action. ORA-38850: an enabled thread missing from control file Cause: A CREATE CONTROLFILE statement was given that did not list all the enabled threads for the database. Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads. ORA-38851: cannot mark the current instance (redo thread) as disabled Cause: The standby switchover or failover operation failed because it needs to mark the current instance (redo thread) as disabled. Action: Shut down this instance and start up using a different instance name or redo thread number and retry. ORA-38852: cannot mark the current instance (redo thread) as disabled Cause: The open resetlogs or standby activation operation failed because it must use a different instance (redo thread) than the current instance (redo thread) to open the database. Action: Shut down this instance and start up using a different instance name or redo thread number and retry. ORA-38853: cannot mark instance string (redo thread string) as disabled Cause: The standby switchover or failover operation failed because it needs to mark an instance (redo thread) as disabled. That instance was up, which prevented it from being disabled. Action: Shut down the specified instance and retry this command. ORA-38854: cannot mark instance string (redo thread string) as disabled Cause: The open resetlogs or standby activation operation failed because it needs to mark an instance (redo thread) as disabled. That instance was up, which prevented it from being disabled. Action: Shut down the specified instance and retry this command. ORA-38855: cannot mark instance string (redo thread string) as enabled Cause: The standby switchover or failover operation failed because it needs to mark an instance (redo thread) as enabled. However, it had less than 2 online redo logs, which prevented it from being enabled. Action: Add more logfiles to the specified instance and retry the command. ORA-38856: cannot mark instance string (redo thread string) as enabled Cause: The open resetlogs or standby activation operation failed because it needs to mark an instance (redo thread) as enabled. However, it had less than 2 online redo logs, which prevented it from being enabled. Action: Add more logfiles to the specified instance and retry the command. ORA-38857: cannot mark redo thread string as enabled Cause: The standby switchover or failover operation failed because it needs to mark a redo thread as enabled. However, the control file was recreated with a MAXINSTANCES value smaller than the thread number of the redo thread. Action: Recreate the control file with a larger MAXINSTANCES value. ORA-38858: cannot mark redo thread string as enabled Cause: The open resetlogs or standby activation operation failed because it needs to mark a redo thread as enabled. However, the control file was recreated with a MAXINSTANCES value smaller than the thread number of the redo thread. Action: Recreate the control file with a larger MAXINSTANCES value. ORA-38859: instance string (thread string) is not ready to be disabled Cause: The command attempted to switch the instance (thread) into a new log before disabling it. The switch attempt failed because all eligible online logs were either being cleared or not completely archived yet. Action: Wait a few minutes and retry. ORA-38860: cannot FLASHBACK DATABASE during instantiation of a logical standby Cause: The command was not permitted because the controlfile indicates the database was in the process of becoming a logical standby database but the controlfile conversion had not completed. Action: If in the process of creating a logical standby database, perform the remaining instantiation procedures to completion. If this flashback operation followed a Data Guard failure, permit the errant Data Guard operation to successfully complete. Once the instantiation is complete, reissue the flashback operation. ORA-38861: flashback recovery stopped before reaching recovery target Cause: Flashback recovery on the standby ended early because the user attempted to flashback to an SCN or time for which there were no redo logs. Most likely, the user is trying to flashback to a future time in the database that the database has never recovered through. Check the alert log to find out which SCN the database recovered to. Action: Flashback to an older SCN or acquire the necessary redo logs. ORA-38862: FLASHBACK DATABASE in progress Cause: The operation could not be performed while FLASHBACK DATABASE was in progress. Action: Wait for the FLASHBACK DATABASE to complete. ORA-38900: missing mandatory column "string" of error log table "string" Cause: Mandatory column of error logging table is not present Action: Add the named column to the error logging table. Consult ORACLE documentation for the correct data type. ORA-38901: column "string" of table "string" must be one of the first "number" columns Cause: Mandatory information column of error logging table is present, but must be at the beginning of the row. Action: Create the error logging table correctly. Consult ORACLE documentation for the correct format of an error logging table. ORA-38902: errors in array insert exceed string Cause: The operation failed because the array INSERT had more errors than can be stored internally for BATCH ERRORs. Action: Do not use BATCH ERROR mode when array INSERT has more error rows than the number specified in the error. ORA-38903: DML error logging is not supported for abstract column "string" Cause: A DML Error Logging operation was attempted on a table which has an ADT, REF, VARRAY, or nested table column type, and the error logging table referred to the specified column. Action: Either do not use DML Error Logging on such a table or remove the offending column from the error logging table. The scalar columns can be logged, but not abstract column types. ORA-38904: DML error logging is not supported for LOB column "string" Cause: A DML Error Logging operation was attempted on a table which has a CLOB, NCLOB, or BLOB column type, and the error logging table referred to the specified column. Action: Either do not use DML Error Logging on such table or remove the offending column from the error logging table. The scalar columns can be logged, but not LOB column types. ORA-38905: DML error logging is not supported for LONG column "string" Cause: A DML Error Logging operation was attempted on a table which has a LONG, or LONG RAW column type, and the error logging table referred to the specified column. Action: Either do not use DML Error Logging on such a table or remove the offending column from the error logging table. The scalar columns can be logged, but not long column types. ORA-38906: insert into DML Error Logging table "string" failed Cause: An error occurred when attempting to log a DML Error on behalf of the DML Error logging clause. This may be intended if a trigger is defined on the error table (which in turn errors out in certain cases). Action: Determine root cause of error (in error stack). ORA-38907: DML error logging is not supported for FILE column "string" Cause: A DML Error Logging operation was attempted on a table which has a BFILE column and the Error Logging table referred to the specified column. Action: Either don"t use DML Error Logging on such table or remove the offending column from the error logging table. The scalar columns can be logged, but not BFILE column types. ORA-38908: internal error occurred during DML Error Logging Cause: An unexpected error occurred while executing recursive SQL to insert a row into the DML Error Logging table. Action: Report this error to Oracle Support. ORA-38950: Source platform string not cross platform compliant Cause: Cross platform transport was not allowed for this platform. Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM. ORA-38951: Target platform string not cross platform compliant Cause: Cross platform transport was not allowed for this platform. Action: none ORA-38952: Source database not 10.0.0.0 compatible Cause: Cross platform transport is not supported unless database compatibility is advanced to 10.0.0.0 or higher Action: Use the compatible parameter to advance source database compatibility and redo the transport ORA-38954: Cross platform transport is not supported between source platform identifier string and target platform identifier string Cause: The platform identifier in the transported file indicated that the datafile format was different than the target database datafile format. Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM. If both platforms are present, Contact Oracle support ORA-38955: Source platform string not cross platform compliant Cause: The platform identifier in the transported file indicated that this platform is not supported for a cross platform transport. Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM. ORA-38956: Target platform string not cross platform compliant Cause: Cross platform transport was not allowed for this platform. Action: For a list of supported platforms, query fixed view SYS.V$TRANSPORTABLE_PLATFORM. ORA-38957: Target database not 10.0.0.0 compatible Cause: Cross platform transport is not supported unless database compatibility is advanced to 10.0.0.0 or higher Action: Use the compatible parameter to advance source database compatibility ORA-38958: Source platform string is in different byte order than target platform string Cause: Probably a conversion was not done before the import phase of the transport. Action: Use RMAN CONVERT functionality to convert endian ordering. ORA-38959: Failed to update block 0 to new version 10 format Cause: An attempt was made to update block 0 to version 10 format. Action: check additional error messages and contact Oracle Support Services. ORA-39000: bad dump file specification Cause: The user specified a dump file that could not be used in the current job. Subsequent error messages describe the inadequacies of the dump file. Action: Specify a dump file that is usable for the job. ORA-39001: invalid argument value Cause: The user specified API parameters were of the wrong type or value range. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error. Action: Correct the bad argument and retry the API. ORA-39002: invalid operation Cause: The current API cannot be executed because of inconsistencies between the API and the current definition of the job. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error. Action: Modify the API call to be consistent with the current job or redefine the job in a manner that will support the specified API. ORA-39003: unable to get count of total workers alive Cause: Attempt to get count of total worker processes alive failed. Action: Check the additional error messages to see what caused the failure. Correct the error, if possible, and try the operation again. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39004: invalid state Cause: The state of the job precludes the execution of the API. Action: Rerun the job to specify the API when the job is an appropriate state. ORA-39005: inconsistent arguments Cause: The current API cannot be executed because of inconsistencies between arguments of the API call. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error. Action: Modify the API call to be consistent with itself. ORA-39006: internal error Cause: An unexpected error occurred while processing a Data Pump job. Subsequent messages supplied by DBMS_DATAPUMP.GET_STATUS will further describe the error. Action: Contact Oracle Customer Support. ORA-39012: Client detached before the job started. Cause: The client detached or ended their session before the Data Pump job was started. Action: Create new job and remain attached to the job until it is started. ORA-39014: One or more workers have prematurely exited. Cause: One or more of the worker processes exited before the job was completed. With no workers, the master process will terminate the job. Action: Rerun the job. If problem persists, contact Oracle Customer Support. ORA-39015: job is not running Cause: An API was executed that required the job to be running, but the job was not active. Action: Retry the API. If problem persists, contact Oracle Customer Support. ORA-39016: Operation not supported when job is in string state. Cause: The state of the job precludes the execution of the API. Action: Rerun the job to specify the API when the job is an appropriate state. ORA-39017: Worker request not supported when job is in string state. Cause: The state of the job precludes the execution of a worker request. This is an internal error. Action: Contact Oracle Customer Support. ORA-39018: master process received invalid message number string Cause: Internal Error Action: Contact Oracle Customer Support. ORA-39019: invalid operation type string Cause: User specified an invalid operation name on an DBMS_DATAPUMP.OPEN API or an invalid operation name was specified in the master table for a restart API. Action: Correct the operation name and recreate the job. ORA-39020: invalid mode type string Cause: User specified an invalid mode on an DBMS_DATAPUMP.OPEN API or an invalid mode was specified in the master table for a restart API. Action: Correct the mode and recreate the job. ORA-39021: Database compatibility version string is not supported. Cause: User selected COMPATIBLE as the version on an DBMS_DATAPUMP.OPEN API, but the current database compatibility version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump. Action: Specify a supported version and recreate the job. ORA-39022: Database version string is not supported. Cause: User selected LATEST as the version on an DBMS_DATAPUMP.OPEN API, but the current database version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump. Action: Specify a supported version and recreate the job. ORA-39023: Version string is not supported. Cause: User specified an explicit version on an DBMS_DATAPUMP.OPEN API, but the current database version is not supported by the Data Pump API. Database versions before 9.2 are not supported by the Data Pump. Action: Specify a supported version and recreate the job. ORA-39024: wrong schema specified for job Cause: Internal error caused by the master process finding inconsistencies between the schemas specified for the job. Action: Contact Oracle Customer Support. ORA-39025: jobs of type string are not restartable Cause: Attempt to restart a job which was not restartable. Action: Recreate the job via the open API. ORA-39026: master table is inconsistent on validation string Cause: Job cannot be restarted because it failed a validation check. Validation checks are of the form -xx.y where -xx is the value of the PROCESS_ORDER column in the master table where the error was detected and y is the actual validity check for the row. Action: Recreate the job. If master table has not been modified, but problem persists, contact Oracle Customer Support. ORA-39027: wrong version of master table Cause: Job cannot be restarted because the version of the database upon which the job started is different than the current version of the database and the format of the master table has changed between the versions. Action: Recreate the job. ORA-39028: cannot restart job from string state Cause: The job was not in a suitable state for restart. Jobs must begin executing before they can be restarted. Action: Recreate the job. ORA-39029: worker string with process name "string" prematurely terminated Cause: The specified worker process terminated unexpectedly. Subsequent messages describe the reason for the termination. Action: If problem persists, contact Oracle Customer Support. ORA-39030: invalid file type string Cause: An invalid filetype was specified for an DBMS_DATAPUMP.ADD_FILE API call. Action: Correct the filetype parameter and reissue the API request. ORA-39031: invalid filter name string Cause: An invalid filter name was specified on a DBMS_DATAPUMP.DATA_FILTER Action: Correct the filter name parameter and reissue the API request. ORA-39032: function string is not supported in string jobs Cause: The specified API is not supported for the specified class of jobs. Action: Recreate the job with the appropriate mode or operation type. ORA-39033: Data cannot be filtered under the direct path access method. Cause: The user specified that the data access method for the job was direct which precludes the use of certain data filters. Action: Use the SUBQUERY or the SAMPLE data filter with the automatic data access method. ORA-39034: Table string does not exist. Cause: The user referenced a table in an API that did not exist. Action: Correct table name and retry API. ORA-39035: Data filter string has already been specified. Cause: The user has already specified a data filter that matches on the filter name, schema name, and table. Action: Specify a different data filter. ORA-39036: invalid metadata filter name string Cause: An invalid metadata filter name was specified on a DBMS_DATAPUMP.METADATA_FILTER API call. Action: Correct the metadata filter name parameter and reissue the API request. ORA-39037: Object type path not supported for string metadata filter. Cause: An object type path was specified for the filter, but the filter does not support the object type path parameter. Action: Remove the object type path parameter. ORA-39038: Object path "string" is not supported for string jobs. Cause: The specified object type path is invalid for the job mode. Action: Correct the object type path. ORA-39039: Schema expression "string" contains no valid schemas. Cause: The specified SCHEMA_EXPR filter resulted in no schemas being selected. Action: Correct the the SCHEMA_EXPR filter specification. ORA-39040: Schema expression "string" must identify exactly one schema. Cause: For TABLE mode jobs, the SCHEMA_EXPR filter must identify exactly one schema. Action: Correct the the SCHEMA_EXPR filter specification. ORA-39041: Filter "string" either identifies all object types or no object types. Cause: A Metadata filter specifying path names either returned all objects or no objects in the job. Action: Correct the the metadata filter specification. ORA-39042: invalid transform name string Cause: An invalid transform name was specified on a DBMS_DATAPUMP.METADATA_TRANSFORM API call. Action: Correct the transform name parameter and reissue the API request. ORA-39043: Object type string is not supported for string. Cause: The specified object type is invalid for the specified transform or remap. Action: Correct the object type. ORA-39044: Metadata transform string has already been specified. Cause: The user has already specified the metadata transform for the same class of object types. Action: Specify a different object_type for the transform. ORA-39045: invalid metadata remap name string Cause: An invalid metadata remap name was specified on a DBMS_DATAPUMP.METADATA_REMAP API call. Action: Correct the metadata remap name parameter and reissue the API request. ORA-39046: Metadata remap string has already been specified. Cause: The user has already specified a metadata remap that matches on the remap name and original value. Action: Specify a different original value. ORA-39047: Jobs of type string cannot use multiple execution streams. Cause: The user specified a value of parallelism that is precluded by the operation type or mode of the job. Action: Specify only a parallelism of 1 for this type of job. ORA-39048: Unable to start all workers; only string worker(s) available. Cause: The full degree of parallelism could not be honored due process limits, resource limits, or other internal errors. Action: Increase process/resource limits for the job. ORA-39049: invalid parameter name string Cause: An invalid parameter name was specified on a DBMS_DATAPUMP.SET_PARAMETER API call. Action: Correct the parameter name and reissue the API request. ORA-39050: parameter string is incompatible with parameter string Cause: Two parameters were set that were incompatible with each other. Only the first parameter setting will be used. Action: Decide which parameter is to be used and stick to it. ORA-39051: parameter string specified multiple times Cause: The user has already specified a parameter that matches on the name and the specific parameter doesn"t support duplicate definitions. Action: Specify non-repeatable parameters only once. ORA-39052: cannot specify SKIP_CURRENT on initial start of a job. Cause: The user has already specified SKIP_CURRENT for a job that has never executed. Action: Only specify SKIP_CURRENT when restarting a job. ORA-39053: parameter or attribute string must be defined for a string job Cause: The job being defined cannot be started because it is missing the specified definition. Action: Specify the omitted parameter or attribute before starting the job. ORA-39054: missing or invalid definition of the SQL output file. Cause: The job being defined cannot be started because it is missing the file to receive the SQL output of the job or the definition is unusable. Action: Specify a valid directory name and file name for the SQL file. ORA-39055: The string feature is not supported in version string. Cause: The user attempted to use a feature that was not enabled in the database version specified for the current job. Typically, this error occurs if the compatibility level of the database is below the current version of the database or if the user explicitly specifies a version for a Data Pump job. Action: Specify the current database version as a version parameter for the the job. ORA-39056: invalid log file specification. Cause: The log file for the job was incorrectly specified. Action: Specify a valid directory name and file name for the log file. ORA-39057: invalid worker request string for string jobs. Cause: The worker process sent a message that wasn"t supported for the current job. Action: Internal error -- contact Oracle Customer Support and report the error. ORA-39058: current object skipped: string of type string Cause: The user specified SKIP_CURRENT when restarting a job. This message is a confirmation that the object will not be imported. Action: User must manually define the object in the target database. ORA-39059: dump file set is incomplete Cause: An IMPORT or SQL_FILE operation was being performed but not all of the files from the EXPORT dump file set were included. Action: Check the export log file and make sure all of the files that were exported are included in the current job. ORA-39060: table(s) dropped because of conflict with master table Cause: A table specified by a job was not included because its definition would collide with the master table definition for the current job. Action: After the job completes. Import the conflicting tables using a unique job name to avoid conflicts with normal user tables. ORA-39061: import mode string conflicts with export mode string Cause: The mode used for import cannot be used with a dump file set of specified mode. Transportable jobs are not compatible with other modes. Action: Perform the import using a mode compatible with the export. ORA-39062: error creating master process string Cause: An attempt to create the listed master process failed. Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39064: unable to write to the log file Cause: Errors were detecting while writing to the log file. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39065: unexpected master process exception in string Cause: An unhandled exception was detected internally within the master control process for the Data Pump job. This is an internal error. messages will detail the problems. Action: If problem persists, contact Oracle Customer Support. ORA-39067: Unable to close the log file. Cause: Errors were detecting while closing the log file. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39068: invalid master table data in row with PROCESS_ORDER=string Cause: A corruption was detected in the master table in the specified row(s). Either the row wasn"t found, it was missing columns or had illegal values in its columns. Action: Rerun the job with an uncorrupted master table. ORA-39070: Unable to open the log file. Cause: Errors were detecting while opening the log file. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39071: Value for string is badly formed. Cause: The value of the user specified filter did not contain a legitimate SQL clause. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39076: cannot delete job string for user string Cause: Unable to delete a job. Refer to the any following or prior error messages for clarification. Action: Eliminate the problems indicated. ORA-39077: unable to subscribe agent string to queue "string" Cause: The Data Pump"s communication layer was unable to attach one of its processes to the control or status queue. Subsequent messages will detail the problem. Action: Fix the problem if possible, or contact Oracle Customer Support. ORA-39078: unable to dequeue message for agent string from queue "string" Cause: The Data Pump"s communication layer was unable to retrieve a message from the control or status queue. Subsequent messages will detail the problem. Action: Fix the problem if possible, or contact Oracle Customer Support. ORA-39079: unable to enqueue message string Cause: The Data Pump"s communication layer was unable to send the specified message on the control or status queue. Subsequent messages will detail the problem. Action: Fix the problem if possible, or contact Oracle Customer Support. ORA-39080: failed to create queues "string" and "string" for Data Pump job Cause: The Data Pump"s communication layer was unable to create the status and control queues required for interprocess communication. Subsequent messages will detail the problem. Action: Fix the problem if possible, or contact Oracle Support. ORA-39081: failed to unsubscribe agent string from queue "string" Cause: The Data Pump"s communication layer was unable to unsubscribe a process from the control or status queue. Subsequent messages will detail the problem. Action: Fix the problem if possible, or contact Oracle Customer Support. ORA-39082: Object type string created with compilation warnings Cause: The object in the SQL statement following this error was created with compilation errors. If this error occurred for a view, it is possible that the base table of the view was missing. Action: This is a warning. The object may have to be recompiled before being used. ORA-39083: Object type string failed to create with error: string Failing sql is: string Cause: Examine original error code to determine actual cause Action: Original error code will contain more information ORA-39084: cannot detach job string for user string Cause: Unable to detach a job from the session. Refer to any following error messages for clarification. Action: Eliminate the problems indicated. ORA-39085: cannot update job string for user string Cause: Unable to update the fixed table information for a job. Refer to any following or prior error messages for clarification. Action: Eliminate the problems indicated. ORA-39086: cannot retrieve job information Cause: Unable to retrieve fixed table information for a job. Refer to the secondary error messages that follow this one for clarification. Action: Eliminate the problems indicated by the secondary errors. ORA-39087: directory name string is invalid Cause: A corresponding directory object does not exist. Action: Correct the directory object parameter, or create a corresponding directory object with the CREATE DIRECTORY command. ORA-39088: file name cannot contain a path specification Cause: The name of a dump file, log file, or sql file contains a path specification. Action: Use the name of a directory object to indicate where the file should be stored. ORA-39090: Cannot add devices to file oriented job. Cause: Attempt to add a device to a job that already contains more than one disk file. Action: Only specify one file for jobs that contain sequential devices. ORA-39091: unable to determine logical standby and streams status Cause: An error occurred when determining if the Data Pump job needed to support logical standby or streams. Action: The subsequent message describes the error that was detected. Correct the specified problem and restart the job. ORA-39092: unable to set SCN metadata for object "string.string" of type string Cause: An error occurred when applying a SCN to the specified object to support logical standby or streams. Action: The subsequent message describes the error that was detected. Correct the specified problem and restart the job. ORA-39093: FLASHBACK automatically enabled to preserve database integrity. Cause: A Data Pump job was required to enable flashback support to specific SCNs in order to preserve the consistency of a logical standby or streams instantiation. Action: None ORA-39094: Parallel execution not supported in this database edition. Cause: Parallel execution of Data Pump jobs is not supported for this database edition. Action: Specify a parallelism of 1 for jobs not running on Enterprise Edition databases. ORA-39095: Dump file space has been exhausted: Unable to allocate string bytes Cause: The Export job ran out of dump file space before the job was completed. Action: Reattach to the job and add additional dump files to the job restarting the job. ORA-39096: invalid input value string for parameter string Cause: A NULL or invalid value was supplied for the parameter. Action: Correct the input value and try the call again. ORA-39097: Data Pump job encountered unexpected error string Cause: An unexpected, potentially non-fatal error occurred while processing a Data Pump job. Action: Contact Oracle Customer Support. ORA-39098: Worker process received data objects while loading metadata. Invalid process order range is string..string Cause: This is an internal error. Messages will detail the problem. Action: If problem persists, contact Oracle Customer Support. ORA-39099: cannot create index for "string" on master table string Cause: One or more indexes couldn"t be created on the master table. subsequent error messages describe the failure. Action: Correct the condition that is preventing the indexes from being created. ORA-39102: Timeout before master process string finished initialization. Master error: Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit. Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39103: Timeout before worker process string finished initialization. Worker error: Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit. Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39104: cannot call this function from a SQL parallel query slave process Cause: Called a Data Pump process model function from a process which is a SQL parallel query slave process Action: A SQL parallel query slave process cannot create a Data Pump master process. This is not supported. If this error occurs from a Data Pump client (for example, expdp or impdp), contact Oracle Customer Support and report the error. ORA-39105: Master process string failed during startup. Master error: Cause: The master process whose name is listed failed during startup. Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39106: Worker process string failed during startup. Worker error: Cause: The worker process whose name is listed failed during startup. Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39107: Master process string violated startup protocol. Master error: Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization. Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39108: Worker process string violated startup protocol. Worker error: Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization. Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39109: Unprivileged users may not operate upon other users" schemas Cause: An unprivileged user attempted to reference another user"s schema during a Data Pump operation. Because of this, no schemas were were selected for the job. Action: Retry the operation under a username owning the schema. ORA-39110: error deleting worker processes Cause: An attempt to delete the worker processes failed. Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39111: Dependent object type string skipped, base object type string already exists Cause: During a Data Pump import job, a dependent object is being skipped because its base object already existed. Action: If the object from the dump file is wanted, drop the base and dependent objects and try to import again using desired filters. ORA-39112: Dependent object type string skipped, base object type string creation failed Cause: During a Data Pump import job, a dependent object is being skipped because its base object creation failed. Action: If the object from the dump file is wanted, drop the base and dependent objects and try to import again using desired filters ORA-39113: Unable to determine database version Cause: The Data Pump was unable to determine the compatibility level and version of the current database using SYS.DBMS_UTILITY.DB_VERSION. Action: Make sure access to the DBMS_UTILITY package is granted to you. If this is a network job, be sure that access to the DBMS_UTILITY package is granted to you on the remote instance. ORA-39114: Dump files are not supported for network jobs. Cause: An attempt was made to add a dumpfile to an Import job that is using a network link to the source database. Action: Do not specify a dumpfile for jobs that do not require dumpfiles. ORA-39115: %s is not supported over a network link Cause: An attempt was made to use an option that is not supported over network links such as the PARTITION_LIST filter. Action: Do not attempt to use Data Pump features on network jobs if they are not compatible with jobs over the network. ORA-39116: invalid trigger operation on mutating table string.string Cause: A Data Pump load operation failed because a trigger attempted to fire on the table while it was mutating. Action: Disable trigger(s) on the specified table. Also see ORA-004091. ORA-39117: Type needed to create table is not included in this operation. Failing sql is: string Cause: A create table was attempted and a dependent type does not exist in the dumpfile or on the target database. Either the export or the import Data Pump job was a table mode job and types are not included in table mode jobs. Action: Determine which type(s) are missing and create them on the target system and run the Data Pump import job again. ORA-39119: worker process interrupt for delete worker processes call by master process Cause: The master process that created this worker process called delete worker processes to abort the current operation. Action: No action is necessary. This is an informational error message. ORA-39120: Table string can"t be truncated, data will be skipped. Failing error is: string Cause: Table data was about to be loaded into a table that already existed and the table_exists_action parameter is truncate, but the table could not be truncated. Action: Determine actual cause by looking at base error. ORA-39121: Table string can"t be replaced, data will be skipped. Failing error is: string Cause: Table data was about to be loaded into a table that already existed and the table_exists_action parameter is replace, but the table could not be dropped. Action: Determine actual cause by looking at base error. ORA-39122: Unprivileged users may not perform string remappings. Cause: A user attempted to remap objects during an import but lacked the IMPORT_FULL_DATABASE privilege. Action: Retry the job from a schema that owns the IMPORT_FULL_DATABASE privilege. ORA-39123: Data Pump transportable tablespace job aborted string Cause: A DBMS_PLUGTS procedure failed and the Data Pump operation could not continue so it was aborted. The DBMS_PLUGTS failure listed describes the original error. Action: Look at the DBMS_PLUGTS error to determine actual cause. ORA-39124: dump file name "string" contains an invalid substitution variable Cause: The substitution variable "%" must be followed by "%","u", or "U". Action: Correct the substitution variable in the dump file name and re-enter the command. ORA-39125: Worker unexpected fatal error in string while calling string [string] Cause: An unhandled exception was detected internally within the worker process for the Data Pump job while calling the specified external routine. This is an internal error. Additional information may be supplied. Action: If problem persists, contact Oracle Customer Support. ORA-39126: Worker unexpected fatal error in string [string] string Cause: An unhandled exception was detected internally within the worker process for the Data Pump job. This is an internal error. Additional information may be supplied. Action: If problem persists, contact Oracle Customer Support. ORA-39127: unexpected error from call to string string Cause: The exception was raised by the function invocation, a procedural action extension of export. Action: Record the accompanying messages and report this as a Data Pump internal error to customer support. ORA-39128: unexpected DbmsJava error number from statement string Cause: The error was returned from a call to a DbmsJava procedure. Action: Record the accompanying messages and report this as a Data Pump internal error to customer support. ORA-39129: Object type string not imported. Name conflicts with the master table Cause: The table being imported from the remote instance has the same name as the master table running this Data Pump job. Action: Rerun the Data Pump job with a nonconflicting name. ORA-39130: Object type string not imported. Base object name conflicts with the master table Cause: The object being imported from the remote instance is dependent on an object that has the same name as the master table running this Data Pump job. Action: Rerun the Data Pump job with a nonconflicting name. ORA-39132: object type "string"."string" already exists with different hashcode Cause: An object type could not be created because there was already a type with the same name but a different hashcode on the target system. Tables in the transportable tablespace set that use this object type cannot be read. Action: Drop the object type from the target system and retry the operation. ORA-39133: object type "string"."string" already exists with different typeid Cause: An object type in a transportable tablespace set already exists on the target system, but with a different typeid. The typeid could not be changed because the type is used by an existing table. Tables in the transportable tablespace set that use this object type cannot be read. Action: Drop the object type from the target system and retry the operation. ORA-39134: Cannot include "string" tablespace as a Transportable Tablespace Cause: The user attempt to specify the SYSAUX or SYSTEM tablespace as a member of the transportable tablespace list in the current job. These tablespaces may not be transported between databases. Action: Specify different tablespaces to be transported. ORA-39136: cannot specify an SCN on a transportable job Cause: A target SCN was specified for a table in a transportable job by the streams or logical standy components which was not the defaulted SCN for the table. Action: This is an internal error. Please report it to Oracle support. ORA-39137: cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata Cause: A job was defined with the TABLE_EXISTS_ACTION parameter set to REPLACE or SKIP, but without metadata. Without metadata, data could not be loaded for the requested table actions. Action: Change the setting of the TABLE_EXISTS_ACTION parameter to APPEND or TRUNCATE or supply Metadata with the data. ORA-39138: Insufficient privileges to load data not in your schema Cause: An unprivileged user attempted to load data into a different schema. Action: Use a privileged account if you must load data not in your schema ORA-39139: Data Pump does not support XMLSchema objects. string will be skipped. Cause: Object has XMLSchema-based columns, which are unsupported by Data Pump. Action: Use the original exp and imp utilities to move this object. ORA-39140: dump file "string" belongs to job string Cause: When a dump file set consists of multiple files, all files in the set must be specified for an import operation, and all files must have been produced by the same export job. One of the files provided does not belong to the original dump file set. For instance, it was created by a different export job than the other files. Action: Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job. ORA-39141: dump file "string" is a duplicate of dump file "string" Cause: When a dump file set consists of multiple files, all files in the set must be specified for an import operation. One of the files provided to import was found to be a duplicate of another dump file in the set. This can occur if the files in the dump set were copied or renamed using operating system utilities and the same dump file was inadvertently copied more than once with different destination names. Action: Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job. ORA-39142: incompatible version number string in dump file "string" Cause: A dump file was specified for an import operation whose version number is incompatible with the dump file version of the Data Pump product currently running on the system. Usually this message indicates that the dump file was produced by a newer version of the Data Pump export utility. Action: Import this dump file using the Data Pump import utility with the same version as the export which created the file. ORA-39143: dump file "string" may be an original export dump file Cause: A dump file was specified for an import operation which appears to have been created using the original export utility. These dump files cannot be processed by the Data Pump import utility. Action: Try using the original import utility to process this dump file. ORA-39144: file name parameter must be specified and non-null Cause: No file name was provided in an DBMS_DATAPUMP.ADD_FILE API call. Action: Correct the file name parameter and reissue the API request. ORA-39145: directory object parameter must be specified and non-null Cause: No directory object was provided in either an DBMS_DATAPUMP.ADD_FILE API call or to the directory parameter used by the Data Pump command line clients. Action: Correct the directory object parameter and retry the operation. ORA-39146: schema "string" does not exist Cause: The specified schema was referenced as the source of a REMAP_SCHEMA parameter, but did not exist in the dump file (for Action: Specify the correct name of the schema to be remapped. ORA-39147: cannot migrate Data Pump queue table ownership to this instance Cause: There are active Data Pump jobs running on another instance in a RAC. All concurrent, active Data Pump jobs must be run on the same instance. Action: Start this job on the same instance where other active Data Pump jobs are running, or wait until they finish. ORA-39148: unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table Cause: A Data Pump import detected that a queue table that was to be imported already exists. Importing data into pre-existing queue tables is not supported. Action: If the data from the dump file is desired, then drop the queue table and perform the import again, or use the import parameter table_exists_action=replace. ORA-39149: cannot link privileged user to non-privileged user Cause: A Data Pump job initiated be a user with EXPORT_FULL_DATABASE/IMPORT_FULL_DATABASE roles specified a network link that did not correspond to a user with equivalent roles on the remote database. Action: Specify a network link that maps users to identically privileged users in the remote database. ORA-39150: bad flashback time Cause: A flashback time was specified for the Data Pump job which either could not be parsed or else could not be translated into a system change number (SCN). This typically occurs when Action: Specify an explicit SCN for the desired flashback rather than a time. ORA-39154: Objects from foreign schemas have been removed from import Cause: An non-privileged user attempted to import objects into a schema other than their own. Action: Either perform the import from a privileged schema or else remap all schemas that were exported into the username running the import. ORA-39155: error expanding dump file name "string" Cause: Export was unable to expand the directory object and dump file name into a full file name. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39156: error parsing dump file name "string" Cause: Export was unable to parse the dump file name. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39157: error appending extension to file "string" Cause: Export or Import was unable to append the default extension to create the file name. The given file name could be too long or contain illegal characters. Subsequent messages will detail the problems. Action: Fix the problems outlined in the secondary messages. ORA-39159: cannot call this function from a non-Data Pump process Cause: Called a Data Pump process model function from a process which is not a Data Pump process. Action: Refer to any other error messages for additional information. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39160: error on whats my name call Cause: Attempt to get the Data Pump process name failed. Action: Refer to any following error messages for additional information. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error. ORA-39161: Full database jobs require privileges Cause: Either an attempt to perform a full database export without the EXP_FULL_DATABASE role or an attempt to perform a full database import over a network link without the IMP_FULL_DATABASE role. Action: Retry the operation in a schema that has the required roles. ORA-39162: Transportable tablespace job require privileges Cause: User attempted to perform a transportable tablespace job without being having the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role. Action: Retry the operation in a schema that has the required roles. ORA-39163: A sample size of string is invalid. Cause: An attempt was made to do data sampling on a table with a value outside of the range of 0 - 100. Action: Retry the filtering using a sampling number greater than 0 and less than 100. ORA-39164: Partition string was not found. Cause: If exporting or importing over the network, the user specified a partition name that was not found in the source database. For importing from files, the user specified a partition name not found in the dump file set. Action: Retry the operation using the correct partition name. ORA-39165: Schema string was not found. Cause: If exporting or importing over the network, either the user specified a schema name that was not found in the source database or else the user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow them to access another schema. For importing from files, the user specified a schema name not found in the dump file set. Action: Retry the operation using the correct schema name. ORA-39166: Object string was not found. Cause: If exporting or importing over the network, either the user specified an object name that was not found in the source database or else the user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow them to access the object another in another schema. For importing from files, the user specified an object name not found in the dump file set. Action: Retry the operation using the correct object name. ORA-39167: Tablespace string was not found. Cause: If exporting or importing over the network, the user specified a tablespace name that was not found in the source database. For importing from files, the user specified a tablespace name not found in the dump file set. Action: Retry the operation using the correct tablespace name. ORA-39168: Object path string was not found. Cause: If exporting or importing over the network, the user specified an object type path name that was not found in the source database. For importing from files, the user specified an object type path name not found in the dump file set. Action: Retry the operation using the correct object type path name. ORA-39169: Local version of string cannot work with remote version of string. Cause: A Data Pump job specified a network link, but the version on the remote database cannot interoperate with the version on the local database. Action: Do not specify network links between instance running different versions of the database. ORA-39170: Schema expression string does not correspond to any schemas. Cause: A schema expression or schema list was supplied for a Data Pump job that did not identify any schemas in the source database. Action: Correct the schema specifications and retry the job. ORA-39171: Job is experiencing a resumable wait. string Cause: The Data Pump job is stalled with one or more of its sessions having a resumable wait. Resumable waits are typically caused by a non-expandable tablespace running out of space. The follow-on message describes the nature of the wait. Action: Correct the condition causing the wait. This will typically involve adding datafiles to the tablespace that is full. ORA-39172: Cannot remap transportable tablespace names with compatibility of string. Cause: The user attempted to remap a tablespace name in a transportable tablespace job when the compatibility level was set below 10.1. Action: Reset the compatibility level of the database to a more recent version. ORA-39173: Encrypted data has been stored unencrypted in dump file set. Cause: No encryption password was specified for an export job that involved data that was encrypted in the database. Action: No specific user action is required. This is only a warning that secure data may be readable from within the dump file set. ORA-39174: Encryption password must be supplied. Cause: No encryption password was supplied to import a dump file set that was created using an encryption password. Action: Specify the encryption password for the dump file set. ORA-39175: Encryption password is not needed. Cause: An encryption password was supplied to import a dump file set that was not created using an encryption password. Action: No user action is required. This is merely a warning message. ORA-39176: Encryption password is incorrect. Cause: The wrong encryption password was supplied to import a dump file set. Action: Resubmit the job using the correct encryption password for the dump file set. ORA-39177: invalid compression value string Cause: An invalid value was specified for compression. Action: Correct the value and recreate the job. ORA-39178: cannot perform estimate on metadata only jobs Cause: An estimate was requested for a job by specifying the ESTIMATE or ESTIMATE_ONLY parameter. However, the job was also defined to have no data. These specifications conflict with each other. Action: Remove one of the conflicting specifications for the job. ORA-39179: unable to load table "string"."string" because of OID transform Cause: The OID transform for the job was set to false and the identified table contained either VARRAYs with non-final types or unscoped REF columns. Both of these column types have embedded OIDs so they Action: You must manually move the data with the specified tables when OIDs are not preserved. ORA-39180: unable to encrypt ENCRYPTION_PASSWORD Cause: The specified encryption password was unable to be encrypted for placement within the master table or decrypted when it was to be restored from the master table. Subsequent messages will describe the actual error that caused the encryption to fail. Action: Fix the problems referenced by the subsequent messages. The most common reason for the encryption to fail is the lack of a security wallet. ORA-39181: Only partial table data may be exported due to fine grain access control on string Cause: An unprivileged user has tried to export a table that has fine grain access control. The table owner is subjected to access control and may not be able to export all rows in the table. Only the rows that can be seen by that user will be exported. In order to preserve integrity of the table, the user importing the table should have enough privilege to recreate the table with the security policies at import time. Action: It is strongly recommended that the database administrator handle exporting of this table. ORA-39200: Link name "string" is invalid. Cause: The name of the network link supplied for a Data Pump job was not usable. Secondary messages identify the problem. Action: Rerun the job using a valid network link. ORA-39201: Dump files are not supported for estimate only jobs. Cause: An attempt was made to add a dumpfile to an Export job that only requested file estimates. Action: Do not specify a dumpfile for jobs that do not require dumpfiles. ORA-39202: Data cannot be filtered or selected in string jobs. Cause: A data filter was supplied for the specified type of job, but is not supported in the specified job type. From the command line, data filters can be specified by the CONTENT, TABLES (partition specifications), SAMPLE and QUERY parameters. Action: Do not restrict data handling on jobs that cannot support data filtering. ORA-39203: Partition selection is not supported over a network link. Cause: Specific partitions were selected for a job operating over a network link. Action: Remove the partition specifications and rerun the job. ORA-39204: No subsetting of tablespaces is allowed for transportable import. Cause: A tablespace filter was applied to a transportable import job that was not performed over a network link. In this case, the tablespace may not be changed from its specification at export time. Action: Rerun the job without specifying a tablespace filter. ORA-39205: Transforms are not supported in transportable jobs. Cause: A metadata transformation such as STORAGE or SEGMENT_ATTRIBUTES has been specified for a transportable Data Pump job. Action: Rerun the job without specifying a transform. ORA-39206: A parallel degree of string is invalid. Cause: A bad numeric was supplied for specifying the parallelism to be used within a Data Pump job. The degree of parallelism must be an integer great than 0. Action: The the degree specifying and retry the parallelism setting. ORA-39207: Value string is invalid for parameter string. Cause: A parameter for a Data Pump job was set with a NULL or invalid value. Action: Refer to the documentation to identify the legal values for each parameter. Retry the operation with a valid value. ORA-39208: Parameter string is invalid for string jobs. Cause: The a parameter has been specified that is not supported for the specified type of Data Pump. Action: Remove the parameter specification and retry the operation. ORA-39209: Parameter string requires privileges. Cause: Use of the specified privileges requires the user to have the IMP_FULL_DATABASE role for import jobs or the EXP_FULL_DATABASE role for export jobs. Action: Remove the parameter specification and retry the operation. ORA-39210: A PCTSPACE adjustment of string is invalid. Cause: User specified a storage space transformation that was out of range. Values for PCTSPACE must be greater than zero. Action: Retry the operation with a valid PCTSPACE value. ORA-39211: unable to retrieve dumpfile information as specified Cause: User specified an invalid or inaccessible file with the specified filename and directory object. Action: Retry the operation with a valid directory object and filename. ORA-39212: installation error: XSL stylesheets not loaded correctly Cause: The XSL stylesheets used by the Data Pump Metadata API were not loaded correctly into the Oracle dictionary table "sys.metastylesheet." Either the stylesheets were not loaded at all, or they were not converted to the database character set. Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets to reload the stylesheets. ORA-39213: Metadata processing is not available Cause: The Data Pump could not use the Metadata API. Typically, this is caused by the XSL stylesheets not being set up properly. Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets to reload the stylesheets. ORA-39214: Data Pump does not support external tables with encrypted columns. string will not be exported Cause: The object is an external table with encrypted columns and this is unsupported with Data Pump. Action: External table must be manually recreated on the target system. ORA-39216: object type "string"."string" hashcode mismatch Cause: An object type in a transportable tablespace set could not be used because there was a type with the same name but a different hashcode (and type definition) on the target system. Tables in the transportable tablespace set that use this object type cannot be created. Action: Drop the object type and dependent objects from the target system if possible and retry the operation. ORA-39217: object type "string"."string" typeid mismatch Cause: An object type in a transportable tablespace set already exists on the target system, but with a different typeid. The typeid could not be changed because the type or a dependent type is used by an existing table. Tables in the transportable tablespace set that use this object be created. Action: Drop the object type and dependent objects from the target system if possible and retry the operation. ORA-39218: type check on object type "string"."string" failed Cause: The type check on a type failed. Therefore, the table create for the table which uses the type also fails. Action: Refer to any following error messages for additional information. Correct the error, if possible, and try the action again. ORA-39219: directory object name is too long Cause: The directory object name provided to the Data Pump Job was invalid because its length was greater than 30 characters. Action: Retry the operation with a valid directory object name. ORA-39220: file name is too long Cause: The file name provided to the Data Pump Job was invalid because its length was greater than 4000 characters. Action: Retry the operation with a valid file name. ORA-39301: schema "string" does not exist or is in use Cause: The specified schema did not exist, or application upgrade was still in progress in the schema. Action: Retry the operation with an alternate schema or stop the application upgrade and retry. ORA-39302: schema clone operation failed Cause: The schema clone operation could not reach a consistent state after a few iterations. The error occurred because the source schema was changing rapidly. Action: Restart clone from scratch. ORA-39303: schema sync or swap operation failed because of confilcts Cause: There were conflicting changes to objects in source and target schema. This error occurred because some objects were changed in both source and target schemas. Action: Restart the schema clone operation from scratch. ORA-39304: conflicting changes to object "string" : string Cause: The schema sync or swap operation found conflicting changes to the specified object. This error occurred because the specified object was changed in both source and target schemas. Action: Retry the schema sync, swap, or validation_check operation with the "ignore_conflict" or "force_sync" parameters set to TRUE, or restart the schema clone operation from scratch. ORA-39305: schema "string" does not exist Cause: The specified schema did not exist. Action: Verify the schema name and correct it. ORA-39306: schema name mismatch expected "string" got "string" Cause: The schema name specified did not match the schema name specified in the initial clone operation. Action: Specify the correct schema, or restart the schema clone operation from scratch. ORA-39307: operation is illegal without an initial clone Cause: The error occurred because a sync, swap, validation_check, or clean_up operation was attempted without an initial clone operation. Action: Retry the operation after a clone operation. ORA-39308: application or database upgrade internal error: "string" Cause: An unexpected error occurred during application or database upgrade. Action: Check any errors that follow for a possible cause. Retry the operation after fixing reported issues. If the error persists, contact Oracle Customer Support. ORA-39309: schema sync operation failed Cause: The schema sync operation could not reach a consistent state after a few iterations. The error occurred because the source schema was changing rapidly. Action: Retry the schema sync operation. ORA-39310: call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal Cause: The routine DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE was called out of sequence. This error occurred because the prior operation was not a schema clone operation or the prior schema clone operation was successful. Action: Call this routine only if a schema clone operation failed. If you want to clean up the target schema, call the CLEAN_TARGET routine instead. ORA-39311: call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal Cause: The routine DBMS_SCHEMA_COPY.CLONE_RECOVERY was called out of sequence. This error occurred because the prior operation was not a schema clone operation or the prior schema clone operation was successful. Action: Call this routine only if a schema clone operation failed. If you want to clean up the target schema, call the CLEAN_TARGET routine instead. ORA-39312: call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal Cause: The routine DBMS_SCHEMA_COPY.CLEAN_TARGET was called out of sequence. The error occurred because the prior clone operation failed. Action: Call the CLEAN_FAILED_CLONE or CLONE_RECOVERY to clean up or recover from the failed clone operation. ORA-39313: call to DBMS_SCHEMA_COPY.CLONE is not legal Cause: The routine DBMS_SCHEMA_COPY.CLONE was called out of sequence. This error occurred because clone operation was done before. Action: Call the routine in the correct sequence. To redo the clone operation, first call the routine DBMS_SCHEMA_COPY.CLEAN_UP. ORA-39314: call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal Cause: The routine DBMS_SCHEMA_COPY.SYNC_CODE was called out of sequence. The error occurred because the prior operation was not a schema clone or sync operation. Action: Call the routine in the correct sequence. ORA-39315: call to DBMS_SCHEMA_COPY.SWAP is not legal Cause: The routine DBMS_SCHEMA_COPY.SWAP was called out of sequence. The error occurred because the prior operation was not a schema clone or sync operation. Action: Call the routine in the correct sequence or call it with the "force_swap" parameter set to TRUE. ORA-39316: call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal Cause: The routine DBMS_SCHEMA_COPY.CLEAN_UP was called out of sequence. The error occurred because the prior schema clone operation failed. Action: Call the CLEAN_FAILED_CLONE or CLONE_RECOVERY to clean up or recover from the failed clone operation. ORA-39317: call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal Cause: The routine DBMS_SCHEMA_COPY.VALIDATION_CHECK was called out of sequence. The error occurred because the prior operation was not one of schema clone, sync, or valdation_check. Action: Call the routine in the correct sequence. ORA-39500: failed to notify CRS of a Startup/Shutdown event for database "string", instance "string" (ignored) Cause: The instance was unable to obtain the context or information required to notify the CRS framework. Action: None Required. The error is ignored. ORA-39501: failed to notify CRS of a Startup/Shutdown event [string] (ignored) Cause: The instance was unable to communicate with the CRS framework. Action: None Required. The error is ignored. ORA-39502: failed to notify CRS of a Startup/Shutdown event [string] (ignored) Cause: The instance was unable to create an environment context. Action: None Required. The error is ignored. ORA-39503: failed to notify CRS of a Startup/Shutdown event [string] (ignored) Cause: The instance was unable to populate the environment context. Action: None Required. The error is ignored. ORA-39504: failed to notify CRS of a Startup/Shutdown event [string] (ignored) Cause: The instance was unable to find the location of the alert file. Action: None Required. The error is ignored. ORA-39600: Queue keys needs to be a suffix of cluster key. Cause: Attempt to specify queue key columns that don"t form a suffix of the cluster key. Action: Only specify queue key columns as a suffix of cluster key. ORA-39601: Hash key is required. Cause: Missing hash key in the cluster key specification. Action: Specify one or more hash key columns. ORA-39700: database must be opened with UPGRADE option Cause: A normal database open was attempted, but the database has not been upgraded to the current server version. Action: Use the UPGRADE option when opening the database to run catupgrd.sql (for database upgrade), or to run catalog.sql and catproc.sql (after initial database creation). ORA-39701: database must be mounted EXCLUSIVE for UPGRADE or DOWNGRADE Cause: The database was mounted for SHARED cluster access. Action: Set the CLUSTER_DATABASE initialization parameter to FALSE and restart the server with the UPGRADE or DOWNGRADE option. ORA-39702: database not open for UPGRADE or DOWNGRADE Cause: An upgrade, downgrade, reload, or patch script was invoked when the database was not open for UPGRADE or DOWNGRADE. Action: Use STARTUP UPGRADE to open the database for upgrade or to apply a patch set. Use STARTUP DOWNGRADE for running a downgrade script or the reload script. ORA-39703: server version and script version do not match Cause: An upgrade, downgrade, reload, or patch script was invoked, but the database instance version was not the version for which the script was intended. Action: Check that the correct ORACLE_HOME and ORACLE_SID environment variables are set. Also check that the SQL script is being invoked from the correct ORACLE_HOME. ORA-39704: permission to modify component registry entry denied Cause: An attempt was made to modify an entry in the component registry, but the session user was not authorized; only the CONTROL or SCHEMA user for the component are authorized to modify the component registry entry. Action: Connect as either the CONTROL or SCHEMA user for the component. ORA-39705: component "string" not found in registry Cause: No entry in the component registry was found for the specfied component. Action: Check the spelling of the component ID and use the DBA_REGISTRY view to list the existing components. ORA-39706: schema "string" not found Cause: The schema name specified was not found in the database. Action: Create the schema before loading the component. ORA-39707: compatibile parameter string too high for downgrade to string Cause: A downgrade was attempted, but the compatible initialization parameter value was greater than the downgrade release version. Action: Once the compatible value has been raised, downgrade to earlier releases is not supported. ORA-39708: component "string" not a string component Cause: The component was not a component for the specified namespace. Action: Either enter a valid component identifier for the namespace or set the session namespace to the correct component namespace. ORA-39709: incomplete component downgrade; string downgrade aborted Cause: One or more components did not have a status of DOWNGRADED. Action: Correct the component problem and re-run the downgrade script. ORA-39710: only connect AS SYSDBA is allowed when OPEN in UPGRADE mode Cause: An attempt was made to connect to a database when the database was OPEN for UPGRADE or DOWNGRADE. Action: Try to connect again after the database upgrade or downgrade is complete. ORA-39711: critical patch number less than last installed CPU number Cause: A Critical Patch Update (CPU) script was invoked that had a number that was less than the last CPU installed in the database. Action: Check the DBA_REGISTRY_HISTORY view to identify the last CPU for the database, and install the most recent CPU. ORA-39726: unsupported add/drop column operation on compressed tables Cause: An unsupported add/drop column operation for compressed table was attemped. Action: When adding a column, do not specify a default value. DROP column is only supported in the form of SET UNUSED column (meta-data drop column). ORA-39727: COMPATIBLE must be set to 10.0.0.0.0 or higher Cause: An add/drop column operation for compressed table has been performed on the database. This requires COMPATIBLE to be set to 10.0.0.0.0 or higher during upgrade from 9.2 to a 10i or higher release. Action: Set COMPATIBLE to 10.0.0.0.0 and retry the upgrade. ORA-39751: partitioned table on both sides of PARTITIONED OUTER JOIN is not supported Cause: An attempt was made to partition both sides of PARTITIONED OUTER JOIN. Action: Specify partitioned table on one side of PARTITIONED OUTER JOIN only. ORA-39752: redundant column in partitioning and join columns is not allowed Cause: An attempt was made to specify redundant columns in partitioning and join columns for NATURAL or named column PARTITIONED OUTER JOIN. Action: Do not specify redundant column in partitioning and join columns. ORA-39753: unsupported use of subquery in PARTITIONED OUTER JOIN condition Cause: An attempt was made to use subquery in PARTITIONED OUTER JOIN condition. Action: Remove subquery from the join condition. ORA-39754: FULL PARTITIONED OUTER JOIN is not supported Cause: An attempt was made to use FULL PARTITIONED OUTER JOIN. Action: Specify FULL PARTITIONED OUTER JOIN through UNION of LEFT and RIGHT PARITTION OUTER JOIN. ORA-39761: stream reset required before loading this stream again Cause: An attempt was made to load a stream that was previously loaded but has not been reset yet. Action: Reset the specified stream and convert column array data to it before attempting to load it again. ORA-39762: streams must be loaded in conversion order Cause: An attempt was made to load a stream out of conversion order. Action: Load streams in the same order they were converted. ORA-39763: stream must be completely loaded before it is reset Cause: An attempt was made to reset a stream that contains converted column array data and hasn"t been completely loaded yet. Action: Before resetting a stream, load it until a status of OCI_SUCCESS, OCI_NO_DATA, or OCI_NEED_DATA is returned. ORA-39764: specified stream is not in the specified direct path context Cause: A direct path operation was attempted using a stream that was not created in the specfied direct path context. Action: Only use streams created in the specified direct path context. ORA-39765: stream must be reset before used in a column array conversion Cause: The stream was completely loaded, but has not been reset yet. Action: Reset loaded streams after load returns OCI_SUCCESS, OCI_NO_DATA, or OCI_NEED_DATA. The stream can then be used in a column array to stream conversion. ORA-39766: invaid stream specified for column array conversion Cause: A stream must be loaded and reset before used again in a column-array-to-stream conversion. This error is issued if another stream has subsequently been converted before the specified stream has been loaded, or if the latest load of this stream returned OCI_ERROR. Action: Don"t convert into a previous stream before it is loaded. Also, when load stream returns OCI_ERROR, the stream must be loaded again to insure any remaining information in the stream is loaded. The stream must be loaded even if the last or only row was in error. There may be error information in the stream that needs to be sent to the server. ORA-39767: finish is not allowed when unloaded stream data exists Cause: A direct path finish was attempted when at least one stream buffer has not been completely loaded. Action: All streams must be loaded after a column array to stream conversion until load stream returns a status of OCI_SUCCESS or OCI_NO_DATA. The load can then be finished. ORA-39768: only one direct path context top level column array is allowed Cause: Attempt to create multiple top level column arrays in a direct path context, when only one is allowed. Action: Create another direct path context if additional top level column arrays are required. ORA-39769: finish is not allowed with an incompletely loaded last row Cause: Part of a row has been loaded, but it is not complete. Action: Finish loading the current row when load stream returns OCI_ERROR or OCI_NEED_DATA. ORA-39771: stream must be loaded before its handle is freed Cause: An attempt was made to free a stream handle after conversion but before the stream was loaded. Action: Load the stream until OCI_SUCCESS, OCI_NEED_DATA or OCI_NO_DATA is returned before attempting to free the stream handle. If OCI_NEED_DATA is returned, another stream must be loaded to complete last row. ORA-39772: column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA Cause: An attempt was made to reset a column array when a row conversion is still in progress. Action: Complete the current row before reseting the column array. To ignore the current row when conversion returned OCI_NEED_DATA, set the current column flag to OCI_DIRPATH_COL_ERROR. This should be followed by a conversion, which will undo and ignore the row. The column array(s) can then be reset. ORA-39773: parse of metadata stream failed Cause: An unexpected error occured while attempting to parse the metadata // stream for a table being loaded. Action: Call Oracle support. ORA-39774: parse of metadata stream failed with the following error: string Cause: An unexpected error occured while parsing the metadata stream. Action: See the secondary error for more information. ORA-39775: direct path API commit not allowed due to previous fatal error Cause: An attempt was made to commit a Direct Path context after a fatal error. Action: Correct the error and retry. ORA-39776: fatal Direct Path API error loading table string Cause: A fatal error was detected loading the specified or previous table. Action: Correct the error and retry. ORA-39777: data saves are not allowed when loading lob columns Cause: An attempt was made to save data when loading lob columns or columns stored as lobs (such as varrays and xml types). Action: Do not attempt to do a data save or partial save when loading lob columns. A finish save is allowed. ORA-39778: the parallel load option is not allowed when loading lob columns Cause: An attempt was made to load lob columns using the attribute OCI_ATTR_DIRPATH_PARALLEL. This error will also be issued when loading any columns that are stored as lobs (such as varrays and xml types). Action: Do not use the parallel attribute when loading lob columns. ORA-39779: type "string"."string" not found or conversion to latest version is not possible Cause: Unable to import table data using the specified type. The type was nonexistent in the database or the input type could not be converted to the existing type. The reasons why a conversion was not possible are: 1. The version of the type in the database was greater than the version of the type at export time because 1 or more attributes have been added or dropped from the type. 2. If the type existed in the database prior to the import operation, then its internal identifier may not match the internal identifier of the type from the export database. The identifiers must match for an import to succeed. Action: Ensure the types in the database match those at export time. ORA-39780: Direct path context operations are not allowed after the context is aborted or finished Cause: The specified direct path context was aborted or finished. Action: Do not pass a direct path context that has ended to any direct path functions. ORA-39781: Direct path stream loads are not allowed after another context loading the same table has ended Cause: Attempt to load a stream in one context after another loading the same table has ended. Action: Close all contexts before trying to create another that loads the same table as a previous context in the same session. ORA-39782: Direct path prepare is not allowed after another context loading the same table has ended Cause: Direct path prepare called after a context loading the same table has ended. Action: Close all contexts before trying to create another that loads the same table as a previous context in the same session. ORA-39783: Invalid direct path transaction active Cause: Direct path operations were not performed in the transaction started by the first OCIDirPathPrepare call. Action: Ensure the correct transaction is active prior to calling Direct Path API operations. ORA-39784: This direct path operation is not allowed while another is in progress Cause: Another direct path operation was active. Action: Complete any direct path operations in progress before attempting this operation. ORA-39785: SQL expressions returning ADT objects are not allowed in direct path Cause: The passed SQL expression returned a user-defined ADT which was not supported. Action: Remove the SQL expression. ORA-39950: invalid parameter for PLSQL warnings flag Cause: The user either entered invalid value for the PLSQL_WARNINGS flag or the value of the flag conflicts with other values. Action: Enter correct values for the switch. ORA-39951: incomplete values specified for PL/SQL warning settings Cause: The user either did not enter the value for the settings or entered incomplete values. Action: Enter correct syntax for the switch. ORA-39952: only numbers can be specified as range values Cause: The range values did not have numerical values only. Action: Enter only numerical values. ORA-39953: the range value specified is beyond allowed range Cause: The range values were either too low or too high. Action: Specify only the allowed range values. ORA-39954: DEFERRED is required for this system parameter Cause: The ALTER SYSTEM command for PLSQL_WARNINGS did not include the keyword, DEFERRED. Action: Change the command to use the keyword, DEFERRED. ORA-39955: invalid PL/SQL warning message number Cause: The PL/SQL message number specified was not in a valid range. Action: Specify PL/SQL warning message numbers within the valid range. ORA-39956: duplicate setting for PL/SQL compiler parameter string Cause: A PL/SQL compiler parameter was set more than once. Action: Remove the duplicate PL/SQL compiler setting. ORA-39957: invalid warning category Cause: The category of the message was incorrect. Action: Specify a vaild category ORA-39958: invalid warning category qualifier Cause: The category qualifier was incorrect. Action: Specify a vaild category qualifier. ORA-39959: invalid warning number (string) Cause: The warning number was incorrect. Action: Specify a vaild warning number. ORA-39960: scope can only be SYSTEM or SESSION Cause: The scope specified was not set. Action: Specify a vaild scope, either SESSION or SYSTEM. ORA-39961: message specified was not found Cause: The message number specified was not set. Action: specify the message number whise settings have been set in the given scope. ORA-39962: invalid parameter for PLSQL_CCFLAGS Cause: The value for the PLSQL_CCFLAGS parameter was not valid. Action: Specify a vaild value for the PLSQL_CCFLAGS parameter. /// MAX ERROR NUMBER 65535 /// EOF - Add errors till 40000 ABOVE this line. REGISTER at errorinf.txt 20 ORA-40001 to ORA-40322 ORA-40001: value for string must be greater than zero Cause: The input parameter in question has a value of zero or less. Action: Provide a value greater than zero for the relevant parameter. ORA-40002: wordsize must be string or greater Cause: The input wordsize is less than the prescribed limit for the BLAST Match or Align algorithm. Action: Provide a wordsize greater than or equal to the prescribed value. ORA-40003: wordsize must be in the range string - string for BLAST-P Cause: The input wordsize has a value out of the prescribed range. Action: Provide a wordsize value within the prescribed range for BLAST-P. ORA-40004: penalty must be negative for BLAST-N Cause: The input value provided for penalty is zero or greater. Action: Provide a negative penalty value. ORA-40101: Data Mining System Error string-string-string Cause: An internal system error occured during a data mining operation. Action: Contact Oracle Support Services. ORA-40102: invalid input string for data mining operation string Cause: The input parameter is either null or invalid for the given operation. Action: Provide a valid value. Check range for NUMBER parameters. ORA-40103: invalid case-id column: string Cause: The column designated as case-id is not of one of CHAR, VARCHAR2, NUMBER data type. Case-id columns of type CHAR and VARCHAR2 must be of length less than or equal to 128 bytes. Action: Change the schema of your input data to supply a case-id column of appropriate data type and/or length. ORA-40104: invalid training data for model build Cause: The training data provided in the reported table is unsuitable for build, either because it is empty, has unsuitable data, or the schema of the table does not match the input specifications. Action: Inspect the training data and correct the contents/schema as appropriate. ORA-40105: input data incompatible with model signature Cause: The data provided for this post-build operation is in format different from that used for model build. Action: Provide data whose attribute data types match the build data. Input data attributes must have the same data types as those described in the model signature for the model. ORA-40106: positive target value not specified for computing Lift Cause: Positive target value has not been specified for Lift. Action: Provide a positive target value for the Lift operation. ORA-40107: operation requires string option to be installed Cause: The specified option has not been installed with the RDBMS. Action: Install the reported option and retry the operation. ORA-40108: input data contains too few distinct target (string) values Cause: At least two distinct target values are required for Build. Action: Provide counter-example target values in the input data. ORA-40109: inconsistent logical data record Cause: Repeated instances of a record identifier or repeated attribute(s) in a nested column. Action: Remove or re-label repeated instances to resolve inconsistencies. ORA-40201: invalid input parameter string Cause: The input parameter was either null or invalid. Action: Provide a valid value for the input parameter. ORA-40202: column string does not exist in the input table string Cause: The column was missing from the table. Action: Correct the table schema and/or provide the correct column name. ORA-40203: model string does not exist Cause: The model did not exist. Action: Supply a valid model name. ORA-40204: model string already exists Cause: A model by the same name exists. Action: Provide a different, unique name for the model. ORA-40205: invalid setting name string Cause: The input setting name was invalid. Action: Consult the documentation for the settings table and provide a valid setting name. ORA-40206: invalid setting value for setting name string Cause: The input value for the given setting name was invalid. Action: Consult the documentation for the settings table and provide a valid setting value. ORA-40207: duplicate or multiple function settings Cause: The input settings table contained settings for multiple mining functions. Action: Provide setting(s) for a single function in the settings table. ORA-40208: duplicate or multiple algorithm settings for function string Cause: The input settings table had duplicate or multiple algorithm settings for a mining function. Action: Provide only one appropriate algorithm setting for the mining function. ORA-40209: setting % is invalid for % function Cause: The specified setting was not supported for the mining function supplied. Action: Provide appropriate combination of function and algorithm settings. ORA-40211: algorithm name string is invalid Cause: Algorithm name for the model was invalid or the operation was not valid for the algorithm. Action: Check the algorithm name for the model and verify that the operation is valid. ORA-40212: invalid target data type in input data for string function Cause: Target data type was invalid. Action: Classification function accepts CHAR,VARCHAR2, and NUMBER targets. Regression function accepts NUMBER targets only. ORA-40213: contradictory values for settings: string, string Cause: The settings values were not compatible. Action: Check the documentation and change the setting value(s). ORA-40214: duplicate setting: string Cause: Duplicate setting in the settings table. Action: Remove the duplicate setting from the settings table. ORA-40215: model string is incompatible with current operation Cause: The current operation was not supported for the mining function the model corresponds to. Action: Provide the model name suitable for current operation. ORA-40216: feature not supported Cause: The feature was not supported in the API. Action: Modify the code to avoid usage of the feature. ORA-40217: priors table mismatched with training data Cause: The entries in the priors table do not correspond to the targets in the training data. Action: Verify the entries in the priors table. ORA-40219: apply result table string is incompatible with current operation Cause: The current operation was not allowed for the apply result table supplied. Action: Make sure the operation being performed is valid for the mining function used to build the model (using which the apply result table was created). ORA-40220: maximum number of attributes exceeded Cause: The data had too many attributes. Action: Reduce the dimensionality of the data. ORA-40221: maximum target cardinality exceeded Cause: The target cardinality of the training data was too high. Action: Reduce the target cardinality. ORA-40222: data mining model export failed, job name=string, error=string Cause: The model export job failed. Action: Check export job settings as required by DataPump. ORA-40223: data mining model import failed, job name=string, error=string Cause: The model import job failed. Action: Check import job settings as required by DataPump. ORA-40225: model is currently in use by another process Cause: The model is currently in use by another process. Action: Retry if necessary. ORA-40226: model upgrade/downgrade must be performed by SYS Cause: Upgrade/Downgrade routines are being invoked by a user with insufficient privilieges. Action: Run the routines as SYS during migration. ORA-40251: no support vectors were found Cause: The input data is non-predictive in nature, or one of the input settings is incorrect/incompatible with respect to the input data. Action: Provide additional data or change model setting value. ORA-40252: no target values were found Cause: No target values were identified during load. Action: Validate that the target is correctly specified. ORA-40253: no target counter examples were found Cause: One or more of the target classes have only positive examples. Action: Provide counter examples or remove that target class. ORA-40254: priors cannot be specified for one-class models Cause: Priors were specified. Action: Do NOT provide priors for one-class models. ORA-40261: input data for model build contains negative values Cause: The input data contains negative values, which is not acceptable for a Non-negative Matrix Factorization model. Action: Provide clean data for build without any negative values. ORA-40262: NMF: number of features not between [1, string] Cause: The number of requested features must be greater than 1, and less than the smaller of the number of attributes and the number of cases in the dataset. Action: Specify the desired number of features within the acceptable range. ORA-40271: no statistically significant features were found Cause: Input data inadequate in volume and/or quality to derive statistically significant predictions for building a Adaptive Bayes Network model. Action: Provide a well-prepared training data set. ORA-40272: apply rules prohibited for this model mode Cause: Adaptive Bayes Network rules are only generated for SingleFeature ABN models Action: Rebuild model in SingleFeature mode and then apply with rules. ORA-40273: invalid model type string for Adaptive Bayes Network algorithm Cause: The valid values for the abns_model_type settings are: abns_multi_feature, abns_single_feature, abns_naive_bayes. Action: Use a valid value for the abns_model_type setting. ORA-40281: invalid model name Cause: A model name is invalid or does not exist. Action: Check spelling. A valid model name must begin with a letter and may contain only alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word. ORA-40282: invalid cost matrix Cause: Cost matrix specification is invalid. Action: Provide valid cost matrix specification. Check syntax for data mining functions. ORA-40283: missing cost matrix Cause: Cost matrix specification is missing. Action: Provide valid cost matrix specification. Check syntax for data mining functions. ORA-40284: model does not exist Cause: The model entered does not exist. Action: Check spelling. ORA-40285: label not in the model Cause: The model does not have the label. Action: Provide valid label. ORA-40286: remote operations not permitted on mining models Cause: An attempt was made to perform queries or DML operations on remote tables using local mining models. Action: Remove the reference to remote tables in the statement. ORA-40287: invalid data for model - cosine distance out of bounds Cause: The norm computed using attribute values from the incoming row for the cosine model is outside the range 0-1. Action: Remove or correct the data in the offending row. ORA-40289: duplicate attributes provided for data mining function Cause: A duplicate, non-nested attribute was provided as input to the data mining function. A duplicate attribute is one which is present in the model signature, occurs more than once in the USING clause after tablename expansion, and is not a collection element in a nested table column. Action: Eliminate the duplicate attribute(s). ORA-40290: model incompatible with data mining function Cause: The supplied model cannot be operated upon by the data mining function because the model is built for a mining function and/ or based on an algorithm that is incompatible with function. Action: Provide the name of the model suitable for the function. ORA-40291: model cost not available Cause: The supplied model was assumed to have been built with a cost matrix specification, when in reality, it was not. Action: Provide a model name that corresponds to a model that was built with an appropriate cost matrix specification. ORA-40301: invalid cost matrix specification Cause: A valid cost matrix is not specified. Action: Consult documentation for valid cost matrix specification. ORA-40302: invalid classname string in cost matrix specification Cause: Actual or predicted classname specified is not present in training data Action: Provide valid classname(s) in cost matrix specification ORA-40303: invalid prior probability specification Cause: Valid prior probabilities not specified. Valid probabilities should be between 0 and 1. Action: Consult documentation for valid prior probability specification. ORA-40304: invalid classname string in prior probability specification Cause: Actual or predicted classname specified is not present in training data. Action: Provide valid classname(s) in prior probability specification. ORA-40305: invalid impurity metric specified Cause: Impurity metric specified is not valid. Examples of valid metrics are TREE_IMPURITY_GINI, TREE_IMPURITY_ENTROPY. Action: Consult documentation for valid impurity metrics and specification. ORA-40306: wide data not supported for decision tree model create Cause: Wide data (DM_NESTED_NUMERICALS and/or DM_NESTED_CATEGORICALES) is being passed to the decision tree model create routine. These datatypes are currently not supported for tree builds. Action: Remove columns of these datatypes from the input. ORA-40321: invalid bin number, is zero or negative value Cause: Input bin number has zero or negative values. Action: Provide positive bin numbers starting from 1. ORA-40322: bin number too large Cause: Bin number is too large. Action: Reprocess build data by choosing smaller bin numbers. #################################################################################################### SECTION 4: Some important recent ORA- messages: #################################################################################################### ----- Note: ----- ORA-600 ORA-00600 [KFDOFFLINE01] Subject: Ora-00600: [Kfdoffline01], [3] ERROR WHEN ONE OF THE FAILGROUPS IS OFFLINED Doc ID: 745450.1 Type: PROBLEM Modified Date : 11-DEC-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.7 This problem can occur on any platform. Symptoms When one of the LUNs of a failure group was removed, ORA-600 [KFDOFFLINE01] can be received while offlining ASM disk. The behaviour is described in Bug 7311909 which happens when ASM instance is using 11g and database instance is using 10g versions. ### STEPS TO REPRODUCE ### - Be on 11g ASM and 10g DB. - 11g ASM diskgroup(normal redundancy with two failgroups) (compatible.rdbms'='10.1.0.0.0', compatible.asm'='11.1.0.0.0') - Remove one of the active luns in diskgroup - ORA-600 [kfdOffline01], [3] is received in ASM instance There is an important impact of getting ORA-600 kfdoffline01. Although error is reported in the ASM instance, database instance can also fail to start with I/O errors followed by ORA-600 errors: The following errors can happen either during database instance recovery or when reading/writing database controlfile - ORA-00600: internal error code, arguments: [kfioReapIO00], [0], [60], [], [], [], [], [] - ORA-00206: error in writing (block 1, # blocks 1) of control file ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], [] WARNING!!! kfkUfsCancel not implemented!!!! Changes During startup when database instance needs to perform an I/O, database can't find the disk and triggers an offline operation. alert_DB.log Wed Nov 26 09:27:03 2008 WARNING: offlining disk 3.3916111426 (_DROPPED_0003_RDPLCR04) with mask 0x3 Wed Nov 26 09:27:03 2008 WARNING: offlining disk 3.3916111426 (_DROPPED_0003_RDPLCR04) with mask 0x3 Wed Nov 26 09:27:04 2008 Errors in file /opt/app/oracle/admin/PLCR04/bdump/plcr04_ora_28197.trc: ORA-00600: internal error code, arguments: [kfioReapIO00], [0], [60], [], [], [], [], [] Disk offline operation fails with ORA-600[kfdOffline01][3] in ASM instance due to 11g disk mode is not compatible with 10g compatible mode. alert_+ASM.log Wed Nov 26 09:27:04 2008 Errors in file /opt/app/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_28116.trc (incident=31721): ORA-00600: internal error code, arguments: [kfdOffline01], [3], [], [], [], [], [], [] Wed Nov 26 09:27:04 2008 Errors in file /opt/app/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_28209.trc (incident=31729): ORA-00600: internal error code, arguments: [kfdOffline01], [3], [], [], [], [], [], [] Wed Nov 26 09:27:04 2008 Errors in file /opt/app/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_28221.trc (incident=31745): Database instance startup fails with errors as a result: Errors in file /opt/app/oracle/admin/PLCR04/bdump/plcr04_ora_28195.trc: ORA-00600: internal error code, arguments: [kfioReapIO00], [0], [60], [], [], [], [], [] Wed Nov 26 09:28:25 2008 Shutting down instance (abort) The same failure can also happen when database startup needs to write controlfile. alert_DB.log *** 2008-11-24 10:09:42.054 WARNING: offlining disk 1.3915949147 (_DROPPED_0001_WEB0) with mask 0x3 ORA-00206: error in writing (block 1, # blocks 1) of control file ORA-00202: control file: '+WEB0/wdb/control02.ctl' ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], [] WARNING!!! kfkUfsCancel not implemented!!!! Cause In 10g DB instance and 11g ASM instance, disk offline always fails with ORA-600[kfdOffline01][3] w hen11g disk mode is not compatible with 10g disk mode. Hence, disk mode shipped from 10g software always cause ORA-600[kfdOffline01] in 11g ASM instance. Solution -- To implement the solution, please execute the following steps:: There are two solutions for this problem: 1a- Check database instance alert.log and see what disks were being dropped. alert.log for DB instance Wed Sep 17 23:26:16 2008 WARNING: offlining disk 0.3145914571 (DISK1DG1FG1) with mask 0x3 1b- Attach to the ASM instance, and drop the disk manually. SQL> alter diskgroup dg01 drop disk DISK1DG1FG1; 2- Apply the patch for the Bug 7311909. If 11g software finds 10g DB instance or 10g ASM instance, then the patch functions will convert it for compatibilty. The fix will also be included in the forthcoming 11.1.0.8 patchset. References Bug 7311909 - ORA-600 [KFDOFFLINE01] ERROR WHEN ONE OF THE FAILGROUPS IS OFFLINED Keywords ASM ; ----- Note: ----- Subject: ORA-600[kffmUnlock_3] POSSIBLE WHEN DATABASE INSTANCE 10GR2 AND ASM 11G Doc ID: 756696.1 Type: PROBLEM Modified Date : 17-DEC-2008 Status: REVIEWED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.3 This problem can occur on any platform. Symptoms ASM and database instances are using different versions. Database instance runs in a 10gR2 version whereas ASM instance on 11g version. ASM instance is shutdowned when there is a rebalance runing and not finished yet. The following rebalances causes the database instance to get ORA-600[kffmUnlock_3] exception due to an interoperability issue between 10gR2 database and 11g ASM versions. Cause -- alert_+ASM.log SUCCESS: ALTER DISKGROUP DATA ADD DISK 'ORCL:LUN5' SIZE 953357 M ,'ORCL:LUN6' SIZE 953357 M ,'ORCL:LUN7' SIZE 953357 M NOTE: starting rebalance of group 1/0xdc6ccda9 (DATA) at power 1 Starting background process ARB0 Mon Nov 24 16:34:43 2008 ARB0 started with pid=19, OS id=10338 NOTE: assigning ARB0 to group 1/0xdc6ccda9 (DATA) -- alert_DB.log Wed Nov 26 15:26:26 2008 Errors in file /opt/oracle/app/oracle/admin/crn_prod/bdump/crn_prod_asmb_5828.trc: ORA-600: internal error code, arguments: [kffmUnlock_3], [99], [10286], [1], [0], [117], [288063], [] Database instance is crashed by ASMB process. At the same moment, a rebalance was runing in ASM instance. Exception happens when ASM sends multiple unlock messages to database instance. 10g version is not allowed the multiple unlock messages, ASMB process raises the exception and crashes the instance. This is due to BUG.7247337 Bug 7247337 - 10GR2 INSTANCE CRASHED ORA-00600 [KFFMUNLOCK_3] WITH 11.1.0.6 ASM Solution Completing the rebalance when database is shutdowned resolves the further database crashes. Because, in this situation multiple unlock messages will be ignored. 1- Shutdown 10g database and 11g ASM instances with normal/immediate option. 2- Set asm_power_limit=11 in init.ora for the 11g ASM instance for faster relocation. 3- Startup the 11g ASM instace, mount the diskgroup, so the interrupted rebalance will resume automatically. You will see the rebalance startup messages in ASM alert.log like: NOTE: starting rebalance of group 1/0x7200055 (DATA) at power 11 NOTE: assigning ARB0 to group 1/0x7200055 (DATA) NOTE: assigning ARB1 to group 1/0x7200055 (DATA) ... 4- Monitor the rebalance sql> select * from v$asm_operation; Ensure the rebalance is completed by checking ASM alert.log: SUCCESS: rebalance completed for group group 1/0x7200055 (DATA) 5- After rebalance is completed, startup the 10g DB instance. This will avoid the further database crashes. Bug:7602341 is fixed in 10.2.0.5 version. Please contact Oracle Support for the availability of patches for different versions. ----- Note: ----- Subject: 11g Diagnosability: Frequently Asked Questions Doc ID: 453125.1 Type: FAQ Modified Date : 18-SEP-2008 Status: PUBLISHED In this Document Purpose Questions and Answers What is new in 11g Diagnosability? What is ADR? What is an ADR HOME? What is a Problem? What is an Incident? Where are the trace files and alert log Compared to 10g? What Oracle Errors can create an Incident? Can The Diagnosability Framework be configured to create an Incident for other errors? What is EM Support Workbench? What is ADRCI? How to send trace files and alert log related to a Problem/Incident to Oracle Support? What errors Can trigger Automatic Health Checks? Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.6 Information in this document applies to any platform. Purpose This document covers some of the 11g Diagnosability Frequently Asked Questions. Questions and Answers What is new in 11g Diagnosability? Beginning with Release 11g, Oracle Database includes an advanced fault diagnosability infrastructure for collecting and managing diagnostic data. Diagnostic data includes the trace files, dumps, and core files that are also present in previous releases, plus new types of diagnostic data that enable customers and Oracle Support to identify, investigate, track, and resolve problems quickly and effectively. What is ADR? The Automatic Diagnostic Repository (ADR) is a file-based repository for storing diagnostic data. Because this repository is stored outside the database, the diagnostic data is available even when the database is down. As of Release 11g, the alert log, all trace and dump files, and other diagnostic data are also stored in the ADR. What is an ADR HOME? An ADR HOME is the root directory for all diagnostic data—traces, dumps, the alert log, and so on—for a particular instance of a particular Oracle product or component. The location of an ADR home is given by the following path, which starts at the ADR base directory: diag/product_type/product_id/instance_id Example of ADR HOMES: diag/rdbms/orcl/ORCL1 (Product=rdbms, product_id=db_name=orcl, instance_id=ORACLE_SID=ORCL) diag/asm/+asm/+ASM (Product=asm, product_id=+asm, instance_id=ORACLE_SID=+ASM) diag/tnslsnr/node1/listener (Product=tnslsnr - SQL*NET Listener, product_id=hostname=node1, instance_id=listener name=listener) What is a Problem? A problem is a critical error in the database. Critical errors manifest as internal errors, such as ORA-600, and other severe errors, such as ORA-7445 or ORA-4031. Problems are tracked in the Automatic Diagnostic Repository (ADR). What is an Incident? An incident is a single occurrence of a problem. When a problem occurs multiple times, an incident is created for each occurrence. Incidents are timestamped and tracked in the Automatic Diagnostic Repository (ADR). Where are the trace files and alert log Compared to 10g? Diagnostic Data Previous Location ADR Location Foreground Process Traces user_dump_dest ADR HOME/trace Background Process Traces background_dump_dest ADR HOME/trace Alert Log File background_dump_dest ADR HOME/alert/log.xml ADR HOME/trace/alert_.log SQL*Net Listener Log File log_directory_listener ADR HOME/alert /log.xml Core Dump Files core_dump_dest ADR HOME/cdump Incident Dump Files _dump_dest ADR HOME/incident/incdir_n What Oracle Errors can create an Incident? The next errors will automatically produce an Incident: Internal errors: ORA-00600 "internal error code, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" ORA-00700 "soft internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]" ORA-07445 "exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]" Some of the External Errors are: ORA-04030 "out of process memory when trying to allocate %s bytes (%s,%s)" ORA-04031 "unable to allocate %s bytes of shared memory (\"%s\",\"%s\",\"%s\",\"%s\")" ORA-29740 "evicted by member %s, group incarnation %s" ORA-01578 "ORACLE data block corrupted (file # %s, block # %s)" ORA-00353 "log corruption near block %s change %s time %s" ORA-00355 "change numbers out of order" ORA-00356 "inconsistent lengths in change description" Can The Diagnosability Framework be configured to create an Incident for other errors? No, only a set of predefined errors are automatically tracked by the diagnosability framework. What is EM Support Workbench? The Enterprise Manager Support Workbench (Support Workbench) is a facility that enables you to investigate, report, and in some cases, repair problems (critical errors), all with an easy-to-use graphical interface. The Support Workbench provides a self-service means for you to gather first-failure diagnostic data, obtain a support request number, and upload diagnostic data to Oracle Support with a minimum of effort and in a very short time, thereby reducing time-to-resolution for problems. The Support Workbench also recommends and provides easy access to Oracle advisors that help you repair SQL-related problems, data corruption problems, and more. What is ADRCI? The ADR Command Interpreter (ADRCI) is a utility that enables you to investigate problems, view health check reports, and package and upload first-failure diagnostic data to Oracle Support, all within a command-line environment. ADRCI also enables you to view the names of the trace files in the ADR, and to view the alert log with XML tags stripped, with and without content filtering How to send trace files and alert log related to a Problem/Incident to Oracle Support? In 11g there is a new way to package diagnostic trace files and alert log information. The documentation of Using EM Support Workbench to upload an IPS package to Oracle Support is in: Oracle® Database Administrator's Guide Chapter 8 - Managing Diagnostic Data Creating, Editing, and Uploading Custom Incident Packages The documentation of using ADRCI to upload an IPS package to Oracle Support is in: Oracle® Database Utilities Chapter 15 ADRCI: ADR Command Interpreter Packaging Incidents What errors Can trigger Automatic Health Checks? The errors that might trigger Automatic Health Checks are classified by the health check type: Database Structure Integrity Check: ORA-202 ORA-214 ORA-1103 ORA-312 ORA-313 ORA-1110 Redo Integrity Check: ORA-353 Data Block Integrity check: ORA-1578 Transaction Integrity check: ORA-600 [4136] ORA-600 [4137] ORA-600 [4139] ORA-600 [4140] ORA-600 [4143] ORA-600 [4144] ORA-600 [4152] The documentation about Health Checks is in: Oracle® Database Administrator's Guide Chapter 8 - Managing Diagnostic Data Running HealthChecks with Health Monitor ----- Note: ----- ORA-00600 ORA-600 [kokegPinLob1] Subject: Bug 6922966 - OERI:kokegPinLob1 from select of CLOB view column Doc ID: 6922966.8 Type: PATCH Modified Date : 12-DEC-2008 Status: PUBLISHED Bug 6922966 OERI:kokegPinLob1 from select of CLOB view column This note gives a brief overview of bug 6922966. The content was last updated on: 12-DEC-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 10.2.0.4 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 11.2 (Future Release) Symptoms: Related To: Internal Error May Occur (ORA-600) ORA-600 [kokegPinLob1] Datatypes (LOBs/CLOB/BLOB/BFILE) Description An ORA-600 [kokegPinLob1] can occur when selecting a CLOB view column. 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 6922966 (This link will only work for PUBLISHED bugs) Note 245840.1 Information on the sections in this article ----- Note: ----- ORA-00600 ORA-600 [15201] Subject: Bug 6607505 - OERI [15201] from DML on table with FUNCTION BASED index on LOB column/s Doc ID: 6607505.8 Type: PATCH Modified Date : 24-SEP-2008 Status: PUBLISHED Bug 6607505 OERI [15201] from DML on table with FUNCTION BASED index on LOB column/s This note gives a brief overview of bug 6607505. The content was last updated on: 23-SEP-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 10.2.0.3 10.2.0.4 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 11.2 (Future Release) 10.2.0.5 (Server Patch Set) 11.1.0.7 (Server Patch Set) Symptoms: Related To: Internal Error May Occur (ORA-600) ORA-600 [15201] ORA-600 [mal0-size-too-large] Datatypes (LOBs/CLOB/BLOB/BFILE) Function Based Index (Including DESC Indexes) Description ORA-600 [15201] / ORA-600 [mal0-size-too-large] errors can occur during DML operations on objects having functional indexes containing LOB columns. 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 6607505 (This link will only work for PUBLISHED bugs) Note 245840.1 Information on the sections in this article ----- Note: ----- ORA-00600 ORA-600 [7999] Subject: Bug 3029292 - LOB corruption possible on ASSM tablespace Doc ID: 3029292.8 Type: PATCH Modified Date : 24-SEP-2008 Status: PUBLISHED Bug 3029292 LOB corruption possible on ASSM tablespace This note gives a brief overview of bug 3029292. The content was last updated on: 11-FEB-2004 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 but < 10.1.0.2 Versions confirmed as being affected 9.2.0.4 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in 9.2.0.5 (Server Patch Set) 10.1.0.2 (Base Release) Symptoms: Related To: Internal Error May Occur (ORA-600) Corruption (Physical) ORA-600 [7999] Datatypes (LOBs/CLOB/BLOB/BFILE) ASSM Space Management (Bitmap Managed Segments) Description This issue affect Aut space managed segments: After executing "TRUNCATE TABLE table" or "ALTER TABLE table DEALLOCATE UNUSED", ORA-600 [7999] errors or data corruption can occur in the file that the LOB segments of the table reside in. This is because the truncate/alter table can cause the high watermark to be moved and the way in which the position of the high watermark is calculated is wrong. This can result in blocks being potentially allocated/freed by multiple objects or LOBs simultaenously and therefore corrupted. dbms_space_admin.segment_verify can be used on all LOB segments to check for corruption. 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 3029292 (This link will only work for PUBLISHED bugs) Note 245840.1 Information on the sections in this article ----- Note: ----- Subject: Remote Diagnostic Agent (RDA) 4 - Content Modules Man Page Doc ID: 330760.1 Type: DIAGNOSTIC TOOLS Modified Date : 09-DEC-2008 Status: PUBLISHED RDA 4 - Module Documentation RDA Main Links Getting Started FAQ Manual Pages Troubleshooting Guide Training RDA Documentation Index Related Pages RDA Manual Page Profile Documentation Engine Documentation DATA COLLECTION MODULES · ACT Collects Oracle E-Business Suite Application Information · ADX Collects AutoConfig and Rapid Clone Information · AGT Collects Enterprise Manager Agent Information · APEX Collects APEX Information · ASAP Collects Oracle Communications Automated Service Activation Program · ASBR Collects Oracle Application Server Backup and Recovery Information · ASG Collects Application Server Guard Information · ASM Collects Automatic Storage Management Information · BEE Collects Beehive Information · BI Collects Oracle Business Intelligence Information · BPEL Collects Oracle BPEL Process Manager Information · BR Collects Database Backup/Recovery Information · CFG Collects Key Configuration Information · CONT Collects Oracle Content Services Information · CRID Collects Oracle Access Manager (COREid) Information · CWT Collects Oracle Application Server 11g Classic/WebTier Information · D2PC Collects Distributed Transaction Information · DB Controls RDBMS Data Collection · DBA Collects RDBMS Information · DBC Collects Database Control Information · DBM Collects RDBMS Memory Information · DEV Collects Oracle Developer Information · DG Collects Data Guard Information · DSCS Collects Discussions Information · DSCV Collects Oracle Discoverer Information · EM Collects Enterprise Manager OMS and Repository Information · END Finalizes the Data Collection · ESB Collects Enterprise Service Bus Information · FLTR Controls Report Content Filtering · GRID Controls Grid Control Data Collection · GTW Collects Transparent/Procedural Gateway Information · IA Collects Intelligent Agent Information · IAS Collects Web Server Information · IFS Collects iFS (iFS, CMSDK, Files) Information · INI Initializes the Data Collection · INST Collects the Oracle Installation Information · IPSA Collects the Oracle Communications IP Service Activator Information · J2EE Collects J2EE Standalone Information · JIVE Collects Jive Information · LANG Collects Oracle Language Information · LOAD Produces the External Collection Reports · LOG Collects Database Trace and Log Files · MAIL Collects Oracle Collaboration Suite Mail Information · MSLG Collects Microsoft Languages Information · ND Collects Oracle Communications Network Discovery Information · NET Collects Network Information · NM Collects Oracle Communications Network Mediation Information · NPRF Samples Performance Information (root not required) · OCAL Collects Oracle Calendar Information · OCFS Collects Oracle Cluster File System Information · OCM Setting up Configuration Manager Interface · OCS Controls Oracle Collaboration Suite Data Collection · ODI Collects Oracle Data Integrator Information · ODM Collects Oracle Data Mining Information · OES Collects Oracle Express Server Information · OID Collects Oracle Internet Directory Information · OIM Collects Oracle Identity Manager Information · OLAP Collects OLAP Information · OMM Collects Oracle Multimedia Information · ONET Collects Oracle Net Information · OS Collects the Operating System Information · OVD Collects Oracle Virtual Directory Information · OVMM Collects Oracle VM Manager Information · OVMS Collects Oracle VM Server Information · OWB Collects Oracle Warehouse Builder Information · OWSM Collects Oracle Web Services Manager Information · PDA Collects Portal Diagnostics Information · PERF Collects Performance Information · PLNC Collects Oracle PL/SQL Native Compilation Information · PROF Collects the User Profile · PRSF Collects Portal Software Information · PS Collects Oracle Communications Policy Services Information · RAC Collects Cluster Information · RACD Performs a Database Hang Analysis · RDSP Produces the Remote Data Collection Reports · RET Collects Oracle Retail Information · REXE Performs the Remote Data Collections · RPRF Samples Performance Information (root privileges required) · RSRC Collects Database Resource Manager Information · RTC Collects Real Time Communication Information · SMPL Controls Sampling · SOA Collects Oracle SOA Information · SSO Collects Single Sign-On Information · STC Collects Streams Configuration Information · STM Collects Streams Monitoring Information · WAC Collects Web Access Client Information · WCI Collects Oracle WebCenter Information · WEBC Collects Web Cache Information · WKSP Collects Workspaces Information · WLS Collects Oracle WebLogic Server Information · WMC Collects Webmail Client Information · WRLS Collects Wireless Information · XSMP Samples User Defined Data · XTRA Collects User Defined Data TOOLS Run the following modules with the -T mode option · diff Compares Systems · em Runs the Enterprise Manager Tool · hcve Executes HCVE Tests · merge Merges Alert Log and Trace Files · na Runs the Network Advisor · ora600 Diagnoses ORA-600 Oracle Internal Errors · oraddc Runs the Oracle Database Diagnostic Collector · secure Identifies Potential Security Risks TEST MODULES Run the following modules with the -T mode option · alert Analyzes alert.log · core Tests Stack Trace Extraction · db Tests Local Database Access · dst Daylight Saving Time Tool Box · env Tests the Environment · event Extracts Event Log Information · inv Tests Oracle Home Inventory Content · ocm Tests Configuration Manager Discovery Information · odi Displays the Current Oracle Data Integrator Module Setup · sql Tests SQL Settings · ssd Analyzes System State Dumps · ssh Tests Remote Connectivity and Operations · vms Verifies Current User Environment on VMS -------------------------------------------------------------------------------- NAME APPSinfo - Defines Common Oracle Applications Macros DESCRIPTION This persistent sub module regroups macros that are common to Oracle Applications modules. The following macros are available: chk_apps_column($own,$obj,$col) This macro indicates if the specified column exists in a table. It returns the list of occurrences. chk_apps_object($own,$obj) This macro indicates if an object exists in the database. It returns the list of occurrences. chk_apps_patch($num) This macro checks whether a specified patch has been applied. dsp_patches($fil,$typ,$mod,$lst) This macro determines whether patches from the list are applied. It displays the latest patch, which must be the first in the list. It returns the name of the patch. find_prod_dir2($prd,$sub,$nam) This macro returns the list of directories that match the /*/ pattern in the product directory structure. fmt_version($str) This macro formats a version number that is accepted in the security filter. get_apps_version() This macro retrieves the Oracle Applications versions and product list. get_class_version($fil) This macro gets the version of the Application Java classes. get_file_version($fil) This macro gets the version of a file using the adident command or by extracting the strings from the file. get_prod_version($rec,$prd,$sub,$pat,$dat,$ext,$mlt,$nbf,@lng) This macro displays file versions matching the pattern under the specified product top and subdirectory. It also processes files for each language. get_profile_value($nam,$uid,$rid,$aid) This macro retrieves a profile value for the specified user, responsibility, and application identifiers. get_ssfw_version($ver) This macro gets the version of Oracle Framework. -------------------------------------------------------------------------------- NAME BCaix - Sub Module for AIX-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat 1 1 · lsof -S 2 · netstat -s · ps -elf · uptime · vmstat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BCdarwin - Sub Module for Darwin-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat 1 1 · lsof -S 2 · netstat -s · ps -auxww · top -tl 1 · uptime · vm_stat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BChpux - Sub Module for HP-UX-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat 1 1 · lsof -S 2 · sar -A -S 1 1 (as an alternative to mpstat) · netstat -s · ps -elf · top -s 1 -d 1 -n 40 · uptime · vmstat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BClinux - Sub Module for Linux-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat -x 1 1 · lsof -S 2 · cat /proc/meminfo · mpstat -P ALL · netstat -s · ps -elf · cat /proc/slabinfo · top -b -n 1 · uptime · vmstat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE Requests kernel information using the following: · echo 'm' >/proc/sysrq-trigger · echo 't' >/proc/sysrq-trigger · echo 'w' >/proc/sysrq-trigger -------------------------------------------------------------------------------- NAME BCosf - Sub Module for OSF-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat 1 1 · lsof -S 2 · netstat -s · ps -elf · top -d1 · uptime · vmstat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BCptx - Sub Module for Dynix/Ptx-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · netstat -s · ps -elf · top -d 1 · uptime · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BCsunos - Sub Module for Solaris-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat -n 1 1 · lsof -S 2 · mpstat -P ALL · netstat -s · ps -elf · top -d 1 · uptime · vmstat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BCunix - Sub Module for UNIX-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · iostat 1 1 · lsof -S 2 · netstat -s · ps -elf · top -d 1 · uptime · vmstat 1 1 · The last sar raw data file if NPRF_SAR_DATA setting value is true CONTRIBUTION TO THE RPRF MODULE TBD -------------------------------------------------------------------------------- NAME BCwin32 - Sub Module for Windows-Specific Background Collections DESCRIPTION This module contains the operating system-specific code for the sampling modules. CONTRIBUTION TO THE NPRF MODULE Collected information: · netstat -s · tasklist /V CONTRIBUTION TO THE RPRF MODULE Not applicable -------------------------------------------------------------------------------- NAME COREinfo - Extracts Core Dump Information DESCRIPTION This module extracts relevant information from a core dump file. The following macros are available: can_analyze_core() This macro indicates which command has been found to analyze core dumps. Otherwise, it returns an undefined value. analyze_core($dmp...) This macro analyzes all core dumps specified as arguments. For each dump, it determines the location of the corresponding executable first and then extracts the stack information. run_coreadm($pat) This macro writes the global and per process coreadm command output into the current report. The process for which coreadm command is to be run, are selected based on a regular expression. -------------------------------------------------------------------------------- NAME DARVload - Collects DARV Data DESCRIPTION This module collects a copy of the Database Activity Recorder files. The following report is produced: dar_box - Database Activity Recorder When available, this module collects a copy of the Database Activity Recorder files. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME DBalert - Analyzes alert.log DESCRIPTION This module analyzes the alert.log file and produces an analysis summary. Times are truncated at the second level. -------------------------------------------------------------------------------- NAME DBinfo - Collects Key RDBMS Information DESCRIPTION This module collects key RDBMS information that is required for database-related modules. The following macros are available: find_dest() Determines the background, core, and user destinations. It checks v$parameter first. If the information is not available there, then the macro looks in pfile or in other known places. find_diag() Finds the diagnostic directories. get_alert_name() Gets the name of the alert log. get_bdump() Gets and returns the background dump destination. get_cdump() Gets and returns the core dump destination. get_diag() Gets and returns the diagnostic destination. get_udump() Gets and returns the user dump destination. get_db_version($flg,$dft) Determines the database version. When the flag is set, it forces a new detection but does not save the results. A default value can be provided as a second argument. SEE ALSO See also S010CFG.def, S200DB.def, S201DBA.def, S204LOG.def, S205BR.def, S230STC.def, S231STM.def, S330SSO.def, S391OWB.def, S392ODM.def, S402ASM.def. -------------------------------------------------------------------------------- NAME DBssd - Analyzes System State Dumps DESCRIPTION This module provides an overview of the content of system state dump files. The following macro is available: analyze_ssd($fil,...) This macro analyzes the specified system dump files. -------------------------------------------------------------------------------- NAME DDCload - Collects Oracle Database Diagnostic Collector Reports DESCRIPTION oraddc - Database Diagnostic Collector This module gets reports generated by Oracle Database Diagnostic Collector (ORADDC) during the last 15 days. -------------------------------------------------------------------------------- NAME DDCrun - Oracle Database Diagnostics Collector (Data Collection) DESCRIPTION This module executes the data collection part of the Oracle Database Diagnostics Collector. SEE ALSO See also DBinfo.def, TLoraddc.def, DDCstat.def. -------------------------------------------------------------------------------- NAME DDCrun - Oracle Database Diagnostics Collector (Status Check) DESCRIPTION This module checks whether Oracle Database Diagnostics Collector (ORADDC) is waiting still for a wake-up by checking the last modification of its timestamp file. When the time since the last modification exceeds the specified tolerance (30 seconds by default), it removes the file and exits with a non zero status. SEE ALSO See also TLoraddc.def, DDCrun.def. -------------------------------------------------------------------------------- NAME DFlinux - Collects Linux-specific Comparison Information DESCRIPTION This module collects Linux-specific information for comparing systems. SEE ALSO See also TLdiff.def, DIFFcmp.def, DIFFget.def. -------------------------------------------------------------------------------- NAME DIFFcmp - Compares the Collected Data DESCRIPTION This module compares the data collected about the operating system, the database and other data sources. COMPARISON FILE FORMAT ---+ CHAPTER::title ---+ INTRO::title |**|**| ||| ... [[#Top][Back to Top]] ---+ SECTION::title |**|**| ||| ... [[#Top][Back to Top]] Increasing numbers must be used for each chapter. The introduction and sections must have increasing numbers inside each chapter. Inside each section, the parameter name is a unique identifier. Alternative section formats are available. ---+ SECTION::title |**|**|**|...| ||||...| ... [[#Top][Back to Top]] For these sections, the second column is used for comparing records, and the next columns for the final report. ---+ SECTION::title |**|**%BR%...| ||%BR%...| ... [[#Top][Back to Top]] RDA uses this format to associate multiple information pieces to the same parameter. The heading of the second column indicates how many different elements are stored in the corresponding cells. SEE ALSO See also TLdiff.def, DIFFget.def. -------------------------------------------------------------------------------- NAME DIFFget - Performs Data Collections for Comparing Systems DESCRIPTION This module performs the data collection and generates the intermediate file for comparing systems. The following collection types can be combined: ASM - Automatic Storage Management Information Collects the Automatic Storage Management parameters, hidden parameters, product inventory, and file information on some executables. DB - Oracle Database Information Collects the Oracle database parameters and hidden parameters. Extra - Extra Information Collects file informations for the extra directories. OH - Oracle Home Information Analyzes Oracle home files: sqlnet.ora, listener.ora, and tnsnames.ora. It performs a basic parsing of those files and applies a few normalization rules on the values. The final report contains the original files. It collects the product inventory and file information on some executables also. OH - Real Application Cluster Information Checks if RAC is linked in the Oracle executable and collects CSS Daemon status, crs_stat details, and product inventory. SEE ALSO See also TLdiff.def, DIFFcmp.def. -------------------------------------------------------------------------------- NAME DIFFload - Collects System Comparison Reports DESCRIPTION diff - System Comparisons This module gets system comparison reports generated by during the last 15 days. -------------------------------------------------------------------------------- NAME EMdiag - Common Macros Related to Oracle Enterprise Manager DESCRIPTION This module contains common macros used by the AGT, DBC, and EM modules. call_emdiag_kit($violation,$audit) This macro collects EMDIAG kit information. check_emdiag_kit() This macro indicates whether the EMDIAG kit is installed. check_permissions($ttl,\@own,\%dir,\%fil) This module performs ownership and permission checks on files and directories. It reports non-compliances. display_agent_config($dir,\@cfg,\@log) This macro collects the agent configuration and performs specified tests on emd.properties and emdlogging.properties. display_oms_config($emh,\@cfg,\@log) This macro collects OMS configuration and performs specified tests on emoms.properties and emomslogging.properties. display_targets($cmd,$dir,@tst) This macro lists targets and their properties. It also performs some property tests. dump_oms_threads($cmd,$log) This macro dumps the OMS threads. exec_emctl($cmd,\@opt,\dsc) This macro generates a report with the output of a list of specified emctl command options. extract_errors($ttl,$lim,@fil) This macro extracts ERROR records from the specified log files. It limits the record extraction to the last occurrences. get_agent_name($hom) This macro returns the name of the agent. It parses the target.xml file from the specified context to get the name of the agent. get_agent_version($cmd,$dbc) This macro returns the agent version. get_config($cmd) This macro returns the value of CONSOLE_CFG from the emctl file. get_em_conn($hom) This macro returns the database connection string for the EM repository. get_em_login($hom) This macro returns the database user name for the EM repository. get_oms_version($cmd,$dbc) This macro returns the OMS version. get_repository_host($hom) This macro returns the OMS host name. It parses the emd.properties file from the specified context to get the OMS host name. ping_host($ttl,@hst) This macro performs ping tests. -------------------------------------------------------------------------------- NAME HCaix - Sub Module Specific to the AIX Operating System DESCRIPTION This module determines the operating system version and its bit size. The following macro is available: get_df($dir) This macro returns the number of free KiB on the file system containing the specified directory. -------------------------------------------------------------------------------- NAME HCdarwin - Sub Module Specific to the Mac OS/Darwin Operating System DESCRIPTION This module determines the operating system version. The following macro is available. get_df($dir) This macro returns the number of free KiB on the file system containing the specified directory. -------------------------------------------------------------------------------- NAME HChpux - Sub Module Specific to the HP-UX Operating System DESCRIPTION This module determines the operating system version and its bit size. The following macro is available: get_df($dir) This macro returns the number of free KiB on the file system containing the specified directory. -------------------------------------------------------------------------------- NAME HClinux - Sub Module Specific to the Linux Operating System DESCRIPTION This module determines the Linux flavor. It determines the operating system version and its bit size. The following macros are available: cmp_kernel($name[,$ver[,$ref]]) This macro checks if the kernel release is valid. When no version or reference is provided, it is automatically rejected as not certified. get_df($dir) This macro returns the number of free MiB on the file system containing the specified directory. OPERATING SYSTEM PACKAGE MACROS chk_os_pkg($name[,$architecture[,$options]]) This macro selects the operating system packages matching the name and optionally the architecture. You can provide a regular expression for the architecture. The architecture grep options are specified as an extra argument. It returns the number of packages found. cmp_os_pkg(\@tbl,$name,$ref[,$architecture]) This macro lists the operating system packages matching the name and optionally the architecture that are older than the specified reference. fnd_os_pkg($name,$ver,$ref[,$architecture]) This macro looks for a specified version of operating system packages matching the name and optionally the architecture. It checks if the release is older than the specified reference, and returns the corresponding message. It returns an undefined value if the package is not found. get_os_pkg([...]) This macro gets the first hit from the list and returns the package information as a list, containing the version, release, and architecture. It returns an empty list when no -more- values are found. When you specify arguments, it first performs a chk_os_pkg. tst_os_pkg($name,$ref[,$architecture]) This macro tests if operating system packages matching the name and optionally the architecture are older than the specified reference. -------------------------------------------------------------------------------- NAME HCosf - Sub Module Specific to OSF Operating System DESCRIPTION This module determines the operating system version and its bit size. The following macro is available: get_df($dir) This macro returns the number of free KiB on the file system containing the specified directory. -------------------------------------------------------------------------------- NAME HCptx - Sub Module Specific to the Dynix/Ptx Operating System DESCRIPTION This module determines the operating system version and its bit size. -------------------------------------------------------------------------------- NAME HCsunos - Sub Module Specific to the Solaris Operating System DESCRIPTION This module determines the operating system version and its bit size. The following macro is available: get_df($dir) This macro returns the number of free KiB on the file system containing the specified directory. -------------------------------------------------------------------------------- NAME HCunix - Sub Module Specific to other UNIX Operating Systems DESCRIPTION This module determines the operating system version. -------------------------------------------------------------------------------- NAME HCVEinfo - Defines Health Check/Validation Engine Macros DESCRIPTION This persistent sub module regroups macros to perform health check rules within RDA. The following macros are available: get_hcve_rules($fil) This macro loads the validation rules. It returns 0 on successful completion, -1 for parsing errors at file load, or the rule index for a missing identifier. By default, the module is searched in the hcve directory. val_hcve_rules() This macro validates the rules and returns a list of error messages. exe_hcve_rules() This macro executes the validation rules. dsp_hcve_results() This macro reports the test results on the screen. wrt_hcve_errors($ttl) This macro writes the test errors in the output file. wrt_hcve_man($set) This macro writes a complete description of the specified rule set. wrt_hcve_results($ttl[,$flg]) This macro writes the test results in the output file. When the flag is set, it also reports the details. SEE ALSO See also HCVEinit. -------------------------------------------------------------------------------- NAME HCVEinit - Initializes the Health Check/Validation Engine Evaluation Context DESCRIPTION This persistent sub module contains the initialization of the evaluation context for all actions written in the data collection specification language. COMMON MACROS load_passwords() This macro loads stored passwords. SEE ALSO See also HCaix, HCdarwin, HChpux, HClinux, HCosf, HCptx, HCsunos, HCunix, HCvms, HCwin32. -------------------------------------------------------------------------------- NAME HCVEload - Collects HCVE Reports DESCRIPTION This module gets reports generated by the Health Check/Validation Engine. The following report is produced: hcve - Health Check/Validation Engine Gets reports generated by the Health Check/Validation engine. -------------------------------------------------------------------------------- NAME HCvms - Sub Module Specific to the VMS Operating System DESCRIPTION This module determines the operating system version and its bit size. -------------------------------------------------------------------------------- NAME HCwin32 - Sub Module Specific to the Windows Operating System DESCRIPTION This module determines the operating system version and its bit size. -------------------------------------------------------------------------------- NAME IAS - Collects Web and HTTP Information DESCRIPTION This module collects Web and HTTP-related information. The following macros are available: HTTP SERVER MACROS macro httpServer_getListenerConf([$flag]) This macro recursively searches all httpd.conf included files. It modifies the following imported variables: %HTTPDCONF httpd.conf and all included files (that is, all files that can contain configuration directives). $SERVERROOT The Apache ServerRoot setting. It may not be handled correctly in all cases. Non-absolute paths are relative to ServerRoot, but if ServerRoot is in the included files, ServerRoot and include directives may not be processed in the correct order. It requires the $APACHE_TOP and $ORACLE_HOME variables. It does not generate reports when the flag is true. macro httpServer_getListenerLogs([$flag]) This macro retrieves the log files. It modifies the following imported variables: %HTTPDERRLOG All log files from ErrorLog and SSLLog directives. %HTTPDREQLOG All request log files from TransferLog and CustomLog directives. For rotatelogs, it gets the last or most current file. Because the suffixes indicate the number of seconds since 1970, the last line from the alphabetically sorted output is also the most recent or current one. Only suffixes with exactly ten digits are used because the billionth UNIX second was in 2001 and the 32bit overflow of UNIX time will be greater than 2 billion in 2038. Similarly named files such as access_log.20041231 are ignored. It requires the $APACHE_TOP, $ORACLE_HOME, and %HTTPDCONF variables. It does not generate reports when the flag is true. macro httpServer_getJServConf This macro retrieves the Jserv configuration. It modifies the following imported variables: %JSERVPROPERTIES All jserv.properties that are used by Apache configurations. %JSERVZONEPROPS The zone.properties of all recognized JServ engines. @JSERVCFGFILES Both the jserv properties files and the zone properties files. It requires the $ORACLE_HOME, and %HTTPDCONF variables. macro httpServer_getJServJavaVersions This macro determines the Java versions used by Jserv. It requires %JSERVPROPERTIES. macro httpServer_getJServLogs This macro gets the JServer logs. It modifies the following imported variable: %JSERVLOG JServ log files, both from the engines themselves and from the Apache module. It requires the $APACHE_TOP, $ORACLE_HOME, and %JSERVPROPERTIES variables. macro httpServer_getModplsqlConf This macro attempts to find WV_GATEWAY_CFG from the environment and default location. It modifies the following imported variable: %HTTPDMODPLSQLCFG Heuristically finds candidates for the wdbsvr.app file for mod_plsql. It requires the $APACHE_TOP, $ORACLE_HOME, and @HTTPDSTARTSCRIPTS variable. macro httpServer_getStartScripts This macro displays existing start scripts. It modifies the following imported variables: @HTTPDSTARTSCRIPTS Scripts to start Apache: apachectl and httpdsctl. These scripts may have been changed to include additional environment variables. It requires the $APACHE_TOP and $ORACLE_HOME variables. -------------------------------------------------------------------------------- NAME IASr1012 - Collects OAS 10g R2 Information (10.1.2) DESCRIPTION This module collects Oracle Application Server 10g R2 (10.1.2)-related information (such as DCM, HTTP Server, JAVACACHE, ODL, OPMN, LDAP, and SYSMAN). REPORTS Oracle AS 10g Gathers all general Oracle AS 10g information. Install and Configuration Gathers the Application Server configuration and installation files. DCM Collects the last DCM error, the cluster and standalone instance information, the DCM dump, and the log files of the DCM repository. RDA performs these collections only when the ias.properties file is available. Unless forced, collections are skipped if the DCM daemon is not running for versions earlier than 10.1.2.2. dcm_error - dcmctl getError Retrieves the last DCM error before RDA started. dcm_cluster - DCM Cluster Collects DCM cluster information. For each instance on which clusters are found, RDA gathers information about the components and applications. dcm_standalone - Standalone Instances Collects dcmctl information for instances that are not part of a cluster. RDA gathers information that includes the components and applications. dcm_dump - dcmctl dump Collects DCM dump information from the infrastructure. DMS Collects a dmstool dump and provides a starting point for analyzing performance issues. HTTP Server Gathers HTTP server information. JAVACACHE Gathers Java Object Cache information. javacache - Java Cache Gathers Java Cache command information. diskcache - Java DiskCache Gathers Java DiskCache information. LDAP Gathers LDAP information. ODL Gathers Oracle Diagnostics Logging (ODL) information. It collects utilization over the last 24 hours, with warnings and errors from components that are enabled for ODL. odl_log - HTTP Server Log File Gathers HTTP Server Oracle Diagnostics Logging (ODL) information. This new method for reporting diagnostic messages presents a common format for diagnostic messages and log files, and a mechanism for correlating all diagnostic messages from various components across Oracle database. J2EE ODL Log Files Gathers J2EE ODL Diagnostics information. OPMN Gathers OPMN information. It finds all *.log, *.conf, and *.xml files. SYSMAN Gathers SYSMAN information. HCVE When requested, performs the pre-installation checks. SEE ALSO See also IAS.def, library.def. -------------------------------------------------------------------------------- NAME IASr1013 - Collects OAS 10g R3 Information (10.1.3) DESCRIPTION This module collects Oracle Application Server 10g R3 (10.1.3)-related information (such as AS Control, HTTP Server, ODL, OPMN, LDAP, and SYSMAN) REPORTS Oracle AS 10g Gathers all general Oracle Application Server 10g information AS Control Gathers AS Control information. BAM Note: RDA performs Business Activity Monitoring (BAM) collection on a Windows platform only. bam_root_dir - BAM Root Directory Displays the content of the BAM root directory. BAM Configuration Files Collects the configuration files from the BAM root directory. BAM Log Files Collects the BAM log files from the log directory. bam_events - BAM Events Displays the details of all the events related to BAM services from the application event log. DMS Collects a dmstool dump and provides a starting point for analyzing performance issues. HTTP Server Gathers HTTP server information. JAVACACHE Gathers Java Object Cache information. javacache - Java Cache Gathers Java Cache command information. diskcache - Java DiskCache Gathers Java DiskCache information. LDAP Gathers LDAP information. Not every Oracle Application Server 10g installation has an LDAP directory. ODL Gathers Oracle Diagnostics Logging (ODL) information. It collects utilization over the last 24 hours, with warnings and errors from components that are enabled for ODL. odl_log - HTTP Server Log File Gathers HTTP Server Oracle Diagnostics Logging (ODL) information. This new method for reporting diagnostic messages presents a common format for diagnostic messages and log files, and a mechanism for correlating all diagnostic messages from various components across Oracle database. J2EE ODL Log Files Gathers J2EE ODL Diagnostics information. OPMN Gathers OPMN information. It finds all *.log, *.conf, and *.xml files. SYSMAN Gathers SYSMAN information. TOPLINK Gathers TOPLINK information. HCVE When requested, performs the pre-installation checks. SEE ALSO See also IAS.def, library.def. -------------------------------------------------------------------------------- NAME IASr1014 - Collects OAS 10g R4 Information (10.1.4) DESCRIPTION This module collects Oracle Application Server 10g R4 (10.1.4)-related information (such as DCM, HTTP Server, JAVACACHE, ODL, OIF, OPMN, LDAP, and SYSMAN). REPORTS Oracle AS 10g Gathers all general Oracle Application Server 10g information. DCM Collects the last DCM error, the cluster and standalone instance information, the DCM dump, and the log files of the DCM repository. RDA performs these collections only when the ias.properties file is available. Unless forced, collections are skipped if the DCM daemon is not running. dcm_error - dcmctl getError Retrieves the last DCM error before RDA started. dcm_cluster - DCM Cluster Collects DCM cluster information. For each instance on which clusters are found, RDA gathers information about the components and applications. dcm_standalone - Standalone Instances Collects dcmctl information for instances that are not part of a cluster. RDA gathers information that includes the components and applications. dcm_dump - dcmctl dump Collects DCM dump information from the infrastructure. DMS Collects a dmstool dump and provides a starting point for analyzing performance issues. HTTP Server Gathers HTTP server information. JAVACACHE Gathers Java Object Cache information. javacache - Java Cache Gathers Java Cache command information. diskcache - Java DiskCache Gathers Java DiskCache information. LDAP Gathers LDAP information. ODL Gathers Oracle Diagnostics Logging (ODL) information. It collects utilization over the last 24 hours, with warnings and errors from components that are enabled for ODL. odl_log - HTTP Server Log File Gathers HTTP Server Oracle Diagnostics Logging (ODL) information. This new method for reporting diagnostic messages presents a common format for diagnostic messages and log files, and a mechanism for correlating all diagnostic messages from various components across Oracle database. J2EE ODL Log Files Gathers J2EE ODL Diagnostics information. OIF Gathers Oracle Internet Filesystem (OIF) information. Includes the Federation Server, ShareID Module, and Monitoring information. data_store - data-store.xml Displays the data-store.xml file with some security key attributes obfuscated. config - config.xml Displays the config.xml file with some security key attributes obfuscated. shareid - shareidconfig.xml Displays the shareid-config.xml file with some security key attributes obfuscated. OPMN Gathers OPMN information. It finds all *.log, *.conf, and *.xml files. SYSMAN Gathers SYSMAN information. SEE ALSO See also IAS.def, library.def. -------------------------------------------------------------------------------- NAME IASr10g - Collects OAS 10g Information (9.0.4) DESCRIPTION This module collects Oracle Application Server 10g (9.0.4)-related information (such as DCM, DMS, HTTP Server, LDAP, OPMN, and SYSMAN). REPORTS Oracle AS 10g Gathers all general Oracle Application Server 10g information DCM Collects the last DCM error, the cluster and standalone instance information, the DCM dump, and the log files of the DCM repository. dcm_error - dcmctl getError Retrieves the last DCM error before RDA is started. dcm_cluster - DCM Cluster Collects DCM cluster information. For each instance on which clusters are found, RDA gathers information about the components and applications. dcm_standalone - Standalone Instances Collects dcmctl information for instances that are not part of a cluster. RDA gathers information that includes the components and applications. dcm_dump - dcmctl dump Collects DCM dump information from the infrastructure. DMS Collects a dmstool dump and provides a starting point for analyzing performance issues. HTTP Server Gathers HTTP server information. LDAP Gathers LDAP Information. OPMN Gathers OPMN information. It finds all *.log, *.conf, and *.xml files. SYSMAN Gathers SYSMAN information. HCVE When requested, performs the pre-installation checks. SEE ALSO See also IAS.def, library.def. -------------------------------------------------------------------------------- NAME IASr1 - Collects Web Server Information (9iAS 1.x) DESCRIPTION This module collects Web Server-related information. There are two functions in this script: one that gathers information for Apache in a hard-coded manner and one that gathers information dynamically. REPORTS web_env - Web Environment Collects the Web environment. cfg_files - Configuration Files Reports information about configuration files. web_processes - Web Processes Gathers Web processes. apache_over - Apache Overview Provides Apache configuration and overview. apache_logs - Apache Log Files Gathers Apache log files jserv_conf - Jserv Overview Collects Jserv files and configuration information. signon - Main URL / signonp - owa_util.print_cgi_env Performs Web checks through SQLPLUS. For Web server checks, you must set up the base URL and PL/SQL as follows: · WEB_BASE="http://:" · WEB_DCD="http://:/VIS/plsql" HTTP Server (new) Collects all files that are directly related to Oracle HTTP Server Powered by Apache, by scanning configuration files dynamically and identifying relevant files. SEE ALSO See also IAS.def, library.def. -------------------------------------------------------------------------------- NAME IASr2 - Collects 9iAS R2 Information (9.0.2 or 9.0.3) DESCRIPTION This module collects Oracle 9i Application Server R2 (9.0.2 or 9.0.3)-related information (such as DCM, DMS, HTTP Server, LDAP, OPMN, and SYSMAN). REPORTS 9iAS R2 Gathers all general Oracle 9i Application Server information. DCM Collects the last DCM error, the cluster and standalone instance information, the DCM dump, and the log files of the DCM repository. dcm_error - dcmctl getError Retrieves the last DCM error that occurred before RDA started. dcm_cluster - DCM Cluster Collects DCM cluster information. For each instance on which clusters are found, RDA gathers information about the components and applications. dcm_standalone - Standalone Instances Collects dcmctl information for instances that are not part of a cluster. RDA gathers information that includes the components and applications. dcm_dump - dcmctl dump Collects DCM dump information from infrastructure. DMS Collects a dmstool dump and provides a starting point for analyzing performance issues. HTTP Server Gathers HTTP server information. LDAP Gathers LDAP information. OPMN Gathers OPMN information. It finds all *.log, *.conf, and *.xml files. SYSMAN Gathers SYSMAN information. SEE ALSO See also IAS.def, library.def. -------------------------------------------------------------------------------- NAME IFSr1 - Collects iFS Information (iFS R1) DESCRIPTION This module collects iFS (CMSDK, Files) information (for example, configuration and log files). It regroups the produced reports under Internet File System. REPORTS ifs_repos_info - Repository Collects the Internet File System repository information. It asks for the Internet File System repository user password. For batch/cron execution, you can encode the password in the setup file using the pseudo user IFS_REPOS_USER. Log Files Inserts the log files that are found in all sub directories under $IFS_HOME as separate reports. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME IFSr2 - Collects iFS Information (iFS R2) DESCRIPTION This module collects iFS (CMSDK, Files) information (for example, configuration and log files). It regroups the produced reports under Internet File System. REPORTS ifs_repos_info - Repository Collects the Internet File System repository information. It asks for the Internet File System repository user password. For batch/cron execution, you can encode the password in the setup file using the pseudo user IFS_REPOS_USER. Log Files Inserts the log files that are found in all sub directories under $IFS_HOME as separate reports. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME INSTinfo - Defines Common Installation/Inventory Macros DESCRIPTION This persistent sub module regroups common installation/inventory macros. The following macro is available: inventory_details($file[,$flag]) This macro reports the inventory details. When the flag is set, it adds the file or directory list for the interim patches. -------------------------------------------------------------------------------- NAME library - Defines Common Macros DESCRIPTION This persistent sub module regroups macros that are common to several modules. The following macros are available: cat_file($dir,$nam,$cmd,$alt) This macro inserts a file into the current report. cat_report($dir,$nam,$pre,$cmd,$alt) This macro generates a report from a file. cat_search($nam,$opt,$pre,$cmd,$alt) This macro generates a report from a file that is searched for in a directory list. head_file($dir,$nam,$lin) This macro inserts the first lines of a file into the current report. head_report($dir,$nam,$lin,$pre) This macro inserts the first lines of a file into a report. search_files($dir,$re,$lgt[,$opt]) This macro looks in the specified directory and sub directories for all files that match the regular expression. When a number of lines is specified, only the final lines are collected. In addition, you can provide the search options as an extra argument. By default, it performs a recursive case insensitive search. sort_files($lvl,$lgt,@fil) This macro is equivalent to sort_shares(undef,$lvl,$lgt,@fil). sort_shares($shr,$lvl,$lgt,@fil) This macro uses the unsorted file list to generate links in the RDA menu structure for each directory and the files located in that directory. If the file name has the *.log structure, it limits the lines collected to the last lines. When a non-empty string is specified as a share group, all produced reports are shared automatically using that group, specifying their file name as link text. A file is collected only once per module. The following occurrences are replaced by a link to the first one. tail_file($dir,$nam,$lin) This macro inserts the last lines of a file into the current report. tail_report($dir,$nam,$lin,$pre) This macro inserts the last lines of a file into a report. -------------------------------------------------------------------------------- NAME library - Defines TLmerge Macros DESCRIPTION This persistent sub module regroups macros that are used by the alert log and trace file merge tool. -------------------------------------------------------------------------------- NAME MRGload - Collects Trace Merge Reports DESCRIPTION merge - Trace Merge This module gets reports generated by Trace Merge during the last 15 days. -------------------------------------------------------------------------------- NAME NAload - Collects Network Advisor Reports DESCRIPTION na - Network Advisor This module gets reports generated by Network Advisor during the last 15 days. -------------------------------------------------------------------------------- NAME OCMload - Collects Oracle Configuration Manager Reports DESCRIPTION This module retrieves the Oracle Configuration Manager reports. -------------------------------------------------------------------------------- NAME OCMsetup - Module for Setting up Oracle Configuration Manager DESCRIPTION This module installs and sets up Oracle Configuration Manager in the specified home and configures it for database collection as required. -------------------------------------------------------------------------------- NAME MAIL - Defines Common Oracle Collaboration Suite Macros DESCRIPTION This persistent sub module regroups macros that are common to several Oracle Collaboration Suite modules. The following macros are available: get_log($dir,$nam,$lin) This macro collects the last lines of of log file. When you do not specify a number of lines, RDA collects the whole log file. get_last_log($dir,$nam,$lin) This macro lists the directories present, lists the content of the most recent directory, and collects the log file from the most recent directory. -------------------------------------------------------------------------------- NAME ORA600load - Collects ORA-600 Reports DESCRIPTION ora600 - ORA-600 Tool This module gathers reports generated by the ORA-600 tool. -------------------------------------------------------------------------------- NAME OSaix - Sub Module Specific to the AIX Operating System DESCRIPTION This module determines the ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System Information Extracts system information such as CPU, memory, and swap information. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. patches - Operating System Patches Lists the installed operating system patches. sysdef - System/Kernel Settings Gets the system/kernel settings. system_error_log - System Error Log Collects system error log data. The system log file (/var/adm/ras/errlog) is a binary file; therefore, a textual display offers no use. This module identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE sar and svmon are not usually executable on AIX systems. If they are executable, they will run. Otherwise, a warning is issued and the data collection continues. Gets the system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Provides a disk overview in terms of free space, disk I/O, paging, and swapping. Provides a system overview in terms of processor usage, system calls, memory, semaphores, and shared memory statistics. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. udp_settings - UDP Settings Gets the UDP settings. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. CONTRIBUTION TO THE RAC MODULE When not available from the environment, it extracts ORA_CRS_HOME from the init file. cluster_status_file - Cluster Status Detects the status of the cluster and verifies that it is up and ready for RAC. Because Oracle Database 10g works with CRS, CRS may be used instead of vendor clusterware. net - Network Looks for network and interconnect settings at the operating system level. · cksum · clstat · df · echo · errpt · grep · ifconfig · instfix · iostat · ipcs · lsattr · lslpp · lsof · mount · netstat · nm · no · nslookup · ntpq · oslevel · ping · ps · pstat · sar · sort · svmon · swap · tail · traceroute · uptime · vmstat · who -------------------------------------------------------------------------------- NAME OSdarwin - Sub Module Specific to the Mac OS/Darwin Operating System DESCRIPTION This module determines the ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version. system - System Information Extracts system information such as CPU and memory information. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. sysdef - System/Kernel Settings Gets the system/kernel settings. system_error_log - System Error Log Collects system error log data. Identifies useful platform-related links (not implemented). CONTRIBUTION TO THE PERF MODULE Gets the system uptime. Get a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk I/O, and paging. Get a system overview in terms of CPU usage, top processes, and virtual memory statistics. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. udp_settings - UDP Settings Gets the UDP settings. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. OPERATING SYSTEM COMMANDS USED The main operating system commands used in the data collection include the following: · cksum · df · dmesg · echo · grep · ifconfig · iostat · ipcs · lsof · mount · netstat · nm · nslookup · ntpq · ping · ps · pstat · sar · sort · sysctl · system_profiler · tail · top · traceroute · uptime · vm_stat · who -------------------------------------------------------------------------------- NAME OShpux - Sub Module Specific to the HP-UX Operating System DESCRIPTION This module determines the HP-UX version and the ps command format. CONTRIBUTION TO THE INI MODULE Setting for UNIX95 must be in place to enable the use of ps -o. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System Information Extracts system information such as CPU and memory information. Because this information requires the use of the cstm command, it is available only when the OS module is collected. Otherwise, only the number of processors is retrieved. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. This is subject to the availability of the cstm command (cf. licensing aspects). disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. patches - Operating System Patches Lists the operating system patches installed. Release 11.0 uses show_patches to show revisions, while 10.20 uses swlist. sysdef - System/Kernel Settings Gets the system/kernel settings. This is subject to the availability of the cstm command (cf. licensing aspects). system_error_log - System Error Log Collects system error log data. Identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE Gets the system uptime. Get a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk IO, and swapping. Gets a system overview in terms of CPU usage, top processes, system calls, memory, messages, and semaphores statistics. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. udp_settings - UDP Settings Gets the UDP settings. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. CONTRIBUTION TO THE RAC MODULE When not available from the environment, it extracts ORA_CRS_HOME from the init file. cluster_status_file - Cluster Status Detects the status of the cluster and verifies that it is up and ready for RAC. Because Oracle Database 10g works with CRS, CRS may be used instead of vendor clusterware. net - Network Looks for network and interconnect settings at the operating system level. · cksum · cmviewcl · cstm (with license availability limitations) · cut · df · dmesg · echo · getconf · grep · ioscan · iostat · ipcs · kctune (on HP-UX 11.*) · kmtune (on HP-UX 11.*) · lanscan · lsof · mount · ndd (on HP-UX 11.*) · netstat · nettune (on HP-UX 10.*) · nm · nslookup · ntpq · ping · ps · sar · show_patches (on HP-UX 11.*) · sort · swapinfo · swlist (on HP-UX 10.*) · sysdef (on HP-UX 10.*) · tail · top · traceroute · uptime · vmstat · who · xargs -------------------------------------------------------------------------------- NAME OSlinux - Sub Module Specific to the Linux Operating System DESCRIPTION This module determines the Linux flavor and ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System Information Extracts the system information such as CPU, memory, and swap information. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. services - Services Displays information about system services. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. sysdef - System/Kernel Settings Gets the system/kernel settings. system_error_log - System Error Log Collects system error log data. linux_release - Linux Release Information There is a potential problem of more than one file being collected. Therefore, instead of determining the exact platform, it gathers all files. misc_linux_info - Miscellaneous Linux Information Gets the data for OAP. libc - Linux GNU Libc Finds the Linux libc version. The GNU C Library prints its version when it is directly called. Linux distributions have different ideas about the exact file name of the C Library, so RDA tests everything starting with libc.so, even if that means returning duplicate information. ssh_daemon - SSH Daemon Configuration Displays SSH daemon configuration information when RDA is executed with super user privilege. Identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE Gets the system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk I/O, virtual memory, paging, and swapping. Gets a system overview in terms of processor usage, top processes, and memory. Lists open files. When requested, collects latest sar files. CONTRIBUTION TO THE NET MODULE Determines the ping and ps command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. The data is located in the /proc/sys/net/ipv4/tcp* files. Gets the list of files, then prints the contents of the files. udp_settings - UDP Settings Gets the UDP settings. The data is located in the /proc/sys/net/core/*mem* files. Gets the list of files, then prints the contents of the files. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. CONTRIBUTION TO THE RAC MODULE When not available from the environment, it extracts ORA_CRS_HOME from the init file. cluster_status_file - Cluster Status Detects the status of the cluster and verifies that it is up and ready for RAC. Because Oracle Database 10g works with CRS, CRS may be used instead of vendor clusterware. net - Network Looks for network and interconnect settings at the operating system level. OPERATING SYSTEM COMMANDS USED The main operating system commands used in the data collection include the following: · chkconfig · cksum · df · dmesg · echo · free · getconf · grep · ifconfig · iostat · ipcs · lsmod · lsof · lspci · modinfo · mount · mpstat · netstat · nm · nslookup · ntpq · ping · ps · pstree · rpm · sar · service · sort · sysctl · swapon · tail · top · traceroute · uptime · vmstat · who -------------------------------------------------------------------------------- NAME OSosf - Sub Module Specific to the OSF Operating System DESCRIPTION This module determines the ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System Information Extracts the system information such as CPU, memory, and swap information. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. patches - Operating System Patches Lists the operating system patches installed. patchkit - Operating System Patchkit Gets the patchkit information. sysdef - System/Kernel Settings Gets the system/kernel settings. system_error_log - System Error Log Collects system error log data. Identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE Gets the system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk I/O, paging, and swapping. Gets a system overview in terms of CPU usage. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. udp_settings - UDP Settings Gets the UDP settings. UDP information on Tru64 requires three different commands to be executed. Two commands are for clusters only and are skipped if the clusters have not been identified yet. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. CONTRIBUTION TO THE RAC MODULE When not available from the environment, it extracts ORA_CRS_HOME from the init file. cluster_status_file - Cluster Status Detects the status of the cluster and verifies that it is up and ready for RAC. Because Oracle Database 10g works with CRS, CRS may be used instead of vendor clusterware. net - Network Looks for network and interconnect settings at the operating system level. · cksum · clu_get_info · df · dupatch · echo · grep · ifconfig · iostat · ipcs · lsof · mount · netstat · nm · nslookup · ntpq · ping · ps · pset_info · psrinfo · sar · setld · sort · swap · swapon · sysconfig · traceroute · uerf · uptime · vmstat · who -------------------------------------------------------------------------------- NAME OSptx - Sub Module Specific to the Dynix/Ptx Operating System DESCRIPTION This module determines the ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System Information Extracts the system information such as CPU, and memory. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. patches - Operating System Patches Lists the operating system patches installed. sysdef - System/Kernel Settings Collects system/kernel settings. system_error_log - System Error Log Collects system error log data. Identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE Gets the system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk I/O, paging, and swapping. Gets a system overview in terms of CPU usage, top processes, system calls, memory, message, and semaphore statistics. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. udp_settings - UDP Settings Gets the UDP settings. Because there is no known method of performing UDP on Sequent, this is skipped on Sequent systems. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. · cksum · df · echo · grep · ifconfig · ipcs · ktmesg · mount · netstat · nm · nslookup · ntpq · ping · pkginfo · ps · sar · showcfg · showquads · sort · swap · sysdef · tail · top · traceroute · uptime · who -------------------------------------------------------------------------------- NAME OSsunos - Sub Module Specific to the Solaris Operating System DESCRIPTION This module determines the Solaris version and the ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System information Extracts the system information such as CPU, memory, and swap information. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. ism_info - Intimate Shared Memory Gets Intimate Shared Memory (ISM) usage. Version 2.8 of Solaris identifies ISM attachments correctly. disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. projects - Projects List all projects and reports their dynamic settings. Only projects with settings are reported in the second section. (Applies to Solaris 2.10 and later only) zones - Zones Gets the zone information. (Applies to Solaris 2.10 and later only) ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. packages - Operating System Packages Lists all operating system packages. patches - Operating System Patches Lists the operating system patches installed. Some Sun patches have long requirement lists, which cause awk to throw "too many fields" errors. RDA extracts data from the first 7 fields, thus limiting the output from showrev to 200 bytes, which prevents these errors. sysdef - System/Kernel Settings Gets the system/kernel settings. system_error_log - System Error Log Collects system error log data. Identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE Gets the system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk I/O, disk errors, paging, and swapping. Gets a system overview in terms of CPU usage, top processes, system calls, memory, message, and semaphore statistics. CONTRIBUTION TO THE NET MODULE Determines the ping and ps command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings. udp_settings - UDP Settings Gets the UDP settings. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. CONTRIBUTION TO THE RAC MODULE When not available from the environment, it extracts ORA_CRS_HOME from the init file. cluster_status_file - Cluster Status Detects the status of the cluster and verifies that it is up and ready for RAC. Because Oracle Database 10g works with CRS, CRS may be used instead of vendor clusterware. net - Network Looks for network and interconnect settings at the operating system level. OPERATING SYSTEM COMMANDS USED The main operating system commands used in the data collection include the following: · cksum · df · dmesg · echo · grep · ifconfig · iostat · ipcs · isainfo · lsof · mount · mpstat · netstat · nm · nslookup · ntpq · ping · pkginfo · prctl · projects · prtconf · ps · ps (/usr/ucb/ps) · psrinfo · sar · showrev · sort · swap · sysdef · tail · top · traceroute · uptime · vmstat · who · zoneadm -------------------------------------------------------------------------------- NAME OSunix - Sub Module Specific to other UNIX Operating Systems DESCRIPTION This module determines the ps command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version. system - System Information Extracts the system information. Not implemented because required commands are platform-specific. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information (not implemented). memory_info - Memory Gets information about the physical memory (not implemented). disk_info - Disk Drives Gets information about the disks. ipc_info - Kernel Tables and IPC Gets the kernel tables and IPC information. packages - Operating System Packages Lists all operating system packages (not implemented) sysdef - System/Kernel Settings Gets the system/kernel settings (not implemented). system_error_log - System Error Log Collects system error log data. Identifies useful platform-related links (not implemented). CONTRIBUTION TO THE PERF MODULE Gets system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space. Gets a system overview in terms of virtual memory. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. tcpip_settings - TCP/IP Settings Gets the TCP/IP settings (not implemented). udp_settings - UDP Settings Gets the UDP settings (not implemented). CONTRIBUTION TO THE DEV MODULE Sets up shared library path for Oracle Forms and Reports. -------------------------------------------------------------------------------- NAME OSvms - Sub Module Specific to the VMS Operating System DESCRIPTION This module determines the 'ps' command format. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. system - System Information Extracts the system information such as CPU, memory, and swap information. CONTRIBUTION TO THE OS MODULE cpu_info - CPUs Gets CPU information. memory_info - Memory Gets information about the physical memory. disk_info - Disk Drives Gets information about the disks. ntpstatus - NTP Status Collects NTP status when NTP is running and accessible. patches - Operating System Patches Lists the operating system patches installed. sysdef - System/Kernel Settings Gets the system/kernel settings. system_error_log - System Error Log Collects system error log data. cluster - Cluster Collects VMS cluster details. Identifies useful platform-related links. CONTRIBUTION TO THE PERF MODULE Gets system uptime. Gets a process overview in terms of running databases, users logged on, and top CPU users. Gets a disk overview in terms of free space, disk I/O, queue length, and paging files. Gets a memory overview in terms of paging and resources. CONTRIBUTION TO THE NET MODULE Determines the 'ping' command format. ifconfig - Interface Configuration Gets the network interface configuration and lists TCP/IP hosts. tcpip_settings - Local TCP/IP Settings Gets the local TCP/IP settings. cluster_settings - Cluster Settings Gets the cluster settings. beqstatus - Bequeath Listener Gets Bequeath listener status and process. vmsmbx - VMS Mailboxes Lists known TCP/IP hosts. CONTRIBUTION TO THE DEV MODULE Sets up the shared library path for Oracle Forms and Reports. OPERATING SYSTEM COMMANDS USED The main operating system commands used in the data collection include the following: · dir · mc · monitor · pipe · product · show · tcpip · type · write -------------------------------------------------------------------------------- NAME OSwin32 - Sub Module Specific to the Windows Operating System DESCRIPTION This module exports Windows version registry settings. CONTRIBUTION TO THE INI MODULE Nothing required yet. CONTRIBUTION TO THE END MODULE report - Report Settings Determines the operating system version and its bit size. Also identifies the Windows system directory and the user domain. system - System Information Gets the system information. It first attempts to use systeminfo, and when that is not available, it uses winmsd on NT, and msinfo32 otherwise. CONTRIBUTION TO THE OS MODULE sys_config - Machine Configuration Displays the configuration information on NT. cpu_info - CPUs Displays the CPU information on W2000, XP, and W2003. memory_info - Memory Displays the memory configuration on W2000, XP, and W2003. display_info - Display Displays the display configuration on W2000, XP, and W2003. disk_info - Disk Drives Displays the disk drive configuration on W2000, XP, and W2003. protocol - Protocol Displays the protocol information on W2000, XP, and W2003. services - Services Displays the defined services on W2000, XP, and W2003. wintime - Windows Time Service Collects Windows time service information on W2000, XP, and W2003. drivers - Drivers Displays the driver information on W2000, XP, and W2003. odbc_info - ODBC Displays the ODBC driver information on W2000, XP, and W2003. appevtlog - Application Event Log Displays the application event log information. For 64-bit systems, RDA collects this information only when it can access the event log file. secevtlog - Security Event Log Displays the security event log information. For 64-bit systems, RDA collects this information only when it can access the event log file. sysevtlog - System Event Log Displays the system event log information. For 64-bit systems, RDA collects this information only when it can access the event log file. firewall - Firewall Collects the firewall settings. mode_info - Mode Collects the modes. For 64-bit systems, RDA collects this information only when it can access mode.com. misc_win_info - Miscellaneous Windows Information Collects the boot.ini file and the registry key value from HKLM\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows. CONTRIBUTION TO THE PERF MODULE overview - Overview Under cygwin, it indicates the system uptime. Displays an overview of started services. Lists the running databases. CONTRIBUTION TO THE NET MODULE Determines the ping command format. ifconfig - Interface Configuration Gets the network interface configuration. -------------------------------------------------------------------------------- NAME OSWload - Archives and Collects OSWatcher Files DESCRIPTION osw - OSWatcher When available, this module archives OSWatcher files and collects the resulting zip file. -------------------------------------------------------------------------------- NAME OWBinfo - Collects Generic Oracle Warehouse Builder Information DESCRIPTION This module collects generic Oracle Warehouse Builder-related information generic - Generic Information Gathers generic information. -------------------------------------------------------------------------------- NAME OWBr10g - Collects Oracle Warehouse Builder Information (9.2, 10.1, or 10.2) DESCRIPTION This module collects Oracle Warehouse Builder-related information (9.2, 10.1, or 10.2). report10g - Repository Information (9.2, 10.1, or 10.2) Gathers release-related information. -------------------------------------------------------------------------------- NAME OWBr11g - Collects Oracle Warehouse Builder Information (11g) DESCRIPTION This module collects Oracle Warehouse Builder-related information (11g). report11g - Repository Information (11g) Gathers release-related information. -------------------------------------------------------------------------------- NAME PDAinfo - Collects Generic Portal Information DESCRIPTION This module collects generic Portal information. rep_info - Portal Repository Information Collects the repository information from the Portal database. Run PDA in advanced mode for a detailed report collection. users - Portal User Information Gathers the list of Portal users from WWSEC_Person$. portal_status - Portal Tier HTTP Status Gathers the HTTP status of URLs from Portal tier. infra_status - Infrastructure HTTP Status Gathers the HTTP status of URLs from Infrastructure. oiddiag - OID Diagnostics Gathers the OID connection information. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME PDAlog - Collects Portal Configuration and Log Information DESCRIPTION This module collects Portal configuration and log-related information. Performance Analysis Provides a summary of the performance information logged by mod_plsql. It collects the information from the latest Apache error file. For the 10.1.4 version, it captures information from all the application.log files. Configuration Files Gathers Portal-related configuration files. Log Files Gathers Portal-related log files. OC4J_Portal Files Gathers OC4J_Portal configuration and log files. SEE ALSO See also IAS.def, library.def, PDAperf.def. -------------------------------------------------------------------------------- NAME PDAperf - Collects Portal Performance Information DESCRIPTION This module collects Portal performance-related information. Performance Analysis Provides a summary of the performance information logged by mod_plsql. -------------------------------------------------------------------------------- NAME PRSFr73 - Collect Information on Portal Software 7.0, 7.2 or 7.3 DESCRIPTION This module collects information on Portal or integRate pipeline-based systems. PORTAL BASED SYSTEM The following reports can be generated and are regrouped under Portal System: pin_log - Collection Log Provides the collection details. Pin and log files Collects all log and pinlog files of all components and all applications. PIPELINE BASED SYSTEM The following reports can be generated and are regrouped under Pipeline Manager: ifw_log - Collection Log Provides the collection details. Registry, description, log and trace files. Reads the specified registry files and collects information such as description, log, and trace files for each of the registry files. It captures the pipeline information also. SEE ALSO See also S380PRSF.def. -------------------------------------------------------------------------------- NAME RACdiag - Runs the Cluster Diagnostic Scripts in the Database DESCRIPTION This module runs the cluster diagnostic scripts in the database and collects the output. Gets a first hanganalyze and systemstate dump. This is only performed for databases associated with the current Oracle home. Collects the diagnostic information from the database. Retrieves hanganalyze and systemstate dumps. This is only performed for databases associated with the current Oracle home. Collects related trace files. This is only performed for databases associated with the current Oracle home. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME RACsetup - Gathers Setup Information for Remote Data Collection in a Cluster DESCRIPTION This module supports the following setup and configuration actions: setup Gets the list of all nodes belonging to a cluster, gathers the related setup information (such as Oracle home and SID), and generates the corresponding setup files. When you specify the -f option, it also resets the default remote commands and the external collections are disabled on the collecting node. disable Disables the remote collection. This is only performed for nodes that are executing a step before the post treatment or the report package transfer. When no nodes are specified and the force option is specified, all nodes are considered. edit Edits one or more remote node initial settings. These modifications are provided as a comma separated list of key/value pairs and no settings are created. If no nodes are specified and the force option is specified, all nodes are considered. list Lists the nodes and the related Oracle SIDs. For the remote nodes, a command is executed to check its accessibility. restart Restarts the remote node collection from the beginning. This action is only performed if the node step has been defined already. When no nodes are specified and the force option is specified, all nodes are restarted. retry Tries to execute the last step of remote data collections again and this is only performed for nodes with errors. If no nodes are specified and the force option is specified, all nodes are restarted. set_dft, set_remsh, set_rsh, set_ssh, set_ssh0 Specifies which commands to use for remote operations for the specified nodes. When no nodes are specified and the force option is specified, all nodes are considered. start_daemon Starts a background collection on the specified nodes. When no nodes are specified and the force option is specified, all nodes are considered. stop_daemon Stops the background collection on the specified nodes. When no nodes are specified and the force option is specified, all nodes are considered. suspend Suspends the remote collection by putting the current step in an error state. This action is only performed for nodes where the collection is not completed. When no nodes are specified and the force option is specified, all nodes are considered. You can enable the remote collection again by using a retry command. -------------------------------------------------------------------------------- NAME S000INI - Performs Data Collection Initialization DESCRIPTION This module does the following: Performs operating system specific initialization. When required for batch execution (for example, by cron jobs), defines login information to run data collection. Determines if output files can be produced. Determines if a database connection can be made. RDA performs this test only when the S200DB module has been configured. When a problem is detected, all SQL requests are disabled, but the other data collections are still performed. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME S010CFG - Collects Key Configuration Information DESCRIPTION This module performs the gathering of key configuration information for the RDA process. The following reports can be generated and are regrouped in Overview: report - Report Settings Produces an overview of the main current settings, as well as some statistics about the SQL statement executions. This report contains basic runtime information only. You can find all gathered data by using the links in the index frame. The END module generates the report itself. system - System Information Produces an overview of key system configuration information (for example, CPUs and memory). The END module generates the report itself. database - Database Information When the database is installed, it gets the product versions and determines which version of the database is installed. Next, it gets additional information about the database from V$Database, V$Instance. Finally, it executes a tnsping and collects connection characteristics. The tnsping command execution is limited to 30 seconds. homes - Oracle Home List Lists Oracle homes from central inventory. oh_inv - Oracle Home Inventory Produces a detailed inventory report based on the Oracle Home inventory information. as_inv - Application Server Inventory In Oracle Application context, it produces a detailed inventory report based on the Application Server inventory information. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32, S999END, DBinfo.def, INSTinfo.def. -------------------------------------------------------------------------------- NAME S020SMPL - Provides RDA Sampling Overview DESCRIPTION This module provides an overview of the available RDA samples. -------------------------------------------------------------------------------- NAME S090OCM - Interacts with the Oracle Configuration Manager DESCRIPTION This module executes Oracle Configuration Manager to collect configuration data when possible. -------------------------------------------------------------------------------- NAME S100OS - Collects the Operating System Information DESCRIPTION This module performs operating system information gathering for the RDA process. The following reports can be generated and are regrouped under Operating System Setup: report - Report Settings Produces an overview of the main current settings, as well as some statistics about the SQL statement executions. This report contains basic runtime information only. You can find all gathered data by using the links in the index frame. The END module generates the report itself. system - System Information Produces an overview of key system configuration information (for example, CPUs and memory). The END module generates the report itself. It reports on details of the machine and operating system information (platform-specific code). nls_env - NLS Environment Information Collects NLS information. java_version - Java Version Gets the Java Version. etc_conf - *.conf Files in /etc Gets *.conf files in /etc. tracing - Tracing Tools Identifies the availability of tracing tools. Adds useful platform-related links in the index. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME S105PROF - Collects the User Profile DESCRIPTION This module collects the configuration of the user profile. The following reports can be generated and are regrouped under User Profile: env - Environment Variables Lists defined environment variables. FOR VMS SYSTEMS profiles - Profile settings Collects both system and user login scripts and the Oracle environment settings. user - User Information Reports user information. FOR OTHER SYSTEMS ulimit - Ulimit Reports user limits. umask - Umask Reports the user file creation mode mask. profiles - Hidden Files in HOME Lists hidden files in $HOME. Handles the hidden files of interest that were found. Handles the profile files of interest that were found. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S110PERF - Collects Performance Information DESCRIPTION This module performs the operating system and database performance data gathering for the RDA process. The following reports can be generated and are regrouped under Performance: overview - Overview Gets a performance overview (platform-specific code). top_sql - Top SQL Gets session/status/latch/wait-event information. Gets the top 10 SQL statements in the SQL area. lock_data - Locking Information Gathers locking information. latch_data - Latch Information Gathers latch information including latch holder. autostats - Automatic Gathering Statistics Checks if Automatic Gathering Statistics is enabled. cbo_trace - Cost Based Optimizer Gets the cost based optimizer statistics for a dummy SQL. spack_report - Statspack Report Generates the Statspack report. addm_report - ADDM Report Generates the ADDM report. awr_report - AWR Report Generates the AWR report. ash_report - ASH Report Generates the Active Session History report. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSwin32, OSwin32. -------------------------------------------------------------------------------- NAME S120NET - Collects Network Information DESCRIPTION This module collects network information. The following reports can be generated and are regrouped under Network: ifconfig - Interface Configuration Gets the network interface configuration (platform-specific code). tcpip_settings - TCP/IP Settings Gets the TCP/IP settings (platform-specific code). udp_settings - UDP Settings Gets the UDP settings (platform-specific code). netperf - Network Performance Performs ping tests when specified in the setup file. Collects connection information and statistics from netstat. Lists declared ports. etc_files - Key /etc Files Extracts the top 500 lines of /etc/hosts. Gets /etc/group, /etc/nodename, /etc/nsswitch.conf, /etc/networks. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME S122ONET - Collects Oracle Net Information DESCRIPTION This module collects Oracle Net information. The following reports can be generated and are regrouped under Oracle Net: adapters - Adapters Output Executes the $ORACLE_HOME/bin/adapters command. Gets the Oracle Net (formerly called SQL*Net) configuration information. Some of the Oracle Net files can reside in multiple well-known locations. Captures the Oracle Names configuration. Retrieves the Heterogeneous Services configuration and log files. sqlnet_log - sqlnet.log Extracts the last 1000 lines of $ORACLE_HOME/network/log/sqlnet.log. It also also searches for sqlnet.log in other usual locations for Oracle database 11g and later. lstatus - Listener Status and Services It is possible that more than one listener can be started with the same name using a different Oracle home. On UNIX, because the listeners cannot be queried individually using the lsnrctl that started them, it removes duplicate listener names to query the status of each one once only. On Windows, the listener list is extracted from the listener.ora file. lsnrctl status can hang, causing the script to hang. To prevent this, the request is limited to 30 seconds when alarm is supported in the Perl version. Passwords found in the listener.ora file are used. It analyzes the log file and collect existing trace files. cman - Connection Manager Shows the connection manager services and status. netenv - Network Environment Checks the setting of TNS_ADMIN and lists .ora files from well-known directories. dynamic_dep - Dynamic Dependencies Lists the dynamic dependencies of executable files or shared libraries. SEE ALSO See also library.def, OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME S125GTW - Collects Transparent/Procedural Gateway Information DESCRIPTION This module collects Transparent/Procedural Gateway information (for example, initialization, trace, and log files) The following reports can be generated and are regrouped under Gateways: Gateway Information Collects the initialization files (that is, the *.map, *.ora *.sh files from the admin directory) and the last lines of the 5 most recent trace and log files for the following: · Transparent gateway for DRDA · Transparent gateway for Informix · Transparent gateway for Ingres · Transparent gateway for Microsoft SQL Server · Transparent gateway for Sybase · Transparent gateway for Teradata · Procedural gateway for APPC · Procedural gateway for IBM MQ Series Depending on the operating system, only a subset of the gateways will be captured. dblinks - Database Links When the database is installed, it lists the database links that are defined. No passwords are collected. not_found - Not found Used as a warning when transparent or procedural gateway or database links information is found. -------------------------------------------------------------------------------- NAME S130INST - Collects Oracle Installation Information DESCRIPTION This module collects Oracle installation information. The following reports can be generated and are regrouped under Oracle Installation: registry - Registry Settings On Windows, it exports the Oracle registry settings. oratab - Oratab On UNIX, it reports oratab file content. oracle_home - Oracle Home Files Reports the content of key ORACLE_HOME directories. logicals - VMS Logicals On VMS, it reports the ORA*, NLS_*, *PQL* logicals and the database logical name tables. identifiers - VMS Identifiers On VMS, it reports the ORA*, NLS_*, *PQL* logicals and the database logical name tables. orainst_loc - oraInst.loc File On UNIX, it reads the oraInst.loc file to determine the directory where the inventory is stored. The installActions.log files should be in a logs directory directly underneath this. If the oraInst.loc file does not exist in any of three known possible locations, then a message is displayed informing you that the inventory was not found or else this is a pre-Oracle 8i installation. On Windows, the inventory directory is retrieved from the registry key HKLM\Software\Oracle. inventory_xml - inventory.xml File Collects the inventory.xml file from the inventory directory. comps_xml - comps.xml File Collects the comps.xml file from the inventory directory. orainventory_logdir - Inventory Log Directory Explores the inventory directory. orainventory_files - Inventory Log Files Reports the Oracle Inventory log files and the related error and out files. Only accessible files with some content are collected. oui_loc[n] - Oracle Installer Location When the oui.loc file is found, it indicates the Oracle Universal Installer location. install_log[n] - Install.log Looks for install.log in the inventory directory. homes[n] - Oracle Home List Lists Oracle homes from central inventory. oh_inv[n] - Oracle Home Inventory Produces a detailed inventory report based on the Oracle Home inventory information. make_report - Last Make Log Looks for install.log and make.log in the Oracle home. rdbms_patches - RDBMS Patches On VMS, it gets the list of RDBMS patches. opatch_detail - Current Oracle Home Produces a detailed inventory report. Determines if opatch.pl exists in the OPATCH_DIR. If it does not exist, the possible reasons may be as follows: · The directory specified in the setup is incorrect. · Opatch is not valid, that is, Oracle Server is pre-Oracle 9i R2. opatch_all - All Oracle Homes When OPatch is available, it gives an overview of all Oracle homes. oradim_log - Oradim Log File Reports the contents of the oradim.log file. oracle_install - Oracle Home Installation Files Lists the content of the Oracle home installation directories and collects the recent related files. SEE ALSO See also library. -------------------------------------------------------------------------------- NAME S140OVM - Collects Oracle VM Server Information DESCRIPTION This module collects information about Oracle VM Server. The following reports can be generated and are regrouped in Oracle VM Server: xm_list - xm list Gathers xm list output. xenstore - Xenstore Information Xenstore is an information storage space (centralised configuration database) that is shared between Oracle VM domains. RDA collects this information using the xenstore-list and xenstore-read commands. Configuration Files Gathers configuration files in the following directory structure: · /etc/xen Log Files Gathers log files in the following directory structure: · /var/log/xen SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S142OVMM - Collects Oracle VM Manager Information DESCRIPTION This module collects information about Oracle VM Manager. It asks for the Oracle VM Manager repository user password. For batch/cron execution, you can encode the password in the setup file using the pseudo user OVMM_REPOS_USER. The following reports can be generated and are regrouped in Oracle VM Manager: no_access - No Access Reports database access issue. This module requires a database connection for collecting the information. dbinfo - Database Information Gets the version and edition of the database tableinfo - Table Information Gathers the Oracle VM Manager table information. stat_info - Statistics Gathers the Oracle VM Manager OVS_STATISTIC table information for the last days. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S200DB - Controls RDBMS Data Collection DESCRIPTION This module defines common settings for all database modules. SEE ALSO See also S201DBA.def, S204LOG.def, S205BR.def. -------------------------------------------------------------------------------- NAME S201DBA - Collects RDBMS Information DESCRIPTION This module collects the basic RDBMS-related diagnostic information. The following reports can be generated and are regrouped under RDBMS: versions - Product Versions Gets product versions and determines which version of the database is installed. init_ora - INIT.ORA Determines if spfile is in use by connecting to the database and looking up the spfile parameter. If a value is found, then RDA does not search INIT.ORA. A select for v$spparameter is executed to determine whether to skip the search for INIT.ORA. vparameters - Database Parameters Gets V$Parameter information. vspparameters - Database SPFile Parameters Gets V$SPParameter information. (Spfiles are available only in Oracle 9i and later) voption - Database Options Gets V$Option information. dba_registry - Database Registry Gets DBA_Registry information (Oracle 9i and later). app_registry - Application Registry Gets application registry information (Oracle 9i and later). sga_info - SGA Information Gets SGA information. mts - Multi-Threaded Server / Shared Server Collects multi-threaded server (Oracle 8i) or shared server (Oracle 9i and later) information. ses_procs - Sessions and Processes Lists sessions and processes. vlicense - V$License Information Gets V$License information. vcompatibility - V$Compatibility Information Gets V$Compatibility information. nls_parms - NLS Information Gets NLS Parameters. Timezone did not exist until Oracle version 8.1.7. vfeatureusage - Feature Usage Statistics Gets DBA_Feature_Usage_Statistics information. (Only available for Oracle Database 10g and later) vfeatureinfo - Feature Information Collects rows that have feature information from DBA_Feature_Usage_Statistics. (Only available for Oracle Database 10g and later) vHWM_Statistic - HighWaterMark Statistics Gets DBA_Highwater_Mark_Statistics information. (Only available for Oracle Database 10g and later) CPU_Statistic - CPU Usage Statistics Gets DBA_CPU_Usage_Statistics information. (Only available for Oracle Database 10g R2 and later) jvm_info - Java Information Gets JVM information. (JVM information available for Oracle 8i and later only) vcontrolfile - Control File Information Gets V$ControlFile information. log_info - Log Information Gets V$Logfile and V$Log information. rollback_info - Rollback Information / undo_info - Undo Information Gets rollback information. database_properties - Database Properties Gets Database Properties. (Only in Oracle 9i and later) vsystem_event - V$System_Event Gets V$System_Event information. vresource_limit - V$Resource_Limit Gets V$Resource_Limit information. vsession_wait - V$Session_Wait Gets V$Session_Wait information. latch_info - Latch Information Gets V$Latch and V$LatchHolder information. tablespace - Tablespaces Gets tablespace information. datafile - Database Files Gets data file information. replication - Replication Information Gets Replication data. jobs - DBA Jobs Information Gets DBA_Jobs information. security - Auditing and Password Information Gets database data for security/passwords/auditing. invalids - Invalid Objects Gets invalid objects. all_errors - All Errors Gets DBA_Errors information. security_files - Security Related Directory Listings and File Contents Lists the data for O/S authentication and password files. It is performed only for databases associated with the current Oracle home. spatial - Spatial Information Gets spatial information (only available for Oracle 8i and later). aq_data - Advanced Queuing Information Collects Advanced Queuing information. AQ is available in 8.0 and later. It can be manually installed in 8.0 and 8i, and is automatically installed in Oracle 9i. For the manual installations, a quick check is performed on a predetermined item to see if the product is installed. If it is, then data is gathered; if not, then a message is displayed to indicate that AQ is not installed. mgw_files_data - Messaging Gateway Files Data First, RDA determines if and what version of the product is installed. Gateway is new to Oracle 9i and is manually setup. Because it is a manual setup, RDA performs a quick check for the MGW_ADMINISTRATOR_ROLE role to see if the product is installed. When the role is found, it gets Message Gateway-related files. mgw_db_data - Messaging Gateway Database Data Gets next Message Gateway database information. partition_data - Partitioned Object Data Collects partitioning data. Partitioning is a new option to Oracle 8. ctxsys - CTXSYS Information Gets CTXSYS information. HCVE When requested and available, performs the pre-installation checks. SEE ALSO See also S200DB.def, DBinfo.def, TSThcve.def. -------------------------------------------------------------------------------- NAME S203DBM - Collects RDBMS Memory Information DESCRIPTION This module collects the RDBMS memory-related information. The following report can be generated and are regrouped under RDBMS Memory: no_privileges - Insufficient Privileges This module needs to be run as a SYSDBA user. respool - Reserved Pool Information Collects information about Reserved Pool (or Reserved Area) inside the Shared Pool. subpool - Number of Subpools Collects the number of subpools. spresmal - Shared Pool Reserved Minimum Allocation Collects shared pool reserved minimum allocation information. lchitrat - Library Cache Hit Ratio Collects how many times a statement needed to be parsed instead of being reused. hwm - HighWaterMark Information Collects statistics about code in the library cache. sgacomp - SGA Component Information Collects information on the auto-tuned components in the SGA and shows activity moving memory around in the SGA (Oracle 9i Release 2 and later). sgastat - Top SGA Components Collects top SGA components by size. libcache - Library Cache Information Collects overview information about the shared pool and the library cache usage (Oracle 9i Release 2 and later). SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S204LOG - Collects RDBMS Log and Trace Files DESCRIPTION This module collects the RDBMS log and trace files. This is performed only for databases associated with the current Oracle home. The following reports can be generated and are regrouped in RDBMS Log/Trace Files: alert_log - Alert.log Displays the content of the alert log. By default, it is limited to the last 30000 lines, but the number of lines can be increased to include the last start. alert_sum - Alert.log Analysis When requested, RDA analyzes the lines extracted from the alert log and produces a summary. more_alerts - Additional Alert Log Files Displays the content of the alert log specified by patterns. If the number of errors already collected is less than the maximum possible, it also includes the errors in the error reporting. last_errors - Last Errors The alert log is also scanned to retrieve the trace files associated with errors. To limit the data collection volume, only the latest trace files are collected based on their last modification date and the total volume. log_trace - Trace/Log Directory Listings Lists the contents of trace/dump directories. bdump - Recent Background Trace Files Collects the most recent trace files for each type of background process. Old files are not considered. udump - Recent User Dumps When requested, most recent user dumps can be collected. dg - Data Guard Broker Log Files Displays the Data Guard Broker-related log files. MERGE When requested, merges information from alert log and trace files. SEE ALSO See also S200DB.def, S405DG.def, DBalert.def, DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S205BR - Collects Database Backup and Recovery Information DESCRIPTION This module collects the RDBMS backup and recovery-related information. This is performed only for databases associated with the current Oracle home. The following reports can be generated and are regrouped under Backup and Recovery: dump_request - Request Dumps control files and file headers, which can be used by Recovery Advisor. dump_file - Dump File Retrieves the dump file in the user dump destination. user_dump - User Dump Destination Lists the contents of user dump destination. db - Database Information Gathers the backup/recovery information from the database. It displays data from v$datafile, v$backup, v$recover_file, v$tablespace, and v$tempfile. data_file - Datafile Information Gathers the information related to data files. ctlfil_data - Backup to File Performs the backup of the control file to a file in a binary format. ctlfil_trace - Backup to Trace Performs the backup of the control file to trace in a text format. RECOVERY MANAGER REPORTS The following reports are generated only if RMAN is used for backup and recovery. rman_versions - Versions Provides the RDBMS versions of catalog database, catalog schema, and RMAN executables. rman_info - RMAN Database Information Gathers the important RMAN-specific information from the database. debug_output - Debug Output Gathers the trace file information only if RMAN is started with the debug option. channel_tracing - Channel Tracing Gathers the trace file information if channel tracing has been enabled. Important RMAN Files Gathers the important RMAN files. catalog - RMAN Catalog Export Exports the RMAN catalog schema. SEE ALSO See also S200DB.def, DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S206RSRC - Collects Database Resource Manager Information DESCRIPTION This module collects Database Resource Manager information. The following reports can be generated and are regrouped under Resource Manager: active_plan - Active Plan and Statistics Gets the active Database Resource Manager plan and statistics. details - Active Plan Details Gets the Database Resource Manager plan, consumer groups, and directives of the current active plan. history - History Gets the Database Resource Manager-related historic information. -------------------------------------------------------------------------------- NAME S207D2PC - Collects Distributed Transaction Information DESCRIPTION This module collects information about in-doubt distributed transactions. The following report can be generated and is regrouped under Distributed Transactions: no_privileges - Insufficient Privileges This module needs to be run as a SYSDBA user. in-doubt - In-Doubt Distributed Transactions Collects information about in-doubt distributed transactions. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S208OMM - Collects Oracle Multimedia Information DESCRIPTION This module collects the Oracle Multimedia information. This module only applies to Oracle Database 11g and later. The following report can be generated and are regrouped under Oracle Multimedia: omm - Oracle Multimedia Information Collects information about Oracle Multimedia. -------------------------------------------------------------------------------- NAME S210OLAP - Collects OLAP Information DESCRIPTION This module collects OLAP-related information. The following reports can be generated and are regrouped under OLAP: not_applicable - Not Applicable The OLAP module can be executed only on Oracle 9i Release 2 or later, where OLAP option is present. no_olap - OLAP Components Checks if OLAP components are present and their status. report - OLAP Information Gathers OLAP information. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S215OES - Collects Oracle Express Server Information DESCRIPTION This module collects Oracle Express Server-related information. It executes Express SPL commands to get the patch level of Oracle Express Server and gathers files pertaining to the OES installation. Requires the Oracle Express Server password. For batch/cron execution, you can encode the password in the setup file using the pseudo user OES_DBA_USER. The following reports can be generated and are regrouped under Express Server: summary - Services Summary Gives an overview of the Oracle Express Server services. eversion - eversion Collects the related eversions. oeskey - oes.key / expressprm - express.prm Collects the basic OES-related configurations. xsdaemon - xsdaemon Extracts the last 10000 lines of xsdaemon.log. xsauth - xsauth Extracts the last 10000 lines of xsauth.log. oesevents - OESevent Extracts the last 10000 lines of all the OESEvent log files. ofainfo - OFA Determines the database versions and gets the OFA configuration files. owainfo - OWA Determines the XWDEVKIT database version and gets the OWA configuration file. dpeinfo - DPE Collects Demand Planning information. This includes, when present, the XSOOWAROAS and Single Sign-On configurations. Requires the application "system" password for Demand Planning Server. For batch/cron execution, you can encode the password in the setup file using the pseudo user DPE_DPS_SYSTEM. SEE ALSO See also library.def, OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME S220IA - Collects Intelligent Agent Information DESCRIPTION This module collects the Intelligent Agent information. This module only applies to versions earlier than Oracle Database 10g. The following reports can be generated and are regrouped under Intelligent Agent: Configuration Files Collects all files related to Intelligent Agent. Log files Collects last lines of log files. status - Intelligent Agent Status Gets the Intelligent Agent status. From Oracle 9i on, lsnrctl is no longer the interface to IA and is replaced by agentctl. There may not be a database available on this system, so Oracle cannot guarantee the version information from the database. Therefore, RDA checks to see if agentctl exists; if it exists, then it is used. Otherwise, RDA uses lsnrctl. lsnrctl status can hang, thus causing the script to hang. To prevent this, the command execution is limited to 30 seconds when alarm is supported in the Perl version. processes - dbsnmp Process Status Checks for the existence of the dbsnmp process. SEE ALSO See also library.def, OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME STC - Collects Streams Configuration Information DESCRIPTION This module collects Streams configuration-related information (for Oracle 9i Release 2 or later). The following reports can be generated and are regrouped under Streams Configuration. no_privileges - Insufficient Privileges This module needs to be run as a SYSDBA user. history - History Analyses Performs history checks. (Oracle 10g Release 2 and later) rules - Rules Analyses Performs rules checks. topology - Topology Analyses Performs topology checks. (Oracle 11g and later) wait - Wait Analyses Performs wait checks. (Oracle 10g and later) other - Other Analyses Performs additional checks. (Oracle 10g and later) apply_set - Apply Settings Collects information about Apply Settings. capture_set - Capture Settings Collects information about Capture Settings. db - Database Settings Collects information about Database Settings. prpgt_set - Propagation Settings Collects information about Propagation Settings. queue_set - Queue Settings Collects information about Queue Settings. apply_stat - Apply Statistics Collects information about Apply Statistics. apply_error - Apply Errors Collects information about Apply Errors Statistics. capture_stat - Capture Statistics Collects information about Capture Statistics. prpgt_stat - Propagation Statistics Collects information about Propagation Statistics. queue_stat - Queue Statistics Collects information about Queue Statistics. ruleset - Rules and Rule Sets Collects information about the various Rule and Rule Set Statistics. wait_events - Wait Events Collects information about Wait Events. (Oracle 9i Release 2) SEE ALSO See also S200DB.def, DBinfo.def. -------------------------------------------------------------------------------- NAME S231STM - Collects Streams Monitoring Information DESCRIPTION This module collects Streams activity information occurring within an Oracle database. The following reports can be generated and are regrouped under Streams Monitoring: no_setup - No Streams Monitor Setup All versions earlier than Oracle 9i Release 2 do not have the Streams Monitoring option. monitor - Monitor Results Monitors database streams. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S240OCS - Controls Oracle Collaboration Suite Data Collection DESCRIPTION This module defines common settings for all Oracle Collaboration Suite modules and gathers information that is common for Oracle Collaboration Suite components. The following reports can be generated and are regrouped under "Oracle Collaboration Suite": virtual - Virtual Service Gathers Virtual Service (Service to Service) information from the Oracle Collaboration Suite installation. SEE ALSO See also S241MAIL.def, S242WAC.def, S243WMC.def, S244OCAL.def, S245RTC.def, S246DSCS.def, S247WKSP.def, S248CONT.def, S249WRLS.def. -------------------------------------------------------------------------------- NAME S241MAIL - Collects Oracle Collaboration Suite Mail Information DESCRIPTION The following reports can be generated and are regrouped under Mail Server: Configuration Files For UNIX, it collects the following mail files: · /etc/mail/sendmail.cf · /etc/mail/aliases LDAP Information Performs some LDAP queries to get process information, process connection information, and the original users. Requests the orcladmin password. For batch/cron execution, you can encode the password in the setup file using the pseudo user LDAP_ORCLADMIN. Log Files For the selected processes, it lists the most recent log directories and collects the last lines of the most recent log files (10.1.2). listener_es_log - Listener_es Log Extracts the last lines of the listener_es.log file. not_found - Not found Used as a warning when none of the Oracle Collaboration Suite Mail files are found. SEE ALSO See also S240OCS.def, OCS.def, library.def. -------------------------------------------------------------------------------- NAME S242WAC - Collects Web Access Client Information DESCRIPTION The following reports can be generated and are regrouped under Web Access Client: Log Files Gets the last lines of the log files. not_found - Not found Used as a warning when none of the Web Access Client files are found. SEE ALSO See also S240OCS.def, OCS.def, library.def. -------------------------------------------------------------------------------- NAME S243WMC - Collects Webmail Client Information DESCRIPTION The following reports can be generated and are regrouped under Webmail Client: logs - Log Files Lists the most recent log directory and collects the last lines of the most recent log file. not_found - Not found Used as a warning when none of the Webmail Client files are found. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S244OCAL - Collects Oracle Calendar Information DESCRIPTION The following reports can be generated and are regrouped under Oracle Calendar: version - Calendar Server / Version Gets Oracle Calendar version. status - Calendar Server / Status Gets Oracle Calendar status. uninode_cws - Calendar Server / uninode -cws Executes uninode -cws. uninode_snc - Calendar Server / uninode -snc Executes uninode -snc. uninode_test - Calendar Server / uninode -test Executes uninode -test. Calendar Server / Parameters Collects all .ini files for the Oracle Calendar server. Calendar Server Log Files Takes a log snapshot and collects the most recent Oracle Calendar server log files. ocas_status - Calendar Application Server / Status Collects the Oracle Calendar Application server status. ocas_sys - Calendar Application Server / Overview Collects the Oracle Calendar Application server overview. Calendar Application Server / Configuration files Collects the Oracle Calendar Application server configuration files. Calendar Application Server / Log Files Collects the Oracle Calendar Application server log files. Calendar Directory Server / Configuration files Collects all .conf files for the Oracle Calendar Directory server. ocad_log - ocad.log Collects the Oracle Calendar Administration log file. not_found - Not found Used as a warning when none of the Oracle Calendar files are found. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S245RTC - Collects Real Time Communication Information DESCRIPTION The following reports can be generated and are regrouped under Real Time Communication: properties - Properties Collects the Real Time Collaboration properties. version - Version Collects the Real Time Collaboration version. instances - Instances Lists the Real Time Collaboration instances. state - State Collects the Real Time Collaboration state. components - Components Lists the Real Time Collaboration components. pids - Pids Collects the Real Time Collaboration pids. Configuration Files Collects all .conf files. Log Files Collect the log files. not_found - Not found Used as a warning when none of the Real Time Communication files are found. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S246DSCS - Collects Discussions Information DESCRIPTION The following reports can be generated and are regrouped under Discussions: Log Files Gets the last lines of the log files. not_found - Not found Used as a warning when none of the Oracle Discussions files are found. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S247WKSP - Collects Workspaces Information DESCRIPTION The following reports can be generated and are regrouped under Workspaces: Log Files Gets the last lines of the log files. not_found - Not found Used as a warning when none of the Workspaces files are found. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S248CONT - Collects Oracle Content Services Information DESCRIPTION This module collects Oracle Content Services information (for example, configuration and log files). The reports are regrouped under Oracle Content Services. REPORTS repos_info - Repository Collects the repository information such as repository version, domain properties, node, service, and server configurations. Requests for the Oracle Content Services repository user password. For batch/cron execution, you can encode the password in the setup file using the pseudo user CONTENT_REPOS_USER. Configuration and Log Files Gets configuration and log files for Content Services node. Gets configuration and log files for Content Services HTTP Node. Gets configuration and log files for Content Services Records Management Node. Gets configuration and log files for Java containers running Content Services Node, HTTP Node, and Records Management Node. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S249WRLS - Collects Wireless Information DESCRIPTION The following reports can be generated and are regrouped under Wireless: Gathering Wireless Information Finds all wireless configuration and log files. Recent archive files Lists the recent archive files and collects the last lines of the most recent file of each type. Recent status files Lists the recent status files and collects the last lines of the most recent file of each type. not_found - Not found Used as a warning when none of the Wireless files are found. SEE ALSO See also S240OCS.def, library.def. -------------------------------------------------------------------------------- NAME S250BEE - Collects Beehive Information DESCRIPTION This module collects the Beehive-related information. The following reports can be generated and are regrouped under Beehive: beectl_status - beectl status Gathers beectl status output. beectl_version - beectl version Gathers beectl and version output. opmnctl_status - opmnctl status Gathers opmnctl status information. comp_prop - Components Properties When requested, gathers all components and their properties. table_info_jms - JMS Tables When requested, gathers JMS table information using the dmstool command. table_info_jvm - JVM Table When requested, gathers JVM table information using the dmstool command. table_info_oc4j - oc4j Tables When requested, gathers oc4j table information using the dmstool command. table_info_ohs - ohs Tables When requested, gathers ohs table information using the dmstool command. table_info_opmn - opmn Tables When requested, gathers opmn table information using the dmstool command. table_info_uds - uds Tables When requested, gathers uds table information using the dmstool command. Log Files Gathers most recent log files in the following directory structures: · $ORACLE_HOME/beehive/logs · $ORACLE_HOME/clone/logs · $ORACLE_HOME/install · $ORACLE_HOME/opmn/logs SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S260OMS - Collects Oracle Management Server Information (obsolete) DESCRIPTION The EM module replaces this module. SEE ALSO See also S440EM.def. -------------------------------------------------------------------------------- NAME S290DEV - Collects Oracle Forms and Reports Information DESCRIPTION This module collects the reports and forms information from Forms/Reports 6.0.x, Forms/Reports 9.0.x, Forms/Reports 10.1.x, and Apps 11.5.x. Produced reports are regrouped under Oracle Forms/Reports. ITEMS COMMON TO BOTH REPORTS AND FORMS For Forms/Reports 9.0.x and 10.1.x, Collects all general Application Server startup scripts and Forms/Reports installation files. Toolkit files Collects the toolkit files (such as uiprint.txt, uifont.ali, and Tk2Motif.rgb). versions - Versions Reports on versions. Forms/Reports Install Logs For Forms/Reports 6.0.x, collects install logs (such as unix.prd, install.log, make.log, os.log, and sql.log) ITEMS SPECIFIC TO ORACLE REPORTS On UNIX, it lists all active Oracle Reports processes. For Reports 6.0.x, Collects standalone scripts (such as reports60.sh, reports60.csh, and reports60_server). Collects a streaming dump of reports6iconfig.txt and all the .ora and .log files from the Reports server. Determines if RWServlet.class and cgicmd.dat exist. For Reports 9.0.x and 10.1.x, Collects all general Application Server information for Oracle Reports from the Reports conf, logs and server sub directories. ITEMS SPECIFIC TO ORACLE FORMS For Forms 6.0.x, On UNIX, it lists active Oracle Forms processes. Collects Forms files (such as forms60.sh, forms60.csh, forms60_server, and fmrweb.res). Collects the Forms server files (such as formsweb.cfg, default.env, base.htm, baseie.htm, basejini.htm, Oracle Jinitiator version, and Registry.dat). For Forms 9.0.x and 10.1.x, On UNIX, it lists active Forms processes. Collects Forms files (such as fmrweb.res). Collects the Forms server files (such as Oracle Jinitiator version, and Registry.dat). Application Server Information about Forms Collects the OC4J demos. Collects Forms config, trace, and server sub directory contents. Lists Forms Java sub directory. ITEMS SPECIFIC TO APPS 11.5.X INSTALLS If this is an Applications install, it stores the appropriate environment settings and pulls startup scripts. SEE ALSO See also library.def, OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME S292APEX - Collects APEX Information DESCRIPTION This module collects APEX-related information. Configuration Files Gathers the following configuration files: · $ORACLE_HOME/Apache/modplsql/conf/marvel.conf · $ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app Database Information Gathers APEX information from all databases specified at setup. SEE ALSO See also DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S294LANG - Collects Oracle Language Information DESCRIPTION This module collects information about Oracle language products. The following reports can be generated and are regrouped in Oracle Languages: Precompiler Versions Collects Oracle precompiler versions. Library Versions For Windows, it collects Oracle OCI and precompiler library versions. appl_analysis - Application Analysis Collects application information such as bit architecture. link_analysis - Linking Information For UNIX, it collects application dynamic linking information. core_analysis - Core Dump Analysis For UNIX, it analyzes core dumps present in the application directory structure. Network Trace Files Collects the Network trace files. SEE ALSO See also library.def, COREinfo.def. -------------------------------------------------------------------------------- NAME S295MSLG - Collects Microsoft Languages Information DESCRIPTION This module collects information about Microsoft APIs and languages products. The following reports can be generated and are regrouped in Microsoft Languages: mdac_version - MDAC Version Collects Microsoft Data Access versions from the Windows registry. odbc_registry - ODBC Registry Keys Collects the basic ODBC-related configurations from the registry. ODP.NET Traces Collects an ODP.NET trace for each different Oracle homes. OLEDB Traces Collects the OLEDB trace for different Oracle homes. ORAMTS Traces Gathers the last 10 modified files from ORAMTS trace directory specified in the registry. Oracle Driver Versions Gathers the version information of Oracle drivers from all the $ORACLE_HOME/bin folders. Microsoft Product Versions Gathers the versions of various Microsoft products. odbc_trace - ODBC Trace File Gets the location of the ODBC trace file from the registry and collects it. gac_list - Global Assembly Cache Lists the files registered with Global Assembly Cache. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S298PLNC - Collects Oracle PL/SQL Native Compilation Information DESCRIPTION This module collects information about Oracle PL/SQL native compilation. The following reports can be generated and are regrouped in PL/SQL Native Compilation: Native Compilation Collects Oracle PL/SQL native compilation information. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S300IAS - Collects Web Server Information DESCRIPTION This module collects Web Server-related information through a release-specific sub module. It automatically detects OAS 11g, OAS 10g R4 (10.1.4), OAS 10g R3 (10.1.3), OAS 10g R2 (10.1.2), OAS 10g (9.0.4), 9iAS R2 (9.0.2/9.0.3), and 9iAS (1.0.2). SEE ALSO See also IASr1012, IASr1013, IASr1014, IASr10g, IASm11g, IASs11g, IASr2, IASr1. -------------------------------------------------------------------------------- NAME S301WLS - Collects Oracle WebLogic Server Information DESCRIPTION This module collects Oracle WebLogic Server-related information. The module covers Oracle WebLogic Server Release 9.x and 10.x. SEE ALSO See also WLSm, WLSs. -------------------------------------------------------------------------------- NAME S305ASBR - Collects Application Server Backup and Recovery Information. DESCRIPTION This module collects the Application Server backup and recovery-related information. The following reports can be generated and are regrouped under AS Backup/Recovery: db_info - Database Information Gathers the Application Server backup and recovery information from the database. Depending on the database version, it can collect data from V$Database, V$Recovery_File_Dest, and V$Flash_Recovery_Area_Usage. scripts - Backup Script Results Collects the backup list, instance backup list, and changed configuration files by executing backup and restore scripts. dcm_archives - DCM archives Collects the list of DCM archives. Configuration Files Collects all files from the config directory. Log Files Collects the log files. not_found - Not Found Used as a warning when no Application Server Backup Recovery information is found. -------------------------------------------------------------------------------- NAME S306ASG - Collects Application Server Guard Information DESCRIPTION This module collects the Application Server Guard-related information. The following reports can be generated and are regrouped under AS Guard: Configuration Files Collects all files from the conf directory. Log Files Collects all files from the log directory. not_found - Not Found Used as a warning when none of the Application Server Guard information is found. -------------------------------------------------------------------------------- NAME S310J2EE - Collects J2EE/OC4J Information DESCRIPTION This module collects J2EE/OC4J-related information (for example, configuration and log files). The following reports can be generated and are regrouped under J2EE/OC4J: J2EE/OC4J Gathers J2EE/OC4J Information. Determines the version of oc4j.jar, located in the $J2EE_TOP directory. Checks for the available JDK. It uses this information to execute the command that gathers the oc4j.jar version. java -jar oc4j.jar -version Finds all mime.types, policy, properties, xml, and log files in the $J2EE_TOP directory. Gathers information about all *.jar files located in the $J2EE_TOP directory. For each Jar file, the report collects file information and the output from cksum. -------------------------------------------------------------------------------- NAME S313CWT - Collects Oracle Application Server 11g Classic/WebTier Information DESCRIPTION This module collects Oracle Application Server 11g Classic/WebTier-related information for single or all Oracle instances. Oracle Application Server 11g Classic includes: · Oracle Discoverer · Oracle Forms/Reports · Oracle HTTP Server · Oracle Process Management Node · Portal Diagnostics · Oracle Web Cache Oracle Application Server 11g WebTier includes: · Oracle HTTP Server · Oracle Process Management Node · Oracle Web Cache The following reports can be generated and are regrouped under Oracle AS 11g Classic/WebTier: REPORTS ORACLE HOME COLLECTIONS error - Classic/WebTier Error Indicates that the specified Oracle home does not contain Classic/WebTier information. Install and Configuration Gathers the Oracle Application Server configuration and installation files. product_info - Classic/WebTier Product Information Gathers the product information if Classic/WebTier is installed in a separate Oracle home. Oracle Discoverer Gathers Oracle Discoverer executable and library versions. Oracle Forms/Reports Gathers Oracle Forms/Reports installation files and also collects all general Application Server information for Oracle Forms/Reports. Oracle HTTP Server Gathers Oracle HTTP server executable list and apachectl script. LDAP Gathers LDAP executable list. OPMN Gathers OPMN executable list. Portal Diagnostics Collects the repository information from the Portal database. Run PDA in advanced mode for a detailed report collection. Gathers the list of Portal users from WWSEC_Person$. Gathers the HTTP status of URLs from Portal and Infrastructure tier. Gathers the OID connection information. Oracle Web Cache Gathers Oracle Web Cache file permissions and DTD files. INSTANCES COLLECTIONS It performs the following collections on all specified instances. Oracle Discoverer Gathers Oracle Discoverer configuration and log files. It also runs the checkdiscoverer script. Oracle Forms/Reports Collects all startup scripts. Collects the toolkit files (such as uiprint.txt, uifont.ali, and Tk2Motif.rgb). Reports on versions used. Gathers Oracle Forms/Reports configuration and log files. Oracle HTTP Server Gathers Oracle HTTP server configuration and log files. It also includes a DMS dump. OPMN Gathers OPMN information using opmnctl. It collects all *.conf, *.log, and *.xml files. It also includes a DMS dump. Portal Diagnostics Provides a summary of the performance information logged by mod_plsql. Oracle Web Cache Gathers Oracle Web Cache configuration and log files. It also includes a DMS dump. SEE ALSO See also IAS.def, INSTinfo.def. -------------------------------------------------------------------------------- NAME S320IFS - Collects iFS (iFS, CMSDK, Files) Information DESCRIPTION This module collects iFS-related information (iFS, CMSDK, Files) through a release-specific sub module. SEE ALSO See also IFSr1, IFSr2. -------------------------------------------------------------------------------- NAME S325PDA - Collects Portal Diagnostics Information DESCRIPTION This module collects the Portal diagnostics-related information. The reports are regrouped under Portal Diagnostics. SEE ALSO See also PDAinfo.def,PDAlog.def. -------------------------------------------------------------------------------- NAME S326JIVE - Collects Jive Information DESCRIPTION This module collects the Jive-related diagnostic information. The following report can be generated and are regrouped under Jive: prop - jive.properties Gathers jive.properties file. start - jive_startup.xml Gathers jive_startup.xml file. user - jive_usersearch.xml Gathers jive_usersearch.xml file. Log Files Finds all files in JIVE_HOME/log directory. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S328WCI - Collects Oracle WebCenter 11g Information DESCRIPTION This module collects diagnostic information for Oracle WebCenter 11g or later. The following reports can be generated and are regrouped under Oracle WebCenter: ORACLE HOME COLLECTIONS error - WebCenter Error Indicates that the specified Oracle home does not contain Oracle WebCenter information. Install and Configuration Gathers the Oracle Application Server configuration and installation files. product_info - WebCenter Product Information Gathers the product information if Oracle WebCenter is installed in a separate Oracle home. jdk_info - JDK Information Checks for the available JDK and reports its version. jdk_libs - Java Libs Gathers information about all *.jar files located in the common directory. For each Jar file, the report collects file information and the output from cksum. SEE ALSO See also INSTinfo.def, library.def. -------------------------------------------------------------------------------- NAME S330SSO - Collects Single Sign-On Information DESCRIPTION This module collects Single Sign-On-related information. The following reports can be generated and are regrouped under Single Sign-On: overview - SSO Repository Information Gets Single Sign-On repository information from the database. sso_bin - $OH/sso/bin sso_bin - Lists the files in the sso/bin sub directory. Configuration and Log Files Finds configuration and all *.err/*.log files. OSSO Configuration Files Decrypts and collects the OSSO configuration content. ldap_bind - LDAP Bind Information Gets LDAP server information from the database and then runs ldapbind to check the connection. ssogito - Timeout Information Gets the timeout information. kerk5_conf - Kerberos Configuration Collects the Kerberos configuration. SEE ALSO See also DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S340OID - Collects Oracle Internet Directory Information DESCRIPTION This module collects Oracle Internet Directory-related information. The following reports can be generated and are regrouped under Oracle Internet Directory: oid_diag - OIDDIAG Output Displays the output of the oiddiag command. oidctl - OIDCTL Status Displays the oidctl status. process - Processes Displays the information about processes. ods_process - ODS_PROCESS Information Lists details from ods_process table. attrstore - DS_ATTRSTORE table Information Lists details from ds_attrstore table. oidmon.log Displays the last lines of the monitor log. oidldapd.log Displays the last lines of the LDAP log. oidrepld.log Displays the last lines of the replication log. $OH/ldap/odi/log Displays the contents of the files in the $ORACLE_HOME/ldap/odi/log directory. odiprop - $OH/ldap/odi/conf/odi.properties Displays the contents of the $OH/ldap/odi/conf/odi.properties file. $OH/ldap/load Displays the contents of the files in the $ORACLE_HOME/ldap/load directory. $OH/ldap/das Displays the contents of the files in the $ORACLE_HOME/ldap/das directory except for the oiddas.ear file. not_found - Not found Used as a warning when none of the Oracle Internet Directory files are found. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S342OVD - Collects Oracle Virtual Directory Information DESCRIPTION This module collects Oracle Virtual Directory-related information (for example, server, configuration, and log files). The following reports can be generated and are regrouped under Oracle Virtual Directory: Server Files Collects the following server files: · ovidserver.lax · vde.sh · vde_start.sh Configuration Files Collects configuration files from the conf directory. Log Files Collects the log files from the log directory. not_found - Not Found Used as a warning when none of the Oracle Virtual Directory files are found. -------------------------------------------------------------------------------- NAME S350WEBC - Collects Web Cache Information DESCRIPTION This module collects Web Cache information (for example, configuration, DTD, and log files). The following reports can be generated and are regrouped under Web Cache: Log files can be relocated. Because of this, RDA parses a few xml files to get their location, and then dumps them. perms - File Permissions Collects the owner and group permissions of the files used by Web Cache. not_found - Not found Used as a warning when none of the Web Cache files are found. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S360CRID - Collects Oracle Access Manager (COREid) Information DESCRIPTION This module collects Oracle Access Manager (formerly COREid) product-related information (for example, installation, configuration, and log files). The following reports can be generated and are regrouped under Oracle Access Manager Components: Policy Manager Setup Files Gathers Policy Manager (formerly Access Manager) setup files. Policy Manager Configuration Files Gathers Policy Manager configuration files. Policy Manager Log Configuration File Gathers the Policy Manager log configuration file. Policy Manager Default Log File Gathers the Policy Manager default log file. Policy Manager Database Configuration Files Gathers Policy Manager database configuration files. Access Server Setup Files Gathers Access Server setup files. Access Server Configuration Files Gathers Access Server configuration files. Access Server Log Configuration Files Gathers Access Server log configuration files. Access Server Default Log File Gathers the Access Server default log file. Access Server Database Config Files Gathers Access Server database configuration files. as_core - Access Server Core Dump Analysis Analyzes any Access Server core dumps. Identity Server Scripts Gathers Identity Server scripts for UNIX platforms. Identity Server Setup Files Gathers Identity Server setup files. Identity Server Log Configuration Files Gathers Identity Server log configuration files. Identity Server Default Log Files Gathers Identity Server default log files. Identity Server Default Audit Files Gathers Identity Server default audit files. Identity Server Configuration Files Gathers Identity Server configuration files. Identity Server Application Registry Files Gathers Identity Server application registry files. Identity Server Database Configuration Files Gathers Identity Server database configuration files. is_core - Identity Server Core Dump Analysis Analyzes any Identity Server core dump files. WebGate Configuration Files Gathers WebGate configuration files. WebGate Log Configuration File Gathers the WebGate log configuration file. WebGate Default Log File Gathers the WebGate default log file. WebPass Component Configuration Files Gathers WebPass component configuration files. WebPass Log Configuration Files Gathers WebPass log configuration files. WebPass Log Files Gathers WebPass log files. WebPass Configuration Files Gathers WebPass configuration files. SEE ALSO See also library.def, COREinfo.def. -------------------------------------------------------------------------------- NAME S362OIM - Collects Oracle Identity Manager Information DESCRIPTION This module collects information about Oracle Identity Manager. The following reports can be generated and are regrouped in Oracle Identity Manager: system - System Information Collects OIM system information from the database. users - User Information Displays the information about OIM users. users - Password Policy Information Displays the information about OIM password policies. expimp - Export/Import Information Displays the export/import information. miscellaneous - Miscellaneous Displays the miscellaneous information. OIM Configuration Files Gets OIM configuration files. Diagnostics Dashboard reports sys_info - System Information Collects Oracle Identity Manager system information. db_connect - Database Connectivity Check This test is to verify if Oracle Identity Manager is able to connect to the database or not. This test verifies the direct database connection as well as the J2EE data sources (XA and non-XA). lock_status - Account Lock Status This test is to verify if Oracle Identity Manager locks an account when there are successive multiple invalid login attempts. This test checks if a given account is locked or not. enc_key_ver - Data Encryption Key Verification This test is to verify the Data Encryption Key used for Oracle Identity Manager. The data encryption key in an Oracle Identity Manager installation should be the same as the one used to encrypt the data in the Oracle Identity Manager database. This may not be the case when an Oracle Identity Manager installation is pointed to a database schema created for a different Oracle Identity Manager installation. This can also happen when database dump from one Oracle Identity Manager installation is imported for a different Oracle Identity Manager installation without copying the corresponding key. sch_svc_sta - Scheduler Service Status This test is to verify the status of the Oracle Identity Manager Scheduler Service running on this server. rem_mgr_sta - Remote Manager Status This test reports the status of the Remote Managers that this Oracle Identity Manager installation is set up to work with. jms_msg - JMS Messaging Verification The purpose of this test is to verify that Oracle Identity Manager will be able to submit a JMS message and process it. jvm_prop - Java VM System Properties Report This test is to display all the Java VM system properties. lib_version - Libraries and Extensions Version Report This test reports the version of the Oracle Identity Manager libraries and extensions. lib_manifest - Libraries and Extensions Manifest Report This test reports the manifest information of the Oracle Identity Manager libraries and extensions. sso_diag - SSO Diagnostic Information This test provides information pertaining to SSO setup. Also, provides instructions required to set up Oracle Identity Manager to enable retrieving run-time diagnostic information related to SSO logins. -------------------------------------------------------------------------------- NAME S370SOA - Collects Oracle SOA 11g Information DESCRIPTION This module collects diagnostic information for Oracle SOA 11g or later. The following reports can be generated and are regrouped under Oracle SOA: ORACLE HOME COLLECTIONS error - SOA Error Indicates that the specified Oracle home does not contain Oracle SOA information. rep_info - Repository Information Collects the repository information from the Oracle SOA database. Install and Configuration Gathers the Oracle Application Server configuration and installation files. product_info - SOA Product Information Gathers the product information if Oracle SOA is installed in a separate Oracle home. jdk_info - JDK Information Checks for the available JDK and reports its version. jdk_libs - Java Libs Gathers information about all *.jar files located in the common directory. For each Jar file, the report collects file information and the output from cksum. BAM Gathers the Business Activity Monitoring (BAM) Information. bam_root_dir - BAM Root Directory Displays the content of the BAM root directory. BAM Configuration Files Gathers BAM-related configuration files. bam_events - BAM Events Displays the details of all the events related to BAM services from the application event log. Note: Applicable to Windows platform only. SYSMAN Gathers SYSMAN information. SEE ALSO See also DBinfo.def, INSTinfo.def, library.def. -------------------------------------------------------------------------------- NAME S371ESB - Collects Enterprise Service Bus Information DESCRIPTION This module collects the Enterprise Service Bus-related information. The following reports can be generated and are regrouped under Enterprise Service Bus: rep_info - Repository Information Collects the repository information from the Enterprise Service Bus database. Configuration Files Gathers Enterprise Service Bus-related configuration files. SEE ALSO See also DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S372OWSM - Collects Oracle Web Services Manager Information DESCRIPTION This module collects the Oracle Web Services Manager-related information. The following reports can be generated and are regrouped under Oracle Web Services Manager: rep_info - Repository Information Collects the repository information from the Oracle Web Services Manager database. Configuration Files Gathers Oracle Web Services Manager-related configuration files. Log Files Gathers Oracle Web Services Manager-related log files. SEE ALSO See also DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S373BPEL - Collects Oracle BPEL Process Manager Information DESCRIPTION This module collects the Oracle BPEL Process Manager-related information. The following reports can be generated and are regrouped under Oracle BPEL Process Manager: rep_info - Repository Information Collects the repository information from the Oracle BPEL Process Manager database. clock_chk - Clock Issue BPEL PM product requires a monotonically increasing time. RDA produces this report when it detects an occurrence of time going backwards. It performs this test only when the Perl has access to the high resolution clock. SEE ALSO See also DBinfo.def, library.def. -------------------------------------------------------------------------------- NAME S380PRSF - Collect Portal Software Information DESCRIPTION This module collects Portal Software-related information through a release-specific sub module. It automatically detects Portal Software release. SEE ALSO See also PRSFr73.def. -------------------------------------------------------------------------------- NAME S385ODI - Collects Oracle Data Integrator Information DESCRIPTION This module collects information related to Oracle Data Integrator 10.1.3.4 or later. The following reports can be generated and are regrouped under Oracle Data Integrator: master - Master Repositories Collects master repositories and technical environment. work - Work Repositories Collects work directories and execution log data. -------------------------------------------------------------------------------- NAME S378BI - Collects Oracle Business Intelligence Information DESCRIPTION This module collects the Oracle Business Intelligence-related information. The following reports can be generated and are regrouped under Oracle Business Intelligence: bi_version - Version Information Gathers version information. present_config - Presentation Server Configuration Gathers presentation server configuration information. server_config - Server Configuration Gathers server configuration information. cluster_config - Cluster Controller Configuration Gathers cluster controller configuration information. Log Files Gathers important log files. repository - Repositories Gathers repositories. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S390DSCV - Collects Information for Oracle Discoverer DESCRIPTION This module collects information for Oracle Discoverer. Produced reports are regrouped under Oracle Discoverer. check_discoverer - Discoverer Status. Runs the checkdiscoverer script. Configuration Files. Gathers configuration files. exe_versions - Executable Versions. Gathers Oracle Discoverer executable versions. lib_versions - Library Versions. Gathers Oracle Discoverer library versions. Log Files. Gathers the most recent Oracle Discoverer logs. not_found - Not found Used as a warning when no Oracle Discoverer files are found. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S391OWB - Collects Oracle Warehouse Builder Information DESCRIPTION This module collects Oracle Warehouse Builder-related information. The following reports can be generated and are regrouped under Oracle Warehouse Builder: not_applicable - Not Applicable The Oracle Warehouse Builder module can only be executed on Oracle 9i Release 2 or later. generic - Generic Information Gathers generic information. report11g - Repository Information (11g) Gathers release-related information. report10g - Repository Information (9.2, 10.1, or 10.2) Gathers release-related information. SEE ALSO See also DBinfo.def, OWBinfo.def, OWBr10g.def, OWBr11g.def. -------------------------------------------------------------------------------- NAME S392ODM - Collects Oracle Data Mining Information DESCRIPTION This module collects Oracle Data Mining-related information. The following reports can be generated and are regrouped under Oracle Data Mining: not_applicable - Not Applicable The Oracle Data Mining module can only be executed on Oracle Database 10g Release 1 or later. report - Oracle Data Mining Gathers Oracle Data Mining information. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S400RACD - Performs a Database Hang Analysis DESCRIPTION This module performs a database hang analysis. The following reports can be generated and are regrouped under Hang Analysis in Cluster: diag - Diagnostics Runs diagnostic scripts in the database. SEE ALSO See also RACdiag.def. -------------------------------------------------------------------------------- NAME S400RAC - Collects Cluster Information DESCRIPTION This module collects data that is related to the operation of the Oracle Cluster and its configuration. The following reports can be generated and are regrouped under Cluster Information in Cluster: Reports the details of the operating system-specific aspects (platform-specific code) racOnOff - RAC on/off Linked Verifies that the RAC option is currently linked into the oracle executable. This check is performed only in supported platforms. init - Init Files Collects the /etc/inittab and the init files. Additional platform-specific files can be present. core - Core Dumps When a debugger is found on UNIX, RDA tries to extract the stack trace from the core dumps present in the cluster directories. crs_status - CRS Status Sets up and populates CRS_status if Cluster Ready Services is installed. crs_inventory - CRS Inventory Provides the inventory of the Cluster Ready Services home if inventory information is still available. crs_stat - CRS Stat Details If Cluster Ready Services is installed, provides the crs_stat -u detailed output. alert_log - Alert Log Collects last lines of $ORA_CRS_HOME/log//alert.log (Oracle Database 10g R2 and later). crs_log - CRS Log Handles the log files in $ORA_CRS_HOME/crs/log (Oracle Database 10g R1) or in $ORA_CRS_HOME/log//crsd (Oracle Database 10g R2 and later). css_log - CSS Log Handles the log files in $ORA_CRS_HOME/css/log (Oracle Database 10g R1) or in $ORA_CRS_HOME/log//cssd (Oracle Database 10g R2 and later). racg_dump - RACG Dump Gets dump files from $CRS_HOME/racg/dump (Oracle Database 10g R1) or from $ORA_CRS_HOME/log//racg (Oracle Database 10g R2 and later). evm_log - CRS EVM Log Handles the log files in $ORA_CRS_HOME/evm/log (Oracle Database 10g R1) or in $ORA_CRS_HOME/log//evmd (Oracle Database 10g R2 and later). client_log - Client Log Handles the log files in $ORA_CRS_HOME/log//client (Oracle Database 10g R2 and later). admin_log - Admin Log Handles the log files in $ORA_CRS_HOME/log//admin (Oracle Database 10g R2 and later). ocrdump - ocrdump An OCR dump can be requested by CLUSTER_OCRDUMP setting to a true (non zero) value. ocrcheck - ocrcheck Executes ocrcheck. (Oracle Database 10g R2 and later) ocrconfig - ocrconfig -showbackup Executes ocrconfig -showbackup. (Oracle Database 10g R2 and later) srvctl - SRVM Runs srvctl commands and reports the configuration information. ipc - IPC Runs oradebug commands to generate a trace file, and then displays the IPC trace file. It is performed only for databases associated with the current Oracle home. logs - Cluster Configuration/Logs Looks for the cluster configuration and log files on the operating system. The file list is platform-specific. SEE ALSO See also library.def, COREinfo.def, INSTinfo.def, OSaix, OShpux, OSlinux, OSosf, OSsunos. -------------------------------------------------------------------------------- NAME S401OCFS - Collects Oracle Cluster File System Information DESCRIPTION This module collects data that is related to the use of the Oracle Cluster File System and its configuration. This is currently restricted to Linux environments. The following reports can be generated and are regrouped under OCFS: config_status - Configuration and Status Gets the OCFS package information, collects /etc/ocfs.conf and /etc/fstab.conf, and determines the OCFS status. drives - Drives Identifies all OCFS drives and provides a report on the space that is available on the drives. messages - Error Messages Extracts all OCFS messages from the error log. -------------------------------------------------------------------------------- NAME S402ASM - Collects Automatic Storage Management Information DESCRIPTION This module collects Automatic Storage Management information (Oracle Database 10g). This module must be run as SYSDBA to collect the whole information. The following reports can be generated and are regrouped under ASM: product_info - ASM Product Information Gathers the ASM product information if ASM is installed in a separate Oracle Home. init_ora - INIT.ORA Determines if the spfile is used. RDA connects to the database and looks for a value coming from the spfile parameter. If a value is found, RDA does not search for init.ora. A select for v$spparameter is executed to determine whether to skip the search for init.ora. vspparameters - SPFile Parameters Gets V$SPParameter information. vparameters - V$Parameters Gets V$Parameter information. overview - Overview Extracts the ASM information from the database. storage_info - Storage Information Gathers the ASM storage information. space_info - File/Space Related Information Gathers the File/Space-related information. rpm_info - ASM Library Information On Linux, it gets related package manager information. asmlib_config - ASM Library Configuration On Linux, it collects the /etc/sysconfig/oracleasm file. asmlib_disks - ASM Library Disk Information On Linux, it gets ASM library disk information. partitions - Disk Partitions On Linux, it gets the disk partition information used to identify the physical devices with the ASM disk. udev - Udev Settings On Linux, it gets the udev settings information. dev_list - Device List Lists the devices from the /dev/ directory. dev_header - ASM Devices Header Information Collects the ASM devices header information. dev_duplicates - Potential Duplicate Devices Collects the potential duplicate devices information. alert_log - Alert Log Gathers the alert Log Information. last_errors - Last Errors RDA also scans the alert log to retrieve the trace files associated with errors. To limit the data collection volume, only the latest trace files are collected based on their last modification date and the total volume. log_trace - Trace/Log Directory Listings Lists the contents of the trace/dump directories. Most recent trace files Collects the most recent trace files for each type of background process. Older files are not considered. When requested, RDA can collect the most recent user dumps. SEE ALSO See also DBinfo.def, INSTinfo.def, library.def. -------------------------------------------------------------------------------- NAME S405DG - Collects Data Guard Information DESCRIPTION This module collects Data Guard-related information (for Oracle 9i Release 2 or later). The following reports can be generated and are regrouped under Data Guard. basic - Basic Database Information Provides the basic information related to Data Guard. primary - Primary Database Information Provides the primary database information. physical - Physical Standby Information Provides the physical standby database information. logical - Logical Standby Information Provides the logical standby database information. Data Guard Broker Information Provides the Data Guard Broker information. config - Data Guard Broker Configuration Displays a detailed summary about the broker configuration. site - Data Guard Site Information Displays a detailed summary of the available databases if the Data Guard broker is enabled. SEE ALSO See also S200DB.def, S405DG.def, DBinfo.def. -------------------------------------------------------------------------------- NAME S410GRID - Controls Grid Control Data Collection DESCRIPTION This module allows to use the Grid Control directory in the EM module. SEE ALSO See also S440EM.def. -------------------------------------------------------------------------------- NAME S420AGT - Collects Enterprise Manager Agent Information DESCRIPTION This module collects Enterprise Manager Agent-related information. The following reports can be generated and are regrouped under Enterprise Manager Agent: emctl - emctl Command Output Displays the output of the following emctl command options: · emctl status agent · emctl upload · emctl status agent scheduler · emctl status agent memory · emctl status agent jobs · emctl config agent getTZ · emctl secure status agent or emctl status agent -secure · emctl pingOMS monitored_targets - Monitored Targets Displays the targets in the target.xml file of the agent and performs some pre-defined tests on target properties. It displays also the current state of the target and its blackout information. ping_test - OMS Ping Test Displays the output of the ping test performed on the OMS. This test picks OMS from the REPOSITORY_URL property in the emd.properties file. agent_config - Agent Configuration Collects the following configuration files: emd.properties This file contains all the operational parameters for the agent. emdlogging.properties This file contains the logging setup for the Java fetchlets. It performs some pre-defined tests on the configuration properties also. It reports failures. file_permissions - File/Directory Details Displays the details of some files and directories and checks the ownership and permissions. log_errors - Log Errors Filters all the lines with ERROR message from various OMS log files. Log Files Collects the agent log files. Miscellaneous Files Collects agent files. Some of the important files are as follows: OUIinventories.add This file contains the list of all OUI inventories on the machine to be considered by the agent. agntstmp.txt This file contains the timestamp of the last heartbeat to the OMS. discover.lst This file contains a list of all discovery scripts that must be run for discovery. Discovery is run only once, typically during the installation of the Enterprise Manager Agent. lastupld.xml This file has information about categories properties computed for various targets. nsupportedtzs.lst This file contains the names of all supported time zones. protocol.ini This file contains the version-specific information of the OMS, which is required by the agent to communicate properly. setupinfo.txt This file is generated by OUI during the installation of the Enterprise Manager Agent. It contains installation-specific information. supportedtzs.lst This file contains the names of all supported time zones. tzmappings.lst This file contains the names of all supported time zones. SEE ALSO See also EMdiag.def, library.def. -------------------------------------------------------------------------------- NAME S430DBC - Collects Database Control Information DESCRIPTION This module collects Database Control-related information. The following reports can be generated and are regrouped under Database Control: emctl - emctl Command Output Displays the output of the following emctl command options: · emctl getversion · emctl status dbconsole · emctl status agent · emctl upload · emctl status agent scheduler · emctl status agent memory · emctl status agent jobs · emctl config agent getTZ · emctl secure status monitored_targets - Monitored Targets Displays the targets found in the target.xml file of the agent and performs some pre-defined tests on target properties. It also displays the current state of the target and its blackout information. oms_config - OMS Configuration Displays the content of the following configuration files: emoms.properties This file contains all the operational parameters for the OMS. emomslogging.properties This file contains all the logging and tracing parameters for the OMS. agent_config - Agent Configuration Collects the following configuration files: emd.properties This file contains all the operational parameters for the agent. emdlogging.properties This file contains the logging setup for the Java fetchlets. It also performs some pre-defined tests on the configuration properties. It reports failures. file_permissions - File/Directory Details Displays the details of some files and directories and checks the ownership and permissions. log_errors - Log Errors Filters all the lines with ERROR message from various Database Control log files. Log Files Collects the Database Control log files. Miscellaneous Files Collects files that are related to Database Control. Some of the important files are as follows: emomsintg.xml This file specifies the list of special integration classes to be loaded when the Enterprise Manager application starts. These integration classes define and shape which special pages and features are enabled for the various target types. opmn.xml This file contains OPMN settings. orion-web.xml This file contains specific settings for the OC4J application. uix-config.xml This file contains specific settings for the UIX Web pages including supported languages. web.xml This file contains specific settings for the user interface. SEE ALSO See also EMdiag.def, library.def. -------------------------------------------------------------------------------- NAME S440EM - Collects Oracle Enterprise Manager OMS and Repository Information DESCRIPTION This module collects Oracle Enterprise Manager OMS and Repository-related information. Some reports require that you install the EMDIAG kit. The following reports can be generated and are regrouped under Enterprise Manager Server: no_access - No Repository Access Indicates whether the Oracle Enterprise Manager repository is not accessible. not_found - No EMDIAG Kit Indicates whether the EMDIAG kit is not found. diagkit - EMDIAG Kit Information Displays the information collected by the EMDIAG kit. It generates this report only when the EMDIAG kit is installed in the Enterprise Manager repository. To trigger EMDIAG kit collections, use RDA -T em before running this module. violations - Violation List Collects the diagnostic violation list. audit - Audit Log Lists all actions taken in the last days. emctl - emctl Command Output Displays the output of the following emctl command options: emctl getversion oms emctl status oms emctl secure status oms or emctl status oms -secure oms_config - OMS Configuration Displays the output of the following configuration files: emoms.properties This file contains all the operational parameters for the OMS. emomslogging.properties This file contains all the logging and tracing parameters for the OMS. thread_dump - Thread Dump Displays the thread dump for OMS java process. It takes two thread dumps at an interval of 3 minutes. It produces this report when the emctl dump omsthread option is available. This option was added to the 10.2 version. file_permissions - File/Directory Details Displays the details of the OMS receive directory, where Enterprise Manager stores all agent uploads before their upload in the repository. It also checks the directory ownership. ping_test - Agent Ping Test When requested, performs a ping test to a specified host list. log_errors - Log Errors Filters all the lines with ERROR message from various OMS log files. Log Files Collects the Database Control log files. OMS Miscellaneous Files Collects various files. Some of the important files are as follows: emomsintg.xml This file specifies the list of special integration classes to be loaded when the Enterprise Manager application starts. These integration classes define and shape which special pages and features are enabled for the various target types. opmn.xml This file contains OPMN settings. orion-web.xml This file contains specific settings for the OC4J application. uix-config.xml This file contains specific settings for the UIX Web pages including supported languages. web.xml This file contains specific settings for the user interface. SEE ALSO See also EMdiag.def, library.def. -------------------------------------------------------------------------------- NAME S480NM - Collect Oracle Communications Network Mediation Software Information DESCRIPTION This module collects Oracle Communications Network Mediation-related information. The following reports can be generated and are regrouped under Network Mediation: ifconfig - Network Configuration Gets the network interface configuration. product_info - Product Information Collects a variety of relevant Oracle Communications Network Mediation product information. export - Environment Variables Lists defined environment variables. node_mgr_info - Node Manager Information Gets Node Manager information. adm_server_info - Admin Server Information Gets Admin Server information. gui_info - GUI Information Gets GUI information. security_info - Security Information Gets the content of various security related files node_mgr_log - Node Manager Log Analysis Extracts information from the Node Manager log file. adm_server_log - Admin Server Log Analysis Extracts information from the Admin Server log file. Node Analyses Gets basic information about the Oracle Communications Network Mediation nodes. -------------------------------------------------------------------------------- NAME S482ND - Collect Oracle Communications Network Discovery Software Information DESCRIPTION This module collects Oracle Communications Network Discovery-related information. The following reports can be generated and are regrouped under Network Discovery: ifconfig - Network Configuration Gets the network interface configuration. product_info - Product Information Collects a variety of relevant Oracle Communications Network Discovery product information. export - Environment Variables Lists defined environment variables. discovery_info - Discovery Information Gets Discovery information. node_mgr_info - Node Manager Information Gets Node Manager information. adm_server_info - Admin Server Information Gets Admin Server information. gui_info - GUI Information Gets GUI information. security_info - Security Information Gets the content of various security related files. node_mgr_log - Node Manager Log Analysis Extracts information from the Node Manager log file. adm_server_log - Admin Server Log Analysis Extracts information from the Admin Server log file. Node Analyses Gets basic information about the Oracle Communications Network Discovery nodes. -------------------------------------------------------------------------------- NAME S484ASAP - Collect Oracle Communications ASAP Software Information DESCRIPTION This module collects Oracle Communications ASAP-related information. The following reports can be generated and are regrouped under ASAP: product_info - Product Information Collects a variety of Oracle Communications ASAP product information. environment_profile - Environment Profile Reports the environment profile. properties - Properties File Reports Oracle Communications ASAP properties. configs - Configuration Files Collects Oracle Communications ASAP configuration files. core_file_analysis - Product Information Analyzes core files. install_info - Installation Files Collects Oracle Communications ASAP installation files. java_information - Java Information Collects Oracle Communications ASAP Java information. log_files - Log Files Collects Oracle Communications ASAP log files. diag_files - Diagnostic Files Collects Oracle Communications ASAP diagnostic files. lib_files - Library Information Collects Oracle Communications ASAP library information. object_files - Object Information Lists Oracle Communications ASAP object files. full_directory_listing - Full Directory Listing Lists the content of the Oracle Communications ASAP directory structure. -------------------------------------------------------------------------------- NAME S486IPSA - Collect Oracle Communications IP Service Activator Information DESCRIPTION This module collects Oracle Communications IPSA-related information. components - Installed Components Lists installed components. variables - IPSA Variables Collects system variables relevant to Oracle Communication IP Service Activator. system_packages - System Package Information Gathers the system package information. ipsa_packages - IPSA Package Information Gathers the IPSA specific package information. miscellaneous - Miscellaneous Information Gathers miscellaneous information. audit_trails - Audit Trails Gathers the last lines of audit trails. config_files - Configuration Files Gathers configuration files. lib_files - Library Files Lists library files and some related statistics. core_analysis - Core Files Analyzes core files. profile_extractor - Profile Extractor Gathers results from the ProfileExtractor tool. Log Files Lists the contents of IPSA log files and analyzes them when requested. SEE ALSO See also library.def. -------------------------------------------------------------------------------- NAME S488PS - Collect Oracle Communications Policy Services Software Information DESCRIPTION This module collects Oracle Communications Policy Services-related information. The following reports can be generated and are regrouped under Policy Services: ifconfig - Network Configuration Gets the network interface configuration. configuration_info - Configuration Information Collects Oracle Communications Policy Services configuration information. processes_info - PS Processes Lists relevant Oracle Communications Policy Services processes. mib_info - MIB Information Collects Oracle Communications Policy Services MIB information. properties_info - Property Files Information Collects Oracle Communications Policy Services property files. ps_log_info - PS Log Files Collects last lines of Oracle Communications Policy Services log files. iplanet_log_info - iPlanet Log Files Collects last lines of iPlanet log files. data_files_info - Data Files Information Collects Oracle Communications Policy Services data files. database_files_info - Database Files Information Collects Oracle Communications Policy Services database files. lib_info - Library Information Collects information about installed libraries. access_security_info - Access Security Information Collects domain access security information. ldap_directory_info - LDAP Directory Dump Gets a dump of the Oracle Communications Policy Services LDAP directory. radius_info - Radius Log Files Collects the last lines of the Oracle Communications Policy Services Radius log files. -------------------------------------------------------------------------------- NAME S500ACT - Collects Oracle Applications Information DESCRIPTION This module collects basic information for a specified list of Oracle Applications products and for a specified user and responsibility. The following reports can be generated and are regrouped under ACT: apps_info - Application Information Gives an overview of the Applications instance including release, multi-org, and multi-currency information. apps_details - Application Installation Details Lists the installed Applications products with the installation status and patchset level. db_details - Database Instance Details Provides details about the underlying database including the database version, and archivelog state. rdbms_ver - Oracle RDBMS Versions Lists the version of products in the underlying database such as SQL*Net and PL/SQL. nls - NLS Settings Gets the NLS parameter settings of the Applications tiers. Lists the installed and base languages. vparameters - Non Default V$Parameter Settings Gets the non-default V$Parameter settings of the underlying database. managers - Concurrent and Interface Managers Gets information about concurrent, transaction, and interface managers. Not all products have managers. (Applicable for Oracle Applications 11.5 and later) stat_req - Gather Schema Statistics Requests Displays information about the last two executions of the concurrent program Gather Schema Statistics. profile - Profile Option Values Lists profile names, values, site, and user settings for the specified user and Applications products. triggers - Database Triggers Lists the database triggers on tables of the specified Applications products. indexes - Table Indexes Lists the database indexes on tables of the specified Applications products. packages - Package Versions Lists the versions of the package specifications and bodies for the specified Applications products. invalid_objs - Invalid Objects/Errors Lists the invalid objects or errors for the specified Applications products. invalid_refobjs - Invalid Referenced Objects Lists the invalid referenced objects for the specified Applications products. tops - Product Tops Reports the directories containing all code for the specified Applications products. custom_lib - Custom Library Information Reports the custom library information for the specified Applications products. bom_info - Bill of Materials Information Gathers information for the Bill of Materials when requested. ldt_ver - LDT File Versions Lists the version of the Loader Data Files for the specified Applications products. frm_ver - Form Versions Lists the version of the forms for the specified Applications products. frm_lib_ver - Form Library Versions Lists the version of the form libraries for the specified Applications products. rpt_ver - Report Versions Lists the version of the reports for the specified Applications products. rpt_lib_ver - Report Library Versions Lists the version of the report libraries for the specified Applications products. wf_ver - Workflow File Versions Lists the version of the workflow files for the specified Applications products. odf_ver - ODF File Versions Lists the version of the ODF files for the specified Applications products. proc_ver - Pro*C File Versions Lists the versions of the objects files, shared libraries, and executables for the specified Applications products. extra_ver - Extra File Versions Lists the version of the extra files for a restricted list of Applications products. java_ver - Java Class File Versions Lists the version of the Java classes for the specified Applications products. listener_ora - Contents of Listener.ora Collects the content of the Applications tier listener.ora file. jinit_ver - JInitiator Version Collects Oracle JInitiator component versions. (Applicable up to Oracle Applications 11.5.x) plugin_ver - JDK Plugin Version Collects JDK Plugin version. (Applicable from Oracle Applications 12.0.x) dev_ver - Developer Version Gets the version of the developer tools (Oracle Forms and Reports). jdbc_ver - JDBC Version Gets the JDBC version. jdk_ver - JDK Version Gets the Java Development Kit version. ssfw_ver - Self-Service FrameWork Version Gets the Self-Service FrameWork version. od_ver - Oracle Diagnostics Version Gets the Oracle Diagnostics version. http_server - HTTP Server Information Gets the HTTP server version. patches - Patches Information Regroups patch information. Applications Technology Patches Lists Applications technology patchset versions. Patches of not Registered Products Lists patchset versions of some products that are not registered. Last Month Applied Patches Displays the patch runs, with driver information (that is, C, D, or G), applied during the last month. rup - Release Update Packs Lists all Oracle E-Business Suite RUPs. nodes - Nodes Information Displays information about the different middle-tier nodes of the Applications installation. appl_top - Shared APPL_TOP Information Reports how APPL_TOPs are shared between the different Applications tier nodes. autoconfig - Autoconfig Information Displays the location of the Autoconfig files for the Applications tiers. env - Important Environment Settings Lists important Applications environment variable settings. SEE ALSO See also APPSinfo.def. -------------------------------------------------------------------------------- NAME S510ADX - Collects Oracle Applications AutoConfig and Rapid Clone Information DESCRIPTION This module collects the AutoConfig files and Rapid Clone logs from an Oracle Applications environment. To further assist in problem analysis, it can also gather Oracle Applications configuration files. You can restrict data collection to the applications tier, database tier, or performed on both tiers. However, the data collection is limited to the local host only. Rapid Clone Collects the Rapid Clone logs and the context files. Autoconfig Collects AutoConfig logs, the scripts that error out, and the corresponding template files. Configuration Collects Oracle Applications environment and configuration files. -------------------------------------------------------------------------------- NAME S590RET - Collects Oracle Retail Information DESCRIPTION This module collects Oracle Retail-related diagnostic information. The following reports can be generated and are regrouped under Oracle Retail: not_applicable - Not Applicable The Oracle Retail module can be executed only on Oracle 9i or later. tablespace - Tablespace Information Provides a tablespace overview. log_info - V$Log Information Gathers information from V$Log. table - Table Information Gathers information about Oracle Retail tables. index - Index Information Gathers information about Oracle Retail indexes. segment - Segment Information Gathers information about Oracle Retail segments. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME S800NPRF - Samples Performance Data (root not required) DESCRIPTION This module performs the operating system performance data sampling for the RDA process. In most platforms, you can run this module without root privileges. System Performance Gets a performance overview (platform-specific code). Trace Route Information Optionally, you can collect trace route information to specified hosts. Those tests are not necessarily executed for each sample. SEE ALSO See also BCaix, BChpux, BChpux, BClinux, BCosf, BCptx, BCsunos, BCunix, BCwin32. -------------------------------------------------------------------------------- NAME S801RPRF - Samples Performance Data (root privileges required) DESCRIPTION This module performs the operating system performance data sampling for the RDA process. Root privileges are required to use this module. System Performance Gets a performance overview (platform-specific code). SEE ALSO See also BCaix, BChpux, BChpux, BClinux, BCosf, BCptx, BCsunos, BCunix, BCwin32. -------------------------------------------------------------------------------- NAME S898XSMP - Samples User Specified Data DESCRIPTION This module performs the extra user-defined samplings. Sample files are created only when the command produces output. You can add extra commands for collecting data. The report name is specified as the first argument. It must start with a letter. -X RDA::Extra add_smpl name command ... The list of extra collection requests can be obtained as follows: -X RDA::Extra list You can remove extra elements selectively from the list as follows: -X RDA::Extra del_extra pos ... pos represents the position of the element in the list. Alternatively, the list can also be cleared completely by re-running the setup for the corresponding module. For example: -S XTRA SEE ALSO See also S998XTRA.def. -------------------------------------------------------------------------------- NAME S900REXE - Performs the Remote Data Collections DESCRIPTION This module performs the remote data collection. For each node: · It determines the storage type (that is, LOCAL, SHARED, SPLIT, or REMOTE), by transferring the remote setup file. · It installs the RDA software if it is not installed already. The installation is checked. · It runs RDA on the remote node and packages the reports. · It transfers the resulting report package back. -------------------------------------------------------------------------------- NAME S909RDSP - Produces the Remote Data Collection Reports DESCRIPTION This module produces the remote data collection reports. REMOTE DATA COLLECTION overview - Node Information Gets node information. results - Collected Data Gets the remote data collection results. -------------------------------------------------------------------------------- NAME S919LOAD - Produces the External Collection Reports DESCRIPTION This module collects information from external tools through specific sub modules. The name of the sub modules ends with load and they are detected automatically at the data collection module setup. Produced reports are regrouped under External Data Collection. -------------------------------------------------------------------------------- NAME S990FLTR - Control Report Content Filtering DESCRIPTION Adds filter functionality to RDA, which can mask sensitive data like host, domain, group and user names, IP addresses, LDAP domain components, and network masks. You can activate the filter by adding the Security profile to your profile. For instance, -vdSCRP -p DB10g-Security RDA offers a default filter configuration based on the system configuration but end-users can create their own filter or they can customize the existing default filter. When the setup file exists already, enable the filter with the following command: -X Filter enable If the filter configuration is not performed, then default rules are created. The filter has a status flag (enabled or disabled), an ordered list of rule sets, limits, and substitution formats. When the filter is enabled, RDA applies each rule, in the specified order listed, to each generated report. Each rule set has one or more matching patterns, possible matching options, a substitution format, and a replacement string, which tells RDA what strings to find in the output and how to substitute them. The syntax for the filter commands is as follows: -X Filter ... FILTER MANAGEMENT COMMANDS -X Filter add set [] Adds a rule set. · If the rule set already exists, then RDA moves the rule set to the end of the rule set list and resets the rule set description if present. · RDA adds a non-existing rule set to the end of the rule set list with a description if present. If the description is not present, then the rule set name is taken as the description. -X Filter add pattern Adds an extra pattern to an existing rule set. -X Filter add format Adds a new substitution format to the filter. -X Filter -f clear Clears all filtering, which means that filtering is disabled and that the whole filter definition is removed. -X Filter delete format Deletes the substitution format. This works for user-defined substitution formats only. -X Filter delete pattern Deletes a matching pattern from a rule set. Patterns are referenced by their offset (cf. the list set command). -X Filter delete set Deletes a rule set from the list of rule sets. -X Filter disable Disables the filtering. -X Filter enable Enables the filtering. When there is no existing rule set list, it also generates the default filter configuration based on the system configuration. -X Filter export Prints out the entire current filter configuration. The output is a series of commands, which can be issued again to recreate the current filter (or parts of it) into another RDA setup. -X Filter list formats Prints all internal and user-defined substitution formats. -X Filter list set [] Displays the specified rule set and its component. When the name is omitted, all rule sets are reported. -X Filter list sets Prints the ordered rule set list. -X Filter -f reset Restores the default filter configuration. -X Filter set format Specifies a format for this rule set. -X Filter set options Defines pattern-matching options. Use i to ignore case. -X Filter set string Sets the replacement string for this rule set. -X Filter set gid [] Defines the minimum group identifier value to consider when generating default filtering rules for groups on UNIX. When no argument is given, it resets it to the default value (101). -X Filter set uid [] Defines the minimum user identifier value to consider when generating default filtering rules for users on UNIX. When no argument is given, it resets it to the default value (101). -X Filter [-d] test Tests the rules for a correct syntax. When the -d option is used, the rules are printed to standard output. AUTOMATIC FILTERING When RDA detects, during the generation of a new setup file, .filter file on Unix, filter.win on Windows, filter.vms on VMS, in the work directory or in the software top directory, it loads the filter definition contained in that file. -X Filter save Saves the current filter definition in a file located in the work directory. The file is .filter on Unix, filter.win on Windows, or filter.vms on VMS. It does not write the file if the filter is disabled. -X Filter remove Removes any filter file from the work directory. The file is .filter on Unix, filter.win on Windows, or filter.vms on VMS. -------------------------------------------------------------------------------- NAME S998XTRA - Collects User Defined Data DESCRIPTION Adds extra commands for collecting data. The report title is specified as the first argument. -X Extra add_cmd <command> ... Adds extra files to a standard RDA data collection. You can specify additional files explicitly or search in directories by patterns. RDA sorts resulting files and discards duplicates. It collects the last lines of log files only. The EXTRA_TAIL setting controls the number of log lines. <rda> -X Extra add_files <file> ... <rda> -X Extra add_dir <dir> <pattern> <options> Files and directories can contain references to other settings, such as ${name} or ${name:default}. Such values should be quoted to avoid shell substitutions. Relative paths are evaluated from the RDA top directory. Regular expressions are used in patterns. The valid search options are as follows: 'i' Ignores case distinctions in both the pattern and the results. 'r' Searches files recursively under each sub directory. To avoid loops in the directory structure, the recursion level is limited to 8. 'v' Inverts the sense of matching to select non-matching files. For instance, <rda> -X Extra add_dir '${RDA_HOME}' '\.p[lm]' ir This collects all Perl scripts and packages used by RDA. It is possible to collect binary files as follows: <rda> -X Extra add_data <file> ... It is possible to import temporary environment variables (for example, HOME) as settings. For example: <rda> -X Extra add_env <name> ... The list of extra collection requests can be obtained as follows: <rda> -X Extra list Environment variable names can be removed from the import list as follows: <rda> -X Extra del_env <name> ... Extra elements can be removed selectively from the list as follows: <rda> -X Extra del_extra <pos> ... <pos> represents the position of the element in the list. Alternatively, the list can also be cleared completely by re-running the setup for the corresponding module. For example: <rda> -S XTRA Collected information is regrouped under Extra Commands and Extra Files. NOTE Any deletion operation causes the removal of the data previously collected by the XTRA module. SEE ALSO See also S898XSMP.def, library.def. -------------------------------------------------------------------------------- NAME S999END - RDA Module Finalizing the Data Collection DESCRIPTION system - System Information Collects key system configuration for the CFG module. report - Report Settings Produces an overview report of the main current settings and the data collection, as well as some statistics about the SQL statement and operating system command execution for the CFG module. Locates packaging commands (for example, tar and zip) and the compression tools (compress or gzip) that are available. Stores the time of the last RDA Data Collection execution and indicates the end of the script. SEE ALSO See also OSaix, OSdarwin, OShpux, OSlinux, OSosf, OSptx, OSsunos, OSunix, OSvms, OSwin32. -------------------------------------------------------------------------------- NAME TLdiff - Compares Two Systems DESCRIPTION This tool compares two systems or two samples from the same system. For remote collections: · A remote collection setup must be performed before running this tool. Use a command similar to the following: <rda> -vX Remote setup_cluster / · Data is extracted remotely on all nodes and transferred back into the sample sub directory. Collected samples are regrouped in a result set. You can only compare samples from the same result set. A list of all samples, grouped by result sets, is available. USAGE This tool can be used in two ways: a) Runs interactively. It requests the user to enter the required information. <rda> -vT diff b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vT diff:A:<set>,<sample>:<type>[,...][:<dir>|...] Performs a data collection on all remote nodes. <set> is the result name. <rda> -vT diff:B:<set>,<node>,<sample>:<type>[,...][:<dir>|...] Performs a data collection on the local host. <set> is the result name. <rda> -vT diff:C:<set>:<node1>,<sample1>:<node2>,<sample2> Compares two data collections. <rda> -vT diff:D Lists all available samples, grouped by result set. <rda> -vT diff:E:<set>:<spec_name>:<type>[,...][:<dir>|...] Prepares a specification file for comparing independent systems. <rda> -vT diff:F:<node>,<sample>:<spec_path> Verifies the prerequisites and performs a data collection based in a specification file. SEE ALSO See also DIFFcmp.def, DIFFget.def. -------------------------------------------------------------------------------- NAME TLem - Executes Enterprise Manager Diagkit Tests. DESCRIPTION This tool executes one or more tests from an Enterprise Manager Diagkit module. When specified, the test module attempts to fix problems. REQUIREMENTS IMPORTANT: The system must have Enterprise Manager Diagkit installed in the repository to use this module. USAGE <rda> -T em Can select the tests interactively. <rda> [-e EM_SID=<sid>] -T em:<module>:<test>:<level>:<fix> <rda> [-e EM_SID=<sid>] -T em:<module>:<test>:<level> <rda> [-e EM_SID=<sid>] -T em:<module>:<test> <rda> [-e EM_SID=<sid>] -T em:<module> Can specify the parameter at the command line. Problems are fixed automatically only if FIX is specified explicitly as the value for the latest argument. No attempt will be made otherwise. Level 1 is assumed by default. All tests of the module are performed unless a test identifier is specified. The EM_SID setting can provide the default repository database identifier. When the setting is not defined, the TWO_TASK and ORACLE_SID environment variables are successively considered. The SYSMAN user is used by default for executing the tests. An alternative user can be specified through the EM_LOGIN setting. -------------------------------------------------------------------------------- NAME TLmerge - Merges Alert Logs and Trace Files. DESCRIPTION This tool extracts information from alert log and trace files from the local node or remote nodes and merges them in a single report. It can extract data from the Oracle Database, Oracle Real Application Cluster, and Automatic Storage Management contexts. It considers events in a provided time stamp range only. For remote collections: · A remote collection setup must be performed before running this tool. Use a command similar to the following: <rda> -vX Remote setup_cluster / · Data is extracted remotely from all relevant alert logs and trace files. They are merged into a single file, which is transferred back into the remote sub directory. · Final merge report of all the remote merged files is shown in the extern sub directory. · You can merge files from remote machines again later with or without individual time corrections (offsets). · A list of available remote result sets can be provided. By default, a maximum of 10 trace lines per record are shown in the final output. If required, you can change this limit by executing the tool in advanced mode. <rda> -vT -p advanced merge USAGE This tool can be used in two ways: a) Runs interactively. It requests the user to enter the required information. <rda> -vT merge b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> [-e MERGE_LINES=<n>] -vT merge:A:<set>:<start>,<end>[,<path>|...] Performs a new merge from remote nodes. <set> is the result name. The result name starts with a letter followed by alphanumerical characters. The next argument includes the start and end time stamps. Time stamps are in the format DD-Mon-YYYY_HH24:MI:SS. You can provide additional full paths to locate rotated alert logs. RDA searches in those directories, for files that contain the 'basename' in their name. To alter the maximum number of lines to consider in trace log entries, specify an alternative value for the MERGE_LINES setting. <rda> [-e MERGE_LINES=<n>] -vT merge:B:<set>:<start>,<end>[,<path>|...] Performs a new merge on the local node. It takes the same argument as used for remote collections. <rda> -vT merge:C:<set> Merges existing data without time corrections. <rda> -vT merge:D:<set>:<node>=<offset>,... Merges existing data with time corrections. Names assigned by the setup should be used for <node>. The offsets are specified in seconds and can be either positive or negative (for example, NOD001=-1.450). <rda> -vT merge:E Lists all available collections present. WARNING The tool does not support currently the data extraction from files in the XML format. For 11g databases having their alert log in both XML and text formats, the data is extracted from the alert log in text format. SEE ALSO See also MERGElib.def. -------------------------------------------------------------------------------- NAME TLna - Network Advisor DESCRIPTION Net Advisor is a tool that provides advice on resolving network layer errors encountered using Oracle Net Services. The tool assesses information produced in a network trace file. It notes which naming methods were used in attempting to resolve a given service name and provides an overview of the network configuration. Net Advisor identifies conflicts or issues in the network setup of the client, and suggests what to check or which actions to take for the issues found. This tool supports the LDAP, ONAMES, and LOCAL naming methods currently, and analyzes TNS-12154 and TNS-12541 errors. REQUIREMENTS Must have a valid Oracle Networking trace file. USAGE This tool takes a corresponding trace file as input and can be used in two different ways: a) Runs through RDA setup. It requests the user to enter the absolute path of the trace file. <rda> -vT na b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vT na:absolute_path_of_trace_file The tool generates a report with findings. The reports can also be viewed in the External Data Collections sub menu of the final RDA output package. If it is not disabled, you can refresh the section with the following command: <rda> -vdCRP LOAD SEE ALSO See also S919LOAD. -------------------------------------------------------------------------------- NAME TLora600 - Diagnoses ORA-600 Oracle Internal Errors. DESCRIPTION ORA-600 errors are raised from the kernel code of the Oracle RDBMS software when an internal inconsistency is detected or an unexpected condition is met. These types of error conditions are not necessarily bugs because the error condition may be caused by problems with the operating system, lack of resources, hardware failures, and so on. Whenever an ORA-600 error is raised, a trace file is generated in USER_DUMP_DEST or BACKGROUND_DUMP_DEST depending on whether the error was caught in a user or a background process. The error is also written in the alert log with the name of the trace file. This trace file contains vital information about the factors that led to the error condition. REQUIREMENTS Must have a valid Oracle database trace file. USAGE This tool takes the trace file as input and can be used in two ways: a) Runs through RDA setup. It requests the user to input the absolute path of the trace file. <rda> -vT ora600 b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vT ora600:absolute_path_of_trace_file The tool analyzes the trace file, generates reports, and displays key information about the results. The reports can also be viewed in the External Data Collections sub menu of the final RDA output package. If it is not disabled, you can refresh that section by the following command: <rda> -vdCRP LOAD The following reports can be produced: Summary Report Obtains the ORA-600 arguments, call stack details, current SQL statement, the corresponding Knowledge Article, and the heap error summary. Header Report Displays the header of the input trace file. Heap Report For a heap dump error, it obtains the heap dump details, corrupted extent details, and memory dump details. SEE ALSO See also S919LOAD. -------------------------------------------------------------------------------- NAME TLoraddc - Oracle Database Diagnostics Collector DESCRIPTION Oracle Product Support may request a variety of diagnostics from SYSTEMSTATE dumps to trace files generated by operating system commands, in situations where a database is encountering outages or severe loss of service. Oracle Database Diagnostics Collector (ORADDC) is designed to make the collection of database diagnostics a more streamlined process. ORADDC has the following capabilities: · It can generate the following dumps and collect the corresponding trace files: · Hang Analyze Dump · Shared Pool Heap Dump · Library Cache Dump · O/S Command Tracing (where truss, strace or tusc are available) · Process Error Stack · Process State Dump · Process Stack Trace (where pstack is available) · Process Open Files (where pfiles is available) · Process Dynamic Libraries (where pldd is available) · Row Cache (Dictionary Cache) Dump · System State Dump · 10046 Trace · It can produce the following reports: · Active Session History (requires licenses) · Locking/blocking contention · Shared Pool memory chunk allocation (when a heap dump is requested) · Session Wait Events In addition, ORADDC is able to do the following: · Run requested diagnostics as multiple requests in parallel as background processes, which helps for reducing the collection time. · Name a list of background processes to trace and to dump. · Specify one or more Oracle server processes by any one of the following methods: · A list of database session identifiers · A list of listener names (UNIX only) · A list of Oracle process identifiers · A list of operating system process identifiers · Sessions from a specified username · Sessions with entries in DBA_BLOCKERS · Sessions waiting on specified wait events (limited to 10 per wait#) · Keep track of trace/dump/process stack/report files produced as well has being able to determine process dumps caused indirectly by requesting a hang analyze dump. It adds a summary of dump, report, and trace files to the execution log. · Inspect a produced hang analyze dump and display a list of sessions in a 'hang' state as well as sessions that are blocking other sessions. It writes these details in the execution log. It lists any process dumps caused by the HANGANALYZE request also. By default system/process dumps are performed several times with a two-minutes interval in between. You can override the default time interval by a time specified in seconds. ORADDC has the ability (if requested) to pre-connect to the database and sleep until told to wake up before taking the specified diagnostics. If 10046 or operating system traces were requested, ORADDC waits for all non-trace tasks (dumps, reports) to complete. It then waits approximately thirty seconds and terminates all tracing activity. USAGE This tool can be used in two ways: a) Runs interactively. It requests the user to enter the required information. <rda> -vdT oraddc b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vdT oraddc:<command>[:<arg1>[:...]] It supports the following commands: A Perform a collection B Perform a collection under the control of wake-up commands C Wake up ORADCC D Remove a result set E Check if ORADDC is still alive F Auto wake up ORADCC ORADDC Diagnostic Collection You can specify the collection details interactively or from the command line with the following syntax: <rda> -vdT oraddc:A:[<nam>,...]:<met>[/...]:[<t1>,...]:[<t2>,...]:<sleep>... <nam>,... is a comma-separated list of background process names for which reports are requested. It supports following names: arc, asmb, cjq, ckpt, d, dbw, diag, j, lck, lgwr, lmd, lmon, lms, mman, mmnl, mmon, o, pmon, psp, q, qmnc, rbal, reco, s, and smon. Names that are shorter than four characters regroup several processes. For example, q matches q000, q001, ... With <met>, you can specify additional process identifiers by one of the following methods: B Blocking sessions E Sessions waiting on the wait events provided as argument L Listener names (list provided as argument) O Oracle process identifiers (list provided as argument) P Process identifiers (list provided as argument) S Session identifiers (list provided as argument) U Sessions for the user provided as argument - None Use a comma-separated format to specify the information like the process or system identifiers, or the wait event numbers. Be careful on the number of sessions logged in as a specified user. <t1>,... is a comma-separated list of traces or dumps that ORADDC must collect for the specified processes. It supports following entries: E Process Error Stack F Process Open Files L Process Dynamic Libraries O Operating System Trace P Process State Dump S Process Stack T 10046 Trace Operating system traces and process stacks are depending on command availability. Usually, you cannot execute them simultaneously. <t2>,... is a comma-separated list of traces or dumps that ORADDC must collect. It supports following entries: A Hang Analyze Dump C Locking Contention Report D Active Session History Dump H Shared Pool (Heap) Dump L Library Cache Dump R Row Cache Dump S System State Dump W Session Wait Events Report For example, <rda> -vdT oraddc:A:smon:B:T:S <rda> -vdT oraddc:A::E/125,137 <rda> -vdT oraddc:A::U/scott:T,S:A,H,S:3 <rda> -vdT oraddc:A::::C,L,R ORADDC Delayed Diagnostic Collection ORADDC supports same collection capabilities in wait mode as the direct mode and uses a similar syntax: <rda> -vdT oraddc:B:[<nam>,...]:<met>[/...]:[<t1>,...]:[<t2>,...]:<sleep>... It waits for a wake-up command before proceeding with gathering diagnostics: The wake-up can be done in two ways: · Wake-up manually. <rda> -T oraddc:C · Wake-up automatically when the database is no longer responding. <rda> -T oraddc:F:[<sleep>,<timeout>] The default values for <sleep> and <timeout> are respectively 60 seconds and 120 seconds. This is useful when a pre-connection is required because fresh connections to the database are not possible. When ORADDC runs in delayed mode, you can test if it is still alive by using one of the following commands (or its equivalent interactive form): <rda> -T oraddc:E <rda> -T oraddc:E:<tolerance> Oracle recommends a default delay of 30 seconds. If you decide to override this, do not use a value less than 10 seconds. This is because ORADDC sleeps in 5 second cycles. Therefore, anything approaching 5 seconds may risk a false result if the system is busy. You can specify a flag as an extra argument to get the list of processes that are waiting for a wake-up. <rda> -T oraddc:E::1 <rda> -T oraddc:E:<tolerance>:1 The delay mechanism is based on the current Oracle system identifier (SID). You can specify an alternative SID, using the following: <rda> -T -e ORACLE_SID=<sid> oraddc:C <rda> -T -e ORACLE_SID=<sid> oraddc:E <rda> -T -e ORACLE_SID=<sid> oraddc:F ORADDC Result Management With the D command, you can remove all files from a specified ORADDC run. In interactive mode, you can select the result set to remove from the list of existing result sets. ORADDC removes it only after confirmation. You can use the following command also: <rda> -T oraddc:D:<timestamp> The timestamp should be in YYYYMMDDhhmm format. Other Relevant Settings The following settings influence the database connections used to collect the diagnostic information: · ORACLE_SID · SQL_LOGIN · SQL_SYSDBA · SQL_PRELIM ORADDC supports the RDA extended SID formats. Nevertheless, collecting trace files requires a local database. WARNING For some of the operations, this tool can have negative affects on system performance. If you are not sure about the options you intend to use, you should ensure that you are working under the guidance of Oracle Support. This tool parallelizes its tasks. It launches one background process per report and per specified process. Therefore, it requires a Perl version where 'fork' is implemented and not disabled in the setup. SEE ALSO See also DDCload.def, DDCrun.def, DDCstat.def. -------------------------------------------------------------------------------- NAME TLsecure - Identifies Potential Security Risks DESCRIPTION This tool performs checks to identify potential security risks. Most checks come from Oracle Technology Network article Project Lockdown available at http://www.oracle.com/technology/pub/articles/project_lockdown/index.html This tool does not incorporate all of the checks and additional checks could be implemented in future releases. USAGE This tool can be used in two ways: a) Runs interactively. It requests the user to enter the required information. <rda> -vT secure b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vT secure:<opt1>[,<opt2>[,...]] The tool generates a report with findings. D_DP - Users with a Default Password Checks the existence of users with a default password (Oracle Database 11g and later). D_KP - Users with a Well Known Password Checks the existence of users with a well known password and displays whether the account is locked. You must have access to the sys.user$ table to get the results. D_NV - Users not Visible in dba_users Lists users from sys.user$ table who are not visible in the dba_users view. DB_OS - Operating System Authenticated Users with a Password Lists users who are identified externally but who does not have c<EXTERNAL> as password. It considers all user names that start with the os_authent_prefix value. D_PG - Privileges not granted by their Owner Lists the privileges that have not been granted by their owner. It reports the receiver of the privilege, the grantor, and the owner. D_UP - Users and Privileges from gv$pwfile_users Lists the users who have been granted SYSDBA and SYSOPER privileges as derived from the password file. D_ST - Users with SYSTEM as Default Tablespace Lists users who have SYSTEM as the default tablespace. It skips the sys and system users. L_NP - Listeners without a Password Reports the name of the listeners without an associated passwords present in listener.ora files from well known locations. You can specify extra files with the SECURE_LISTENER setting. With a password, privileged operations, such as saving configuration changes or stopping the listener, used from the Listener Control utility, will require a password. L_OS - Listeners with Local Operating System Authentication This check is applicable only for Oracle Database 10g and later. Reports the name of the listeners with a password but where the local operating system authentication is not disabled. In such contexts, the user who is running the listener can administer the listener without providing the password. It checks all listener.ora files from well known locations. You can specify extra files with the SECURE_LISTENER setting. L_RT - Listeners Modifiable at Runtime Reports the name of the listeners that does not have ON as value for ADMIN_RESTRICTIONS. It checks all listener.ora files from well known locations. You can specify extra files with the SECURE_LISTENER setting. Setting ADMIN_RESTRICTIONS_<listener_name>=ON disables the runtime modification of parameters in listener.ora. That is, the listener will refuse to accept SET commands that alter its parameters. N_AS - AUTHENTICATION_SERVICES Values in sqlnet.ora Files Reports the current value of SQLNET.AUTHENTICATION_SERVICES from sqlnet.ora files found in well known locations. You can specify extra files with the SECURE_SQLNET setting. The process of restricting sysdba access only with a password is controlled by the parameter SQLNET.AUTHENTICATION_SERVICES in sqlnet.ora file. If this parameter is set to NONE, then the auto login of the SYSDBA role is disabled. A security method that enables you to have high confidence in the identity of users, clients, and servers in distributed environments. Network authentication methods can also provide the benefit of single sign-on for users. Oracle Advanced Security must be installed. WARNING Any action based on these checks should be performed only after careful planning and additional analysis. If you are not sure about the action you intend to perform, you should perform proper analysis to ensure it will not affect the current functionality. SEE ALSO See also DBinfo.def. -------------------------------------------------------------------------------- NAME TSTalert - Analyzes Alert Log. DESCRIPTION This test module analyzes the alert log and provides a summary of finding in the final report. The alert log file can be specified in two ways: a) Runs interactively. It requests the user to enter the absolute path of the alert log file. <rda> -vT alert b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vT alert:absolute_path_of_alert_log If the file does not have a .xml extendion, RDA assumes that the alert log is in a pre-11g format. Times are always truncated at second level. SEE ALSO See also DBalert.def. -------------------------------------------------------------------------------- NAME TSTcore - Tests Stack Trace Extraction DESCRIPTION This test module extracts the stack trace from a system core dump. -------------------------------------------------------------------------------- NAME TSTdb - Tests Database Access DESCRIPTION This test module loads the passwords encoded in the setup file. It looks for sqlplus in the command path and displays the corresponding path when found. It looks for oracle in the command path and displays related information (such as path, checksum, permissions, and size). Displayed information is platform-specific. It checks the settings for a database connection. ORACLE_HOME and ORACLE_SID must be defined in the setup file. A warning is issued if TWO_TASK is found. It executes a simple query in the database with sqlplus. -------------------------------------------------------------------------------- NAME Daylight Saving Time Tool Box DESCRIPTION This test module regroups a number of tools for detecting issues relating to 2007 Daylight Saving Time changes. See Knowledge Article 397281.1 USA 2007 Daylight Saving Time (DST) Compliance for Oracle Server Technologies Products and Knowledge Article 403659.1 2007 Daylight Saving Time Changes For Oracle Applications for more information about the subject. REQUIREMENTS Must have a valid Oracle home and a valid connection to a running database. USAGE Use the following command to execute the tool kit: <rda> -T dst Use the following command to ignore the current setup: <rda> -Tn dst AVAILABLE TOOLS Client Timezone Patch Test Checks whether the time zone definition file on the client is the same version as the definition file on the database. First it considers a version 4 change (Canada/Mountain). When the version 4 definition is not installed on either side, it then tests a version 3 change (US/Mountain). The test is based on Knowledge Article 402742.1 (Q202 - Is the time zone file patch applied correctly to the client?). Oracle Java Virtual Machine Test Checks if the March 2006 Time Zone Update and February 2007 Time Zone Update are applied for Oracle JVM. The test is based on Knowledge Article 414309.1 (Q6 - How can I test if the OJVM patch has been applied correctly?) and requires the privilege to create objects in the database. utltzuv2 test Existing TIMESTAMP WITH TIME ZONE data that uses time zones that are updated in the new time zone files, will be affected by the installation of these new time zone files. Oracle provides the utltzuv2.sql script to scan your current data to see if any of this TSTZ data exists. Using the results of this script, you can save the affected TSTZ data before the new time zone files are installed in a VARCHAR2 column. After the time zone files are installed, the TIMESTAMP values can then be restored to their intended value. If you have an existing utltzuv2.sql script, this is not sufficient for scanning the updates in the version 3 of the time zone files (which include the changes for the USA from 2007), or for version 4 changes. Standalone implementation of the utltzuv2.sql script does not require installing files in the Oracle Home or installing a Java Virtual Machine. It can be executed on remote databases. It is based on Knowledge Article 359145.1 - Impact of 2007 USA daylight saving changes on the Oracle database. Timezone Usage Views Drops and recreates the following objects in the SYS schema, and ensure that you do not use these for your own purpose: · View TZ$TSLTZ_TAB_COLS Shows columns of tables using the TIMESTAMP WITH LOCAL TIME ZONE type. If all session time zones and the database time zone are not affected by the time zone changes, then these types are not affected. · View TZ$TSLTZ_VW_COLS Shows columns of views using TIMESTAMP WITH LOCAL TIME ZONE type. These views are based on tables with TSLTZ types. Therefore these views themselves do not introduce any new time zone use. They would not be affected by any time zone changes. The underlying table data may be affected, but the views will only reflect the data stored in the tables. · View TZ$NAMED_TSTZ_TAB_COLS Shows columns of tables using TIMESTAMP WITH TIME ZONE type where named time zones are used. When TSTZ data uses offsets (-05:00, +10:00, etc.) or static time zones (GMT, UTC), it is not affected by any changes to time zone rules because offsets are always the same. Therefore you are only interested in TSTZ data using named time zones (US/EASTERN, Europe/Berlin, etc.). This view shows TSTZ data only with named time zones. It lists the column details and the number of rows in each column using a named time zone. Because this view has to work out exactly how many affected rows there are in each column it could take some time to complete. If you know you have a lot of this type of data, then it is a good idea to create a table based on the view results to query it again without the same amount of work. · View TZ$NAMED_TSTZ_VW_COLS Similar to TZ$NAMED_TSTZ_TAB_COLS, but for views. Usually views that are marked as using these types are based on tables using the same types, and therefore these views are not important when assessing time zone use. For these views, it is the underlying table data that requires investigation. However, it is possible also to create a view where a TO_TIMESTAMP_TZ function is used to "build" a timestamp: for example, a DATE in a underlying table. When it is performed, you must check the view definition for the usage of named time zones. When these are used, then the view is affected by time zone changes even if the underlying data is not. · View TZ$ARGUMENTS Shows arguments of PL/SQL procedures and functions that use time zone types. This does not mean that these objects are affected by time zone changes. This is the case only if they are called with arguments that use updated time zone information. For this reason, the standard Oracle schemas (like SYS etc.) are filtered out of the results of this view as well. Many of the standard functions are capable of dealing with time zones, but these are only affected when affected data is used. Therefore these functions are not flagged since they do not 'introduce' any time zone use. Note: If your application stores PL/SQL objects in the SYS schema (or other standard schemas), you should adjust the view so that they can be checked, but discard Oracle-standard objects. · View TZ$DBTIMEZONE Shows the database time zone. The database time zone should be an offset rather than a named time zone. See Knowledge Article 359119.1 Using named timezones vs offsets in database & session timezone. · View TZ$OVERVIEW Contains an overview of the results of all the above queries. For x_TAB_COLS and x_VW_COLS, it makes a split between SYS usage and non-SYS usage. For an overview of time zone data in the data dictionary please see Knowledge Article 402614.1 Time Zone Data in the Data Dictionary (SYS) and the Effects of a Time Zone File Update. This view does not contain results of the TZ$SOURCE view because they must be interpreted manually before they can be judged. · View TZ$SOURCE Shows all lines of PL/SQL stored in the database that use time zone keywords. This view filters some of the standard Oracle schemas like SYS because these schemas contain source code, which use time zones. However, it does not mean that the the database uses time zone functionality. When these functions are used, other time zone functionality must be used in the database, and that is found either through this view or other views. Similar to TZ$ARGUMENTS, if your application stores PL/SQL objects in the SYS schema (or other standard schemas), adjust the view so that these can be checked, but discard Oracle-standard objects. This view should be handled with care. Firstly it is a simple "like" query based on the DBA_SOURCE view, which can be large, so this view can be slow. Also, because these keywords can be used in other settings, the output from this view should be handled with care since it might contain some "false-positives". An example of such a false positive is the keyword TIMESTAMP. This can be used to indicate a timestamp only without a time zone, which is not affected by time zone changes. However, it can also be used in a "time zone aware" context. Therefore, as stated, you must check the output from this view manually before conclusions can be drawn. TZ$SOURCE contains a TEXT column, which contains the line of source text in a PL/SQL block that contains one of the TZ keywords. Based on this complete line, you can judge whether this is using time zone aware data, or whether this is a false positive. · Function TZ$NAMED_TSTZ_TAB_COLS_FN · Function TZ$NAMED_TSTZ_VW_COLS_FN · Type TSTZ_NAMED_TABLE · Type TSTZ_NAMED_TYPE It is based on Knowledge Article 412971.1 Assess Time Zone usage in a Database. NOTES · All the tests require RDA to connect as a sysdba user to the database. -------------------------------------------------------------------------------- NAME TSTenv - Tests the Environment DESCRIPTION This test module lists all defined environment variables seen by RDA. Compares the environment with the RDA context. -------------------------------------------------------------------------------- NAME TSTevent - Extracts Event Log Information DESCRIPTION This test module extracts event log information. <rda> -T event or <rda> -T event:Collect Produces an overview of the data collection execution duration, including the tools and test modules execution. <rda> -T event:Setup Produces an overview of the data collection setup duration. In some cases, data collection duration time can include the setup time, particularly for tasks performed before the creation of the report directory. -------------------------------------------------------------------------------- NAME TSThcve - Executes Health Check/Validation Engine Tests. DESCRIPTION <rda> -T hcve This test module presents all possible rule sets for the current platform and executes the selected one. It removes all previous reports for that rule set. If the -d option is specified, it displays step execution progress. <rda> -T hcve:<name> Executes the specified rule set. <rda> -T M:hcve:<name> Produces the documentation of the specified rules set as a report. SEE ALSO See also HCVEinfo.def. -------------------------------------------------------------------------------- NAME TSTinv - Tests Oracle Home Inventory Content DESCRIPTION This test module extracts the components from the Oracle home inventory. The names, versions, and installation locations are listed. -------------------------------------------------------------------------------- NAME TSTocm - Tests Oracle Configuration Manager Discovery Information. DESCRIPTION This test module extracts the components from the Oracle Configuration Manager discovery information. It lists the names, versions, and installation locations. -------------------------------------------------------------------------------- NAME TSTodi - Displays the Current Oracle Data Integrator Module Setup DESCRIPTION This test module displays the current Oracle Data Integrator module setup, indicating which master and work repositories, which technical environments, and which journals are collected. SEE ALSO See also S385ODI. -------------------------------------------------------------------------------- NAME TSTsql - Tests SQL*Plus Settings and Gets some Database Configuration Information DESCRIPTION This tool loads the passwords that are encoded in the setup file and collects the following information: · Current user · Current SQL*Plus settings · Content of the v$version table · Content of the v$database table · Content of the v$pwfile_users table · Value of the remote_login_passwordfile parameter · Records of the dba_triggers table with a null table_name -------------------------------------------------------------------------------- NAME TSTssd - Analyzes System State Dumps. DESCRIPTION This test module analyzes all system state dumps contained in a specified trace file and provides a summary as a report. The trace file can be specified in two ways: a) Runs interactively. It requests the user to input the absolute path of the trace file. <rda> -vT ssd b) Runs from the command line. The input can be given in the command line using the following syntax: <rda> -vT ssd:absolute_path_of_trace_file SEE ALSO See also DBssd.def. -------------------------------------------------------------------------------- NAME TSTssh - Tests Remote Connectivity and Associated Operations DESCRIPTION This test module executes several tests to check remote connectivity and operations: - Tests which commands are available from the PATH. - Lists related files. - Tests if an authentication agent is configured. When possible, it checks if identities have been added. - Lists default remote operation settings defined. - Lists common settings modified by the remote operation initialization. - Checks if an authentication agent has been started. When possible, lists agent identities. - Tests a remote command execution with different settings. -------------------------------------------------------------------------------- NAME TSTvms - Verifies Current User Environment on VMS DESCRIPTION This test module determines if the current VMS account has the required settings, and that the current logicals and symbols are a valid Oracle Server environment. If not, you cannot run the RDA procedure. ERROR SECTION Any failure means that the RDA script cannnot proceed. Checks VMS version. Checks if TCPIP Services for OpenVMS is installed and running. UIC check (Taken from ORACLEINS.COM). Checks basic Oracle Server environment (Taken from PREFLIGHTVMS.COM). Additional Oracle Server environment checks. Checks rights/identifiers. WARNINGS SECTION RDA can proceed, but with limited functionality. Checks if DECC$FILE_SHARING value is set to ENABLE. Checks privileges for an Oracle Admin account. Checks if the database instance is running (that is, ORA_<sid>_PMON process exists). Checks for OPER, as it is required to run SYSMAN. Checks for SYSLCK, as it is required to run PRODUCT command. Checks for WORLD, as it is required to run SHOW command. Checks for read access to UAF file. Checks for availability of the VMS ZIP program. -------------------------------------------------------------------------------- NAME WLSm - Collects Oracle WebLogic Server Information (All Servers) DESCRIPTION This module collects Oracle WebLogic Server-related information for multiple Servers. The following reports can be generated and are regrouped under WebLogic Server: REPORTS Clusters Collects domain-wide cluster management objects information (such as number of Servers managed under the cluster). Domain Configuration Collects domain-wide configuration management objects information (such as JDBCSystemResources, JMSServers, JMSSystemResources, Log, LogFilters, Servers, and VirtualHosts). Configuration Files Gathers domain-wide Oracle WebLogic Server-related configuration files. patch_list - Applied Patch List Lists the applied Oracle WebLogic Server patches. patch_registry - Patch Registry Displays the patch-registry.xml file. Patches from Log Files Displays the patches found in the server log files since the last startup. It lists the server logs also. Domain Runtime Collects domain-wide runtime management objects information (such as ClusterRuntime, DomainServices, JDBCServiceRuntime, JMSRuntime, JVMRuntime, LogRuntime, and ServerRuntimes). Diagnostic Images You use the Diagnostic Image Capture component of the Oracle WebLogic Diagnostic Framework (WLDF) to create a diagnostic snapshot, or dump, of a server's internal runtime state at the time of the capture. It requires the availability of Oracle WebLogic Scripting Tool (WLST). Log Exports Gathers Oracle WebLogic Server-related log information. Executes a query on the server side and retrieves the exported Oracle WebLogic Diagnostic Framework (WLDF) data. This is done using exportDiagnosticDataFromServer. -------------------------------------------------------------------------------- NAME WLSs - Collects Oracle WebLogic Server Information (Single Server/Off Line) DESCRIPTION This module collects Oracle WebLogic Server-related information for single Server or off-line collections. The following reports can be generated and are regrouped under WebLogic Server: REPORTS Clusters Collects domain-wide cluster management objects information (such as number of Servers managed under the cluster). It does not collect those information in offline collections. Domain Configuration Collects domain-wide configuration management objects information (such as JDBCSystemResources, JMSServers, JMSSystemResources, Log, LogFilters, Servers, and VirtualHosts). It does not collect those information in offline collections. Configuration Files Gathers domain-wide Oracle WebLogic Server-related configuration files. patch_list - Applied Patch List Lists the applied Oracle WebLogic Server patches. patch_registry - Patch Registry Displays the patch-registry.xml file. Patch Information Displays the patches found in the server log files since the last startup. It lists the server logs also. Domain Runtime Collects domain-wide runtime management objects information (such as ClusterRuntime, DomainServices, JDBCServiceRuntime, JMSRuntime, JVMRuntime, LogRuntime, and ServerRuntimes). diag_image - Diagnostic Image You use the Diagnostic Image Capture component of the Oracle WebLogic Diagnostic Framework (WLDF) to create a diagnostic snapshot, or dump, of a server's internal runtime state at the time of the capture. It requires the availability of Oracle WebLogic Scripting Tool (WLST). log_info - Log Exports Gathers Oracle WebLogic Server-related log information. It executes a query against the specified log file and retrieves the exported Oracle WebLogic Diagnostic Framework (WLDF) data. This is done using exportDiagnosticDataFromServer in connected mode and exportDiagnosticData in offline mode. The exportDiagnosticData collects data with the default options. It requires the availability of Oracle WebLogic Scripting Tool (WLST). ----- Note: ----- Subject: Bug 6770913 - Various errors during upgrade to 11g Doc ID: 6770913.8 Type: PATCH Modified Date : 24-SEP-2008 Status: PUBLISHED Bug 6770913 Various errors during upgrade to 11g This note gives a brief overview of bug 6770913. The content was last updated on: 09-SEP-2008 Click here for details of each of the sections below. This bug is alerted in Note 579523.1 Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions >= 11 but < 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) and 11.1.0.7 (Server Patch Set) Symptoms: Related To: Process May Dump (ORA-7445) / Abend / Abort Internal Error May Occur (ORA-600) OCI-21500 ORA-600 [kokeiix1] ORA-600 [22635] Dump in or under kopesiz Migration / Upgrade / Downgrade Description Upgrade to 11g can fail with various ORA-600 / OCI-21500 or dump type errors in certain cases. Please see Note 579523.1 for full details of this issue. Further details on this issue can be found in Note 579523.1 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. ----- Note: ----- Subject: Upgrade From 10.2.0.3 To 11.1.0.7 Using DBUA Throws ORA-600 [kksfbc-reparse-infinite-loop] Error During Update to SYS.AQ_SRVNTFN_TABLE Doc ID: 761711.1 Type: PROBLEM Modified Date : 28-JAN-2009 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.7 This problem can occur on any platform. Symptoms While performing an upgrade from 10.2.0.3 to the 11.1.0.7 RDBMS, the upgrade fails when an ORA-600 [kksfbc-reparse-infinite-loop] is raised during the update to the SYS.AQ_SRVNTFN_TABLE table: SET tab.user_data.context_type = 0 UPDATE SYS.AQ_SRVNTFN_TABLE tab SET tab.user_data.context_type = 0 Stack will be similar to: ksedst1 <- ksedst <- dbkedDefDump <- dbgexPhaseII <- dbgexProcessError <-dbgePostErrorKGE <- kgerinv_internal <- kgerinv <- kgeasnmierr <-kksfbc <- kkspsc0 <- kksParseCursor <- opiosq0 <- kpooprx <- kpoal8 <-opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- main <- start Cause The cause of this problem has been identified in Bug 7708445 The default value for PLSQL_OPTIMIZE_LEVEL is 2 in both 10.2 and 11.1, however, the PLSQL_DEBUG parameter is deprecated in 11g so the if this parameter (PLSQL_DEBUG) is set to TRUE, the DBUA will change the PLSQL_OPTIMIZE_LEVEL to 1 during the upgrade which will adversely influence pl/sql operations (such as package creation, type compilation etc) and cause the ORA-600 [kksfbc-reparse-infinite-loop] during the upgrade. Solution Please use the following workaround: 1. Make sure that PLSQL_DEBUG is set to FALSE or removed from the init.ora/spfile of the 10g database prior to upgrade so it will default to FALSE. OR 2. Force the DBCA to use PLSQL_OPTIMIZE_LEVEL=2 $dbua -initParam plsql_optimize_level=2 ----- Note: ----- ORA-600 ORA-00600 Kzaxgfl Subject: Ora-00600: Internal Error Code, Arguments: [Kzaxgfl:Maxfiles], [32778], [], [], Doc ID: 755149.1 Type: PROBLEM Modified Date : 20-JAN-2009 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.4 to 10.2.0.5 This problem can occur on any platform. Symptoms In 10.2.0.4, when the number of XML audit files surpasses a certain number (+30000), the queries on v$xml_audit_trail or dba_common_audit_trail start to error out with errors like: ORA-00600: internal error code, arguments: [kzaxgfl:maxfiles] Removing the files from the audit_file_dest directory solves the problem for the moment. In time, however, if the files are not removed, the problem tends to reoccur. This problem is rarely seen on 32k bits systems, where the maxpid parameter is generally hardcoded to 32k. Cause The problem here is a structural limitation of Oracle 10.2.0.4. The error message has been introduced in 10.2.0.4, in order to fix a previous issue - when the limit was set at 1000 files. As a result of the fix for the 1000 files limitation, in 10.2.0.4 the database process can read up to 32k XML audit files. However, when the number of files is beyond 32k, the ORA-00600 is raised when querying v$xml_audit_trail. This limitation cannot be overcome in Oracle 10.2. Solution This a structural limitation of the 10g release. The solutions are to try to workaround this limitation: 1. control the number of XML files in the audit_file_dest directory, to avoid reaching them a number that would lead to the error above, by designing a backup/delete process of the audit information and audit files. When backing up the audit files, the adx_<SID>.txt file should be backed up with them and the file should be removed from the adump destination as part of the cleaning process. 2. limit the number of possible different PIDs by limiting the maxpid parameter. The limit has been completely removed in 11g References Bug 7516149 - ORA-00600 [KZAXGFL:MAXFILES] WHEN AUDIT_TRAIL=XML Keywords AUDIT_FILE_DEST ; DBA_COMMON_AUDIT_TRAIL ; ----- Note: ----- ORA-600 ORA-00600 25027 Subject: ORA-600 [25027] Errors When Attemping To Migrate 9.2 Database To 11g Using the DBUA Doc ID: 555866.1 Type: PROBLEM Modified Date : 30-MAY-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.7.0 to 11.0.1.6 This problem can occur on any platform. Symptoms When attempting to migrate a database from 9.2.0.7 to 11g using the DBUA, the migration fails and the database fails to open with the following error similar to the following: ORA-00600: internal error code, arguments: [25027], [0], [16783073], [], [], [], [], [] ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [25027], [0], [16783073], [], [], [], [], [] Error 704 happened during db open, shutting down database USER (ospid: 1724): terminating the instance due to error 704 The stack trace is similar to the following: ksedst1 <- ksedst <- dbkedDefDump <- dbgexPhaseII <- dbgexProcessError <- dbgePostErrorKGE <- 1124 <- kgeade <- kgeriv_int <- kgesiv <- ksesic2 <- krtd2abh <- kcbgtcr <- kqlbebs <- kqlblfc <- adbdrv <- opiexe <- opiosq0 <- kpooprx <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- main <- start Cause The default tablespace for the SYS and SYSTEM schemas are incorrectly defined. The default tablespace for the SYS and SYSTEM schemas needs to be the SYSTEM tablespace as well as the objects. Solution To implement the solution, please execute the following steps: 1. Ensure that the default tablespace for SYSTEM and SYS is the SYSTEM tablespace prior to the upgrade and the objects owned by SYS and SYSTEM are in the SYSTEM tablespace. This can be done by checking dba_users and dba_extents. a. First, check the default tablespace using the following query: SQL> select username, default_tablespace from dba_users where username in('SYS','SYSTEM'); USERNAME DEFAULT_TABLESPACE ------------------------------ ------------------------------ SYSTEM SYSTEM SYS SYSTEM b. Then, check for objects owned by SYS or SYSTEM in other tablespaces, no rows should return from the following query: SQL> select owner, segment_type, segment_name from dba_segments where owner in ('SYS','SYSTEM') 2 and tablespace_name <> 'SYSTEM' and segment_type <>'TYPE2 UNDO'; no rows selected c. If rows are returned, move the objects back into the SYSTEM tablespace. 2. Once the default tablespace and objects are set back to the SYSTEM tablespace, the DBUA should run fine. References Note 284433.1 - ORA-600 [25027] ----- Note: ----- Subject: ORA-7445 [__intel_fast_memcpy.A+14] When Inserting From an XMLTABLE() Doc ID: 567831.1 Type: PROBLEM Modified Date : 14-MAY-2008 Status: MODERATED Applies to: Oracle Server - Standard Edition - Version: 10.2.0.3.0 to 11.1 This problem can occur on any platform. Symptoms ORA-7445 [__intel_fast_memcpy.A+14] error occurs on INSERT from an XMLTABLE(). The call stack looks like: __intel_fast_memcpy __VInfreq__delini insbrp insrow insdrv inscovexe insExecStmtExecIniEngine insexe opiexe opipls ... or __intel_fast_memcpy insolev insbrp insrow insdrv inscovexe insExecStmtExecIniEngine insexe opiexe opipls ... It is possible that heap memory corruption errors may also be seen, such as: ORA-600 [kghfrempty:ds] ORA-600 [kghbigcasp:ds] Cause This is due to Bug 6487827 fixed in 11.1. No fix has yet been identified for this in previous releases as the INSERT code changed substantially in 11g, and so it has not been possible to identify the actual code change that fixed this. Solution Upgrade to 11g. References Bug 6487827 - ORA-7445 [__INTEL_FAST_MEMCPY.A+14] ERROR INSERTING INTO XMLTYPE() Keywords MEMORY~CORRUPTION; ----- Note: ----- ORA-600 ORA-00600 [3619] Subject: Unable to start RAC database due to ORA-600 [3619] Doc ID: 463963.1 Type: PROBLEM Modified Date : 14-MAY-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 10.1.0.0 to 10.2.0.4 This problem can occur on any platform. Symptoms Startup of RAC database fails due to ORA-00600 [3619] ALERT LOG Fri Oct 19 12:05:24 2007 Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE) Completed: ALTER DATABASE MOUNT Fri Oct 19 12:05:24 2007 ALTER DATABASE OPEN This instance was first to open Fri Oct 19 12:05:25 2007 Errors in file /opt/oracle/product/admin/pl01bko1/udump/pl01bko1_ora_2773136. trc: ORA-00600: internal error code, arguments: [3619], [27], [0], [], [], [], [], [] ORA-600 signalled during: ALTER DATABASE OPEN... ... Changes Simultaneous startup/shutdown of RAC instances. Cause This situation might occur due to some race condition when instances starting up and shutting down simultaneously. Instance recovery will be done during database open and while advancing the thread checkpoint the controlfile will be updated but not the file headers. The next instance to startup will find these files still need recovery and will raise the internal error. This issue is caused by unpublished bug 6059157 which will be fixed in 11g. Solution FIX Fixed in 11g. PATCH AVAILABILITY On some platforms there are patches for RDBMS release 10.2.0.3.0 available. Please check Metalink, if there's any patch available for your platform. WORKAROUND To fix the issue, manual recovery will be required after ORA-600 occurrence: SQL> connect / as sysdba SQL> startup mount SQL> recover database SQL> alter database open; References Keywords START~INSTANCE; RAC; CLUSTER_DATABASE; ----- Note: ----- ORA-00600 ORA-600 [kksfbc-reparse-infinite-loop] Subject: Summary of Bugs and Patches for ORA-600 [kksfbc-reparse-infinite-loop] Doc ID: 444985.1 Type: REFERENCE Modified Date : 01-APR-2008 Status: PUBLISHED In this Document Purpose Scope Summary of Bugs and Patches for ORA-600 [kksfbc-reparse-infinite-loop] ORA-600 [kksfbc-reparse-infinite-loop] Using LOB's ORA-600 [kksfbc-reparse-infinite-loop] During Upgrade ORA-600 [kksfbc-reparse-infinite-loop] After Installation of a Patch ORA-600 [kksfbc-reparse-infinite-loop] Using Partitions or With ORA-600 [17059] Other Bugs Dealing with ORA-600 [kksfbc-reparse-infinite-loop] What If These Bugs Do Not Apply To My Situation? Conclusion References Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4.0 to 10.2.0.3.0 Information in this document applies to any platform. Purpose A number of bugs have been filed that contain ORA-600 [kksfbc-reparse-infinite-loop]. This note summarizes many of the bugs filed, patches available, and offers workarounds and rediscovery information if it exists. It also categorizes the circumstances and product options this error may occur under to help you find the bug that best applies to your situation. Scope This article is a consolidated effort of other notes written about the same error. It is directed towards Oracle Support Analysts and Oracle Customers with the intention of summarizing and clarifying the different bugs filed for this problem. Summary of Bugs and Patches for ORA-600 [kksfbc-reparse-infinite-loop] ======================================================================================= ORA-600 [kksfbc-reparse-infinite-loop] Using LOB's Bug 4559728 Details of the bug: ORA-600 [17059] and ORA-600 [kksfbc-reparse-infinite-loop] can occur while operating on a view with lob columns if a dependent synonym of the view is dropped concurrently. Versions affected: 9.2.0.5, may affect versions up to and including 9.2.0.7, also affects 10.1.0.5 Fixed in releases: 9.2.0.8, 10.2.0.4, 11g Workaround: Do not issue DROP SYNONYM during SELECT. One-off Patch 4559728 is available for some versions and platforms. ======================================================================================= ORA-600 [kksfbc-reparse-infinite-loop] During Upgrade Bugs 3411348 and 4262668 can be encountered during upgrades. Unpublished Bug 3411348 Details of the bug: DML may intermittently fail with ORA-600 [kksfbc-reparse-infinite-loop]or dumps in kksfbc after "ALTER TABLE ___ UPGRADE" type DDL for objects referenced by the DML. Versions affected: Versions lower than 10.2, confirmed in 9.2.0.5 and 9.2.0.6 Fixed in releases: 9.2.0.7, 10.1.0.3, 10.2.0.1 Workaround: a. Recompile all relevant PL/SQL packages/views to reinitialize timestamps in dependency$. b. Upgrade to a version of the database where the problem is corrected. Rediscovery Information: Intermittent kksfbc-reparse-infinite-loop assert while doing DMLs, and there was an "ALTER TABLE ___ UPGRADE" previously. One-off Patch 3411348 is available for some versions and platforms. Unpublished Bug 4262668 Details of the bug: Upgrade from 9.0 to 10g can get invalid views and/or ORA-600 [kksfbc-reparse-infinite-loop] errors due to an incorrect timestamp on XMLType in the 9i database. Versions affected: Suspect versions greater than and equal to 10.1.0.2, confirmed in 10.1.0.4 Fixed in releases: 10.1.0.5, 10.2.0.1 Workaround: a. Upgrade to a database version where the issue is corrected. b. Possibly available with the assistance of Oracle Support. As with any solution that involves data dictionary modification, this option should only be pursued as a last resort. There is no guarantee modifying the data dictionary will resolve the problem, and it is possible it may corrupt the database. Rediscovery Information: a. 901 databases that have had a patch applied. b. The following SQL should show the mismatch if it exists. select distinct o.name, o.stime, d.p_timestamp from obj$ o, dependency$ d where o.stime != d.p_timestamp and o.type#=13 and o.obj#=d.p_obj# ; If the results show a difference in timestamps you may be encountering this bug. No one-off patch exists for this problem. ======================================================================================= ORA-600 [kksfbc-reparse-infinite-loop] After Installation of a Patch Unpublished Bug 2902335 Details of the bug: ORA-600 [KKSFBC-REPARSE-INFINITE-LOOP] when fixed view version is changed. Historically, all dependents of fixed views were invalidated if there was a version change when the database was started. This cannot be done for standby read-only databases. Now we invalidate dependents for fixed views only if the database is in migrate mode. Workaround: SQL> shutdown immediate SQL> startup migrate SQL>shutdown immediate SQL>startup (normal) This issue is not feasible to fix and no patch has been released. Note: This problem can also occur if the database was not patched or upgraded correctly, e.g. catpatch.sql was not run. If the problem continues after a database restart see the section titled, " What If These Bugs Do Not Apply To My Situation" for more troubleshooting information. ======================================================================================= ORA-600 [kksfbc-reparse-infinite-loop] Using Partitions or With ORA-600 [17059] Bugs 2707304, 2636685, 2626347, 5649326, and 6144489 can be encountered when using Partitioning. Bug 2707304 Details of the bug: Adding partitions to a partitioned IOT can cause problems such as ORA-600 [17059], ORA-600 [kqludp2], ORA-600 [KKSFBC-REPARSE-INFINITE-LOOP]. It can also cause "ALTER PACKAGE <package_name> COMPILE BODY" statements to fail with PLS-907 when the package depends on the PIOT. Version affected: Up to and including 9.0.1.4.0 and 9.2.0.2 Fixed in releases: 9.2.0.3, 10g Workaround: a. Alter package <package_name> compile; b. In the case of a view, compile the view. Rediscovery Information: 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. One-off Patch 2707304 is available for some versions and platforms. Bug 2636685 Details of the bug: Select on a view (based on a partitioned table) may hang/fail with get ORA-600 [17059] (or ORA-600 [kksfbc-reparse-infinite-loop]), after adding/dropping a list value to a partition of the base table. Version affected: Versions greater than and equal to 9.0.1, and less than 10g Fixed in releases: 9.2.0.3, 10g Workaround: Recompile the dependent (view). Rediscovery Information: After add/dropping a list value to a partition you get the following errors while accessing a view based on the above partitioned table: a. ORA-600 [17059] b. ORA-600 [kqludp2] c. ORA-600 [kksfbc-reparse-infinite-loop] 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. @ Please check Bug 2626347 for a similar problem. One-off Patch 2636685 is available for some versions and platforms. Bug 2626347 Details of the bug: This problem is introduced in 9.0.1.4 by the fix for Bug 1213768. This issue can only affect 8i where an interim fix for that bug has been installed. Adding/Splitting a partition can result in ORA-600 [17059], ORA-600 [kqludp2] or ORA-600 [kksfbc-reparse-infinite-loop] errors when subsequently accessing views which depend on the base table. Versions affected: 8.1.7.4, 9.0.1.4, 9.2.0.1 and 9.2.0.2 Fixed in releases: 8.1.7.5, 9.0.1.5, 9.2.0.3, 10g Workaround: Recompile the view (the dependent). Rediscovery Information: After splitting a partition by reusing the partition name you get the following errors while accessing a view based on the above partitioned table: a. ORA-600 [17059] b. ORA-600 [kqludp2] c. ORA-600 [kksfbc-reparse-infinite-loop] Note: For views running into this bug before the patch is applied, it's still necessary to recompile these views *after* the patch is applied. The following query issued in SQL as SYS (SYSDBA) can be used to find out which views need recompile: select obj#, owner#, name , to_char(ctime,'DD.MM.YY:HH24:MI:SS') ctime_view, to_char(mtime,'DD.MM.YY:HH24:MI:SS') mtime_view, to_char(stime,'DD.MM.YY:HH24:MI:SS') stime_view from obj$ o where obj# in (select d_obj# from dependency$ d where d.p_obj# in (select obj# from obj$ p where p.stime > d.p_timestamp and p.ctime <= d.p_timestamp)) and o.type#=4 and o.status <> 5;This query has shown the affected views in all cases tested. For new views or new partitioned tables created after patch application there is no further action needed. Unpublished Bug 6144489 (closed as a duplicate of Bug 5649326) Details of the bug: ORA-600 [kksfbc-reparse-infinite-loop] while running a query in a RAC setup. Bug 5649326 Details of the bug: ORA-600 [kksfbc-reparse-infinite-loop] while running a query. Versions affected: Filed against 10.2.0.2 Fixed in releases: 10.2.0.4 Workaround: Flush the shared pool. Rediscovery Information: a. ORA-600[KKSFBC-REPARSE-INFINITE-LOOP] b. KGLHDNORFINV set in parent handle c. Valid status of parent and dependent but invalid dependency d. DDL on partitioned object at remote node One-off Patch 5649326 is available for some versions and platforms. ======================================================================================= Other Bugs Dealing with ORA-600 [kksfbc-reparse-infinite-loop] Unpublished Bug 4632438 Details of the bug: ORA-00600 [kksfbc-reparse-infinite-loop] can occur when loading a new child cursor if the authorization check fails because of a translation mismatch. Versions affected: 10.2.0.1 and 10.1.0.x Fixed in releases: 10.2.0.2, 11g Workaround: Flush the shared pool and re-issue the statement or increase the shared pool size significantly. Note: The fix for unpublished Bug 4632438 introduced an issue documented in unpublished Bug 5106546. After applying the patch for Bug 4632438, an ORA-600 [15205] can occur if the patch was installed on top of a 10.1.x release. If you have encountered Bug 4632438 on 10.1.x as evident by the ORA-600 [15205], you should apply the two one-off patches below. If you have encountered Bug 4632438 on 10.2, you only need to apply the patch for Bug 4632438: One-off Patch 4632438 One-off Patch 5106546 ======================================================================================= What If These Bugs Do Not Apply To My Situation? In many cases this problem can be resolved by running utlrp.sql or flushing the shared pool: a. @ORACLE_HOME/rdbms/admin/utlrp.sql b. alter system flush SHARED_POOL; If you have recently upgraded or patched the database: a. ensure all of the post installation steps were completed b. verify the components are VALID with the following SQL: select comp_name, version, status from dba_registry order by comp_name; If the problem still exists contact Oracle Support. ======================================================================================= Conclusion At the time this article was written (July 2007), many of the bugs mentioned are already corrected in patchset releases. A majority of these patchsets are available with the exception of 10.2.0.4. If you suspect you are encountering one of these bugs, the first plan of action should be to upgrade to the latest patchset release available for the version and platform you are running. In cases where upgrading is not possible, patchset exceptions (one-off backport requests) are available for some platforms and versions already. More may be provided in the future. Patchset exceptions are not always provided for every database release requested and are subject to a review process. References Note 1213768.8 - Support Description of Bug 1213768 Note 138554.1 - ORA-600 [17059] Note 2626347.8 - Support Description of Bug 2626347 Note 2636685.8 - Support Description of Bug 2636685 Note 264061.1 - ORA-600 [kqludp2] "Unable to lock or pin dependent object" Note 2707304.8 - Support Description of Bug 2707304 Note 285705.1 - ORA-600 [kksfbc-reparse-infinite-loop] Note 285786.1 - ORA-600 [kqlupd2] Note 310290.1 - ORA-7445 (kksfbc) Note 3411348.8 - Bug 3411348 - OERI[kksfbc-reparse-infinite-loop] / dump [kksfbc] after ALTER TABLE .. UPGRADE Note 370914.1 - ORA-600 [15205] Note 3814658.8 - Bug 3814658 - Library cache is dumped everytime process signals OERI[kksfbc-reparse-infinite-loop] Note 404484.1 - ORA-600 [17003], ORA-600 [kksfbc-reparse-infinite-loop], ORA-600 [qmtcolcb_nomatch] After Failed Upgrade Note 4262668.8 - Bug 4262668 - Upgrade from 9.0 to 10g can get invalid views / OERI:kksfbc-reparse-infinite-loop Note 4559728.8 - Bug 4559728 - Select lob from view loops / OERI [17059] if synonym dropped Note 4632438.8 - Bug 4632438 - OERI[kksfbc-reparse-infinite-loop] can occur Note 5106546.8 - Bug 5106546 - OERI:15205 can occur with 10.1 fix for bug 4632438 ----- Note: ----- ORA-600 ORA-00600 [Xsocihandles] Subject: Ora-600[Xsocihandles] after killing a session Doc ID: 552729.1 Type: PROBLEM Modified Date : 08-FEB-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.3.0 This problem can occur on any platform. Symptoms After killing a session you can encounter ORA-00600 [XSOCIHANDLES]. Cause The ORA-600 is caused by Bug 5940486 fixed in 11g, no patch available. This issue is a minor one in that an ORA-600 happens when killing a session which is running a command under the PL/SQL call. Solution The ora-600 is generated because of Bug 5940486 fixed in 11g. The ora-600 here is occurring only because the session is being killed, and is of little concern. You need to focus on the process that is hanging rather than the error generated as a result of the kill. References Bug 5940486 - ORA-00600 [XSOCIHANDLES] IN __XML_SEQUENTIAL_LOADER WITH NO XML ----- Note: ----- ORA-00600 ORA-600 [KCFLGETLOCK40] Subject: ORA-600 [KCFLGETLOCK40] in ASM Instance and may Crash with ORA-00600 [504] Doc ID: 386896.1 Type: PROBLEM Modified Date : 28-NOV-2007 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.2 This problem can occur on any platform. Symptoms The following internal error may be signalled in an ASM instance ORA-00600: [kfclGetLock40], [5] Due to the above error , the ASM instance may crash with the error ORA-00600 [504]. ORA-600 [kfclGetLock40] Call Stack: kfclGetLock kfcGetBlockLock kfcReadBuffer kfcGet0 kfcGet1Priv kfcGetPriv kffbSetLimits kffbGetBlkPriv ORA-600 [504] Call Stack: ksesic7 ksl_level_check kslgetl kfclDoLazyCloses kfclDoDownConverts kjmsm ksbrdp Cause The cause of this ORA-600 [kfclGetLock40] is Bug 4709214 fixed in version 11g. Details : ORA-600 [kfclGetLock40] may be signalled from an ASM instance The cause of this ORA-00600 [504] is due to Bug 4709210 fixed in the version 11g. Details: LMS process in an ASM instance can crash the instance with error ORA-600[504] with kfclDoLazyCloses() on the call stack. Solution One Off Patches are available for the Bugs . Check Patch 4709210 for availability of patches for Bug 4709210 for your platform and Oracle version. Also search for merge patches containing the fix for Bug 4709214. References Bug 4709210 - ASM LMS ORA-600 [504], [0X2D94B5C8], [16], [4],[KFCL LE FREELIST], [1], [0] Bug 4709214 - ASM ORA-600 [KCFLGETLOCK40] Note 386897.1 - ASM instance may terminate by LMS with ORA-600 [504], [0X2D94B5C8], [16], [4],[KFCL LE FREELIST] ----- Note: ----- Subject: Register 9.2.0.7 Database In 11g Catalog Fails With Oeri[17069] And Ora-04028 Doc ID: 780101.1 Type: PROBLEM Modified Date : 04-FEB-2009 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.7 This problem can occur on any platform. Symptoms Register of 9207 target database with 11.1.0.7 catalog failed with error message ORA-00600: internal error code, arguments: [17069], RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of register command on default channel at 01/13/2009 15:33:05 RMAN-10015: error compiling PL/SQL program RMAN-10033: error during compilation of job step 1: ORA-00600: internal error code, arguments: [17069], [0x80000001007A70E0], [], [], [] Cause Its because of the limitation of virtual catalog . Virtual catalog is a new feature of 11g . Solution If the recovery catalog is a virtual private catalog, then the RMAN client connecting to it must be at patch level 10.1.0.6 or 10.2.0.3. Oracle9i RMAN clients cannot connect to a virtual private catalog. This version restriction does not affect RMAN client connections to an Oracle Database 11g base recovery catalog, even if it has some virtual private catalog users. If the target database is not comatable with the virtual catalog then diretly register the database with the actual catalog database. ----- Note: ----- ORA-00600 ORA-600 [kzsviver:1] Subject: ORA-600 [kzsviver:1] ERROR ON SETTING A USERS PASSWORD Doc ID: 554605.1 Type: PROBLEM Modified Date : 16-OCT-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.6 This problem can occur on any platform. Symptoms ORA-600 [kzsviver:1] possibly followed by ORA-600 [kks-hash-collision] errors can occur when trying to set a users password via SQL or PL/SQL scripts using the "CREATE/ALTER USER ... IDENTIFIED BY VALUES ..." command syntax if a null password value, e.g. an empty string '', is used. Changes The code is being executed in Oracle11g, and works successfully in previous releases. Cause This is due to unpublished bug:6755379 as identified in Bug 6833049, and was deemed as expected behaviour by development due to the use of unsupported command syntax as the use of the 'IDENTIFIED BY VALUES' clause on a CREATE/ALTER USER statement is not officially documented, and is intended purely for internal use by the export/import utilities within the Oracle RDBMS. Therefore it was deemed appropriate for this to raise an internal error as opposed to a user error as encountering a null password string would otherwise not be possible. Additionally the use of export/import for general use is desupported in Oracle11g. Solution Ensure that users have none null passwords defined and don't use the "ALTER USER ... IDENTIFIED BY VALUES ..." command syntax which is not officially documented and therefore not supported, and may cease to work in a future Oracle RDBMS version. In 11g, the new hash value is stored in the USER$.SPARE4 column, see Note 429465.1, if existing passwords must be migrated, make sure to make no errors in transferring this value to avoid this internal error. References Bug 6833049 - ORA-600 [KZSVIVER:1] AND ORA-600 [KKS-HASH-COLLISION] CHANGING PASSWORDS Note 429465.1 - 11g R1 New Feature : Case Sensitive Passwords and Strong User Authentication Note 1051962.101 - Restoring a user's original password Keywords IMPORT~UTILITY ; ----- Note: ----- ORA-00700 ORA-700 Subject: ORA-700 Soft Internal Errors in 11g Doc ID: 737878.1 Type: FAQ Modified Date : 24-OCT-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 11.1.0.6 to 11.1.0.8 Information in this document applies to any platform. Purpose The purpose of this document is to explain the new Soft Internal Error code "ORA-700" that is introduced in the 11g RDBMS. Questions and Answers 1) What are ORA-700 errors? 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. Soft asserts are triggered when the caller wants to make a note of the fact that something unexpected has happened, but would like to continue on because the failure is not fatal to the process or the instance. In such cases, the process just records the error, takes the corresponding dumps and moves on as though nothing happened. 2) Are ORA-700 errors similar to ORA-600 in 10g? Yes, ORA-700 errors separate less harmful ORA-600 errors from the ones that cause huge impact like instance failures. For example, if the code finds that a hint in a query is corrupt, it can just raise a soft-assert since the query can be run without the hint being used, and so doesn't need to crash the process. So in 11g, for such a condition an ORA-700 error would be raised. General Format of ORA-700 error is: ORA-00700: soft internal error, arguments: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s] e.g.: ORA-700: soft internal error, arguments: [kgeade_is_0], [], [], [], [], [], [], [] References Oracle® Database Error Messages 11g Release 1 (11.1) Note 453125.1 - 11g Diagnosability: Frequently Asked Questions Note 461960.1 - How to ask for Diagnostic Information To Support Keywords km ; ----- Note: ----- ORA-00600 ORA-600 504 Subject: ORA-00600[504] [RESMGR:PLAN CPU METHOD] Doc ID: 467774.1 Type: PROBLEM Modified Date : 10-FEB-2009 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 10.2.0.3 This problem can occur on any platform. Symptoms Following error may lead to database hang: ORA-00600: internal error code, arguments: [504], [0x70000008EAFE2C8], [160], [7], [resmgr:plan CPU method], [2], [0], [0x7000000100E6EF8] Error is reported on : "resmgr:plan CPU method" latch Call Stack ksl_level_check kslgetsl ksfglt kgkplopicknext kgskgnextcl kgskgnextthr kgskrunnext kgskbwt kskthbwt kslges kslgetl ksfglt kglsim_unpin_simhp_ new kglsim_unpin_simhp kghupr_flg kglpndl Cause Bug 5176098 (Unpublished) which is fixed in 11G and 10.2.0.4 version of Oracle Database software. The latch hierarchy violation is that we have "Child shared pool" latch, which is level 7. We request for "resmgr:plan CPU method" latch, which is also level 7, and we assert. Solution This bug affects all versions (before 11.1 and 10.2.0.4) that uses the Resource Manager. Check for the availability of one-off Patch 5176098 for your platform on MetaLink. There is no Workaround available for the error. ----- Note: ----- ORA-00600 [12870] ORA-00600: internal error code, arguments: [12870] Subject: ORA-00600 [12870], [kkdlgon: waited too long for object id] If Many Concurrent Sessions Need New Object IDs Doc ID: 460516.1 Type: PROBLEM Modified Date : 13-JAN-2009 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.6 to 11.1.0.6 This problem can occur on any platform. Symptoms 1. Many of the following errors are seen in the alert log and tracefiles: ORA-00600: internal error code, arguments: [12870], [kkdlgon: waited too long for object id], [], [], [], [], [], [] 2. Several concurrent sessions are being run that are asking for a large number of new object_ids. This was observed when an application report would first create temporary tables with a large number of partitions. Five of the reports were running concurrently. One created 80 partitions; the other 4 reports created 20-30 partitions each. 3. The call stack may resemble the following: ksedmp ksfdmp kgeriv kgesiv ksesic1 kkdlgon kkdlcob ctcdrv Cause The error is caused by unpublished Bug 5343815. In Oracle RDBMS versions lower than 11.1, a session attempting to perform a DDL operation (such as create a new table or index or add a partition to an existing table or index) may encounter ORA-600:[12870],[KKDLGON: WAITED TOO LONG FOR OBJECT ID] if a large number of other sessions are concurrently attempting to perform DDL operations requiring use of new object ids. Solution 1. Upgrade to 11g. 2. Workaround for versions 10.2.0.4 and above: Set the hidden parameter to a value greater than 20000, which is the default. This parameter sets the number of times a session will wait before asserting an error: "_kkdlgon_max_iter" = <value_higher_than_20000>; 3. Workaround for versions lower than 10.2.0.4 Reduce the number of consecutive sessions that are attempting to perform DLL operations needing new object ids. ----- Note: ----- ORA-600 ORA-00600 [qctVCO:csform] http://www.oraclerant.com/?p=15=1 Oracle Rant Thomas Roach is an Oracle DBA in the Tampa Bay area. Solutions for ORA-00600: internal error code, arguments: [qctVCO:csform], [0], [0], [0], [0], [1], [1], [0] November 14, 2007 at 6:46 pm · Filed under Oracle Errors ORA-00600: internal error code, arguments: [qctVCO:csform], [0], [0], [0], [0], [1], [1], [0] We got this error in Oracle 10g. A little about our environment. This is 10.2.0.3 and we are using Transparent Data Encryption (TDE). I found on metalink that there is a bug (see note Note:406958.1) with Complex View Merging and Transparent Data Encryption (TDE). The fix was to set _complex_view_merging=false or upgrade to 11g. The problem with this approach is that Oracle is not able to efficiently rewrite queries using Complex View Merging and the upgrade to 11g will introduce some risks. Queries that should take seconds may now take minutes due to disabling Complex View Merging. I found a better work around. Do not set _complex_view_merging=false. If you did, set it back to true. Find the offending view that is causing the problem and build it with the /*+ no_merge */ hint. For example: CREATE OR REPLACE FORCE VIEW V_TEST_VIEW AS SELECT DISTINCT fi.provider_id as fi_id , co.provider_id as co_id , ag.provider_id as ag_id Instead, do this: CREATE OR REPLACE FORCE VIEW V_TEST_VIEW AS SELECT /*+ no_merge */ DISTINCT fi.provider_id as fi_id , co.provider_id as co_id , ag.provider_id as ag_id And there you go. You still get Complex View Merging except on views that contain columns that are encrypted by TDE. ----- Note: ----- ORA-600 ORA-00600 [16201] http://it.toolbox.com/blogs/david/ora600-16201-when-dropping-a-procedure-20051 Life as a DBA by David Yahalom (Senior Project Manager) Blog Main / Archive / Invite Peers / Connect to this blog Previous Entry / Next Entry ORA-600 [16201] when dropping a procedure David Yahalom (Senior Project Manager) posted 10/28/2007 | Comments (0) In certain older versions of Oracle database (such as 8.1.7.4 like this case) you may receive an ORA-600 error when trying to drop or recompile a database PL/SQL package or procedure. Usually when the source is wrapped. SQL> drop procedure schema.proc_name; * ERROR at line 1: ORA-00600: internal error code, arguments: [16201], [], [], [], [], [], [], [] SQL> create or replace procedure schema.proc_name as begin end; / * ERROR at line 1: ORA-00600: internal error code, arguments: [16201], [], [], [], [], [], [], [] This is a documented Oracle bug (No. 2422726). It affects Oracle versions 8.1.7.4, 9.0.1.4, 9.2.0.1 and fixed in Oracle 9.2.0.2 and 10g. However, even if you are running an older version of Oracle there's a possible workaround available to solve this issue. Note, this is an ugly hack, but it works, and sometimes your only solution for this annoying problem. The solution is as follows: 1) Connect as SYS to the problematic db. 2) Run the following query to identify the object# of the INVALID object you can't drop. SQL> select obj#,owner#,type# from sys.obj$ where name = 'PROC_NAME'; OBJ# OWNER# TYPE# ---------- ---------- ---------- 1396504 5 7 3) Now try and select the procedure from v$procedure using the OBJ# from the above query. SQL> select * from procedure$ where obj# in (1396504); no rows selected 4) You can't. That's because of the above mentioned bug. 5) The only way to fix this is to insert a fake row into the procedure$ view to fool Oracle to allow you to successfully drop the procedure. SQL> insert into procedure$ values (1396504, '-----------------------',NULL,2); 1 row created. SQL> commit; Commit complete. 6) Now you can successfully drop the INVALID procedure. SQL> drop procedure schema.proc_name; Procedure dropped. As I said, it's a hack, so you are better of upgrading your Oracle installation to a version not effected by this bug. But as we all know, many times this is simply not an option. And for those occasions the solution I've written here seems to be the only one. Good luck! David Yahalom Senior Project Manager, CTO ----- Note: ----- ORA-00600 ORA-600 [ktspgetmyb-1] Subject: ORA-600 [ktspgetmyb-1] When Inserting Into a Table Doc ID: 330928.1 Type: PROBLEM Modified Date : 07-JAN-2009 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 10.2.0.2 This problem can occur on any platform. Symptoms When inserting into a table in an ASSM (automatic segment space management) tablespace, the following error is raised: ORA-00600: internal error code, arguments: [ktspgetmyb-1], [], [], [], [], The problem can also be seen for updates. Changes Previously, a truncate of the table in question was interrupted - either deliberately by hitting Ctrl-C, or due to a client crash etc. Cause This problem is addressed in Bug 3279497. By interrupting a truncate command, the extent bitmap will be left in an inconsistent state. This will result in a problem when an extent switch is required (ie. when the current extent is full) and the ORA-600 [ktspgetmyb-1] is raised. Solution To resolve the problem, the table needs to be truncated (to reset the extent bitmap). If the data in the table are required, then export the data first (or create a new table to hold the contents), then truncate the table, and import (or insert) the table data again. Since the problem will only be hit after interrupting a truncate command, then avoiding this will also prevent the error in the future. The bug is fixed in 11g, and the fix is included in the 9.2.0.8, 10.1.0.5, and 10.2.0.3 patchsets as well. Availability of one-off patches for earlier versions can be checked via Patch 3279497. Note that Bug 3279497 was previously marked as fixed in 10.2.0.1. References Bug 3279497 - INSERT CAUSES ORA-600[KTSPGETMYB-1] AFTER TRUNCATE CTL+C Keywords ASSM ; AUTOMATIC~SEGMENT~SPACE~MANAGEMENT ; ----- Note: ----- http://www.ora600.net/node/126 ORA-845 ORA-00845 ORA-00845: MEMORY_TARGET not supported on this system Submitted by kurtvm on Wed, 01/14/2009 - 06:41. Problem Description While creating a startup database using dbca the database creation GUI gives error message in a pop up window, ORA-00845: MEMORY_TARGET not supported on this system from where you can ignore the error message. The similar scenario also occur whenever you try to start your database then startup shows error message like below. SQL> STARTUP ORA-00845: MEMORY_TARGET not supported on this system Cause of the Problem •Starting from Oracle 11g the automatic memory management feature is now defined with parameter MEMORY_TARGET and MEMMORY_MAX_TARGET. •On linux file system the shared memory need to be mounted on /dev/shm directory on the operating system. •And the size of /dev/shm needs to be greater than MEMORY_TARGET or MEMMORY_MAX_TARGET. •The AMM (Automatic Memory Management) now in 11g manages both SGA and PGA together by MMAN process. •The MEMORY_TARGET parameter in 11g comes for (SGA_TARGET+PGA_AGGREGATE_TARGET) which was in 10g. •And MEMORY_MAX_TARGET parameter in 11g comes instead of SGA_MAX_TARGET parameter which was in 10g. •The ORA-00845:can arises for the following two reasons on linux system. 1)If the shared memory which is mapped to /dev/shm directory is less than the size of MEMORY_TARGET or MEMORY_MAX_TARGET. or, 2)If the shared memory is not mapped to /dev/shm directory. Solution of the Problem Make sure /dev/shm is properly mounted. You can see it by, df -h The output should be similar like $ df -k Filesystem Size Used Avail Use% Mounted on ... shmfs 1G 512M 512M 50% /dev/shm We see here for /dev/shm we have assigned 1G memory. Now if you set MEMORY_TARGET more than 1G then above ORA-845 will arise. For example if you have MEMORY_TARGET or MEMORY_MAX_TARGET set to 12G then you can mount shared memory to 13g like below. As a root user, # mount -t tmpfs shmfs -o size=13g /dev/shm In order to make the settings persistence so that it will affect after restarting machine add an entry in /etc/fstab similar to the following: shmfs /dev/shm tmpfs size=13g 0 ----- Note: ----- http://askdba.org/weblog/?p=106 ORA-600 ORA-00600 [12333] ORA-00600 with [12333] is an error that I have encountered on multiple occasions. This post is to shed some light on what this error is all about. To start with let us try to understand when does oracle report ora-00600 error. An ora-00600 error is raised in the exception handler section of Oracle’s c-program code. i.e. Coders have forseen certain exceptional situation that are potential threats to data integrity or memory integrity and written appropriate exceptional handlers to report a ora-00600 error with appropriate information about the exception condition. Details like [12333] indicate or provide hints as to what caused the exception. ora-00600 [12333] is reported when the server recieves data from a client and the server cannot recognize the data format. This error mostly is because of issues with network and does not indicate any data corruption. Few Common Causes & Suggestions: 1. An incompatible client software can cause such an internal error. Metalink document 207303.1 explains the supported combinations of clients and Server release. 2. An incompatible NLS settings on Client. Check NLS settings especially ORA_NLS33 for 9i, ORA_NLS10 for 10g. 3. Apart from this, it could be because of network issues, client software, TIMEOUT setting, etc. Try to narrow down the error to a particular client machine/ client software. 4. This can be because of an Oracle bug also. Refer to metalink document 428629.1 for list of known bugs with ora-00600 [12333]. As a last resort you can check this with Oracle Support for any new issues. ----- Note: ----- ORA-00600: internal error code, arguments: [kturrur11], [65535], [0], [], [], [], [], [] Affects versions <= 10.2.0.2 Bug 4940513 OERI[kturrur11] can occur with multi block undo This note gives a brief overview of bug 4940513. Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions < 11 Versions confirmed as being affected * 9.2.0.6 * 9.2.0.7 * 10.1.0.4 * 10.1.0.5 * 10.2.0.2 Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in * 9.2.0.8 (Server Patch Set) * 10.2.0.3 (Server Patch Set) * 11g (Future version) Symptoms: Related To: * Internal Error May Occur (ORA-600) * ORA-600 [kturrur11] * (None Specified) Description In rare situations the server could raise ORA-600 [kturrur11][65535][0] Workaround: Avoid the multi block undo code path by making sure that the block size in the undo tablespace is large enough to accomodate the largest column that is changed by any SQL statement. If the block size of the data tablespaces is larger than the block size of the undo tablespace, increase the blocksize of the undo tablespace to that of the data tablespace. ----- Note: ----- ORA-600 ORA-00600 [16305] Note 1: ------- Subject: ORA-600 [16305] "Failed to allocate network NS context for MTS dispatcher" Doc ID: 106601.1 Type: REFERENCE Modified Date : 06-OCT-2005 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: Check for any additional errors and address those first. 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# 3752301 See Note 3752301.8 OERI:16305 at startup if unresolvable node in invited nodes list Fixed: 9.2.0.7, 10.1.0.4, 10.2.0.1 Note 2: ------- Subject: ORA-600 [16305] While Starting Up the Database Doc ID: 405602.1 Type: PROBLEM Modified Date : 30-APR-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.1.0.3 This problem can occur on any platform. The SQLNET.ORA may contain any one or a combination of the following: 1. protocol.validnode_checking=yes 2. protocol.invited_nodes= (hostname | ip_address) 3. leading spaces before a specified parameter Symptoms You may be encountering one of the following problems while trying to start the database. 1. A single ORA-600 error: ORA-600 [16305] 2. A combination of ORA-600 errors: ORA-600 [16305] ORA-600 [16388] 3. A combination of an ORA-600 error with other Oracle errors: ORA-600 [16305] ORA-24324: service handle not initialized ORA-24323: value not allowed ORA-3113: end-of-file on communication channel 4. Or, the following errors while trying to start the listener: TNS-12532: TNS:invalid argument TNS-12560: TNS:protocol adapter error TNS-502: Invalid argument 5. Shutdown normal and immediate may hang. Only a shutdown abort is successful. Changes 1. Security Patch #68 may have been recently applied. 2. The sqlnet.ora may have been recently modified. Cause 1. The cause of the problem is unpublished Bug 3752301. Details: If tcp.validnode_checking is yes and tcp.invited_nodes includes an unresolvable host, PMON and dispatchers will not start presenting the following errors: ORA-600[16305] Workaround: Correct invited_nodes parameter not to have unresolvable hosts. 2. This problem has also been documented in Bug 4110378 "Sqlnet.Ora With Leading Spaces In Parameter Names Causes Shutdown To Hang", closed as a duplicate of Bug 3752301. Solution Any one of the following solutions may resolve the problem: 1. Upgrade the database. This problem has been corrected in database versions 9.2.0.7, 10.1.0.4, and 10.2.0.1. 2. Check the sqlnet.ora located in $ORACLE_HOME/network/admin or in the TNS_ADMIN location for leading spaces in front of parameters. 3. Verify all hosts in protocol.invited_nodes do not have unresolvable hosts listed. 4. Comment out the parameters protocol.validnode_checking and protocol.invited_nodes. 5. Set protocol.validnode_checking = no in the sqlnet.ora file. 6. Apply one-off Patch 3752301 if available for your platform/version from MetaLink. Note 3: ------- Old stuff: Subject: ORA-600 [16305] / ORA-600 [16388] on Startup After Installation of Security Patch #68 Doc ID: 291211.1 Type: PROBLEM Modified Date : 12-JAN-2005 Status: PUBLISHED The information in this document applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.5 to 9.2.0.5 This problem can occur on any platform. After installing Security Patch #68, customer attempts to restart the database and fails with errors ORA-600 [16305] and ORA-600 [16388]. Database may not be started. Symptoms -shared servers are enabled -customer is using sql*net validnode_checking feature Cause ORA-600 [16305] error indicates a problem initializing shared servers. When security patch #68 is installed, checking of valid/invalid nodes becomes more rigorous and the existence of an invalid node in the invited nodes list will cause this failure in the shared server initialization routine. The ORA-600 [16388] error is actually a side-effect of the ORA-600 [16305] error and does not need to be addressed directly; it is resolved when the first error is resolved. Fix Short-term: disable validnode verification: set {protocol}.validnode_checking = no in the protocol.ora files. Longer-term: identify and remove the invalid nodes from the invited nodes list in the protocol.ora file. Note 4: ------- Subject: ORA-600 [16305] Caused Database To Crash Doc ID: 333907.1 Type: PROBLEM Modified Date : 16-JUL-2008 Status: MODERATED Applies to: Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 10.2.0.1 This problem can occur on any platform. Symptoms In the alert log is reported: ORA-00600: codigo de error interno, argumentos: [16305], [], [], [], [], [] and Pmon terminated the Instance. The call stack is: kmmini ksucln ksbrdp opirip opidrv Cause The cause of this problem has been identified and verified in the unpublished Bug 3752301. It is caused by network problems: if tcp.validnode_checking is yes and tcp.invited_nodes includes an unresolvable host, PMON and dispatchers will not start presenting the following errors: ORA-600[16305] Others possible causes - problems with MTS - networking problems with TCP protocol. - TCP.INVITED_NODES in the "protocol.ora" is not working (Note 3752301.8) - Leading blank characters inside sqlnet.ora Solution To fix the issue: 1. check system error logs for network issues 2. check the SQL*Net configuration files for errors (blank characters inside) 3. check if invited_nodes parameter not to have unresolvable hosts. 4. upgrade to 10.2 release or apply 10.1.0.4 patchset where the unpublished Bug 3752301 is fixed References Note 3752301.8 - Bug 3752301 - OERI:16305 at startup if unresolvable node in invited nodes list ----- Note: ----- ORA-00600 Ora-600 [Kfiotranslateio01] Subject: Ora-600[Kfiotranslateio01], [5], [1823] and All 4 RAC Instances Crashed Doc ID: 438468.1 Type: PROBLEM Modified Date : 18-DEC-2008 Status: PUBLISHED Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 This problem can occur on any platform. Symptoms RAC instances crashed with ORA-00600 [kfioTranslateIO01], [5],[1823]. STACK: kfioTranslateIO kfioRqSetPrepare kfioSubmitIO kfioRequest ksfd_osmio Changes The error reproduced when a script was ran to create 86 tablespaces. Cause Bug 5717578 fixed in 11g. Because of a race between a file size refresh and a file resize operation, DB instance may incorrectly observe a file shrinkage and encounters ORA-600 in the ASMB process. Solution This problem occurs most likely because you have turned on auto-extent and uses the default auto-extent size or a small auto-extent size. The best way to handle this issue in 10.2 is to set a larger auto-extent size, eg. 100MB or more. This way the problem can be avoided. References Bug 6133281 - ALL RAC INSTANCES CRASHED WITH ORA-600[KFIOTRANSLATEIO01], [5], [1823] #################################################################################################### SECTION 5: Other errors related to backup / recovery: #################################################################################################### Article 1. Oracle Article. Recover a datafile with missing archivelogs Subject: RECOVER A DATAFILE WITH MISSING ARCHIVELOGS Doc ID: Note:418476.1 Type: PROBLEM Last Revision Date: 23-NOV-2007 Status: REVIEWED In this Document Symptoms Cause Solution Applies to: Oracle Server - Enterprise Edition - Version: 8.1.7.4.0 to 10.2.0.4 This problem can occur on any platform. Symptoms Database cannot be opened, because a datafile checkpoint is lagging behind from the rest of the datafiles. Cause A datafile was restored from a previous backup, but archivelogs required to recover the said datafile are missing. Solution There are 3 options available, as shown below: Option#1: Restore the database from the same backupset, and then recover it by applying up to the last available archivelog to roll it forward, but any updates to the database after the point-in-time of recovery will be lost. Option#2: Force open the database by setting the _ALLOW_RESETLOGS_CORRUPTION=TRUE in the init.ora. But there is no 100% guarantee that we can open the database. However, once the database is opened, then you must immediately rebuild the database. Database rebuild means doing the following, namely: (1) perform a full-database export, (2) create a new and separate database, and finally (3) import the recent export dump. Option#3: Manually extract the data using the Oracle's Data Unloader (DUL), which is performed by Oracle Field Support on-site for an extra charge. Note by Antapex: never rely completely on your physical backup. Make sure you have a good and recent export of the database as well. If you make use of exp (or imp) in combination with mknod to create a pipe, and using gzip or compress, you can typically create small exports from even quite large databases. For example, a 500GB database can be exported to a 25GB exportfile. As an example, a script could contain code like: Create a compressed export on the fly. # create a named pipe mknod exp.pipe p # read the pipe - output to zip file in the background gzip < exp.pipe > scott.exp.gz & # feed the pipe exp userid=scott/tiger file=exp.pipe Article 2. TEST: Incomplete Recovery to a point in time: up to a certain SCN Suppose we have target database test10g Suppose we have the rman catalog in database rman Suppose we have user "albert" in test10g which has created the table PERSON. At this moment there were NO BACKUPS taken: SQL> select * from person; PERS_ID PERS_NAME ---------- --------------------- 1 db was never gebackupped 2 before 1st backup The SCN at that time is 549794. But ofcourse the SCN is always increasing. >>> Now we run our first backup: run { allocate channel t1 type disk; backup full database ; backup (spfile) (current controlfile) ; sql 'alter system archive log current'; backup archivelog all delete input ; release channel t1; } Some time after the backup, albert does an insert. SQL> select * from person; PERS_ID PERS_NAME ---------- ---------------------------- 1 db was never gebackupped 2 before 1st backup 3 after 1ste backup >>> Now we run our second backup: run { allocate channel t1 type disk; backup full database ; backup (spfile) (current controlfile) ; sql 'alter system archive log current'; backup archivelog all delete input ; release channel t1; } Some time after the second backup, albert does an insert. SQL> select * from person; PERS_ID PERS_NAME ---------- ---------------------------- 1 db was never gebackupped 2 before 1st backup 3 after 1ste backup 4 after 2nd backup >>> Now we run our third backup: run { allocate channel t1 type disk; backup full database ; backup (spfile) (current controlfile) ; sql 'alter system archive log current'; backup archivelog all delete input ; release channel t1; } SQL> SELECT DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER() from dual; DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER() ----------------------------------------- 572936 Now we want to restore to SCN where there were only two records in the PERSON table: The target instance of database "test10g" is started, but not mounted or opened. RMAN> run { 2> allocate channel t1 type disk; 3> set until scn 549794; 4> restore controlfile; 5> alter database mount; 6> restore database ; 7> recover database ; 8> release channel t1; 9> alter database open resetlogs; 10> } allocated channel: t1 channel t1: sid=156 devtype=DISK executing command: SET until clause Starting restore at 27-JUN-08 released channel: t1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 06/27/2008 23:10:43 RMAN-06026: some targets not found - aborting restore RMAN-06024: no backup or copy of the control file found to restore Because we also tried to restore the controlfile, at SCN=549794, rman tells us that there is no backup at that specific SCN. Lets see if we can find an SCN "close" to what we want. RMAN> list backup of controlfile; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 47 Full 6.80M DISK 00:00:03 27-JUN-08 BP Key: 49 Status: AVAILABLE Compressed: NO Tag: TAG20080627T103023 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T103023_469DWKVT_.BKP Control File Included: Ckp SCN: 549830 Ckp time: 27-JUN-08 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 61 Full 6.77M DISK 00:00:02 27-JUN-08 BP Key: 65 Status: AVAILABLE Compressed: NO Tag: TAG20080627T103209 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCNNF_TAG20080627T103209_469DWV0Z_.BKP Control File Included: Ckp SCN: 549850 Ckp time: 27-JUN-08 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 114 Full 6.80M DISK 00:00:03 27-JUN-08 BP Key: 122 Status: AVAILABLE Compressed: NO Tag: TAG20080627T104611 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T104611_469FT57B_.BKP Control File Included: Ckp SCN: 550283 Ckp time: 27-JUN-08 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 137 Full 6.77M DISK 00:00:02 27-JUN-08 BP Key: 141 Status: AVAILABLE Compressed: NO Tag: TAG20080627T104755 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCNNF_TAG20080627T104755_469FTDJM_.BKP Control File Included: Ckp SCN: 550302 Ckp time: 27-JUN-08 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 203 Full 6.80M DISK 00:00:03 27-JUN-08 BP Key: 210 Status: AVAILABLE Compressed: NO Tag: TAG20080627T111308 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T111308_469HDDYR_.BKP Control File Included: Ckp SCN: 551014 Ckp time: 27-JUN-08 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 228 Full 6.77M DISK 00:00:02 27-JUN-08 BP Key: 232 Status: AVAILABLE Compressed: NO Tag: TAG20080627T111442 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCNNF_TAG20080627T111442_469HDN5C_.BKP Control File Included: Ckp SCN: 551032 Ckp time: 27-JUN-08 RMAN> So lets try the restore with SCN=549830 RMAN> run { 2> allocate channel t1 type disk; 3> set until scn 549830; 4> restore controlfile; 5> alter database mount; 6> restore database ; 7> recover database ; 8> release channel t1; 9> alter database open resetlogs; 10> } allocated channel: t1 channel t1: sid=156 devtype=DISK executing command: SET until clause Starting restore at 27-JUN-08 channel t1: starting datafile backupset restore channel t1: restoring control file channel t1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T103 23_469DWKVT_.BKP channel t1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T103023_469DWKVT_.BKP tag=TAG 0080627T103023 channel t1: restore complete, elapsed time: 00:00:05 output filename=C:\ORACLE\ORADATA\TEST10G\CONTROL01.CTL output filename=C:\ORACLE\ORADATA\TEST10G\CONTROL02.CTL output filename=C:\ORACLE\ORADATA\TEST10G\CONTROL03.CTL Finished restore at 27-JUN-08 database mounted Starting restore at 27-JUN-08 Starting implicit crosscheck backup at 27-JUN-08 Crosschecked 1 objects Finished implicit crosscheck backup at 27-JUN-08 Starting implicit crosscheck copy at 27-JUN-08 Finished implicit crosscheck copy at 27-JUN-08 searching for all files in the recovery area cataloging files... cataloging done List of Cataloged Files ======================= File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_ANNNN_TAG20080627T103227_469DXG4D_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_ANNNN_TAG20080627T104805_469FTQ6T_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_ANNNN_TAG20080627T111453_469HDYYR_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCNNF_TAG20080627T103209_469DWV0Z_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCNNF_TAG20080627T104755_469FTDJM_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCNNF_TAG20080627T111442_469HDN5C_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T103023_469DWKVT_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T104611_469FT57B_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NCSNF_TAG20080627T111308_469HDDYR_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNNDF_TAG20080627T104611_469FQ48S_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNNDF_TAG20080627T111308_469H9OK2_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNSNF_TAG20080627T103209_469DWZ5C_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNSNF_TAG20080627T104755_469FTGQX_.BKP File Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNSNF_TAG20080627T111442_469HDPF5_.BKP channel t1: starting datafile backupset restore channel t1: specifying datafile(s) to restore from backup set restoring datafile 00001 to C:\ORACLE\ORADATA\TEST10G\SYSTEM01.DBF restoring datafile 00002 to C:\ORACLE\ORADATA\TEST10G\UNDOTBS01.DBF restoring datafile 00003 to C:\ORACLE\ORADATA\TEST10G\SYSAUX01.DBF restoring datafile 00004 to C:\ORACLE\ORADATA\TEST10G\USERS01.DBF restoring datafile 00005 to C:\ORACLE\ORADATA\TEST10G\TEST01.DBF channel t1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNNDF_TAG20080627T103 23_469DSJF5_.BKP channel t1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_NNNDF_TAG20080627T103023_469DSJF5_.BKP tag=TAG 0080627T103023 channel t1: restore complete, elapsed time: 00:01:25 Finished restore at 27-JUN-08 Starting recover at 27-JUN-08 starting media recovery channel t1: starting archive log restore to default destination channel t1: restoring archive log archive log thread=1 sequence=11 channel t1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_ANNNN_TAG20080627T103 27_469DXG4D_.BKP channel t1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_27\O1_MF_ANNNN_TAG20080627T103227_469DXG4D_.BKP tag=TAG 0080627T103227 channel t1: restore complete, elapsed time: 00:00:01 archive log filename=C:\ORACLE\ORADATA\LOG\ARC00011_0658480420.001 thread=1 sequence=11 media recovery complete, elapsed time: 00:00:02 Finished recover at 27-JUN-08 released channel: t1 database opened new incarnation of database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN> Now we return to database test10g. SQL> select * from person; PERS_ID PERS_NAME ---------- --------------------- 1 db was never gebackupped 2 before 1st backup SQL> SQL> SELECT DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER() from dual; DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER() ----------------------------------------- 553255 Article 3. TEST: Incomplete Recovery to a point in time: up to a certain SCN This example is quite similar to the example above. But there is a difference. This time, we have set the following default in rman: RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS; This will mark all backups older than one day as obsolete. Now in this example we are going to test if we still can use a backup that’s several days old. Lets first list our backups: RMAN> list backup of database; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 24 Full 498.62M DISK 00:01:24 28-JUN-08 BP Key: 26 Status: AVAILABLE Compressed: NO Tag: TAG20080628T012918 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_28\O1_MF_NNNDF_TAG20080628T012918_46C1GZMK_.BKP List of Datafiles in backup set 24 File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 1 Full 545773 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\SYSTEM01.DBF 2 Full 545773 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\UNDOTBS01.DBF 3 Full 545773 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\SYSAUX01.DBF 4 Full 545773 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\USERS01.DBF 5 Full 545773 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\TEST01.DBF BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 88 Full 498.66M DISK 00:01:28 28-JUN-08 BP Key: 93 Status: AVAILABLE Compressed: NO Tag: TAG20080628T014827 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_28\O1_MF_NNNDF_TAG20080628T014827_46C2LW5V_.BKP List of Datafiles in backup set 88 File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 1 Full 546326 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\SYSTEM01.DBF 2 Full 546326 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\UNDOTBS01.DBF 3 Full 546326 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\SYSAUX01.DBF 4 Full 546326 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\USERS01.DBF 5 Full 546326 28-JUN-08 C:\ORACLE\ORADATA\TEST10G\TEST01.DBF BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 186 Full 499.70M DISK 00:01:22 30-JUN-08 BP Key: 193 Status: AVAILABLE Compressed: NO Tag: TAG20080630T044903 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_30\O1_MF_NNNDF_TAG20080630T044903_46JOXJQX_.BKP List of Datafiles in backup set 186 File LV Type Ckp SCN Ckp Time Name ---- -- ---- ---------- --------- ---- 1 Full 551460 30-JUN-08 C:\ORACLE\ORADATA\TEST10G\SYSTEM01.DBF 2 Full 551460 30-JUN-08 C:\ORACLE\ORADATA\TEST10G\UNDOTBS01.DBF 3 Full 551460 30-JUN-08 C:\ORACLE\ORADATA\TEST10G\SYSAUX01.DBF 4 Full 551460 30-JUN-08 C:\ORACLE\ORADATA\TEST10G\USERS01.DBF 5 Full 551460 30-JUN-08 C:\ORACLE\ORADATA\TEST10G\TEST01.DBF RMAN> What we want to do now, is restore the backup of 28 june, while our latest backup is from 30 june. The first backup is, according to rman, obsolete, but we want to investigate whether we can use this backup in a simple restore/recovery action. Let's try: RMAN> run { 2> allocate channel t1 type disk; 3> set until scn 545773; 4> restore controlfile; 5> alter database mount; 6> restore database ; 7> recover database ; 8> release channel t1; 9> alter database open resetlogs; 10> } allocated channel: t1 channel t1: sid=157 devtype=DISK executing command: SET until clause Starting restore at 30-JUN-08 released channel: t1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 06/30/2008 06:46:31 RMAN-06026: some targets not found - aborting restore RMAN-06024: no backup or copy of the control file found to restore Again, there is no controlfile of that specific SCN, so lets take a look at the backups of the controlfile with an SCN close to what we want. We are not going to list those backups, but take for granted that the command below shows us what we want to find: RMAN> list backup of controlfile; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 25 Full 6.80M DISK 00:00:03 28-JUN-08 BP Key: 27 Status: AVAILABLE Compressed: NO Tag: TAG20080628T012918 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_28\O1_MF_NCSNF_TAG20080628T012918_46C1KQ3F_.BKP Control File Included: Ckp SCN: 545801 Ckp time: 28-JUN-08 BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 39 Full 6.77M DISK 00:00:02 28-JUN-08 BP Key: 43 Status: AVAILABLE Compressed: NO Tag: TAG20080628T013052 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_28\O1_MF_NCNNF_TAG20080628T013052_46C1KY00_.BKP Control File Included: Ckp SCN: 545820 Ckp time: 28-JUN-08 etc.. Etc.. So now we try: RMAN> run { 2> allocate channel t1 type disk; 3> set until scn 545801; 4> restore controlfile; 5> alter database mount; 6> restore database ; 7> recover database ; 8> release channel t1; 9> alter database open resetlogs; 10> } allocated channel: t1 channel t1: sid=157 devtype=DISK executing command: SET until clause Starting restore at 30-JUN-08 channel t1: starting datafile backupset restore channel t1: restoring control file channel t1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\TEST1 18_46C1KQ3F_.BKP channel t1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_28\O 0080628T012918 channel t1: restore complete, elapsed time: 00:00:03 output filename=C:\ORACLE\ORADATA\TEST10G\CONTROL01.CTL output filename=C:\ORACLE\ORADATA\TEST10G\CONTROL02.CTL output filename=C:\ORACLE\ORADATA\TEST10G\CONTROL03.CTL Finished restore at 30-JUN-08 database mounted Starting restore at 30-JUN-08 Starting implicit crosscheck backup at 30-JUN-08 Crosschecked 1 objects Finished implicit crosscheck backup at 30-JUN-08 Starting implicit crosscheck copy at 30-JUN-08 Finished implicit crosscheck copy at 30-JUN-08 searching for all files in the recovery area etc.. Etc.. Finished restore at 30-JUN-08 Starting recover at 30-JUN-08 starting media recovery channel t1: starting archive log restore to default destination channel t1: restoring archive log archive log thread=1 sequence=8 channel t1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2 04_46C1L9TC_.BKP channel t1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\TEST10G\BACKUPSET\2008_06_28\O1_MF_ANNNN_TAG 0080628T013104 channel t1: restore complete, elapsed time: 00:00:02 archive log filename=C:\ORACLE\ORADATA\LOG\ARC00008_0658542361.001 thread=1 sequence=8 media recovery complete, elapsed time: 00:00:01 Finished recover at 30-JUN-08 released channel: t1 database opened new incarnation of database registered in recovery catalog starting full resync of recovery catalog full resync complete So even with the small "retention period" of one day, we can restore a backup from several days old. Article 4. TEST: Restore a database from a former incarnation. If you did a recovery of a database to a certain point in time, or a certain SCN, then after the recovery, you must have opened the database with the "reset logs" clause. As far as rman "sees it", a new Database Incarnation has been created, and all backup start from scratch. The former backups just belong to the former Incarnation, and are detached from the new incarnation. You "just start again from 0" when you create new backups from the new incarnation. But, can we still use the former backups, if we really need to do so? Yes they can. Suppose we have target database prodross Suppose we have the rman catalog in database rman Suppose we have restored and recovered the target database to a prior SCN. In that case, we have opened the target with the "reset logs" clause, and a new incarnation was created. Lets see how this looks in rman RMAN> connect target / connected to target database: PRODROSS (DBID=1443222271) RMAN> connect catalog rman/rman@rman connected to recovery catalog database RMAN> list incarnation; List of Database Incarnations DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- ---------- 1 8 PRODROSS 1443222271 PARENT 1 30-AUG-05 1 2 PRODROSS 1443222271 PARENT 534907 01-JUL-08 1 345 PRODROSS 1443222271 CURRENT 547426 01-JUL-08 this is the new incarnation If you were to open a sqlplus session to the RMAN database, you could have issued the following SQL query: SQL>select DBINC_KEY,DB_KEY,DB_NAME,RESET_SCN,RESET_TIME,DBINC_STATUS from DBINC; DBINC_KEY DB_KEY DB_NAME RESET_SCN RESET_TIM DBINC_ST ---------- ---------- -------- ---------- --------- -------- 2 1 PRODROSS 534907 01-JUL-08 PARENT 8 1 PRODROSS 1 30-AUG-05 PARENT 345 1 PRODROSS 547426 01-JUL-08 CURRENT So, the table DBINC, as well as several other tables in the catalog, store the incarnation information. Suppose now that we want to "restore" the database to a prior incarnation, using an sufficiently older backup. In this case, we need to "make clear" to rman, we are going to use such an old backup, belonging to the prior incarnation. We can do that by using the "RESET DATABASE TO INCARNATION <Key>" command. If we bring back the database to that incarnation, characterized by the correct incarnation key, we are able to use those older backups. How was the database a while ago? Lets check alberts person table. SQL> select * from albert.person; PERS_ID PERS_NAME ---------- ----------------------------- 1 Before any backup 2 After 1st backup 3 After 2nd backup Then we restored the 2nd backup. Albert's table now is PERS_ID PERS_NAME ---------- ----------------------------- 1 Before any backup 2 After 1st backup What we want to do now, is restore the first backup, so Albert's table should become PERS_ID PERS_NAME ---------- ----------------------------- 1 Before any backup Lets take a look at the first controlfile backup: RMAN> list backup of controlfile; List of Backup Sets =================== BS Key Type LV Size Device Type Elapsed Time Completion Time ------- ---- -- ---------- ----------- ------------ --------------- 32 Full 6.80M DISK 00:00:03 01-JUL-08 BP Key: 34 Status: AVAILABLE Compressed: NO Tag: TAG20080701T074551 Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\PRODROSS\BACKUPSET\2008_07_01\O1_MF_NCSNF_TAG20080701T074551_46MNQG7T_.BKP Control File Included: Ckp SCN: 546782 Ckp time: 01-JUL-08 So now we are going to reset the incarnation to the former one, and we will use the backup that was associated to that incarnation. Watch this: RMAN> RESET DATABASE TO INCARNATION 2; database reset to incarnation 2 RMAN> RESTORE DATABASE UNTIL SCN 546782; Starting restore at 02-JUL-08 allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=155 devtype=DISK channel ORA_DISK_1: starting datafile backupset restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set restoring datafile 00001 to C:\ORACLE\ORADATA\PRODROSS\SYSTEM01.DBF restoring datafile 00002 to C:\ORACLE\ORADATA\PRODROSS\UNDOTBS01.DBF restoring datafile 00003 to C:\ORACLE\ORADATA\PRODROSS\SYSAUX01.DBF restoring datafile 00004 to C:\ORACLE\ORADATA\PRODROSS\USERS01.DBF restoring datafile 00005 to C:\ORACLE\ORADATA\PRODROSS\TEST.DBF channel ORA_DISK_1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\PRODROSS\BACKUPSET\2008_07_01\O1_MF_NNNDF_TAG200 0701T074551_46MNO0VC_.BKP channel ORA_DISK_1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\PRODROSS\BACKUPSET\2008_07_01\O1_MF_NNNDF_TAG20080701T074551_46MNO0VC_.BKP tag=TA 20080701T074551 channel ORA_DISK_1: restore complete, elapsed time: 00:01:16 Finished restore at 02-JUL-08 RMAN> RECOVER DATABASE UNTIL SCN 546782; Starting recover at 02-JUL-08 using channel ORA_DISK_1 starting media recovery channel ORA_DISK_1: starting archive log restore to default destination channel ORA_DISK_1: restoring archive log archive log thread=1 sequence=12 channel ORA_DISK_1: reading from backup piece C:\ORACLE\FLASH_RECOVERY_AREA\PRODROSS\BACKUPSET\2008_07_01\O1_MF_ANNNN_TAG200 0701T074725_46MNQZXS_.BKP channel ORA_DISK_1: restored backup piece 1 piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\PRODROSS\BACKUPSET\2008_07_01\O1_MF_ANNNN_TAG20080701T074725_46MNQZXS_.BKP tag=TA 20080701T074725 channel ORA_DISK_1: restore complete, elapsed time: 00:00:02 archive log filename=C:\ORACLE\ORADATA\LOG\ARC00012_0658911298.001 thread=1 sequence=12 media recovery complete, elapsed time: 00:00:02 Finished recover at 02-JUL-08 RMAN> ALTER DATABASE OPEN RESETLOGS; database opened new incarnation of database registered in recovery catalog starting full resync of recovery catalog full resync complete RMAN> Now we enter a session in the prodross database, and have a look at Albert's table: SQL> select * from albert.person; PERS_ID PERS_NAME ---------- ------------------------------- 1 Before any backup We have done it! Article 5. Oracle paper: Disaster Recovery http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov004.htm#sthref734 Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 Performing Disaster RecoveryDisaster recovery includes the restore of and recovery of the target database To perform a disaster recovery, the minimum required set of backups is backups of some datafiles, some archived redo logs generated after the time of the backup, and at least one autobackup of the control file. The basic procedure for disaster recovery begins with restoring an autobackup of the server parameter file, as described in Oracle Database Backup and Recovery Basics. Once you have an SPFILE, you can start the target database instance, restore the control file from autobackup and mount it. With the control file mounted, then follow the instructions found in "Performing Recovery with a Backup Control File" (see Article 2) to restore and recover your datafiles. Note: If you are restoring to a new host, you should review the considerations described in "Restore and Recovery of the Database on a New Host". The following scenario restores and recovers the database to the most recently available archived log, which in this example is log 1124 in thread 1. It assumes that: You are restoring the database to a new host with the same directory structure. You have one tape drive containing backups of all the datafiles and archived redo logs through log 1124, as well as autobackups of the control file and server parameter file. You do not use a recovery catalog. In this scenario, perform the following steps: If possible, restore all relevant network files such as tnsnames.ora and listener.ora by means of operating system utilities. Start RMAN and connect to the target database. If you do not have the Oracle Net files, then connect using operating system authentication. Specify the DBID for the target database with the SET DBID command, as described in "Performing Recovery with a Backup Control File and No Recovery Catalog: Scenario". Run the STARTUP NOMOUNT command. RMAN attempts to start the instance with a dummy server parameter file. Allocate a channel to the media manager and then run the RESTORE SPFILE FROM AUTOBACKUP command. Run STARTUP FORCE NOMOUNT mode so that the instance is restarted with the restored server parameter file. Allocate a channel to the media manager and then restore a control file autobackup (refer to"Performing Recovery with a Backup Control File and No Recovery Catalog: Scenario"). Mount the restored control file. Catalog any backups not recorded in the repository with the CATALOG command (refer to"Removing DELETED Records From the Recovery Catalog After Upgrade"). Restore the datafiles to their original locations. If volume names have changed, then run SET NEWNAME commands before the restore and perform a switch after the restore to update the control file with the new locations for the datafiles (refer to"Performing Disaster Recovery"). Recover the datafiles. RMAN stops recovery when it reaches the log sequence number specified. Open the database in RESETLOGS mode. Only complete this last step if you are certain that no other archived logs can be applied. # Start RMAN and connect to the target database % rman TARGET SYS/oracle@trgt # Set the DBID for the target database RMAN> SET DBID 676549873; RMAN> STARTUP FORCE NOMOUNT; # rman starts instance with dummy parameter file RUN { ALLOCATE CHANNEL t1 DEVICE TYPE sbt; RESTORE SPFILE FROM AUTOBACKUP; } # Restart instance with restored server parameter file RMAN> STARTUP FORCE NOMOUNT; RMAN> RUN { # Manually allocate a channel to the media manager ALLOCATE CHANNEL t1 DEVICE TYPE sbt; # Restore autobackup of the control file. This example assumes that you have # accepted the default format for the autobackup name. RESTORE CONTROLFILE FROM AUTOBACKUP; # The set until command is used in case the database # structure has changed in the most recent backups, and you wish to # recover to that point-in-time. In this way RMAN restores the database # to the same structure that the database had at the specified time. ALTER DATABASE MOUNT; SET UNTIL SEQUENCE 1124 THREAD 1; RESTORE DATABASE; RECOVER DATABASE; } RMAN> ALTER DATABASE OPEN RESETLOGS; # Reset the online logs after recovery completes The following example of the RUN command shows the same scenario except with new filenames for the restored datafiles: RMAN> RUN { # If you need to restore the files to new locations, tell Recovery Manager # to do this using SET NEWNAME commands: SET NEWNAME FOR DATAFILE 1 TO '/dev/vgd_1_0/rlvt5_500M_1'; SET NEWNAME FOR DATAFILE 2 TO '/dev/vgd_1_0/rlvt5_500M_2'; SET NEWNAME FOR DATAFILE 3 TO '/dev/vgd_1_0/rlvt5_500M_3'; ALLOCATE CHANNEL t1 DEVICE TYPE sbt; RESTORE CONTROLFILE FROM AUTOBACKUP; ALTER DATABASE MOUNT; SET UNTIL SEQUENCE 124 THREAD 1; RESTORE DATABASE; SWITCH DATAFILE ALL; # Update control file with new location of datafiles. RECOVER DATABASE; } RMAN> ALTER DATABASE OPEN RESETLOGS; Article 6: Oracle Paper http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov003.htm#i1006245 Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02 Performing Recovery with a Backup Control FileIf all copies of the current control file are lost or damaged, then you must restore and mount a backup control file before you can perform recovery. When using a backup control file, and using a recovery catalog, the process is identical to recovery with a current control file, as the RMAN repository information missing from the backup control file is available from the recovery catalog. There are special considerations when using a backup controlfile and not using a recovery catalog. The following notes and restrictions apply regardless of whether you use a recovery catalog: You must run the RECOVER command after restoring a backup control file, even if no datafiles have been restored. You must open the database with the RESETLOGS option after performing either complete or point-in-time recovery with a backup control file. If the online redo logs are inaccessible, then you must perform incomplete recovery to an SCN before the earliest SCN in the online redo logs. This limitation is necessary because RMAN does not back up online logs. During recovery, RMAN automatically searches for online and archived redo logs that are not recorded in the RMAN repository, and catalogs any that it finds so that it can use them in recovery. RMAN attempts to find a valid archived log in any of the current archiving destinations with the current log format. The current format is specified in the initialization parameter file used to start the instance (or all instances in a Real Application Clusters installation). Similarly, RMAN attempts to find the online redo logs by using the filenames as specified in the control file. If you changed the archiving destination or format during recovery, or if you added new online log members after the backup of the control file, then RMAN may not be able to automatically catalog a needed online or archived log. In this situation, RMAN reports errors similar to the following: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 08/29/2001 14:23:09 RMAN-06054: media recovery requesting unknown log: thread 1 scn 86945 In this case, you must use the CATALOG command to manually add the required logs to the repository so that recovery can proceed. The cataloging procedure is described in Oracle Database Backup and Recovery Basics. Performing Recovery with a Backup Control File and No Recovery Catalog: Scenario This section assumes that you have RMAN backups of the control file, but do not use a recovery catalog. Assuming that you enabled the control file autobackup feature for the target database, you can restore an autobackup of the control file. Because the autobackup uses a default format, RMAN can restore it even though it does not have a repository available that lists the available backups. You can restore the autobackup to the default or a new location. RMAN replicates the control file to all CONTROL_FILES locations automatically. Note: If you know the backup piece name (for example, from the media manager or because the piece is on disk), then you can specify the piece name using the RESTORE CONTROLFILE FROM 'filename' command. The server records the location of every autobackup in the alert log. Because you are not connected to a recovery catalog, the RMAN repository contains only information about available backups at the time of the control file backup. If you know the location of other usable backup sets or image copies, add them to the control file RMAN repository with the CATALOG command. Because the repository is not available when you restore the control file, you must use the SET DBID command to identify the target database. The DBID is used to determine the location of control file autobackups. Use SET DBID command only in the following special circumstances: You are not connected to a recovery catalog and want to restore the control file or server parameter file. You are connected to a recovery catalog and want to restore the control file, but the database name is not unique in the recovery catalog. The server parameter file is lost and you want to restore it. To recover the database with an autobackup of the control file without a recovery catalog: Start RMAN and connect to the target database. For example, run: CONNECT TARGET / Start the target instance without mounting the database. For example: STARTUP NOMOUNT; Set the database identifier for the target database with SET DBID. RMAN displays the DBID whenever you connect to the target. You can also obtain it by inspecting saved RMAN log files, querying the catalog, or looking at the filenames of control file autobackup. (refer to "Restoring Control File When Databases in the Catalog Have the Same Name: Example"). For example, run: SET DBID 676549873; Restore the autobackup control file, then perform recovery. Do the following: Optionally, specify the most recent backup time stamp that RMAN can use when searching for a control file autobackup to restore. If you know that a different control file autobackup format was in effect when the control file autobackup was created, then specify a nondefault format for the restore of the control file. If the channel that created the control file autobackup was device type sbt, then you must allocate one or more sbt channels. Because no repository is available, you cannot use preconfigured channels. Restore the autobackup of the control file, optionally setting the maximum number of days backward that RMAN can search (up to 366) and the initial sequence number that it should use in its search for the first day. If you know that your control file contained information about configured channels that will be useful to you in the rest of the restore process, you can exit the RMAN client at this point, to clear manually allocated channels from step "c". If you then restart the RMAN client and mount the database those configured channels become available for your use in the rest of the restore and recovery process. If you do not care about using configured channels from your control file, then you can simply mount the database at this point. If the online logs are usable, then perform a complete restore and recovery as described in Oracle Database Backup and Recovery Basics. Otherwise, restore and perform incomplete recovery of the database, as described in Oracle Database Backup and Recovery Basics Use an UNTIL clause to specify a target time , SCN or log sequence number for the recovery prior to the first SCN of the online redo logs. In this example, the online redo logs have been lost, and the most recent archived log sequence number is 13243. This example shows how to restore the control file autobackup, then performs recovery of the database to log sequence 13243. RUN { # Optionally, set upper limit for eligible time stamps of control file # backups # SET UNTIL TIME '09/10/2000 13:45:00'; # Specify a nondefault autobackup format only if required # SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK # TO '?/oradata/%F.bck'; ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='...'; # allocate manually RESTORE CONTROLFILE FROM AUTOBACKUP MAXSEQ 100 # start at sequence 100 and count down MAXDAYS 180; # start at UNTIL TIME and search back 6 months ALTER DATABASE MOUNT DATABASE; } # uses automatic channels configured in restored control file RESTORE DATABASE UNTIL SEQUENCE 13243; RECOVER DATABASE UNTIL SEQUENCE 13243; # recovers to latest archived log If recovery was successful, then open the database and reset the online logs: ALTER DATABASE OPEN RESETLOGS; Article 7. How to use the Online redologs for recovery. Subject: How To Recover Using The Online Redo Log Doc ID: Note:186137.1 Type: BULLETIN Last Revision Date: 11-OCT-2007 Status: PUBLISHED How to recover using the online redo log ======================================== PURPOSE ------- To easily and quickly find out if the online redo log files can be used to recover a database. AUDIENCE -------- This document is addressed to DBAs that want to quickly find the best recovery solution in case of a database crash. HOW TO ------ Many databases today are run without archive logging enabled, this reduces the available options to quickly recover a database. Basically 2 options are available: a) restore from a backup b) recover the database using the online redo logs. Option a) is straight forward and will not be covered here. Only important thing to mention is that option a) WILL cause loss of data if there has been updates/inserts to the database since the backup was taken. Let us instead take a look at option b): In case of a database crash or a database that will not startup due to ORA-1110, ORA-1113 or both, we first need to identify which files need to be recovered. 1) First we mount the database then issue the following query: select * from v$recover_file; This will give us a list of the files that need media recovery. It will also give us CHANGE#, i.e. the SCN where the media recovery must start. To get the name of the file use the FILE# column and query against v$datafile like this: select name from v$datafile where file# = <file# from v$recover_file> or like this in 9i: select substr(d.name,1,30) fname , r.online_status , r.error , r.change# , r.time from v$datafile d, v$recover_file r where d.file# = r.file# 2) Next we do: archive log list This will give us the current log sequence. We need the current log sequence -1. This will give us the last redo log file that was in use. 3) As the last step we do: select recid , stamp , sequence# , first_change# , next_change# from v$log_history where sequence# = <current log sequence -1) This will show us the NEXT_CHANGE#, i.e.the highest SCN, in the redo log file. It will also give us the FIRST_CHANGE# SCN in this redo log file. We need these 2 SCN numbers to find out if we can use the redo log file for recovery against the file(s) found in 1). If the CHANGE# from 1) is between the FIRST_CHANGE# and the NEXT_CHANGE# then we can use the redo log file for recovery. If the CHANGE# from 1) is lower than FIRST_CHANGE# we need to investigate an earlier online redo log file. When we have identified which redo log files to use for the recovery we perform the recovery using the redo log file(s) in the following way: =- mount the Database =- recover Database The recover process will now display something similar to the following: ORA-00279: change 12599 generated at 08/18/98 13:25:48 needed for thread 1 ORA-00289: suggestion : /oracle/OFA_base/app/oracle/admin/NE804DB1/arch/129.arc ORA-00280: change 12599 for thread 1 is in sequence #129 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} As the database is not in ARCHIVELOG mode we will not have the 129.arc file. Instead the name of the redo log file must be entered on the command line. The filename must include the full path. After the redo log file has been applied the recover process will return: Log applied. At this stage 2 things can happend: 1) Media Recovery Completed 2) or additional redo log files must be applied If 2) then just specify the next redo log file on the command line and continue to do so until Media Recovery Completed is displayed. This must be done with all the redo log files also the CURRENT redo log. To find the CURRENT redo log file one can issue the following query: select f.member,to_char(v.first_change#) , v.sequence# from v$log v , v$logfile f where v.group# = f.group# and v.status='CURRENT'; When the CURRENT redo log has been applied the database can be opened with: alter database open; It is necessary to apply all relevant redo logs otherwise we will not be able to perform the complete recovery which is the only option we have when the database is in NOARCHIVELOG mode. If we do not find any online redo log files which covers the CHANGE# from 1) we cannot do a recover of the database or datafile(s). This means we are left with only 2 options of bringing the database back online: 1) restore from a valid backup taken before the crash. Doing so and running the database in NOARCHIVELOG MODE will cause a loss of data. This is unavoidable. 2) force the database open. This will override Oracle's internal datafile synchronisation and consistency check. The result is an inconsistent database. The database MUST now be exported and rebuild as an inconsistent database is unreliable, and hence not supported. This last option should only be used in cooperation with Oracle Support Article 8. Oracle paper: RMAN best practices Subject: Top 10 Backup and Recovery best practices. Doc ID: Note:388422.1 Type: FAQ Last Revision Date: 05-DEC-2007 Status: PUBLISHED In this Document Purpose Top 10 Backup and Recovery best practices. Questions and Answers Applies to: Oracle Server - Enterprise Edition - Version: 9.2 Information in this document applies to any platform. Purpose Top 10 Backup and Recovery best practices. This document assumes that you are doing the Backup and Recovery basics =- Running in Archivelog mode =- multiplexing the controlfile =- Taking regular backups =- Periodically doing a complete restore to test your procedures. Questions and Answers 1. Turn on block checking. REASON: The aim is to detect, very early the presence of corrupt blocks in the database. This has a slight performance overhead, but will allow Oracle to detect early corruption caused by underlying disk, storage system, or I/O system problems. SQL> alter system set db_block_checking = true scope=both; 2. Turn on block tracking when using RMAN backups (if running 10g) REASON: This will allow RMAN to backup only those blocks that have changed since the last full backup, which will reduce the time taken to back up, as less blocks will be backed up. SQL> alter database enable block change tracking using file ‘/u01/oradata/ora1/change_tracking.f’; 3. Duplex log groups and members and have more than one archive log dest. REASON: If an archivelog is corrupted or lost, by having multiple copies in multiple locations, the other logs will still be available and could be used. If an online log is deleted or becomes corrupt, you will have another member that can be used to recover if required. SQL> alter system set log_archive_dest_2='location=/new/location/archive2' scope=both; SQL> alter database add logfile member '/new/location/redo21.log' to group 1; 4. When backing up the database use the 'check logical' parameter REASON: This will cause RMAN to check for logical corruption within a block as well as the normal head/tail checksumming. This is the best way to ensure that you will get a good backup. RMAN> backup check logical database plus archivelog delete input; 5. Test your backup. REASON: This will do everything except actually restore the database. This is the best method to determine if your backup is good and usable before being in a situation where it is critical and issues exist. RMAN> restore validate database; 6. Have each datafile in a single backup piece REASON: When doing a partial restore RMAN must read through the entire piece to get the datafile/archivelog requested. The smaller the backup piece the quicker the restore can complete. This is especially relevent with tape backups of large databases or where the restore is only on individual / few files. RMAN> backup database filesperset 1 plus archivelog delete input; 7. Maintain your RMAN catalog/controlfile REASON: Choose your retention policy carefully. Make sure that it compliments your tape subsystem retention policy, requirements for backup recovery strategy. If not using a catalog, ensure that your controlfile record keep time instance parameter matches your retention policy. SQL> alter system set control_file_record_keep_time=21 scope=both; This will keep 21 days of backup records. Run regular catalog maintenance. REASON: Delete obsolete will remove backups that are outside your retention policy. If obsolete backups are not deleted, the catalog will continue to grow until performance becomes an issue. RMAN> delete obsolete; REASON: crosschecking will check that the catalog/controlfile matches the physical backups. If a backup is missing, it will set the piece to 'EXPIRED' so when a restore is started, that it will not be eligible, and an earlier backup will be used. To remove the expired backups from the catalog/controlfile use the delete expired command. RMAN> crosscheck backup; RMAN> delete expired backup; 8. Prepare for loss of controlfiles. set autobackup on REASON: This will ensure that you always have an up to date controlfile available that has been taken at the end of the current backup not during. RMAN> configure controlfile autobackup on; keep your backup logs REASON: The backup log contains parameters for your tape access, locations on controlfile backups that can be utilised if complete loss occurs. 9. Test your recovery REASON: During a recovery situation this will let you know how the recovery will go without actually doing it, and can avoid having to restore source datafiles again. SQL> recover database test; 10. Do not specify 'delete all input' when backing up archivelogs REASON: Delete all input' will backup from one destination then delete both copies of the archivelog where as 'delete input' will backup from one location and then delete what has been backed up. The next backup will back up those from location 2 as well as new logs from location 1, then delete all that are backed up. This means that you will have the archivelogs since the last backup available on disk in location 2 (as well as backed up once) and two copies backup up prior to the previous backup. See Note 443814.1 Managing multiple archive log destinations with RMAN for details. Article 9. Oracle article: Recovery after disk loss Subject: Recover database after disk loss Doc ID: Note:230829.1 Type: TROUBLESHOOTING Last Revision Date: 20-MAY-2007 Status: PUBLISHED *** 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 ------- This article aims at walking you through some of the common recovery techniques after a disk failure SCOPE & APPLICATION ------------------- All Oracle support Analysts, DBAs and Consultants who have a role to play in recovering an Oracle database Loss due to Disk Failure ------------------------ What can we lose due to disk failure: A) Control files B) Redo log files C) Archivelog files D) Datafiles E) Parameter file or SPFILE F) Oracle software installation Detecting disk failure ----------------------- 1) Run copy utilities like "dd" on unix 2) If using RAID mechanisms like RAID 5, parity information may mask the disk failure and more vigorous check would be needed 3) As always, check the Operating system log files 4) Another obvious case would be when the disk could not be seen or mounted by the OS. 5) On the Oracle side, run dbverify if the file affected is a datafile 6) The best way to detect disk failure is by running Hardware diagnostic tools and OS specific disk utilities. Next Action ------------ Once the type of failure is identified, the next step is to rectify them. Options could be: (1) Replace the corrupted disk with a new one and mount them with the same name (say /oracle or D:\) (2) Replace the corrupted disk with a new one and mount them with a different name (say /oracle1 as the new mount point) (3) Decide to use another existing disk mounted with a different name (say /oracle2) The most common methods are (1) AND (3). Oracle Recovery --------------- Once the disk problem is sorted, the next step is to perform recovery at the Oracle level. This would depend on the type of files that is lost (see Loss due to Disk Failure section) and also on the type of disk recovery done as mentioned in the "Next Action" section above. (A) Control Files ------------------ Normally, we have multiplexing of controlfiles and they are expected to be placed in different disks. If one or more controlfile is/are lost,mount will fail as shown below: SQL> startup Oracle Instance started .... ORA-00205: error in identifying controlfile, check alert log for more info You can verify the controlfile copies using: SQL> select * from v$controlfile; **If atleast one copy of the controlfile is not affected by the disk failure, When the database is shutdown cleanly: (a) Copy a good copy of the controlfile to the missing location (b) Start the database Alternatively, remove the lost control file location specified in the init parameter control_files and start the database. **If all copies of the controlfile are lost due to the disk failure, then: Check for a backup controlfile. Backup controlfile is normally taken using either of the following commands: (a) SQL> alter database backup controlfile to '/backup/control.ctl'; -- This would have created a binary backup of the current controlfile -- -->If the backup was done in binary format as mentioned above, restore the file to the lost controlfile locations using OS copying utilities. --> SQL> startup mount; --> SQL> recover database using backup controlfile; --> SQL> alter database open; (b) SQL> alter database backup controlfile to trace; -- This would have created a readable trace file containing create controlfile script -- --> Edit the trace file created (check user_dump_dest for the location) and retain the SQL commands alone. Save this to a file say cr_ctrl.sql --> Run the script SQL> @cr_ctrl This would create the controlfile, recover database and open the database. ** If no copy of the controlfile or backup is available, then create a controlfile creation script using the datafile and redo log file information. Ensure that the file names are listed in the correct order as in FILE$. Then the steps would be similar to the one followed with cr_ctrl.sql script. Note that all controlfile related SQL maintenance operations are done in the database nomount state (B) Redo logs --------- In normal cases, we would not have backups of online redo log files. But the inactive logfile changes could already have been checkpointed on the datafiles and even archive log files may be available. SQL> startup mount Oracle Instance Started Database mounted ORA-00313: open failed for members of log group 1 of thread 1 ORA-00312: online log 1 thread 1: '/ORACLE/ORADATA/H817/REDO01.LOG' ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) The system cannot find the file specified. ** Verify if the lost redolog file is Current or not. SQL> select * from v$log; SQL> select * from v$logfile; --> If the lost redo log is an Inactive logfile, you can clear the logfile: SQL> alter database clear logfile '/ORACLE/ORADATA/H817/REDO01.LOG'; Alternatively, you can drop the logfile if you have atleast two other logfiles: SQL> alter database drop logfile group 1; --> If the logfile is the Current logfile, then do the following: SQL> recover database until cancel; Type Cancel when prompted SQL>alter database open resetlogs; The 'recover database until cancel' command can fail with the following errors: ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/ORACLE/ORADATA/H817/SYSTEM01.DBF' In this case , restore an old backup of the database files and apply the archive logs to perform incomplete recovery. --> restore old backup SQL> startup mount SQL> recover database until cancel using backup controlfile; SQL> alter database open resetlogs; If the database is in noarchivelog mode and if ORA-1547, ORA-1194 and ORA-1110 errors occur, then you would have restore from an old backup and start the database. Note that all redo log maintenance operations are done in the database mount state (C) Archive logs ----------------- If the previous archive log files alone have been lost, then there is not much to panic. ** Backup the current database files using hot or cold backup which would ensure that you would not need the missing archive logs (D) Datafiles -------------- This obviously is the biggest loss. (1) If only a few sectors are damaged, then you would get ora-1578 when accessing those blocks. --> Identify the object name and type whose block is corrupted by querying dba_extents --> Based on the object type, perform appropriate recovery --> Check metalink Note 28814.1 for resolving this error (2) If the entire disk is lost, then one or more datafiles may need to be recovered . SQL> startup ORACLE instance started. ... Database mounted. ORA-01157: cannot identify/lock data file 3 - see DBWR trace file ORA-01110: data file 3: '/ORACLE/ORADATA/H817/USERS01.DBF' Other possible errors are ORA-00376 and ORA-1113 The views and queries to identify the datafiles would be: SQL> select file#,name,status from v$datafile; SQL> select file#,online,error from v$recover_file; ** If restoring to a replaced disk mounted with the same name, then : (1) Restore the affected datafile(s) using OS copy/restore commands from the previous backup (2) Perform recovery based on the type of datafile affected namely SYSTEM, ROLLBACK or UNDO, TEMP , DATA or INDEX. (3) The recover commands could be 'recover database', 'recover tablespace' or 'recover datafile' based on the loss and the database state ** If restoring to a different mount point, then : (1) Restore the files to the new location from a previous backup (2) SQL> STARTUP MOUNT (3) SQL> alter database rename file '/old path_name' to 'new path_name'; -- Do this renaming for all datafiles affected. -- (4) Perform recovery based on the type of datafile affected namely SYSTEM, ROLLBACK or UNDO, TEMP , DATA or INDEX. (5) The recover commands could be 'recover database', 'recover tablespace' or 'recover datafile' based on the loss and the database state The detailed steps of recovery based on the datafile lost and the Oracle error are outlined in the following articles : Note 184327.1 Note 198640.1 Note 183327.1 Note 183367.1 NOARCHIVELOG DATABASE ===================== The loss mentioned in (A),(B) and (D) would be different in this case wherever archive logs are involved. We will discuss the datafile loss scenarios here: (a) If the datafile lost is a SYSTEM datafile, restore the complete database from the previous backup and start the database. (b) If the datafile lost is Rollback related datafile with active transactions, restore from the previous backup and start the database. (c) If the datafile contains rollback with no active rollback segments, you can offline the datafile (after commenting the rollback_segments parameter assuming that they are private rollback segments) and open the database. (d) If the datafile is temporary, offline the datafile and open the database. Drop the tablespace and recreate the tablespace. (e) If the datafile is DATA or INDEX, **Offline the tablespace and start the database. **If you have a previous backup, restore it to a separate location. **Then export the objects in the affected tablespace ( using User or table level export). **Create the tablespace in the original database. **Import the objects exported above. If the database is 8i or above, you can also use Transportable tablespace feature. (E) Parameter file --------------- This is not a major loss and can be easily restored. Options are: (1) If there is a backup, restore the file (2) If there is no backup, copy sample file or create a new file and add the required parameters. Ensure that the parameters db_name, control_files, db_block_size, compatible are set correctly (3) If the spfile is lost, you can create it from the init parameter file (F) Oracle Software Installation ---------------------------- There are two ways to recover from this scenario: (1) If there is a backup of the Oracle home and Oracle Inventory, restore them to the respective directories. Note if you change the Oracle Home, the inventory would not be aware of thid new path and you would not be able to apply patchsets. Also restore to the same OS user and group. (2) Perform a fresh Install PRACTICAL SCENARIO ================== In most cases, when a disk is lost, more than one type of file could be lost. The recovery in this scenario would be: (1) A combination of each of these data loss recovery scenarios (2) Perform entire database restore from the last backup and apply archive logs to perform recovery. This is a highly preferred method but could be time consuming. Note: For any issues or clarifications, call into Oracle Support RELATED DOCUMENTS ------------------ Note 103176.1 - How to Recover Having Lost Controlfiles and Online Redo Logs Note 184327.1 - Common Causes and Solutions on ORA-1157 Error Found in B&R Note 198640.1 - How to Recover from a Lost Datafile with Different Scenarios Note 183327.1 - Common Causes and Solutions on ORA-376 Error Found in B&R Note 183367.1 - Common Causes and Solutions on ORA-1113 Error Found in B&R Note 117481.1 - Loss Of Online Redo Log And ORA-312 And ORA-313 ----- Note: ----- ORA-600 [4400] on 10.2.0.3 ORA-600 [4400] [a] [b] [c] [d] [e] DESCRIPTION: Internal error 4400 means that we are trying to delete a transaction (for example at logoff time) but the transaction has not yet been marked completed. This can happen at the remote site in a distributed transaction if the first part of the first stage of a two phase commit gets an error before it really starts the protocol. FUNCTIONALITY: TRANSACTION CONTROLIMPACT: PROCESS FAILURE - but only at logoff so minimal impact NON CORRUPTIVE - No underlying data corruption. Some other errors you might encounter workin with RMAN: ======================================================= Err 1: Missing archived redolog: ================================ Problem: If an archived redo is missing, you might get a message similar like this: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 03/05/2008 07:44:35 RMAN-06059: expected archived log not found, lost of archived log compromises recoverability ORA-19625: error identifying file /dbms/tdbaeduc/educroca/recovery/archive/arch_1_817_617116679.arch ORA-27037: unable to obtain file status IBM AIX RISC System/6000 Error: 2: No such file or directory Solution: If archived redo logs are (wrongly) deleted/moved/compressed from disk without being backed up, the rman catalog will not know this has happened, and will keep attempting to backup the missing archived redo logs. That will cause rman archived redo log backups to fail altogether with an error like: RMAN-06059: expected archived log not found, lost of archived log compromises recoverability If you can, you should bring back the missing archved redo logs to their original location and name, and let rman back them up. But if that is impossible, the workaround is to “crosscheck archivelog all”, like: rman <<e1 connect target / connect catalog username/password@catalog run { allocate channel c1 type disk ; crosscheck archivelog all ; release channel c1 ; } e1 Or just go into rman and run the command: RMAN> crosscheck archivelog all; You’ll get output like this: validation succeeded for archived log archive log filename=D:REDOARCHARCH_1038.DBF recid=1017 stamp=611103638 for every archived log as they are all checked on disk. That should be the catalog fixed, run an archivelog backup to make sure. Err 2: online redo logs listed as archives: =========================================== Testcase: a 10g 10.2.0.3 shows after recovery with resetlogs the following in v$archived_log. It looks as if it will stay there forever: SEQ# FIRST NEXT NAME DIFF STATUS 814 17311773 17311785 12 D 815 17311785 17354662 42877 D 816 17354662 17354674 12 D 817 17354674 17402531 47857 D 2 17415287 2.81E+14 redo01.log 2.8147E+14 A 0 0 0 redo02.log 0 A 0 0 0 redo03.log 0 A 0 0 0 redo04.log 0 A 1 -->17402532 17415287 redo05.log 12755 A 1 17402532 17404154 1622 D 2 17404154 17404165 11 D FIRST_CHANGE# NEXT_CHANGE# SEQUENCE# RESETLOGS_CHANGE# ------------- ------------ ---------- ----------------- 17311785 17354662 815 1 17354662 17354674 816 1 17354674 17402531 817 1 -->17402532 17404154 1 -->17402532 17404154 17404165 2 17402532 17404165 17415733 3 17402532 We dont know what is going on here. Err 3: Highlevel overview RMAN Error Codes ========================================== RMAN error codes are summarized in the table below. 0550-0999 Command-line interpreter 1000-1999 Keyword analyzer 2000-2999 Syntax analyzer 3000-3999 Main layer 4000-4999 Services layer 5000-5499 Compilation of RESTORE or RECOVER command 5500-5999 Compilation of DUPLICATE command 6000-6999 General compilation 7000-7999 General execution 8000-8999 PL/SQL programs 9000-9999 Low-level keyword analyzer 10000-10999 Server-side execution 11000-11999 Interphase errors between PL/SQL and RMAN 12000-12999 Recovery catalog packages 20000-20999 Miscellaneous RMAN error messages Err 4: RMAN-03009 accompinied with ORA- error: ============================================== Q: Here is my problem; When trying to delete obsolete RMAN backupsets, I get an error: RMAN> change backupset 698, 702, 704, 708 delete; List of Backup Pieces BP Key BS Key Pc# Cp# Status Device Type Piece Name ------- ------- --- --- ----------- ----------- ---------- 698 698 1 1 AVAILABLE SBT_TAPE df_546210555_706_1 702 702 1 1 AVAILABLE SBT_TAPE df_546296605_709_1 704 704 1 1 AVAILABLE SBT_TAPE df_546383776_712_1 708 708 1 1 AVAILABLE SBT_TAPE df_546469964_715_1 Do you really want to delete the above objects (enter YES or NO)? YES RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at 03/02/2005 16:27:06 ORA-27191: sbtinfo2 returned error Additional information: 2 What in the world does "Additional information: 2" mean? I can't find any more useful detail than this. A: Oracle Error :: ORA-27191 sbtinfo2 returned error Cause sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager"s catalog. Action This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor. A: ---> ORA-27191 John Clarke: My guess is that "2" is an O/S return code, and in /usr/sys/include/errno.h, you'll see that error# 2 is "no such file or directory. Accompanied with ORA-27191, I'd guess that your problem is that your tape library doesn't currently have the tape(s) loaded and/or can't find them. Mladen Gogala: Additional information 2 means that OS returned status 2. That is a "file not found" error. In plain Spanglish, you cannot delete files from tape, only from the disk drives. Niall Litchfield: The source error is the ora-27191 error (http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e24280.htm#ORA-27191) which suggests a tape library issue to me. You can search for RMAN errors using the error search page as well http://otn.oracle.com/pls/db10g/db10g.error_search?search=rman-03009, for example A: ---> RMAN-03009 RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at date/time RMAN-03009: failure of allocate command on t1 channel at date/time RMAN-03009: failure of backup command on t1 channel at date/time etc.. -> Means most of the time that you have Media Management Library problems -> Can also mean that there is a problem with backup destination (disk not found, no space, tape not loaded etc..) ERR 5: Test your Media Management API: ====================================== Testing the Media Management API On specified platforms, Oracle provides a diagnostic tool called "sbttest". This utility performs a simple test of the tape library by acting as the Oracle database server and attempting to communicate with the media manager. Obtaining the Utility On UNIX, the sbttest utility is located in $ORACLE_HOME/bin. Obtaining Online Documentation For online documentation of sbttest, issue the following on the command line: % sbttest The program displays the list of possible arguments for the program: Error: backup file name must be specified Usage: sbttest backup_file_name # this is the only required parameter <-dbname database_name> <-trace trace_file_name> <-remove_before> <-no_remove_after> <-read_only> <-no_regular_backup_restore> <-no_proxy_backup> <-no_proxy_restore> <-file_type n> <-copy_number n> <-media_pool n> <-os_res_size n> <-pl_res_size n> <-block_size block_size> <-block_count block_count> <-proxy_file os_file_name bk_file_name [os_res_size pl_res_size block_size block_count]> The display also indicates the meaning of each argument. For example, following is the description for two optional parameters: Optional parameters: -dbname specifies the database name which will be used by SBT to identify the backup file. The default is "sbtdb" -trace specifies the name of a file where the Media Management software will write diagnostic messages. Using the Utility Use sbttest to perform a quick test of the media manager. The following table explains how to interpret the output: If sbttest returns... Then... 0 The program ran without error. In other words, the media manager is installed and can accept a data stream and return the same data when requested. non-0 The program encountered an error. Either the media manager is not installed or it is not configured correctly. To use sbttest: Make sure the program is installed, included in your system path, and linked with Oracle by typing sbttest at the command line: % sbttest If the program is operational, you should see a display of the online documentation. Execute the program, specifying any of the arguments described in the online documentation. For example, enter the following to create test file some_file.f and write the output to sbtio.log: % sbttest some_file.f -trace sbtio.log You can also test a backup of an existing datafile. For example, this command tests datafile tbs_33.f of database PROD: % sbttest tbs_33.f -dbname prod Examine the output. If the program encounters an error, it provides messages describing the failure. For example, if Oracle cannot find the library, you see: libobk.so could not be loaded. Check that it is installed properly, and that LD_ LIBRARY_PATH environment variable (or its equivalent on your platform) includes the directory where this file can be found. Here is some additional information on the cause of this error: ld.so.1: sbttest: fatal: libobk.so: open failed: No such file or directory ERR 6: RMAN-12004 ================= Hi, I m facing this problem any pointers will of great help.... 1. RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00579: the following error occurred at 12/16/2003 02:46:31 RMAN-10035: exception raised in RPC: RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE RMAN-03015: error occurred in stored script backup_db_full RMAN-03015: error occurred in stored script backup_del_all_al RMAN-03007: retryable error occurred during execution of command: backup RMAN-12004: unhandled exception during command execution on channel t1 RMAN-10035: exception raised in RPC: ORA-19506: failed to create sequential file, name="l0f93ro5_1_1", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: sbtbackup: Failed to process backup file. RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE OR another errorstack RMAN-12004: unhandled exception during command execution on channel disk13 RMAN-10035: exception raised in RPC: ORA-19502: write error on file "/db200_backup/archive_log03/EDPP_ARCH0_21329_1_492222998", blockno 612353 (blocksize=1024) ORA-27072: skgfdisp: I/O error HP-UX Error: 2: No such file or directory Additional information: 612353 RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE OR another errorstack RMAN-12004: unhandled exception during command execution on channel ch00 RMAN-10035: exception raised in RPC: ORA-19599: block number 691 is corrupt in controlfile C:\ORACLE\ORA90\DATABASE\SNCFSUMMITDB.ORA RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE OR another errorstack Have managed to create a job to backup my db, but I can't restore. I get the following: RMAN-03002: failure during compilation of command RMAN-03013: command type: restore RMAN-03006: non-retryable error occurred during execution of command: IRESTORE RMAN-07004: unhandled exception during command execution on channel BackupTest RMAN-10035: exception raised in RPC: ORA-19573: cannot obtain exclusive enqueue for datafile 1 RMAN-10031: ORA-19583 occurred during call to DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE Seems to relate to corrupt or missing Oracle files. $$$$ ERR 7: ORA-27211 ================ Q: Continue to get ORA-27211 Failed to load media management library A: had a remarkably similar experience a few months ago with Legato NetWorker and performed all of the steps you listed with the same results. The problem turned out to be very simple. The SA installed the 64-bit version of the Legato Networker client because it is a 64-bit server. However, we were running a 32-bit version of Oracle on it. Installing the 32-bit client solved the problem. A: Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for error code. Action: Retry the command with proper media library. Or re-install Media management module for Oracle. A: Exact Error Message ORA-27211: Failed to load Media Management Library on HP-UX system Details: Overview: The Oracle return code ORA-27211 implies a failure to load a shared object library into process space. Oracle Recovery Manager (RMAN) backups will fail with a message "ORA-27211: Failed to load Media Management Library" if the SBT_LIBRARY keyword is defined and points to an incorrect library name. The SBT_LIBRARY keyword must be set in the PARMS clause of the ALLOCATE CHANNEL statement in the RMAN script. This keyword is not valid with the SEND command and is new to Oracle 9i. If this value is set, it overrides the default search path for the libobk library. By default, SBT_LIBRARY is not set. Troubleshooting: If an ORA-27211 error is seen for an Oracle RMAN backup, it is necessary to review the Oracle RMAN script and verify if SBT_LIBRARY is either not set or is set correctly. If set, the filename should be libobk.sl for HP-UX 10, 11.00 and 11.11, but libobk.so for HP-UX 11.23 (ia64) clients. Example of an invalid entry for HP-UX 11.23 (ia64) clients: PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.sl' Example of a correct entry for HP-UX 11.23 (ia64) clients: PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so' Master Server Log Files: n/a Media Server Log Files: n/a Client Log Files: The RMAN log file on the client will show the following error message: RMAN-00571: =========================================== RMAN-00569: ======= ERROR MESSAGE STACK FOLLOWS ======= RMAN-00571: =========================================== RMAN-03009: failure of allocate command on ch00 channel at 05/21/2005 16:39:17 ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-27211: Failed to load Media Management Library Additional information: 25 Resolution: The Oracle return code ORA-27211 implies a failure to load a shared object library into process space. Oracle RMAN backups will fail with a message "ORA-27211: Failed to load Media Management Library" if the SBT_LIBRARY keyword is defined and points to an incorrect library name. To manually set the SBT_LIBRARY path, follow the steps described below: 1. Modify the RMAN ALLOCATE CHANNEL statement in the backup script to reference the HP-UX 11.23 library file directly: PARMS='SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so' Note: This setting would be added to each ALLOCATE CHANNEL statement. A restart of the Oracle instance is not needed for this change to take affect. 2. Run a test backup or wait for the next scheduled backup of the Oracle database ERR8: More on DBMS_BACKUP_RESTORE: ================================== Note 1: The dbms_backup_restore package is used as a PL/SQL command-line interface for replacing native RMAN commands, and it has very little documentation. The Oracle docs note how to install and configure the dbms_backup_restore package: “The DBMS_BACKUP_RESTORE package is an internal package created by the dbmsbkrs.sql and prvtbkrs.plb scripts. This package, along with the target database version of DBMS_RCVMAN, is automatically installed in every Oracle database when the catproc.sql script is run. This package interfaces with the Oracle database server and the operating system to provide the I/O services for backup and restore operations as directed by RMAN.” The docs also note that “The DBMS_BACKUP_RESTORE package has a PL/SQL procedure to normalize filenames on Windows NT platforms.” Oracle DBA John Parker gives this example of dbms_backup_restore to recover a controlfile: declare devtype varchar2(256); done boolean; begin devtype:=dbms_backup_restore.deviceallocate( type=>'sbt_tape', params=>'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=rdcs,OB2BARLIST=ORA_RDCS_WEEKLY)', ident=>'t1'); dbms_backup_restore.restoresetdatafile; dbms_backup_restore.restorecontrolfileto('D:\oracle\ora81\dbs\CTL1rdcs.ORA'); dbms_backup_restore.restorebackuppiece( 'ORA_RDCS_WEEKLY<rdcs_6222:596513521:1>.dbf', DONE=>done ); dbms_backup_restore.restoresetdatafile; dbms_backup_restore.restorecontrolfileto('D:\DBS\RDCS\CTL2RDCS.ORA'); dbms_backup_restore.restorebackuppiece( 'ORA_RDCS_WEEKLY<rdcs_6222:596513521:1>.dbf', DONE=>done ); dbms_backup_restore.devicedeallocate('t1'); end; Here are some other examples of using dbms_backup_restore: DECLARE devtype varchar2(256); done boolean; BEGIN devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN'); dbms_backup_restore.RestoreSetDatafile; dbms_backup_restore.RestoreDatafileTo(dfnumber => 1,toname => 'D:\ORACLE_BASE\datafiles\SYSTEM01.DBF'); dbms_backup_restore.RestoreDatafileTo(dfnumber => 2,toname => 'D:\ORACLE_BASE\datafiles\UNDOTBS.DBF'); --dbms_backup_restore.RestoreDatafileTo(dfnumber => 3,toname => 'D:\ORACLE_BASE\datafiles\MYSPACE.DBF'); dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_DF_BCK05H2LLQP_1_1', params => null); dbms_backup_restore.DeviceDeallocate; END; / --restore archived redolog DECLARE devtype varchar2(256); done boolean; BEGIN devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN'); dbms_backup_restore.RestoreSetArchivedLog(destination=>'D:\ORACLE_BASE\achive\'); dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>1); dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>2); dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>3); dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_LOG_BCK0DH1JGND_1_1', params => null); dbms_backup_restore.DeviceDeallocate; END; / Note 2: ------- --restore controlfile DECLARE devtype varchar2(256); done boolean; BEGIN devtype := dbms_backup_restore.DeviceAllocate(type => '',ident => 'FUN'); dbms_backup_restore.RestoresetdataFile; dbms_backup_restore.RestoreControlFileto('D:\ORACLE_BASE\controlfiles\CONTROL01.CTL'); dbms_backup_restore.RestoreBackupPiece('D:\ORACLE_BASE\Rman_Backup\MYDB_DF_BCK0BH1JBVA_1_1',done => done); dbms_backup_restore.RestoresetdataFile; dbms_backup_restore.RestoreControlFileto('D:\ORACLE_BASE\controlfiles\CONTROL02.CTL'); dbms_backup_restore.RestoreBackupPiece('D:\ORACLE_BASE\Rman_Backup\MYDB_DF_BCK0BH1JBVA_1_1',done => done); dbms_backup_restore.RestoresetdataFile; dbms_backup_restore.RestoreControlFileto('D:\ORACLE_BASE\controlfiles\CONTROL03.CTL'); dbms_backup_restore.RestoreBackupPiece('D:\ORACLE_BASE\Rman_Backup\MYDB_DF_BCK0BH1JBVA_1_1',done => done); dbms_backup_restore.DeviceDeallocate; END; / --restore datafile DECLARE devtype varchar2(256); done boolean; BEGIN devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN'); dbms_backup_restore.RestoreSetDatafile; dbms_backup_restore.RestoreDatafileTo(dfnumber => 1,toname => 'D:\ORACLE_BASE\datafiles\SYSTEM01.DBF'); dbms_backup_restore.RestoreDatafileTo(dfnumber => 2,toname => 'D:\ORACLE_BASE\datafiles\UNDOTBS.DBF'); --dbms_backup_restore.RestoreDatafileTo(dfnumber => 3,toname => 'D:\ORACLE_BASE\datafiles\MYSPACE.DBF'); dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_DF_BCK05H2LLQP_1_1', params => null); dbms_backup_restore.DeviceDeallocate; END; / --restore archived redolog DECLARE devtype varchar2(256); done boolean; BEGIN devtype := dbms_backup_restore.DeviceAllocate (type => '',ident => 'FUN'); dbms_backup_restore.RestoreSetArchivedLog(destination=>'D:\ORACLE_BASE\achive\'); dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>1); dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>2); dbms_backup_restore.RestoreArchivedLog(thread=>1,sequence=>3); dbms_backup_restore.RestoreBackupPiece(done => done,handle => 'D:\ORACLE_BASE\RMAN_BACKUP\MYDB_LOG_BCK0DH1JGND_1_1', params => null); dbms_backup_restore.DeviceDeallocate; END; / ERR 9: RMAN-00554 initialization of internal recovery manager package failed: ============================================================================= connected to target database: PLAYROCA (DBID=575215626) RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-04004: error from recovery catalog database: ORA-03135: connection lost contact keys: RMAN-00554 RMAN-04004 ORA-03135 ORA-3136 >>>> In alertlog of the rman, we can find: WARNING: inbound connection timed out (ORA-3136) Thu Mar 13 23:09:54 2008 >>>> In Net logs sqlnet.log we can find: Warning: Errors detected in file /dbms/tdbaplay/ora10g/home/network/log/sqlnet.log > *********************************************************************** > Fatal NI connect error 12170. > > VERSION INFORMATION: > TNS for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production > TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production > Oracle Bequeath NT Protocol Adapter for IBM/AIX RISC System/6000: Version 10.2.0.3.0 - Production > Time: 18-MAR-2008 23:01:43 > Tracing not turned on. > Tns error struct: > ns main err code: 12535 > TNS-12535: TNS:operation timed out > ns secondary err code: 12606 > nt main err code: 0 > nt secondary err code: 0 > nt OS err code: 0 > Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=57.232.4.123)(PORT=35844)) Note 1: ------- RMAN-00554: initialization of internal recovery manager package failed Is a general error code. You must turn your attention the the codes underneath this one. For example: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-06003: ORACLE error from target database: ORA-00210: cannot open the specified control file ORA-00202: control file: '/devel/dev02/dev10g/standbyctl.ctl' RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-04005: error from target database: ORA-01017: invalid username/password; Note 2: ------- RMAN-04004: error from recovery catalog database: ORA-03135: connection lost contact ERR 10: RMAN-00554 initialization of internal recovery manager package failed: ============================================================================== Starting backup at 17-MAY-08 released channel: t1 released channel: t2 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 05/17/2008 23:30:13 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog Note 1: ------- Oracle Error :: RMAN-20242 specification does not match any archivelog in the recovery catalog Cause No archive logs in the specified archive log range could be found. Action Check the archive log specifier. Note 2: ------- Some of the common RMAN errors are: RMAN-20242: Specification does not match any archivelog in the recovery catalog. Add to RMAN script: sql 'alter system archive log current'; Note 3: ------- Q: RMAN-20242: specification does not match any archive log in the recovery ca Posted: Feb 12, 2008 7:52 AM Reply A couple of archive log files were deleted from the OS. They still show up in the list of archive logs in Enterprise Manager. I want to fix this because now whenever I try to run a crosscheck command, I get the message: RMAN-20242: specification does not match any archive log in the recovery catalog I also tried to uncatalog those files, but got the same message. Any suggestions on what to do? Thanks! A: hi, from rman run the command list expired archivelog; if ther archives are in this list they will show, then i think you should do a crosscheck archivelog all; then you should be able to delete them. regards Note 4: ------- The RMAN error number would be helpful, but this is a common problem - RMAN-20242 - and is addressed in detail in MetaLink notes. Either the name specification (the one you entered) is wrong, or you could be using mismatched versions between RMAN and the database (don't know since you didn't provide any version details). Note 5: ------- Q: Hi there! We are having problems with an Oracle backup. The compiling of the backup command fails with the error message: RMAN-20242: specification does not match any archivelog in the recovery catalog But RMAN is only supposed to backup any archived logs that are there and then insert them in the catalog... Did anybody experience anything similar? This is 8.1.7 on HP-UX with Legato Networker Thanks, A: If i ask rman to backup archivelogs that are more than 2days old and there are none, thats not an error. That is when i see it the most, now most companies will force a log switch after a set amount of time during the day so in DR, you dont lose days worth of redo that might still be hanging in a redo log if it gets lost. ----- Note: RMAN error: Server Status: cannot connect on socket ----- RMAN-03009: failure of backup command on ch00 channel at 08/14/2010 20:00:34 ORA-19506: failed to create sequential file, name="al_56_1_727041608", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSAValidateFeatureId: Failed with error: Server Status: cannot connect on socket Answer 1: --------- Could be caused by recent IP address or subnetmask or gateway changes. Could be caused by recent Firewall changes. Could be caused by insufficient permissions on names reolution files like /etc/hosts, /etc/nsswitch.conf and /etc/resolv.conf Answer 2: --------- Oracle RMAN backup fails with status 6 and dbclient reports "cannot connect on socket (25)" preceded by "gethostbyname failed. Article: TECH28981 Created: 2006-01-26 Updated: 2006-01-26 Article URL http://www.symantec.com/docs/TECH28981 Oracle RMAN backup fails with status 6 and dbclient reports "cannot connect on socket (25)" preceded by "gethostbyname failed." Error setup_connect_options: gethostbyname failed for myHostName: ?undefined error? (0) Solution The NetBackup (tm) Oracle extension attempts to connect to the master server by performing name resolution to get the IP address of the master server. The resolution fails because the Oracle user performing the backup does not have the necessary permissions to access the system files which control the name resolution process. The following error is reported in the dbclient log: 16:38:07.339 [24626] <2> setup_connect_options: gethostbyname failed for nbmaster-bk: ?undefined error? (0) 16:38:07.339 [24626] <2> setup_connect_options: cannot find host: nbmaster-bk, h_errno=0 16:38:07.340 [24626] <2> getsockconnected: setup_connect_options() failed, Error 0 (0) 16:38:07.340 [24626] <2> bprd_connect: Cannot connect to server nbmaster-bk 16:38:07.340 [24626] <2> bprd_connect: errno = 0 - Error 0 16:38:07.341 [24626] <16> dbc_GetMediaListByName: Can't connect to host nbmaster-bk: cannot connect on socket (25) 16:38:07.341 [24626] <16> find_backup_image: GetMediaListByName() failed 16:38:07.341 [24626] <16> sbtbackup: Failed to process backup file. This situation can be confirmed by executing the bpclntcmd command on the failing host for the indicated host name, both as root (which should have permissions) and then as the Oracle user that is performing the backup: # /usr/openv/netbackup/bin/bpclntcmd -hn nbmaster-bk host nbmaster-bk: nbmaster-bk at 10.82.105.15 (0xa52690f) checkhname: aliases: # su - oracle8 $ /usr/openv/netbackup/bin/bpclntcmd -hn nbmaster-bk gethostbyname failed for nbmaster-bk: HOST_NOT_FOUND (1 alter client: nbmaster-bk : not found. (1) Resolution: The modes on the name resolution files /etc/nsswitch.conf and /etc/resolv.conf were found to be set to 0640 (-rw-r-----). The file was owned by user=root group=root which did not permit the oracle8 user to read the contents of the files. Changing the modes on the files to 0644 (-rw-r--r--) allowed the host name of the master server to be resolved and the backup was successful. ----- Note: ----- Using sbt, media manager software, the sbtio.log contains information written by the media management software, and is not from the Oracle Database. This could provide for clues in case of media manager error messages. ----- Note: ----- #################################################################################################### SECTION 6: RMAN messages #################################################################################################### 46 RMAN-00201 to RMAN-20512 RMAN-00201: Do you really want to execute the above repair (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00202: Do you want to open the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00203: Do you want to open resetlogs the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00204: Do you really want to delete the above objects (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00205: Do you really want to drop all backups and the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00206: Do you really want to drop the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00207: Do you really want to unregister the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00208: Want to unregister the database with target db_unique_name (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00209: Do you really want to change the above failures (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00210: Do you really want to catalog the above files (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-00211: Error occurred getting response - assuming NO response Cause: An error occurred reading user response. Action: No action is required, this is an informational message only. RMAN-00212: "string" is an invalid response - please re-enter. Cause: An incorrect response was entered. Action: Enter a correct response. RMAN-00550: parser package failed to load Cause: lpmloadpkg() return an error indication. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00551: initialization of parser package failed Cause: The parser package initialization routine returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00552: syntax error in command line arguments Cause: The arguments supplied to RMAN could not be parsed, or no arguments were supplied at all. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00553: internal recovery manager package failed to load Cause: lpmloadpkg() return an error indication. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00554: initialization of internal recovery manager package failed Cause: The internal package initialization routine returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00555: target database connect string must be specified Cause: The TARGET parameter was not specified. Action: Supply the necessary parameter. RMAN-00556: could not open CMDFILE "string" Cause: An error occurred when trying to open the file. Action: Check that the file name was specified correctly and that the file exists and that the user running RMAN has read permission for the file. RMAN-00557: could not open MSGLOG "string" Cause: An error occurred when trying to open the file. Action: Check that the file name was specified correctly and that the file exists and that the user running RMAN has write permission for the file. RMAN-00558: error encountered while parsing input commands Cause: The parser detected a syntax error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00562: username too long Cause: The specified user name exceeds the maximum allowable username length. Action: Correct the username. RMAN-00563: password too long Cause: The specified password exceeds the maximum allowable password length. Action: Correct the password. RMAN-00564: host data too long Cause: The SQL*NET host connect string exceeds the maximum allowable length. Action: Correct the host string. RMAN-00565: unable to read input file Cause: An error occurred while trying to read from STDIN or from the CMDFILE. Action: Ensure that the cmdfile is readable. The cmdfile must be a text file with 1 line per record. RMAN-00566: could not open TRACE "string" Cause: An error occurred when trying to open the file. Action: Check that the file name was specified correctly and that the user running RMAN has write permission for the file. RMAN-00567: Recovery Manager could not print some error messages Cause: An error occurred while trying to print the error message stack. Action: If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-00568: user interrupt received Cause: The user typed ^C or ATTN. Action: No action is required. RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== Cause: This message precedes an error message stack. Action: The errors are printed in last-in first-out order. To interpret them correctly, read from the bottom to the top. RMAN-00570: **end-of-file** Cause: The end of an inline cmdfile was reached. This is just an informational message. Action: No action is required. RMAN-00571: =========================================================== Cause: Displayed to highlight the error message stack. Action: The errors are printed in last-in first-out order. To interpret them correctly, read from the bottom to the top. RMAN-00572: waiting for DBMS_PIPE input Cause: This message is used only when the PIPE option was specified. Action: enqueue some RMAN input into the pipe RMAN-00573: DBMS_PIPE.NEXT_ITEM_TIME returned unknown type code: number Cause: This is an internal error. Action: contact Oracle Support Services. RMAN-00574: rman aborting due to errors reading/writing DBMS_PIPE Cause: RMAN was run with input/output being sent to DBMS_PIPE. An error was encountered while reading from or writing to the pipe. This error should be preceded by information describing the error. Action: RMAN terminates. Refer to the cause/action for the preceding errors. RMAN-00575: timeout while trying to write to DBMS_PIPE Cause: d by death of the process that was talking to rman. Action: RMAN will abort. RMAN-00576: PIPE cannot be used with CMDFILE Cause: The PIPE and CMDFILE options cannot be used together. When using the PIPE option, RMAN must obtain its input from the input pipe. Action: Remove either the PIPE or CMDFILE option. RMAN-00577: PIPE requires that TARGET be specified on the command line Cause: The PIPE option obtains its input from, and writes its output to, an Oracle database pipe in the target database. Therefore, the target database connection must be specified on the command line, so that RMAN can connect to the target database to receive its input from the pipe. Action: Specify the TARGET option on the RMAN command line. RMAN-00578: pipe string is not private and owned by SYS Cause: The pipe that RMAN needs to use for its input or output is either a public pipe or a private pipe that is not owned by SYS. This is a potential security problem, because it allows a non-SYS user to issue commands to RMAN or to retrieve the RMAN output. Action: If you are attempting to put data on the RMAN input pipe prior to starting RMAN, so RMAN will process the data on the pipe as soon as it starts, you must be connected as SYS and you must first use the DBMS_PIPE.CREATE_PIPE function to explicitly create the pipe as a private pipe. RMAN-00579: SCRIPT cannot be used with CMDFILE Cause: The SCRIPT and CMDFILE options cannot be used together. When using the SCRIPT option, RMAN executes only the specified script. Action: Remove either the SCRIPT or CMDFILE option. RMAN-00600: internal error, arguments [string] [string] [string] [string] [string] Cause: An internal error in recovery manager occurred. Action: Contact Oracle Support Services. RMAN-00601: fatal error in recovery manager Cause: A fatal error has occurred. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00700: SCRIPT requires that TARGET be specified on the command line Cause: A SCRIPT option was included on the RMAN command line without a specified TARGET database. Action: Specify the TARGET option on the RMAN command line. RMAN-00701: SCRIPT requires that CATALOG be specified on the command line Cause: A SCRIPT option was included on the RMAN command line without a specified CATALOG recovery catalog. Action: Specify the CATALOG option on the RMAN command line. RMAN-00702: The command has no syntax errors Cause: This is an informational message only. Action: No action is required. RMAN-00703: The cmdfile has no syntax errors Cause: This is an informational message only. Action: No action is required. RMAN-01006: error signaled during parse Cause: An error was signaled during parsing. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-01007: at line number column number file: string Cause: This is an informational message indicating the line and column where a syntax error was detected. Action: No action is required. RMAN-01008: the bad identifier was: string Cause: This is an informational message indicating the identifier token that caused a syntax error. Action: No action is required. RMAN-01009: syntax error: found "string": expecting one of: "string" Cause: A syntax error was signaled during parsing. Action: Correct the input. RMAN-02000: wrong message file version (msg number not found) Cause: The rmanxx.msb file is not the correct version. Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your O/S) and the rmanxx.msb file must be from the same version, release, and patch level. RMAN-02001: unrecognized punctuation symbol "string" Cause: An illegal punctuation character was encountered. Action: Remove the illegal character. RMAN-02002: unexpected end of input file reached Cause: This is probably caused by failure to supply the closing quote for a quoted string. Action: Correct the input. RMAN-02003: unrecognized character: string Cause: An input character that is neither an alpha, digit, or punctuation was encountered. Action: Remove the character. RMAN-02004: quoted string too big Cause: A quoted string longer than 2000 bytes was encountered. Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string. RMAN-02005: token too big Cause: A token longer than 1000 bytes was encountered Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token. RMAN-02006: script line too long Cause: a line longer than 500 bytes was encountered Action: break the line up into shorter lines RMAN-02007: Integer value overflow Cause: Parser failed to convert input string to integer Action: Acceptable values for integer are from 0 to 2147483648. Retry command using valid integer value. RMAN-02008: no value exists for variable "string" Cause: The RMAN variable specified was either undefined or null Action: Verify that a proper value has been given to that variable. RMAN-02009: unexpected end of command file reached Cause: This is probably caused by failure to supply the closing brace for a stored script in a command file. Action: Correct the input. RMAN-03000: recovery manager compiler component initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03001: recovery manager command sequencer component initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03002: failure of string command at string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03003: command not implemented yet: string Cause: The command is not implemented in the current release. Action: Avoid using the command. RMAN-03004: fatal error during execution of command Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03008: error while performing automatic resync of recovery catalog Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03009: failure of string command on string channel at string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03010: fatal error during library cache pre-loading Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03011: Recovery Managerstring Cause: This is the RMAN banner Action: No action is required. RMAN-03012: fatal error during compilation of command Cause: A fatal error occurred during compilation of a command. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved. Cause: This is the copyright banner Action: No action is required. RMAN-03014: implicit resync of recovery catalog failed Cause: of the failure. Action: No action is required. RMAN-03015: error occurred in stored script string Cause: This is an informational message only. Action: No action is required. RMAN-03017: recursion detected in stored script string Cause: A stored script is calling itself or another script which calls itself. Action: Remove the recursion. RMAN-03018: asynchronous RPCs are working correctly Cause: This is an informational message only. Action: No action is required. RMAN-03019: asynchronous RPCs are NOT working Cause: The RPCTEST command has determined that RPCs are not executing asynchronously. Instead, they are blocking. This is caused by using a SQL*NET driver that does not support non-blocking UPI. Action: Try using a different SQL*NET driver. RMAN-03020: asynchronous RPC test will take 1 minute Cause: This is an informational message only. Action: No action is required. RMAN-03023: executing command: string Cause: This is an informational message only. Action: No action is required. RMAN-03028: fatal error code for command string : number Cause: Informational message. This precedes error 3012. Action: No action is required. RMAN-03029: echo set on Cause: a SET ECHO ON command was issued Action: No action is required. RMAN-03030: echo set off Cause: a SET ECHO OFF command was issued Action: No action is required. RMAN-03031: this option of set command needs to be used inside a run block Cause: The option used with the SET command is not valid outside a run block. Action: Change the SET command or place it inside a run block. RMAN-03032: this option of set command needs to be used outside of a run block Cause: The option used with the SET command is not valid inside of a run block. Action: Change the SET command or place it outside a run block. RMAN-03033: current log archived Cause: "ALTER SYSTEM ARCHIVE LOG CURRENT" command completed successfully. Action: None, this is an informational message. RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string Cause: An invalid DEBUG LEVEL was used. Action: Change the DEBUG LEVEL argument. RMAN-03035: Debugging turned off Cause: a DEBUG OFF command was issued Action: No action is required. RMAN-03036: Debugging set to level=number, types=string Cause: a DEBUG command was issued Action: No action is required. RMAN-03037: Spooling started in log file: string Cause: a SPOOL LOG TO ... command was issued Action: No action is required. RMAN-03038: Spooling started in trace file: string Cause: a SPOOL TRACE TO ... command was issued Action: No action is required. RMAN-03039: Spooling for log turned off Cause: a SPOOL LOG OFF command was issued Action: No action is required. RMAN-03040: Spooling for trace turned off Cause: a SPOOL TRACE TO ... command was issued Action: No action is required. RMAN-03042: error while analyzing automatic repair options Cause: of the failure. Action: No action is required. RMAN-03090: Starting string at string Cause: This is an informational message only. Action: No action is required. RMAN-03091: Finished string at string Cause: This is an informational message only. Action: No action is required. RMAN-03098: stringRMAN-number: stringstring Cause: This is the message prefix with a possible indentation. Action: No action is required. RMAN-03099: job cancelled at user request Cause: The user interrupted the current job. Action: None RMAN-03999: Oracle error occurred while while converting a date: ORA-number: string Cause: Internal error converting a date. Action: Contact Oracle Support Services. RMAN-04000: memory allocation failure Cause: A memory allocation request could not be satisfied. Action: Increase the amount of memory available to RMAN. RMAN-04001: heap initialization failure Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04002: OCIPI failed, ORA-string Cause: OCI process level initialization failed. Action: This error should not normally occur. RMAN-04003: OCIINIT failed Cause: The call to OCIEnvInit failed. Action: This error should not normally happen. Contact Oracle Customer Support. RMAN-04004: error from recovery catalog database: string Cause: Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04005: error from target database: string Cause: Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04006: error from auxiliary database: string Cause: Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04007: WARNING from recovery catalog database: string Cause: Non fatal Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04008: WARNING from target database: string Cause: Non fatal Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04009: WARNING from auxiliary database: string Cause: Non fatal Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04010: target database Password: Cause: No password was provided for the target database. Action: Provide target database password. RMAN-04011: recovery catalog database Password: Cause: No password was provided for the recovery catalog database. Action: Provide recovery catalog database password. RMAN-04012: auxiliary database Password: Cause: No password was provided for the auxiliary database. Action: Provide auxiliary database password. RMAN-04013: must connect before startup Cause: A STARTUP command was attempted before connecting to the database. Action: Connect to database before attempting STARTUP command. RMAN-04014: startup failed: string Cause: The database failed to startup. Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the startup command. RMAN-04015: error setting target database character set to string Cause: An error was received while setting the session character set in the target database. Action: This error should not normally happen. Contact Oracle Customer Support. RMAN-04016: could not get OCI error handle Cause: An error was received while initializing the OCI layer. Action: This error should not normally happen. Contact Oracle Customer Support. RMAN-04017: startup error description: string Cause: of failure. Action: No action is required. RMAN-04020: target database name "string" does not match channel's name: "string" Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database. Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command. RMAN-04021: target database DBID string does not match channel's DBID string Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database. Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command. RMAN-04022: target database mount id string does not match channel's mount id string Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database. Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command. RMAN-04024: starting Oracle instance without parameter file for retrieval of spfile Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters. Action: None - this is an informational message. RMAN-04025: unable to generate a temporary file Cause: Creation of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar). Action: Verify and free some system resources memory and try again. RMAN-04026: unable to open a temporary file: "string" Cause: Opening of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar). Action: Verify and free some system resources memory and try again. RMAN-04027: unable to write to a temporary file: "string" Cause: Writing to a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar). Action: Verify and free some system resources memory and try again. RMAN-04031: initialization parameters used for automatic instance: string Cause: This is an informational message only. Action: No action is required. RMAN-04032: using contents of file string Cause: The specified file was included as part of the auxiliary database parameter file. This is an informational message. Action: No action is required. RMAN-04033: cannot open auxiliary parameter file string Cause: An auxiliary parameter file was specified with SET AUXILIARY INSTANCE PARAMETER FILE command but the specified file cannot be found. Action: Set the parameter file to an existent file or retry the command without setting AUXILIARY INSTANCE PARAMETER FILE. RMAN-04034: source recovery catalog database Password: Cause: A password was not provided for the source recovery catalog database. Action: Provide source recovery catalog database password. RMAN-04035: error from source recovery catalog database: string Cause: Oracle error signaled by source recovery catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04036: WARNING from source recovery catalog database: string Cause: Nonfatal Oracle error signaled by source recovery catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-05000: CONFIGURE AUXNAME required for datafile string Cause: Either: -) The control file mounted by the auxiliary database does not have an entry for this datafile, therefore file name conversion is not possible. -) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this datafile. Action: Use the CONFIGURE AUXNAME command to specify a file name that the auxiliary database can use as a restore destination. RMAN-05001: auxiliary file name string conflicts with a file used by the target database Cause: RMAN is attempting to use the specified file name as a restore destination in the auxiliary database, but this name is already in use by the target database. Action: Use the CONFIGURE AUXNAME command to specify a name for the data file that does not conflict with a file name in use by the target db. RMAN-05002: aborting Tablespace Point-in-Time Recovery Cause: Previously encountered error(s) were issued which require corrective action. Action: Resolve the error conditions, and then re-issue the RECOVER command. RMAN-05003: Tablespace Point-in-Time Recovery is not allowed for tablespace string Cause: The SYSTEM, SYSUAX or a tablespace containing rollback segments is not allowed in Tablespace Point-in-Time Recovery. Action: Remove the indicated tablespace from the recovery set and retry the operation. RMAN-05004: target database log mode is NOARCHIVELOG Cause: An attempt was made to apply Tablespace Point-in-Time Recovery to a database that is in NOARCHIVELOG mode. Action: If all required archived log files are available for Tablespace Point-in-Time Recovery, alter the target database log mode to ARCHIVELOG and retry the Tablespace Point-in-Time Recovery operation. Otherwise, Tablespace Point-in-Time Recovery cannot be applied to this database. RMAN-05005: Tablespace Point-in-Time Recovery is not allowed for re-created tablespace string Cause: The requested tablespace has been re-created and is not allowed in Point-in-Time Recovery. Action: Remove the indicated tablespace from the recovery set and retry the operation. RMAN-05006: cannot recover clone standby single tablespaces Cause: Standby recover can only be performed for the whole database. Action: Change the tablespace list to a database specification. RMAN-05007: no channel allocated Cause: A command was entered that requires a channel, and no channel is allocated. Action: Use ALLOCATE CHANNEL before using the command RMAN-05009: Block Media Recovery requires Enterprise Edition Cause: The RECOVER...BLOCK command was specified. Action: Remove the RECOVER...BLOCK command. RMAN-05010: target database must be opened in READ WRITE mode for Tablespace Point-in-Time Recovery Cause: The target database was not opened in read write mode. Action: Open the database in read write mode. RMAN-05011: auxiliary instance must be in NOMOUNT state for Tablespace Point-in-Time Recovery Cause: The Auxiliary instance was not in NOMOUNT state. Action: Open the auxiliary instance in NOMOUNT state. RMAN-05013: auxiliary control file name string conflicts with a file used by the target database Cause: RMAN is attempting to use the specified control file name for Tablespace Point-in-Time Recovery as a restore destination in the auxiliary database, but this name is already in use by the target database. Action: Set control_files parameter in the auxiliary instance to a name that does not conflict with a file name in use by the target database. RMAN-05014: Tablespaces with undo segments were not found in recovery catalog Cause: The recovery catalog did not have information about tablespaces with undo segments. Action: Manually specify the tablespaces with undo segments in the optional UNDO tablespaces clause of the RECOVER command. RMAN-05015: WARNING: not enough information in recovery catalog for specified point-in-time recovery Cause: The recovery catalog did not have information about the tablespaces with undo segments at the specified Point-in-Time. This happened because the current recovery catalog was not in use at the specified Point-in-Time. A list of tablespaces with undo segments was supplied. Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces. RMAN-05016: failover to previous backup Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the datafile/archived logs/ control file/SPFILE using a previous existing backup. Action: See accompanying additional error messages indicating the cause of the failover. RMAN-05017: no copy of datafile number found to recover Cause: A RECOVER COPY command was not able to proceed because no copy of indicated file was found to recover. Possible causes include the following: 1. no copy of indicated file exists on disk that satisfy the criteria specified in the user's recover operands. 2. copy of indicated datafile exists on disk but no incremental backup was found to apply to the datafile copy. Action: One of the following: 1. Use or correct TAG specification to recover a different datafile copy. 2. Use BACKUP FOR RECOVER OF COPY command to create necessary incremental backup or copy. RMAN-05018: some datafile copies cannot be recovered, aborting the RECOVER command Cause: This error message can follow one or more RMAN-5017 or RMAN-5019 error messages. Action: See RMAN-5017 or RMAN-5019 error messages documentation for more information. RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile number Cause: A RECOVER COPY command could not proceed because incremental backup sets exist on a device type that has not been allocated. Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type. RMAN-05020: cannot specify AUXILIARY DESTINATION option for normal recovery Cause: The AUXILIARY DESTINATION option was specified for a normal recovery. It is only allowed for Tablespace Point-in-Time Recovery. Action: Remove the AUXILIARY DESTINATION option and re-run the RECOVER command. RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file Cause: The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY. The following configurations can be changed only when connected to primary database instance that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ENCRYPTION CONFIGURE DB_UNIQUE_NAME Action: Connect to primary database instance and execute the command. RMAN-05022: TRANSPORT TABLESPACE may not be used with user-managed auxiliary instance Cause: A user-managed auxiliary instance was specified. Action: Retry the operation with an RMAN-managed auxiliary instance. RMAN-05023: TABLESPACE DESTINATION required Cause: A required TABLESPACE DESTINATION was not specified. Action: Specify a TABLESPACE DESTINATION and retry the operation. RMAN-05024: List of tablespaces presumed to have UNDO segments Cause: Accompanying message to 5015. Action: See action of message 5015. RMAN-05025: Tablespace string Cause: Accompanying message to 5015. Action: See action of message 5015. RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time Cause: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces. Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces. RMAN-05027: List of tablespaces expected to have UNDO segments Cause: Accompanying message to 5026. Action: See action of message 5026. RMAN-05028: Tablespace string Cause: Accompanying message to 5026. Action: See action of message 5026. RMAN-05029: UNDO TABLESPACE clause is only valid for Tablespace Point-in-Time Recovery Cause: The UNDO TABLESPACE clause was specified for non-Tablespace Point-in-Time Recovery. Action: Remove the UNDO TABLESPACE clause. RMAN-05030: CLONE clause cannot be used with Tablespace Point-in-Time Recovery Cause: The CLONE clause was specified for a Tablespace Point-in-Time Recovery. Action: Remove the CLONE clause. RMAN-05031: cannot specify UNDO TABLESPACE clause for normal recovery Cause: The UNDO TABLESPACE clause was specified for a normal recovery. It is only allowed for Tablespace Point-in-Time Recovery. Action: Remove the UNDO TABLESPACE clause and re-run the RECOVER command. RMAN-05032: datafile string will be created automatically during restore operation Cause: The specified datafile did not have an available backup. Action: None. This is an informational message displayed for VALIDATE or PREVIEW option of the RESTORE command. RMAN-05033: Media recovery start SCN is string Cause: The above system change number (SCN) would be starting media recovery SCN, if the specified files are restored. Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command. RMAN-05034: Recovery must be done beyond SCN string to clear datafile fuzziness Cause: The above system change number (SCN) identifies the minimum SCN beyond which the media recovery must be performed on the specific datafile to clear the media recovery fuzziness for all datafile. Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command. RMAN-05035: archived logs generated after SCN string not found in repository Cause: The recovery catalog or target database control file did not have a record of archived logs containing the redo generated after the specified system change number (SCN). Action: None. To avoid this message, perform a log switch if the database is in open mode. RMAN-05036: FOR DB_UNIQUE_NAME option cannot be used for this configuration Cause: An attempt was made to set the configuration which cannot be used with FOR DB_UNIQUE_NAME option. Action: Remove FOR DB_UNIQUE_NAME option and execute the command. RMAN-05037: FOR DB_UNIQUE_NAME option cannot be used in nocatalog mode Cause: An attempt was made to set the remote configuration in nocatalog mode. Action: Connect to recovery catalog and execute the command. RMAN-05038: unable to determine UNTIL SCN for TRANSPORT Cause: No archived logs were found in the control file. Action: Add UNTIL clause to TRANSPORT command and retry. RMAN-05039: One or more auxiliary set datafiles could not be removed Cause: There was an error while performing Tablespace Point-in-Time Recovery. Some of the restored datafiles had OMF names and were not deleted. Action: Manually remove the auxiliary set datafiles that were not removed. RMAN-05040: List of tablespaces that have been dropped from the target database: Cause: One or more tablespaces in the recovery set were not found in the control file of the target database. Action: None. Informational message. RMAN-05041: Error during export of metadata Cause: Export of metadata received an error from Data Pump. Action: This message is accompanied by other error message(s) indicating the cause of the error. RMAN-05042: Error during import of metadata Cause: Import of metadata received an error from Data Pump. Action: This message is accompanied by other error message(s) indicating the cause of the error. RMAN-05043: Tablespace string Cause: Accompanying message to 5040. Action: See Action of message 5040. RMAN-05044: Performing export of metadata... Cause: This is an informational message only. Action: No action is required. RMAN-05045: Performing import of metadata... Cause: This is an informational message only. Action: No action is required. RMAN-05046: Export completed Cause: This is an informational message only. Action: No action is required. RMAN-05047: Import completed Cause: This is an informational message only. Action: No action is required. RMAN-05048: specified file name string conflicts with a file used by the target database Cause: The specified file name was already in use by another datafile in the database. Action: Use SET NEWNAME command to specify a different name for the datafile that does not conflict with a file name in use by the target database. RMAN-05049: datafile string is an Oracle Managed File, DB_CREATE_FILE_DEST not set at target Cause: A Tablespace Point-in-Time Recovery was attempted but the datafile is an Oracle Managed File and DB_FILE_CREATE_DEST is not currently set for the target database. Action: Specify DB_FILE_CREATE_DEST for the target database or provide a NEWNAME for the specified datafile. RMAN-05050: flashing back control file to SCN string Cause: RESTORE command was issued with a SET UNTIL clause and Flashback Database enabled. The control file was flashed back to the SET UNTIL time. Action: This is an informational message only. RMAN-05051: analyzing automatic repair options; this may take some time Cause: This is an informational message only. Action: No action is required. RMAN-05052: Repair string is not compatible with this version of RMAN. Cause: The specified repair was not compatible with this version of Recovery Manager (RMAN). Action: Use a newer version of the RMAN executable. RMAN-05053: AUXILIARY DESTINATION is only valid when using a RMAN-managed auxiliary instance Cause: AUXILIARY DESTINATION clause was specified while using an user-managed auxiliary instance. Action: Do not specify AUXILIARY DESTINATION clause and retry the operation or use a RMAN-managed auxiliary instance. RMAN-05054: recover block operand string cannot be used to recover datafile Cause: The specified operand could not be used with RECOVER datafile command. Action: Delete the invalid operand and retry the command. RMAN-05055: recover datafile operand string cannot be used to recover block Cause: The specified operand could not be used with RECOVER block command. Action: Delete the invalid operand and retry the command. RMAN-05060: block specifier must be specified to recover block Cause: Block Specifier was not specified in the command. Action: Specify block specifier and resubmit the command. RMAN-05061: analyzing automatic repair options complete Cause: This is an informational message only. Action: No action is required. RMAN-05062: image copy needs no roll forward Cause: The image copy that would be rolled forward by the RECOVER COPY command is already more recent than the specified UNTIL time or system change number (SCN). Action: Usually this is the result of a recent OPEN RESETLOGS operation, and no action is needed, because the daily backup strategy will start rolling this copy forward after it becomes old enough to be eligible for rolling forward. To force the copy to be rolled forward, specify a more recent UNTIL time or system change number (SCN). RMAN-05070: Running TRANSPORT_SET_CHECK on recovery set tablespaces Cause: This is an informational message only. Action: No action is required. RMAN-05071: TRANSPORT_SET_CHECK completed successfully Cause: This is an informational message only. Action: No action is required. RMAN-05072: TRANSPORT_SET_CHECK failed Cause: SYS.TS_PITR_CHECK was not empty for recovery set tablespaces. Action: Fix dependencies before attempting TSPITR again. RMAN-05073: Tablespace string creation SCN string is ahead of point-in-time SCN string Cause: The tablespace was found in the control file but the creation system change number (SCN) of the datafile(s) is after the specified point-in-time. This can happen if a previous tablespace point-in-time recovery was performed, for the tablespace. Action: If a previous TSPITR has been performed drop the tablespace and retry the command. Otherwise, verify the name of the tablespace and/or the point-in-time and resubmit the command. RMAN-05074: Tablespace string does not exist at specified point-in-time SCN string Cause: The tablespace was found in the control file but the creation system change number (SCN) of the datafile(s) is after the specified point-in-time. Action: Verify the name of the tablespace and/or the point-in-time and resubmit the command. RMAN-05500: the auxiliary database must be not mounted when issuing a DUPLICATE command Cause: A DUPLICATE command was issued, but the auxiliary database is mounted. Action: Dismount the auxiliary database. RMAN-05501: aborting duplication of target database Cause: Previously encountered errors require corrective action. Action: Resolve the error conditions, and reissue the DUPLICATE command. RMAN-05502: the target database must be mounted when issuing a DUPLICATE command Cause: A DUPLICATE command was issued, but the target database control file is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-05503: at least one auxiliary channel must be allocated to execute this command Cause: No auxiliary channels were allocated. Action: Allocate an auxiliary channel. RMAN-05504: at least two redo log files or groups must be specified for this command Cause: Only one redo log file or group was specified Action: Specify at least one more redo log file or group RMAN-05505: auxiliary file name conversion of 'string' exceeds maximum length of string Cause: When the given file name is converted to the name used for the auxiliary database, the converted name is larger than the maximum allowed file name. Action: Change initialization parameter DB_FILE_NAME_CONVERT to convert to a valid file name. RMAN-05506: error during recursive execution Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-05507: standby control file checkpoint (string) is more recent than duplication point-in-time (string) Cause: A DUPLICATE FOR STANDBY command was issued, but the checkpoint of the control file is more recent than the last archived log or the specified point-in-time. Action: If an explicit point-in-time was specified, change it to be at least the control file checkpoint; otherwise archive (and backup/copy) the current log. RMAN-05510: Duplicate finished Cause: This is an informational message only. Action: No action is required. RMAN-05511: Datafile string skipped by request Cause: This is an informational message only. Action: No action is required. RMAN-05512: Tablespace string cannot be skipped from duplication Cause: The SYSTEM and SYSAUX tablespaces were not included in the DUPLICATE DATABASE. They must be present. Action: Remove the SYSTEM and/or SYSAUX tablespace from the SKIP list and retry the operation. RMAN-05513: cannot duplicate, control file is not current or standby Cause: Target database did not have a current or standby control file. DUPLICATE requires the target database to have a current or standby control file. Action: Open database to make control file current or connect to a different database before retrying the command. RMAN-05514: Tablespace string has undo information, cannot skip Cause: All tablespaces that have undo information must be included in the duplication. Action: Remove the specified tablespace from the SKIP list and retry the operation. RMAN-05515: Duplicate for standby does not allow the use of SET UNTIL Cause: A SET UNTIL clause was specified for the command. Action: Remove the SET UNTIL clause and try again. RMAN-05516: duplicate operand specified: string Cause: The specified operand appears more than once in the same DUPLICATE option list Action: Delete the duplicated operand. RMAN-05517: tempfile string conflicts with file used by target database Cause: RMAN attempted to use the specified tempfile as a restore destination in the auxiliary database, but this name was already in use by the target database. Action: Use the SET NEWNAME FOR TEMPFILE command to specify a name for the indicated tempfile, making sure that the new name does not conflict with a file name in use by target database. Alternatively, use DB_FILE_NAME_CONVERT and retry the command. RMAN-05518: Automatically adding tablespace string Cause: This is an informational message only. Action: No action is required. RMAN-05519: WARNING: tablespace string is always included when duplicating Cause: The SYSTEM and SYSAUX tablespaces were included in the DUPLICATE TABLESPACE command. They were automatically included by the command and did not need to be explicitly named. Action: To avoid this warning,, remove the SYSTEM and/or SYSAUX tablespace from the tablespaces list and retry the operation. RMAN-05520: database name mismatch, auxiliary instance has string, command specified string Cause: The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command. Action: Correct the database name in the command or adjust the database name of the auxiliary instance. RMAN-05521: DUPLICATE without CATALOG and TARGET not open requires that UNDO TABLESPACE is specified Cause: A DUPLICATE was attempted when target database was not open without connection to a recovery catalog. It is necessary that the list of tablespaces with undo segments is provided with the UNDO TABLESPACE clause. Action: Retry the command specifying the list of tablespaces with undo segments using the UNDO TABLESPACE clause. RMAN-05522: Skipping tablespace string Cause: This is an informational message only. Action: No action is required. RMAN-05523: Tablespace string is read only and SKIP READONLY was specified Cause: Conflicting parameters were provided. Action: Remove SKIP READONLY or remove read-only tablespace from list of tablespaces to duplicate. RMAN-05524: Tablespace string is offline Cause: It was not possible to duplicate offline tablespaces. Action: Remove offline tablespace from list or online tablespace to duplicate it. RMAN-05525: SKIP TABLESPACE cannot be used when using DUPLICATE TABLESPACE Cause: A SKIP TABLESPACE clause was specified for the command. Action: Remove the SKIP TABLESPACE clause and try again. RMAN-05526: datafile number not processed because file is OFFLINE IMMEDIATE Cause: A DUPLICATE command omitted processing the indicated datafile because it is offline immediate. The tablespace to which this datafile belongs will also not be included. See message 5528. Action: None, informational message only. RMAN-05527: Tablespace string has one or more OFFLINE IMMEDIATE datafiles Cause: It was not possible to duplicate a tablespace who had offline immediate tablespaces. Action: Remove offending tablespace from list or recover datafile which are offline immediate in the tablespace before attempting the command again. RMAN-05528: datafile number not processed because file belongs to tablespace with one or more offline immediate datafile (string) Cause: A DUPLICATE command omitted processing the indicated datafile because it is part of a tablespace that has offline immediate datafile. See message 5526. Action: No action is required. This is an informational message only. RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only. Cause: It was not possible to convert ASM Oracle Managed Files names using DB_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead. Action: No action is required. This is an informational message only. If the automatic change is incorrect, use one of the following options instead of using DB_FILE_NAME_CONVERT for ASM Oracle Managed Files: 1) use RMAN command SET NEWNAME for each Oracle Managed File. 2) set DB_CREATE_FILE_DEST initialization parameter in auxiliary instance and not specify DB_FILE_NAME_CONVERT. RMAN-05530: an UNTIL TIME or SCN cannot be specified with FROM ACTIVE DATABASE Cause: A DUPLICATE with FROM ACTIVE DATABASE was specified along with either a SET UNTIL statment or UNTIL clause on the command. This is not supported. A DUPLICATE FROM ACTIVE DATABASE always creates a copy as of the current time. Action: Check the statement and remove the use of UNTIL. RMAN-05531: a mounted database cannot be duplicated while datafiles are fuzzy Cause: A DUPLICATE with FROM ACTIVE DATABASE command was specified while the database was mounted or open read-only. Unless the database is open read/write, the datafiles cannot be fuzzy. Action: Open the database read/write, then shutdown cleanly before mounting. RMAN-05532: PASSWORD FILE specified without FROM ACTIVE DATABASE Cause: The PASSWORD FILE clause of the DUPLICATE command was specified but the FROM ACTIVE DATABASE clause was not. A password file can only be duplicated if the FROM ACTIVE DATABSE clause has been used. Action: Remove the PASSWORD FILE clause from the command, or perform an online duplicate of the database by specifying the FROM ACTIVE DATABASE clause. RMAN-05533: string is not supported on string database Cause: The specified command is not supported on this type of database. The type of database can be STANDBY, CLONE, or RAC. Action: Do not use the specified command against this database. RMAN-05534: WARNING: LOG_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only. Cause: It was not possible to convert ASM Oracle Managed Files names using LOG_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead. Action: If the automatic change is incorrect, use one of the following options instead of using LOG_FILE_NAME_CONVERT for ASM Oracle Managed Files: 1) Use the LOGFILE clause for online log files. 2) After DUPLICATE completes, create standby log files using the SQL ALTER DATABASE ADD STANDBY LOGFILE command. RMAN-05535: WARNING: All redo log files were not defined properly. Cause: It was not possible to define all the redo log files. This can occur when LOG_FILE_NAME_CONVERT initialization parameter is defined but fails to match all the names or causes names to be created that are not in valid directories. Action: Query the V$LOGFILE view to see what redo log files are defined after DUPLICATE has completed. Use the ALTER DATABASE RENAME FILE SQL command to correctly name the existing redo log files. RMAN-05536: auxiliary logfile name string conflicts with a file used by the target database Cause: RMAN attempted to use the specified logfile name as a standby redo log file in the auxiliary database, but this name was already in use by the target database. Action: Use or alter LOG_FILE_NAME_CONVERT so that unique logfile names can be generated. Or wait for the command to complete and create standby logfiles using the SQL ALTER DATABASE ADD STANDBY LOGFILE command. RMAN-05537: DUPLICATE without TARGET connection when auxiliary instance is started with spfile cannot use SPFILE clause Cause: A DUPLICATE was attempted when the auxiliary database was started with a server parameter file and the SPFILE sub-clause was specified. RMAN cannot restore the server parameter file if the auxiliary database is already started with a server parameter file. Action: Start the auxiliary database with a client parameter file or do not specify SPFILE sub-clause and retry. RMAN-05538: WARNING: implicitly using DB_FILE_NAME_CONVERT Cause: The duplicated SPFILE had DB_FILE_NAME_CONVERT set and it has been used to produce datafile names for the new database. Action: No action is required. This is an informational message only. If this behavior was not intended, then do not duplicate the server parameter file, or explicitly set DB_FILE_NAME_CONVERT in the DUPLICATE command and retry the operation. RMAN-05539: DUPLICATE TARGET DATABASE cannot be used without connecting to the TARGET Cause: A DUPLICATE TARGET DATABASE was attempted and no connection to the TARGET database was established. Action: Connect to TARGET or use DATABASE <db_name> clause. RMAN-05540: no archived logs found in repository for database string Cause: Recovery catalog did not have archived log records for the specified database. If database is running in NOARCHIVELOG mode, then specify NOREDO. Action: Specify NOREDO for NOARCHIVELOG databases. Cannot duplicate an ARCHIVELOG database unless the recovery catalog or target database control file has archived redo log information about it. RMAN-05541: no archived logs found in target database Cause: Target database was running in archived log mode, but control file did not have any archived log records. Action: Archive current log before retrying command. RMAN-05542: Only UNTIL TIME can be used with DUPLICATE without TARGET and CATALOG connections Cause: A DUPLICATE without TARGET and CATALOG connections was attempted specifying an UNTIL clause that was not TIME based. Action: Retry the command with an UNTIL TIME clause or without an UNTIL clause. RMAN-05543: DUPLICATE without TARGET connection requires that DATABASE is specified Cause: A DUPLICATE without TARGET connection was attempted without specifying the database to duplicate. Action: Retry the command specifying the DATABASE to duplicate. RMAN-05544: Cannot specify ACTIVE DATABASE when not connected to target database Cause: DUPLICATE from ACTIVE DATABASE required a connection to the target database. Action: Connect to target database or remove from ACTIVE DATABASE and retry the command. RMAN-05545: WARNING: Until SCN string is ahead of SCN of last full resync of recovery catalog: string Cause: The specified point-in-time for duplication without a target connection was ahead of the last time that the datafile information was resynced to the recovery catalog. Information about offline and read-only datafiles might be incorrect. Action: If duplication fails due to incorrectly identified offline and/or read-only datafiles, specify a point-in-time before the last resync of the recovery catalog and retry the command. Or perform full resync of the target database and retry the command. RMAN-05546: DUPLICATE without TARGET and CATALOG connections requires that BACKUP LOCATION is specified Cause: A DUPLICATE without TARGET and CATALOG connections was attempted without specifying BACKUP LOCATION. Action: Retry the command specifying a BACKUP LOCATION. RMAN-05547: Checking that duplicated tablespaces are self-contained Cause: This is an informational message only. Action: No action is required. RMAN-05548: The set of duplicated tablespaces is not self-contained Cause: A DUPLICATE TABLESPACE has specified a set of tablespaces that cannot function independently. Action: Retry the command without incomplete tablespaces or add other tablespaces to make the set self-contained. RMAN-05549: The following SYS objects were found in skipped tablespaces Cause: This is an informational message only. Action: No action required. RMAN-05550: TARGET database not open, cannot verify that set of tablespaces being duplicated does not have SYS objects Cause: This is an informational message only. Action: No action is required. RMAN-05551: Not connected to TARGET, cannot verify that set of tablespaces being duplicated does not have SYS objects Cause: This is an informational message only. Action: No action is required. RMAN-05552: Object string on tablespace string Cause: A SYS object was found in one of the skipped tablespaces. Action: Remove object if possible or include tablespace in duplicated tablespaces. RMAN-05553: SYS objects in skipped tablespaces prevent duplication Cause: Objects owned by SYS were found in the tablespaces that would not be duplicated. Action: If using SKIP TABLESPACE, do not skip tablespaces that contain SYS objects. If using DUPLICATE TABLESPACE, make sure to specify all tablespaces containing SYS objects. RMAN-05554: cannot specify INCARNATION when duplicating without TARGET and CATALOG connections Cause: A DUPLICATE without TARGET and CATALOG connections was attempted when INCARNATION was also specified. Action: Retry the command without specifying INCARNATION. RMAN-05555: Not connected to TARGET or TARGET not open, cannot verify that subset of tablespaces is self-contained Cause: This is an informational message only. Action: No action is required. RMAN-05556: not all datafiles have backups that can be recovered to SCN string Cause: One or more datafiles being duplicated could not be restored as no available backups were found. Action: Change the system change number (SCN) or make backups available for the specified datafiles and retry the command. RMAN-05557: Target instance not started with server parameter file Cause: SPFILE clause was used but target instance was not started with a server parameter file. Action: Do not specify SPFILE clause, or restart target instance with server parameter file. RMAN-05558: Must specify DB_UNIQUE_NAME with FOR STANDBY clause Cause: A DUPLICATE FOR STANDBY ... SPFILE command was issued but DB_UNIQUE_NAME was not provided for the standby database. Action: Specify a DB_UNIQUE_NAME in the SPFILE clause for the standby database. RMAN-05559: error converting parameter string, string larger than number Cause: While attempting to apply a PARAMETER_VALUE_CONVERT to the specified parameter value, the resulting string exceeded the maximum length for a value. Action: Change the PARAMETER_VALUE_CONVERT so that, when converting the parameter, the maximum lenght is not reached. RMAN-05560: Using previous duplicated file string for datafile number with checkpoint SCN of string Cause: A datafile copy from a previous duplicate attempt matching the duplicate name requested was found for the specified datafile and will be used instead of restoring the datafile from a backup. Action: No action needed unless this behavior is not desire. In that case, either use a different name for the datafile or use NORESUME to avoid using previous datafile copies for all the datafiles. RMAN-05561: CATALOG did not return information about tablespaces with undo segments Cause: A DUPLICATE with no target connection was attempted, but the recovery catalog did not have information about the tablespaces with undo segments at the specified point in time. It is necessary that the list of tablespaces with undo segments is provided with the UNDO TABLESPACE clause. Action: Retry the command specifying the list of tablespaces with undo segments using the UNDO TABLESPACE clause. RMAN-05562: SPFILE backup not found for database string with DBID number created before string in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05563: SPFILE backup not found for database with DBID number created before string in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05564: SPFILE backup not found for database string created before string in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05565: SPFILE backup created before string not found in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05566: SPFILE backup not found for database string with DBID number in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05567: SPFILE backup not found for database with DBID number in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05568: SPFILE backup not found for database string in string Cause: RMAN could not locate a backup of the SPFILE in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05569: SPFILE backup not found in string Cause: RMAN could not locate a backup of the SPFILE in the specified location. Action: Provide a different location and retry the command. RMAN-05570: Duplicate for standby does not allow the use of LOGFILE Cause: A LOGFILE clause was specified for the command. Action: Remove the LOGFILE clause and try again. RMAN-05571: DORECOVER specified for non standby duplication Cause: A DORECOVER clause was specified and the duplicate did not specify FOR STANDBY. Action: Remove the DORECOVER clause or add FOR STANDBY and try again. RMAN-05572: Controlfile backup not found for database string with DBID number created before string in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05573: CONTROLFILE backup not found for database with DBID number created before string in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05574: CONTROLFILE backup not found for database string created before string in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05575: CONTROLFILE backup created before string not found in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05576: CONTROLFILE backup not found for database string with DBID number in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05577: CONTROLFILE backup not found for database with DBID number in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05578: CONTROLFILE backup not found for database string in string Cause: RMAN could not locate a backup of the control file in the specified location that satisfied the specified parameters. Action: Change the parameters, or provide a different location and retry the command. RMAN-05579: CONTROLFILE backup not found in string Cause: RMAN could not locate a backup of the control file in the specified location. Action: Provide a different location and retry the command. RMAN-05580: Duplicate for standby does not allow the use of SKIP READONLY Cause: A SKIP READONLY clause was specified for the command. Action: Remove the SKIP READONLY clause and try again. RMAN-05581: Duplicate for standby does not allow the use of SKIP TABLESPACE Cause: A SKIP TABLESPACE clause was specified for the command. Action: Remove the SKIP TABLESPACE clause and try again. RMAN-05582: Duplicate for standby does not allow the use of OPEN RESTRICTED Cause: An OPEN RESTRICTED clause was specified for the command. Action: Remove the OPEN RESTRICTED clause and try again. RMAN-05583: Duplicate for standby does not allow the use of TABLESPACE Cause: A TABLESPACE clause was specified for the command. Action: Remove the TABLESPACE clause and try again. RMAN-05584: Duplicate for standby does not allow the use of NOREDO Cause: A NOREDO clause was specified for the command. Action: Remove the NOREDO clause and try again. RMAN-05585: Duplicate for standby does not allow the use of UNDO TABLESPACE Cause: A UNDO TABLESPACE clause was specified for the command. Action: Remove the UNDO TABLESPACE clause and try again. RMAN-05586: The following materialized objects were found in skipped tablespaces Cause: This is an informational message only. Action: No action required. RMAN-05587: Materialized table string on tablespace string Cause: A materialized table was found in one of the skipped tablespaces. Action: Remove object if possible or include tablespace in duplicated tablespaces. RMAN-05588: Materialized index string on tablespace string Cause: A materialized index was found in one of the skipped tablespaces. Action: Remove object if possible or include tablespace in duplicated tablespaces. RMAN-05589: Materialized objects in skipped tablespaces prevent duplication Cause: Materialized objects found in the tablespaces that would not be duplicated. Action: If using SKIP TABLESPACE, do not skip tablespaces that contain materialized objects. If using DUPLICATE TABLESPACE, make sure to specify all tablespaces containing SYS objects. RMAN-05590: Reenabling controlfile options for auxiliary database Cause: This is an informational message only. Action: No action is required. RMAN-05591: Ignoring error, reattempt command after duplicate finishes Cause: A sql error was received during the execution of command. Action: Check the accompanying errors. RMAN-05592: Dropping offline and skipped tablespaces Cause: This is an informational message only. Action: No action is required. RMAN-05593: Could not drop tablespace string due to constraints, will reattempt removal after other tablespaces are removed Cause: This is an informational message only. Action: No action is required. RMAN-05594: Could not drop tablespace string due to constraints Cause: The tablespace failed to be dropped several times, no more attempts will be made. Action: Drop the tablespace manually after duplicate finishes. RMAN-05595: Leaving database unopened, as requested Cause: User requested that the new database was not open. Action: After the database is opened with resetlogs you might want to: - Catalog datafilecopies of readonly datafiles - Switch readonly datafiles to the cataloged datafilecopies - Online read only tablespaces - Drop skipped tablespaces - Enable supplemental logging - Enable force logging - Enable change tracking RMAN-05596: Error while removing created server parameter file Cause: Server parameter file was not deleted. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. Remove file manually. RMAN-05597: Database started with server parameter file and PFILE clause used in command Cause: A PFILE clause was specified for duplicate command, but database was started with a server parameter file causing a conflict. Action: Remove PFILE clause from command or restart database without using a server parameter file. RMAN-05598: SPFILE and PFILE clause specified in command Cause: SPFILE and PFILE clauses were specified for duplicate command causing a conflict. Action: Remove either one of the clauses and retry the command. RMAN-05599: PASSWORD clause is not needed when duplicating for standby database from active database Cause: PASSWORD clause was specified when creating a standby database from active database. This is not needed, it is automatic. Action: No action is required. This is an informational message only. RMAN-05600: Cannot specify UNTIL clause when duplicating from active database Cause: An UNTIL clause in the command or with a SET UNTIL was in effect for an active database duplication. Action: Remove UNTIL clause and reattempt duplication. RMAN-05601: Failed to restore original settings to server parameter file Cause: An error was received while duplicating the database after the server parameter file was modified by RMAN. An attempt was made to restore original settings to the server parameter file, but the original error was such that it was not possible to restore the settings. Action: Before reattempting database duplication, the server parameter file needs to be fixed manually with the original values. RMAN-05602: restarting auxiliary database without server parameter file Cause: This is an informational message only. Action: No action is required. RMAN-06000: could not open recovery manager library file: string Cause: The "recover.bsq" file could not be opened. Action: Check that the file was installed correctly and that the user running RMAN has authority to read the file. RMAN-06001: error parsing job step library Cause: A syntax error was encountered while parsing "recover.bsq". Action: Ensure that the correct version of the file is installed and that it has not been modified in any way. RMAN-06002: command not allowed when not connected to a recovery catalog Cause: A command that is allowed only when a recovery catalog connect string was supplied was attempted. Action: Avoid using the command, or restart RMAN and supply a recovery catalog connect string via the CATALOG parameter. RMAN-06003: ORACLE error from target database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06004: ORACLE error from recovery catalog database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06005: connected to target database: string (DBID=string) Cause: This is an informational message only. Action: No action is required. RMAN-06006: connected to target database: string (not mounted) Cause: This is an informational message only. Action: No action is required. RMAN-06007: target database not mounted and db_name not set in init.ora Cause: The target database has not mounted the control file, and its "init.ora" file does not specify the DB_NAME parameter. Action: MOUNT the target database, or add the DB_NAME parameter to its "init.ora" and restart the instance. RMAN-06008: connected to recovery catalog database Cause: This is an informational message only. Action: No action is required. RMAN-06009: using target database control file instead of recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-06010: error while looking up datafile: string Cause: An error occurred while looking up the specified datafile in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06011: invalid level specified: number Cause: An invalid incremental backup level was specified. Action: Incremental backup level must be between 0 and 4. RMAN-06012: channel: string not allocated Cause: A RELEASE command was found for a channel identifier that was not yet allocated. Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command. RMAN-06013: duplicate channel identifier found: string Cause: A channel identifier was reused without first releasing the channel. Action: Add a RELEASE CHANNEL command. RMAN-06014: command not implemented yet: string Cause: Not all commands are implemented for the beta release. Action: Avoid using the command. RMAN-06015: error while looking up datafile copy name: string Cause: An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the datafile copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06016: duplicate backup operand specified: string Cause: The specified operand appears more than once in the same backup specifier or backup command. Action: Delete the duplicated operand. RMAN-06017: initialization of parser failed Cause: The parser package initialization routine returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06018: duplicate operand specified in backup specification: string Cause: A backup specification operand appears more than once in a backup specification. Action: Delete the duplicate operand. RMAN-06019: could not translate tablespace name "string" Cause: An error occurred while looking up the specified tablespace name in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06020: connected to auxiliary database (not started) Cause: This is an informational message only. Action: No action is required. RMAN-06021: FROM DATAFILECOPY/BACKUPSET may not be specified with archived logs Cause: The FROM DATAFILECOPY/BACKUPSET option applies only to datafile and control file restores. Action: Use this option only for datafile and control file restores. RMAN-06022: invalid level specified for image copy: number Cause: An invalid incremental backup level was specified for an image copy. Action: Incremental backup level must be 0 for image copies. RMAN-06023: no backup or copy of datafile number found to restore Cause: A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: None - this is an informational message. See message 6026 for further details. RMAN-06024: no backup or copy of the control file found to restore Cause: A control file restore could not proceed because no backup or copy of the control file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: None - this is an informational message. See message 6026 for further details. RMAN-06025: no backup of archived log for thread number with sequence number and starting SCN of string found to restore Cause: An archived log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: None - this is an informational message. See message 6026 for further details. RMAN-06026: some targets not found - aborting restore Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged. Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list. RMAN-06027: no archived logs found that match specification Cause: An archived log record specifier did not match any archived logs in the recovery catalog or target database control file. Action: Resubmit the command with a different archived log record specifier. The Recovery Manager (RMAN) LIST command can be used to display all archived logs that RMAN knows about. RMAN-06028: duplicate operand specified in restore specification: string Cause: The CHANNEL, TAG, FROM, PARMS, VALIDATE, DEVICE TYPE, CHECK READONLY or DB_UNIQUE_NAME option was specified more than once in the restore command or in one of the restore specifications. Action: Correct and resubmit the command. RMAN-06029: the control file may be included only in a datafile backup set Cause: The "include current/standby control file" option was specified for an archived log backup set. Action: Use this option only for datafile backup sets. RMAN-06030: the DELETE [ALL] INPUT option may not be used with a datafile backup set Cause: The DELETE [ALL] INPUT option was specified for a backup that contains the current control file or datafile. Action: Remove the option and resubmit the command. RMAN-06031: could not translate database keyword Cause: An error was received when calling DBMS_RCVMAN Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06032: at least 1 channel of TYPE DISK must be allocated to execute a COPY command Cause: No channel of TYPE DISK was allocated. Action: Allocate a channel of TYPE DISK and re-issue the command. RMAN-06033: channel string not allocated Cause: An rman command requests a specific channel, but the requested channel has not been allocated. Action: ALLOCATE the channel, or correct the channel identifier. RMAN-06034: at least 1 channel must be allocated to execute this command Cause: No channels were allocated. Action: ALLOCATE a channel. RMAN-06035: wrong version of recover.bsq, expecting string, found string Cause: The "recover.bsq" file is incompatible with the RMAN executable. Action: Install the correct version of recover.bsq. RMAN-06036: datafile number is already restored to file string Cause: A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken. Action: None - this is an informational message. RMAN-06038: recovery catalog package detected an error Cause: A call to DBMS_RCVMAN returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06039: SET NEWNAME command has not been issued for datafile string Cause: A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued. Action: Correct and resubmit the SWITCH command. RMAN-06040: control file is already restored to file string Cause: The best candidate control file for restoration is the one that is named in the RESTORE CONTROLFILE command, hence no action need be taken. Action: None - this is an informational message. RMAN-06041: cannot switch file number to copy of file number Cause: An attempt was made to switch a datafile to a copy of a different datafile. Action: Correct and resubmit the SWITCH command. RMAN-06042: PLUS ARCHIVELOG option is not supported with non-datafile backups Cause: The PLUS ARCHIVELOG option was supplied but does not apply to this type of backup. Action: Remove the PLUS ARCHIVELOG operand and re-enter the command. RMAN-06043: TAG option not supported for archived log copies Cause: The tag option was supplied but does not apply to this type of copy. Action: Remove the TAG operand and re-enter the command RMAN-06045: LEVEL option not supported for archived log or current/standby control file copies Cause: The LEVEL option was supplied but does not apply to this type of copy. Action: Remove the LEVEL operand and re-enter the command. RMAN-06046: archived log name: string Cause: An error occurred while translating an archived log name to its recovery catalog RECID/time stamp. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06047: duplicate datafile number specified for restoration from copy Cause: The indicated datafile was specified more than once in the same restore command. Action: Correct and resubmit the RESTORE command. RMAN-06048: duplicate control file specified for restoration from copy Cause: The control file was specified more than once in the same RESTORE command. Action: Correct and resubmit the RESTORE command. RMAN-06049: CHECK LOGICAL option not supported for archived log or current/standby control file copies Cause: The check logical option was supplied but does not apply to this type of copy. Action: Remove the CHECK LOGICAL operand and re-enter the command RMAN-06050: archived log for thread number with sequence number is already on disk as file string Cause: An archived log which was requested to be restored (either explicitly or via a range specification) does not need to be restored because it already exists on disk. Action: None - this is an informational message RMAN-06051: DELETE INPUT option not implemented yet Cause: This option was specified in a backup specification. Action: Remove the DELETE INPUT option. RMAN-06052: no parent backup or copy of datafile number found Cause: An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically. Action: This is an informational message only. RMAN-06053: unable to perform media recovery because of missing log Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available. Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point-in-time recovery up to the missing log is the only alternative. RMAN-06054: media recovery requesting unknown archived log for thread string with sequence string and starting SCN of string Cause: Media recovery is requesting a log whose existence is not recorded in the recovery catalog or target database control file. Action: If a copy of the log is available, then add it to the recovery catalog and/or control file via a CATALOG command and then retry the RECOVER command. If not, then a point-in-time recovery up to the missing log is the only alternative and database can be opened using ALTER DATABASE OPEN RESETLOGS command. RMAN-06055: could not find archived log with sequence string for thread string Cause: A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found. Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Support Services. RMAN-06056: could not access datafile number Cause: A backup or copy could not proceed because the datafile header could not be read or the header was not valid. Action: Make the datafile accessible or skip it. RMAN-06057: a standby control file cannot be included along with a current control file Cause: "current control file" was specified along with "standby control file". Action: Remove "current control file" or "standby control file" from backup specification. RMAN-06058: a current control file cannot be included along with a standby control file Cause: "standby control file" was specified along with "current control file". Action: Remove "standby control file" or "current control file" from backup specification. RMAN-06059: expected archived log not found, loss of archived log compromises recoverability Cause: The archived log was not found. The recovery catalog or target database control file thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point-in-time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the recovery catalog or target database control file. Action: If the archived log has been removed with an outside utility and the archived log has already been backed up, then you can synchronize the recovery catalog or target database control file by running CROSSCHECK ARCHIVELOG ALL. If the archived log has not been previously backed up, then you should take a full backup of the database and archived logs to preserve recoverability. Previous backups are not fully recoverable. RMAN-06060: WARNING: skipping datafile compromises tablespace string recoverability Cause: SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping datafile during BACKUP. If the datafile has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archived logs since datafile creation. This may occur because the datafile was deleted by an outside utility or the datafile is made OFFLINE [DROP]. Action: If there is no backup of skipped datafile and the tablespace has to be recoverable without ALL archived logs since datafile creation, then you should make these datafile available for backup. RMAN-06061: WARNING: skipping archived log compromises recoverability Cause: SKIP INACCESSIBLE option resulted in skipping archived logs during BACKUP. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point-in-time covered by the archived log. This may occur because archived log was removed by an outside utility without updating the recovery catalog or target database control file. Action: If the archived log has been removed with an outside utility and the archived log has already been backed up, then you can synchronize the recovery catalog or target database control file by running CROSSCHECK ARCHIVELOG ALL. If the archived log has not been previously backed up, then you should take a full backup of the database and archived logs to preserve recoverability. Previous backups are not fully recoverable. RMAN-06062: 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 or modify the command. RMAN-06063: DBID is not found in the recovery catalog Cause: DBID is not found in the recovery catalog. Action: Verify that the DBID is correct and restart the command. RMAN-06064: creating datafile file number=string name=string Cause: RESTORE/RECOVER command was issued and there were no backup available for the datafile. Action: This is an informational message only. RMAN-06065: The backup operand [string] conflicts with another specified operand. Cause: The user attempted to use two (or more) conflicting operands within the same statement. Action: Remove one or both of the conflicting operands. RMAN-06066: the target database must be mounted when issuing a RECOVER command Cause: A RECOVER command was issued, but the target database control file is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-06067: RECOVER DATABASE required with a backup or created control file Cause: The control file has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE. Action: Use the RECOVER DATABASE command to perform the recovery. RMAN-06068: recovery aborted because of missing datafiles Cause: This error should be accompanied by one or more instances of message ORA-19687ORA-19687ORA-06094ORA-06094. Action: Refer to message . RMAN-06069: the file name for datafile string is missing in the control file Cause: Media recovery of a backup control file added this datafile to the control file, but it does not set the file name because that is unsafe. Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace. RMAN-06070: DBWR could not identify datafile string Cause: DBWR could not find the specified datafile. Action: Ensure that the datafile exists and is accessible. RMAN-06071: could not open datafile string Cause: An error was encountered when trying to open the specified datafile. Action: Ensure that the datafile exists and is accessible. RMAN-06073: file header is corrupt for datafile string Cause: ORACLE detected a corruption in the file header. A media failure has probably occurred. Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command. RMAN-06074: file string is not an ORACLE datafile Cause: The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted. Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command. RMAN-06075: datafile string does not belong to this database Cause: The file header indicates that this file belongs to some other ORACLE database. Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command. RMAN-06076: datafile string contains wrong datafile Cause: The datafile header indicates the file contains a different datafile number. Action: RESTORE the datafile, and then retry the RECOVER command. RMAN-06077: datafile string is a different version than contained in the control file Cause: The control file entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers. Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command. RMAN-06078: the control file is older than datafile string Cause: The control file appears to be older than the specified datafile, but it is not marked as a backup control file. This indicates that the control file has been replaced with an older version. This error does not occur when a backup control file which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such control files are marked as backups. Action: RESTORE a control file and perform RECOVER DATABASE. RMAN-06079: database must be mounted to perform recovery Cause: A RECOVER command was issued, but the target database is not mounted. Action: Issue ALTER DATABASE MOUNT. RMAN-06080: SWITCH required for datafile string Cause: The control file record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to updated the control file before doing RECOVER. Action: Issue SWITCH command then retry RECOVER. RMAN-06081: error reading datafile header for datafile string, code string Cause: X$KCVFH returned the specified code in the HXERR column when it was queried for the specified datafile. Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Support Services. RMAN-06082: datafile copy tag string is ambiguous Cause: The specified tag refers to multiple datafile copies belonging to different datafiles. Action: Specify the datafile copy by file name rather than by tag. RMAN-06083: error when loading stored script string Cause: The recovery catalog database returned an error. This error explains the cause of the problem. Action: Correct the problem and retry. RMAN-06084: the target database may not be mounted when issuing REPLICATE Cause: A REPLICATE command was issued, but the target database is already mounted. Action: dismount the target database control file by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager. RMAN-06085: must use SET NEWNAME command to restore datafile string Cause: A RESTORE command for the specified datafile could not find a destination name for the specified datafile. Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file. RMAN-06086: offline files may only be skipped in a datafile backup set Cause: The SKIP OFFLINE option was specified for an archived log backup set. Action: Use this option only for datafile backup sets. RMAN-06087: read-only files may only be skipped in a datafile backup set Cause: The SKIP READONLY option was specified for an archived log backup set. Action: Use this option only for datafile backup sets. RMAN-06088: datafile copy string not found or out of sync with catalog Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database. Action: Re-catalog the file and retry the operation. RMAN-06089: archived log string not found or out of sync with catalog Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database. Action: Re-catalog the file and retry the operation. RMAN-06090: error while looking up control file copy: string Cause: An error occurred while looking up the specified control file copy in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the control file copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06091: no channel allocated for maintenance (of an appropriate type) Cause: A command was entered that requires a maintenance channel, and no maintenance channel is allocated, or none of the appropriate type. Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup pieces, or using the CROSSCHECK or DELETE EXPIRED commands. Proxy copies require a non-DISK channel. RMAN-06092: error while looking up backup piece Cause: An error occurred while looking up the specified backup piece in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the backup piece was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06093: recovery catalog contains obsolete version of datafile string Cause: The specified datafile number was dropped and then reused. The control file mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version. Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle Support Services. RMAN-06094: datafile string must be restored Cause: A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the control file, and cannot be found on disk. Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER. RMAN-06095: a backup control file must be restored to recover datafile string Cause: The control file currently mounted by the target database contains a newer incarnation of the datafile than the recovery catalog indicates is appropriate for the Point-in-Time being recovered to. Action: Restore the control file, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no control file can be restored, then you should issue a CREATE CONTROLFILE command. RMAN-06096: SWITCH required for newname of datafile string to take effect Cause: A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command. Action: Issue a SWITCH command to make the newname take effect before doing RECOVER. RMAN-06098: the target database must be mounted when issuing a BACKUP command Cause: A BACKUP command was issued, but the target database control file is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-06099: error occurred in source file: string, line: number Cause: See accompanying error. Action: See accompanying error. RMAN-06100: no channel to restore a backup or copy of datafile number Cause: A datafile, tablespace, or database restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore. Action: None - this is an informational message. See message 6026 for further details. RMAN-06101: no channel to restore a backup or copy of the control file Cause: A control file restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore. Action: None - this is an informational message. See message 6026 for further details. RMAN-06102: no channel to restore a backup or copy of archived log for thread number with sequence number and starting SCN of string Cause: An archived log restore restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore. Action: None - this is an informational message. See message 6026 for further details. RMAN-06103: duplicate qualifier found in REPORT command: string Cause: The indicated qualifier appears more than once in a REPORT qualifier list. Action: delete the duplicate qualifier RMAN-06105: duplicate qualifier found in LIST command: string Cause: The indicated qualifier appears more than once in a LIST qualifier list. Action: delete the duplicate qualifier RMAN-06106: this command requires that target database be mounted Cause: A command was issued that requires the target database to be mounted, but the target database is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-06107: WARNING: control file is not current for REPORT NEED BACKUP DAYS Cause: The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current control file is mounted. Action: No action is required, however, a current control file should be mounted, if possible, to get the most accurate REPORT output. RMAN-06108: changed datafile copy unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06109: changed archived log unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06110: changed control file copy unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06111: changed backup piece unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06112: changed datafile copy available Cause: This is an informational message only. Action: No action is required. RMAN-06113: changed archived log available Cause: This is an informational message only. Action: No action is required. RMAN-06114: changed control file copy available Cause: This is an informational message only. Action: No action is required. RMAN-06115: changed backup piece available Cause: This is an informational message only. Action: No action is required. RMAN-06116: cannot crosscheck unavailable object Cause: An attempt was made to crosscheck an object which is unavailable. Action: Make object available and try again or don't crosscheck object. RMAN-06117: cannot do DELETE EXPIRED on an object which is not expired Cause: An attempt was made to DELETE EXPIRED an object which is not expired. Action: Remove EXPIRED keyword, crosscheck object, or don't delete object. RMAN-06118: a backup control file older than SCN string must be used for this recovery Cause: An attempt was made to recover the database, but some files had no backup, and were not present in the control file at the beginning of the restore. This happens when the control file used during the recovery is a backup control file taken before the creation of some of the files that had no backup. In this situation, the control file that is used must be taken before the creation of all files that have no backup. This will enable RMAN to automatically re-create all of the files that had no backup. Action: Restore a control file that was backed up before the specified system change number (SCN). The following RMAN commands can be used to do this: SET UNTIL SCN <x>; (where <x> is the SCN displayed in the message) RESTORE CONTROLFILE; RMAN-06119: uncataloged datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-06120: uncataloged archived log Cause: This is an informational message only. Action: No action is required. RMAN-06121: uncataloged control file copy Cause: This is an informational message only. Action: No action is required. RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET Cause: The CHANGE BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup set. Action: Use CHANGE BACKUPSET .. DELETE instead. RMAN-06123: operation not supported without the recovery catalog or mounted control file Cause: A command was used which requires a connection to a recovery catalog database or the target database to be mounted. The command cannot be used when no backup repository is available. Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command. RMAN-06124: error while looking up datafile copy key: number Cause: An error occurred while looking up the specified datafile copy key in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. RMAN-06125: error while looking up archived log key: number Cause: An error occurred while looking up the specified archived log key in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. RMAN-06126: skipping offline file string Cause: The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified. Action: No action is required. RMAN-06127: skipping read-only file string Cause: The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified. Action: No action is required. RMAN-06128: skipping inaccessible file string Cause: The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified. Action: No action is required. RMAN-06129: invalid reserved channel ID: string Cause: The specified channel id is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users. Action: Specify a different channel ID. RMAN-06131: SKIP OFFLINE/READONLY only allowed with current control file Cause: The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database control file is current. When the target control file is not current, it is not possible to obtain a datafile's offline/read only status. Action: Remove the skip option or mount a current control file on the target database. RMAN-06132: cannot backup datafile string because it is not in the control file Cause: A backup command was issued that includes the specified datafile, but the datafile is not listed in the control file. The control file is not current (it is a backup or a created control file). Action: Recover the control file to make it current, then retry the backup command. RMAN-06133: recovery catalog may have obsolete data for datafile string Cause: A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the control file. Action: If the recovery catalog has correct data for the datafile, then restore a backup control file using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the control file. RMAN-06134: host command complete Cause: An operating system command has completed. Action: None - this is an informational message. RMAN-06135: error executing host command: string Cause: A host command returned a non-zero return code. Action: Correct the offending command. RMAN-06136: ORACLE error from auxiliary database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIME Cause: A 'REPORT SCHEMA at_clause' command was issued, but there is no recovery catalog database. Action: If you are not using a recovery catalog, then you may only issue the 'REPORT SCHEMA' command with no at_clause. RMAN-06138: control file not mounted - must specify AT clause with REPORT command Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database. Action: Use a recovery catalog or mount a control file at the target database. RMAN-06139: WARNING: control file is not current for REPORT SCHEMA Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current. Action: Use a recovery catalog or mount a current control file. RMAN-06140: cannot specify TAG option with LIST INCARNATION Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation. Action: Remove the TAG option and re-run the LIST command. RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE Cause: The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk. Action: Remove the ARCHIVELOG LIKE option and re-run the command. RMAN-06142: DEVICE TYPE cannot be specified with this command Cause: The DEVICE TYPE option was specified with a command that does not support it. Action: Remove the DEVICE TYPE option and re-run the command. RMAN-06143: LIKE may only be specified with COPY Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files or archived logs have file names that may be tested with a LIKE operand. Action: Remove the LIKE option and re-run the RMAN command. RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation. Action: Remove the FROM or UNTIL option and re-run the LIST command. RMAN-06145: control file is not current - obsolete file list may be incomplete Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS. Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current control file. RMAN-06146: changes found for file number beyond offline SCN Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the system change number(SCN) when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file. Action: Mount a current control file or a backup control file. RMAN-06147: no obsolete backups found Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness. Action: None - this is an informational message. RMAN-06148: redundancy count must be greater than zero Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero. Action: Specify a REDUNDANCY operand of 1 or greater. RMAN-06150: auxiliary name for datafile number set to: string Cause: This message is issued in response to a CONFIGURE AUXNAME command. Action: None - this is an informational message. RMAN-06151: datafile string creation SCN string Cause: This is an informational message. It should be accompanied by other messages. Action: None RMAN-06153: validation failed for datafile copy Cause: The CHANGE DATAFILECOPY VALIDATE command discovered that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog or target database control file. Action: None - this is an informational message. RMAN-06154: validation succeeded for datafile copy Cause: The CHANGE DATAFILECOPY VALIDATE command discovered that the datafile copy still matches its data in the recovery catalog or target database control file. Action: None - this is an informational message. RMAN-06155: validation failed for control file copy Cause: The CHANGE CONTROLFILECOPY VALIDATE command discovered that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog or target database control file. Action: None - this is an informational message. RMAN-06156: validation succeeded for control file copy Cause: The CHANGE CONTROLFILECOPY VALIDATE command discovered that the control file copy still matches its data in the recovery catalog or target database control file. Action: None - this is an informational message. RMAN-06157: validation failed for archived log Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired. Action: None - this is an informational message. RMAN-06158: validation succeeded for archived log Cause: The CROSSCHECK ARCHIVELOG command or VALIDATE HEADER option determined that the archived log still matches its data. Action: None - this is an informational message. RMAN-06159: error while looking up backup set Cause: An error occurred while looking up the specified backup set in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06160: no backup pieces found for backup set key: number Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file. Action: Specify an existing backup set. RMAN-06161: error when inspecting auxiliary file name: string Cause: This error is accompanied by other errors explaining the cause. Action: Correct the auxiliary file name if it is wrong via the CONFIGURE AUXNAME command. RMAN-06162: sql statement: string Cause: This is the sql statement about to be executed for a SQL command. Action: None, informational message only. RMAN-06163: some datafiles cannot be recovered, aborting the RECOVER command Cause: This message should be followed by one or more 6162 or 6164 messages. Action: Check the accompanying errors. RMAN-06164: WARNING: no channel of required type allocated to recover datafile number Cause: A RECOVER command could not proceed because incremental backup sets or archived log backup sets exist on a device type that has not been allocated. Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type. RMAN-06165: datafile string is too old to recover, restore a more recent copy Cause: The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered. Action: Issue a RESTORE for the datafile, then reissue the RECOVER command. RMAN-06166: datafile string cannot be recovered Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists. Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a Point-in-Time Recovery may be possible. RMAN-06167: already connected Cause: a CONNECT command was issued, but RMAN is already connected to the specified database. Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again. RMAN-06168: no backup pieces with this tag found: string Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found. Action: Make sure the tag is specified correctly. RMAN-06169: could not read file header for datafile string error reason string Cause: The specified datafile could not be accessed. The reason codes are: 1 - file name is MISSINGxx in the control file 2 - file is offline 3 - file is not verified 4 - DBWR could not find the file 5 - unable to open file 6 - I/O error during read 7 - file header is corrupt 8 - file is not a datafile 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - control file is not current Action: If the error can be corrected, do so and retry the operation. The SKIP option can be used to ignore this error during a backup. RMAN-06170: no control file copy found with offline range RECID string STAMP string datafile string Cause: This offline range is needed for recovering the specified data file, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status. Action: Query the RC_CONTROLFILE_COPY view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command. RMAN-06171: not connected to target database Cause: A command was issued but no connection to the target database has been established. Action: Issue a CONNECT TARGET command to connect to the target database. RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece Cause: A restore could not proceed because no AUTOBACKUP was found or specified handle is not a valid copy or backup piece. In case of restore from AUTOBACKUP, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user's restore operands. In case of restore from handle, it may be the handle is not a backup piece or control file copy. In may be that it does not exist. Action: Modify AUTOBACKUP search criteria or verify the handle. RMAN-06173: SET NEWNAME command has not been issued for datafile string when restore auxiliary Cause: Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile. Action: Issue SET NEWNAME command for every datafile in the recovery set. RMAN-06174: not connected to auxiliary database Cause: An auxiliary command was issued but no connection to a auxiliary database has been established. Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database. RMAN-06175: deleted script: string Cause: A DELETE SCRIPT command was executed. Action: None, informational message only. RMAN-06176: no recovery required; all files are read only or offline Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the SYSTEM tablespace. Action: None, informational message only RMAN-06177: restore not done; all files read only, offline, or already restored Cause: A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read-only, or are already restored to their correct destinations. Action: None, informational message only RMAN-06178: datafile number not processed because file is offline Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point-in-time. Action: None, informational message only RMAN-06179: datafile number not processed because file is read-only Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point-in-time. Action: None, informational message only RMAN-06180: incremental backups require Enterprise Edition Cause: A BACKUP command with INCREMENTAL LEVEL > 0 was specified. Action: Use FULL, or INCREMENTAL LEVEL 0. RMAN-06181: multiple channels require Enterprise Edition Cause: Attempt to allocate more than 1 channel in a job. Action: Remove all except one ALLOCATE CHANNEL command. RMAN-06182: archived log string of thread string with sequence string larger than MAXSETSIZE Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archived log is larger than MAXSETSIZE will allow. Action: Increase MAXSETSIZE limit. RMAN-06183: datafile or datafile copy string (file number string) larger than MAXSETSIZE Cause: A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow. Action: Increase MAXSETSIZE limit. RMAN-06184: duplicate object in backup specifier: string string Cause: A backup command specifies the same datafile or copy of a data file multiple times. Action: Eliminate the duplicates. RMAN-06185: Recovery Manager incompatible with string database: RMAN number.number.number.number to number.number.number.number required Cause: This version of recovery manager was incompatible with the indicated database or the DBMS_BACKUP_RESTORE package installed in the indicated 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. Otherwise, use a version of RMAN within the range specified in the error message. RMAN-06186: PL/SQL package string.string version string in string database is too old Cause: The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN). Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. RMAN-06187: control file copy string not found or out of sync with catalog Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database. Action: Re-catalog the file and retry the operation. RMAN-06188: cannot use command when connected to a mounted target database Cause: An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted. Action: Dismount the database or restart RMAN and use the command before connecting to the target database. RMAN-06189: current DBID number does not match target mounted database (number) Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected. Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN. RMAN-06190: PL/SQL package string.string version string in string database is not current Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode. Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb. RMAN-06191: PL/SQL package string.string version string in string database is too new Cause: RMAN detected an incompatible version of the specified package. Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager. RMAN-06192: maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb Cause: Input size for MAXPIECESIZE or MAXSETSIZE was out of range. Action: Specify a valid size and retry the command. RMAN-06193: connected to target database (not started) Cause: This is an informational message only. Action: The database must be started before any other RMAN commands are issued. RMAN-06194: target database instance not started Cause: A command was issued that requires the target database instance be started. Action: Issue a STARTUP command to start the instance. RMAN-06195: auxiliary database not started Cause: A command was issued that requires the auxiliary database instance be started. Action: Issue a STARTUP AUXILIARY command. RMAN-06196: Oracle instance started Cause: A STARTUP command completed successfully. Action: None, this is an informational message. RMAN-06197: Total System Global Area string bytes Cause: This is an informational message only. Action: No action is required. RMAN-06198: string string bytes Cause: This is an informational message only. Action: No action is required. RMAN-06199: database mounted Cause: This is an informational message only. Action: No action is required. RMAN-06200: Changed string objects to AVAILABLE status Cause: This is an informational message only. Action: No action is required. RMAN-06201: Deleted string objects Cause: This is an informational message only. Action: No action is required. RMAN-06202: Deleted string EXPIRED objects Cause: This is an informational message only. Action: No action is required. RMAN-06203: Changed KEEP options for string objects Cause: This is an informational message only. Action: No action is required. RMAN-06204: Changed string objects to UNAVAILABLE status Cause: This is an informational message only. Action: No action is required. RMAN-06205: Uncataloged string objects Cause: This is an informational message only. Action: No action is required. RMAN-06206: Crosschecked string objects Cause: This is an informational message only. Action: No action is required. RMAN-06207: WARNING: string objects could not be deleted for string channel(s) due Cause: This is an informational message only. Action: No action is required. RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status Cause: This is an informational message only. Action: No action is required. RMAN-06209: List of failed objects Cause: This is an informational message only. Action: No action is required. RMAN-06210: List of Mismatched objects Cause: This is an informational message only. Action: No action is required. RMAN-06211: ========================== Cause: This is an informational message only. Action: No action is required. RMAN-06212: Object Type Filename/Handle Cause: This is an informational message only. Action: No action is required. RMAN-06213: --------------- --------------------------------------------------- Cause: This is an informational message only. Action: No action is required. RMAN-06214: string string Cause: This is an informational message only. Action: No action is required. RMAN-06215: List of objects that must perform same operation at other database Cause: This is an informational message only. Action: The specified list of objects were not accessible at connected target database. Re-run the CROSSCHECK command after connecting to database that has DB_UNIQUE_NAME displayed in output for the specified object. RMAN-06216: WARNING: db_unique_name mismatch - string objects could not be updated Cause: This is an informational message only. Action: Run CROSSCHECK command after connecting to a primary or physical standby database that can access the specified objects. RMAN-06217: not connected to auxiliary database with a net service name Cause: A command that moves files from the target instance to the auxiliary instance was requested. Such a command requires a net service name be present in the connect string used to connect to the auxiliary instance. Action: Issue a CONNECT AUXILIARY command and include a net serice name in the connect string. That service name must be valid on the target instance. RMAN-06218: List of objects requiring same operation on database with db_unique_name string Cause: This is an informational message only. Action: The specified list of objects were not accessible by the target database. Re-run the same command after connecting to database that has DB_UNIQUE_NAME displayed in output for the specified object. RMAN-06219: List of objects not associated with all known db_unique_names Cause: This is an informational message only. Action: The specified list of objects were not accessible by the target database. Re-run the same command after connecting to primary database or physical standby database that can access the specified objects. RMAN-06220: Creating automatic instance, with SID='string' Cause: No connection to the auxiliary instance was provided, but the command requires an auxiliary instance. Action: No action is required unless you want to create a permanent database, in which case you should stop the command and re-run it, providing an auxiliary instance connection. RMAN-06221: Removing automatic instance Cause: RMAN is removing the automatic auxiliary instance that was created for this command. Action: No action is required. RMAN-06223: starting up automatic instance string Cause: This is an informational message only. Action: No action is required. RMAN-06224: Automatic instance created Cause: This is an informational message only. Action: No action is required. RMAN-06225: shutting down automatic instance string Cause: This is an informational message only. Action: No action is required. RMAN-06226: Automatic instance removed Cause: This is an informational message only. Action: No action is required. RMAN-06230: List of Stored Scripts in Recovery Catalog Cause: This message is issued in response to a LIST SCRIPT NAMES command. The following fields are shown for each script that is stored in the recovery catalog: Header indicating to what database the script belongs. Script Name: name of the script. Description: comment associated with this script. Action: No action is required. RMAN-06238: List of Databases Cause: This message is issued in response to a LIST DB_UNIQUE_NAME command. The following fields are shown for each database that is known to the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. DB_UNIQUE_NAME: db_unique_name value for the database. Action: No action is required. RMAN-06246: List of Database Incarnations Cause: This message is issued in response to a LIST INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: 'YES' if this is the current incarnation of this database, otherwise 'NO'. Reset SCN: system change number (SCN) of the most recent RESETLOGS operation. Reset Time: Time of the most recent RESETLOGS operation. Action: No action is required. RMAN-06250: Report of files that need backup due to unrecoverable operations Cause: An unlogged change (such as 'create table unrecoverable') has been made to this file, and the most recent backup of the file does not contain those changes. Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice. RMAN-06263: string string string Cause: This message is issued in response to the REPORT NEED BACKUP INCREMENTAL command, for those files which would use more than the specified number of incrementals during recovery. Action: To reduce the number of incremental backups which would be used during recovery of this datafile, take a new full backup of this file now. RMAN-06270: Report of files whose recovery needs more than number days of archived logs Cause: This message is issued in response to the REPORT NEED BACKUP DAYS command for those files which need more than the specified number of days' archived logs for recovery. Action: To reduce the number of log files needed for recovery of this datafile, take a new full or incremental backup now. RMAN-06274: Report of files that must be backed up to satisfy number days recovery window Cause: This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS command for those files that must be backed up to satisfy specified retention policy. Action: To satisfy specified recovery window for this datafile, take a new full or incremental backup now. RMAN-06275: invalid number of days specified for report : string days Cause: This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS or REPORT NEED BACKUP DAYS n command when an invalid number of days was specified in input command. Action: The number of days specified in REPORT command must be greater than zero. RMAN-06280: Report of obsolete backups and copies Cause: This message is issued in response to the REPORT OBSOLETE command. Each of the files listed is obsolete because it is more redundant than the level of redundancy specified in the REPORT command. Action: Depending on your needs, you might need to take new backups. RMAN-06290: Report of database schema for database with db_unique_name string Cause: This message is issued in response to the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each datafile and tempfile: File: The file number. Size(MB): The size of the file in mega bytes. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Datafile/Tempfile Name: The file name. Maxsize(MB): Maximum file size to which file can be extended Action: No action is required. RMAN-06300: Report of files with less than number redundant backups Cause: This message is issued when the REPORT NEED BACKUP REDUNDANCY command is used for those files which have less than the specified number of backups which can be used for recovery. Action: Take another backup of the datafiles listed. RMAN-06306: ==================== Cause: This message is issued in response to a LIST BACKUP DATABASE/TABLESPACE/DATAFILE command when some backups were taken with the PROXY option. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each proxy datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the control file. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status 'U' will not be used if the target database control file is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint system change number (SCN) of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup. Action: No action is required. RMAN-06378: List of Backup Sets Cause: This message is issued in response to a LIST BACKUP command. Action: No action is required. RMAN-06400: database opened Cause: This is an informational message only. Action: No action is required. RMAN-06401: database is already started Cause: A STARTUP command without the FORCE option was issued, but the target database is already started. Action: Use the FORCE option if you want to restart the database. RMAN-06402: Oracle instance shut down Cause: This is an informational message only. Action: No action is required. RMAN-06403: could not obtain a fully authorized session Cause: The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has has been shutdown. Other error messages should identify exactly which database is the problem. Action: Startup the database causing the problem. RMAN-06404: database dismounted Cause: This is an informational message only. Action: No action is required. RMAN-06405: database closed Cause: This is an informational message only. Action: No action is required. RMAN-06406: deleted archived log Cause: This is an informational message only. Action: No action is required. RMAN-06407: auxiliary instance file string deleted Cause: This is an informational message only. Action: No action is required. RMAN-06408: recovery catalog upgraded to version string Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog schema is not changed with each Oracle release. Action: No action is required. RMAN-06409: LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported Cause: LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported. Action: Remove LIKE clause from command. RMAN-06410: cannot use command when channels are allocated Cause: An attempt was made to issue a command that can be used only when there are no allocated channels. Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated. RMAN-06411: backup copies setting out of range (1-4): number Cause: An attempt was made to set backup copies to an invalid value. Action: Use a value in the specified range. RMAN-06412: no proxy copy channel found Cause: A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy. Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores. RMAN-06413: channel string does not support proxy copy Cause: The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy. Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores. RMAN-06414: target database COMPATIBLE option does not support proxy copy Cause: PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups. Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter. RMAN-06415: file string cannot be proxy backed up Cause: The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set. Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file. RMAN-06416: PROXY ONLY was specified and some files could not be proxy copied Cause: PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied. Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files. RMAN-06417: command not allowed when connected to a virtual private catalog Cause: The command that was entered cannot be used while connected to a virtual private catalog. Action: Connect to the base catalog and re-execute the command. RMAN-06418: proxy incremental backups with level > 0 not supported Cause: PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups. Action: Remove one of the conflicting options. RMAN-06419: file string cannot be proxy restored from handle string Cause: The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle. Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor. RMAN-06420: some files could not be proxy restored - aborting restore Cause: Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored. Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from them. RMAN-06421: sent command to channel: string Cause: This is an informational message only. Action: No action is required. RMAN-06422: no channels found for SEND command Cause: No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated. Action: Specify a different channel type or allocate a channel of the desired type. RMAN-06423: requested limit of number exceeds vendor limit of number Cause: A command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large. Action: Specify a smaller backup piece limit. RMAN-06424: error while looking up proxy copy Cause: An error occurred while looking up the specified proxy copy in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06425: <datafile pathname not available> Cause: This is an informational message only. Action: No action is required. RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to user string Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the USERID that was supplied in the CATALOG connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role. Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner. RMAN-06427: recovery catalog already exists Cause: The CREATE CATALOG command cannot be used when the recovery catalog already exists. Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog. RMAN-06428: recovery catalog is not installed Cause: A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed. Action: If you mis-typed the recovery catalog owner USERID, then correct the USERID and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner USERID, then use the CREATE CATALOG command to create the recovery catalog schema. Alternatively, exit RMAN and connect without specifying a recovery catalog connection. RMAN-06429: string database is not compatible with this version of RMAN Cause: The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error. Action: See the other messages. If the database is CATALOG, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable. RMAN-06430: recovery catalog USERID cannot be SYS Cause: A recovery catalog connection was made to USERID SYS. The recovery catalog must be created in a USERID other than SYS. Action: Specify a different USERID in the CATALOG connect string. RMAN-06431: recovery catalog created Cause: This is an informational message issued by the CREATE CATALOG command. Action: No action is required. RMAN-06432: recovery catalog dropped Cause: This is an informational message issued by the DROP CATALOG command. Action: No action is required. RMAN-06433: error installing recovery catalog Cause: An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server. Action: The most common reasons for failure to install the recovery catalog are: - Lack of space in the recovery catalog database: allocate more space, use the DROP CATALOG command to remove any partially installed recovery catalog, and retry the command. - Object already exists: This is caused by a partial recovery catalog installation. Use the DROP CATALOG command to remove the partially installed recovery catalog and retry the command. RMAN-06434: some errors occurred while removing recovery catalog Cause: Some errors were received from the recovery catalog database while removing the recovery catalog. Action: Correct the error(s) and retry the command. Note that Recovery Manager intercepts and ignores common errors, such as 'object not found', which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog. RMAN-06435: recovery catalog owner is string Cause: This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands. Action: No action is required. RMAN-06436: enter DROP CATALOG command again to confirm catalog removal Cause: The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do. Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again. RMAN-06437: cannot drop catalog - catalog is newer than this RMAN Cause: The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog. Action: Use the version of RMAN which most recently created or upgraded the recovery catalog. RMAN-06438: error executing package DBMS_RCVMAN in string database Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation. To re-create the package, run the files dbmsrman.sql and prvtrmns.plb. Action: re-create the DBMS_RCVMAN package in the SYS schema. RMAN-06439: RMAN must be upgraded to version string to work with this package Cause: This message indicates the minimum version of recovery manager required to use the package which was specified in message 6191. Action: A newer version of RMAN must be used with this package. RMAN-06440: virtual catalog dropped Cause: This is an informational message issued by the DROP CATALOG command, when connected to a virtual private catalog. Note that dropping a virtual private catalog does not delete any data, because the catalog data is owned by the base catalog. Action: No action is required. RMAN-06441: cannot upgrade catalog - catalog is already newer than this RMAN Cause: The recovery catalog is already at a version level that is greater than this version of the Recovery Manager. The UPGRADE CATALOG command is not needed. Action: Either upgrade to a more recent Recovery Manager, or continue to use the current version. Message 6191 will be issued if the recovery catalog is too new to work with this version of Recovery Manager. RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade Cause: The UPGRADE CATALOG command alters the recovery catalog schema. Although the recovery catalog is designed to be compatible with older versions of the Recovery Manager (RMAN), it is possible that an upgrade will remove support for older versions of RMAN. Action: If you really want to upgrade the recovery catalog, then enter the UPGRADE CATALOG command again. If you are not going to use an older version of RMAN with this recovery catalog, then compatibility is not an issue. If you plan to also continue using an older version of RMAN with this recovery catalog then, before upgrading, consult the Migration Guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN. RMAN-06443: error upgrading recovery catalog Cause: An error was received from the recovery catalog database while upgrading the recovery catalog. Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog. RMAN-06444: error creating string Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated object could not be created due to errors. Action: Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle support. If the error refers to one of the RMAN PL/SQL packages, connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors. RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option. Action: Re-start rman if you wish to use a recovery catalog. RMAN-06446: changed proxy copy unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06447: changed proxy copy available Cause: This is an informational message only. Action: No action is required. RMAN-06448: uncataloged proxy copy Cause: This is an informational message only. Action: No action is required. RMAN-06449: deleted proxy copy Cause: This is an informational message only. Action: No action is required. RMAN-06450: crosschecked proxy copy: found to be 'string' Cause: This is an informational message only. Action: No action is required. RMAN-06451: proxy copy handle=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-06452: string package upgraded to version string Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog packages are not changed with each Oracle release. Action: No action is required. RMAN-06453: RECOVERABLE may only be used with datafile objects Cause: An attempt was made to use LIST ... RECOVERABLE .. with OF CONTROLFILE or OF ARCHIVELOG. Action: Remove the RECOVERABLE keyword and try again. RMAN-06454: duplexed backups require Enterprise Edition Cause: The SET COPIES or CONFIGURE BACKUP COPIES command was used to create more than one copy of each backup piece, but Enterprise Edition is not installed. Action: Do not attempt to create more than one copy of each backup piece. RMAN-06455: Tablespace Point-in-Time Recovery requires Enterprise Edition Cause: Tablespace Point-in-Time Recovery was attempted, but Enterprise Edition is not installed. Action: Do not attempt Tablespace Point-in-Time Recovery. RMAN-06456: command is obsolete Cause: This is an informational message only. Action: No action is required. RMAN-06457: UNTIL SCN (string) is ahead of last SCN in archived logs (string) Cause: UNTIL SCN cannot be more than the last system change number (SCN) of the last archived log Action: Check the UNTIL SCN. RMAN-06458: AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST Cause: The RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST was specified with AS COPY. Action: Remove the AS COPY option and resubmit the command. RMAN-06459: BACKUP <VALIDATE|DURATION> is not supported with PROXY Cause: BACKUP <VALIDATE|DURATION> and PROXY were specified in the same backup command. Action: Remove the incompatible option. RMAN-06460: control file copy string cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message. RMAN-06461: current control file cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message. RMAN-06462: no backup sets found on device DISK that match specification Cause: A backup set record specifier did not match an backup set on device DISK in the recovery catalog. Action: Resubmit the command with a different backup set record specifier. The Recovery Manager (RMAN) LIST command can be used to display all backup sets that RMAN knows about. RMAN-06463: Backup set key string cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of backup set is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message. RMAN-06464: BACKUP BACKUPSET is not supported with VALIDATE option Cause: BACKUP BACKUPSET and VALIDATE were specified in the same backup command. Action: To VALIDATE BACKUPSET use 'validate' or 'restore validate' command. RMAN-06465: configuration not implemented: string Cause: The configuration is not implemented in the current release. Action: Avoid using the command. RMAN-06466: error parsing configuration string (string) Cause: Unsupported configuration string is stored in recovery catalog or target database control file. Action: Check compatibility matrix rman executable and target database and recover catalog. Use DBMS_BACKUP_RESTORE.DELETECONFIG to remove problematic configuration. RMAN-06467: could not translate DBA: number Cause: An error was received when calling DBMS_RCVMAN Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06468: Invalid Data Block Address: number Cause: The DBA specified doesn't belong to the mentioned tablespace Action: Check the DBA RMAN-06469: could not translate corruption list Cause: An error was received when calling DBMS_RCVMAN Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06470: DEVICE TYPE is supported only when automatic channels are used Cause: The DEVICE TYPE option was specified with a BACKUP, RESTORE, RECOVER, DUPLICATE, CHANGE, VALIDATE, CROSSCHECK, or DELETE EXPIRED command. This option is allowed only when automatically allocated channels are used. Action: Remove the DEVICE TYPE option and re-run the command. Or Remove all ALLOCATE commands and re-run the script so that channels are automatically allocated. RMAN-06471: no configuration found to allocate channels for string Cause: Device type configuration was not found in recovery catalog Action: Setup device type configuration using configure command for required device type RMAN-06472: channel id string is automatically allocated Cause: Channel id was used on ALLOCATE/RELEASE command. Action: Use other channel id that does not belong to reserved channel id's name space RMAN-06473: SET DATABASE can only be used in case of DUPLICATE without TARGET connection Cause: A SET DATABASE command was specified when connected to target database or not connected to an auxiliary instance. Action: Specify the command only when not connected to a target database and when connected to an auxiliary instance in preparation to DUPLICATE without TARGET connection. RMAN-06474: maintenance channels are not allocated Cause: RELEASE CHANNEL was used without allocating any maintenance channels. Action: Allocate maintenance channel before executing this command. RMAN-06475: parallelism setting out of range (1-254): number Cause: Parallelism for the device type in CONFIGURE PARALLELISM command is out of range Action: Enter value of parallelism that are within the allowed range. RMAN-06476: channel number out of range (1-254): number Cause: Channel number entered in CONFIGURE CHANNEL command is out of range. Action: Enter channel number within allowed range and retry the command. for this device and retry the command RMAN-06477: configuration value length exceeds 1024 Cause: CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes. Action: Reduce the length of CONFIGURE CHANNEL command options RMAN-06478: WARNING: datafile copy 'string' cannot be found on disk Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafile copy cannot be found on disk. Action: If the storage containing the datafile copy has been removed from the host, restore it and retry the command. If the datafile copy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile. RMAN-06479: WARNING: control file copy 'string' cannot be found on disk Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk. Action: If the storage containing the control file copy has been removed from the host, restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this control file. RMAN-06480: WARNING: archived log 'string' cannot be found on disk Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the archived log cannot be found on disk. Action: If the storage containing the archived log has been removed from the host, restore it and retry the command. If the archived log is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archived log. RMAN-06481: WARNING: backup piece 'string' cannot be found on the storage medium Cause: The CHANGE BACKUPPIECE AVAILABLE command was used, but the backup piece cannot be found on the storage medium. Action: If the storage containing the backup piece has been removed from the host, restore it and retry the command. If the backup piece is permanently gone, then issue the CHANGE BACKUPPIECE DELETE command for this backup piece. RMAN-06482: WARNING: proxy copy 'string' cannot be found on the storage medium Cause: The CHANGE PROXY AVAILABLE command was used, but the proxy copy cannot be found on disk. Action: If the storage containing the proxy copy has been removed from the host, restore it and retry the command. If the proxy copy is permanently gone, then issue the CHANGE PROXY DELETE command for this proxy copy. RMAN-06483: changed datafile copy expired Cause: This is an informational message only. Action: No action is required. RMAN-06484: changed control file copy expired Cause: This is an informational message only. Action: No action is required. RMAN-06485: changed archived log expired Cause: This is an informational message only. Action: No action is required. RMAN-06486: changed backup piece expired Cause: This is an informational message only. Action: No action is required. RMAN-06487: changed proxy copy expired Cause: This is an informational message only. Action: No action is required. RMAN-06488: restore from AUTOBACKUP does not allow any other modifiers Cause: A control file or SPFILE restore from AUTOBACKUP was attempted and other restore options were used. Action: Do not specify any other options for the control file AUTOBACKUP restore. RMAN-06489: no configuration found to allocate clone channel number for device type string Cause: Target channel configuration could not be used for clone channel as it contains CONNECT option. Action: Setup clone channel configuration using CONFIGURE CLONE command for required number and type of channels. RMAN-06490: WARNING: limit of AUTOBACKUPS for the day has been reached Cause: No more control file AUTOBACKUPS are possible in this day. Action: This is a warning message, no action is required. RMAN-06491: control file AUTOBACKUP format "string" contains more than one "string" format specifier Cause: A CONTROLFILE AUTOBACKUP FORMAT cannot have more than one reserved format specifier. Action: Specify only one reserved format specifier or use an alternative format. RMAN-06492: control file AUTOBACKUP format "string" must specify a "string" format specifier Cause: A reserved format specifier was not specified for the CONTROLFILE AUTOBACKUP FORMAT Action: Add a specifier to the CONTROLFILE AUTOBACKUP FORMAT RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from AUTOBACKUP, found: string Cause: For restoring a control file AUTOBACKUP only SET UNTIL TIME can be used. It is not possible to translate the others to a precise day. Action: Specify SET UNTIL TIME to indicate the day to start the restore of a control file AUTOBACKUP. RMAN-06494: string = string is out of range (string-string) Cause: The specified parameter for restoring a control file AUTOBACKUP is out of the valid range. Action: Change the parameter value to a valid number or do not specify it. RMAN-06495: must explicitly specify DBID with SET DBID command Cause: Restore of a control file AUTOBACKUP or ADVISE FAILURE was attempted when the database is not mounted. Action: Specify the DBID of the database using SET DBID or mount the database. RMAN-06496: must use the TO clause when the database is mounted or open Cause: A control file restore was attempted when the database is mounted or open and no alternate destination was specified. Action: Specify an alternate destination with the TO clause or dismount the database. RMAN-06497: WARNING: control file is not current, control file AUTOBACKUP skipped Cause: Control file AUTOBACKUP is not possible without a current control file. Action: This is a warning message, no action is required. RMAN-06498: skipping datafile string; already backed up string time(s) Cause: The indicated datafile will not be included in the backup set. It is already backed up on the device requested and file is offline/read-only datafile. Use the FORCE option to override backup optimization. Action: No action is required. RMAN-06499: skipping archived log file string; already backed up string time(s) Cause: The indicated log file will not be included in the backup set because it is already backed up on the device requested. Use FORCE option to override backup optimization. Action: No action is required. RMAN-06500: skipping backup set key string; already backed up string time(s) Cause: The indicated backup set will not be copied because it is already backed up on the device requested. Use FORCE option to override backup optimization. Action: No action is required. RMAN-06501: skipping datafile string; already backed up on string Cause: The indicated datafile will not be included in the backup set. It is already been backed up once, or before the since time specified. Action: No action is required. RMAN-06502: skipping archived log file string; already backed on string Cause: The indicated log file will not be included in the backup set. It is already been backed up once, or before the since time specified. Action: No action is required. RMAN-06503: skipping backup set key string; already backed up on string Cause: The indicated backup set will not be backed up. It has already been backed up on the device once, or before the since time specified. Action: No action is required. RMAN-06504: PROXY option with multiple backup copies is not supported Cause: Multiple backup copies and PROXY option were specified in BACKUP command. Action: Resolve the conflict. RMAN-06505: specified DATABASE: string does not match previous DATABASE: string Cause: SET DBID was used to set a DBID that translated into a database name that does not match newly specified database name or a previous SET DATABASE set a different database name. Action: Verify that the correct DBID was specified or avoid using the SET DATABASE command. RMAN-06506: the MAXSETSIZE option cannot be used with a backup backup set Cause: The MAXSETSIZE option was specified for a backup backup set command. Action: Remove the option and resubmit the command. RMAN-06507: trying alternate file for archived log of thread number with sequence number Cause: This is an informational message, appearing when an archived log was found out of sync with catalog database. Action: No action is required. RMAN-06508: MAXSETSIZE string KBYTES should be greater than block size string bytes Cause: MAXSETSIZE configured or specified in backup command should be greater than database block size. Action: Specify a larger MAXSETSIZE limit. RMAN-06509: only SPFILE or control file can be restored from AUTOBACKUP Cause: A datafile or archived log restore from AUTOBACKUP was attempted. Action: Do not specify DATAFILE or ARCHIVELOG for restore from AUTOBACKUP. RMAN-06510: RMAN retention policy is set to recovery window of number days Cause: This is an informational message only. Action: No action is required. RMAN-06511: RMAN retention policy is set to redundancy number Cause: This is an informational message only. Action: No action is required. RMAN-06512: copy will be obsolete on date string Cause: This is an informational message only. Action: No action is required. RMAN-06513: copy will never be obsolete Cause: This is an informational message only. Action: No action is required. RMAN-06514: archived logs required to recover from this copy will not be kept Cause: This is an informational message only. Action: No action is required. RMAN-06515: archived logs required to recover from this copy will expire when this copy expires Cause: This is an informational message only. Action: No action is required. RMAN-06516: time specified in KEEP UNTIL clause must be be after today Cause: KEEP UNTIL support only a future time. Action: Correct the time and retry the command. RMAN-06517: KEEP option is not supported for archived log backups Cause: The KEEP option is not supported for archived logs. Action: Either remove KEEP option and retry the command or don't specify archived logs for this backup. RMAN-06518: backup will be obsolete on date string Cause: This is an informational message only. Action: No action is required. RMAN-06519: backup will never be obsolete Cause: This is an informational message only. Action: No action is required. RMAN-06520: archived logs will not be kept or backed up Cause: This is an informational message only. Action: No action is required. RMAN-06521: archived logs required to recover from this backup will expire when this backup expires Cause: This is an informational message only. Action: No action is required. RMAN-06522: KEEP FOREVER option is not supported without the recovery catalog Cause: The KEEP FOREVER option was used, but it requires a connection to a recovery catalog database. The KEEP FOREVER option cannot be used when the backup repository is the target database control file. This is because information about this backup cannot be permanently stored. (If information is stored just in the control file it will be aged out depending on CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.) Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise use a different KEEP option. 6523, 1, "unused" RMAN-06524: RMAN retention policy will be applied to the command Cause: This is an informational message only. Action: No action is required. RMAN-06525: RMAN retention policy is set to none Cause: Command DELETE OBSOLETE and REPORT OBSOLETE requires that either: * RMAN retention policy is not NONE or, * RMAN retention policy is specified with REPORT/DELETE command. Action: Either configure RMAN retention policy with CONFIGURE command or specify it at the end of DELETE/REPORT command. RMAN-06526: KEEP option cannot be used with incremental backup Cause: The KEEP option was specified for a incremental backup. Action: Remove the option and resubmit the command. RMAN-06527: KEEP option is not supported for backup of backup sets Cause: The KEEP option is not supported for backup of backup sets. Action: Either remove KEEP option and retry the command or don't specify backup sets for this backup. RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECE Cause: The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces. Action: Use CHANGE BACKUPSET ... KEEP instead. RMAN-06529: CHANGE ... KEEP not supported for ARCHIVELOG Cause: The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archived logs. Action: Use CHANGE BACKUPSET ... KEEP instead. RMAN-06530: CHANGE ... KEEP LOGS not supported for backup set which contains archived logs Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contains archived logs. Backup sets with archived logs cannot have KEEP attributes. Action: Do not specify backup set with archived logs for the CHANGE BACKUPSET ... KEEP command. RMAN-06531: CHANGE ... KEEP not supported for incremental BACKUPSET Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET is an incremental backup set. Incremental backup sets cannot have KEEP attributes. Action: Do not specify a backup set with archived logs for the CHANGE BACKUPSET ... KEEP command. RMAN-06532: redundancy count must be greater than zero Cause: The REDUNDANCY operand specified for the retention policy was zero. Action: Specify a REDUNDANCY operand of 1 or greater. RMAN-06533: KEEP ... NOLOGS option cannot be used when datafiles are fuzzy Cause: The KEEP ... NOLOGS option was specified for a backup or copy of files in a fuzzy state. This kind of backup requires archived logs for recovery, so archived logs must be kept. Action: Remove the KEEP ... NOLOGS option or make sure the files are not in a fuzzy state and resubmit the command. RMAN-06534: archived logs required to recover from this backup will be backed up Cause: This is an informational message only. An archivelog backup will be created and kept so the specified backup can be recovered to a consistent state. Action: No action is required. RMAN-06535: LIST COPY OF SPFILE is not supported Cause: LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy. Action: Remove SPFILE from the command. RMAN-06536: BACKED UP ... TIMES option is supported only for archived logs Cause: The BACKUP UP ... TIMES option was used as a qualifier. This option is supported only for archived logs. Action: Remove the option and resubmit the command. RMAN-06537: CHANGE ... KEEP not supported for BACKUP Cause: The CHANGE BACKUP... KEEP command was entered. KEEP attributes cannot be specified for copies and backup pieces in a single command. Action: Use CHANGE BACKUPSET ... KEEP instead. RMAN-06538: The expected DB_UNIQUE_NAME is string, but found string Cause: The is an informational message. Action: Check other error messages associated with this message. RMAN-06540: Tablespace string will be excluded from future whole database backups Cause: This is an informational message only. Action: No action is required. RMAN-06541: Tablespace string will be included in future whole database backups Cause: This is an informational message only. Action: No action is required. RMAN-06542: file string is excluded from whole database backup Cause: The indicated file will not be included in the backup set because its tablespace is configured as excluded from backup. Action: No action is required. RMAN-06543: duplicate or conflicting LIST options: string and string Cause: The indicated options conflict with each other or appear more than once in a LIST command. Action: remove the duplicate/conflicting option from the command. RMAN-06547: SYSTEM tablespace cannot be excluded from whole database backup Cause: The SYSTEM tablespace must be included in whole database backup. Action: Remove the SYSTEM tablespace from the CONFIGURE ... EXCLUDE and retry the operation. RMAN-06548: connected to auxiliary database: string (DBID=string) Cause: This is an informational message only. Action: No action is required. RMAN-06549: connected to auxiliary database: string (not mounted) Cause: This is an informational message only. Action: No action is required. RMAN-06550: clone database not mounted and db_name not set in init.ora Cause: The clone database "init.ora" file does not specify the DB_NAME parameter. Action: Add the DB_NAME parameter to the clone database "init.ora" and restart the instance. RMAN-06551: error while looking up datafile copy for file number: string Cause: An error occurred while looking up the specified datafile copy in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. If the datafile copy was created during a RESTORE with a new name, ensure that the RESTORE completed successfully. RMAN-06552: newname for datafile number was set to NEW, but file was not restored Cause: A SWITCH command was specified for a datafile, but the newname was set to NEW and the file was not restored. If newname is set to NEW, the file must be restored before issuing a SWITCH command. Action: Correct and resubmit the SWITCH command. RMAN-06553: DB_CREATE_FILE_DEST must be set for SET NEWNAME ... TO NEW Cause: The SET NEWNAME ... TO NEW option was specified but the OMF destination init parameter DB_CREATE_FILE_DEST is not set. Action: Supply a full name to the SET NEWNAME command or set DB_CREATE_FILE_DEST at the target database. RMAN-06554: WARNING: file string is in backup mode Cause: A file which is being backed up or copied is in backup mode. RMAN will back up the file anyway, but files do not need to be put into backup mode before backing them up with RMAN. Action: Use the ALTER TABLESPACE ... END BACKUP statement, at the target database server, to take the files out of backup mode. RMAN-06555: datafile string must be restored from backup created before string Cause: An incomplete recovery session was started, but the file is in newer than the UNTIL TIME clause. Action: Check the UNTIL TIME clause or restore the file from a sufficient old backup. RMAN-06556: datafile string must be restored from backup older than SCN string Cause: An incomplete recovery session was started, but the file is newer than the UNTIL clause. Action: Check the UNTIL clause or restore the file from a sufficient old backup. RMAN-06557: unable to restore archived log of thread number with sequence number Cause: Restore of the specified archived log failed because the size of the archived log is larger than available disk space. Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area. RMAN-06558: archived log size of number kb is bigger than available space of number kb Cause: This message should be followed by one or more 6557 messages. Action: Check the accompanying errors. RMAN-06559: MAXSIZE must be larger than 1 kb Cause: The MAXSIZE parameter is out of range. Action: Specify a valid size and retry the command. RMAN-06560: WARNING: backup set with key number will be read number times Cause: This message should be followed by one or more 6562 messages. Action: Check the accompanying messages. RMAN-06561: available space must be larger than number kb Cause: The recovery failed because it requires more disk space. One of the following could have caused this error: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to recovery area, but available disk space is not large enough to restore files. Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area. RMAN-06562: available space of number kb needed to avoid reading the backup set multiple times Cause: A backup set is read more than once. Multiple reads of a backup set can slow restore performance. One of the following could have caused this: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to a recovery area, but the available disk space is not large enough to restore files. Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area. RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP Cause: RESTORE CONTROLFILE or RESTORE SPFILE was specified without the FROM AUTOBACKUP option when RMAN is not connected to the recovery catalog. Action: If the recovery catalog is available, connect to the recovery catalog and retry the restore. If the recovery catalog in not available, following is the procedure to restore control file or SPFILE: 1. Specify the DBID of the database with the SET DBID command. 2. If the AUTOBACKUP was created with non-default AUTOBACKUP format, then specify the AUTOBACKUP format using the SET CONTROLFILE AUTOBACKUP FORMAT command. 3. If the backup was created with SBT device, then allocate an SBT channel using the ALLOCATE CHANNEL command. 4. Restore control file or SPFILE by starting the RESTORE ... FROM AUTOBACKUP command. RMAN-06564: must use the TO clause when the instance is started with SPFILE Cause: A restore of the SPFILE from AUTOBACKUP was attempted when the instance is started with SPFILE and no alternate destination was specified. Action: Specify an alternate destination with the TO clause. RMAN-06565: WARNING: string: sqlcode number was caught, automatic retry #number Cause: The RMAN client caught a transient error and will automatically retry several times. Action: No action required, this is an informational message. RMAN-06566: target database incarnation not found in control file Cause: RESETLOGS CHANGE# and/or time of the target database doesn't match any database incarnation in the control file. Action: One of the following actions can be taken to resolve this error 1) Restore the control file from the incarnation. 2) To populate the new incarnation, inspect or restore an archived log/datafile/datafile copy/backup set from the target incarnation RMAN-06567: connected to auxiliary database: string (DBID=string, not open) Cause: This is an informational message only. Action: No action is required. RMAN-06568: connected to target database: string (DBID=string, not open) Cause: This is an informational message only. Action: No action is required. RMAN-06569: DATABASE: string does not match previous DATABASE: string Cause: SET DBID or SET DATABASE was used to specify the target database name which does not match specified database name in DUPLICATE command. Action: Verify that the correct DBID or the correct DATABASE was specified or avoid specifying DATABASE in DUPLICATE command. RMAN-06570: datafile number switched to datafile copy "string" Cause: This message was issued in response to a SWITCH command. Action: No action is required, this is an informational message. RMAN-06571: datafile number does not have recoverable copy Cause: The SWITCH command with the option TO COPY was specified but the datafile has no valid copy to switch to. Action: Verify whether the datafile has a valid datafile copy. RMAN-06572: database is open and datafile number is not offline Cause: The SWITCH command with the option TO COPY was specified, but datafile is not offline and database is open. Action: Either make sure the datafile is offline or the database must be mounted but not opened. RMAN-06573: specified DBID: string does not match previous DBID: string Cause: The DBID in the DUPLICATE command did not match the previously specified DBID in the SET DBID command. Action: Verify that the correct DBID was specified or avoid using DBID in the DUPLICATE command. RMAN-06575: platform id number found in datafile string header is not a valid platform id Cause: The platform id found in the datafile header was not recognized. Action: Verify that this is a valid datafile. RMAN-06576: platform 'string' (number) found in header of datafile string does not match specified platform name 'string' (number) Cause: The platform specified in the command did not match the platform found in the datafile header. Action: Specify the correct platform name and retry the command. RMAN-06577: FROM TAG option may only be used with datafile copies Cause: The FROM TAG option was specified for datafiles. Action: Remove the option and resubmit the command. RMAN-06578: INCREMENTAL LEVEL > 0 must be specified with FOR RECOVER OF Cause: The FOR RECOVER OF option was specified without specifying INCREMENTAL LEVEL > 0. Action: Specify INCREMENTAL LEVEL > 0 and resubmit the command. RMAN-06580: the string option cannot be used with AS COPY Cause: The specified option was specified for a backup as copy command. Action: Remove the option and resubmit the command. RMAN-06581: option string not supported Cause: This option was specified and it is not supported. Action: Remove the specified option. RMAN-06582: AS COPY option cannot be used when backing up backup sets Cause: The backup set was specified with AS COPY. Action: Remove the AS COPY option or remove the backup sets. RMAN-06583: at least 1 channel of TYPE DISK must be allocated to use AS COPY option Cause: No channel of TYPE DISK was allocated. Action: Allocate a channel of TYPE DISK and re-issue the command or remove AS COPY. RMAN-06584: WARNING: AS BACKUPSET option added due to allocation of multiple channel types Cause: DISK and non DISK channels were allocated for a backup command. Configuration indicates to produce image copies to DISK, however due to the mixed channel types BACKUPSETS will be created on DISK. Action: Do not allocate non DISK channels to produce image copies to DISK or allocate only non DISK channels to produce BACKUPSETS only. RMAN-06585: no copy of datafile number found Cause: An available datafile copy for the specified datafile could not be found. Action: make sure that all specified datafiles have a copy available. RMAN-06586: no copy of datafile number with tag string found Cause: An available datafile copy for the specified datafile could not be found. Action: make sure that all specified datafiles have a copy available. RMAN-06587: one or more datafile copies were not found Cause: This error message was accompanied by an additional error message or messages indicating the cause of the error. Action: Follow the recommended actions of the additional error message or messages. RMAN-06588: number of patterns (number) to DB_FILE_NAME_CONVERT should be even Cause: An uneven number of patterns was specified. Action: Specify one more or one less pattern. RMAN-06589: cannot specify DB_FILE_NAME_CONVERT option without AS COPY Cause: The DB_FILE_NAME_CONVERT option was specified without AS COPY. This is not permitted for backup set backups where multiple files are combined into a set. Action: Remove the DB_FILE_NAME_CONVERT option and re-run the BACKUP command. RMAN-06590: Tablespace string cannot be converted Cause: The system tablespaces could not be transported to other platforms. Action: Remove the specified tablespace from the CONVERT command and retry the operation. RMAN-06593: platform name 'string' specified in FROM PLATFORM is not valid Cause: The platform name was not recognized. Action: Specify a valid platform name. RMAN-06594: platform name 'string' specified in TO PLATFORM is not valid Cause: The platform name was not recognized. Action: Specify a valid platform name. RMAN-06595: platform name 'string' does not match database platform name 'string' Cause: The platform name specified did not match the name of the database performing the conversion. Action: Specify the correct platform name. RMAN-06596: string requires target database compatibility string, currently set to string Cause: A command or option was used that requires a higher database compatibility than is currently set at the target database. Action: Raise the compatibility of the database before attempting the command again. RMAN-06597: conversion between platforms 'string' and 'string' is not implemented Cause: Conversion of Oracle datafiles between the specified platforms was not supported. Action: Do not do the conversion. RMAN-06599: Tablespace string is not read-only Cause: A conversion was attempted on a tablespace which is not read-only. Action: Change the tablespace to read-only and retry the operation. RMAN-06600: old RMAN configuration parameters: Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06601: new RMAN configuration parameters: Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06602: TO DESTINATION option can be used only for disk device Cause: The TO DESTINATION option was specified for non-disk device. Action: Remove the TO DESTINATION option and resubmit the command. RMAN-06603: TO DESTINATION option must be specified with RECOVERY AREA, RECOVERY FILES or DB_RECOVERY_FILE_DEST on disk device Cause: RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command on disk device without specifying TO DESTINATION option. Action: Specify TO DESTINATION option and retry the command. RMAN-06604: new RMAN configuration parameters are successfully stored Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06605: old RMAN configuration parameters are successfully deleted Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06606: RMAN configuration parameters are successfully reset to default value Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06607: RMAN configuration parameters for database with db_unique_name string are: Cause: This message is issued in response to a SHOW command. Action: No action is required, this is an informational message only. RMAN-06608: RMAN configuration has no stored or default parameters Cause: This message is issued in response to a SHOW command. Action: No action is required, this is an informational message only. RMAN-06609: AS COPY can be configured only for disk device Cause: The AS COPY option was specified for non-disk device. Action: Remove the AS COPY option and resubmit the command. RMAN-06610: For record type string RECIDS from number to number are re-used before resync Cause: This messages is issued when the control file records were re-used before resyncing to catalog database. Action: Increase control_file_keep_record_time setting or issue BACKUP command that it will generate fewer control file records, e.g., backup few tablespaces instead of the complete database in one BACKUP command. RMAN-06611: Following RMAN configuration applied before deleting logs: Cause: This message is issued in response to a DELETE command. Action: No action is required, this is an informational message only. RMAN-06612: Incompatible options were specified for archivelog deletion policy Cause: Incompabitle options were specified on CONFIGURE ARCHIVELOG DELETION POLICY command. Action: Remove incompabitle options and retry the command. BACKED UP option can be used individually or combined with SHIPPED or APPLIED option. Following are invalid combination of options: a) TO NONE cannot be used with other options b) SHIPPED ON STANDBY and SHIPPED ON ALL STANDBY cannot be used together. c) APPLIED ON STANDBY and APPLIED ON ALL STANDBY cannot be used together. d) SHIPPED and APPLIED cannot be used together. RMAN-06613: Connect identifier for DB_UNIQUE_NAME string not configured Cause: The connect identifier for the specified DB_UNIQUE_NAME initialization parameter was not configured. Action: Do one of the following: - If the DB_UNIQUE_NAME belongs to a connected target database, then define the DB_UNIQUE_NAME parameter in LOG_ARCHIVE_DEST_n at the remote database from where the resynchronization is performed. Otherwise, define DB_UNIQUE_NAME parameter in LOG_ARCHIVE_DEST_n at the target database. Or, - Configure the appropriate connect identifier using the CONFIGURE DB_UNIQUE_NAME RMAN command and rerun the command. RMAN-06614: DB_UNIQUE_NAME string is too long Cause: The DB_UNIQUE_NAME initialization parameter string was too long. Action: Configure the appropriate DB_UNIQUE_NAME initialization parameter string and re-run the command. RMAN-06615: resyncing from database with DB_UNIQUE_NAME string Cause: Resync was performed remotely for the specified DB_UNIQUE_NAME initialization parameter without connecting to it as target database. This type of remote resync has limitations. For example, RMAN output cannot be resynced. Please refer to RMAN documentation for a complete set of limitations. Action: This is an informational message. RMAN-06616: RMAN output not resynced for database with DB_UNIQUE_NAME string Cause: V$RMAN_OUTPUT contents were not rescyned when the RESYNC CATALOG FROM DB_UNIQUE_NAME command was executed." Action: This is an informational message. RMAN-06617: UNTIL TIME (string) is ahead of last NEXT TIME in archived logs (string) Cause: UNTIL TIME was more than the last NEXT TIME of the last archived log. Action: Check the UNTIL SCN. RMAN-06700: error parsing text script in file string Cause: Incorrect syntax or invalid commands were found. Action: Fix text script and retry the command. RMAN-06701: could not construct path for file: "string" Cause: An error was encountered when trying to construct the full pathname for the specified file. Action: Ensure that the path is correct. RMAN-06702: could not initialize for input file: "string" Cause: An error was encountered when trying to initialize the specified file for input. Action: Ensure that the file exists. RMAN-06703: could not open file: "string" (reason=string) Cause: An error was encountered when trying to open the specified file. Action: Ensure that the file has correct permissions. RMAN-06705: text script line is too long (>1024) Cause: A text script contained a line longer than the permitted maximum length. Action: Split the line in smaller lines an retry the operation. RMAN-06706: could not close file: "string" (reason=string) Cause: An error was encountered when trying to close the specified file. Action: Ensure that the file has correct permissions and still exists. RMAN-06707: could not initialize for output file: "string" Cause: An error was encountered when trying to initialize the specified file for output. Action: Ensure that the file exists. RMAN-06708: short write while writing file "string". Wrote string bytes instead of string bytes Cause: An attempt was made to write to a file system that was full. Action: Ensure that the file system has room for the file. Check system logs. RMAN-06709: No scripts in recovery catalog Cause: An attempt was made to list the scripts in the catalog, but no scripts could be found in the specified recovery catalog. Action: No action required, this is an informational message only. RMAN-06710: script string not found in catalog Cause: An attempt was made to call a script that could not be found in the target database or as a global script in the specified catalog. Action: Verify the script name and retry the command. RMAN-06711: global scripts require a TARGET connection Cause: Connection to a TARGET database was not specified. Action: Provide a TARGET connection and retry the command. RMAN-06716: skipping datafile number; already restored to file string Cause: Recovery Manager determined that this file is already restored. Use FORCE option to override this optimization. Action: No action required, this is an informational message only. RMAN-06717: Could not delete auxiliary instance file string Cause: Auxiliary instance file was not deleted. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06724: backup not done; all files already backed up Cause: A BACKUP command does not need to backup any files, because all of the files to backup are already backed up. Action: No action required, this is an informational message only. RMAN-06725: database not open: sort area size too small Cause: sort area size too small to execute RMAN commands. Action: open the database or increase sort_area_size. RMAN-06726: could not locate archived log string Cause: The specified archived log could not be found on any allocated channel. Action: Allocate additional channels on other nodes of the cluster or, if the archived logs has been deleted, use the CROSSCHECK ARCHIVELOG command to correct the recovery catalog or target database control file entries. RMAN-06727: could not locate datafile copy string Cause: The specified datafile copy could not be found on any allocated channel. Action: Allocate additional channels on other nodes of the cluster or if the datafile copy has been deleted, use the CROSSCHECK DATAFILECOPY command to correct the recovery catalog or target database control file entries. RMAN-06728: could not locate control file copy string Cause: The specified control file copy could not be found on any allocated channel. Action: Allocate additional channels on other nodes of the cluster or if the control file copy has been deleted, use the CROSSCHECK CONTROLFILECOPY command to correct the recovery catalog or target database control file entries. RMAN-06729: no backup of the SPFILE found to restore Cause: A SPFILE restore could not proceed because no backup of the SPFILE was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: Modify options for the SPFILE restore. RMAN-06730: no channel to restore a backup of the SPFILE Cause: A SPFILE restore could not proceed because the backup on a device type that was not allocated for restore. Action: No action required, this is an informational message only. See message 6026 for further details. RMAN-06731: command string:string% complete, time left number:number:number Cause: This is an informational message only. Action: No action is required. RMAN-06732: database dropped Cause: This is an informational message only. Action: No action is required. RMAN-06733: database unregistered from the recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-06737: database name "string" does not match target database name "string" Cause: The UNREGISTER DATABASE command was used with a database name that does not match the name of the database to which RMAN is connected. Action: Specify the correct database name or avoid specifying the database name when connected to the target database. RMAN-06738: database name "string" is not unique in the recovery catalog Cause: The UNREGISTER DATABASE command was used with a database name that is ambiguous. Action: Use the SET DBID command to specify the database id and resolve the ambiguity. RMAN-06739: database "string" is not found in the recovery catalog Cause: The UNREGISTER DATABASE command was used with a database name that was not found in the recovery catalog. Action: Make sure the database name specified in the DROP DATABASE command syntax is correct. RMAN-06740: database name is not specified Cause: The command failed because of the following: o RMAN is not connected to the target database o The database name is not specified in the command o DBID is not set with the SET DBID command Action: Any one of the following actions will fix the problem: o Connect to the target database o Specify database name o Set DBID with SET DBID command RMAN-06741: database name is "string" and DBID is string Cause: This is an informational message only. Action: No action is required. RMAN-06742: platform name 'string' longer than number Cause: The specified platform name exceeds the maximum allowable platform name. Action: Correct the platform name. RMAN-06743: specification does not match any backup set in the repository Cause: The specified backup sets were not found in the recovery catalog or target database control file. Action: Verify backup set existence and retry the command. RMAN-06744: specification does not match any datafile copy in the repository Cause: The specified datafile copies were not found in the recovery catalog or target database control file. Action: Verify datafile copy existence and retry the command. RMAN-06745: skipping datafile copy string; already backed up string time(s) Cause: The indicated datafile copy was not included in the backup set because it was already backed up on the device requested. Action: Use FORCE option to override backup optimization. RMAN-06746: backup cancelled because there are no files to backup Cause: There were no files or all files were skipped for this backup set, therefore no backup set was created. Action: This message is informational only. RMAN-06747: at least 1 channel of tertiary storage must be allocated to execute this command Cause: The executed command requires a SBT channel, but no channels of type SBT were configured or allocated. Action: ALLOCATE or CONFIGURE a SBT channel. RMAN-06748: more than one channel types were allocated Cause: RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command, but more than one channel types was used and no DEVICE TYPE or CHANNEL option was specified. Action: Specify CHANNEL or DEVICE TYPE option and retry the command. RMAN-06749: restore point string does not exist. Cause: The specified restore point does not exists in v$restore_point table of the target database. Action: Check the name of restore point and retry the command. RMAN-06750: SPFILE cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of SPFILE is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message only. RMAN-06751: ASM file string cannot be proxy backed up. Cause: The PROXY option was specified, but proxy copy of ASM file is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message only. RMAN-06752: error while looking up tempfile: string Cause: An error occurred while looking up the specified tempfile in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure; see those error messages for further information. One possible problem is that the tempfile name was not entered correctly. RMAN-06753: tempfile not found in the repository Cause: The specified tempfile is not found in the control file or recovery catalog. Action: Make sure that the tempfile name is correct and retry RMAN-06754: INCREMENTAL FROM SCN option is not supported with [string] Cause: The INCREMENTAL FROM SCN option was supplied but does not apply to this type of backup. Action: Remove the INCREMENTAL FROM SCN operand and re-enter the command. RMAN-06755: WARNING: datafile string: incremental-start SCN is too recent; using checkpoint SCN string instead Cause: The incremental-start sysetm change number (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 system change number (SCN). RMAN-06756: cannot flashback database to non-guaranteed restore point string when flashback is off Cause: The indicated restore point was not guaranteed and flashback was disabled. When flashback is disabled, Oracle can flashback only to guaranteed restore point. Action: Specify a guaranteed restore point or turn on flashback and retry the command. the command. RMAN-06757: DB_UNIQUE_NAME "string" does not match target database ("string") Cause: The value specified in the FOR DB_UNIQUE_NAME option did not match the DB_UNIQUE_NAME parameter setting of the target database. Action: Use the RMAN STARTUP command, with no parameter file option, to start the target database without a parameter file, then run the RESTORE SPFILE command again. RMAN-06758: DB_UNIQUE_NAME is not unique in the recovery catalog Cause: RMAN could not identify which SPFILE to restore for this target database, because the recovery catalog contained two or more different instances of this database, each with different DB_UNIQUE_NAME values. Action: Use the FOR DB_UNIQUE_NAME option to specify the name of the instance whose parameter file you want to restore. RMAN-06759: skipping datafile copies that are already backed up Cause: Some datafile copies were not be backed up because they were already backed up on the device requested. Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up. RMAN-06760: skipping archived logs that are already backed up Cause: Some archived logs were not be backed up because they were already backed up on the device requested. Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up. RMAN-06761: skipping backup sets that are already backed up Cause: Some backup sets were not be backed up because they were already backed up on the device requested. Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up. RMAN-06762: ignoring encryption for proxy or image copies Cause: This information message is displayed when the RMAN client is generating proxy or image copies and encryption was enabled for the input files. Action: This is an informational message only. RMAN-06763: specified encryption algorithm not supported Cause: An encryption algorithm not supported by the database is specified during backup. Action: Refer to contents of v$rman_encryption_algorithms view for the list of supported encryption algorithm. Specify a valid encryption algorithm and retry the command. RMAN-06764: string Cause: An error occurred when processing user request. Action: None RMAN-06765: Tablespace string will be encrypted in future backup sets Cause: This is an informational message only. Action: No action is required. RMAN-06766: Tablespace string will not be encrypted in future backup sets Cause: This is an informational message only. Action: No action is required. RMAN-06767: Tablespace string will default to database encryption configuration Cause: This is an informational message only. Action: No action is required. RMAN-06768: duplicate or conflicting options are specified: string and string Cause: An error occurred when processing the command because user specified two duplicate options or the two options are not allowed to be used together. Action: Remove one of the above options and retry the command. RMAN-06769: length of password must be greater than zero Cause: Zero length password was specified for encrypted backups. Action: Retry the command using a password with non-zero length. RMAN-06770: backup encryption requires Enterprise Edition Cause: The backup command tried to create encrypted backups, but Enterprise Edition is not installed. Action: Do not create encrypted backups. RMAN-06771: cannot do IMPORT CATALOG after NOCATALOG has been used Cause: The IMPORT CATALOG command was used after the NOCATALOG option was already specified. Action: Restart RMAN and connect to recovery catalog if you wish to IMPORT CATALOG. RMAN-06772: cannot do IMPORT CATALOG before connecting to recovery catalog Cause: The IMPORT CATALOG command was used before connecting to the recovery catalog. Action: Connect to recovery catalog using CONNECT CATALOG command if you wish to IMPORT CATALOG. RMAN-06773: connected to source recovery catalog database Cause: This is an informational message only. Action: No action is required. RMAN-06774: must specify a TNS service name for source recovery catalog database Cause: The connect string does not contain TNS service name. IMPORT CATALOG without TNS service name is not supported. Action: Specify a service name and resubmit the command. RMAN-06775: not connected to source recovery catalog database Cause: IMPORT CATALOG command was issued but no connection to the source recovery catalog database has been established. Action: Resubmit IMPORT CATALOG command with correct connect string. RMAN-06776: source recovery catalog database not started Cause: IMPORT CATALOG command was issued which requires the source recovery catalog to be open. Action: Open the source recovery catalog database and re-submit the command. RMAN-06777: ORACLE error from source recovery catalog database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06778: WARNING: string: sqlcode number was caught, automatic retry #string Cause: The RMAN client caught a transient error during temporary resource allocate for IMPORT CATALOG command and will automatically retry several times. Action: No action required, this is an informational message. RMAN-06779: import validation complete Cause: This is an informational message only. Action: No action required. RMAN-06780: database unregistered from the source recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-06781: string package version string in source database is not of version string Cause: The catalog schema version of the source recovery catalog is not the same as the target recovery catalog. The two catalog Action: UPGRADE source recovery catalog schema and recovery catalog schema to same version and retry the command. RMAN-06782: Datafile headers of locally managed datafiles need to be updated. Cause: This is an informational message only. Action: No action is required. RMAN-06783: Update of datafile headers of locally managed datafiles finished. Cause: This is an informational message only. Action: No action is required. RMAN-06784: One or more datafile headers of locally managed datafiles were not updated. Cause: Errors prevented the update of one or more datafile headers. Action: See trace file for details of the problem. RMAN-06785: This operation might take some time. Cause: This is an informational message only. Action: No action is required. RMAN-06786: could not read file header for datafile string to do FLASHBACK. Cause: The indicated datafile header could not be read to do FLASHBACK DATABASE. Action: If the database must be taken back in time then a restore and incomplete recovery must be performed. RMAN-06787: WARNING: TAG string option is ignored; backups will be tagged with string Cause: WITH TAG option and TAG option were used together. When WITH TAG option is used, all the backups created by the command will have tag specified with WITH TAG option. Action: The TAG option can be removed to not display the message. RMAN-06791: changed the DB_UNIQUE_NAME value from string to string Cause: This is an informational message only. Action: No action is required. RMAN-06792: database db_unique_name is "string", db_name is "string" and DBID is string Cause: UNREGISTER DB_UNIQUE_NAME or CHANGE DB_UNIQUE_NAME command was executed, hence RMAN displayed the database information for which DB_UNIQUE_NAME the metadata will be removed/renamed in the recovery catalog. Action: No action required, this is an informational message only. RMAN-06793: database with db_unique_name string unregistered from the recovery catalog Cause: UNREGISTER DB_UNIQUE_NAME command was executed. Action: No action required, this is an informational message only. RMAN-06795: Flashback database logging is not on. Cause: A FLASHBACK DATABASE command was tried but flashback database logging has not been enabled. Action: Flashback database logging must be enabled via the ALTER DATABASE FLASHBACK ON command before a FLASHBACK DATABASE command can be tried. If the database must be taken back in time then a restore and incomplete recovery must be performed. RMAN-06796: Not enough flashback database log data to do FLASHBACK. Cause: There was not enough flashback database log data to do the FLASHBACK DATABASE. Action: If the database must be taken back in time then a restore and incomplete recovery must be performed. RMAN-06797: Grant succeeded. Cause: This is an informational message issued in response to a GRANT command. Action: No action required. RMAN-06798: Revoke succeeded. Cause: This is an informational message issued in response to a REVOKE command. Action: No action required. RMAN-06799: found eligible base catalog owned by string Cause: When creating a virtual private catalog, an 11g base catalog was found, owned by the specified user, and the currently connected catalog user has been granted privileges on this catalog, and can therefore create a virtual private catalog using this base catalog. This is an informational message issued in response to a CREATE VIRTUAL CATALOG command. Action: No action required. RMAN-06800: found ineligible base catalog owned by string Cause: When creating a virtual private catalog, an 11g base catalog was found, owned by the specified user, and the currently connected catalog user has not been granted any privileges on this catalog. This is an informational message issued in response to a CREATE VIRTUAL CATALOG command. Action: No action required. RMAN-06801: no base catalog found Cause: When trying to create a virtual catalog, either no base catalog was found, or this user has no privilege to create a virtual catalog against any existing base catalog. Action: Establish the correct privileges and re-create the virtual catalog. RMAN-06802: too many eligible base catalogs found Cause: When trying to create a virtual catalog, more than one base catalog was found that is eligible to be the base catalog for this virtual catalog. Action: Revoke privileges so that the current catalog user has privileges on only one base catalog, then re-issue the CREATE VIRTUAL CATALOG command. RMAN-06803: created virtual catalog against base catalog owned by string Cause: A virtual private catalog was created, where the base catalog data is owned by the specified user. This is an informational message issued in response to a CREATE VIRTUAL CATALOG command. Action: No action required. RMAN-06804: Enter value for string: Cause: This is a user prompt. Action: Enter a substitution value to proceed. RMAN-06805: SET NEWNAME command has not been issued for tempfile string Cause: A SWITCH command was specified for a tempfile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued. Action: Correct and resubmit the SWITCH command. RMAN-06806: compression algorithm 'string' of release string not found Cause: An unsupported compression algorithm was specified for the backup. Action: Query the V$RMAN_COMPRESSION_ALGORITHM view for the list of suppmrted compression algorithms. Specify a valid compression algorithm and retry the command. RMAN-06807: compression algorithm 'string' of release string cannot be used because database compatibility is less than string Cause: The compression algorithm is not supported because the current compatibility level of the database is too low. Action: Query the V$RMAN_COMPRESSION_ALGORITHM view for the list of supported compression algorithms. Specify a valid compression algorithm and retry the command. RMAN-06808: SECTION SIZE cannot be used when piece limit is in effect Cause: The SECTION SIZE backup option was used together with the MAXPIECESIZE channel limit. These options are mutually exclusive, because they are independant methods of creating multiple backup pieces with one backup command. Action: Use one option or the other, but not both. RMAN-06809: compression algorithm 'string' of release string requires advanced compression option Cause: The compression algorithm was not supported because it requires advanced compression option to be enabled. Action: Enable advanced compression option by setting advanced_compression_option_usable=true or specify a different compression algorithm. RMAN-06810: specification does not match any datafile copy in the repository Cause: No datafile copies were found that match specification in the recovery catalog or target database control file. Action: Check the specifier. RMAN-06811: specification does not match any control file copy in the repository Cause: No control file copies were found that match specification in the recovery catalog or target database control file. Action: Check the specifier. RMAN-06812: specification does not match any backup in the repository Cause: No backups were found that match specification in the recovery catalog or target database control file. Action: Check the specifier. ADD NEW KRMK ERROR MESSAGES HERE RMAN-06898: recovery catalog is partially upgraded to string Cause: The recovery catalog database was not completely upgraded to the specified version. Either there were some errors during execution of UPGRADE CATALOG or UPGRADE CATALOG was cancelled before completion. Action: Execute UPGRADE CATALOG again. RMAN-06899: updating recovery catalog with new database incarnation Cause: The target database has a new incarnation that has not already been seen by the recovery catalog. This usually happens because a Point-in-Time Recovery was done. RMAN has made the necessary updates to the recovery catalog. Action: This is an informational message only. RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row Cause: The routine createRmanStatusRow() or createRmanOutputRow() could add new row into V$RMAN_STATUS or V$RMAN_OUTPUT. Action: Check the associated error messages. If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows Cause: Informational message only. Action: No action required. RMAN-06902: AS COMPRESSED BACKUPSET option cannot be used when backing up backup sets Cause: The backup set was specified with AS COMPRESSED BACKUPSET. Action: Remove the AS COMPRESSED BACKUPSET option. RMAN-06903: backup of datafile string was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run the BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06904: backup of archived log for thread number with sequence number and starting SCN of string was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06905: backup of backup set key number was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06906: backup of control file was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06907: MINIMIZE LOAD option not allowed for the specified input files Cause: This option was specified in a backup command specification for BACKUP BACKUPSET or BACKUP CURRENT CONTROLFILE command. Action: Remove the MINIMIZE LOAD option and retry the command. RMAN-06908: WARNING: operation will not run in parallel on the allocated channels Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition. Action: None RMAN-06909: WARNING: parallelism require Enterprise Edition Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition. Action: None RMAN-06910: can not invoke parallel recovery for test recovery Cause: Recover database was called with TEST and PARALLEL option Action: Call recover database with either just the TEST or PARALLEL option RMAN-06911: only one PARALLEL or NOPARALLEL clause may be specified Cause: Recover database was called with PARALLEL and NOPARALLEL option Action: Call recover database with either just the PARALLEL or NOPARALLEL option. RMAN-06912: backup of spfile was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06913: validate cancelled because there are no files to validate Cause: All files for this validate command were skipped, therefore no files to validate. Action: This message is informational only. RMAN-06914: BLOCK string must be greater or equal to BLOCK string Cause: The value of TO block number was less than the value of from block number. Action: Increase the value of TO BLOCK past the value of from BLOCK and retry the command. RMAN-06915: restore point string already exists Cause: The specified restore point already exists on this database. Action: Use LIST RESTORE POINT to see existing names and retry the command with a unique restore point name. RMAN-06920: database string is not open read-only Cause: CONVERT DATABASE attempted on a database that was not open read-only. Action: Open the database in read-only mode and retry the operation. RMAN-06921: Convert database check failed Cause: This database could not be transported because DBMS_TDB.CHECK_DB returned FALSE. Action: None RMAN-06922: External table string.string found in the database Cause: An external table was found in the database. Action: Redefine the table in the transported database. RMAN-06923: Directory string.string found in the database Cause: A directory object was found in the database. Action: Redefine the directory in the transported database. RMAN-06924: BFILE string.string found in the database Cause: A BFILE was found in the database. Action: Redefine the BFILE in the transported database. RMAN-06925: BFILEs are used in the system, please redefine them in the transported database Cause: BFILEs may or may not exist in the database. Automatically performed BFILE check failed because database was open read-only and could not allocate temporary space. This does not affect CONVERT DATABASE operation. Action: Use DBMS_TDB.CHECK_EXTERNAL to perform BFILE check when the database is open in read/write mode. RMAN-06926: User string with string privilege found in password file Cause: Password file was used. Action: Re-create the password file on the target platform using ORAPWD for the transported database. RMAN-06927: Cannot specify NEW DATABASE clause more than once Cause: NEW DATABASE clause specified more than once Action: Remove redundant NEW DATABASE clause and retry the operation. RMAN-06928: Cannot specify ON TARGET PLATFORM clause more than once Cause: ON TARGET PLATFORM clause specified more than once Action: Remove redundant ON TARGET PLATFORM clause and retry the operation. RMAN-06929: Cannot specify TRANSPORT SCRIPT clause more than once Cause: TRANSPORT SCRIPT clause specified more than once Action: Remove redundant ON TARGET PLATFORM clause and retry the operation. RMAN-06930: Cannot specify SKIP clause more than once Cause: SKIP clause specified more than once Action: Remove redundant SKIP clause and retry the operation. RMAN-06931: Cannot specify FROM PLATFORM clause Cause: CONVERT DATABASE command cannot use FROM PLATFORM clause. Action: Change FROM PLATFORM clause and retry. RMAN-06932: Database name 'string' longer than number Cause: The specified database name exceeded the maximum allowable database name length. Action: Correct the database name. RMAN-06933: Transport script name too long Cause: The specified transport script name exceeded the maximum allowable script name length. Action: Correct the script name. RMAN-06934: Format string too long Cause: The specified format string exceeded the maximum allowable format string length. Action: Correct the format string. RMAN-06935: Convert script name too long Cause: The specified convert script name exceeded the maximum allowable script name length. Action: Correct the script name. RMAN-06941: Database must be closed and mounted EXCLUSIVE and RESTRICTED. Cause: DROP DATABASE was attempted while the database was open or not mounted EXCLUSIVE and RESTRICTED. Action: Change the database state to mounted EXCLUSIVE and RESTRICTED. RMAN-06942: OPTION number is invalid; OPTION must be between string and string Cause: An invalid OPTION was used. Action: Change the OPTION argument. RMAN-06943: no automatic repair OPTION number was listed in ADVISE FAILURE Cause: The OPTION specified was not one of the automatic repair options listed by ADVISE FAILURE or there were no options listed by the ADVISE FAILURE command. Action: Change the OPTION argument or resubmit ADVISE FAILURE with a different set of failures. RMAN-06944: contents of repair script: Cause: This is an informational message only. Action: No action is required. RMAN-06945: no repair script present for REPAIRID string Cause: REPAIRID option specified in the command was invalid or the repair script had been purged from Automated Diagnostic Repository. Action: Retry REPAIR FAILURE command with a different OPTION number. RMAN-06946: executing repair script Cause: This is an informational message only. Action: No action is required. RMAN-06947: searching flashback logs for block images until SCN string Cause: Starting the flashback log search for RECOVER...BLOCK command. The log is searched until the indicated system change number (SCN). Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06948: searching flashback logs for block images Cause: Starting the flashback log search for RECOVER...BLOCK command. The log is searched until the end of the log. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06949: finished flashback log search, restored string blocks Cause: Flashback log search finished for RECOVER...BLOCK command. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06950: invalid validate option specified: string Cause: The specified object was invalid with VALIDATE command. Action: Delete the invalid operand. RMAN-06951: repair failure complete Cause: This is an informational message only. Action: No action is required. RMAN-06952: database needs to be restarted Cause: The target database control file was missing. Action: Restart the instance and repair the database. RMAN-06953: no automatic repairs were listed by ADVISE FAILURE Cause: There were no automatic repairs listed by the ADVISE FAILURE command. Action: Choose a different failure, submit ADVISE FAILURE command, and then submit REPAIR FAILURE command. RMAN-06954: REPAIR command must be preceded by ADVISE command in same session Cause: The ADVISE command was not issued in the same session as the REPAIR command. Action: Submit ADVISE command and then submit the REPAIR command in same session. RMAN-06955: Network copies are only supported for image copies. Cause: An attempt was made to specify BACKUP AUXILIARY FORMAT without specifying the AS COPY clause. A network copy is only supported with an image copy. Action: Seek an alternate method of copying the desired files. RMAN-06956: create datafile failed; retry after removing string from OS Cause: An attempt was made to re-create a database file. This attempt failed. Action: If the indicated file already exists, remove the file from operating system and retry the RMAN command. RMAN-06957: finished standby search, restored string blocks Cause: Standby search finished for RECOVER...BLOCK command. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06958: Executing: string Cause: This is an informational message only. Action: No action is required. RMAN-06959: WARNING: repair completed but could not verify that failures were fixed by it Cause: RMAN repair command successfully completed but could not check if the failures were fixed. Action: Use LIST FAILURE command to verify repair results. RMAN-06960: EXPDP> string Cause: This is an informational message only. Action: No action is required. RMAN-06961: IMPDP> string Cause: This is an informational message only. Action: No action is required. RMAN-06962: Error received during export of metadata Cause: Data Pump could not perform export of tablespace metadata. Action: See accompanying datapump messages indicating the cause of the error. RMAN-06963: Error received during import of metadata Cause: Data Pump could not perform import of tablespace metadata. Action: See accompanying datapump messages indicating the cause of the error. RMAN-06964: option string cannot be used with string Cause: Incompatible options were specified that caused the command to fail. Action: Remove one of the options from the command and retry. RMAN-06965: Datapump job has stopped Cause: A Data Pump error has caused the job to stop. Action: See accompanying datapump messages or look for a Data Pump trace file for the cause of the error. RMAN-06966: Invalid release number string Cause: An incorrectly formatted release number was specified. Action: Specify a valid release number in n.n.n.n.n format. RMAN-06967: finished primary search, recovered string blocks Cause: Primary Database search finished for RECOVER...BLOCK command. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06970: NEWNAME 'string' for database must include %f or %U format Cause: The newname in SET NEWNAME FOR DATABASE did not include a format specifier to produce different newnames for the datafiles. Action: Include %f or %U in the newname or use SET NEWNAME FOR DATABASE TO NEW to ensure datafiles get different datafile names. RMAN-06971: NEWNAME 'string' for tablespace must include %f or %U format Cause: The newname in SET NEWNAME FOR TABLESPACE did not include a format specifier to produce different newnames for the datafiles. Action: Include %f or %U in the newname or use SET NEWNAME FOR TABLESPACE ... TO NEW to ensure datafiles get different datafile names. RMAN-06980: The following errors need to be fixed before peforming this command Cause: The tablespaces failed validation by DBMS_TTS.TRANSPORT_SET_CHECK. Action: Fix accompanying violations before attempting the command again. RMAN-06981: Violation: string Cause: This message was issued to show a violation obtained from the DBMS_TTS.TRANSPORT_SET_CHECK. Action: Fix violation before attempting the command again. RMAN-07000: List of SPFILE Backups Cause: This message is issued in response to a LIST BACKUP OF SPFILE command. Action: No action is required. RMAN-07025: string is not supported for foreign archived log Cause: The specified option was not supported for foreign archived log. Action: Do not use the specified command for foreign archived log. RMAN-07200: no failures found that match specification Cause: A failure specifier did not match any failures in the Automated Diagnostic Repository. Action: Resubmit the command with a different failure specifier. You can use the LIST FAILURE ALL command in Recovery Manager to display all failures known to RMAN. RMAN-07207: changed string failures to HIGH priority Cause: This is an informational message only. Action: No action is required. RMAN-07208: changed string failures to LOW priority Cause: This is an informational message only. Action: No action is required. RMAN-07209: closed string failures Cause: This is an informational message only. Action: No action is required. RMAN-07210: new failures after most recent LIST FAILURE command Cause: New failures were found since last LIST FAILURE command in this RMAN session. Action: No action is required. This is an informational message only. RMAN-07211: failure option not specified Cause: ALL, CRITICAL, HIGH, LOW, or list of failure numbers was not specified. Action: Specify a failure option and resubmit the command. RMAN-07212: skipping failure string because it was CLOSED Cause: The specified failure has been already closed, so ADVISE FAILURE or CHANGE FAILURE cannot be executed on this failure. Action: This is an informational message only. No action is required. RMAN-07213: Mandatory Manual Actions Cause: This is an informational message only. Action: No action is required. RMAN-07215: Automated Repair Options Cause: This is an informational message only. Action: No action is required. RMAN-07220: no manual actions available Cause: This is an informational message only. Action: No action is required. RMAN-07222: ======================= Cause: This is an informational message only. Action: No action is required. RMAN-07251: Repair script: string Cause: This is an informational message only. Action: No action is required. RMAN-07252: ======================== Cause: This is an informational message only. Action: No action is required. RMAN-07253: ======================== Cause: This is an informational message only. Action: No action is required. RMAN-07255: priority change for failure string failed Cause: An attempt was made to change the priority of a child failure. Action: Specify the parent failure ID to change the child failure. RMAN-07256: cannot change priority of child failure Cause: An attempt was made to change the priority of child failure. Action: This message should be followed by one or more 7255 messages. RMAN-07259: string critical failures exist; cannot exclude from ADVISE FAILURE Cause: ADVISE FAILURE was executed for HIGH or LOW priority failures when CRITICAL failures existed. Action: Execute ADVISE FAILURE with the CRITICAL or ALL options. RMAN-07262: no automatic repair options available Cause: This is an informational message only. Action: No action is required. RMAN-07500: searching for all files that match the pattern string Cause: This is an informational message only. Action: No action is required. RMAN-07501: searching for all files in the recovery area Cause: This is an informational message only. Action: No action is required. RMAN-07502: List of Files Unknown to the Database Cause: This message is issued in response to a CATALOG command. Action: No action is required. RMAN-07505: no files found to be unknown to the database Cause: This is an informational message displayed by the CATALOG command. The command either found no files, or all files that matched the specified search pattern were already present in the target database control file. Action: No action is required. RMAN-07507: cataloging files... Cause: This is an informational message only. Action: No action is required. RMAN-07508: cataloging done Cause: This is an informational message only. Action: No action is required. RMAN-07509: List of Cataloged Files Cause: This message is issued in response to a CATALOG command. Action: No action is required. RMAN-07513: List of Files Which Where Not Cataloged Cause: This message is issued in response to a CATALOG command. Action: No action is required. RMAN-07514: ======================================= Cause: This is an informational message only. Action: No action is required. RMAN-07515: File Name: string Cause: This is an informational message only. Action: No action is required. RMAN-07516: Reason: Error reading Cause: This is an informational message only. Action: No action is required. RMAN-07517: Reason: The file header is corrupted Cause: Either the file is not an Oracle file or the file header is corrupted. Action: Delete the file using OS utility. RMAN-07518: Reason: Foreign database file DBID: string Database Name: string Cause: This is an informational message only. Action: No action is required. RMAN-07519: Reason: Error while cataloging. See alert.log. Cause: This is an informational message only. Action: No action is required. RMAN-07520: Reason: Data pump dump file Cause: This is an informational message only. Action: No action is required. RMAN-07521: cannot create recovery catalog in database version string; version string required Cause: An attempt was made to use a version of the recovery catalog schema that was incompatible with the version of the database. Action: Upgrade the catalog database to at least the required version or install the catalog schema in a different database which is of at least the required version. RMAN-07522: CREATE TYPE privilege must be granted to user string Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the USERID that was supplied in the CATALOG connect string does not have the CREATE TYPE privilege granted. Action: Grant CREATE TYPE privilege to the recovery catalog owner. RMAN-07523: List of files in Recovery Area not managed by the database Cause: This message was issued in response to a CATALOG RECOVERY AREA command. Action: No action is required. RMAN-07524: ========================================================== Cause: This is an informational message only. Action: No action is required. RMAN-07525: Reason: File is not a supported file type in Recovery Area Cause: This message should be accompanied by other message(s) indicating the name of file that was not supported in recovery area. Any file other than current control file, online log, archived log, RMAN backups and flashback log is not supported in recovery area. This is an informational message only. Action: No action is required. RMAN-07526: Reason: File is not an Oracle Managed File Cause: This message should be accompanied by other message(s) indicating the name of file that was not a oracle managed file. This is an informational message only. Action: No action is required. RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter Cause: This message should be accompanied by other message(s) indicating the name of file that was not created using DB_RECOVERY_FILE_DEST initialization parameter. One of the following scenarios caused this error: 1) This is an archived log file and was created when the LOG_ARCHIVE_DEST_n initialization parameter was set explicitly to recovery area location. For example, LOG_ARCHIVE_DEST_1='location=+FRA' where '+FRA' was also your DB_RECOVERY_FILE_DEST value. 2) This is an RMAN backup file and was created in a recovery area using the FORMAT option of the BACKUP command. 3) This is an online log file or current control file and was created prior to setting the recovery area. 4) This file fits none of the above scenarios and is not supported by the recovery area. Action: All of following actions will resolve future occurrences of this error: 1) To create archived logs in recovery area, set the LOG_ARCHIVE_DEST_n initialization parameter to 'location=USE_DB_RECOVERY_FILE_DEST'. Do not explicitly set the LOG_ARCHIVE_DEST_n initialization parameter to a recovery area location. 2) To create RMAN backups in recovery area, do not use the FORMAT option of the BACKUP command. All of following actions will resolve current problem: 1) If this is an archived log file or an RMAN backup file, use the CATALOG command to re-catalog the files. 2) If this is an online log file or a current control file to be managed by the recovery area, re-create the file using the DB_RECOVERY_FILE_DEST initialization parameter. RMAN-07528: number of files not managed by recovery area is string, totaling string Cause: This message should be accompanied by other message(s) indicating the list of files. Either the files listed are not known to the database or not managed by recovery area. The number and size of the files are shown. This is an informational message only. Action: No action is required. RMAN-07529: Reason: catalog is not supported for this file type Cause: The CATALOG command encountered one or more files of types that cannot be cataloged. These file types include online redo logs, flashback logs, block change tracking files, and data pump files. This message will be accompanied by other messages indicating the names of the file's that could not be cataloged. Action: No action is required. RMAN-07530: Reason: This file type is not requested for cataloging Cause: This is an informational message only. Action: No action is required. RMAN-08000: channel string: copied datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08001: restore not complete Cause: All of the backup pieces have been successfully applied, but DBMS_BACKUP_RESTORE package indicates that the restore conversation is not complete. This usually means that the backup set contained corrupt data. Action: Restore the files from a different backup set, if possible. The Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can be used to prevent Recovery Manager from attempting to restore from the corrupt backup piece(s). RMAN-08002: starting full resync of recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-08003: channel string: reading from backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08004: full resync complete Cause: This is an informational message only. Action: No action is required. RMAN-08005: new incarnation of database registered in recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-08006: database registered in recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-08007: channel string: copied datafile copy of datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08008: channel string: starting full datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08009: channel string: starting archived log backup set Cause: This is an informational message only. Action: No action is required. RMAN-08010: channel string: specifying datafile(s) in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08011: including current control file in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08012: including control file copy in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08013: channel string: backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08014: channel string: specifying archived log(s) in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08015: datafile string switched to datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08016: channel string: starting datafile backup set restore Cause: This is an informational message only. Action: No action is required. RMAN-08017: channel string: starting archived log restore to default destination Cause: This is an informational message only. Action: No action is required. RMAN-08018: channel string: starting archived log restore to user-specified destination Cause: This is an informational message only. Action: No action is required. RMAN-08019: channel string: restoring datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08020: including standby control file in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08021: channel string: restoring control file Cause: This is an informational message only. Action: No action is required. RMAN-08022: channel string: restoring archived log Cause: This is an informational message only. Action: No action is required. RMAN-08023: channel string: restored backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08025: channel string: copied control file copy Cause: This is an informational message only. Action: No action is required. RMAN-08026: channel string: copied archived log Cause: This is an informational message only. Action: No action is required. RMAN-08027: channel string: copied current control file Cause: This is an informational message only. Action: No action is required. RMAN-08028: channel string: copy current control file failed Cause: This is an informational message only. Action: No action is required. RMAN-08029: snapshot control file name set to default value: string Cause: This is an informational message only. Action: No action is required. RMAN-08030: allocated channel: string Cause: This is an informational message only. Action: No action is required. RMAN-08031: released channel: string Cause: This is an informational message only. Action: No action is required. RMAN-08032: channel string: RECID string STAMP string does not match recovery catalog Cause: The record that identifies the source file for a copy or backup database does not contain the same data as is stored in the recovery catalog. Action: Perform a full resync and retry the operation. If the problem persists, then contact Oracle. RMAN-08033: channel string: including datafile copy of datafile string in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08034: full resync skipped, target database not mounted Cause: This is an informational message only. Action: No action is required. RMAN-08035: partial resync skipped, target database not mounted Cause: This is an informational message only. Action: No action is required. RMAN-08036: channel string: could not create control file record for string string Cause: The record identifying the named file was no longer present in the target database control file, and repeated attempts to inspect the file were unsuccessful in creating the record. This could be because the circular-reuse section of the control file which holds information about the specified type of file is too small and there is other database activity which is causing the record to be overwritten before it can be used. Action: Try increasing either the size of the control file circular-reuse section for this file type (datafile copy or archived log, as indicated in the error message, or the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter. If neither of those remedies works then contact Oracle. RMAN-08037: channel string: unexpected validation return code string Cause: This is an internal error that should never be issued. Action: Contact Oracle Support. RMAN-08038: channel string: starting piece string at string Cause: This is an informational message only. Action: No action is required. RMAN-08039: channel string: starting incremental datafile backup set restore Cause: This is an informational message only. Action: No action is required. RMAN-08040: full resync skipped, control file is not current or backup Cause: This is an informational message only. Action: No action is required. RMAN-08041: partial resync skipped, control file is not current or backup Cause: This is an informational message only. Action: No action is required. RMAN-08042: channel string: copied standby control file Cause: This is an informational message only. Action: No action is required. RMAN-08043: channel string: copy standby control file failed Cause: This is an informational message only. Action: No action is required. RMAN-08044: channel string: finished piece string at string Cause: This is an informational message only. Action: No action is required. RMAN-08045: channel string: finished piece string at string with string copies Cause: This is an informational message only. Action: No action is required. RMAN-08046: channel string: starting compressed full datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08047: channel string: starting compressed incremental level string datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08048: channel string: starting incremental level string datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08049: channel string: starting compressed archived log backup set Cause: This is an informational message only. Action: No action is required. RMAN-08050: cataloged datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08051: cataloged archived log Cause: This is an informational message only. Action: No action is required. RMAN-08052: cataloged control file copy Cause: This is an informational message only. Action: No action is required. RMAN-08053: channel string: finished piece string at string with string copies and tag string Cause: This is an informational message only. Action: No action is required. RMAN-08054: starting media recovery Cause: This is an informational message only. Action: No action is required. RMAN-08056: skipping datafile string because it has not changed Cause: The specified datafile has not had its checkpoint advanced since the previous backup, therefore it does not need a new incremental backup. Action: This is an informational message only. RMAN-08057: channel string: backup cancelled because all files were skipped Cause: All datafiles for this backup were skipped, therefore no backup is created. Action: This is an informational message only. RMAN-08058: replicating control file Cause: This is an informational message only. Action: No action is required. RMAN-08059: media recovery failed Cause: This is an informational message only. Action: No action is required. RMAN-08060: unable to find archived log Cause: This is an informational message only. Action: No action is required. RMAN-08061: WARNING: change failure ID string failed due to error ORA-string Cause: CHANGE FAILURE for the indicated failure ID encountered an error. Action: See the indicated ORA error message for the cause of the error. RMAN-08062: WARNING: cannot change priority of a critical failure string Cause: An attempt was made to change priority of a failure with CRITICAL priority. Action: No action is required. RMAN-08066: database reset to incarnation string Cause: This is an informational message only. Action: No action is required. RMAN-08070: deleted datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08071: channel string: deleting archived log(s) Cause: This is an informational message only. Action: No action is required. RMAN-08072: deleted control file copy Cause: This is an informational message only. Action: No action is required. RMAN-08073: deleted backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08074: crosschecked backup piece: found to be 'string' Cause: This is an informational message only. Action: No action is required. RMAN-08085: created script string Cause: This is an informational message only. Action: No action is required. RMAN-08086: replaced script string Cause: This is an informational message only. Action: No action is required. RMAN-08087: channel string: started backup set validation Cause: This is an informational message only. Action: No action is required. RMAN-08088: applied offline range to datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08089: channel string: specifying datafile(s) to restore from backup set Cause: This is an informational message only. Action: No action is required. RMAN-08090: channel string: starting proxy restore Cause: This is an informational message only. Action: No action is required. RMAN-08091: channel string: specifying datafile(s) for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08092: channel string: specifying datafile copy of datafile string for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08093: specifying current control file for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08094: channel string: specifying datafile(s) for proxy restore Cause: This is an informational message only. Action: No action is required. RMAN-08096: channel string: starting validation of datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08097: channel string: starting validation of archived log backup set Cause: This is an informational message only. Action: No action is required. RMAN-08099: specifying standby control file for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08100: channel string: starting proxy validation Cause: This is an informational message only. Action: No action is required. RMAN-08101: channel string: proxy validation complete Cause: This is an informational message only. Action: No action is required. RMAN-08102: channel string: located backup piece: string Cause: This is an informational message only. Action: No action is required. RMAN-08103: channel string: could not locate backup piece: string Cause: This is an informational message only. Action: No action is required. RMAN-08104: channel string: input backup set: count=string, stamp=string, piece=string Cause: This is an informational message only. Action: No action is required. RMAN-08105: channel string: backup cancelled because no pieces were found Cause: All backup sets specified has no pieces. Therefore, no backup set is created. Action: This is an informational message only. RMAN-08106: channel string: restoring block(s) Cause: This is an informational message only. Action: No action is required. RMAN-08107: skipping inaccessible backup set count=string STAMP=string Cause: The indicated backup set will not be backed up because one or more pieces of the backup set could not be read, and the SKIP INACCESSIBLE option was specified. Action: No action is required. RMAN-08108: channel string: specifying block(s) to restore from backup set Cause: This is an informational message only. Action: No action is required. RMAN-08109: channel string: restored block(s) from backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08110: failover to next copy of backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08111: some blocks not recovered: See trace file for details Cause: Some blocks not recovered due to errors. Action: See trace file for details of the problem. RMAN-08112: archived log failover was done on string, check alert log for more info Cause: This is an informational message to indicate the server found a corrupted block in an archived log and had to switch to another copy of the same archived log in an alternate archived log destination to get corresponding un-corrupted block. Action: If backup is done with delete input option, nothing needs to be done. Otherwise delete the archived log that has corrupted block(s) as recovery on applying this log would fail. Alert log contains name of the log that has corrupted block(s). RMAN-08113: including current SPFILE in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08114: channel string: restoring SPFILE to PFILE Cause: This is an informational message only. Action: No action is required. RMAN-08115: channel string: restoring SPFILE Cause: This is an informational message only. Action: No action is required. RMAN-08116: output file name is original SPFILE location Cause: This is an informational message only. Action: No action is required. RMAN-08117: channel string: the AUTOBACKUP does not contain an SPFILE Cause: The requested AUTOBACKUP does not contain a SPFILE. This is because the instance was not started with a SPFILE when the AUTOBACKUP was created. Action: No action is required. RMAN will try three older AUTOBACKUPS before signaling . RMAN-08118: WARNING: could not delete the following archived redo log Cause: The routine deleteArchivedLog() could not delete an archived redo log on the target instance. Action: Check the accompanying file specification and the associated error messages. The file specification indicates what archived redo log on the target instance RMAN was trying to delete and the error messages indicate why RMAN was unable to delete it. Resolve the problem by first confirming that the archived redo log in question has been backed up, do the deletion manually, and then do a crosscheck so that RMAN is aware of the deletion. RMAN-08119: skipping backup piece handle string; already exists Cause: A BACKUP command does not need to backup control file AUTOBACKUP pieces, because they already exists. Action: This is an informational message, no action is required. RMAN-08120: WARNING: archived log not deleted, not yet applied by standby Cause: This is an informational message to alert the user that an archived log that should have been deleted was not as it has not been applied to the standby database. The next message identifies the archived log Action: Archivelog can be deleted after it has been applied to standby database. RMAN-08121: keep attributes for the backup are deleted Cause: This is an informational message only. Action: No action is required. RMAN-08122: keep attributes for the backup are changed Cause: This is an informational message only. Action: No action is required. RMAN-08123: keep attributes for the datafile/control file copy are deleted Cause: This is an informational message only. Action: No action is required. RMAN-08124: keep attributes for the datafile/control file copy are changed Cause: This is an informational message only. Action: No action is required. RMAN-08125: keep attributes for the proxy copy are deleted Cause: This is an informational message only. Action: No action is required. RMAN-08126: keep attributes for the proxy copy are changed Cause: This is an informational message only. Action: No action is required. RMAN-08127: cataloged backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08128: uncataloged backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08129: failover to piece handle=string tag=string Cause: This is an informational message to indicate the server found a corrupted block in a piece and had to switch to another copy of piece to get corresponding un-corrupted block. Action: See alert log for information on corruption block(s) and the name of the piece that has the corrupted block(s). RMAN-08130: failover to copy on device type string Cause: This is an informational message to indicate the RMAN could not successfully restore the database using the specified backups. An attempt was made to restore the datafiles/archived logs/ control file/SPFILE using the same backup set on a different device type. Action: See accompanying additional error messages indicating the cause of the failover. RMAN-08131: channel string: specifying datafile copies to recover Cause: This is an informational message only. Action: No action is required. RMAN-08132: WARNING: cannot update recovery area reclaimable file list Cause: This error should be accompanied by other errors giving the cause of failure to update reclaimable file list. Action: Check the accompanying error. RMAN-08133: channel string: the AUTOBACKUP does not contain a standby control file. Cause: The requested AUTOBACKUP did not contain a standby control file. Action: No action is required, RMAN will try three older AUTOBACKUPS before signaling . RMAN-08135: some corrupt blocks found during conversion of file string Cause: While converting the specified file from one platform to another, some corrupt blocks were discovered in the specified file. Details about the corruption have been written to a server trace file. Action: If these corrupt blocks are unexpected, you may be able to use Block Media Recovery at the source database to fix the problem, then re-convert the files. RMAN-08136: channel string: deleting incremental backup(s) Cause: This is an informational message only. Action: No Action Required. RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process Cause: An archived log that should have been deleted was not as it was required by upstream capture process or Data Guard. The next message identifies the archived log. Action: This is an informational message. The archived log can be deleted after it is no longer needed. See the documentation for Data Guard to alter the set of active Data Guard destinations. See the documentation for Streams to alter the set of active streams. RMAN-08138: WARNING: archived log not deleted - must create more backups Cause: An archived log that should have been deleted was not as it it did not meet the user specified archive log deletion policy of number of backups required before deleting the logs. Action: This is an informational message. The archived log can be deleted after more backups are created to satify archivelog deletion policy. RMAN-08139: WARNING: archived redo log not deleted, needed for guaranteed restore point Cause: An archived log that should have been deleted was not because it is required for guaranteed restore point. Action: This is an informational message. The archived redo log can be deleted after backups are created or after deleting the guaranteed restore point that requires the log. RMAN-08140: channel string: starting validation of datafile Cause: This is an informational message only. Action: No action is required. RMAN-08141: channel string: specifying datafile(s) for validation Cause: This is an informational message only. Action: No action is required. RMAN-08142: including standby control file for validation Cause: This is an informational message only. Action: No action is required. RMAN-08143: including current control file for validation Cause: This is an informational message only. Action: No action is required. RMAN-08144: channel string: validation complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08145: channel string: starting validation of archived log Cause: This is an informational message only. Action: No action is required. RMAN-08146: channel string: specifying archived log(s) for validation Cause: This is an informational message only. Action: No action is required. RMAN-08150: created global script string Cause: This is an informational message only. Action: No action is required. RMAN-08151: replaced global script string Cause: This is an informational message only. Action: No action is required. RMAN-08152: global script string written to file string Cause: This is an informational message only. Action: No action is required. RMAN-08153: deleted global script: string Cause: This is an informational message only. Action: No action is required. RMAN-08154: deleted script: string Cause: This is an informational message only. Action: No action is required. RMAN-08155: printing stored global script: string Cause: This is an informational message only. Action: No action is required. RMAN-08156: printing stored script: string Cause: This is an informational message only. Action: No action is required. RMAN-08157: script string written to file string Cause: This is an informational message only. Action: No action is required. RMAN-08158: executing script: string Cause: This is an informational message only. Action: No action is required. RMAN-08159: executing global script: string Cause: This is an informational message only. Action: No action is required. RMAN-08160: script commands will be loaded from file string Cause: This is an informational message only. Action: No action is required. RMAN-08161: contents of Memory Script: Cause: This is an informational message only. Action: No action is required. RMAN-08162: executing Memory Script Cause: This is an informational message only. Action: No action is required. RMAN-08163: validation succeeded for backup piece Cause: The VALIDATE HEADER option determined that the backup piece still matches its data. Action: None - this is an informational message. RMAN-08164: validation succeeded for proxy copy Cause: The VALIDATE HEADER option determined that the proxy copy still matches its data. Action: None - this is an informational message. RMAN-08165: could not locate proxy copy string Cause: The specified proxy copy could not be found on proxy channel. Action: If the proxy copy has been deleted, use the CROSSCHECK BACKUP command to correct the recovery catalog or target database control file entries. RMAN-08166: validation succeeded for datafile copy and control file copy Cause: The VALIDATE HEADER option discovered that the datafile copy and control file copy still matches its data in the recovery catalog or target database control file. Action: None - this is an informational message. RMAN-08167: WARNING: string encountered a piece that was in use Cause: The backup piece is currently in use by another BACKUP, RESTORE or DELETE operation. Action: Use LIST to determine if backup has been deleted. If not deleted, then check if any process is hung while accessing the piece and terminate them before retrying DELETE. If using SBT device, then check Media Manager as well. Alternatively, consider the command DELETE FORCE. RMAN-08180: channel string: restore complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08181: media recovery complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08182: channel string: validation complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08183: channel string: block restore complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08184: added tempfile string to tablespace string in control file Cause: This is an informational message only. Action: No action is required. RMAN-08185: renamed tempfile string to string in control file Cause: This is an informational message only. Action: No action is required. RMAN-08186: tempfile string size altered in control file Cause: One of tempfile size attributes AUTOEXTEND, MAXSIZE, NEXTSIZE was altered. This is an informational message only. Action: No action is required. RMAN-08187: WARNING: media recovery until SCN string complete Cause: Media recovery was completed until the indicated system change number (SCN) because the database was in NOARCHIVELOG mode. Action: This is an informational message only. No action is required. RMAN-08190: validate found one or more corrupt blocks Cause: Backup validate found that one or more blocks were corrupt in the specified datafiles. This message should be followed by 8191 message. Action: Repair them at your earliest convenience. RMAN-08191: See trace file string for details Cause: This is an informational message only. Action: No action is required. RMAN-08300: Run SQL script string on the target platform to create database Cause: This is an informational message only. Action: No action is required. RMAN-08301: Edit init.ora file string. This PFILE will be used to create the database on the target platform Cause: This is an informational message only. Action: No action is required. RMAN-08302: Run RMAN script string on target platform to convert datafiles Cause: This is an informational message only. Action: No action is required. RMAN-08303: To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on the target platform Cause: This is an informational message only. Action: Transport script invokes utlirp.sql and utlrp.sql. RMAN-08304: To change the internal database identifier, use DBNEWID Utility Cause: This is an informational message only. Action: Transport script does not invoke DBNEWID Utility automatically. RMAN-08305: channel string: starting to check datafiles Cause: This is an informational message only. Action: No action is required. RMAN-08306: channel string: datafile checking complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08500: channel string: SID=string device type=string Cause: This is an informational message only. Action: No action is required. RMAN-08501: output file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08503: piece handle=string comment=string Cause: This is an informational message only. Action: No action is required. RMAN-08504: input archived log thread=string sequence=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08505: output file name=string Cause: This is an informational message only. Action: No action is required. RMAN-08506: input file name=string Cause: This is an informational message only. Action: No action is required. RMAN-08507: input datafile copy RECID=string STAMP=string file name=string Cause: This is an informational message only. Action: No action is required. RMAN-08508: archived log destination=string Cause: This is an informational message only. Action: No action is required. RMAN-08509: destination for restore of datafile string: string Cause: This is an informational message only. Action: No action is required. RMAN-08510: archived log thread=string sequence=string Cause: This is an informational message only. Action: No action is required. RMAN-08511: piece handle=string tag=string Cause: This is an informational message only. Action: No action is required. RMAN-08512: waiting for snapshot control file enqueue Cause: This is an informational message only. Action: No action is required. RMAN-08513: datafile copy file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08514: archived log file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08515: archived log file name=string thread=string sequence=string Cause: This is an informational message only. Action: No action is required. RMAN-08516: control file copy file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08517: backup piece handle=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08518: channel string: scanning control file copy string Cause: This is an informational message only. Action: No action is required. RMAN-08519: channel string: scanning datafile copy string Cause: This is an informational message only. Action: No action is required. RMAN-08520: channel string: scanning archived log string Cause: This is an informational message only. Action: No action is required. RMAN-08521: offline range RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08522: input datafile file number=string name=string Cause: This is an informational message only. Action: No action is required. RMAN-08523: restoring datafile string to string Cause: This is an informational message only. Action: No action is required. RMAN-08524: input control file copy name=string Cause: This is an informational message only. Action: No action is required. RMAN-08525: backing up blocks string through string Cause: This is an informational message only Action: No action is required. RMAN-08526: channel string: string Cause: This is an informational message only. Action: No action is required. RMAN-08527: channel string: starting string proxy datafile backup at string Cause: This is an informational message only. Action: No action is required. RMAN-08528: channel string: proxy copy complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08529: proxy file handle=string Cause: This is an informational message only. Action: No action is required. RMAN-08530: piece handle=string tag=string comment=string Cause: This is an informational message only. Action: No action is required. RMAN-08531: channel string: proxy copy string is string in media management catalog Cause: This is an informational message only. Action: No action is required. RMAN-08532: channel string: restoring block(s) from datafile copy string Cause: This is an informational message only. Action: No action is required. RMAN-08533: restoring blocks of datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08534: channel string: control file restore from AUTOBACKUP complete Cause: This is an informational message only. Action: No action is required. RMAN-08535: channel string: looking for AUTOBACKUP on day: string Cause: This is an informational message only. Action: No action is required. RMAN-08536: channel string: AUTOBACKUP found: string Cause: This is an informational message only. Action: No action is required. RMAN-08537: channel string: skipped, AUTOBACKUP already found Cause: This is an informational message only. Action: No action is required. RMAN-08538: channel string: no AUTOBACKUP in string days found Cause: This is an informational message only. Action: No action is required. RMAN-08539: backup set key=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08540: channel string: backup set complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08541: channel string: SPFILE restore from AUTOBACKUP complete Cause: This is an informational message only. Action: No action is required. RMAN-08542: channel string: starting proxy archived log backup at string Cause: This is an informational message only. Action: No action is required. RMAN-08543: channel string: specifying archived log(s) for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08544: channel string: specifying archived log(s) for proxy restore Cause: This is an informational message only. Action: No action is required. RMAN-08545: flashback command failed: See trace file for details Cause: An attempt was made to issue a flashback command which failed due to errors. See trace file for details. Action: See trace file for details of the problem. RMAN-08546: channel string: AUTOBACKUP string found in the recovery area Cause: This is an informational message only. Action: No action is required. RMAN-08547: channel string: no AUTOBACKUPS found in the recovery area Cause: The recovery area does not have desired AUTOBACKUP. Action: Check the option UNTIL TIME in case an existing AUTOBACKUP does satisfy the criteria specified in the restore command. Otherwise, verify the init.ora parameters DB_RECOVERY_FILE_DEST and DB_UNIQUE_NAME to verify whether the recovery area location is set correctly. Note that the parameters can be specified as options to the restore command. RMAN-08548: recovery area destination: string Cause: This is an informational message only. Action: No action is required. RMAN-08549: database name (or database unique name) used for search: string Cause: This is an informational message only. Action: No action is required. RMAN-08550: AUTOBACKUP search with format "string" not attempted because DBID was not set Cause: Restore of a control file AUTOBACKUP was attempted without DBID being set. Action: If you want to search for AUTOBACKUP with the indicated format, then specify the DBID of the database using SET DBID and retry the command. RMAN-08551: recovering datafile copy file number=string name=string Cause: This is an informational message only. Action: No action is required. RMAN-08552: backup and output file names are identical: string Cause: The backup file name chosen was identical to output file name specified for a restore operation. Action: This is an informational message only. RMAN will failover to next available backup. RMAN-08553: channel string: restoring control file from AUTOBACKUP string Cause: This is an informational message only. Action: No action is required. RMAN-08554: channel string: restoring spfile from AUTOBACKUP string Cause: This is an informational message only. Action: No action is required. RMAN-08555: channel string: restoring section string of string Cause: This is an informational message only Action: No action is required. RMAN-08556: channel string: backup piece complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08580: channel string: starting datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08581: channel string: datafile copy complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08582: channel string: starting archived log copy Cause: This is an informational message only. Action: No action is required. RMAN-08583: channel string: archived log copy complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08584: copying current control file Cause: This is an informational message only. Action: No action is required. RMAN-08585: copying standby control file Cause: This is an informational message only. Action: No action is required. RMAN-08586: output file name=string tag=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08587: input is copy of datafile string: string Cause: This is an informational message only. Action: No action is required. RMAN-08588: converted datafile=string Cause: This is an informational message only. Action: No action is required. RMAN-08589: channel string: starting datafile conversion Cause: This is an informational message only. Action: No action is required. RMAN-08590: channel string: datafile conversion complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08591: WARNING: invalid archived log deletion policy Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived log deletion policy was APPLIED but there was no mandatory archived log destinations. Action: One of the following: 1) Change archived log deletion policy using CONFIGURE command 2) Make one or more of standby destination as MANDATORY. RMAN-08592: output file name=string tag=string Cause: This is an informational message only. Action: No action is required. RMAN-08599: channel string: throttle time: string Cause: This is an informational message only. Action: No action is required. RMAN-08600: ASM disk group to search: string Cause: This is an informational message only. Action: No action is required. RMAN-08601: channel string: AUTOBACKUP string found in ASM disk group string Cause: This is an informational message only. Action: No action is required. RMAN-08602: channel string: no AUTOBACKUPS found in ASM disk group string Cause: The specified ASM area does not have desired AUTOBACKUP. Action: Check the option UNTIL TIME in case an existing AUTOBACKUP does satisfy the criteria specified in the restore command. Otherwise, verify the values used for the format of the CONFIGURE CONTROLFILE AUTOBACKUP FORMAT command and DB_UNIQUE_NAME to verify whether the ASM area location is set correctly. Note that the DB_UNIQUE_NAME can be specified as option to the restore command. RMAN-08603: skipping string; file in use by another process Cause: The indicated file was not included in the backup because it is part of another restore or delete operation. Action: No action is required. Wait for the other operation to complete, then retry. RMAN-08604: skipping string; file deleted from recovery area to reclaim disk space Cause: The indicated file was not included in the backup because it was deleted from the recovery area to reclaim disk space for other operations. Action: No action is required. RMAN-08605: channel string: SID=string instance=string device type=string Cause: This is an informational message only. Action: No action is required. RMAN-08606: WARNING: The change tracking file is invalid. Cause: Backup found changed blocks that were not marked in the change tracking file. See alert log for more information. Action: Do not use any of the incremental backups taken since the last full backup. RMAN-08607: List of remote backup files Cause: RESTORE command detected that one or more remote backup files were required to perform restore operation. Action: Recall the media from remote site that contains the specified backup files before actual restore operation. The message should be accompanied with the list of remote backup files. RMAN-08608: Initiated recall for the following list of remote backup files Cause: This is an informational message displayed when the specified RECALL option of the RESTORE command detected that one or more remote backup files were required to perform the restore operation. The message indicated that RMAN had initiated the request on SBT channel to recall the remote backup files. Action: No action required. RMAN-08609: channel string: starting incremental datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08610: channel string: restoring datafile string to string Cause: This is an informational message only. Action: No action is required. RMAN-08611: channel string: piece handle=string tag=string Cause: This is an informational message only. Action: No action is required. RMAN-08612: channel string: failover to duplicate backup on device string Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the datafiles/archived logs/ control file/SPFILE using a previous existing backup. Action: See accompanying additional error messages indicating the cause of the failover. RMAN-08613: channel string: failover to piece handle=string tag=string Cause: This is an informational message to indicate the server found a corrupted block in a backup piece and had to switch to another copy of the piece to get the same block. Action: See alert log for information on corruption block(s) and the name of the backup piece that has the corrupted block(s). RMAN-08614: channel string: errors found reading piece handle=string Cause: This is an informational message to indicate the server found a corrupted block in a backup piece. Accompanying error will describe the action taken. Action: See alert log for more information. RMAN-08615: channel string Cause: This is an informational message to indicate the server could not perform the restore due to the included errors. A least recent backup set will be used to perform the restore. Action: See alert log for information on corruption block(s) and the name of the backup piece that has the corrupted block(s). RMAN-08616: validating blocks string through string Cause: This is an informational message only Action: No action is required. RMAN-08617: validation failed for foreign archived log Cause: The CROSSCHECK FOREIGN ARCHIVELOG command determined that the foreign archived log could not be found or no longer contained the same data, so its record was marked expired. Action: None - this is an informational message. RMAN-08618: validation succeeded for foreign archived log Cause: The CROSSCHECK FOREIGN ARCHIVELOG command determined that the foreign archived log still matches its data. Action: None - this is an informational message. RMAN-08619: foreign archived log file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08620: uncataloged foreign archived log Cause: This is an informational message only. Action: No action is required. RMAN-08621: deleted foreign archived log Cause: This is an informational message only. Action: No action is required. RMAN-10000: error parsing target database connect string "string" Cause: An invalid target connect string was supplied. Action: Specify a valid connect string and re-run the job. RMAN-10001: error parsing recovery catalog connect string "string" Cause: An invalid recovery catalog connect string was supplied. Action: Specify a valid connect string and re-run the job. RMAN-10002: ORACLE error: string Cause: The specified Oracle error was received. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-10003: unable to connect to target database Cause: Recovery manager was unable to connect to the target database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Ensure that that the target database is started, and that the connect string is valid. RMAN-10004: unable to connect to recovery catalog Cause: Recovery manager was unable to connect to the recovery catalog Action: Ensure that that the recovery catalog is started, and that the connect string is valid. This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-10005: error opening cursor Cause: An error was received while trying to open a cursor. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10006: error running SQL statement: string Cause: An error message was received while running the SQL statement shown. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10007: error closing cursor Cause: An error was received while trying to close a cursor. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10008: could not create channel context Cause: An error was received while trying create a channel context. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10009: error logging off of Oracle Cause: An error was received while disconnecting from Oracle. This message should be accompanied by other error message(s) indicating the cause of the error. Action: This is an informational message only. RMAN-10010: error while checking for RPC completion Cause: Recovery Manager's channel context had an error while checking to see if a remote procedure call had completed. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10011: synchronization error while polling for rpc number, action=string Cause: Recovery Manager could not synchronize properly with a remote procedure call. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10012: KGU error: string Cause: An error occurred while initializing the KGU subsystem Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10013: error initializing PL/SQL Cause: An error occurred while initializing the PL/SQL subsystem. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10014: PL/SQL error number on line number column number: string Cause: PL/SQL error Action: The text of this message will be issued by the PL/SQL subsystem. See the PL/SQL error message manual. RMAN-10015: error compiling PL/SQL program Cause: An error occurred while compiling a PL/SQL program. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10018: error cleaning up channel context Cause: An error was received during inter-step cleanup of a channel context. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10020: error initializing Recovery Manager execution layer Cause: An error was received while initializing the Recovery Manager execution layer in preparation for running a job. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10022: error in system-dependent sleep routine Cause: An error was received while waiting for a remote RPC to complete. The error occurred in the system-dependent sleep routine. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10023: RPC attempted to unrecognized package Cause: The Recovery Manager internal RPC router received a package name that it could not understand. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10024: error setting up for rpc polling Cause: The Recovery Manager could not create the RPC polling context which is required to test for RPC completion. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10025: connection is already registered for events Cause: The Recovery Manager could not enable the target database connection to test for RPC completion. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10026: network error number-number occurred registering connection Cause: An network error occurred while attempting to register the target database connection to test for RPC completion. Action: This is an internal error that should not be issued. The message numbers are issued by the Sql*Net layer. Contact Oracle Support. RMAN-10027: could not locate network layer context Cause: Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10028: network error number-number occurred during remote RPC Cause: An network error occurred while waiting for a remote RPC to complete. Action: This is an internal error that should not be issued. The message numbers are issued by the Sql*Net layer. Contact Oracle Support. RMAN-10029: unexpected return code number from PL/SQL execution Cause: PL/SQL returned an unexpected return code while executing one channel program. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10030: RPC call appears to have failed to start on channel string Cause: An RPC to a target database instance was issued, but was not observed to start within 5 timeouts. Action: This error is probably accompanied by other error messages giving the precise cause of the failure. RMAN-10031: RPC Error: ORA-number occurred during call to string.string Cause: An RPC to the target database or recovery catalog database encountered an error. Action: This error is accompanied with the error message from the server where the error occurred. RMAN-10032: unhandled exception during execution of job step number: string Cause: An unhandled PL/SQL exception occurred during a job step. Action: This error is accompanied by the error messages describing the exception. RMAN-10033: error during compilation of job step number: string Cause: PL/SQL detected a problem during the compilation of a job step Action: This error message is accompanied by the error messages describing RMAN-10034: unhandled exception during execution of job step number, error unknown Cause: PL/SQL detected an unhandled exception during execution of a job step, but no further information available Action: None RMAN-10035: exception raised in RPC: string Cause: A call to a remote package resulted in an exception. Action: The exception should indicate what went wrong. RMAN-10036: RPC call OK on channel string Cause: This is just an informational message. It should be preceded by message 10030. Action: No action is required. RMAN-10037: RPC anomaly detected on channel string, UPINBLT=number Cause: This is an debugging message and can be ignored. Action: No action is required. RMAN-10038: database session for channel string terminated unexpectedly Cause: The database connection for the specified channel no longer exists. Either the session was terminated by some external means or the channel terminated because of an internal error. Action: Check for an oracle trace file for detailed information on why the session terminated. RMAN-10039: error encountered while polling for RPC completion on channel string Cause: This error should be accompanied by other errors giving the cause of the polling error. Action: Check the accompanying errors. RMAN-10040: asynchronous support not detected, RMAN will run synchronously Cause: The database connection does not support asynchronous operation, so RMAN will not multi-task work among multiple channels. Multiple channels can still be allocated, but they will not run work concurrently. Action: Use a connection type that supports asynchronous operations. RMAN-10041: Could not re-create polling channel context following failure. Cause: The RPC polling context, which is required to test for RPC completion, failed and Recovery Manager could not re-create this channel. This message should be accompanied by other error messages indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-11000: message number number not found in recovery manager message file Cause: Recovery manager message file is out of date. Action: Make sure that the recovery manager error message file is current and installed in the correct location. RMAN-11001: Oracle Error: string Cause: This is an informational message only. Action: No action is required. RMAN-11002: could not open a cursor to the target database Cause: This is an informational message only. Action: No action is required. RMAN-11003: failure during parse/execution of SQL statement: string Cause: This is an informational message only. Action: No action is required. RMAN-11004: format requires %c when duplexing Cause: SET_DUPLEX=ON was specified, but %c was not part of the format. Action: Include %c in format, or use %U. RMAN-11005: conflicting media information for piece "string" Cause: While restoring the specified backup piece, RMAN received conflicting information about the physical location of the piece from the Media Management software. This can cause poor restore performance. Action: If RMAN does not parallelize the restore from all of the available channels, then you should contact the Media Management vendor. RMAN-11006: WARNING: test recovery results: string Cause: User called recover database with the test option Action: None required RMAN-12000: execution layer initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-12001: could not open channel string Cause: An ALLOCATE CHANNEL command could not be processed. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-12005: error during channel cleanup Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-12007: cannot allocate more than number channels Cause: The maximum number of RMAN channels has been exceeded. Note that one channel is reserved for RMAN. Action: Allocate fewer channels. Contact Oracle if you have a need for more channels in a single job. RMAN-12008: could not locate backup piece string Cause: There was at least 1 backup set that could not be accessed by any of the allocated channels. Action: Allocate additional channels on other nodes of the cluster RMAN-12009: command aborted because some backup pieces could not be located Cause: Same as 7008. Action: Refer to 7008. RMAN-12010: automatic channel allocation initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-12011: multiple records for default device type found in repository Cause: Configuration for default device type was not consistent. Action: Re-run CONFIGURE DEFAULT DEVICE TYPE command to set device type. RMAN-12012: multiple records for string parallelism found in repository Cause: Configuration for device parallelism was not consistent. Action: Re-run CONFIGURE PARALLELISM command for device to set parallelism. RMAN-12013: multiple records for string channel number found in repository Cause: Configuration for the channel was not consistent. Action: Re-run CONFIGURE CHANNEL command to configure this channel. RMAN-12014: multiple records for default channel configuration for string found in repository Cause: Configuration for the channel was not consistent. Action: Re-run CONFIGURE CHANNEL command to configure the channel. RMAN-12015: configuration for string channel number is ignored Cause: This is an informational message only. Parallelism for the device is less than associated channel number. Action: To use this configuration increase parallelism for this device. To clear this configuration use CONFIGURE CHANNEL... CLEAR command. RMAN-12016: using channel string Cause: This is an informational message only. Action: No action is required. RMAN-12017: could not locate pieces of backup set key string Cause: Copies of the specified backup set key could not be accessed on any of the allocated channels. Action: Allocate additional channels on other nodes of the cluster or, if the backup pieces has been deleted, use the CROSSCHECK BACKUP command to correct the recovery catalog or target database control file entries. RMAN-12018: channel string disabled, job failed on it will be run on another channel Cause: This is an informational message displayed whenever a retryable error occurs for the job and there are channels available to run this step. Action: No action is required. RMAN-12019: continuing other job steps, job failed will not be re-run Cause: This is an informational message displayed whenever there is a non-retryable error occurred for the job. Action: No action is required. RMAN-12020: error on step filtered for normal output string Cause: This message is added when stacking errors for failed jobs after channel failover was performed. It will be filtered from normal output. Action: No action is required. RMAN-20000: abnormal termination of job step Cause: A job step encountered an error and could not recover. This error should be followed by other errors indicating the cause of the problem. Action: Check the accompanying error. RMAN-20001: target database not found in recovery catalog Cause: target database is not found in the recovery catalog Action: make sure that the target database is registered in the recovery recovery catalog RMAN-20002: target database already registered in recovery catalog Cause: target database is already registered in the recovery catalog Action: if the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog. RMAN-20003: target database incarnation not found in recovery catalog Cause: RESETLOGS CHANGE# and/or time of the target database doesn't match any database incarnation in the recovery catalog. Action: if target database was opened with RESETLOGS option then use 'reset database' to register the new incarnation. RMAN-20004: target database name does not match name in recovery catalog Cause: name of the target database doesn't match the one stored in the recovery catalog Action: This is an internal error. RMAN-20005: target database name is ambiguous Cause: two or more databases in the recovery catalog match this name Action: None RMAN-20006: target database name is missing Cause: target database instance is not started or db_name initialization parameter is not set Action: startup the instance and make sure that db_name parameter is set RMAN-20009: database incarnation already registered Cause: this incarnation is already registered in the recovery catalog Action: No action is required. RMAN-20010: database incarnation not found Cause: database incarnation does not match any database incarnation in the recovery catalog Action: specify a valid database incarnation key RMAN-20011: target database incarnation is not current in recovery catalog Cause: the database incarnation that matches the RESETLOGS CHANGE# and time of the mounted target database control file is not the current incarnation of the database Action: If 'reset database to incarnation <key>' was used to make an old incarnation current then restore the target database from a backup that matches the incarnation and mount it. You will need to do 'STARTUP NOMOUNT' before you can restore the control file using RMAN. Otherwise use 'reset database to incarnation <key>' make the intended incarnation current in the recovery catalog. RMAN-20012: not authorized to register new database Cause: You attempted to register a new database with this recovery catalog, but you are using a virtual private catalog, and you have not been granted permission by the catalog administrator to register this database with this recovery catalog Action: Ask the catalog administrator to grant permission for you to register this database. RMAN-20013: error upgrading virtual private catalog Cause: An error occurred while automatically upgrading a virtual private catalog. Action: Ensure that the virtual private catalog userid has all of the required privileges, such as being granted the RECOVERY_CATALOG_OWNER role. RMAN-20014: virtual private catalog owner must be granted RECOVERY_CATALOG_OWNER role Cause: An attempt was made to establish a virtual private RMAN catalog in a schema that is not granted the RECOVERY_CATALOG_OWNER role. Action: Grant RECOVERY_CATALOG_OWNER to the virtual private catalog owner. RMAN-20015: not authorized to share this catalog Cause: You attempted to share a recovery catalog but were not authorized to do this by the catalog administrator. Action: Ask the catalog administrator to grant permission for you to share this catalog. RMAN-20016: virtual private catalog user cannot modify global scripts Cause: A virtual private catalog user attempted to create, delete, or modify a global script. Virtual private catalog users cannot modify global scripts. Action: Connect to the catalog owner userid and retry the global script operation. RMAN-20017: illegal script update operation Cause: An illegal script operation was performed. Action: None RMAN-20018: database not found in recovery catalog Cause: An attempt was made to grant or revoke catalog access to a database whose name was not registered in the recovery catalog. Action: Correct the database name and re-issue the GRANT or REVOKE command. If this is an attempt to grant or revoke access to a database that is not yet registered, then re-issue the command using the database ID of the desired database. RMAN-20019: database name not unique in recovery catalog Cause: An attempt was made to grant or revoke catalog access to a database whose name is not unique in the recovery catalog. Action: Re-issue the command specifying the database ID of the desired database. RMAN-20022: user not found Cause: An attempt was made to grant a privilege to a user that does not exist. Action: Reissue the command specifying a user that exists. RMAN-20029: cannot make a snapshot control file Cause: another operation that needs the snapshot control file is in progress Action: try again later if necessary RMAN-20030: resync in progress Cause: this procedure cannot be called while a resync is in progress Action: This is an internal error. RMAN-20031: resync not started Cause: this procedure can only be called in a resync Action: This is an internal error. RMAN-20032: checkpoint CHANGE# too low Cause: the checkpoint change# is less than the one of the previous resync or the checkpoint change# is null Action: make sure that the right control file is used RMAN-20033: control file SEQUENCE# too low Cause: the control file sequence is less than the one of the previous resync Action: make sure that the right control file is used RMAN-20034: resync not needed Cause: the control file has not changed since the previous resync Action: nothing since the recovery catalog is in sync RMAN-20038: must specify FORMAT for CONVERT command Cause: No FORMAT was specified when using CONVERT command. Action: Resubmit the command using FORMAT clause. RMAN-20039: format requires character when duplexing Cause: SET_DUPLEX=ON was specified, but %c was not part of the format. Action: Include %c in format, or use %U. RMAN-20045: must specify FORMAT for BACKUP INCREMENTAL FROM SCN command Cause: No FORMAT was specified when using BACKUP INCREMENTAL FROM SCN command. Action: Resubmit the command using FORMAT clause. RMAN-20079: full resync from primary database is not done Cause: Resync from standby detected that a full resync from primary database is required. One of the following events on primary database may have caused this error: 1) one or more tablespaces or datafiles were added 2) one or more tablespaces or datafiles were dropped 3) one or more datafiles status changed Action: Perform full resync after connecting to primary database. RMAN-20081: change stamp for the record Cause: A record with same recid and stamp is already known to catalog. Action: None. This error is automatically handled by RMAN client by changing the stamp in control file during resync. RMAN-20108: control file for remote database cannot be updated Cause: RESYNC CATALOG FROM DB_UNIQUE_NAME command was attempted, but the control file at the database with DB_UNIQUE_NAME needs to be resynced directly instead of through the current target. Action: Directly connect as target to the remote database with the specified DB_UNIQUE_NAME and resync. RMAN-20109: remote database has different database ID Cause: Command RESYNC CATALOG FROM DB_UNIQUE_NAME was executed and the database ID of the remote database was different than the connected target database. Action: The remote database should have the same database ID as the database connected as the target database. Fix the connect identifier for the remote database and retry the command. RMAN-20201: datafile not found in the recovery catalog Cause: The specified datafile is not found in the recovery catalog Action: make sure that the datafile name is correct and that the recovery catalog is up-to-date RMAN-20202: Tablespace not found in the recovery catalog Cause: the specified tablespace is not found in the recovery catalog Action: make sure that the tablespace name is correct and that the recovery catalog is up-to-date RMAN-20203: translation in progress Cause: this procedure can not be called when name translation is in progress Action: This is an internal error. RMAN-20204: translation not started Cause: GETDATAFILE procedure was called before TRANSLATETABLESPACE Action: This is an internal error. RMAN-20205: incomplete UNTIL clause Cause: The sequence# was NULL Action: This is an internal error. RMAN-20206: log sequence not found in the repository Cause: The specified log sequence does not exists in log history of the current database incarnation Action: check the thread# and sequence# RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time Cause: UNTIL TIME and RECOVERY WINDOW cannot be less than the database creation time or RESETLOGS time. Action: Check the UNTIL TIME or RECOVERY WINDOW. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20208: UNTIL CHANGE is before RESETLOGS change Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change. Action: Check the UNTIL CHANGE. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20209: duplicate datafile name Cause: Two datafiles have the same name Action: This is an internal error. RMAN-20211: FROM TIME is before RESETLOGS time Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time. Action: Check the FROM TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20212: UNTIL CHANGE is an orphan incarnation Cause: Specified UNTIL CHANGE was an orphan incarnation. Action: Check the UNTIL CHANGE or UNTIL RESTORE POINT. If the database needs to be restored or flashed back to an orphan incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20215: backup set not found Cause: The specified backup set key was not found in the recovery catalog or target database control file. Action: Specify a different backup set key. RMAN-20217: datafile not part of the database Cause: the datafile does not exists or did not exist at until time/scn Action: check the datafile name or number. This is an internal error. for restore database or tablespace. RMAN-20218: datafile not found in repository Cause: This is an internal error. Action: Contact Oracle Support Services. RMAN-20220: control file copy not found in the repository Cause: The specified control file was not in the recovery catalog or target database control file or it was marked deleted. Action: check the file name RMAN-20221: ambiguous control file copy name Cause: more than one control file copy in the recovery catalog match the specified name. Action: None RMAN-20222: datafile name not found in recovery catalog or is ambiguous Cause: The specified datafile name is not the name of a datafile that is currently part of the target database, or an UNTIL clause has been specified and the file name was for a different datafile at the time specified by the UNTIL clause than it is now. Action: Use a datafile number to specify the datafile you want to RESTORE or RECOVER. RMAN-20223: DB_UNIQUE_NAME mismatch in snapshot control file Cause: The DB_UNIQUE_NAME value in the snapshot control file was incorrect. This error can occur in Oracle RAC when the snapshot control file location is not shared across nodes and virtual IPs are setup in the remote database from where resynchronization is done using RESYNC CATALOG FROM DB_UNIQUE_NAME commnad. Action: To avoid this error, one of the following actions can be taken: 1) Share the control file snapshot location. The snapshot location can be displayed by executing SHOW SNAPSHOT CONTROLFILE NAME at the RMAN prompt. 2) Do not use Virtual IPs in the service name used to define the connect identifiers. The connect identifiers can be displayed using SHOW DB_UNIQUE_NAME command at the RMAN prompt. RMAN-20230: datafile copy not found in the repository Cause: The specified datafile was not in the recovery catalog or target database control file or it was marked deleted. Action: check the datafile copy name or key RMAN-20231: ambiguous datafile copy name Cause: more than one control file copy in the recovery catalog match the specified name. Action: use the datafile copy key to uniquely specify the datafile copy RMAN-20240: archived log not found in the repository Cause: The specified archived log was not found in the recovery catalog or target database control file or it was marked deleted. Action: check the archived log name or key RMAN-20241: ambiguous archived log name Cause: more than one archived log in the recovery catalog match the specified name Action: use the archived log key to uniquely specify the archived log RMAN-20242: specification does not match any archived log in the repository Cause: No archived logs found that match specification in the recovery catalog or target database control file. Action: check the archived log specifier RMAN-20243: database db_unique_name is not known to the recovery catalog Cause: the user specified DB_UNIQUE_NAME not known to the recovery catalog. Action: change the database DB_UNIQUE_NAME to a known database value. To display list of known db_unique_names execute LIST DB_UNIQUE_NAME OF DATABASE RMAN-20244: can not change currently connected database db_unique_name Cause: the user specified currently connected DB_UNIQUE_NAME value to unregister. Action: use the DB_UNIQUE_NAME other than connected target database's DB_UNIQUE_NAME value. RMAN-20245: can not specify db_unique_name option in nocatalog mode Cause: the user specified DB_UNIQUE_NAME in nocatalog mode. Action: remove the DB_UNIQUE_NAME option from the command. RMAN-20246: new db_unique_name is already known to the recovery catalog Cause: the user specified known DB_UNIQUE_NAME value when renaming a DB_UNIQUE_NAME in the recovery catalog. Action: change the database DB_UNIQUE_NAME to an known DB_UNIQUE_NAME value; or unregister the new DB_UNIQUE_NAME before renaming an old DB_UNIQUE_NAME value for a database. To display the list of all DB_UNIQUE_NAME for the databases LIST DB_UNIQUE_NAME OF DATABASE command can be executed. RMAN-20247: specification does not match any foreign archived log in the repository Cause: No foreign archived logs found that match specification in the recovery catalog or target database control file. Action: check the foreign archived log specifier RMAN-20250: offline range not found in the repository Cause: The specified offline was not found in the recovery catalog or target database control file. Action: check that recovery catalog is current RMAN-20260: backup piece not found in the repository Cause: The specified backup piece was not in the recovery catalog or target database control file or it was marked deleted. Action: check the backup piece handle or key RMAN-20261: ambiguous backup piece handle Cause: more than one backup piece in the recovery catalog match the specified handle Action: use the backup piece key to uniquely specify the backup piece RMAN-20272: no parent backup found for the incremental backup Cause: no available backup or copy that could be used as the parent of the incremental backup was found in the recovery catalog. Action: take a level 0 backup or copy of the datafile first RMAN-20280: too many device types Cause: more than 8 device types were allocated Action: make sure that the job allocates at most 8 different device types RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVCAT package. Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version. RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVMAN package. Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version. RMAN-20310: proxy copy not found in the repository Cause: The specified proxy copy was not in the recovery catalog or target database control file or it was marked deleted. Action: check the proxy copy handle or key RMAN-20311: ambiguous proxy copy handle Cause: more than one proxy copy in the recovery catalog matches the specified handle Action: use the proxy copy key to uniquely specify the proxy copy RMAN-20401: script already exists Cause: a CREATE SCRIPT was issued, but a script with the specified name already exists. Action: use a different name or use REPLACE SCRIPT. RMAN-20501: redo logs from parent database incarnation cannot be applied Cause: A RESTORE or RECOVER of a datafile was requested, but recovery of the datafile would require applying redo logs that were generated before the most recent OPEN RESETLOGS. Action: If a full backup or datafile copy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified. RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK Cause: A DELETE EXPIRED command was run, but the object was actually found to exist. This means the recovery catalog or target database control file is out of sync with reality. Action: Run CROSSCHECK. RMAN-20503: DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED Cause: A DELETE command was run without EXPIRED option, but the object doesn't exist. This means the recovery catalog or target database control file is out of sync with reality. Action: Run CROSSCHECK. RMAN-20504: corruption list not found in recovery catalog Cause: corruption list is empty Action: make sure that one or more blocks are marked corrupted in v$copy_corruption and v$backup_corruption and recovery catalog is up-to-date. RMAN-20505: create datafile during recovery Cause: applying of archived log caused a create datafile redo-entry to to terminate recovery. Action: none. This message is never displayed. RMAN automatically detects this case and creates the datafile. RMAN-20506: no backup of archived log found Cause: during the recover process, no backup was found from which the archived logs could be restored. Action: this message should be followed by a list of missing archived logs. Please make the necessary archived log backups available and try again. RMAN-20507: some targets are remote - aborting restore Cause: during the restore process, one or more backup files were unavailable locally for the restore operation. Action: This message should be accompanied with the list of remote backup files. Recall these backups from remote location and retry the RESTORE command. RMAN-20508: temporary resource already in use Cause: Temporary resource that was allocated for IMPORT CATALOG command was already in use. Action: Retry IMPORT CATALOG command. RMAN-20509: temporary resource not found Cause: Temporary resource that was allocated for IMPORT CATALOG command was not found. Action: Retry IMPORT CATALOG command. RMAN-20510: database not found in source recovery catalog database Cause: Database that was specified in IMPORT CATALOG command was not found in the source recovery catalog database. Action: Make sure that the database is registered in the source recovery catalog database. RMAN-20511: database name is ambiguous in source recovery catalog database Cause: Two or more databases in the source recovery catalog database match this name. Action: Use DBID option in IMPORT CATALOG command to specify the source database. RMAN-20512: source database already registered in recovery catalog Cause: Source database was already registered in the recovery catalog. Action: If the source database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog. RMAN-00550 to RMAN-20512 RMAN-00550: parser package failed to load Cause: lpmloadpkg() return an error indication. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00551: initialization of parser package failed Cause: The parser package initialization routine returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00552: syntax error in command line arguments Cause: The arguments supplied to RMAN could not be parsed, or no arguments were supplied at all. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00553: internal recovery manager package failed to load Cause: lpmloadpkg() return an error indication. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00554: initialization of internal recovery manager package failed Cause: The internal package initialization routine returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00555: target database connect string must be specified Cause: The TARGET parameter was not specified. Action: Supply the necessary parameter. RMAN-00556: could not open CMDFILE "string" Cause: An error occurred when trying to open the file. Action: Check that the file name was specified correctly and that the file exists and that the user running RMAN has read permission for the file. RMAN-00557: could not open MSGLOG "string" Cause: An error occurred when trying to open the file. Action: Check that the file name was specified correctly and that the file exists and that the user running RMAN has write permission for the file. RMAN-00558: error encountered while parsing input commands Cause: The parser detected a syntax error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00562: username too long Cause: The specified user name exceeds the maximum allowable username length. Action: Correct the username. RMAN-00563: password too long Cause: The specified password exceeds the maximum allowable password length. Action: Correct the password. RMAN-00564: host data too long Cause: The SQL*NET host connect string exceeds the maximum allowable length. Action: Correct the host string. RMAN-00565: unable to read input file Cause: An error occurred while trying to read from STDIN or from the CMDFILE. Action: Ensure that the cmdfile is readable. The cmdfile must be a text file with 1 line per record. RMAN-00566: could not open TRACE "string" Cause: An error occurred when trying to open the file. Action: Check that the file name was specified correctly and that the user running RMAN has write permission for the file. RMAN-00567: Recovery Manager could not print some error messages Cause: An error occurred while trying to print the error message stack. Action: If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-00568: user interrupt received Cause: The user typed ^C or ATTN. Action: No action is required. RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== Cause: This message precedes an error message stack. Action: The errors are printed in last-in first-out order. To interpret them correctly, read from the bottom to the top. RMAN-00570: **end-of-file** Cause: The end of an inline cmdfile was reached. This is just an informational message. Action: No action is required. RMAN-00571: =========================================================== Cause: Displayed to highlight the error message stack. Action: The errors are printed in last-in first-out order. To interpret them correctly, read from the bottom to the top. RMAN-00572: waiting for DBMS_PIPE input Cause: This message is used only when the PIPE option was specified. Action: enqueue some RMAN input into the pipe RMAN-00573: DBMS_PIPE.NEXT_ITEM_TIME returned unknown type code: number Cause: This is an internal error. Action: contact Oracle Customer Support. RMAN-00574: rman aborting due to errors reading/writing DBMS_PIPE Cause: RMAN was run with input/output being sent to DBMS_PIPE. An error was encountered while reading from or writing to the pipe. This error should be preceded by information describing the error. Action: RMAN terminates. Refer to the cause/action for the preceding errors. RMAN-00575: timeout while trying to write to DBMS_PIPE Cause: d by death of the process that was talking to rman. Action: RMAN will abort. RMAN-00576: PIPE cannot be used with CMDFILE Cause: The PIPE and CMDFILE options cannot be used together. When using the PIPE option, RMAN must obtain its input from the input pipe. Action: Remove either the PIPE or CMDFILE option. RMAN-00577: PIPE requires that TARGET be specified on the command line Cause: The PIPE option obtains its input from, and writes its output to, an Oracle database pipe in the target database. Therefore, the target database connection must be specified on the command line, so that RMAN can connect to the target database to receive its input from the pipe. Action: Specify the TARGET option on the RMAN command line. RMAN-00578: pipe string is not private and owned by SYS Cause: The pipe that RMAN needs to use for its input or output is either a public pipe or a private pipe that is not owned by SYS. This is a potential security problem, because it allows a non-SYS user to issue commands to RMAN or to retrieve the RMAN output. Action: If you are attempting to put data on the RMAN input pipe prior to starting RMAN, so RMAN will process the data on the pipe as soon as it starts, you must be connected as SYS and you must first use the DBMS_PIPE.CREATE_PIPE function to explicitly create the pipe as a private pipe. RMAN-00579: SCRIPT cannot be used with CMDFILE Cause: The SCRIPT and CMDFILE options cannot be used together. When using the SCRIPT option, RMAN executes only the specified script. Action: Remove either the SCRIPT or CMDFILE option. RMAN-00600: internal error, arguments [string] [string] [string] [string] [string] Cause: An internal error in recovery manager occurred. Action: Contact Oracle Customer Support. RMAN-00601: fatal error in recovery manager Cause: A fatal error has occurred. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-00700: SCRIPT requires that TARGET be specified on the command line Cause: A SCRIPT option was included on the RMAN command line without a specified TARGET database. Action: Specify the TARGET option on the RMAN command line. RMAN-00701: SCRIPT requires that CATALOG be specified on the command line Cause: A SCRIPT option was included on the RMAN command line without a specified CATALOG recovery catalog. Action: Specify the CATALOG option on the RMAN command line. RMAN-00702: The command has no syntax errors Cause: This is an informational message only. Action: No action is required. RMAN-00703: The cmdfile has no syntax errors Cause: This is an informational message only. Action: No action is required. RMAN-01006: error signaled during parse Cause: An error was signaled during parsing. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-01007: at line number column number file: string Cause: This is an informational message indicating the line and column where a syntax error was detected. Action: No action is required. RMAN-01008: the bad identifier was: string Cause: This is an informational message indicating the identifier token that caused a syntax error. Action: No action is required. RMAN-01009: syntax error: found "string": expecting one of: "string" Cause: A syntax error was signaled during parsing. Action: Correct the input. RMAN-02000: wrong message file version (msg number not found) Cause: The rmanxx.msb file is not the correct version. Action: Check that the installation was done correctly. The RMAN binary (executable, load module, whatever it is called on your O/S) and the rmanxx.msb file must be from the same version, release, and patch level. RMAN-02001: unrecognized punctuation symbol "string" Cause: An illegal punctuation character was encountered. Action: Remove the illegal character. RMAN-02002: unexpected end of input file reached Cause: This is probably caused by failure to supply the closing quote for a quoted string. Action: Correct the input. RMAN-02003: unrecognized character: string Cause: An input character that is neither an alpha, digit, or punctuation was encountered. Action: Remove the character. RMAN-02004: quoted string too big Cause: A quoted string longer than 2000 bytes was encountered. Action: This may be caused by a missing close quote. If so, add the missing quote, otherwise shorten the string. RMAN-02005: token too big Cause: A token longer than 1000 bytes was encountered Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token. RMAN-02006: script line too long Cause: a line longer than 500 bytes was encountered Action: break the line up into shorter lines RMAN-02007: Integer value overflow Cause: Parser failed to convert input string to integer Action: Acceptable values for integer are from 0 to 2147483648. Retry command using valid integer value. RMAN-02008: no value exists for variable "string" Cause: The RMAN variable specified was either undefined or null Action: Verify that a proper value has been given to that variable. RMAN-03000: recovery manager compiler component initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03001: recovery manager command sequencer component initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03002: failure of string command at string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03003: command not implemented yet: string Cause: The command is not implemented in the current release. Action: Avoid using the command. RMAN-03004: fatal error during execution of command Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03008: error while performing automatic resync of recovery catalog Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03009: failure of string command on string channel at string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03010: fatal error during library cache pre-loading Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-03011: Recovery Managerstring Cause: This is the RMAN banner Action: No action is required. RMAN-03012: fatal error during compilation of command Cause: A fatal error occurred during compilation of a command. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-03013: Copyright (c) 1995, 2003, Oracle Corporation. All rights reserved. Cause: This is the copyright banner Action: No action is required. RMAN-03014: implicit resync of recovery catalog failed Cause: of the failure. Action: No action is required. RMAN-03015: error occurred in stored script string Cause: This is an informational message only. Action: No action is required. RMAN-03017: recursion detected in stored script string Cause: A stored script is calling itself or another script which calls itself. Action: Remove the recursion. RMAN-03018: asynchronous RPCs are working correctly Cause: This is an informational message only. Action: No action is required. RMAN-03019: asynchronous RPCs are NOT working Cause: The RPCTEST command has determined that RPCs are not executing asynchronously. Instead, they are blocking. This is caused by using a SQL*NET driver that does not support non-blocking UPI. Action: Try using a different SQL*NET driver. RMAN-03020: asynchronous RPC test will take 1 minute Cause: This is an informational message only. Action: No action is required. RMAN-03023: executing command: string Cause: This is an informational message only. Action: No action is required. RMAN-03028: fatal error code for command string : number Cause: Informational message. This precedes error 3012. Action: No action is required. RMAN-03029: echo set on Cause: a SET ECHO ON command was issued Action: No action is required. RMAN-03030: echo set off Cause: a SET ECHO OFF command was issued Action: No action is required. RMAN-03031: this option of set command needs to be used inside a run block Cause: The option used with the SET command is not valid outside a run block. Action: Change the SET command or place it inside a run block. RMAN-03032: this option of set command needs to be used outside of a run block Cause: The option used with the SET command is not valid inside of a run block. Action: Change the SET command or place it outside a run block. RMAN-03033: current log archived Cause: "ALTER SYSTEM ARCHIVE LOG CURRENT" command completed successfully. Action: None, this is an informational message. RMAN-03034: LEVEL number is invalid. LEVEL must be between string and string Cause: An invalid DEBUG LEVEL was used. Action: Change the DEBUG LEVEL argument. RMAN-03035: Debugging turned off Cause: a DEBUG OFF command was issued Action: No action is required. RMAN-03036: Debugging set to level=number, types=string Cause: a DEBUG command was issued Action: No action is required. RMAN-03037: Spooling started in log file: string Cause: a SPOOL LOG TO ... command was issued Action: No action is required. RMAN-03038: Spooling started in trace file: string Cause: a SPOOL TRACE TO ... command was issued Action: No action is required. RMAN-03039: Spooling for log turned off Cause: a SPOOL LOG OFF command was issued Action: No action is required. RMAN-03040: Spooling for trace turned off Cause: a SPOOL TRACE TO ... command was issued Action: No action is required. RMAN-03042: error while analyzing automatic repair options Cause: of the failure. Action: No action is required. RMAN-03090: Starting string at string Cause: This is an informational message only. Action: No action is required. RMAN-03091: Finished string at string Cause: This is an informational message only. Action: No action is required. RMAN-03098: stringRMAN-number: stringstring Cause: This is the message prefix with a possible indentation. Action: No action is required. RMAN-03099: job cancelled at user request Cause: The user interrupted the current job. Action: None RMAN-03999: Oracle error occurred while while converting a date: ORA-number: string Cause: Internal error converting a date. Action: Contact Oracle Customer Support. RMAN-04000: memory allocation failure Cause: A memory allocation request could not be satisfied. Action: Increase the amount of memory available to RMAN. RMAN-04001: heap initialization failure Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04002: OCIPI failed, ORA-string Cause: OCI process level initialization failed. Action: This error should not normally occur. RMAN-04003: OCIINIT failed Cause: The call to OCIEnvInit failed. Action: This error should not normally happen. Contact Oracle Customer Support. RMAN-04004: error from recovery catalog database: string Cause: Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04005: error from target database: string Cause: Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04006: error from auxiliary database: string Cause: Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04007: WARNING from recovery catalog database: string Cause: Non fatal Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04008: WARNING from target database: string Cause: Non fatal Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04009: WARNING from auxiliary database: string Cause: Non fatal Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04010: target database Password: Cause: No password was provided for the target database. Action: Provide target database password. RMAN-04011: recovery catalog database Password: Cause: No password was provided for the recovery catalog database. Action: Provide recovery catalog database password. RMAN-04012: auxiliary database Password: Cause: No password was provided for the auxiliary database. Action: Provide auxiliary database password. RMAN-04013: must connect before startup Cause: A STARTUP command was attempted before connecting to the database. Action: Connect to database before attempting STARTUP command. RMAN-04014: startup failed: string Cause: The database failed to startup. Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the startup command. RMAN-04015: error setting target database character set to string Cause: An error was received while setting the session character set in the target database. Action: This error should not normally happen. Contact Oracle Customer Support. RMAN-04016: could not get OCI error handle Cause: An error was received while initializing the OCI layer. Action: This error should not normally happen. Contact Oracle Customer Support. RMAN-04017: startup error description: string Cause: of failure. Action: No action is required. RMAN-04020: target database name "string" does not match channel's name: "string" Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database. Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command. RMAN-04021: target database DBID string does not match channel's DBID string Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database. Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command. RMAN-04022: target database mount id string does not match channel's mount id string Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database. Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command. RMAN-04024: starting Oracle instance without parameter file for retrieval of spfile Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters. Action: None - this is an informational message. RMAN-04025: unable to generate a temporary file Cause: Creation of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar). Action: Verify and free some system resources memory and try again. RMAN-04026: unable to open a temporary file: "string" Cause: Opening of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar). Action: Verify and free some system resources memory and try again. RMAN-04027: unable to write to a temporary file: "string" Cause: Writing to a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar). Action: Verify and free some system resources memory and try again. RMAN-04031: initialization parameters used for automatic instance: string Cause: This is an informational message only. Action: No action is required. RMAN-04032: using contents of file string Cause: The specified file was included as part of the auxiliary database parameter file. This is an informational message. Action: No action is required. RMAN-04033: cannot open auxiliary parameter file string Cause: An auxiliary parameter file was specified with SET AUXILIARY INSTANCE PARAMETER FILE command but the specified file cannot be found. Action: Set the parameter file to an existent file or retry the command without setting AUXILIARY INSTANCE PARAMETER FILE. RMAN-04034: source recovery catalog database Password: Cause: A password was not provided for the source recovery catalog database. Action: Provide source recovery catalog database password. RMAN-04035: error from source recovery catalog database: string Cause: Oracle error signaled by source recovery catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-04036: WARNING from source recovery catalog database: string Cause: Nonfatal Oracle error signaled by source recovery catalog database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-05000: CONFIGURE AUXNAME required for datafile string Cause: Either: -) The control file mounted by the auxiliary database does not have an entry for this datafile, therefore file name conversion is not possible. -) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this datafile. Action: Use the CONFIGURE AUXNAME command to specify a file name that the auxiliary database can use as a restore destination. RMAN-05001: auxiliary file name string conflicts with a file used by the target database Cause: RMAN is attempting to use the specified file name as a restore destination in the auxiliary database, but this name is already in use by the target database. Action: Use the CONFIGURE AUXNAME command to specify a name for the data file that does not conflict with a file name in use by the target db. RMAN-05002: aborting Tablespace Point-in-Time Recovery Cause: Previously encountered error(s) were issued which require corrective action. Action: Resolve the error conditions, and then re-issue the RECOVER command. RMAN-05003: Tablespace Point-in-Time Recovery is not allowed for tablespace string Cause: The SYSTEM tablespace or a tablespace containing rollback segments is not allowed in Tablespace Point-in-Time Recovery. Action: Remove the indicated tablespace from the recovery set and retry the operation. RMAN-05004: target database log mode is NOARCHIVELOG Cause: An attempt was made to apply Tablespace Point-in-Time Recovery to a database that is in NOARCHIVELOG mode. Action: If all required archived log files are available for Tablespace Point-in-Time Recovery, alter the target database log mode to ARCHIVELOG and retry the Tablespace Point-in-Time Recovery operation. Otherwise, Tablespace Point-in-Time Recovery cannot be applied to this database. RMAN-05005: Tablespace Point-in-Time Recovery is not allowed for re-created tablespace string Cause: The requested tablespace has been re-created and is not allowed in Point-in-Time Recovery. Action: Remove the indicated tablespace from the recovery set and retry the operation. RMAN-05006: cannot recover clone standby single tablespaces Cause: Standby recover can only be performed for the whole database. Action: Change the tablespace list to a database specification. RMAN-05007: no channel allocated Cause: A command was entered that requires a channel, and no channel is allocated. Action: Use ALLOCATE CHANNEL before using the command RMAN-05008: SET NEWNAME TO NEW not allowed (datafile string) Cause: SET NEWNAME ... TO NEW is not allowed with Tablespace Point-in-Time Recovery. Action: Set the new name to a specific file name and retry. RMAN-05009: Block Media Recovery requires Enterprise Edition Cause: The RECOVER...BLOCK command was specified. Action: Remove the RECOVER...BLOCK command. RMAN-05010: target database must be opened in READ WRITE mode for Tablespace Point-in-Time Recovery Cause: The target database was not opened in read write mode. Action: Open the database in read write mode. RMAN-05011: auxiliary instance must be in NOMOUNT state for Tablespace Point-in-Time Recovery Cause: The Auxiliary instance was not in NOMOUNT state. Action: Open the auxiliary instance in NOMOUNT state. RMAN-05012: trying to start the Oracle instance without parameter files ... Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters. Action: None - this is an informational message. RMAN-05013: auxiliary control file name string conflicts with a file used by the target database Cause: RMAN is attempting to use the specified control file name for Tablespace Point-in-Time Recovery as a restore destination in the auxiliary database, but this name is already in use by the target database. Action: Set control_files parameter in the auxiliary instance to a name that does not conflict with a file name in use by the target database. RMAN-05014: Tablespaces with undo segments were not found in recovery catalog Cause: The recovery catalog did not have information about tablespaces with undo segments. Action: Manually specify the tablespaces with undo segments in the optional UNDO tablespaces clause of the RECOVER command. RMAN-05015: WARNING: not enough information in recovery catalog for specified point in time recovery Cause: The recovery catalog did not have information about the tablespaces with undo segments at the specified Point-in-Time. This happened because the current recovery catalog was not in use at the specified Point-in-Time. A list of tablespaces with undo segments was supplied. Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces. RMAN-05016: failover to previous backup Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the datafile/archived logs/ control file/SPFILE using a previous existing backup. Action: See accompanying additional error messages indicating the cause of the failover. RMAN-05017: no copy of datafile number found to recover Cause: A RECOVER COPY command was not able to proceed because no copy of indicated file was found to recover. Possible causes include the following: 1. no copy of indicated file exists on disk that satisfy the criteria specified in the user's recover operands. 2. copy of indicated datafile exists on disk but no incremental backup was found to apply to the datafile copy. Action: One of the following: 1. Use or correct TAG specification to recover a different datafile copy. 2. Use BACKUP FOR RECOVER OF COPY command to create necessary incremental backup or copy. RMAN-05018: some datafile copies cannot be recovered, aborting the RECOVER command Cause: This error message can follow one or more RMAN-5017 or RMAN-5019 error messages. Action: See RMAN-5017 or RMAN-5019 error messages documentation for more information. RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile number Cause: A RECOVER COPY command could not proceed because incremental backup sets exist on a device type that has not been allocated. Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type. RMAN-05020: cannot specify AUXILIARY DESTINATION option for normal recovery Cause: The AUXILIARY DESTINATION option was specified for a normal recovery. It is only allowed for Tablespace Point-in-Time Recovery. Action: Remove the AUXILIARY DESTINATION option and re-run the RECOVER command. RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file Cause: The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY. The following configurations can be changed only when connected to primary database instance that has CURRENT/CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ENCRYPTION CONFIGURE DB_UNIQUE_NAME Action: Connect to primary database instance and execute the command. RMAN-05022: TRANSPORT TABLESPACE may not be used with user-managed auxiliary instance Cause: A user-managed auxiliary instance was specified. Action: Retry the operation with an RMAN-managed auxiliary instance. RMAN-05023: TABLESPACE DESTINATION required Cause: A required TABLESPACE DESTINATION was not specified. Action: Specify a TABLESPACE DESTINATION and retry the operation. RMAN-05024: List of tablespaces presumed to have UNDO segments Cause: Accompanying message to 5015. Action: See action of message 5015. RMAN-05025: Tablespace string Cause: Accompanying message to 5015. Action: See action of message 5015. RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point in time Cause: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces. Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified Point-in-Time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACE clause of the RECOVER command to specify the correct set of tablespaces. RMAN-05027: List of tablespaces expected to have UNDO segments Cause: Accompanying message to 5026. Action: See action of message 5026. RMAN-05028: Tablespace string Cause: Accompanying message to 5026. Action: See action of message 5026. RMAN-05029: UNDO TABLESPACE clause is only valid for Tablespace Point-in-Time Recovery Cause: The UNDO TABLESPACE clause was specified for non-Tablespace Point-in-Time Recovery. Action: Remove the UNDO TABLESPACE clause. RMAN-05030: CLONE clause cannot be used with Tablespace Point-in-Time Recovery Cause: The CLONE clause was specified for a Tablespace Point-in-Time Recovery. Action: Remove the CLONE clause. RMAN-05031: cannot specify UNDO TABLESPACE clause for normal recovery Cause: The UNDO TABLESPACE clause was specified for a normal recovery. It is only allowed for Tablespace Point-in-Time Recovery. Action: Remove the UNDO TABLESPACE clause and re-run the RECOVER command. RMAN-05032: datafile string will be created automatically during restore operation Cause: The specified datafile did not have an available backup. Action: None. This is an informational message displayed for VALIDATE or PREVIEW option of the RESTORE command. RMAN-05033: Media recovery start SCN is string Cause: The above SCN would be starting media recovery SCN, if the specified files are restored. Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command. RMAN-05034: Recovery must be done beyond SCN string to clear datafile fuzziness Cause: The above SCN identifies the minimum SCN beyond which the media recovery must be performed on the specific datafile to clear the media recovery fuzziness for all datafile. Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command. RMAN-05035: archived logs generated after SCN string not found in repository Cause: The repository did not have a record of archived logs containing the redo generated after the specified SCN. Action: None. To avoid this message, perform a log switch if the database is in open mode. RMAN-05036: FOR DB_UNIQUE_NAME option cannot be used for this configuration Cause: An attempt was made to set the configuration which cannot be used with FOR DB_UNIQUE_NAME option. Action: Remove FOR DB_UNIQUE_NAME option and execute the command. RMAN-05037: FOR DB_UNIQUE_NAME option cannot be used in nocatalog mode Cause: An attempt was made to set the remote configuration in nocatalog mode. Action: Connect to recovery catalog and execute the command. RMAN-05040: List of tablespaces that have been dropped from the target database: Cause: One or more tablespaces in the recovery set were not found in the control file of the target database. Action: None. Informational message. RMAN-05041: Error during export of metadata Cause: Export of metadata received an error from DATAPUMP. Action: This message is accompanied by other error message(s) indicating the cause of the error. RMAN-05042: Error during import of metadata Cause: Import of metadata received an error from DATAPUMP. Action: This message is accompanied by other error message(s) indicating the cause of the error. RMAN-05043: Tablespace string Cause: Accompanying message to 5040. Action: See Action of message 5040. RMAN-05044: Performing export of metadata... Cause: This is an informational message only. Action: No action is required. RMAN-05045: Performing import of metadata... Cause: This is an informational message only. Action: No action is required. RMAN-05046: Export completed Cause: This is an informational message only. Action: No action is required. RMAN-05047: Import completed Cause: This is an informational message only. Action: No action is required. RMAN-05048: specified file name string conflicts with a file used by the target database Cause: The specified file name was already in use by another datafile in the database. Action: Use SET NEWNAME command to specify a different name for the datafile that does not conflict with a file name in use by the target database. RMAN-05049: datafile string is an Oracle Managed File, DB_CREATE_FILE_DEST not set at target Cause: A Tablespace Point-in-Time Recovery was attempted but the datafile is an Oracle Managed File and DB_FILE_CREATE_DEST is not currently set for the target database. Action: Specify DB_FILE_CREATE_DEST for the target database or provide a NEWNAME for the specified datafile. RMAN-05051: analyzing automatic repair options; this may take some time Cause: This is an informational message only. Action: No action is required. RMAN-05052: Repair string is not compatible with this version of RMAN. Cause: The specified repair was not compatible with this version of Recovery Manager (RMAN). Action: Use a newer version of the RMAN executable. RMAN-05053: Do you really want to execute the above repair (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-05054: recover block operand string cannot be used to recover datafile Cause: The specified operand could not be used with RECOVER datafile command. Action: Delete the invalid operand and retry the command. RMAN-05055: recover datafile operand string cannot be used to recover block Cause: The specified operand could not be used with RECOVER block command. Action: Delete the invalid operand and retry the command. RMAN-05057: Do you want to open the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-05058: Do you want to open resetlogs the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-05060: block specifier must be specified to recover block Cause: Block Specifier was not specified in the command. Action: Specify block specifier and resubmit the command. RMAN-05061: analyzing automatic repair options complete Cause: This is an informational message only. Action: No action is required. RMAN-05062: image copy needs no roll forward Cause: The image copy that would be rolled forward by the RECOVER COPY command is already more recent than the specified UNTIL time or SCN. Action: Usually this is the result of a recent OPEN RESETLOGS operation, and no action is needed, because the daily backup strategy will start rolling this copy forward after it becomes old enough to be eligible for rolling forward. To force the copy to be rolled forward, specify a more recent UNTIL time or SCN. RMAN-05500: the auxiliary database must be not mounted when issuing a DUPLICATE command Cause: A DUPLICATE command was issued, but the auxiliary database is mounted. Action: Dismount the auxiliary database. RMAN-05501: aborting duplication of target database Cause: Previously encountered errors require corrective action. Action: Resolve the error conditions, and reissue the DUPLICATE command. RMAN-05502: the target database must be mounted when issuing a DUPLICATE command Cause: A DUPLICATE command was issued, but the target database control file is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-05503: at least one auxiliary channel must be allocated to execute this command Cause: No auxiliary channels were allocated. Action: Allocate an auxiliary channel. RMAN-05504: at least two redo log files or groups must be specified for this command Cause: Only one redo log file or group was specified Action: Specify at least one more redo log file or group RMAN-05505: auxiliary file name conversion of 'string' exceeds maximum length of string Cause: When the given file name is converted to the name used for the auxiliary database, the converted name is larger than the maximum allowed file name. Action: Change initialization parameter DB_FILE_NAME_CONVERT to convert to a valid file name. RMAN-05506: error during recursive execution Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-05507: standby control file checkpoint (string) is more recent than duplication point in time (string) Cause: A DUPLICATE FOR STANDBY command was issued, but the checkpoint of the control file is more recent than the last archived log or the specified point in time. Action: If an explicit point in time was specified, change it to be at least the control file checkpoint; otherwise archive (and backup/copy) the current log. RMAN-05510: Duplicate finished Cause: This is an informational message only. Action: No action is required. RMAN-05511: Datafile string skipped by request Cause: This is an informational message only. Action: No action is required. RMAN-05512: Tablespace string cannot be skipped from duplication Cause: The SYSTEM and SYSAUX tablespaces were not included in the DUPLICATE DATABASE. They must be present. Action: Remove the SYSTEM and/or SYSAUX tablespace from the SKIP list and retry the operation. RMAN-05513: cannot duplicate, control file is not current or backup Cause: DUPLICATE requires that the target database has a current control file. Action: Open the target database and retry operation. RMAN-05514: Tablespace string has undo information, cannot skip Cause: All tablespaces that have undo information must be included in the duplication. Action: Remove the specified tablespace from the SKIP list and retry the operation. RMAN-05515: Duplicate for standby does not allow the use of SET UNTIL Cause: A SET UNTIL clause was specified for the command. Action: Remove the SET UNTIL clause and try again. RMAN-05516: duplicate operand specified: string Cause: The specified operand appears more than once in the same DUPLICATE option list Action: Delete the duplicated operand. RMAN-05517: tempfile string conflicts with file used by target database Cause: RMAN attempted to use the specified tempfile as a restore destination in the auxiliary database, but this name was already in use by the target database. Action: Use the SET NEWNAME FOR TEMPFILE command to specify a name for the indicated tempfile, making sure that the new name does not conflict with a file name in use by target database. Alternatively, use DB_FILE_NAME_CONVERT and retry the command. RMAN-05518: Automatically adding tablespace string Cause: This is an informational message only. Action: No action is required. RMAN-05519: WARNING: tablespace string is always included when duplicating Cause: The SYSTEM and SYSAUX tablespaces were included in the DUPLICATE TABLESPACE command. They were automatically included by the command and did not need to be explicitly named. Action: To avoid this warning,, remove the SYSTEM and/or SYSAUX tablespace from the tablespaces list and retry the operation. RMAN-05520: database name mismatch, auxiliary instance has string, command specified string Cause: The database name specified in the initialization parameter was not the same as the database name provided in the DUPLICATE command. Action: Correct the database name in the command or adjust the database name of the auxiliary instance. RMAN-05521: WARNING: No undo tablespaces found. Will proceed assuming that list contains all necessary undo tablespaces. Cause: No information was found about tablespaces with undo segments Action: If TABLESPACE clause does not contain all tablespaces with undo segments, duplication might fail to open the database. RMAN-05522: Skipping tablespace string Cause: This is an informational message only. Action: No action is required. RMAN-05523: Tablespace string is read only and SKIP READONLY was specified Cause: Conflicting parameters were provided. Action: Remove SKIP READONLY or remove read-only tablespace from list of tablespaces to duplicate. RMAN-05524: Tablespace string is offline Cause: It was not possible to duplicate offline tablespaces. Action: Remove offline tablespace from list or online tablespace to duplicate it. RMAN-05525: SKIP TABLESPACE cannot be used when using DUPLICATE TABLESPACE Cause: A SKIP TABLESPACE clause was specified for the command. Action: Remove the SKIP TABLESPACE clause and try again. RMAN-05526: datafile number not processed because file is OFFLINE IMMEDIATE Cause: A DUPLICATE command omitted processing the indicated datafile because it is offline immediate. The tablespace to which this datafile belongs will also not be included. See message 5528. Action: None, informational message only. RMAN-05527: Tablespace string has one or more OFFLINE IMMEDIATE datafiles Cause: It was not possible to duplicate a tablespace who had offline immediate tablespaces. Action: Remove offending tablespace from list or recover datafile which are offline immediate in the tablespace before attempting the command again. RMAN-05528: datafile number not processed because file belongs to tablespace with one or more offline immediate datafile (string) Cause: A DUPLICATE command omitted processing the indicated datafile because it is part of a tablespace that has offline immediate datafile. See message 5526. Action: No action is required. This is an informational message only. RMAN-05529: WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only. Cause: It was not possible to convert ASM Oracle Managed Files names using DB_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead. Action: No action is required. This is an informational message only. If the automatic change is incorrect, use one of the following options instead of using DB_FILE_NAME_CONVERT for ASM Oracle Managed Files: 1) use RMAN command SET NEWNAME for each Oracle Managed File. 2) set DB_CREATE_FILE_DEST initialization parameter in auxiliary instance and not specify DB_FILE_NAME_CONVERT. RMAN-05530: an UNTIL TIME or SCN cannot be specified with FROM ACTIVE DATABASE Cause: A DUPLICATE with FROM ACTIVE DATABASE was specified along with either a SET UNTIL statment or UNTIL clause on the command. This is not supported. A DUPLICATE FROM ACTIVE DATABASE always creates a copy as of the current time. Action: Check the statement and remove the use of UNTIL. RMAN-05531: a mounted database cannot be duplicated while data files are fuzzy Cause: A DUPLICATE with FROM ACTIVE DATABASE command was specified while the database was mounted or open read-only. Unless the database is open read/write, the data files cannot be fuzzy. Action: Open the database read/write, then shutdown cleanly before mounting. RMAN-05532: PASSWORD FILE specified without FROM ACTIVE DATABASE Cause: The PASSWORD FILE clause of the DUPLICATE command was specified but the FROM ACTIVE DATABASE clause was not. A password file can only be duplicated if the FROM ACTIVE DATABSE clause has been used. Action: Remove the PASSWORD FILE clause from the command, or perform an online duplicate of the database by specifying the FROM ACTIVE DATABASE clause. RMAN-05533: string is not supported on string database Cause: The specified command is not supported on this type of database. The type of database can be STANDBY, CLONE, or RAC. Action: Do not use the specified command against this database. RMAN-05534: WARNING: LOG_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to disk group only. Cause: It was not possible to convert ASM Oracle Managed Files names using LOG_FILE_NAME_CONVERT parameter. RMAN changed these invalid names to the converted disk group name instead. Action: If the automatic change is incorrect, use one of the following options instead of using LOG_FILE_NAME_CONVERT for ASM Oracle Managed Files: 1) Use the LOGFILE clause for online log files. 2) After DUPLICATE completes, create standby log files using the SQL ALTER DATABASE ADD STANDBY LOGFILE command. RMAN-05535: WARNING: All standby logfiles were not created Cause: It was not possible to convert and create new standby logfiles. Action: If standby logfiles are desired, create them after DUPLICATE has completed using the ALTER DATABASE ADD STANDBY LOGFILE SQL command. RMAN-05536: auxiliary logfile name string conflicts with a file used by the target database Cause: RMAN attempted to use the specified logfile name as a standby redo log file in the auxiliary database, but this name was already in use by the target database. Action: Use or alter LOG_FILE_NAME_CONVERT so that unique logfile names can be generated. Or wait for the command to complete and create standby logfiles using the SQL ALTER DATABASE ADD STANDBY LOGFILE command. RMAN-06000: could not open recovery manager library file: string Cause: The "recover.bsq" file could not be opened. Action: Check that the file was installed correctly and that the user running RMAN has authority to read the file. RMAN-06001: error parsing job step library Cause: A syntax error was encountered while parsing "recover.bsq". Action: Ensure that the correct version of the file is installed and that it has not been modified in any way. RMAN-06002: command not allowed when not connected to a recovery catalog Cause: A command that is allowed only when a recovery catalog connect string was supplied was attempted. Action: Avoid using the command, or restart RMAN and supply a recovery catalog connect string via the CATALOG parameter. RMAN-06003: ORACLE error from target database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06004: ORACLE error from recovery catalog database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06005: connected to target database: string (DBID=string) Cause: This is an informational message only. Action: No action is required. RMAN-06006: connected to target database: string (not mounted) Cause: This is an informational message only. Action: No action is required. RMAN-06007: target database not mounted and db_name not set in init.ora Cause: The target database has not mounted the control file, and its "init.ora" file does not specify the DB_NAME parameter. Action: MOUNT the target database, or add the DB_NAME parameter to its "init.ora" and restart the instance. RMAN-06008: connected to recovery catalog database Cause: This is an informational message only. Action: No action is required. RMAN-06009: using target database control file instead of recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-06010: error while looking up datafile: string Cause: An error occurred while looking up the specified datafile in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the datafile was added recently, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06011: invalid level specified: number Cause: An invalid incremental backup level was specified. Action: Incremental backup level must be between 0 and 4. RMAN-06012: channel: string not allocated Cause: A RELEASE or SETLIMIT command was found for a channel identifier that was not yet allocated. Action: Correct the channel identifier, or add an ALLOCATE CHANNEL command. RMAN-06013: duplicate channel identifier found: string Cause: A channel identifier was reused without first releasing the channel. Action: Add a RELEASE CHANNEL command. RMAN-06014: command not implemented yet: string Cause: Not all commands are implemented for the beta release. Action: Avoid using the command. RMAN-06015: error while looking up datafile copy name: string Cause: An error occurred while looking up the specified datafile copy name in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the datafile copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06016: duplicate backup operand specified: string Cause: The specified operand appears more than once in the same backup specifier or backup command. Action: Delete the duplicated operand. RMAN-06017: initialization of parser failed Cause: The parser package initialization routine returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06018: duplicate operand specified in backup specification: string Cause: A backup specification operand appears more than once in a backup specification. Action: Delete the duplicate operand. RMAN-06019: could not translate tablespace name "string" Cause: An error occurred while looking up the specified tablespace name in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the tablespace is entered correctly. If the tablespace was added recently, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06020: connected to auxiliary database (not started) Cause: This is an informational message only. Action: No action is required. RMAN-06021: FROM DATAFILECOPY/BACKUPSET may not be specified with archived logs Cause: The FROM DATAFILECOPY/BACKUPSET option applies only to datafile and control file restores. Action: Use this option only for datafile and control file restores. RMAN-06022: invalid level specified for image copy: number Cause: An invalid incremental backup level was specified for an image copy. Action: Incremental backup level must be 0 for image copies. RMAN-06023: no backup or copy of datafile number found to restore Cause: A datafile, tablespace, or database restore could not proceed because no backup or copy of the indicated file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: None - this is an informational message. See message 6026 for further details. RMAN-06024: no backup or copy of the control file found to restore Cause: A control file restore could not proceed because no backup or copy of the control file was found. It may be the case that a backup or copy of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: None - this is an informational message. See message 6026 for further details. RMAN-06025: no backup of archived log for thread number with sequence number and starting SCN of string found to restore Cause: An archived log restore restore could not proceed because no backup of the indicated archived log was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: None - this is an informational message. See message 6026 for further details. RMAN-06026: some targets not found - aborting restore Cause: Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged. Action: The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list. RMAN-06027: no archived logs found that match specification Cause: An archived log record specifier did not match any archived logs in the recovery catalog. Action: Resubmit the command with a different archived log record specifier. The rman LIST command can be used to display all archived logs that Recovery Manager knows about. RMAN-06028: duplicate operand specified in restore specification: string Cause: The CHANNEL, TAG, FROM, PARMS, VALIDATE, DEVICE TYPE, CHECK READONLY or DB_UNIQUE_NAME option was specified more than once in the restore command or in one of the restore specifications. Action: Correct and resubmit the command. RMAN-06029: the control file may be included only in a datafile backup set Cause: The "include current/standby control file" option was specified for an archived log backup set. Action: Use this option only for datafile backup sets. RMAN-06030: the DELETE [ALL] INPUT option may not be used with a datafile backup set Cause: The DELETE [ALL] INPUT option was specified for a backup that contains the current control file or datafile. Action: Remove the option and resubmit the command. RMAN-06031: could not translate database keyword Cause: An error was received when calling DBMS_RCVMAN Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06032: at least 1 channel of TYPE DISK must be allocated to execute a COPY command Cause: No channel of TYPE DISK was allocated. Action: Allocate a channel of TYPE DISK and re-issue the command. RMAN-06033: channel string not allocated Cause: An rman command requests a specific channel, but the requested channel has not been allocated. Action: ALLOCATE the channel, or correct the channel identifier. RMAN-06034: at least 1 channel must be allocated to execute this command Cause: No channels were allocated. Action: ALLOCATE a channel. RMAN-06035: wrong version of recover.bsq, expecting string, found string Cause: The "recover.bsq" file is incompatible with the RMAN executable. Action: Install the correct version of recover.bsq. RMAN-06036: datafile number is already restored to file string Cause: A SET NEWNAME command was issued to restore a datafile to a location other than the original datafile, and Recovery Manager determined that the best candidate for restoring the file is the datafile copy with the same name, therefore the file is already restored and no action need be taken. Action: None - this is an informational message. RMAN-06038: recovery catalog package detected an error Cause: A call to DBMS_RCVMAN returned an error. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06039: SET NEWNAME command has not been issued for datafile string Cause: A SWITCH command was specified for a datafile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued. Action: Correct and resubmit the SWITCH command. RMAN-06040: control file is already restored to file string Cause: The best candidate control file for restoration is the one that is named in the RESTORE CONTROLFILE command, hence no action need be taken. Action: None - this is an informational message. RMAN-06041: cannot switch file number to copy of file number Cause: An attempt was made to switch a datafile to a copy of a different datafile. Action: Correct and resubmit the SWITCH command. RMAN-06042: PLUS ARCHIVELOG option is not supported with non-datafile backups Cause: The PLUS ARCHIVELOG option was supplied but does not apply to this type of backup. Action: Remove the PLUS ARCHIVELOG operand and re-enter the command. RMAN-06043: TAG option not supported for archived log copies Cause: The tag option was supplied but does not apply to this type of copy. Action: Remove the TAG operand and re-enter the command RMAN-06045: LEVEL option not supported for archived log or current/standby control file copies Cause: The LEVEL option was supplied but does not apply to this type of copy. Action: Remove the LEVEL operand and re-enter the command. RMAN-06046: archived log name: string Cause: An error occurred while translating an archived log name to its recovery catalog RECID/time stamp. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06047: duplicate datafile number specified for restoration from copy Cause: The indicated datafile was specified more than once in the same restore command. Action: Correct and resubmit the RESTORE command. RMAN-06048: duplicate control file specified for restoration from copy Cause: The control file was specified more than once in the same RESTORE command. Action: Correct and resubmit the RESTORE command. RMAN-06049: CHECK LOGICAL option not supported for archived log or current/standby control file copies Cause: The check logical option was supplied but does not apply to this type of copy. Action: Remove the CHECK LOGICAL operand and re-enter the command RMAN-06050: archived log for thread number with sequence number is already on disk as file string Cause: An archived log which was requested to be restored (either explicitly or via a range specification) does not need to be restored because it already exists on disk. Action: None - this is an informational message RMAN-06051: DELETE INPUT option not implemented yet Cause: This option was specified in a backup specification. Action: Remove the DELETE INPUT option. RMAN-06052: no parent backup or copy of datafile number found Cause: An incremental backup at level 1 or higher could not find any parent backup or copy of the indicated datafile. A level 0 backup of the datafile will be taken automatically. Action: This is an informational message only. RMAN-06053: unable to perform media recovery because of missing log Cause: This message is accompanied with another message identifying the missing log. The log would be needed to perform the media recovery, but the log is not on disk and no backup set containing the log is available. Action: Determine if a backup set containing the log can be made available. If so, then use the CHANGE command to make the backup set available and retry the command. If not, then a point in time recovery up to the missing log is the only alternative. RMAN-06054: media recovery requesting unknown archived log for thread string with sequence string and starting SCN of string Cause: Media recovery is requesting a log whose existence is not recorded in the recovery catalog or control file. Action: If a copy of the log is available, then add it to the recovery catalog and/or control file via a CATALOG command and then retry the RECOVER command. If not, then a point in time recovery up to the missing log is the only alternative and database can be opened using ALTER DATABASE OPEN RESETLOGS command. RMAN-06055: could not find archived log with sequence string for thread string Cause: A log which was on disk at the start of media recovery or which should have been restored from a backup set could not be found. Action: Check the Recovery Manager message log to see if the log was restored by a previous job step. If so, then check the V$ARCHIVED_LOG view to see if the log is listed in the control file. If so, then validate that the log exists on disk and is readable. If the log was not restored, or was restored but no record of the log exists in V$ARCHIVED_LOG, then contact Oracle Customer Support. RMAN-06056: could not access datafile number Cause: A backup or copy could not proceed because the datafile header could not be read or the header was not valid. Action: Make the datafile accessible or skip it. RMAN-06057: a standby control file cannot be included along with a current control file Cause: "current control file" was specified along with "standby control file". Action: Remove "current control file" or "standby control file" from backup specification. RMAN-06058: a current control file cannot be included along with a standby control file Cause: "standby control file" was specified along with "current control file". Action: Remove "standby control file" or "current control file" from backup specification. RMAN-06059: expected archived log not found, lost of archived log compromises recoverability Cause: The archived log was not found. The repository thinks it does exist. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because the archived log was removed by an outside utility without updating the repository. Action: If the archived log has been removed with an outside utility and the archived log has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archived log has not been previously backed up, then you should take a full backup of the database and archived logs to preserve recoverability. Previous backups are not fully recoverable. RMAN-06060: WARNING: skipping datafile compromises tablespace string recoverability Cause: SKIP INACCESSIBLE or SKIP OFFLINE option resulted in skipping datafile during BACKUP. If the datafile has in fact been lost and there is no backup, then the tablespace is no longer recoverable without ALL archived logs since datafile creation. This may occur because the datafile was deleted by an outside utility or the datafile is made OFFLINE [DROP]. Action: If there is no backup of skipped datafile and the tablespace has to be recoverable without ALL archived logs since datafile creation, then you should make these datafile available for backup. RMAN-06061: WARNING: skipping archived log compromises recoverability Cause: SKIP INACCESSIBLE option resulted in skipping archived logs during BACKUP. If the archived log has in fact been lost and there is no backup, then the database is no longer recoverable across the point in time covered by the archived log. This may occur because archived log was removed by an outside utility without updating the repository. Action: If the archived log has been removed with an outside utility and the archived log has already been backed up, then you can synchronize the repository by running CROSSCHECK ARCHIVELOG ALL. If the archived log has not been previously backed up, then you should take a full backup of the database and archived logs to preserve recoverability. Previous backups are not fully recoverable. RMAN-06062: 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 or modify the command. RMAN-06063: DBID is not found in the recovery catalog Cause: DBID is not found in the recovery catalog. Action: Verify that the DBID is correct and restart the command. RMAN-06064: creating datafile file number=string name=string Cause: RESTORE/RECOVER command was issued and there were no backup available for the datafile. Action: This is an informational message only. RMAN-06065: The backup operand [string] conflicts with another specified operand. Cause: The user attempted to use two (or more) conflicting operands within the same statement. Action: Remove one or both of the conflicting operands. RMAN-06066: the target database must be mounted when issuing a RECOVER command Cause: A RECOVER command was issued, but the target database control file is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-06067: RECOVER DATABASE required with a backup or created control file Cause: The control file has been restored from a backup or was created via ALTER DATABASE CREATE CONTROLFILE. Action: Use the RECOVER DATABASE command to perform the recovery. RMAN-06068: recovery aborted because of missing datafiles Cause: This error should be accompanied by one or more instances of message ORA-06094. Action: Refer to message ORA-06094. RMAN-06069: the file name for datafile string is missing in the control file Cause: Media recovery of a backup control file added this datafile to the control file, but it does not set the file name because that is unsafe. Action: If the datafile is on disk, then issue ALTER DATABASE RENAME to correct the control file. Otherwise, RESTORE the datafile, and then use SWITCH to make it known to the control file. If the tablespace containing this datafile will be dropped, then reissue the RECOVER command with a SKIP clause to skip recovery of this tablespace. RMAN-06070: DBWR could not identify datafile string Cause: DBWR could not find the specified datafile. Action: Ensure that the datafile exists and is accessible. RMAN-06071: could not open datafile string Cause: An error was encountered when trying to open the specified datafile. Action: Ensure that the datafile exists and is accessible. RMAN-06073: file header is corrupt for datafile string Cause: ORACLE detected a corruption in the file header. A media failure has probably occurred. Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command. RMAN-06074: file string is not an ORACLE datafile Cause: The file header indicates that this file is not a datafile. The file may have been overlaid or corrupted. Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command. RMAN-06075: datafile string does not belong to this database Cause: The file header indicates that this file belongs to some other ORACLE database. Action: RESTORE the datafile to a new location, then do a SWITCH, and then retry the RECOVER command. RMAN-06076: datafile string contains wrong datafile Cause: The datafile header indicates the file contains a different datafile number. Action: RESTORE the datafile, and then retry the RECOVER command. RMAN-06077: datafile string is a different version than contained in the control file Cause: The control file entry for this datafile specifies a different version of this datafile. Different versions of a datafile can exist when a tablespace is dropped, and a new tablespace is created which reuses the same datafile numbers. Action: If the datafile is correct, the fix the control file by using the SWITCH command. Otherwise, RESTORE the correct version of this datafile and retry the RECOVER command. RMAN-06078: the control file is older than datafile string Cause: The control file appears to be older than the specified datafile, but it is not marked as a backup control file. This indicates that the control file has been replaced with an older version. This error does not occur when a backup control file which was created via Recovery Manager or the ALTER DATABASE BACKUP CONTROLFILE command is restored because such control files are marked as backups. Action: RESTORE a control file and perform RECOVER DATABASE. RMAN-06079: database must be mounted to perform recovery Cause: A RECOVER command was issued, but the target database is not mounted. Action: Issue ALTER DATABASE MOUNT. RMAN-06080: SWITCH required for datafile string Cause: The control file record for this datafile is for an older incarnation of the datafile. A SWITCH command must be issued to updated the control file before doing RECOVER. Action: Issue SWITCH command then retry RECOVER. RMAN-06081: error reading datafile header for datafile string, code string Cause: X$KCVFH returned the specified code in the HXERR column when it was queried for the specified datafile. Action: Ensure the datafile exists and is readable. Using a newer release of Recovery Manager may return a more meaningful error message. If you have no newer version of Recovery Manager, contact Oracle Customer Support. RMAN-06082: datafile copy tag string is ambiguous Cause: The specified tag refers to multiple datafile copies belonging to different datafiles. Action: Specify the datafile copy by file name rather than by tag. RMAN-06083: error when loading stored script string Cause: The recovery catalog database returned an error. This error explains the cause of the problem. Action: Correct the problem and retry. RMAN-06084: the target database may not be mounted when issuing REPLICATE Cause: A REPLICATE command was issued, but the target database is already mounted. Action: dismount the target database control file by issuing ALTER DATABASE CLOSE and ALTER DATABASE DISMOUNT via Enterprise Manager or Server Manager. RMAN-06085: must use SET NEWNAME command to restore datafile string Cause: A RESTORE command for the specified datafile could not find a destination name for the specified datafile. Action: Add a SET NEWNAME command prior to the RESTORE command to specify the restore destination for this file. RMAN-06086: offline files may only be skipped in a datafile backup set Cause: The SKIP OFFLINE option was specified for an archived log backup set. Action: Use this option only for datafile backup sets. RMAN-06087: read-only files may only be skipped in a datafile backup set Cause: The SKIP READONLY option was specified for an archived log backup set. Action: Use this option only for datafile backup sets. RMAN-06088: datafile copy string not found or out of sync with catalog Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database. Action: Re-catalog the file and retry the operation. RMAN-06089: archived log string not found or out of sync with catalog Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database. Action: Re-catalog the file and retry the operation. RMAN-06090: error while looking up control file copy: string Cause: An error occurred while looking up the specified control file copy in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the file name is entered correctly. If the control file copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06091: no channel allocated for maintenance (of an appropriate type) Cause: A command was entered that requires a maintenance channel, and no maintenance channel is allocated, or none of the appropriate type. Action: Use ALLOCATE CHANNEL FOR MAINTENANCE before deleting backup pieces, or using the CROSSCHECK or DELETE EXPIRED commands. Proxy copies require a non-DISK channel. RMAN-06092: error while looking up backup piece Cause: An error occurred while looking up the specified backup piece in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the backup piece was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06093: recovery catalog contains obsolete version of datafile string Cause: The specified datafile number was dropped and then reused. The control file mounted by the target database contains the newer version of the datafile, but the recovery catalog contains information about only the older version. Action: Issue a RESYNC command to update the recovery catalog, then reissue the failing command. If the error persists, contact Oracle Customer Support. RMAN-06094: datafile string must be restored Cause: A RECOVER command was issued, and the recovery catalog indicates the specified datafile should be part of the recovery, but this datafile is not listed in the control file, and cannot be found on disk. Action: Issue a RESTORE command for this datafile, using the same UNTIL clause specified to the RECOVER command (if any), then reissue the RECOVER. RMAN-06095: a backup control file must be restored to recover datafile string Cause: The control file currently mounted by the target database contains a newer incarnation of the datafile than the recovery catalog indicates is appropriate for the Point-in-Time being recovered to. Action: Restore the control file, using the same UNTIL clause specified on the failing RECOVER command, then reissue the command. If no control file can be restored, then you should issue a CREATE CONTROLFILE command. RMAN-06096: SWITCH required for newname of datafile string to take effect Cause: A SET NEWNAME was issued for this datafile, but no SWITCH command was issued before the RECOVER command. Action: Issue a SWITCH command to make the newname take effect before doing RECOVER. RMAN-06098: the target database must be mounted when issuing a BACKUP command Cause: A BACKUP command was issued, but the target database control file is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-06099: error occurred in source file: string, line: number Cause: See accompanying error. Action: See accompanying error. RMAN-06100: no channel to restore a backup or copy of datafile number Cause: A datafile, tablespace, or database restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore. Action: None - this is an informational message. See message 6026 for further details. RMAN-06101: no channel to restore a backup or copy of the control file Cause: A control file restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore. Action: None - this is an informational message. See message 6026 for further details. RMAN-06102: no channel to restore a backup or copy of archived log for thread number with sequence number and starting SCN of string Cause: An archived log restore restore could not proceed because the backup of the indicated file exists on a device type that was not allocated for restore. Action: None - this is an informational message. See message 6026 for further details. RMAN-06103: duplicate qualifier found in REPORT command: string Cause: The indicated qualifier appears more than once in a REPORT qualifier list. Action: delete the duplicate qualifier RMAN-06105: duplicate qualifier found in LIST command: string Cause: The indicated qualifier appears more than once in a LIST qualifier list. Action: delete the duplicate qualifier RMAN-06106: this command requires that target database be mounted Cause: A command was issued that requires the target database to be mounted, but the target database is not mounted. Action: Mount the target database control file by issuing ALTER DATABASE MOUNT via Enterprise Manager or Server Manager. RMAN-06107: WARNING: control file is not current for REPORT NEED BACKUP DAYS Cause: The REPORT NEED BACKUP DAYS command may report some files as requiring backups when they really do not, because the most current online status of the file is not known unless a current control file is mounted. Action: No action is required, however, a current control file should be mounted, if possible, to get the most accurate REPORT output. RMAN-06108: changed datafile copy unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06109: changed archived log unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06110: changed control file copy unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06111: changed backup piece unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06112: changed datafile copy available Cause: This is an informational message only. Action: No action is required. RMAN-06113: changed archived log available Cause: This is an informational message only. Action: No action is required. RMAN-06114: changed control file copy available Cause: This is an informational message only. Action: No action is required. RMAN-06115: changed backup piece available Cause: This is an informational message only. Action: No action is required. RMAN-06116: cannot crosscheck unavailable object Cause: An attempt was made to crosscheck an object which is unavailable. Action: Make object available and try again or don't crosscheck object. RMAN-06117: cannot do DELETE EXPIRED on an object which is not expired Cause: An attempt was made to DELETE EXPIRED an object which is not expired. Action: Remove EXPIRED keyword, crosscheck object, or don't delete object. RMAN-06118: a backup control file older than SCN string must be used for this recovery Cause: An attempt was made to recover the database, but some files had no backup, and were not present in the control file at the beginning of the restore. This happens when the control file used during the recovery is a backup control file taken before the creation of some of the files that had no backup. In this situation, the control file that is used must be taken before the creation of all files that have no backup. This will enable RMAN to automatically re-create all of the files that had no backup. Action: Restore a control file that was backed up before the specified SCN. The following RMAN commands can be used to do this: SET UNTIL SCN <x>; (where <x> is the SCN displayed in the message) RESTORE CONTROLFILE; RMAN-06119: uncataloged datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-06120: uncataloged archived log Cause: This is an informational message only. Action: No action is required. RMAN-06121: uncataloged control file copy Cause: This is an informational message only. Action: No action is required. RMAN-06122: CHANGE .. UNCATALOG not supported for BACKUPSET Cause: The CHANGE BACKUPSET .. UNCATALOG command was entered. The UNCATALOG operation is not supported with backup set. Action: Use CHANGE BACKUPSET .. DELETE instead. RMAN-06123: operation not supported without the recovery catalog or mounted control file Cause: A command was used which requires a connection to a recovery catalog database or the target database to be mounted. The command cannot be used when no backup repository is available. Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise enter a different command. RMAN-06124: error while looking up datafile copy key: number Cause: An error occurred while looking up the specified datafile copy key in the recovery catalog. Action: This error is accompanied by other errors describing the reason for the failure. RMAN-06125: error while looking up archived log key: number Cause: An error occurred while looking up the specified archived log key in the recovery catalog. Action: This error is accompanied by other errors describing the reason for the failure. RMAN-06126: skipping offline file string Cause: The indicated file will not be included in the backup set because it is offline and the SKIP OFFLINE option was specified. Action: No action is required. RMAN-06127: skipping read-only file string Cause: The indicated file will not be included in the backup set because it is read only and the SKIP READONLY option was specified. Action: No action is required. RMAN-06128: skipping inaccessible file string Cause: The indicated file will not be included in the backup set because it could not be read, and the SKIP INACCESSIBLE option was specified. Action: No action is required. RMAN-06129: invalid reserved channel ID: string Cause: The specified channel id is invalid. DELETE and DEFAULT are reserved channel names and may not be specified by users. Action: Specify a different channel ID. RMAN-06131: SKIP OFFLINE/READONLY only allowed with current control file Cause: The SKIP OFFLINE and SKIP READONLY options are only permitted when the target database control file is current. When the target control file is not current, it is not possible to obtain a datafile's offline/read only status. Action: Remove the skip option or mount a current control file on the target database. RMAN-06132: cannot backup datafile string because it is not in the control file Cause: A backup command was issued that includes the specified datafile, but the datafile is not listed in the control file. The control file is not current (it is a backup or a created control file). Action: Recover the control file to make it current, then retry the backup command. RMAN-06133: recovery catalog may have obsolete data for datafile string Cause: A RESTORE UNTIL was issued, and the recovery catalog choose an older incarnation of the datafile than is listed in the control file. Action: If the recovery catalog has correct data for the datafile, then restore a backup control file using the same UNTIL clause, then retry the datafile restore. Otherwise, restore a backup of the incarnation of the datafile listed in the control file. RMAN-06134: host command complete Cause: An operating system command has completed. Action: None - this is an informational message. RMAN-06135: error executing host command: string Cause: A host command returned a non-zero return code. Action: Correct the offending command. RMAN-06136: ORACLE error from auxiliary database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06137: must have recovery catalog for REPORT SCHEMA AT TIME Cause: A 'REPORT SCHEMA at_clause' command was issued, but there is no recovery catalog database. Action: If you are not using a recovery catalog, then you may only issue the 'REPORT SCHEMA' command with no at_clause. RMAN-06138: control file not mounted - must specify AT clause with REPORT command Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and there is also no control file mounted at the target database, so there is no place to get the information about the current list of files comprising the database. Action: Use a recovery catalog or mount a control file at the target database. RMAN-06139: WARNING: control file is not current for REPORT SCHEMA Cause: A 'REPORT SCHEMA' with no at_clause was issued, and there is no recovery catalog, and the control file mounted by the target instance is not current, so the information about the current list of datafiles may not be current. Action: Use a recovery catalog or mount a current control file. RMAN-06140: cannot specify TAG option with LIST INCARNATION Cause: The TAG option was specified with LIST INCARNATION. This is not permitted because there is no TAG associated with a database incarnation. Action: Remove the TAG option and re-run the LIST command. RMAN-06141: cannot specify ARCHIVELOG LIKE option with RESTORE Cause: The ARCHIVELOG LIKE option was specified with RESTORE. This is not permitted because recovery catalog contains only those records that are not deleted from disk. Action: Remove the ARCHIVELOG LIKE option and re-run the command. RMAN-06142: DEVICE TYPE cannot be specified with this command Cause: The DEVICE TYPE option was specified with a command that does not support it. Action: Remove the DEVICE TYPE option and re-run the command. RMAN-06143: LIKE may only be specified with COPY Cause: The LIKE option was specified with a RMAN command. This is not permitted because only copies of datafiles, control files or archived logs have file names that may be tested with a LIKE operand. Action: Remove the LIKE option and re-run the RMAN command. RMAN-06144: FROM or UNTIL may not be specified with LIST INCARNATION Cause: The FROM or UNTIL option was specified with LIST INCARNATION. This is not permitted because there is no time associated with a database incarnation. Action: Remove the FROM or UNTIL option and re-run the LIST command. RMAN-06145: control file is not current - obsolete file list may be incomplete Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. If the mounted control file is not current, it may not be possible to determine if a satisfactory backup exists for files which have been offline since the last OPEN RESETLOGS. Action: No action need be taken - this is an informational message only. To ensure a complete report of obsolete backups, mount a current control file. RMAN-06146: changes found for file number beyond offline SCN Cause: A CHANGE or REPORT command needs to compute the list of backups that are redundant and may be deleted. A backup was found for a file which is shown as offline in the target database control file, but the backup contains changes beyond the SCN when the file went offline. This is most likely because the target database control file is not really current, but is a restored copy of an older control file. Action: Mount a current control file or a backup control file. RMAN-06147: no obsolete backups found Cause: A CHANGE or REPORT command could find no files that meet the specified criteria for obsoleteness. Action: None - this is an informational message. RMAN-06148: redundancy count must be greater than zero Cause: The REDUNDANCY operand specified for a CHANGE or REPORT OBSOLETE command was zero. Action: Specify a REDUNDANCY operand of 1 or greater. RMAN-06150: auxiliary name for datafile number set to: string Cause: This message is issued in response to a CONFIGURE AUXNAME command. Action: None - this is an informational message. RMAN-06151: datafile string creation SCN string Cause: This is an informational message. It should be accompanied by other messages. Action: None RMAN-06153: validation failed for datafile copy Cause: The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog. Action: None - this is an informational message. RMAN-06154: validation succeeded for datafile copy Cause: The CHANGE DATAFILECOPY VALIDATE command found that the datafile copy still matches its data in the recovery catalog. Action: None - this is an informational message. RMAN-06155: validation failed for control file copy Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy could not be found or no longer contains the same data, so its record was deleted from the recovery catalog. Action: None - this is an informational message. RMAN-06156: validation succeeded for control file copy Cause: The CHANGE CONTROLFILECOPY VALIDATE command found that the control file copy still matches its data in the recovery catalog. Action: None - this is an informational message. RMAN-06157: validation failed for archived log Cause: The CROSSCHECK ARCHIVELOG command determined that the archived log could not be found or no longer contained the same data, so its record was marked expired. Action: None - this is an informational message. RMAN-06158: validation succeeded for archived log Cause: The CROSSCHECK ARCHIVELOG command or VALIDATE HEADER option determined that the archived log still matches its data. Action: None - this is an informational message. RMAN-06159: error while looking up backup set Cause: An error occurred while looking up the specified backup set in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the key is entered correctly. If the backup set was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06160: no backup pieces found for backup set key: number Cause: No backup pieces for the requested backup set were found in the recovery catalog, or the target database control file. Action: Specify an existing backup set. RMAN-06161: error when inspecting auxiliary file name: string Cause: This error is accompanied by other errors explaining the cause. Action: Correct the auxiliary file name if it is wrong via the CONFIGURE AUXNAME command. RMAN-06162: sql statement: string Cause: This is the sql statement about to be executed for a SQL command. Action: None, informational message only. RMAN-06163: some datafiles cannot be recovered, aborting the RECOVER command Cause: This message should be followed by one or more 6162 or 6164 messages. Action: Check the accompanying errors. RMAN-06164: WARNING: no channel of required type allocated to recover datafile number Cause: A RECOVER command could not proceed because incremental backup sets or archived log backup sets exist on a device type that has not been allocated. Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type. RMAN-06165: datafile string is too old to recover, restore a more recent copy Cause: The archived logs and/or incremental backup sets required to recover the datafile do not exist, but a more recent backup of the datafile exists which can be recovered. Action: Issue a RESTORE for the datafile, then reissue the RECOVER command. RMAN-06166: datafile string cannot be recovered Cause: Incremental backups or archived redo logs needed to recover the datafile cannot be found, and no recoverable full backup or datafile copy exists. Action: Use the LIST command to see if there is a backup set or datafile copy that can be made AVAILABLE. If not, then the datafile is unrecoverable. If a full or datafile copy exists, then a Point-in-Time Recovery may be possible. RMAN-06167: already connected Cause: a CONNECT command was issued, but RMAN is already connected to the specified database. Action: RMAN has no DISCONNECT command, so to connect to a different instance, exit RMAN and start it again. RMAN-06168: no backup pieces with this tag found: string Cause: A tag was used to specify a list of backup pieces, but no backup pieces with this tag could be found. Action: Make sure the tag is specified correctly. RMAN-06169: could not read file header for datafile string error reason string Cause: The specified datafile could not be accessed. The reason codes are: 1 - file name is MISSINGxx in the control file 2 - file is offline 3 - file is not verified 4 - DBWR could not find the file 5 - unable to open file 6 - I/O error during read 7 - file header is corrupt 8 - file is not a datafile 9 - file does not belong to this database 10 - file number is incorrect 12 - wrong file version 15 - control file is not current Action: If the error can be corrected, do so and retry the operation. The SKIP option can be used to ignore this error during a backup. RMAN-06170: no control file copy found with offline range RECID string STAMP string datafile string Cause: This offline range is needed for recovering the specified data file, but the offline range record has aged out of the current control file and no control file copy with the record could be accessed. At least 1 control file copy containing the offline range was found in the recovery catalog and was in AVAILABLE status. Action: Query the RC_CONTROLFILE_COPY view for the names of all control file copies, then issue a CHANGE CONTROLFILECOPY ... VALIDATE; command for them. Then reissue the RECOVER command. RMAN-06171: not connected to target database Cause: A command was issued but no connection to the target database has been established. Action: Issue a CONNECT TARGET command to connect to the target database. RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece Cause: A restore could not proceed because no AUTOBACKUP was found or specified handle is not a valid copy or backup piece. In case of restore from AUTOBACKUP, it may be the case that a backup exists, but it does not satisfy the criteria specified in the user's restore operands. In case of restore from handle, it may be the handle is not a backup piece or control file copy. In may be that it does not exist. Action: Modify AUTOBACKUP search criteria or verify the handle. RMAN-06173: SET NEWNAME command has not been issued for datafile string when restore auxiliary Cause: Auxiliary type was specified for the control file, but no SET NEWNAME command has been previously issued for a datafile. Action: Issue SET NEWNAME command for every datafile in the recovery set. RMAN-06174: not connected to auxiliary database Cause: An auxiliary command was issued but no connection to a auxiliary database has been established. Action: Issue a CONNECT AUXILIARY command to connect to the auxiliary database. RMAN-06175: deleted script: string Cause: A DELETE SCRIPT command was executed. Action: None, informational message only. RMAN-06176: no recovery required; all files are read only or offline Cause: A RECOVER DATABASE command does not need to recover any files because all of the files to be recovered are offline or read only. This can only occur when the SKIP clause includes the SYSTEM tablespace. Action: None, informational message only RMAN-06177: restore not done; all files read only, offline, or already restored Cause: A RESTORE command does not need to restore any files, because all of the files to be restored are offline, read-only, or are already restored to their correct destinations. Action: None, informational message only RMAN-06178: datafile number not processed because file is offline Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is offline clean at the desired point in time. Action: None, informational message only RMAN-06179: datafile number not processed because file is read-only Cause: A RESTORE DATABASE or RECOVER DATABASE command omitted processing the indicated datafile because it is part of a read-only tablespace at the desired point in time. Action: None, informational message only RMAN-06180: incremental backups require Enterprise Edition Cause: A BACKUP command with INCREMENTAL LEVEL > 0 was specified. Action: Use FULL, or INCREMENTAL LEVEL 0. RMAN-06181: multiple channels require Enterprise Edition Cause: Attempt to allocate more than 1 channel in a job. Action: Remove all except one ALLOCATE CHANNEL command. RMAN-06182: archived log string of thread string with sequence string larger than MAXSETSIZE Cause: A BACKUP ARCHIVELOG command specified the MAXSETSIZE operand too low. The specified archived log is larger than MAXSETSIZE will allow. Action: Increase MAXSETSIZE limit. RMAN-06183: datafile or datafile copy string (file number string) larger than MAXSETSIZE Cause: A BACKUP DATAFILE(copy) command specified the MAXSETSIZE operand too low. The specified datafile is larger than MAXSETSIZE will allow. Action: Increase MAXSETSIZE limit. RMAN-06184: duplicate object in backup specifier: string string Cause: A backup command specifies the same datafile or copy of a data file multiple times. Action: Eliminate the duplicates. RMAN-06185: Recovery Manager incompatible with string database: RMAN number.number.number.number to number.number.number.number required Cause: This version of recovery manager was incompatible with the indicated database or the DBMS_BACKUP_RESTORE package installed in the indicated 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. Otherwise, use a version of RMAN within the range specified in the error message. RMAN-06186: PL/SQL package string.string version string in string database is too old Cause: The specified PL/SQL package is a version that is too old to work with this version of the Recovery Manager (RMAN). Action: If the database indicated is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. RMAN-06187: control file copy string not found or out of sync with catalog Cause: The indicated file is not found, or is found but is not the same file that the recovery catalog thinks it is. It is likely that some operation outside of Recovery Manager has altered the file, or that Recovery Manager has not resynced with the target database. Action: Re-catalog the file and retry the operation. RMAN-06188: cannot use command when connected to a mounted target database Cause: An attempt was made to issue a command that can be used only when there is no connection to the target database or when the target database is not mounted. Action: Dismount the database or restart RMAN and use the command before connecting to the target database. RMAN-06189: current DBID number does not match target mounted database (number) Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected. Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN. RMAN-06190: PL/SQL package string.string version string in string database is not current Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode. Action: No action is required, but certain features and bug-fixes may not be available when RMAN runs in backwards-compatible mode. If the database is CATALOG, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are dbmsrman.sql and prvtrman.plb. RMAN-06191: PL/SQL package string.string version string in string database is too new Cause: RMAN detected an incompatible version of the specified package. Action: Use a newer version of recovery manager. Message 6439 indicates the minimum required version of recovery manager. RMAN-06192: maximum value for MAXPIECESIZE or MAXSETSIZE must be between 1 Kb and 2048 Gb Cause: Input size for MAXPIECESIZE or MAXSETSIZE was out of range. Action: Specify a valid size and retry the command. RMAN-06193: connected to target database (not started) Cause: This is an informational message only. Action: The database must be started before any other RMAN commands are issued. RMAN-06194: target database instance not started Cause: A command was issued that requires the target database instance be started. Action: Issue a STARTUP command to start the instance. RMAN-06195: auxiliary database not started Cause: A command was issued that requires the auxiliary database instance be started. Action: Issue a STARTUP AUXILIARY command. RMAN-06196: Oracle instance started Cause: A STARTUP command completed successfully. Action: None, this is an informational message. RMAN-06197: Total System Global Area string bytes Cause: This is an informational message only. Action: No action is required. RMAN-06198: string string bytes Cause: This is an informational message only. Action: No action is required. RMAN-06199: database mounted Cause: This is an informational message only. Action: No action is required. RMAN-06200: Changed string objects to AVAILABLE status Cause: This is an informational message only. Action: No action is required. RMAN-06201: Deleted string objects Cause: This is an informational message only. Action: No action is required. RMAN-06202: Deleted string EXPIRED objects Cause: This is an informational message only. Action: No action is required. RMAN-06203: Changed KEEP options for string objects Cause: This is an informational message only. Action: No action is required. RMAN-06204: Changed string objects to UNAVAILABLE status Cause: This is an informational message only. Action: No action is required. RMAN-06205: Uncataloged string objects Cause: This is an informational message only. Action: No action is required. RMAN-06206: Crosschecked string objects Cause: This is an informational message only. Action: No action is required. RMAN-06207: WARNING: string objects could not be deleted for string channel(s) due Cause: This is an informational message only. Action: No action is required. RMAN-06208: to mismatched status. Use CROSSCHECK command to fix status Cause: This is an informational message only. Action: No action is required. RMAN-06209: List of failed objects Cause: This is an informational message only. Action: No action is required. RMAN-06210: List of Mismatched objects Cause: This is an informational message only. Action: No action is required. RMAN-06211: ========================== Cause: This is an informational message only. Action: No action is required. RMAN-06212: Object Type Filename/Handle Cause: This is an informational message only. Action: No action is required. RMAN-06213: --------------- --------------------------------------------------- Cause: This is an informational message only. Action: No action is required. RMAN-06214: string string Cause: This is an informational message only. Action: No action is required. RMAN-06215: List of objects that must perform same operation at other database Cause: This is an informational message only. Action: The specified list of objects were not accessible at connected target database. Re-run the CROSSCHECK command after connecting to database that has DB_UNIQUE_NAME displayed in output for the specified object. RMAN-06216: WARNING: db_unique_name mismatch - string objects could not be updated Cause: This is an informational message only. Action: Run CROSSCHECK command after connecting to a primary or physical standby database that can access the specified objects. RMAN-06217: not connected to auxiliary database with a net service name Cause: A command that moves files from the target instance to the auxiliary instance was requested. Such a command requires a net service name be present in the connect string used to connect to the auxiliary instance. Action: Issue a CONNECT AUXILIARY command and include a net serice name in the connect string. That service name must be valid on the target instance. RMAN-06218: List of objects requiring same operation on database with db_unique_name string Cause: This is an informational message only. Action: The specified list of objects were not accessible by the target database. Re-run the same command after connecting to database that has DB_UNIQUE_NAME displayed in output for the specified object. RMAN-06219: List of objects not associated with all known db_unique_names Cause: This is an informational message only. Action: The specified list of objects were not accessible by the target database. Re-run the same command after connecting to primary database or physical standby database that can access the specified objects. RMAN-06220: Creating automatic instance, with SID='string' Cause: No connection to the auxiliary instance was provided, but the command requires an auxiliary instance. Action: No action is required unless you want to create a permanent database, in which case you should stop the command and re-run it, providing an auxiliary instance connection. RMAN-06221: Removing automatic instance Cause: RMAN is removing the automatic auxiliary instance that was created for this command. Action: No action is required. RMAN-06223: starting up automatic instance string Cause: This is an informational message only. Action: No action is required. RMAN-06224: Automatic instance created Cause: This is an informational message only. Action: No action is required. RMAN-06225: shutting down automatic instance string Cause: This is an informational message only. Action: No action is required. RMAN-06226: Automatic instance removed Cause: This is an informational message only. Action: No action is required. RMAN-06230: List of Stored Scripts in Recovery Catalog Cause: This message is issued in response to a LIST SCRIPT NAMES command. The following fields are shown for each script that is stored in the recovery catalog: Header indicating to what database the script belongs. Script Name: name of the script. Description: comment associated with this script. Action: No action is required. RMAN-06238: List of Databases Cause: This message is issued in response to a LIST DB_UNIQUE_NAME command. The following fields are shown for each database that is known to the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. DB_UNIQUE_NAME: db_unique_name value for the database. Action: No action is required. RMAN-06246: List of Database Incarnations Cause: This message is issued in response to a LIST INCARNATION OF DATABASE command. The following fields are shown for each database that is registered with the recovery catalog: DB Key: This is the unique key which identifies this database in the recovery catalog. Inc Key: This is the unique key which identifies this incarnation of the database in the recovery catalog. DB Name: The name of the database. DB ID: The database ID. This is a number which remains the same for the life of the database, even if the database name is changed. Status: 'YES' if this is the current incarnation of this database, otherwise 'NO'. Reset SCN: SCN of the most recent RESETLOGS operation. Reset Time: Time of the most recent RESETLOGS operation. Action: No action is required. RMAN-06250: Report of files that need backup due to unrecoverable operations Cause: An unlogged change (such as 'create table unrecoverable') has been made to this file, and the most recent backup of the file does not contain those changes. Action: Take a backup of this file. If this file is lost before a backup is taken, then the unlogged modifications will be lost. The message indicates whether a full backup is required or whether a incremental backup will suffice. RMAN-06263: string string string Cause: This message is issued in response to the REPORT NEED BACKUP INCREMENTAL command, for those files which would use more than the specified number of incrementals during recovery. Action: To reduce the number of incremental backups which would be used during recovery of this datafile, take a new full backup of this file now. RMAN-06270: Report of files whose recovery needs more than number days of archived logs Cause: This message is issued in response to the REPORT NEED BACKUP DAYS command for those files which need more than the specified number of days' archived logs for recovery. Action: To reduce the number of log files needed for recovery of this datafile, take a new full or incremental backup now. RMAN-06274: Report of files that must be backed up to satisfy number days recovery window Cause: This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS command for those files that must be backed up to satisfy specified retention policy. Action: To satisfy specified recovery window for this datafile, take a new full or incremental backup now. RMAN-06275: invalid number of days specified for report : string days Cause: This message is issued in response to the REPORT NEED RECOVERY WINDOW OF n DAYS or REPORT NEED BACKUP DAYS n command when an invalid number of days was specified in input command. Action: The number of days specified in REPORT command must be greater than zero. RMAN-06280: Report of obsolete backups and copies Cause: This message is issued in response to the REPORT OBSOLETE command. Each of the files listed is obsolete because it is more redundant than the level of redundancy specified in the REPORT command. Action: Depending on your needs, you might need to take new backups. RMAN-06290: Report of database schema for database with db_unique_name string Cause: This message is issued in response to the REPORT SCHEMA command. The report shows the physical schema of the database at the indicated time. The following fields are shown for each datafile and tempfile: File: The file number. Size(MB): The size of the file in mega bytes. Tablespace: The name of the tablespace which contains this file. RB segs: YES if this file is part of a tablespace containing rollback segments, otherwise NO. Datafile/Tempfile Name: The file name. Maxsize(MB): Maximum file size to which file can be extended Action: No action is required. RMAN-06300: Report of files with less than number redundant backups Cause: This message is issued when the REPORT NEED BACKUP REDUNDANCY command is used for those files which have less than the specified number of backups which can be used for recovery. Action: Take another backup of the datafiles listed. RMAN-06306: ==================== Cause: This message is issued in response to a LIST BACKUP DATABASE/TABLESPACE/DATAFILE command when some backups were taken with the PROXY option. If a recovery catalog is in use, then the information comes from the recovery catalog, otherwise it comes from the target database control file. The following fields are shown for each proxy datafile backup. Key: This is the unique key which identifies this proxy backup in the recovery catalog. This value can be used in a CHANGE command to change its status. If the target database control file is being used as the recovery catalog, then this field uniquely identifies this copy in the control file. File: The file number that this file was copied from. Status: This is the status of the file. Possible values are: A - Available U - Unavailable D - Deleted X - Expired Status 'U' will not be used if the target database control file is being used as the recovery catalog. Completion time: This is the date and time when the backup was created. This column will be printed in the default Oracle date format, unless overridden with a NLS_DATE_FORMAT environment variable. Ckp SCN: This is the checkpoint SCN of the backup. The file contains all changes made at or before this SCN. Ckp time: This is the time that the file was last checkpointed. Handle: This is the media manager handle of the proxy backup. Action: No action is required. RMAN-06378: List of Backup Sets Cause: This message is issued in response to a LIST BACKUP command. Action: No action is required. RMAN-06400: database opened Cause: This is an informational message only. Action: No action is required. RMAN-06401: database is already started Cause: A STARTUP command without the FORCE option was issued, but the target database is already started. Action: Use the FORCE option if you want to restart the database. RMAN-06402: Oracle instance shut down Cause: This is an informational message only. Action: No action is required. RMAN-06403: could not obtain a fully authorized session Cause: The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has has been shutdown. Other error messages should identify exactly which database is the problem. Action: Startup the database causing the problem. RMAN-06404: database dismounted Cause: This is an informational message only. Action: No action is required. RMAN-06405: database closed Cause: This is an informational message only. Action: No action is required. RMAN-06406: deleted archived log Cause: This is an informational message only. Action: No action is required. RMAN-06407: auxiliary instance file string deleted Cause: This is an informational message only. Action: No action is required. RMAN-06408: recovery catalog upgraded to version string Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog schema is not changed with each Oracle release. Action: No action is required. RMAN-06409: LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported Cause: LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported. Action: Remove LIKE clause from command. RMAN-06410: cannot use command when channels are allocated Cause: An attempt was made to issue a command that can be used only when there are no allocated channels. Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated. RMAN-06411: backup copies setting out of range (1-4): number Cause: An attempt was made to set backup copies to an invalid value. Action: Use a value in the specified range. RMAN-06412: no proxy copy channel found Cause: A proxy copy was started, but no allocated channel supports proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because all of the allocated channels are of type DISK, which never support proxy copy. Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK or CHANGE commands should be used so that those backups will not be considered for further restores. RMAN-06413: channel string does not support proxy copy Cause: The channel which was specified for this backup or restore does not support proxy copy. This could be because the media management software used by the target database does not support proxy copy, or because the channel is of type DISK, which never supports proxy copy. Action: If this is a backup, then either allocate a non-disk channel, or do not use the PROXY option. If this is a restore, then a channel of the same type which created the proxy backup was allocated, but now does not support proxy copy. If proxy copy is no longer supported by the media management software at the target database, the CROSSCHECK command should be used so that those backups will not be considered for further restores. RMAN-06414: target database COMPATIBLE option does not support proxy copy Cause: PROXY was specified, and the target database uses a media manager that supports proxy copy, but the COMPATIBLE initialization parameter of the target database must be 8.1.0 or greater to create proxy backups. If the database is downgraded to the earlier release that is specified in the COMPATIBLE parameter, then it will no longer be able to restore proxy backups. Action: Either take a non-proxy backup or change the target database COMPATIBLE parameter. RMAN-06415: file string cannot be proxy backed up Cause: The PROXY option was specified, but the media management software used by the target database cannot back up the specified file using proxy copy. If PROXY ONLY was specified, then the backup is terminated. If PROXY was specified, then this file will be placed into a non-proxy backup set. Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of this file. RMAN-06416: PROXY ONLY was specified and some files could not be proxy copied Cause: PROXY ONLY was specified, and some of the files to be backed up could not be backed up by the media management software used by the target database. Message 6415 is issued for each file that cannot be proxy copied. Action: Remove the ONLY option to place the files into a regular backup set, or contact the media management vendor if you believe that the media management software should support proxy copy of these files. RMAN-06417: command not allowed when connected to a virtual private catalog Cause: The command that was entered cannot be used while connected to a virtual private catalog. Action: Connect to the base catalog and re-execute the command. RMAN-06418: proxy incremental backups with level > 0 not supported Cause: PROXY was specified for a non-level-zero incremental backup. Proxy backups may only be full or level 0 backups. Action: Remove one of the conflicting options. RMAN-06419: file string cannot be proxy restored from handle string Cause: The media management software used by the target database indicated that it cannot restore the specified file from the specified backup handle. Action: Consult the media management software documentation to find out why this restriction exists or contact the media management vendor. RMAN-06420: some files could not be proxy restored - aborting restore Cause: Some of the files to be restored could not be restored by the media management software used by the target database. Message 6419 is issued for each file that cannot be restored. Action: Contact the media management vendor if you believe that the media management software should support proxy copy of these files. The CROSSCHECK or CHANGE commands can be used to remove these proxy copies from the catalog to prevent the RESTORE command from trying to restore from them. RMAN-06421: sent command to channel: string Cause: This is an informational message only. Action: No action is required. RMAN-06422: no channels found for SEND command Cause: No channels with the specified names or device types were found. If no channel qualifiers were specified, then no channels were allocated. Action: Specify a different channel type or allocate a channel of the desired type. RMAN-06423: requested limit of number exceeds vendor limit of number Cause: A SETLIMIT CHANNEL command was used to set the backup piece size limit, but the media management software used by the target database cannot create backup pieces that large. Action: Specify a smaller backup piece limit. RMAN-06424: error while looking up proxy copy Cause: An error occurred while looking up the specified proxy copy in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. Ensure that the name or key is entered correctly. If the proxy copy was created when the recovery catalog was not available, then a RESYNC CATALOG must be done to update the recovery catalog. RMAN-06425: <datafile pathname not available> Cause: This is an informational message only. Action: No action is required. RMAN-06426: RECOVERY_CATALOG_OWNER role must be granted to user string Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the USERID that was supplied in the CATALOG connect string does not have the RECOVERY_CATALOG_OWNER role granted as a DEFAULT role. Action: Grant the RECOVERY_CATALOG_OWNER role to the recovery catalog owner. RMAN-06427: recovery catalog already exists Cause: The CREATE CATALOG command cannot be used when the recovery catalog already exists. Action: Use the UPGRADE CATALOG command to upgrade your recovery catalog to the most current release without losing any existing backup data. Use the DROP CATALOG command to remove an existing recovery catalog. RMAN-06428: recovery catalog is not installed Cause: A recovery catalog database connection has been made, but the recovery catalog tables and views have not been installed. Action: If you mis-typed the recovery catalog owner USERID, then correct the USERID and reconnect to the recovery catalog. If this is the first time that you have signed on to Recovery Manager with this recovery catalog owner USERID, then use the CREATE CATALOG command to create the recovery catalog schema. Alternatively, exit RMAN and connect without specifying a recovery catalog connection. RMAN-06429: string database is not compatible with this version of RMAN Cause: The indicated database is not compatible with this version of the Recovery Manager (RMAN). Other messages have also been issued which detail the cause of the error. Action: See the other messages. If the database is CATALOG, then you may be able to use the CREATE CATALOG or UPGRADE CATALOG commands to correct the problem. If the database is TARGET or AUXILIARY, then you must either upgrade the target database or use a newer version of the RMAN executable. RMAN-06430: recovery catalog USERID cannot be SYS Cause: A recovery catalog connection was made to USERID SYS. The recovery catalog must be created in a USERID other than SYS. Action: Specify a different USERID in the CATALOG connect string. RMAN-06431: recovery catalog created Cause: This is an informational message issued by the CREATE CATALOG command. Action: No action is required. RMAN-06432: recovery catalog dropped Cause: This is an informational message issued by the DROP CATALOG command. Action: No action is required. RMAN-06433: error installing recovery catalog Cause: An error was received from the recovery catalog database while it was being installed. Another error message shows the error message from the server. Action: The most common reasons for failure to install the recovery catalog are: - Lack of space in the recovery catalog database: allocate more space, use the DROP CATALOG command to remove any partially installed recovery catalog, and retry the command. - Object already exists: This is caused by a partial recovery catalog installation. Use the DROP CATALOG command to remove the partially installed recovery catalog and retry the command. RMAN-06434: some errors occurred while removing recovery catalog Cause: Some errors were received from the recovery catalog database while removing the recovery catalog. Action: Correct the error(s) and retry the command. Note that Recovery Manager intercepts and ignores common errors, such as 'object not found', which can happen while removing a partially installed recovery catalog. Only serious errors will be displayed while removing the recovery catalog. RMAN-06435: recovery catalog owner is string Cause: This is an informational message issued by the UPGRADE CATALOG and DROP CATALOG commands. Action: No action is required. RMAN-06436: enter DROP CATALOG command again to confirm catalog removal Cause: The DROP CATALOG command deletes the recovery catalog, rendering all database backups unusable, and should be used with care. The command must be entered twice to ensure that this is really what you want to do. Action: If you really want to remove the recovery catalog, then enter the DROP CATALOG command again. RMAN-06437: cannot drop catalog - catalog is newer than this RMAN Cause: The DROP CATALOG command was entered, but the recovery catalog was created by a newer version of the Recovery Manager (RMAN). This version of RMAN may not be able to drop the entire recovery catalog. Action: Use the version of RMAN which most recently created or upgraded the recovery catalog. RMAN-06438: error executing package DBMS_RCVMAN in string database Cause: Recovery Manager requires the DBMS_RCVMAN package in the SYS schema of the indicated database. Normally this package is installed during database creation. To re-create the package, run the files dbmsrman.sql and prvtrmns.plb. Action: re-create the DBMS_RCVMAN package in the SYS schema. RMAN-06439: RMAN must be upgraded to version string to work with this package Cause: This message indicates the minimum version of recovery manager required to use the package which was specified in message 6191. Action: A newer version of RMAN must be used with this package. RMAN-06440: virtual catalog dropped Cause: This is an informational message issued by the DROP CATALOG command, when connected to a virtual private catalog. Note that dropping a virtual private catalog does not delete any data, because the catalog data is owned by the base catalog. Action: No action is required. RMAN-06441: cannot upgrade catalog - catalog is already newer than this RMAN Cause: The recovery catalog is already at a version level that is greater than this version of the Recovery Manager. The UPGRADE CATALOG command is not needed. Action: Either upgrade to a more recent Recovery Manager, or continue to use the current version. Message 6191 will be issued if the recovery catalog is too new to work with this version of Recovery Manager. RMAN-06442: enter UPGRADE CATALOG command again to confirm catalog upgrade Cause: The UPGRADE CATALOG command alters the recovery catalog schema. Although the recovery catalog is designed to be compatible with older versions of the Recovery Manager (RMAN), it is possible that an upgrade will remove support for older versions of RMAN. Action: If you really want to upgrade the recovery catalog, then enter the UPGRADE CATALOG command again. If you are not going to use an older version of RMAN with this recovery catalog, then compatibility is not an issue. If you plan to also continue using an older version of RMAN with this recovery catalog then, before upgrading, consult the Migration Guide for the current Oracle release to determine if upgrading to the current version of the recovery catalog will remove support for older versions of RMAN. RMAN-06443: error upgrading recovery catalog Cause: An error was received from the recovery catalog database while upgrading the recovery catalog. Action: Correct the error and retry the command. Note that the Recovery Manager intercepts and ignores common errors, such as 'column already exists,' which can happen if the recovery catalog has already been partially upgraded. Only serious errors will be displayed while upgrading the recovery catalog. RMAN-06444: error creating string Cause: During the CREATE CATALOG or UPGRADE CATALOG command, the indicated object could not be created due to errors. Action: Make sure that the RECOVER.BSQ file has not been modified or damaged, and then if this error persists, contact Oracle support. If the error refers to one of the RMAN PL/SQL packages, connect to the recovery catalog owner and query the USER_ERRORS view to find out the details of the compilation errors. RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been used Cause: The CONNECT CATALOG command was used after the user had already specified the NOCATALOG option. Action: Re-start rman if you wish to use a recovery catalog. RMAN-06446: changed proxy copy unavailable Cause: This is an informational message only. Action: No action is required. RMAN-06447: changed proxy copy available Cause: This is an informational message only. Action: No action is required. RMAN-06448: uncataloged proxy copy Cause: This is an informational message only. Action: No action is required. RMAN-06449: deleted proxy copy Cause: This is an informational message only. Action: No action is required. RMAN-06450: crosschecked proxy copy: found to be 'string' Cause: This is an informational message only. Action: No action is required. RMAN-06451: proxy copy handle=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-06452: string package upgraded to version string Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version to which the indicated package was just upgraded. Note that this version number may not reflect the version number of your rman executable or target database, because the recovery catalog packages are not changed with each Oracle release. Action: No action is required. RMAN-06453: RECOVERABLE may only be used with datafile objects Cause: An attempt was made to use LIST ... RECOVERABLE .. with OF CONTROLFILE or OF ARCHIVELOG. Action: Remove the RECOVERABLE keyword and try again. RMAN-06454: duplexed backups require Enterprise Edition Cause: The SET COPIES or CONFIGURE BACKUP COPIES command was used to create more than one copy of each backup piece, but Enterprise Edition is not installed. Action: Do not attempt to create more than one copy of each backup piece. RMAN-06455: Tablespace Point-in-Time Recovery requires Enterprise Edition Cause: Tablespace Point-in-Time Recovery was attempted, but Enterprise Edition is not installed. Action: Do not attempt Tablespace Point-in-Time Recovery. RMAN-06456: command is obsolete Cause: This is an informational message only. Action: No action is required. RMAN-06457: UNTIL SCN (string) is ahead of last SCN in archived logs (string) Cause: UNTIL SCN cannot be more than the last SCN of the last archived log Action: Check the UNTIL SCN. RMAN-06458: AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST Cause: The RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST was specified with AS COPY. Action: Remove the AS COPY option and resubmit the command. RMAN-06459: BACKUP <VALIDATE|DURATION> is not supported with PROXY Cause: BACKUP <VALIDATE|DURATION> and PROXY were specified in the same backup command. Action: Remove the incompatible option. RMAN-06460: control file copy string cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message. RMAN-06461: current control file cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of control file is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message. RMAN-06462: no backup sets found on device DISK that match specification Cause: A backup set record specifier did not match an backup set on device DISK in the recovery catalog. Action: Resubmit the command with a different backup set record specifier. The rman LIST command can be used to display all backup sets that Recovery Manager knows about. RMAN-06463: Backup set key string cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of backup set is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message. RMAN-06464: BACKUP BACKUPSET is not supported with VALIDATE option Cause: BACKUP BACKUPSET and VALIDATE were specified in the same backup command. Action: To VALIDATE BACKUPSET use 'validate' or 'restore validate' command. RMAN-06465: configuration not implemented: string Cause: The configuration is not implemented in the current release. Action: Avoid using the command. RMAN-06466: error parsing configuration string (string) Cause: Unsupported configuration string is stored in recovery catalog or target database control file. Action: Check compatibility matrix rman executable and target database and recover catalog. Use DBMS_BACKUP_RESTORE.DELETECONFIG to remove problematic configuration. RMAN-06467: could not translate DBA: number Cause: An error was received when calling DBMS_RCVMAN Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06468: Invalid Data Block Address: number Cause: The DBA specified doesn't belong to the mentioned tablespace Action: Check the DBA RMAN-06469: could not translate corruption list Cause: An error was received when calling DBMS_RCVMAN Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-06470: DEVICE TYPE is supported only when automatic channels are used Cause: The DEVICE TYPE option was specified with a BACKUP, RESTORE, RECOVER, DUPLICATE, CHANGE, VALIDATE, CROSSCHECK, or DELETE EXPIRED command. This option is allowed only when automatically allocated channels are used. Action: Remove the DEVICE TYPE option and re-run the command. Or Remove all ALLOCATE commands and re-run the script so that channels are automatically allocated. RMAN-06471: no configuration found to allocate channels for string Cause: Device type configuration was not found in recovery catalog Action: Setup device type configuration using configure command for required device type RMAN-06472: channel id string is automatically allocated Cause: Channel id was used on ALLOCATE/RELEASE command. Action: Use other channel id that does not belong to reserved channel id's name space RMAN-06474: maintenance channels are not allocated Cause: RELEASE CHANNEL was used without allocating any maintenance channels. Action: Allocate maintenance channel before executing this command. RMAN-06475: parallelism setting out of range (1-254): number Cause: Parallelism for the device type in CONFIGURE PARALLELISM command is out of range Action: Enter value of parallelism that are within the allowed range. RMAN-06476: channel number out of range (1-254): number Cause: Channel number entered in CONFIGURE CHANNEL command is out of range. Action: Enter channel number within allowed range and retry the command. for this device and retry the command RMAN-06477: configuration value length exceeds 1024 Cause: CONFIGURE CHANNEL command entered has configuration value greater than 1024 bytes. Action: Reduce the length of CONFIGURE CHANNEL command options RMAN-06478: WARNING: datafile copy 'string' cannot be found on disk Cause: The CHANGE DATAFILECOPY AVAILABLE command was used, but the datafile copy cannot be found on disk. Action: If the storage containing the datafile copy has been removed from the host, restore it and retry the command. If the datafile copy is permanently gone, then issue the CHANGE DATAFILECOPY DELETE command for this datafile. RMAN-06479: WARNING: control file copy 'string' cannot be found on disk Cause: The CHANGE CONTROLFILECOPY AVAILABLE command was used, but the control file copy cannot be found on disk. Action: If the storage containing the control file copy has been removed from the host, restore it and retry the command. If the control file copy is permanently gone, then issue the CHANGE CONTROLFILECOPY DELETE command for this control file. RMAN-06480: WARNING: archived log 'string' cannot be found on disk Cause: The CHANGE ARCHIVELOG AVAILABLE command was used, but the archived log cannot be found on disk. Action: If the storage containing the archived log has been removed from the host, restore it and retry the command. If the archived log is permanently gone, then issue the CHANGE ARCHIVELOG DELETE command for this archived log. RMAN-06481: WARNING: backup piece 'string' cannot be found on the storage medium Cause: The CHANGE BACKUPPIECE AVAILABLE command was used, but the backup piece cannot be found on the storage medium. Action: If the storage containing the backup piece has been removed from the host, restore it and retry the command. If the backup piece is permanently gone, then issue the CHANGE BACKUPPIECE DELETE command for this backup piece. RMAN-06482: WARNING: proxy copy 'string' cannot be found on the storage medium Cause: The CHANGE PROXY AVAILABLE command was used, but the proxy copy cannot be found on disk. Action: If the storage containing the proxy copy has been removed from the host, restore it and retry the command. If the proxy copy is permanently gone, then issue the CHANGE PROXY DELETE command for this proxy copy. RMAN-06483: changed datafile copy expired Cause: This is an informational message only. Action: No action is required. RMAN-06484: changed control file copy expired Cause: This is an informational message only. Action: No action is required. RMAN-06485: changed archived log expired Cause: This is an informational message only. Action: No action is required. RMAN-06486: changed backup piece expired Cause: This is an informational message only. Action: No action is required. RMAN-06487: changed proxy copy expired Cause: This is an informational message only. Action: No action is required. RMAN-06488: restore from AUTOBACKUP does not allow any other modifiers Cause: A control file or SPFILE restore from AUTOBACKUP was attempted and other restore options were used. Action: Do not specify any other options for the control file AUTOBACKUP restore. RMAN-06489: no configuration found to allocate clone channel number for device type string Cause: Target channel configuration could not be used for clone channel as it contains CONNECT option. Action: Setup clone channel configuration using CONFIGURE CLONE command for required number and type of channels. RMAN-06490: WARNING: limit of AUTOBACKUPS for the day has been reached Cause: No more control file AUTOBACKUPS are possible in this day. Action: This is a warning message, no action is required. RMAN-06491: control file AUTOBACKUP format "string" contains more than one "string" format specifier Cause: A CONTROLFILE AUTOBACKUP FORMAT cannot have more than one reserved format specifier. Action: Specify only one reserved format specifier or use an alternative format. RMAN-06492: control file AUTOBACKUP format "string" must specify a "string" format specifier Cause: A reserved format specifier was not specified for the CONTROLFILE AUTOBACKUP FORMAT Action: Add a specifier to the CONTROLFILE AUTOBACKUP FORMAT RMAN-06493: only UNTIL TIME clause is allowed when performing a restore from AUTOBACKUP, found: string Cause: For restoring a control file AUTOBACKUP only SET UNTIL TIME can be used. It is not possible to translate the others to a precise day. Action: Specify SET UNTIL TIME to indicate the day to start the restore of a control file AUTOBACKUP. RMAN-06494: string = string is out of range (string-string) Cause: The specified parameter for restoring a control file AUTOBACKUP is out of the valid range. Action: Change the parameter value to a valid number or do not specify it. RMAN-06495: must explicitly specify DBID with SET DBID command Cause: Restore of a control file AUTOBACKUP or ADVISE FAILURE was attempted when the database is not mounted. Action: Specify the DBID of the database using SET DBID or mount the database. RMAN-06496: must use the TO clause when the database is mounted or open Cause: A control file restore was attempted when the database is mounted or open and no alternate destination was specified. Action: Specify an alternate destination with the TO clause or dismount the database. RMAN-06497: WARNING: control file is not current, control file AUTOBACKUP skipped Cause: Control file AUTOBACKUP is not possible without a current control file. Action: This is a warning message, no action is required. RMAN-06498: skipping datafile string; already backed up string time(s) Cause: The indicated datafile will not be included in the backup set. It is already backed up on the device requested and file is offline/read-only datafile. Use the FORCE option to override backup optimization. Action: No action is required. RMAN-06499: skipping archived log file string; already backed up string time(s) Cause: The indicated log file will not be included in the backup set because it is already backed up on the device requested. Use FORCE option to override backup optimization. Action: No action is required. RMAN-06500: skipping backup set key string; already backed up string time(s) Cause: The indicated backup set will not be copied because it is already backed up on the device requested. Use FORCE option to override backup optimization. Action: No action is required. RMAN-06501: skipping datafile string; already backed up on string Cause: The indicated datafile will not be included in the backup set. It is already been backed up once, or before the since time specified. Action: No action is required. RMAN-06502: skipping archived log file string; already backed on string Cause: The indicated log file will not be included in the backup set. It is already been backed up once, or before the since time specified. Action: No action is required. RMAN-06503: skipping backup set key string; already backed up on string Cause: The indicated backup set will not be backed up. It has already been backed up on the device once, or before the since time specified. Action: No action is required. RMAN-06504: PROXY option with multiple backup copies is not supported Cause: Multiple backup copies and PROXY option were specified in BACKUP command. Action: Resolve the conflict. RMAN-06506: the MAXSETSIZE option cannot be used with a backup backup set Cause: The MAXSETSIZE option was specified for a backup backup set command. Action: Remove the option and resubmit the command. RMAN-06507: trying alternate file for archived log of thread number with sequence number Cause: This is an informational message, appearing when an archived log was found out of sync with catalog database. Action: No action is required. RMAN-06508: MAXSETSIZE string KBYTES should be greater than block size string bytes Cause: MAXSETSIZE configured or specified in backup command should be greater than database block size. Action: Specify a larger MAXSETSIZE limit. RMAN-06509: only SPFILE or control file can be restored from AUTOBACKUP Cause: A datafile or archived log restore from AUTOBACKUP was attempted. Action: Do not specify DATAFILE or ARCHIVELOG for restore from AUTOBACKUP. RMAN-06510: RMAN retention policy is set to recovery window of number days Cause: This is an informational message only. Action: No action is required. RMAN-06511: RMAN retention policy is set to redundancy number Cause: This is an informational message only. Action: No action is required. RMAN-06512: copy will be obsolete on date string Cause: This is an informational message only. Action: No action is required. RMAN-06513: copy will never be obsolete Cause: This is an informational message only. Action: No action is required. RMAN-06514: archived logs required to recover from this copy will not be kept Cause: This is an informational message only. Action: No action is required. RMAN-06515: archived logs required to recover from this copy will expire when this copy expires Cause: This is an informational message only. Action: No action is required. RMAN-06516: time specified in KEEP UNTIL clause must be be after today Cause: KEEP UNTIL support only a future time. Action: Correct the time and retry the command. RMAN-06517: KEEP option is not supported for archived log backups Cause: The KEEP option is not supported for archived logs. Action: Either remove KEEP option and retry the command or don't specify archived logs for this backup. RMAN-06518: backup will be obsolete on date string Cause: This is an informational message only. Action: No action is required. RMAN-06519: backup will never be obsolete Cause: This is an informational message only. Action: No action is required. RMAN-06520: archived logs will not be kept or backed up Cause: This is an informational message only. Action: No action is required. RMAN-06521: archived logs required to recover from this backup will expire when this backup expires Cause: This is an informational message only. Action: No action is required. RMAN-06522: KEEP FOREVER option is not supported without the recovery catalog Cause: The KEEP FOREVER option was used, but it requires a connection to a recovery catalog database. The KEEP FOREVER option cannot be used when the backup repository is the target database control file. This is because information about this backup cannot be permanently stored. (If information is stored just in the control file it will be aged out depending on CONTROL_FILE_RECORD_KEEP_TIME initialization parameter.) Action: If a recovery catalog database is available, then connect to the recovery catalog and retry the command, otherwise use a different KEEP option. 6523, 1, "unused" RMAN-06524: RMAN retention policy will be applied to the command Cause: This is an informational message only. Action: No action is required. RMAN-06525: RMAN retention policy is set to none Cause: Command DELETE OBSOLETE and REPORT OBSOLETE requires that either: * RMAN retention policy is not NONE or, * RMAN retention policy is specified with REPORT/DELETE command. Action: Either configure RMAN retention policy with CONFIGURE command or specify it at the end of DELETE/REPORT command. RMAN-06526: KEEP option cannot be used with incremental backup Cause: The KEEP option was specified for a incremental backup. Action: Remove the option and resubmit the command. RMAN-06527: KEEP option is not supported for backup of backup sets Cause: The KEEP option is not supported for backup of backup sets. Action: Either remove KEEP option and retry the command or don't specify backup sets for this backup. RMAN-06528: CHANGE ... KEEP not supported for BACKUPPIECE Cause: The CHANGE BACKUPPIECE ... KEEP command was entered. KEEP attributes cannot be specified for backup pieces. Action: Use CHANGE BACKUPSET ... KEEP instead. RMAN-06529: CHANGE ... KEEP not supported for ARCHIVELOG Cause: The CHANGE ARCHIVELOG ... KEEP command was entered. KEEP attributes cannot be specified for archived logs. Action: Use CHANGE BACKUPSET ... KEEP instead. RMAN-06530: CHANGE ... KEEP LOGS not supported for backup set which contains archived logs Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET contains archived logs. Backup sets with archived logs cannot have KEEP attributes. Action: Do not specify backup set with archived logs for the CHANGE BACKUPSET ... KEEP command. RMAN-06531: CHANGE ... KEEP not supported for incremental BACKUPSET Cause: The CHANGE BACKUPSET ... KEEP command was entered, but the BACKUPSET is an incremental backup set. Incremental backup sets cannot have KEEP attributes. Action: Do not specify a backup set with archived logs for the CHANGE BACKUPSET ... KEEP command. RMAN-06532: redundancy count must be greater than zero Cause: The REDUNDANCY operand specified for the retention policy was zero. Action: Specify a REDUNDANCY operand of 1 or greater. RMAN-06533: KEEP ... NOLOGS option cannot be used when datafiles are fuzzy Cause: The KEEP ... NOLOGS option was specified for a backup or copy of files in a fuzzy state. This kind of backup requires archived logs for recovery, so archived logs must be kept. Action: Remove the KEEP ... NOLOGS option or make sure the files are not in a fuzzy state and resubmit the command. RMAN-06534: archived logs required to recover from this backup will be backed up Cause: This is an informational message only. An archivelog backup will be created and kept so the specified backup can be recovered to a consistent state. Action: No action is required. RMAN-06535: LIST COPY OF SPFILE is not supported Cause: LIST COPY OF SPFILE was used, which is not supported because SPFILE cannot have a copy. Action: Remove SPFILE from the command. RMAN-06536: BACKED UP ... TIMES option is supported only for archived logs Cause: The BACKUP UP ... TIMES option was used as a qualifier. This option is supported only for archived logs. Action: Remove the option and resubmit the command. RMAN-06537: CHANGE ... KEEP not supported for BACKUP Cause: The CHANGE BACKUP... KEEP command was entered. KEEP attributes cannot be specified for copies and backup pieces in a single command. Action: Use CHANGE BACKUPSET ... KEEP instead. RMAN-06540: Tablespace string will be excluded from future whole database backups Cause: This is an informational message only. Action: No action is required. RMAN-06541: Tablespace string will be included in future whole database backups Cause: This is an informational message only. Action: No action is required. RMAN-06542: file string is excluded from whole database backup Cause: The indicated file will not be included in the backup set because its tablespace is configured as excluded from backup. Action: No action is required. RMAN-06543: duplicate or conflicting LIST options: string and string Cause: The indicated options conflict with each other or appear more than once in a LIST command. Action: remove the duplicate/conflicting option from the command. RMAN-06544: Do you really want to delete the above objects (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-06545: "string" is an invalid response - please re-enter. Cause: An incorrect response was entered. Action: Enter a correct response. RMAN-06546: Error occurred getting response - assuming NO response Cause: An error occurred reading user response. Action: No action is required, this is an informational message only. RMAN-06547: SYSTEM tablespace cannot be excluded from whole database backup Cause: The SYSTEM tablespace must be included in whole database backup. Action: Remove the SYSTEM tablespace from the CONFIGURE ... EXCLUDE and retry the operation. RMAN-06548: connected to auxiliary database: string (DBID=string) Cause: This is an informational message only. Action: No action is required. RMAN-06549: connected to auxiliary database: string (not mounted) Cause: This is an informational message only. Action: No action is required. RMAN-06550: clone database not mounted and db_name not set in init.ora Cause: The clone database "init.ora" file does not specify the DB_NAME parameter. Action: Add the DB_NAME parameter to the clone database "init.ora" and restart the instance. RMAN-06551: error while looking up datafile copy for file number: string Cause: An error occurred while looking up the specified datafile copy in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure. If the datafile copy was created during a RESTORE with a new name, ensure that the RESTORE completed successfully. RMAN-06552: newname for datafile number was set to NEW, but file was not restored Cause: A SWITCH command was specified for a datafile, but the newname was set to NEW and the file was not restored. If newname is set to NEW, the file must be restored before issuing a SWITCH command. Action: Correct and resubmit the SWITCH command. RMAN-06553: DB_CREATE_FILE_DEST must be set for SET NEWNAME ... TO NEW Cause: The SET NEWNAME ... TO NEW option was specified but the OMF destination init parameter DB_CREATE_FILE_DEST is not set. Action: Supply a full name to the SET NEWNAME command or set DB_CREATE_FILE_DEST at the target database. RMAN-06554: WARNING: file string is in backup mode Cause: A file which is being backed up or copied is in backup mode. RMAN will back up the file anyway, but files do not need to be put into backup mode before backing them up with RMAN. Action: Use the ALTER TABLESPACE ... END BACKUP statement, at the target database server, to take the files out of backup mode. RMAN-06555: datafile string must be restored from backup created before string Cause: An incomplete recovery session was started, but the file is in newer than the UNTIL TIME clause. Action: Check the UNTIL TIME clause or restore the file from a sufficient old backup. RMAN-06556: datafile string must be restored from backup older than SCN string Cause: An incomplete recovery session was started, but the file is newer than the UNTIL clause. Action: Check the UNTIL clause or restore the file from a sufficient old backup. RMAN-06557: unable to restore archived log of thread number with sequence number Cause: Restore of the specified archived log failed because the size of the archived log is larger than available disk space. Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area. RMAN-06558: archived log size of number kb is bigger than available space of number kb Cause: This message should be followed by one or more 6557 messages. Action: Check the accompanying errors. RMAN-06559: MAXSIZE must be larger than 1 kb Cause: The MAXSIZE parameter is out of range. Action: Specify a valid size and retry the command. RMAN-06560: WARNING: backup set with key number will be read number times Cause: This message should be followed by one or more 6562 messages. Action: Check the accompanying messages. RMAN-06561: available space must be larger than number kb Cause: The recovery failed because it requires more disk space. One of the following could have caused this error: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to recovery area, but available disk space is not large enough to restore files. Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area. RMAN-06562: available space of number kb needed to avoid reading the backup set multiple times Cause: A backup set is read more than once. Multiple reads of a backup set can slow restore performance. One of the following could have caused this: 1) The MAXSIZE option is used but is not large enough to restore files. 2) Files should be restored to a recovery area, but the available disk space is not large enough to restore files. Action: One of the following: 1) Increase the MAXSIZE parameter and retry the command. 2) Free up disk space in the recovery area. RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP Cause: RESTORE CONTROLFILE or RESTORE SPFILE was specified without the FROM AUTOBACKUP option when RMAN is not connected to the recovery catalog. Action: If the recovery catalog is available, connect to the recovery catalog and retry the restore. If the recovery catalog in not available, following is the procedure to restore control file or SPFILE: 1. Specify the DBID of the database with the SET DBID command. 2. If the AUTOBACKUP was created with non-default AUTOBACKUP format, then specify the AUTOBACKUP format using the SET CONTROLFILE AUTOBACKUP FORMAT command. 3. If the backup was created with SBT device, then allocate an SBT channel using the ALLOCATE CHANNEL command. 4. Restore control file or SPFILE by starting the RESTORE ... FROM AUTOBACKUP command. RMAN-06564: must use the TO clause when the instance is started with SPFILE Cause: A restore of the SPFILE from AUTOBACKUP was attempted when the instance is started with SPFILE and no alternate destination was specified. Action: Specify an alternate destination with the TO clause. RMAN-06565: WARNING: string: sqlcode number was caught, automatic retry #number Cause: The RMAN client caught a transient error and will automatically retry several times. Action: No action required, this is an informational message. RMAN-06566: target database incarnation not found in control file Cause: RESETLOGS CHANGE# and/or time of the target database doesn't match any database incarnation in the control file. Action: One of the following actions can be taken to resolve this error 1) Restore the control file from the incarnation. 2) To populate the new incarnation, inspect or restore an archived log/datafile/datafile copy/backup set from the target incarnation RMAN-06567: connected to auxiliary database: string (DBID=string, not open) Cause: This is an informational message only. Action: No action is required. RMAN-06568: connected to target database: string (DBID=string, not open) Cause: This is an informational message only. Action: No action is required. RMAN-06570: datafile number switched to datafile copy "string" Cause: This message was issued in response to a SWITCH command. Action: No action is required, this is an informational message. RMAN-06571: datafile number does not have recoverable copy Cause: The SWITCH command with the option TO COPY was specified but the datafile has no valid copy to switch to. Action: Verify whether the datafile has a valid datafile copy. RMAN-06572: database is open and datafile number is not offline Cause: The SWITCH command with the option TO COPY was specified, but datafile is not offline and database is open. Action: Either make sure the datafile is offline or the database must be mounted but not opened. RMAN-06575: platform id number found in datafile string header is not a valid platform id Cause: The platform id found in the datafile header was not recognized. Action: Verify that this is a valid datafile. RMAN-06576: platform 'string' (number) found in header of datafile string does not match specified platform name 'string' (number) Cause: The platform specified in the command did not match the platform found in the datafile header. Action: Specify the correct platform name and retry the command. RMAN-06577: FROM TAG option may only be used with datafile copies Cause: The FROM TAG option was specified for datafiles. Action: Remove the option and resubmit the command. RMAN-06578: INCREMENTAL LEVEL > 0 must be specified with FOR RECOVER OF Cause: The FOR RECOVER OF option was specified without specifying INCREMENTAL LEVEL > 0. Action: Specify INCREMENTAL LEVEL > 0 and resubmit the command. RMAN-06580: the string option cannot be used with AS COPY Cause: The specified option was specified for a backup as copy command. Action: Remove the option and resubmit the command. RMAN-06581: option string not supported Cause: This option was specified and it is not supported. Action: Remove the specified option. RMAN-06582: AS COPY option cannot be used when backing up backup sets Cause: The backup set was specified with AS COPY. Action: Remove the AS COPY option or remove the backup sets. RMAN-06583: at least 1 channel of TYPE DISK must be allocated to use AS COPY option Cause: No channel of TYPE DISK was allocated. Action: Allocate a channel of TYPE DISK and re-issue the command or remove AS COPY. RMAN-06584: WARNING: AS BACKUPSET option added due to allocation of multiple channel types Cause: DISK and non DISK channels were allocated for a backup command. Configuration indicates to produce image copies to DISK, however due to the mixed channel types BACKUPSETS will be created on DISK. Action: Do not allocate non DISK channels to produce image copies to DISK or allocate only non DISK channels to produce BACKUPSETS only. RMAN-06585: no copy of datafile number found Cause: An available datafile copy for the specified datafile could not be found. Action: make sure that all specified datafiles have a copy available. RMAN-06586: no copy of datafile number with tag string found Cause: An available datafile copy for the specified datafile could not be found. Action: make sure that all specified datafiles have a copy available. RMAN-06587: one or more datafile copies were not found Cause: This error message was accompanied by an additional error message or messages indicating the cause of the error. Action: Follow the recommended actions of the additional error message or messages. RMAN-06588: number of patterns (number) to DB_FILE_NAME_CONVERT should be even Cause: An uneven number of patterns was specified. Action: Specify one more or one less pattern. RMAN-06589: cannot specify DB_FILE_NAME_CONVERT option without AS COPY Cause: The DB_FILE_NAME_CONVERT option was specified without AS COPY. This is not permitted for backup set backups where multiple files are combined into a set. Action: Remove the DB_FILE_NAME_CONVERT option and re-run the BACKUP command. RMAN-06590: Tablespace string cannot be converted Cause: The system tablespaces could not be transported to other platforms. Action: Remove the specified tablespace from the CONVERT command and retry the operation. RMAN-06593: platform name 'string' specified in FROM PLATFORM is not valid Cause: The platform name was not recognized. Action: Specify a valid platform name. RMAN-06594: platform name 'string' specified in TO PLATFORM is not valid Cause: The platform name was not recognized. Action: Specify a valid platform name. RMAN-06595: platform name 'string' does not match database platform name 'string' Cause: The platform name specified did not match the name of the database performing the conversion. Action: Specify the correct platform name. RMAN-06596: string requires target database compatibility string, currently set to string Cause: A command or option was used that requires a higher database compatibility than is currently set at the target database. Action: Raise the compatibility of the database before attempting the command again. RMAN-06597: conversion between platforms 'string' and 'string' is not implemented Cause: Conversion of Oracle datafiles between the specified platforms was not supported. Action: Do not do the conversion. RMAN-06599: Tablespace string is not read-only Cause: A conversion was attempted on a tablespace which is not read-only. Action: Change the tablespace to read-only and retry the operation. RMAN-06600: old RMAN configuration parameters: Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06601: new RMAN configuration parameters: Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06604: new RMAN configuration parameters are successfully stored Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06605: old RMAN configuration parameters are successfully deleted Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06606: RMAN configuration parameters are successfully reset to default value Cause: This message is issued in response to a CONFIGURE command. Action: No action is required, this is an informational message only. RMAN-06607: RMAN configuration parameters for database with db_unique_name string are: Cause: This message is issued in response to a SHOW command. Action: No action is required, this is an informational message only. RMAN-06608: RMAN configuration has no stored or default parameters Cause: This message is issued in response to a SHOW command. Action: No action is required, this is an informational message only. RMAN-06609: AS COPY can be configured only for disk device Cause: The AS COPY option was specified for non disk device. Action: Remove the AS COPY option and resubmit the command. RMAN-06610: For record type string RECIDS from number to number are re-used before resync Cause: This messages is issued when the control file records were re-used before resyncing to catalog database. Action: Increase control_file_keep_record_time setting or issue BACKUP command that it will generate fewer control file records, e.g., backup few tablespaces instead of the complete database in one BACKUP command. RMAN-06611: Following RMAN configuration applied before deleting logs: Cause: This message is issued in response to a DELETE command. Action: No action is required, this is an informational message only. RMAN-06612: Incompatible options were specified for archivelog deletion policy Cause: Incompabitle options were specified on CONFIGURE ARCHIVELOG DELETION POLICY command. Action: Remove incompabitle options and retry the command. BACKED UP option can be used individually or combined with SHIPPED or APPLIED option. Following are invalid combination of options: a) TO NONE cannot be used with other options b) SHIPPED ON STANDBY and SHIPPED ON ALL STANDBY cannot be used together. c) APPLIED ON STANDBY and APPLIED ON ALL STANDBY cannot be used together. d) SHIPPED and APPLIED cannot be used together. RMAN-06613: Connect identifier for DB_UNIQUE_NAME string not configured Cause: The connect identifier for the specified DB_UNIQUE_NAME initialization parameter was not configured. Action: Configure the appropriate connect identifier for the DB_UNIQUE_NAME initialization parameter and re-run the command. RMAN-06614: DB_UNIQUE_NAME string is too long Cause: The DB_UNIQUE_NAME initialization parameter string was too long. Action: Configure the appropriate DB_UNIQUE_NAME initialization parameter string and re-run the command. RMAN-06615: resyncing from database with DB_UNIQUE_NAME string Cause: Resync was performed remotely for the specified DB_UNIQUE_NAME initialization parameter without connecting to it as target database. This type of remote resync has limitations. For example, RMAN output cannot be resynced. Please refer to RMAN documentation for a complete set of limitations. Action: This is an informational message. RMAN-06616: RMAN output not resynced for database with DB_UNIQUE_NAME string Cause: V$RMAN_OUTPUT contents were not rescyned when the RESYNC CATALOG FROM DB_UNIQUE_NAME command was executed." Action: This is an informational message. RMAN-06700: error parsing text script in file string Cause: Incorrect syntax or invalid commands were found. Action: Fix text script and retry the command. RMAN-06701: could not construct path for file: "string" Cause: An error was encountered when trying to construct the full pathname for the specified file. Action: Ensure that the path is correct. RMAN-06702: could not initialize for input file: "string" Cause: An error was encountered when trying to initialize the specified file for input. Action: Ensure that the file exists. RMAN-06703: could not open file: "string" (reason=string) Cause: An error was encountered when trying to open the specified file. Action: Ensure that the file has correct permissions. RMAN-06705: text script line is too long (>1024) Cause: A text script contained a line longer than the permitted maximum length. Action: Split the line in smaller lines an retry the operation. RMAN-06706: could not close file: "string" (reason=string) Cause: An error was encountered when trying to close the specified file. Action: Ensure that the file has correct permissions and still exists. RMAN-06707: could not initialize for output file: "string" Cause: An error was encountered when trying to initialize the specified file for output. Action: Ensure that the file exists. RMAN-06708: short write while writing file "string". Wrote string bytes instead of string bytes Cause: An attempt was made to write to a file system that was full. Action: Ensure that the file system has room for the file. Check system logs. RMAN-06709: No scripts in recovery catalog Cause: An attempt was made to list the scripts in the catalog, but no scripts could be found in the specified recovery catalog. Action: No action required, this is an informational message only. RMAN-06710: script string not found in catalog Cause: An attempt was made to call a script that could not be found in the target database or as a global script in the specified catalog. Action: Verify the script name and retry the command. RMAN-06711: global scripts require a target connection Cause: Connection to a target database was not specified. Action: Provide a target connection and retry the command. RMAN-06716: skipping datafile number; already restored to file string Cause: Recovery Manager determined that this file is already restored. Use FORCE option to override this optimization. Action: No action required, this is an informational message only. RMAN-06717: number of source files (string) and destination files (string) does not match Cause: The number of files to retrieve from the catalog does not match the number of destinations specified. Action: Ensure that the number of files to be retrieved matches the number of destinations specified. RMAN-06718: could not find file "string" in catalog Cause: The file name provided was not found in the catalog. Action: The specified file is not stored in the catalog, or it is stored with a different path than the one provided. Specify the file name as stored in the catalog. RMAN-06719: file "string" (string bytes) retrieved from catalog Cause: This is an informational message only. Action: No action is required. RMAN-06720: file "string" removed from catalog Cause: This is an informational message only. Action: No action is required. RMAN-06721: could not normalize path for file: "string" Cause: An error was encountered when trying to normalize the pathname for the specified file. Action: Ensure that the path is correct. RMAN-06722: unable to remove file "string" from catalog Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Follow actions for other messages. RMAN-06723: file "string" (string bytes) updated in catalog Cause: This is an informational message only. Action: No action is required. RMAN-06724: backup not done; all files already backed up Cause: A BACKUP command does not need to backup any files, because all of the files to backup are already backed up. Action: No action required, this is an informational message only. RMAN-06725: database not open: sort area size too small Cause: sort area size too small to execute RMAN commands. Action: open the database or increase sort_area_size. RMAN-06726: could not locate archived log string Cause: The specified archived log could not be found on any allocated channel. Action: Allocate additional channels on other nodes of the cluster, or, if the archived logs have been deleted, use the CROSSCHECK ARCHIVELOG command to correct the recovery catalog entries. RMAN-06727: could not locate datafile copy string Cause: The specified datafile copy could not be found on any allocated channel. Action: Allocate additional channels on other nodes of the cluster, or if the datafile copy have been deleted, use the CROSSCHECK DATAFILECOPY command to correct the recovery catalog entries. RMAN-06728: could not locate control file copy string Cause: The specified control file copy could not be found on any allocated channel. Action: Allocate additional channels on other nodes of the cluster, or if the control file copy have been deleted, use the CROSSCHECK CONTROLFILECOPY command to correct the recovery catalog entries. RMAN-06729: no backup of the SPFILE found to restore Cause: A SPFILE restore could not proceed because no backup of the SPFILE was found. It may be the case that a backup of this file exists but does not satisfy the criteria specified in the user's restore operands. Action: Modify options for the SPFILE restore. RMAN-06730: no channel to restore a backup of the SPFILE Cause: A SPFILE restore could not proceed because the backup on a device type that was not allocated for restore. Action: No action required, this is an informational message only. See message 6026 for further details. RMAN-06731: command string:string% complete, time left number:number:number Cause: This is an informational message only. Action: No action is required. RMAN-06732: database dropped Cause: This is an informational message only. Action: No action is required. RMAN-06733: database unregistered from the recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-06734: Do you really want to drop all backups and the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-06735: Do you really want to drop the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-06736: Do you really want to unregister the database (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-06737: database name "string" does not match target database name "string" Cause: The UNREGISTER DATABASE command was used with a database name that does not match the name of the database to which RMAN is connected. Action: Specify the correct database name or avoid specifying the database name when connected to the target database. RMAN-06738: database name "string" is not unique in the recovery catalog Cause: The UNREGISTER DATABASE command was used with a database name that is ambiguous. Action: Use the SET DBID command to specify the database id and resolve the ambiguity. RMAN-06739: database "string" is not found in the recovery catalog Cause: The UNREGISTER DATABASE command was used with a database name that was not found in the recovery catalog. Action: Make sure the database name specified in the DROP DATABASE command syntax is correct. RMAN-06740: database name is not specified Cause: The command failed because of the following: o RMAN is not connected to the target database o The database name is not specified in the command o DBID is not set with the SET DBID command Action: Any one of the following actions will fix the problem: o Connect to the target database o Specify database name o Set DBID with SET DBID command RMAN-06741: database name is "string" and DBID is string Cause: This is an informational message only. Action: No action is required. RMAN-06742: platform name 'string' longer than number Cause: The specified platform name exceeds the maximum allowable platform name. Action: Correct the platform name. RMAN-06743: specification does not match any backup set in the repository Cause: The specified backup sets are not found in the repository. Action: Verify backup set existence and retry the command. RMAN-06744: specification does not match any datafile copy in the repository Cause: The specified datafile copies are not found in the repository. Action: Verify datafile copy existence and retry the command. RMAN-06745: skipping datafile copy string; already backed up string time(s) Cause: The indicated datafile copy was not included in the backup set because it was already backed up on the device requested. Action: Use FORCE option to override backup optimization. RMAN-06746: backup cancelled because all files were skipped Cause: All files for this backup set were skipped, therefore no backup no backup set was created. Action: This message is informational only. RMAN-06747: at least 1 channel of tertiary storage must be allocated to execute this command Cause: The executed command requires a SBT channel, but no channels of type SBT were configured or allocated. Action: ALLOCATE or CONFIGURE a SBT channel. RMAN-06748: no or more than one tertiary storage channel found Cause: RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST option was specified in BACKUP command, but no or more than one tertiary channel was found. One of the following could have caused this error: 1) All of the allocated channels are of type DISK. 2) No tertiary storage (SBT) channel configured. 3) CHANNEL or DEVICE TYPE option specified is of DISK type. 4) More than one tertiary storage channel allocated or configured and no DEVICE TYPE or CHANNEL option specified. Action: One of the following: 1) Allocate a channel of TYPE SBT. 2) Configure a SBT channel. 3) Specify CHANNEL, DEVICE TYPE option of TYPE SBT. RMAN-06749: restore point string does not exist. Cause: The specified restore point does not exists in v$restore_point table of the target database. Action: Check the name of restore point and retry the command. RMAN-06750: SPFILE cannot be backed up by proxy. Cause: The PROXY option was specified, but proxy copy of SPFILE is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message only. RMAN-06751: ASM file string cannot be proxy backed up. Cause: The PROXY option was specified, but proxy copy of ASM file is not supported. This file will be placed into a non-proxy backup set. Action: No action required, this is an informational message only. RMAN-06752: error while looking up tempfile: string Cause: An error occurred while looking up the specified tempfile in the recovery catalog or target database control file. Action: This error is accompanied by other errors describing the reason for the failure; see those error messages for further information. One possible problem is that the tempfile name was not entered correctly. RMAN-06753: tempfile not found in the repository Cause: The specified tempfile is not found in the control file or recovery catalog. Action: Make sure that the tempfile name is correct and retry RMAN-06754: INCREMENTAL FROM SCN option is not supported with [string] Cause: The INCREMENTAL FROM SCN option was supplied but does not apply to this type of backup. Action: Remove the INCREMENTAL FROM SCN operand and re-enter the command. RMAN-06755: WARNING: datafile string: incremental-start SCN is too recent; using checkpoint SCN string instead 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. RMAN-06756: cannot flashback database to non-guaranteed restore point string when flashback is off Cause: The indicated restore point was not guaranteed and flashback was disabled. When flashback is disabled, Oracle can flashback only to guaranteed restore point. Action: Specify a guaranteed restore point or turn on flashback and retry the command. the command. RMAN-06757: DB_UNIQUE_NAME "string" does not match target database ("string") Cause: The value specified in the FOR DB_UNIQUE_NAME option did not match the DB_UNIQUE_NAME parameter setting of the target database. Action: Use the RMAN STARTUP command, with no parameter file option, to start the target database without a parameter file, then run the RESTORE SPFILE command again. RMAN-06758: DB_UNIQUE_NAME is not unique in the recovery catalog Cause: RMAN could not identify which SPFILE to restore for this target database, because the recovery catalog contained two or more different instances of this database, each with different DB_UNIQUE_NAME values. Action: Use the FOR DB_UNIQUE_NAME option to specify the name of the instance whose parameter file you want to restore. RMAN-06759: skipping datafile copies that are already backed up Cause: Some datafile copies were not be backed up because they were already backed up on the device requested. Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up. RMAN-06760: skipping archived logs that are already backed up Cause: Some archived logs were not be backed up because they were already backed up on the device requested. Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up. RMAN-06761: skipping backup sets that are already backed up Cause: Some backup sets were not be backed up because they were already backed up on the device requested. Action: No action is required. You can use the FORCE option to override backup optimization and force these files to be backed up. RMAN-06762: ignoring encryption for proxy or image copies Cause: This information message is displayed when the RMAN client is generating proxy or image copies and encryption was enabled for the input files. Action: This is an informational message only. RMAN-06763: specified encryption algorithm not supported Cause: An encryption algorithm not supported by the database is specified during backup. Action: Refer to contents of v$rman_encryption_algorithms view for the list of supported encryption algorithm. Specify a valid encryption algorithm and retry the command. RMAN-06764: string Cause: An error occurred when processing user request. Action: None RMAN-06765: Tablespace string will be encrypted in future backup sets Cause: This is an informational message only. Action: No action is required. RMAN-06766: Tablespace string will not be encrypted in future backup sets Cause: This is an informational message only. Action: No action is required. RMAN-06767: Tablespace string will default to database encryption configuration Cause: This is an informational message only. Action: No action is required. RMAN-06768: duplicate or conflicting options are specified: string and string Cause: An error occurred when processing the command because user specified two duplicate options or the two options are not allowed to be used together. Action: Remove one of the above options and retry the command. RMAN-06769: length of password must be greater than zero Cause: Zero length password was specified for encrypted backups. Action: Retry the command using a password with non-zero length. RMAN-06770: backup encryption requires Enterprise Edition Cause: The backup command tried to create encrypted backups, but Enterprise Edition is not installed. Action: Do not create encrypted backups. RMAN-06771: cannot do IMPORT CATALOG after NOCATALOG has been used Cause: The IMPORT CATALOG command was used after the NOCATALOG option was already specified. Action: Restart RMAN and connect to recovery catalog if you wish to IMPORT CATALOG. RMAN-06772: cannot do IMPORT CATALOG before connecting to recovery catalog Cause: The IMPORT CATALOG command was used before connecting to the recovery catalog. Action: Connect to recovery catalog using CONNECT CATALOG command if you wish to IMPORT CATALOG. RMAN-06773: connected to source recovery catalog database Cause: This is an informational message only. Action: No action is required. RMAN-06774: must specify a TNS service name for source recovery catalog database Cause: The connect string does not contain TNS service name. IMPORT CATALOG without TNS service name is not supported. Action: Specify a service name and resubmit the command. RMAN-06775: not connected to source recovery catalog database Cause: IMPORT CATALOG command was issued but no connection to the source recovery catalog database has been established. Action: Resubmit IMPORT CATALOG command with correct connect string. RMAN-06776: source recovery catalog database not started Cause: IMPORT CATALOG command was issued which requires the source recovery catalog to be open. Action: Open the source recovery catalog database and re-submit the command. RMAN-06777: ORACLE error from source recovery catalog database: string Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-06778: WARNING: string: sqlcode number was caught, automatic retry #string Cause: The RMAN client caught a transient error during temporary resource allocate for IMPORT CATALOG command and will automatically retry several times. Action: No action required, this is an informational message. RMAN-06779: import validation complete Cause: This is an informational message only. Action: No action required. RMAN-06780: database unregistered from the source recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-06781: string package version string in source database is not of version string Cause: The catalog schema version of the source recovery catalog is not the same as the target recovery catalog. The two catalog Action: UPGRADE source recovery catalog schema and recovery catalog schema to same version and retry the command. RMAN-06782: Datafile headers of locally managed datafiles need to be updated. Cause: This is an informational message only. Action: No action is required. RMAN-06783: Update of datafile headers of locally managed datafiles finished. Cause: This is an informational message only. Action: No action is required. RMAN-06784: One or more datafile headers of locally managed datafiles were not updated. Cause: Errors prevented the update of one or more datafile headers. Action: See trace file for details of the problem. RMAN-06785: This operation might take some time. Cause: This is an informational message only. Action: No action is required. RMAN-06786: could not read file header for datafile string to do FLASHBACK. Cause: The indicated datafile header could not be read to do FLASHBACK DATABASE. Action: If the database must be taken back in time then a restore and incomplete recovery must be performed. RMAN-06791: changed the DB_UNIQUE_NAME value from string to string Cause: This is an informational message only. Action: No action is required. RMAN-06792: database db_unique_name is "string", db_name is "string" and DBID is string Cause: UNREGISTER DB_UNIQUE_NAME or CHANGE DB_UNIQUE_NAME command was executed, hence RMAN displayed the database information for which DB_UNIQUE_NAME the metadata will be removed/renamed in the recovery catalog. Action: No action required, this is an informational message only. RMAN-06793: database with db_unique_name string unregistered from the recovery catalog Cause: UNREGISTER DB_UNIQUE_NAME command was executed. Action: No action required, this is an informational message only. RMAN-06794: Want to unregister the database with target db_unique_name (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-06795: Flashback database logging is not on. Cause: A FLASHBACK DATABASE command was tried but flashback database logging has not been enabled. Action: Flashback database logging must be enabled via the ALTER DATABASE FLASHBACK ON command before a FLASHBACK DATABASE command can be tried. If the database must be taken back in time then a restore and incomplete recovery must be performed. RMAN-06796: Not enough flashback database log data to do FLASHBACK. Cause: There was not enough flashback database log data to do the FLASHBACK DATABASE. Action: If the database must be taken back in time then a restore and incomplete recovery must be performed. RMAN-06797: Grant succeeded. Cause: This is an informational message issued in response to a GRANT command. Action: No action required. RMAN-06798: Revoke succeeded. Cause: This is an informational message issued in response to a REVOKE command. Action: No action required. RMAN-06799: found eligible base catalog owned by string Cause: When creating a virtual private catalog, an 11g base catalog was found, owned by the specified user, and the currently connected catalog user has been granted privileges on this catalog, and can therefore create a virtual private catalog using this base catalog. This is an informational message issued in response to a CREATE VIRTUAL CATALOG command. Action: No action required. RMAN-06800: found ineligible base catalog owned by string Cause: When creating a virtual private catalog, an 11g base catalog was found, owned by the specified user, and the currently connected catalog user has not been granted any privileges on this catalog. This is an informational message issued in response to a CREATE VIRTUAL CATALOG command. Action: No action required. RMAN-06801: no base catalog found Cause: When trying to create a virtual catalog, either no base catalog was found, or this user has no privilege to create a virtual catalog against any existing base catalog. Action: Establish the correct privileges and re-create the virtual catalog. RMAN-06802: too many eligible base catalogs found Cause: When trying to create a virtual catalog, more than one base catalog was found that is eligible to be the base catalog for this virtual catalog. Action: Revoke privileges so that the current catalog user has privileges on only one base catalog, then re-issue the CREATE VIRTUAL CATALOG command. RMAN-06803: created virtual catalog against base catalog owned by string Cause: A virtual private catalog was created, where the base catalog data is owned by the specified user. This is an informational message issued in response to a CREATE VIRTUAL CATALOG command. Action: No action required. RMAN-06804: Enter value for string: Cause: This is a user prompt. Action: Enter a substitution value to proceed. RMAN-06805: SET NEWNAME command has not been issued for tempfile string Cause: A SWITCH command was specified for a tempfile, but no destination was specified and no SET NEWNAME command has been previously issued for that file. An explicit file to switch to must be specified if no SET NEWNAME command has been issued. Action: Correct and resubmit the SWITCH command. RMAN-06806: compression algorithm not supported Cause: An unsupported compression algorithm was specified for the backup. Action: Query the V$RMAN_COMPRESSION_ALGORITHM view for the list of supported compression algorithms. Specify a valid compression algorithm and retry the command. RMAN-06807: compression algorithm cannot be used because database compatibility is less than string Cause: The compression algorithm is not supported because the current compatibility level of the database is too low. Action: Query the V$RMAN_COMPRESSION_ALGORITHM view for the list of supported compression algorithms. Specify a valid compression algorithm and retry the command. RMAN-06808: SECTION SIZE cannot be used when piece limit is in effect Cause: The SECTION SIZE backup option was used together with the MAXPIECESIZE channel limit. These options are mutually exclusive, because they are independant methods of creating multiple backup pieces with one backup command. Action: Use one option or the other, but not both. RMAN-06899: updating recovery catalog with new database incarnation Cause: The target database has a new incarnation that has not already been seen by the recovery catalog. This usually happens because a Point-in-Time Recovery was done. RMAN has made the necessary updates to the recovery catalog. Action: This is an informational message only. RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row Cause: The routine createRmanStatusRow() or createRmanOutputRow() could add new row into V$RMAN_STATUS or V$RMAN_OUTPUT. Action: Check the associated error messages. If the associated error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows Cause: Informational message only. Action: No action required. RMAN-06902: AS COMPRESSED BACKUPSET option cannot be used when backing up backup sets Cause: The backup set was specified with AS COMPRESSED BACKUPSET. Action: Remove the AS COMPRESSED BACKUPSET option. RMAN-06903: backup of datafile string was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run the BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06904: backup of archived log for thread number with sequence number and starting SCN of string was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06905: backup of backup set key number was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06906: backup of control file was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06907: MINIMIZE LOAD option not allowed for the specified input files Cause: This option was specified in a backup command specification for BACKUP BACKUPSET or BACKUP CURRENT CONTROLFILE command. Action: Remove the MINIMIZE LOAD option and retry the command. RMAN-06908: WARNING: operation will not run in parallel on the allocated channels Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition. Action: None RMAN-06909: WARNING: parallelism require Enterprise Edition Cause: RMAN allocated more than one channel for a job, but the job will not run in parallel on these channels because parallelism require Enterprise Edition. Action: None RMAN-06910: can not invoke parallel recovery for test recovery Cause: Recover database was called with TEST and PARALLEL option Action: Call recover database with either just the TEST or PARALLEL option RMAN-06911: only one PARALLEL or NOPARALLEL clause may be specified Cause: Recover database was called with PARALLEL and NOPARALLEL option Action: Call recover database with either just the PARALLEL or NOPARALLEL option. RMAN-06912: backup of spfile was cancelled Cause: This is an informational message displayed when PARTIAL option of DURATION option was specified on the BACKUP command and backup could not be completed within the given duration time. Action: Run BACKUP command to backup cancelled files, or let the next backup window backup the cancelled files. It should be noted that the files that were skipped in the current job will be given preference to other files for next the BACKUP command with DURATION option. RMAN-06913: validate cancelled because no files to validate Cause: All files for this validate command were skipped, therefore no files to validate. Action: This message is informational only. RMAN-06914: BLOCK string must be greater or equal to BLOCK string Cause: The value of TO block number was less than the value of from block number. Action: Increase the value of TO BLOCK past the value of from BLOCK and retry the command. RMAN-06915: restore point string already exists Cause: The specified restore point already exists on this database. Action: Use LIST RESTORE POINT to see existing names and retry the command with a unique restore point name. RMAN-06920: database string is not open read-only Cause: CONVERT DATABASE attempted on a database that was not open read-only. Action: Open the database in read-only mode and retry the operation. RMAN-06921: Convert database check failed Cause: This database could not be transported because DBMS_TDB.CHECK_DB returned FALSE. Action: None RMAN-06922: External table string.string found in the database Cause: An external table was found in the database. Action: Redefine the table in the transported database. RMAN-06923: Directory string.string found in the database Cause: A directory object was found in the database. Action: Redefine the directory in the transported database. RMAN-06924: BFILE string.string found in the database Cause: A BFILE was found in the database. Action: Redefine the BFILE in the transported database. RMAN-06925: BFILEs are used in the system, please redefine them in the transported database Cause: BFILEs may or may not exist in the database. Automatically performed BFILE check failed because database was open read-only and could not allocate temporary space. This does not affect CONVERT DATABASE operation. Action: Use DBMS_TDB.CHECK_EXTERNAL to perform BFILE check when the database is open in read/write mode. RMAN-06926: User string with string privilege found in password file Cause: Password file was used. Action: Re-create the password file on the target platform using ORAPWD for the transported database. RMAN-06927: Cannot specify NEW DATABASE clause more than once Cause: NEW DATABASE clause specified more than once Action: Remove redundant NEW DATABASE clause and retry the operation. RMAN-06928: Cannot specify ON TARGET PLATFORM clause more than once Cause: ON TARGET PLATFORM clause specified more than once Action: Remove redundant ON TARGET PLATFORM clause and retry the operation. RMAN-06929: Cannot specify TRANSPORT SCRIPT clause more than once Cause: TRANSPORT SCRIPT clause specified more than once Action: Remove redundant ON TARGET PLATFORM clause and retry the operation. RMAN-06930: Cannot specify SKIP clause more than once Cause: SKIP clause specified more than once Action: Remove redundant SKIP clause and retry the operation. RMAN-06931: Cannot specify FROM PLATFORM clause Cause: CONVERT DATABASE command cannot use FROM PLATFORM clause. Action: Change FROM PLATFORM clause and retry. RMAN-06932: Database name 'string' longer than number Cause: The specified database name exceeded the maximum allowable database name length. Action: Correct the database name. RMAN-06933: Transport script name too long Cause: The specified transport script name exceeded the maximum allowable script name length. Action: Correct the script name. RMAN-06934: Format string too long Cause: The specified format string exceeded the maximum allowable format string length. Action: Correct the format string. RMAN-06935: Convert script name too long Cause: The specified convert script name exceeded the maximum allowable script name length. Action: Correct the script name. RMAN-06941: Database must be closed and mounted EXCLUSIVE and RESTRICTED. Cause: DROP DATABASE was attempted while the database was open or not mounted EXCLUSIVE and RESTRICTED. Action: Change the database state to mounted EXCLUSIVE and RESTRICTED. RMAN-06942: OPTION number is invalid; OPTION must be between string and string Cause: An invalid OPTION was used. Action: Change the OPTION argument. RMAN-06943: no automatic repair OPTION number was listed in ADVISE FAILURE Cause: The OPTION specified was not one of the automatic repair options listed by ADVISE FAILURE or there were no options listed by the ADVISE FAILURE command. Action: Change the OPTION argument or resubmit ADVISE FAILURE with a different set of failures. RMAN-06944: contents of repair script: Cause: This is an informational message only. Action: No action is required. RMAN-06945: no repair script present for REPAIRID string Cause: REPAIRID option specified in the command was invalid or the repair script had been purged from Automated Diagnostic Repository. Action: Retry REPAIR FAILURE command with a different OPTION number. RMAN-06946: executing repair script Cause: This is an informational message only. Action: No action is required. RMAN-06947: searching flashback logs for block images until SCN string Cause: Starting the flashback log search for RECOVER...BLOCK command. The log is searched until the indicated SCN. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06948: searching flashback logs for block images Cause: Starting the flashback log search for RECOVER...BLOCK command. The log is searched until the end of the log. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06949: finished flashback log search, restored string blocks Cause: Flashback log search finished for RECOVER...BLOCK command. Action: None. This is an informational message displayed for RECOVER...BLOCK command. RMAN-06950: invalid validate option specified: string Cause: The specified object was invalid with VALIDATE command. Action: Delete the invalid operand. RMAN-06951: repair failure complete Cause: This is an informational message only. Action: No action is required. RMAN-06952: database needs to be restarted Cause: The target database control file was missing. Action: Restart the instance and repair the database. RMAN-06953: no automatic repairs were listed by ADVISE FAILURE Cause: There were no automatic repairs listed by the ADVISE FAILURE command. Action: Choose a different failure, submit ADVISE FAILURE command, and then submit REPAIR FAILURE command. RMAN-06954: REPAIR command must be preceded by ADVISE command in same session Cause: The ADVISE command was not issued in the same session as the REPAIR command. Action: Submit ADVISE command and then submit the REPAIR command in same session. RMAN-06955: Network copies are only supported for image copies. Cause: An attempt was made to specify BACKUP AUXILIARY FORMAT without specifying the AS COPY clause. A network copy is only supported with an image copy. Action: Seek an alternate method of copying the desired files. RMAN-06956: create datafile failed; retry after removing string from OS Cause: An attempt was made to re-create a database file. This attempt failed. Action: If the indicated file already exists, remove the file from operating system and retry the RMAN command. RMAN-07000: List of SPFILE Backups Cause: This message is issued in response to a LIST BACKUP OF SPFILE command. Action: No action is required. RMAN-07025: string is not supported for foreign archived log Cause: The specified option was not supported for foreign archived log. Action: Do not use the specified command for foreign archived log. RMAN-07200: no failures found that match specification Cause: A failure specifier did not match any failures in the Automated Diagnostic Repository. Action: Resubmit the command with a different failure specifier. You can use the LIST FAILURE ALL command in Recovery Manager to display all failures known to RMAN. RMAN-07201: Do you really want to change the above failures (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-07207: changed string failures to HIGH priority Cause: This is an informational message only. Action: No action is required. RMAN-07208: changed string failures to LOW priority Cause: This is an informational message only. Action: No action is required. RMAN-07209: closed string failures Cause: This is an informational message only. Action: No action is required. RMAN-07210: new failures after most recent LIST FAILURE command Cause: New failures were found since last LIST FAILURE command in this RMAN session. Action: No action is required. This is an informational message only. RMAN-07211: failure option not specified Cause: ALL, CRITICAL, HIGH, LOW, or list of failure numbers was not specified. Action: Specify a failure option and resubmit the command. RMAN-07212: skipping failure string because it was CLOSED Cause: The specified failure has been already closed, so ADVISE FAILURE or CHANGE FAILURE cannot be executed on this failure. Action: This is an informational message only. No action is required. RMAN-07213: Mandatory Manual Actions Cause: This is an informational message only. Action: No action is required. RMAN-07215: Automated Repair Options Cause: This is an informational message only. Action: No action is required. RMAN-07220: no manual actions available Cause: This is an informational message only. Action: No action is required. RMAN-07222: ======================= Cause: This is an informational message only. Action: No action is required. RMAN-07251: Repair script: string Cause: This is an informational message only. Action: No action is required. RMAN-07252: ======================== Cause: This is an informational message only. Action: No action is required. RMAN-07253: ======================== Cause: This is an informational message only. Action: No action is required. RMAN-07255: priority change for failure string failed Cause: An attempt was made to change the priority of a child failure. Action: Specify the parent failure ID to change the child failure. RMAN-07256: cannot change priority of child failure Cause: An attempt was made to change the priority of child failure. Action: This message should be followed by one or more 7255 messages. RMAN-07259: string critical failures exist; cannot exclude from ADVISE FAILURE Cause: ADVISE FAILURE was executed for HIGH or LOW priority failures when CRITICAL failures existed. Action: Execute ADVISE FAILURE with the CRITICAL or ALL options. RMAN-07262: no automatic repair options available Cause: This is an informational message only. Action: No action is required. RMAN-07500: searching for all files that match the pattern string Cause: This is an informational message only. Action: No action is required. RMAN-07501: searching for all files in the recovery area Cause: This is an informational message only. Action: No action is required. RMAN-07502: List of Files Unknown to the Database Cause: This message is issued in response to a CATALOG command. Action: No action is required. RMAN-07505: no files found to be unknown to the database Cause: This is an informational message displayed by the CATALOG command. The command either found no files, or all files that matched the specified search pattern were already present in the target database control file. Action: No action is required. RMAN-07506: Do you really want to catalog the above files (enter YES or NO)? Cause: This is a user prompt. Action: Answer the question to proceed. RMAN-07507: cataloging files... Cause: This is an informational message only. Action: No action is required. RMAN-07508: cataloging done Cause: This is an informational message only. Action: No action is required. RMAN-07509: List of Cataloged Files Cause: This message is issued in response to a CATALOG command. Action: No action is required. RMAN-07513: List of Files Which Where Not Cataloged Cause: This message is issued in response to a CATALOG command. Action: No action is required. RMAN-07514: ======================================= Cause: This is an informational message only. Action: No action is required. RMAN-07515: File Name: string Cause: This is an informational message only. Action: No action is required. RMAN-07516: Reason: Error reading Cause: This is an informational message only. Action: No action is required. RMAN-07517: Reason: The file header is corrupted Cause: Either the file is not an Oracle file or the file header is corrupted. Action: Delete the file using OS utility. RMAN-07518: Reason: Foreign database file DBID: string Database Name: string Cause: This is an informational message only. Action: No action is required. RMAN-07519: Reason: Error while cataloging. See alert.log. Cause: This is an informational message only. Action: No action is required. RMAN-07520: Reason: Data pump dump file Cause: This is an informational message only. Action: No action is required. RMAN-07521: cannot create recovery catalog in database version string; version string required Cause: An attempt was made to use a version of the recovery catalog schema that was incompatible with the version of the database. Action: Upgrade the catalog database to at least the required version or install the catalog schema in a different database which is of at least the required version. RMAN-07522: CREATE TYPE privilege must be granted to user string Cause: The CREATE CATALOG or UPGRADE CATALOG command was used, but the USERID that was supplied in the CATALOG connect string does not have the CREATE TYPE privilege granted. Action: Grant CREATE TYPE privilege to the recovery catalog owner. RMAN-07523: List of files in Recovery Area not managed by the database Cause: This message was issued in response to a CATALOG RECOVERY AREA command. Action: No action is required. RMAN-07524: ========================================================== Cause: This is an informational message only. Action: No action is required. RMAN-07525: Reason: File is not a supported file type in Recovery Area Cause: This message should be accompanied by other message(s) indicating the name of file that was not supported in flash recovery area. Any file other than current control file, online log, archived log, RMAN backups and flashback log is not supported in flash recovery area. This is an informational message only. Action: No action is required. RMAN-07526: Reason: File is not an Oracle Managed File Cause: This message should be accompanied by other message(s) indicating the name of file that was not a oracle managed file. This is an informational message only. Action: No action is required. RMAN-07527: Reason: File was not created using DB_RECOVERY_FILE_DEST initialization parameter Cause: This message should be accompanied by other message(s) indicating the name of file that was not created using DB_RECOVERY_FILE_DEST initialization parameter. One of the following scenarios caused this error: 1) This is an archived log file and was created when the LOG_ARCHIVE_DEST_n initialization parameter was set explicitly to flash recovery area location. For example, LOG_ARCHIVE_DEST_1='location=+FRA' where '+FRA' was also your DB_RECOVERY_FILE_DEST value. 2) This is an RMAN backup file and was created in a flash recovery area using the FORMAT option of the BACKUP command. 3) This is an online log file or current control file and was created prior to setting the flash recovery area. 4) This file fits none of the above scenarios and is not supported by the flash recovery area. Action: All of following actions will resolve future occurrences of this error: 1) To create archived logs in flash recovery area, set the LOG_ARCHIVE_DEST_n initialization parameter to 'location=USE_DB_RECOVERY_FILE_DEST'. Do not explicitly set the LOG_ARCHIVE_DEST_n initialization parameter to a flash recovery area location. 2) To create RMAN backups in flash recovery area, do not use the FORMAT option of the BACKUP command. All of following actions will resolve current problem: 1) If this is an archived log file or an RMAN backup file, use the CATALOG command to re-catalog the files. 2) If this is an online log file or a current control file to be managed by the flash recovery area, re-create the file using the DB_RECOVERY_FILE_DEST initialization parameter. RMAN-07528: number of files not managed by recovery area is string, totaling stringB Cause: This message should be accompanied by other message(s) indicating the list of files. Either the files listed are not known to the database or not managed by flash recovery area. The number and size of the files are shown. This is an informational message only. Action: No action is required. RMAN-07529: Reason: catalog is not supported for this file type Cause: The CATALOG command encountered one or more files of types that cannot be cataloged. These file types include online redo logs, flashback logs, block change tracking files, and data pump files. This message will be accompanied by other messages indicating the names of the file's that could not be cataloged. Action: No action is required. RMAN-07530: Reason: This file type is not requested for cataloging Cause: This is an informational message only. Action: No action is required. RMAN-08000: channel string: copied datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08001: restore not complete Cause: All of the backup pieces have been successfully applied, but DBMS_BACKUP_RESTORE package indicates that the restore conversation is not complete. This usually means that the backup set contained corrupt data. Action: Restore the files from a different backup set, if possible. The Recovery Manager CHANGE BACKUPPIECE UNAVAILABLE can be used to prevent Recovery Manager from attempting to restore from the corrupt backup piece(s). RMAN-08002: starting full resync of recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-08003: channel string: reading from backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08004: full resync complete Cause: This is an informational message only. Action: No action is required. RMAN-08005: new incarnation of database registered in recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-08006: database registered in recovery catalog Cause: This is an informational message only. Action: No action is required. RMAN-08007: channel string: copied datafile copy of datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08008: channel string: starting full datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08009: channel string: starting archived log backup set Cause: This is an informational message only. Action: No action is required. RMAN-08010: channel string: specifying datafile(s) in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08011: including current control file in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08012: including control file copy in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08013: channel string: backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08014: channel string: specifying archived log(s) in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08015: datafile string switched to datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08016: channel string: starting datafile backup set restore Cause: This is an informational message only. Action: No action is required. RMAN-08017: channel string: starting archived log restore to default destination Cause: This is an informational message only. Action: No action is required. RMAN-08018: channel string: starting archived log restore to user-specified destination Cause: This is an informational message only. Action: No action is required. RMAN-08019: channel string: restoring datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08020: including standby control file in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08021: channel string: restoring control file Cause: This is an informational message only. Action: No action is required. RMAN-08022: channel string: restoring archived log Cause: This is an informational message only. Action: No action is required. RMAN-08023: channel string: restored backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08025: channel string: copied control file copy Cause: This is an informational message only. Action: No action is required. RMAN-08026: channel string: copied archived log Cause: This is an informational message only. Action: No action is required. RMAN-08027: channel string: copied current control file Cause: This is an informational message only. Action: No action is required. RMAN-08028: channel string: copy current control file failed Cause: This is an informational message only. Action: No action is required. RMAN-08029: snapshot control file name set to default value: string Cause: This is an informational message only. Action: No action is required. RMAN-08030: allocated channel: string Cause: This is an informational message only. Action: No action is required. RMAN-08031: released channel: string Cause: This is an informational message only. Action: No action is required. RMAN-08032: channel string: RECID string STAMP string does not match recovery catalog Cause: The record that identifies the source file for a copy or backup database does not contain the same data as is stored in the recovery catalog. Action: Perform a full resync and retry the operation. If the problem persists, then contact Oracle. RMAN-08033: channel string: including datafile copy of datafile string in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08034: full resync skipped, target database not mounted Cause: This is an informational message only. Action: No action is required. RMAN-08035: partial resync skipped, target database not mounted Cause: This is an informational message only. Action: No action is required. RMAN-08036: channel string: could not create control file record for string string Cause: The record identifying the named file was no longer present in the target database control file, and repeated attempts to inspect the file were unsuccessful in creating the record. This could be because the circular-reuse section of the control file which holds information about the specified type of file is too small and there is other database activity which is causing the record to be overwritten before it can be used. Action: Try increasing either the size of the control file circular-reuse section for this file type (datafile copy or archived log, as indicated in the error message, or the CONTROL_FILE_RECORD_KEEP_TIME initialization parameter. If neither of those remedies works then contact Oracle. RMAN-08037: channel string: unexpected validation return code string Cause: This is an internal error that should never be issued. Action: Contact Oracle Support. RMAN-08038: channel string: starting piece string at string Cause: This is an informational message only. Action: No action is required. RMAN-08039: channel string: starting incremental datafile backup set restore Cause: This is an informational message only. Action: No action is required. RMAN-08040: full resync skipped, control file is not current or backup Cause: This is an informational message only. Action: No action is required. RMAN-08041: partial resync skipped, control file is not current or backup Cause: This is an informational message only. Action: No action is required. RMAN-08042: channel string: copied standby control file Cause: This is an informational message only. Action: No action is required. RMAN-08043: channel string: copy standby control file failed Cause: This is an informational message only. Action: No action is required. RMAN-08044: channel string: finished piece string at string Cause: This is an informational message only. Action: No action is required. RMAN-08045: channel string: finished piece string at string with string copies Cause: This is an informational message only. Action: No action is required. RMAN-08046: channel string: starting compressed full datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08047: channel string: starting compressed incremental level string datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08048: channel string: starting incremental level string datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08049: channel string: starting compressed archived log backup set Cause: This is an informational message only. Action: No action is required. RMAN-08050: cataloged datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08051: cataloged archived log Cause: This is an informational message only. Action: No action is required. RMAN-08052: cataloged control file copy Cause: This is an informational message only. Action: No action is required. RMAN-08053: channel string: finished piece string at string with string copies and tag string Cause: This is an informational message only. Action: No action is required. RMAN-08054: starting media recovery Cause: This is an informational message only. Action: No action is required. RMAN-08056: skipping datafile string because it has not changed Cause: The specified datafile has not had its checkpoint advanced since the previous backup, therefore it does not need a new incremental backup. Action: This is an informational message only. RMAN-08057: channel string: backup cancelled because all files were skipped Cause: All datafiles for this backup were skipped, therefore no backup is created. Action: This is an informational message only. RMAN-08058: replicating control file Cause: This is an informational message only. Action: No action is required. RMAN-08059: media recovery failed Cause: This is an informational message only. Action: No action is required. RMAN-08060: unable to find archived log Cause: This is an informational message only. Action: No action is required. RMAN-08061: WARNING: change failure ID string failed due to error ORA-05number Cause: CHANGE FAILURE for the indicated failure ID encountered an error. Action: See the indicated ORA error message for the cause of the error. RMAN-08066: database reset to incarnation string Cause: This is an informational message only. Action: No action is required. RMAN-08070: deleted datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08071: channel string: deleting archived log(s) Cause: This is an informational message only. Action: No action is required. RMAN-08072: deleted control file copy Cause: This is an informational message only. Action: No action is required. RMAN-08073: deleted backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08074: crosschecked backup piece: found to be 'string' Cause: This is an informational message only. Action: No action is required. RMAN-08085: created script string Cause: This is an informational message only. Action: No action is required. RMAN-08086: replaced script string Cause: This is an informational message only. Action: No action is required. RMAN-08087: channel string: started backup set validation Cause: This is an informational message only. Action: No action is required. RMAN-08088: applied offline range to datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08089: channel string: specifying datafile(s) to restore from backup set Cause: This is an informational message only. Action: No action is required. RMAN-08090: channel string: starting proxy restore Cause: This is an informational message only. Action: No action is required. RMAN-08091: channel string: specifying datafile(s) for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08092: channel string: specifying datafile copy of datafile string for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08093: specifying current control file for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08094: channel string: specifying datafile(s) for proxy restore Cause: This is an informational message only. Action: No action is required. RMAN-08096: channel string: starting validation of datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08097: channel string: starting validation of archived log backup set Cause: This is an informational message only. Action: No action is required. RMAN-08099: specifying standby control file for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08100: channel string: starting proxy validation Cause: This is an informational message only. Action: No action is required. RMAN-08101: channel string: proxy validation complete Cause: This is an informational message only. Action: No action is required. RMAN-08102: channel string: located backup piece: string Cause: This is an informational message only. Action: No action is required. RMAN-08103: channel string: could not locate backup piece: string Cause: This is an informational message only. Action: No action is required. RMAN-08104: input backup set count=string STAMP=string creation_time=string Cause: This is an informational message only. Action: No action is required. RMAN-08105: channel string: backup cancelled because no pieces were found Cause: All backup sets specified has no pieces. Therefore, no backup set is created. Action: This is an informational message only. RMAN-08106: channel string: restoring block(s) Cause: This is an informational message only. Action: No action is required. RMAN-08107: skipping inaccessible backup set count=string STAMP=string Cause: The indicated backup set will not be backed up because one or more pieces of the backup set could not be read, and the SKIP INACCESSIBLE option was specified. Action: No action is required. RMAN-08108: channel string: specifying block(s) to restore from backup set Cause: This is an informational message only. Action: No action is required. RMAN-08109: channel string: restored block(s) from backup piece string Cause: This is an informational message only. Action: No action is required. RMAN-08110: failover to next copy of backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08111: some blocks not recovered: See trace file for details Cause: Some blocks not recovered due to errors. Action: See trace file for details of the problem. RMAN-08112: archived log failover was done on string, check alert log for more info Cause: This is an informational message to indicate the server found a corrupted block in an archived log and had to switch to another copy of the same archived log in an alternate archived log destination to get corresponding un-corrupted block. Action: If backup is done with delete input option, nothing needs to be done. Otherwise delete the archived log that has corrupted block(s) as recovery on applying this log would fail. Alert log contains name of the log that has corrupted block(s). RMAN-08113: including current SPFILE in backup set Cause: This is an informational message only. Action: No action is required. RMAN-08114: channel string: restoring SPFILE to PFILE Cause: This is an informational message only. Action: No action is required. RMAN-08115: channel string: restoring SPFILE Cause: This is an informational message only. Action: No action is required. RMAN-08116: output file name is original SPFILE location Cause: This is an informational message only. Action: No action is required. RMAN-08117: channel string: the AUTOBACKUP does not contain an SPFILE Cause: The requested AUTOBACKUP does not contain a SPFILE. This is because the instance was not started with a SPFILE when the AUTOBACKUP was created. Action: No action is required. RMAN will try three older AUTOBACKUPS before signaling ORA-19687. RMAN-08118: WARNING: could not delete the following archived redo log Cause: The routine deleteArchivedLog() could not delete an archived redo log on the target instance. Action: Check the accompanying file specification and the associated error messages. The file specification indicates what archived redo log on the target instance RMAN was trying to delete and the error messages indicate why RMAN was unable to delete it. Resolve the problem by first confirming that the archived redo log in question has been backed up, do the deletion manually, and then do a crosscheck so that RMAN is aware of the deletion. RMAN-08119: skipping backup piece handle string; already exists Cause: A BACKUP command does not need to backup control file AUTOBACKUP pieces, because they already exists. Action: This is an informational message, no action is required. RMAN-08120: WARNING: archived log not deleted, not yet applied by standby Cause: This is an informational message to alert the user that an archived log that should have been deleted was not as it has not been applied to the standby database. The next message identifies the archived log Action: Archivelog can be deleted after it has been applied to standby database. RMAN-08121: keep attributes for the backup are deleted Cause: This is an informational message only. Action: No action is required. RMAN-08122: keep attributes for the backup are changed Cause: This is an informational message only. Action: No action is required. RMAN-08123: keep attributes for the datafile/control file copy are deleted Cause: This is an informational message only. Action: No action is required. RMAN-08124: keep attributes for the datafile/control file copy are changed Cause: This is an informational message only. Action: No action is required. RMAN-08125: keep attributes for the proxy copy are deleted Cause: This is an informational message only. Action: No action is required. RMAN-08126: keep attributes for the proxy copy are changed Cause: This is an informational message only. Action: No action is required. RMAN-08127: cataloged backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08128: uncataloged backup piece Cause: This is an informational message only. Action: No action is required. RMAN-08129: failover to piece handle=string tag=string Cause: This is an informational message to indicate the server found a corrupted block in a piece and had to switch to another copy of piece to get corresponding un-corrupted block. Action: See alert log for information on corruption block(s) and the name of the piece that has the corrupted block(s). RMAN-08130: failover to copy on device type string Cause: This is an informational message to indicate the RMAN could not successfully restore the database using the specified backups. An attempt was made to restore the datafiles/archived logs/ control file/SPFILE using the same backup set on a different device type. Action: See accompanying additional error messages indicating the cause of the failover. RMAN-08131: channel string: specifying datafile copies to recover Cause: This is an informational message only. Action: No action is required. RMAN-08132: WARNING: cannot update recovery area reclaimable file list Cause: This error should be accompanied by other errors giving the cause of failure to update reclaimable file list. Action: Check the accompanying error. RMAN-08133: channel string: the AUTOBACKUP does not contain a standby control file. Cause: The requested AUTOBACKUP did not contain a standby control file. Action: No action is required, RMAN will try three older AUTOBACKUPS before signaling ORA-19687. RMAN-08135: some corrupt blocks found during conversion of file string Cause: While converting the specified file from one platform to another, some corrupt blocks were discovered in the specified file. Details about the corruption have been written to a server trace file. Action: If these corrupt blocks are unexpected, you may be able to use Block Media Recovery at the source database to fix the problem, then re-convert the files. RMAN-08136: channel string: deleting incremental backup(s) Cause: This is an informational message only. Action: No Action Required. RMAN-08137: WARNING: archived log not deleted as it is still needed Cause: An archived log that should have been deleted was not as it was required by Streams, Data Guard or Guaranteed Restore Point. The next message identifies the archived log. Action: This is an informational message. The archived log can be deleted after it is no longer needed. See the documentation for Data Guard to alter the set of active Data Guard destinations. See the documentation for Streams to alter the set of active streams. See the documentation for Guaranteed restore point for set of active restore points. RMAN-08138: WARNING: archived log not deleted - must create more backups Cause: An archived log that should have been deleted was not as it it did not meet the user specified archive log deletion policy of number of backups required before deleting the logs. Action: This is an informational message. The archived log can be deleted after more backups are created to satify archivelog deletion policy. RMAN-08139: WARNING: archived redo log not deleted, needed for guaranteed restore point Cause: An archived log that should have been deleted was not because it is required for guaranteed restore point. Action: This is an informational message. The archived redo log can be deleted after backups are created or after deleting the guaranteed restore point that requires the log. RMAN-08140: channel string: starting validation of datafile Cause: This is an informational message only. Action: No action is required. RMAN-08141: channel string: specifying datafile(s) for validation Cause: This is an informational message only. Action: No action is required. RMAN-08142: including standby control file for validation Cause: This is an informational message only. Action: No action is required. RMAN-08143: including current control file for validation Cause: This is an informational message only. Action: No action is required. RMAN-08144: channel string: validation complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08145: channel string: starting validation of archived log Cause: This is an informational message only. Action: No action is required. RMAN-08146: channel string: specifying archived log(s) for validation Cause: This is an informational message only. Action: No action is required. RMAN-08150: created global script string Cause: This is an informational message only. Action: No action is required. RMAN-08151: replaced global script string Cause: This is an informational message only. Action: No action is required. RMAN-08152: global script string written to file string Cause: This is an informational message only. Action: No action is required. RMAN-08153: deleted global script: string Cause: This is an informational message only. Action: No action is required. RMAN-08154: deleted script: string Cause: This is an informational message only. Action: No action is required. RMAN-08155: printing stored global script: string Cause: This is an informational message only. Action: No action is required. RMAN-08156: printing stored script: string Cause: This is an informational message only. Action: No action is required. RMAN-08157: script string written to file string Cause: This is an informational message only. Action: No action is required. RMAN-08158: executing script: string Cause: This is an informational message only. Action: No action is required. RMAN-08159: executing global script: string Cause: This is an informational message only. Action: No action is required. RMAN-08160: script commands will be loaded from file string Cause: This is an informational message only. Action: No action is required. RMAN-08161: contents of Memory Script: Cause: This is an informational message only. Action: No action is required. RMAN-08162: executing Memory Script Cause: This is an informational message only. Action: No action is required. RMAN-08163: validation succeeded for backup piece Cause: The VALIDATE HEADER option determined that the backup piece still matches its data. Action: None - this is an informational message. RMAN-08164: validation succeeded for proxy copy Cause: The VALIDATE HEADER option determined that the proxy copy still matches its data. Action: None - this is an informational message. RMAN-08165: could not locate proxy copy string Cause: The specified proxy copy could not be found on proxy channel. Action: If the proxy copy have been deleted, use the CROSSCHECK BACKUP command to correct the recovery catalog entries. RMAN-08166: validation succeeded for datafile copy and control file copy Cause: The VALIDATE HEADER option found that the datafile copy and controlfile copy still matches its data in the recovery catalog. Action: None - this is an informational message. RMAN-08180: channel string: restore complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08181: media recovery complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08182: channel string: validation complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08183: channel string: block restore complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08184: added tempfile string to tablespace string in control file Cause: This is an informational message only. Action: No action is required. RMAN-08185: renamed tempfile string to string in control file Cause: This is an informational message only. Action: No action is required. RMAN-08186: tempfile string size altered in control file Cause: One of tempfile size attributes AUTOEXTEND, MAXSIZE, NEXTSIZE was altered. This is an informational message only. Action: No action is required. RMAN-08187: WARNING: media recovery until SCN string complete Cause: Media recovery was completed until the indicated SCN because the database was in NOARCHIVELOG mode. Action: This is an informational message only. No action is required. RMAN-08190: validate found one or more corrupt blocks Cause: Backup validate found that one or more blocks were corrupt in the specified datafiles. This message should be followed by 8191 message. Action: Repair them at your earliest convenience. RMAN-08191: See trace file string for details Cause: This is an informational message only. Action: No action is required. RMAN-08300: Run SQL script string on the target platform to create database Cause: This is an informational message only. Action: No action is required. RMAN-08301: Edit init.ora file string. This PFILE will be used to create the database on the target platform Cause: This is an informational message only. Action: No action is required. RMAN-08302: Run RMAN script string on target platform to convert datafiles Cause: This is an informational message only. Action: No action is required. RMAN-08303: To recompile all PL/SQL modules, run utlirp.sql and utlrp.sql on the target platform Cause: This is an informational message only. Action: Transport script invokes utlirp.sql and utlrp.sql. RMAN-08304: To change the internal database identifier, use DBNEWID Utility Cause: This is an informational message only. Action: Transport script does not invoke DBNEWID Utility automatically. RMAN-08305: channel string: starting to check datafiles Cause: This is an informational message only. Action: No action is required. RMAN-08306: channel string: datafile checking complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08500: channel string: SID=string device type=string Cause: This is an informational message only. Action: No action is required. RMAN-08501: output file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08503: piece handle=string comment=string Cause: This is an informational message only. Action: No action is required. RMAN-08504: input archived log thread=string sequence=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08505: output file name=string Cause: This is an informational message only. Action: No action is required. RMAN-08506: input file name=string Cause: This is an informational message only. Action: No action is required. RMAN-08507: input datafile copy RECID=string STAMP=string file name=string Cause: This is an informational message only. Action: No action is required. RMAN-08508: archived log destination=string Cause: This is an informational message only. Action: No action is required. RMAN-08509: destination for restore of datafile string: string Cause: This is an informational message only. Action: No action is required. RMAN-08510: archived log thread=string sequence=string Cause: This is an informational message only. Action: No action is required. RMAN-08511: piece handle=string tag=string Cause: This is an informational message only. Action: No action is required. RMAN-08512: waiting for snapshot control file enqueue Cause: This is an informational message only. Action: No action is required. RMAN-08513: datafile copy file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08514: archived log file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08515: archived log file name=string thread=string sequence=string Cause: This is an informational message only. Action: No action is required. RMAN-08516: control file copy file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08517: backup piece handle=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08518: channel string: scanning control file copy string Cause: This is an informational message only. Action: No action is required. RMAN-08519: channel string: scanning datafile copy string Cause: This is an informational message only. Action: No action is required. RMAN-08520: channel string: scanning archived log string Cause: This is an informational message only. Action: No action is required. RMAN-08521: offline range RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08522: input datafile file number=string name=string Cause: This is an informational message only. Action: No action is required. RMAN-08523: restoring datafile string to string Cause: This is an informational message only. Action: No action is required. RMAN-08524: input control file copy name=string Cause: This is an informational message only. Action: No action is required. RMAN-08525: backing up blocks string through string Cause: This is an informational message only Action: No action is required. RMAN-08526: channel string: string Cause: This is an informational message only. Action: No action is required. RMAN-08527: channel string: starting string proxy datafile backup at string Cause: This is an informational message only. Action: No action is required. RMAN-08528: channel string: proxy copy complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08529: proxy file handle=string Cause: This is an informational message only. Action: No action is required. RMAN-08530: piece handle=string tag=string comment=string Cause: This is an informational message only. Action: No action is required. RMAN-08531: channel string: proxy copy string is string in media management catalog Cause: This is an informational message only. Action: No action is required. RMAN-08532: channel string: restoring block(s) from datafile copy string Cause: This is an informational message only. Action: No action is required. RMAN-08533: restoring blocks of datafile string Cause: This is an informational message only. Action: No action is required. RMAN-08534: channel string: control file restore from AUTOBACKUP complete Cause: This is an informational message only. Action: No action is required. RMAN-08535: channel string: looking for AUTOBACKUP on day: string Cause: This is an informational message only. Action: No action is required. RMAN-08536: channel string: AUTOBACKUP found: string Cause: This is an informational message only. Action: No action is required. RMAN-08537: channel string: skipped, AUTOBACKUP already found Cause: This is an informational message only. Action: No action is required. RMAN-08538: channel string: no AUTOBACKUP in string days found Cause: This is an informational message only. Action: No action is required. RMAN-08539: backup set key=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08540: channel string: backup set complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08541: channel string: SPFILE restore from AUTOBACKUP complete Cause: This is an informational message only. Action: No action is required. RMAN-08542: channel string: starting proxy archived log backup at string Cause: This is an informational message only. Action: No action is required. RMAN-08543: channel string: specifying archived log(s) for proxy backup Cause: This is an informational message only. Action: No action is required. RMAN-08544: channel string: specifying archived log(s) for proxy restore Cause: This is an informational message only. Action: No action is required. RMAN-08545: flashback command failed: See trace file for details Cause: An attempt was made to issue a flashback command which failed due to errors. See trace file for details. Action: See trace file for details of the problem. RMAN-08546: channel string: AUTOBACKUP string found in the recovery area Cause: This is an informational message only. Action: No action is required. RMAN-08547: channel string: no AUTOBACKUPS found in the recovery area Cause: The recovery area does not have desired AUTOBACKUP. Action: Check the option UNTIL TIME in case an existing AUTOBACKUP does satisfy the criteria specified in the restore command. Otherwise, verify the init.ora parameters DB_RECOVERY_FILE_DEST and DB_UNIQUE_NAME to verify whether the recovery area location is set correctly. Note that the parameters can be specified as options to the restore command. RMAN-08548: recovery area destination: string Cause: This is an informational message only. Action: No action is required. RMAN-08549: database name (or database unique name) used for search: string Cause: This is an informational message only. Action: No action is required. RMAN-08550: AUTOBACKUP search with format "string" not attempted because DBID was not set Cause: Restore of a control file AUTOBACKUP was attempted without DBID being set. Action: If you want to search for AUTOBACKUP with the indicated format, then specify the DBID of the database using SET DBID and retry the command. RMAN-08551: recovering datafile copy file number=string name=string Cause: This is an informational message only. Action: No action is required. RMAN-08552: backup and output file names are identical: string Cause: The backup file name chosen was identical to output file name specified for a restore operation. Action: This is an informational message only. RMAN will failover to next available backup. RMAN-08553: channel string: restoring control file from AUTOBACKUP string Cause: This is an informational message only. Action: No action is required. RMAN-08554: channel string: restoring spfile from AUTOBACKUP string Cause: This is an informational message only. Action: No action is required. RMAN-08555: channel string: restoring section string of string Cause: This is an informational message only Action: No action is required. RMAN-08580: channel string: starting datafile copy Cause: This is an informational message only. Action: No action is required. RMAN-08581: channel string: datafile copy complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08582: channel string: starting archived log copy Cause: This is an informational message only. Action: No action is required. RMAN-08583: channel string: archived log copy complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08584: copying current control file Cause: This is an informational message only. Action: No action is required. RMAN-08585: copying standby control file Cause: This is an informational message only. Action: No action is required. RMAN-08586: output file name=string tag=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08587: input is copy of datafile string: string Cause: This is an informational message only. Action: No action is required. RMAN-08588: converted datafile=string Cause: This is an informational message only. Action: No action is required. RMAN-08589: channel string: starting datafile conversion Cause: This is an informational message only. Action: No action is required. RMAN-08590: channel string: datafile conversion complete, elapsed time: string Cause: This is an informational message only. Action: No action is required. RMAN-08591: WARNING: invalid archived log deletion policy Cause: An invalid ARCHIVELOG DELETION POLICY was supplied. The archived log deletion policy was APPLIED but there was no mandatory archived log destinations. Action: One of the following: 1) Change archived log deletion policy using CONFIGURE command 2) Make one or more of standby destination as MANDATORY. RMAN-08599: channel string: throttle time: string Cause: This is an informational message only. Action: No action is required. RMAN-08600: ASM disk group to search: string Cause: This is an informational message only. Action: No action is required. RMAN-08601: channel string: AUTOBACKUP string found in ASM disk group string Cause: This is an informational message only. Action: No action is required. RMAN-08602: channel string: no AUTOBACKUPS found in ASM disk group string Cause: The specified ASM area does not have desired AUTOBACKUP. Action: Check the option UNTIL TIME in case an existing AUTOBACKUP does satisfy the criteria specified in the restore command. Otherwise, verify the values used for the format of the CONFIGURE CONTROLFILE AUTOBACKUP FORMAT command and DB_UNIQUE_NAME to verify whether the ASM area location is set correctly. Note that the DB_UNIQUE_NAME can be specified as option to the restore command. RMAN-08603: skipping string; file in use by another process Cause: The indicated file was not included in the backup because it is part of another restore or delete operation. Action: No action is required. Wait for the other operation to complete, then retry. RMAN-08604: skipping string; file deleted from recovery area to reclaim disk space Cause: The indicated file was not included in the backup because it was deleted from the flash recovery area to reclaim disk space for other operations. Action: No action is required. RMAN-08605: channel string: SID=string instance=string device type=string Cause: This is an informational message only. Action: No action is required. RMAN-08606: WARNING: The change tracking file is invalid. Cause: Backup found changed blocks that were not marked in the change tracking file. See alert log for more information. Action: Do not use any of the incremental backups taken since the last full backup. RMAN-08607: List of remote backup files Cause: RESTORE command detected that one or more remote backup files were required to perform restore operation. Action: Recall the media from remote site that contains the specified backup files before actual restore operation. The message should be accompanied with the list of remote backup files. RMAN-08608: Initiated recall for the following list of remote backup files Cause: This is an informational message displayed when the specified RECALL option of the RESTORE command detected that one or more remote backup files were required to perform the restore operation. The message indicated that RMAN had initiated the request on SBT channel to recall the remote backup files. Action: No action required. RMAN-08609: channel string: starting incremental datafile backup set Cause: This is an informational message only. Action: No action is required. RMAN-08610: channel string: restoring datafile string to string Cause: This is an informational message only. Action: No action is required. RMAN-08611: channel string: piece handle=string tag=string Cause: This is an informational message only. Action: No action is required. RMAN-08612: channel string: failover to duplicate backup on device string Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the datafiles/archived logs/ control file/SPFILE using a previous existing backup. Action: See accompanying additional error messages indicating the cause of the failover. RMAN-08613: channel string: failover to piece handle=string tag=string Cause: This is an informational message to indicate the server found a corrupted block in a backup piece and had to switch to another copy of the piece to get the same block. Action: See alert log for information on corruption block(s) and the name of the backup piece that has the corrupted block(s). RMAN-08614: channel string: errors found reading piece handle=string Cause: This is an informational message to indicate the server found a corrupted block in a backup piece. Accompanying error will describe the action taken. Action: See alert log for more information. RMAN-08615: channel string Cause: This is an informational message to indicate the server could not perform the restore due to the included errors. A least recent backup set will be used to perform the restore. Action: See alert log for information on corruption block(s) and the name of the backup piece that has the corrupted block(s). RMAN-08616: validating blocks string through string Cause: This is an informational message only Action: No action is required. RMAN-08617: validation failed for foreign archived log Cause: The CROSSCHECK FOREIGN ARCHIVELOG command determined that the foreign archived log could not be found or no longer contained the same data, so its record was marked expired. Action: None - this is an informational message. RMAN-08618: validation succeeded for foreign archived log Cause: The CROSSCHECK FOREIGN ARCHIVELOG command determined that the foreign archived log still matches its data. Action: None - this is an informational message. RMAN-08619: foreign archived log file name=string RECID=string STAMP=string Cause: This is an informational message only. Action: No action is required. RMAN-08620: uncataloged foreign archived log Cause: This is an informational message only. Action: No action is required. RMAN-08621: deleted foreign archived log Cause: This is an informational message only. Action: No action is required. RMAN-10000: error parsing target database connect string "string" Cause: An invalid target connect string was supplied. Action: Specify a valid connect string and re-run the job. RMAN-10001: error parsing recovery catalog connect string "string" Cause: An invalid recovery catalog connect string was supplied. Action: Specify a valid connect string and re-run the job. RMAN-10002: ORACLE error: string Cause: The specified Oracle error was received. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-10003: unable to connect to target database Cause: Recovery manager was unable to connect to the target database. This message should be accompanied by other error message(s) indicating the cause of the error. Action: Ensure that that the target database is started, and that the connect string is valid. RMAN-10004: unable to connect to recovery catalog Cause: Recovery manager was unable to connect to the recovery catalog Action: Ensure that that the recovery catalog is started, and that the connect string is valid. This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-10005: error opening cursor Cause: An error was received while trying to open a cursor. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10006: error running SQL statement: string Cause: An error message was received while running the SQL statement shown. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10007: error closing cursor Cause: An error was received while trying to close a cursor. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10008: could not create channel context Cause: An error was received while trying create a channel context. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If the associated Oracle error message indicates a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10009: error logging off of Oracle Cause: An error was received while disconnecting from Oracle. This message should be accompanied by other error message(s) indicating the cause of the error. Action: This is an informational message only. RMAN-10010: error while checking for RPC completion Cause: Recovery Manager's channel context had an error while checking to see if a remote procedure call had completed. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10011: synchronization error while polling for rpc number, action=string Cause: Recovery Manager could not synchronize properly with a remote procedure call. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10012: KGU error: string Cause: An error occurred while initializing the KGU subsystem Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10013: error initializing PL/SQL Cause: An error occurred while initializing the PL/SQL subsystem. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10014: PL/SQL error number on line number column number: string Cause: PL/SQL error Action: The text of this message will be issued by the PL/SQL subsystem. See the PL/SQL error message manual. RMAN-10015: error compiling PL/SQL program Cause: An error occurred while compiling a PL/SQL program. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10018: error cleaning up channel context Cause: An error was received during inter-step cleanup of a channel context. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10020: error initializing Recovery Manager execution layer Cause: An error was received while initializing the Recovery Manager execution layer in preparation for running a job. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10022: error in system-dependent sleep routine Cause: An error was received while waiting for a remote RPC to complete. The error occurred in the system-dependent sleep routine. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10023: RPC attempted to unrecognized package Cause: The Recovery Manager internal RPC router received a package name that it could not understand. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10024: error setting up for rpc polling Cause: The Recovery Manager could not create the RPC polling context which is required to test for RPC completion. This message should be accompanied by other error message(s) indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-10025: connection is already registered for events Cause: The Recovery Manager could not enable the target database connection to test for RPC completion. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10026: network error number-number occurred registering connection Cause: An network error occurred while attempting to register the target database connection to test for RPC completion. Action: This is an internal error that should not be issued. The message numbers are issued by the Sql*Net layer. Contact Oracle Support. RMAN-10027: could not locate network layer context Cause: Recovery Manager could not locate a necessary context area while attempting to register the target database connection to test for RPC completion. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10028: network error number-number occurred during remote RPC Cause: An network error occurred while waiting for a remote RPC to complete. Action: This is an internal error that should not be issued. The message numbers are issued by the Sql*Net layer. Contact Oracle Support. RMAN-10029: unexpected return code number from PL/SQL execution Cause: PL/SQL returned an unexpected return code while executing one channel program. Action: This is an internal error that should not be issued. Contact Oracle Support. RMAN-10030: RPC call appears to have failed to start on channel string Cause: An RPC to a target database instance was issued, but was not observed to start within 5 timeouts. Action: This error is probably accompanied by other error messages giving the precise cause of the failure. RMAN-10031: RPC Error: ORA-number occurred during call to string.string Cause: An RPC to the target database or recovery catalog database encountered an error. Action: This error is accompanied with the error message from the server where the error occurred. RMAN-10032: unhandled exception during execution of job step number: string Cause: An unhandled PL/SQL exception occurred during a job step. Action: This error is accompanied by the error messages describing the exception. RMAN-10033: error during compilation of job step number: string Cause: PL/SQL detected a problem during the compilation of a job step Action: This error message is accompanied by the error messages describing RMAN-10034: unhandled exception during execution of job step number, error unknown Cause: PL/SQL detected an unhandled exception during execution of a job step, but no further information available Action: None RMAN-10035: exception raised in RPC: string Cause: A call to a remote package resulted in an exception. Action: The exception should indicate what went wrong. RMAN-10036: RPC call OK on channel string Cause: This is just an informational message. It should be preceded by message 10030. Action: No action is required. RMAN-10037: RPC anomaly detected on channel string, UPINBLT=number Cause: This is an debugging message and can be ignored. Action: No action is required. RMAN-10038: database session for channel string terminated unexpectedly Cause: The database connection for the specified channel no longer exists. Either the session was terminated by some external means or the channel terminated because of an internal error. Action: Check for an oracle trace file for detailed information on why the session terminated. RMAN-10039: error encountered while polling for RPC completion on channel string Cause: This error should be accompanied by other errors giving the cause of the polling error. Action: Check the accompanying errors. RMAN-10040: asynchronous support not detected, RMAN will run synchronously Cause: The database connection does not support asynchronous operation, so RMAN will not multi-task work among multiple channels. Multiple channels can still be allocated, but they will not run work concurrently. Action: Use a connection type that supports asynchronous operations. RMAN-10041: Could not re-create polling channel context following failure. Cause: The RPC polling context, which is required to test for RPC completion, failed and Recovery Manager could not re-create this channel. This message should be accompanied by other error messages indicating the cause of the error. Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle. RMAN-11000: message number number not found in recovery manager message file Cause: Recovery manager message file is out of date. Action: Make sure that the recovery manager error message file is current and installed in the correct location. RMAN-11001: Oracle Error: string Cause: This is an informational message only. Action: No action is required. RMAN-11002: could not open a cursor to the target database Cause: This is an informational message only. Action: No action is required. RMAN-11003: failure during parse/execution of SQL statement: string Cause: This is an informational message only. Action: No action is required. RMAN-11004: format requires %c when duplexing Cause: SET_DUPLEX=ON was specified, but %c was not part of the format. Action: Include %c in format, or use %U. RMAN-11005: conflicting media information for piece "string" Cause: While restoring the specified backup piece, RMAN received conflicting information about the physical location of the piece from the Media Management software. This can cause poor restore performance. Action: If RMAN does not parallelize the restore from all of the available channels, then you should contact the Media Management vendor. RMAN-11006: WARNING: test recovery results: string Cause: User called recover database with the test option Action: None required RMAN-12000: execution layer initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-12001: could not open channel string Cause: An ALLOCATE CHANNEL command could not be processed. Action: This message should be accompanied by other error message(s) indicating the cause of the error. RMAN-12005: error during channel cleanup Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-12007: cannot allocate more than number channels Cause: The maximum number of RMAN channels has been exceeded. Note that one channel is reserved for RMAN. Action: Allocate fewer channels. Contact Oracle if you have a need for more channels in a single job. RMAN-12008: could not locate backup piece string Cause: There was at least 1 backup set that could not be accessed by any of the allocated channels. Action: Allocate additional channels on other nodes of the cluster RMAN-12009: command aborted because some backup pieces could not be located Cause: Same as 7008. Action: Refer to 7008. RMAN-12010: automatic channel allocation initialization failed Cause: This message should be accompanied by other error message(s) indicating the cause of the error. Action: Check the accompanying errors. RMAN-12011: multiple records for default device type found in catalog Cause: configuration for default device type not consistent. Action: re-run CONFIGURE DEFAULT DEVICE TYPE command to set device type. RMAN-12012: multiple records for string parallelism found in catalog Cause: configuration for device parallelism is not consistent. Action: re-run CONFIGURE PARALLELISM command for device to set parallelism. RMAN-12013: multiple records for string channel number found in catalog Cause: configuration for the channel is not consistent. Action: re-run CONFIGURE CHANNEL command to configure this channel. RMAN-12014: multiple records for default channel configuration for string found in catalog Cause: configuration for the channel is not consistent. Action: re-run CONFIGURE CHANNEL command to configure the channel. RMAN-12015: configuration for string channel number is ignored Cause: This is an informational message only. Parallelism for the device is less than associated channel number. Action: To use this configuration increase parallelism for this device. To clear this configuration use CONFIGURE CHANNEL... CLEAR command. RMAN-12016: using channel string Cause: This is an informational message only. Action: No action is required. RMAN-12017: could not locate pieces of backup set key string Cause: No copies of the specified backup set key can be accessed on any of the allocated channels. Action: Allocate additional channels on other nodes of the cluster, or, if the backup pieces have been deleted, use the CROSSCHECK BACKUP command to correct the recovery catalog entries. RMAN-12018: channel string disabled, job failed on it will be run on another channel Cause: This is an informational message displayed whenever a retryable error occurs for the job and there are channels available to run this step. Action: No action is required. RMAN-12019: continuing other job steps, job failed will not be re-run Cause: This is an informational message displayed whenever there is a non-retryable error occurred for the job. Action: No action is required. RMAN-12020: error on step filtered for normal output string Cause: This message is added when stacking errors for failed jobs after channel failover was performed. It will be filtered from normal output. Action: No action is required. RMAN-20000: abnormal termination of job step Cause: A job step encountered an error and could not recover. This error should be followed by other errors indicating the cause of the problem. Action: Check the accompanying error. RMAN-20001: target database not found in recovery catalog Cause: target database is not found in the recovery catalog Action: make sure that the target database is registered in the recovery recovery catalog RMAN-20002: target database already registered in recovery catalog Cause: target database is already registered in the recovery catalog Action: if the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog. RMAN-20003: target database incarnation not found in recovery catalog Cause: RESETLOGS CHANGE# and/or time of the target database doesn't match any database incarnation in the recovery catalog. Action: if target database was opened with RESETLOGS option then use 'reset database' to register the new incarnation. RMAN-20004: target database name does not match name in recovery catalog Cause: name of the target database doesn't match the one stored in the recovery catalog Action: This is an internal error. RMAN-20005: target database name is ambiguous Cause: two or more databases in the recovery catalog match this name Action: None RMAN-20006: target database name is missing Cause: target database instance is not started or db_name initialization parameter is not set Action: startup the instance and make sure that db_name parameter is set RMAN-20009: database incarnation already registered Cause: this incarnation is already registered in the recovery catalog Action: No action is required. RMAN-20010: database incarnation not found Cause: database incarnation does not match any database incarnation in the recovery catalog Action: specify a valid database incarnation key RMAN-20011: target database incarnation is not current in recovery catalog Cause: the database incarnation that matches the RESETLOGS CHANGE# and time of the mounted target database control file is not the current incarnation of the database Action: If 'reset database to incarnation <key>' was used to make an old incarnation current then restore the target database from a backup that matches the incarnation and mount it. You will need to do 'STARTUP NOMOUNT' before you can restore the control file using RMAN. Otherwise use 'reset database to incarnation <key>' make the intended incarnation current in the recovery catalog. RMAN-20012: not authorized to register new database Cause: You attempted to register a new database with this recovery catalog, but you are using a virtual private catalog, and you have not been granted permission by the catalog administrator to register this database with this recovery catalog Action: Ask the catalog administrator to grant permission for you to register this database. RMAN-20013: error upgrading virtual private catalog Cause: An error occurred while automatically upgrading a virtual private catalog. Action: Ensure that the virtual private catalog userid has all of the required privileges, such as being granted the RECOVERY_CATALOG_OWNER role. RMAN-20014: virtual private catalog owner must be granted RECOVERY_CATALOG_OWNER role Cause: An attempt was made to establish a virtual private RMAN catalog in a schema that is not granted the RECOVERY_CATALOG_OWNER role. Action: Grant RECOVERY_CATALOG_OWNER to the virtual private catalog owner. RMAN-20015: not authorized to share this catalog Cause: You attempted to share a recovery catalog but were not authorized to do this by the catalog administrator. Action: Ask the catalog administrator to grant permission for you to share this catalog. RMAN-20016: virtual private catalog user cannot modify global scripts Cause: A virtual private catalog user attempted to create, delete, or modify a global script. Virtual private catalog users cannot modify global scripts. Action: Connect to the catalog owner userid and retry the global script operation. RMAN-20017: illegal script update operation Cause: An illegal script operation was performed. Action: None RMAN-20018: database not found in recovery catalog Cause: An attempt was made to grant or revoke catalog access to a database whose name was not registered in the recovery catalog. Action: Correct the database name and re-issue the GRANT or REVOKE command. If this is an attempt to grant or revoke access to a database that is not yet registered, then re-issue the command using the database ID of the desired database. RMAN-20019: database name not unique in recovery catalog Cause: An attempt was made to grant or revoke catalog access to a database whose name is not unique in the recovery catalog. Action: Re-issue the command specifying the database ID of the desired database. RMAN-20029: cannot make a snapshot control file Cause: another operation that needs the snapshot control file is in progress Action: try again later if necessary RMAN-20030: resync in progress Cause: this procedure cannot be called while a resync is in progress Action: This is an internal error. RMAN-20031: resync not started Cause: this procedure can only be called in a resync Action: This is an internal error. RMAN-20032: checkpoint CHANGE# too low Cause: the checkpoint change# is less than the one of the previous resync or the checkpoint change# is null Action: make sure that the right control file is used RMAN-20033: control file SEQUENCE# too low Cause: the control file sequence is less than the one of the previous resync Action: make sure that the right control file is used RMAN-20034: resync not needed Cause: the control file has not changed since the previous resync Action: nothing since the recovery catalog is in sync RMAN-20038: must specify FORMAT for CONVERT command Cause: No FORMAT was specified when using CONVERT command. Action: Resubmit the command using FORMAT clause. RMAN-20039: format requires character when duplexing Cause: SET_DUPLEX=ON was specified, but %c was not part of the format. Action: Include %c in format, or use %U. RMAN-20045: must specify FORMAT for BACKUP INCREMENTAL FROM SCN command Cause: No FORMAT was specified when using BACKUP INCREMENTAL FROM SCN command. Action: Resubmit the command using FORMAT clause. RMAN-20079: full resync from primary database is not done Cause: Resync from standby detected that a full resync from primary database is required. One of the following events on primary database may have caused this error: 1) one or more tablespaces or datafiles were added 2) one or more tablespaces or datafiles were dropped 3) one or more datafiles status changed Action: Perform full resync after connecting to primary database. RMAN-20081: change stamp for the record Cause: A record with same recid and stamp is already known to catalog. Action: None. This error is automatically handled by RMAN client by changing the stamp in control file during resync. RMAN-20108: control file for remote database cannot be updated Cause: RESYNC CATALOG FROM DB_UNIQUE_NAME command was attempted, but the control file at the database with DB_UNIQUE_NAME needs to be resynced directly instead of through the current target. Action: Directly connect as target to the remote database with the specified DB_UNIQUE_NAME and resync. RMAN-20109: remote database has different database ID Cause: Command RESYNC CATALOG FROM DB_UNIQUE_NAME was executed and the database ID of the remote database was different than the connected target database. Action: The remote database should have the same database ID as the database connected as the target database. Fix the connect identifier for the remote database and retry the command. RMAN-20201: datafile not found in the recovery catalog Cause: The specified datafile is not found in the recovery catalog Action: make sure that the datafile name is correct and that the recovery catalog is up-to-date RMAN-20202: Tablespace not found in the recovery catalog Cause: the specified tablespace is not found in the recovery catalog Action: make sure that the tablespace name is correct and that the recovery catalog is up-to-date RMAN-20203: translation in progress Cause: this procedure can not be called when name translation is in progress Action: This is an internal error. RMAN-20204: translation not started Cause: GETDATAFILE procedure was called before TRANSLATETABLESPACE Action: This is an internal error. RMAN-20205: incomplete UNTIL clause Cause: The sequence# was NULL Action: This is an internal error. RMAN-20206: log sequence not found in the repository Cause: The specified log sequence does not exists in log history of the current database incarnation Action: check the thread# and sequence# RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time Cause: UNTIL TIME and RECOVERY WINDOW cannot be less than the database creation time or RESETLOGS time. Action: Check the UNTIL TIME or RECOVERY WINDOW. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20208: UNTIL CHANGE is before RESETLOGS change Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change. Action: Check the UNTIL CHANGE. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20209: duplicate datafile name Cause: Two datafiles have the same name Action: This is an internal error. RMAN-20211: FROM TIME is before RESETLOGS time Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time. Action: Check the FROM TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20212: UNTIL CHANGE is an orphan incarnation Cause: Specified UNTIL CHANGE was an orphan incarnation. Action: Check the UNTIL CHANGE or UNTIL RESTORE POINT. If the database needs to be restored or flashed back to an orphan incarnation, use the RESET DATABASE TO INCARNATION command. RMAN-20215: backup set not found Cause: The specified backup set key was not found in the recovery catalog Action: Specify a different backup set key. RMAN-20217: datafile not part of the database Cause: the datafile does not exists or did not exist at until time/scn Action: check the datafile name or number. This is an internal error. for restore database or tablespace. RMAN-20218: datafile not found in recovery catalog Cause: This is an internal error. Action: Contact Oracle Customer Support. RMAN-20220: control file copy not found in the recovery catalog Cause: the specified control file is not in the recovery catalog or it has been marked deleted Action: check the file name RMAN-20221: ambiguous control file copy name Cause: more than one control file copy in the recovery catalog match the specified name. Action: None RMAN-20222: datafile name not found in recovery catalog or is ambiguous Cause: The specified datafile name is not the name of a datafile that is currently part of the target database, or an UNTIL clause has been specified and the file name was for a different datafile at the time specified by the UNTIL clause than it is now. Action: Use a datafile number to specify the datafile you want to RESTORE or RECOVER. RMAN-20230: datafile copy not found in the recovery catalog Cause: the specified datafile is not in the recovery catalog or it has been marked deleted Action: check the datafile copy name or key RMAN-20231: ambiguous datafile copy name Cause: more than one control file copy in the recovery catalog match the specified name. Action: use the datafile copy key to uniquely specify the datafile copy RMAN-20240: archived log not found in the recovery catalog Cause: the specified archived log was not found in the recovery catalog or it has been marked deleted Action: check the archived log name or key RMAN-20241: ambiguous archived log name Cause: more than one archived log in the recovery catalog match the specified name Action: use the archived log key to uniquely specify the archived log RMAN-20243: database db_unique_name is not known to the recovery catalog Cause: the user specified DB_UNIQUE_NAME not known to the recovery catalog. Action: change the database DB_UNIQUE_NAME to a known database value. To display list of known db_unique_names execute LIST DB_UNIQUE_NAME OF DATABASE RMAN-20244: can not change currently connected database db_unique_name Cause: the user specified currently connected DB_UNIQUE_NAME value to unregister. Action: use the DB_UNIQUE_NAME other than connected target database's DB_UNIQUE_NAME value. RMAN-20245: can not specify db_unique_name option in nocatalog mode Cause: the user specified DB_UNIQUE_NAME in nocatalog mode. Action: remove the DB_UNIQUE_NAME option from the command. RMAN-20246: new db_unique_name is already known to the recovery catalog Cause: the user specified known DB_UNIQUE_NAME value when renaming a DB_UNIQUE_NAME in the recovery catalog. Action: change the database DB_UNIQUE_NAME to an known DB_UNIQUE_NAME value; or unregister the new DB_UNIQUE_NAME before renaming an old DB_UNIQUE_NAME value for a database. To display the list of all DB_UNIQUE_NAME for the databases LIST DB_UNIQUE_NAME OF DATABASE command can be executed. RMAN-20250: offline range not found in the recovery catalog Cause: the specified offline was not found in the recovery catalog Action: check that recovery catalog is current RMAN-20260: backup piece not found in the recovery catalog Cause: the specified backup piece is not in the recovery catalog or it has been marked deleted Action: check the backup piece handle or key RMAN-20261: ambiguous backup piece handle Cause: more than one backup piece in the recovery catalog match the specified handle Action: use the backup piece key to uniquely specify the backup piece RMAN-20272: no parent backup found for the incremental backup Cause: no available backup or copy that could be used as the parent of the incremental backup was found in the recovery catalog. Action: take a level 0 backup or copy of the datafile first RMAN-20280: too many device types Cause: more than 8 device types were allocated Action: make sure that the job allocates at most 8 different device types RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVCAT package. Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version. RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVMAN package. Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version. RMAN-20310: proxy copy not found in the recovery catalog Cause: the specified proxy copy is not in the recovery catalog or it has been marked deleted Action: check the proxy copy handle or key RMAN-20311: ambiguous proxy copy handle Cause: more than one proxy copy in the recovery catalog matches the specified handle Action: use the proxy copy key to uniquely specify the proxy copy RMAN-20401: script already exists Cause: a CREATE SCRIPT was issued, but a script with the specified name already exists. Action: use a different name or use REPLACE SCRIPT. RMAN-20501: redo logs from parent database incarnation cannot be applied Cause: A RESTORE or RECOVER of a datafile was requested, but recovery of the datafile would require applying redo logs that were generated before the most recent OPEN RESETLOGS. Action: If a full backup or datafile copy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified. RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK Cause: A DELETE EXPIRED command was run, but the object was actually found to exist. This means the recovery catalog or control file is out of sync with reality. Action: Run CROSSCHECK. RMAN-20503: DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED Cause: A DELETE command was run without EXPIRED option, but the object doesn't exist. This means the recovery catalog or control file is out of sync with reality. Action: Run CROSSCHECK. RMAN-20504: corruption list not found in recovery catalog Cause: corruption list is empty Action: make sure that one or more blocks are marked corrupted in v$copy_corruption and v$backup_corruption and recovery catalog is up-to-date. RMAN-20505: create datafile during recovery Cause: applying of archived log caused a create datafile redo-entry to to terminate recovery. Action: none. This message is never displayed. RMAN automatically detects this case and creates the datafile. RMAN-20506: no backup of archived log found Cause: during the recover process, no backup was found from which the archived logs could be restored. Action: this message should be followed by a list of missing archived logs. Please make the necessary archived log backups available and try again. RMAN-20507: some targets are remote - aborting restore Cause: during the restore process, one or more backup files were unavailable locally for the restore operation. Action: This message should be accompanied with the list of remote backup files. Recall these backups from remote location and retry the RESTORE command. RMAN-20508: temporary resource already in use Cause: Temporary resource that was allocated for IMPORT CATALOG command was already in use. Action: Retry IMPORT CATALOG command. RMAN-20509: temporary resource not found Cause: Temporary resource that was allocated for IMPORT CATALOG command was not found. Action: Retry IMPORT CATALOG command. RMAN-20510: database not found in source recovery catalog database Cause: Database that was specified in IMPORT CATALOG command was not found in the source recovery catalog database. Action: Make sure that the database is registered in the source recovery catalog database. RMAN-20511: database name is ambiguous in source recovery catalog database Cause: Two or more databases in the source recovery catalog database match this name. Action: Use DBID option in IMPORT CATALOG command to specify the source database. RMAN-20512: source database already registered in recovery catalog Cause: Source database was already registered in the recovery catalog. Action: If the source database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog. #################################################################################################### SECTION 7: Some notes on BLOCK CORRUPTION. #################################################################################################### ----- Note: ----- If you use RMAN, you are lucky, because to recover from a corrupt block is then relatively easy. Example: Although datafile media recovery is the principal form of recovery, you can also use the RMAN BLOCKRECOVER command to perform block media recovery. Block media recovery recovers an individual corrupt datablock or set of datablocks within a datafile. In cases when a small number of blocks require media recovery, you can selectively restore and recover damaged blocks rather than whole datafiles. For example, you may discover the following messages in a log or trace file: ORA-01578: ORACLE data block corrupted (file # 7, block # 3) ORA-01110: data file 7: '/oracle/oradata/trgt/tools01.dbf' You can then specify the corrupt blocks in the BLOCKRECOVER command as follows: BLOCKRECOVER DATAFILE 7 BLOCK 3; If using RMAN, that should be your primary method for recovery from block corruption. ----- Note: ----- Traditional, non rman, ways to deal with a corrupt block: Note 1: ======= The most primitive approach would be this: First determine the object where the block belongs to. This is relatively easy, if you use DBA_SEGMENTS in the following way. In the errormessage, you have the file# and block-id. For example: ORA-01578: ORACLE data block corrupted (file # 9, block # 133) So now try to find out which segment (table, index) is involved: SELECT SEGMENT_TYPE, SEGMENT_NAME FROM DBA_EXTENTS WHERE FILE_ID = 9 AND 133 BETWEEN BLOCK_ID AND BLOCK_ID+BLOCKS -1; If it's an index, you can drop and recreate the index again. If it's a table, at least you know which table is involved. - You might have a recent 'export' from which you can recreate the data. - Or you can restore a recent backup on another Server (or instance) and retrieve the tabledata from there. - Or if the table has a unique index: . Just query the table and let the output spool to a file. . You will run into the error, but you have already some data. . Also note what the value of unique key was, at the last spooled record. . Now query again, and spool to a file, and now you use a WHERE clause where the value of the unique key is a couple of values "above" the unique key where the error occurred. Your query will probably start just "after" the bad block. This way, you should be able to "salvage" most of the data. - Or try to see what you can do with the DBMS_REPAIR package. For way better methods, see the next notes. Note 3: ======= Subject: Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g Doc ID: 28814.1 Type: BULLETIN Modified Date : 02-NOV-2008 Status: PUBLISHED Handling Block Corruptions in Oracle7 / 8 / 8i / 9i / 10g Contents Introduction Overview of Steps to handle a Corruption Corruption due to NOLOGGING or UNRECOVERABLE (1) Determine the Extent of the Corruption Problem (2) Replace or Move Away from Suspect Hardware (3) Which Objects are Affected ? Options for various Segment Types: CACHE CLUSTER INDEX PARTITION INDEX LOBINDEX LOBSEGMENT ROLLBACK TABLE PARTITION TABLE TEMPORARY IOT TYPE2 UNDO Other Segment Types No Segment (4) Choosing a Recovery Option (4A) Complete Recovery Block Level Recovery , Datafile Recovery , Database Recovery , After Complete Recovery (4B) Recreating Indexes (4C) Salvaging Data from Tables Methods of extracting data from a corrupt table AROUND a corrupt block Methods of extracting data from a table with a corrupt LOBSEGMENT block Extracting data from the corrupt block itself (4D) Leaving the Corruption in Place Warnings when Leaving a Corruption in Place (4E) Last Options Document History All SQL statements here are for use in SQL*Plus (in 8.1 or higher) or Server Manager (Oracle7 / 8.0) when connected as a SYSDBA user. (Eg: "connect / as sysdba" or "connect internal") Introduction This article discusses how to handle one or more block corruptions on an Oracle datafile and describes the main actions to take to deal with them. Please read the complete article before taking any action. This note does not cover memory corruption issues (typically ORA-600 [17xxx] type errors). Note: If the problem is an ORA-1578 on STARTUP then please contact your local support center for advice referencing Note:106638.1 - this note is not visible to customers but the relevant steps from it can be supplied by an experienced support analyst. You may be referred to this article from many places for many forms of error - it is important that you have the following information for each corrupt block: An absolute FILE NUMBER of the file containing the corrupt block. Referred to as "&AFN" in this article. The file name of the file containing the corrupt block. Referred to as "&FILENAME" in this article. ( If you know the FILE NUMBER but not its name then V$DATAFILE can be used to get the file name: SELECT name FROM v$datafile WHERE file#=&AFN; If the file number does not appear in V$DATAFILE in Oracle8i AND &AFN is greater than the DB_FILES parameter value then it is probably a TEMPFILE. In this case the filename can be found using: SELECT name FROM v$tempfile WHERE file#=(&AFN - &DB_FILES_value); ) The BLOCK NUMBER of the corrupt block in that file. Referred to as "&BL" in this article. The tablespace number and name containing the affected block. Referred to as "&TSN" (tablespace number) and "&TABLESPACE_NAME" in this article. If you do not know these then you can find them using: SELECT ts# "TSN" FROM v$datafile WHERE file#=&AFN; SELECT tablespace_name FROM dba_data_files WHERE file_id=&AFN; The block size of the tablespace where the corruption lies. Referred to as "&TS_BLOCK_SIZE" in this article. For Oracle 9i+, run the following query to determine the appropriate block size: SELECT block_size FROM dba_tablespaces WHERE tablespace_name = (SELECT tablespace_name FROM dba_data_files WHERE file_id=&AFN); For Oracle 7, 8.0 and 8.1: Every tablespace in the database has the same block size. For these versions, issue "SHOW PARAMETER DB_BLOCK_SIZE" and use this value as your &TS_BLOCK_SIZE. Eg: For the ORA-1578 error: ORA-01578: ORACLE data block corrupted (file # 7, block # 12698) ORA-01110: data file 22: '/oracle1/oradata/V816/oradata/V816/users01.dbf' then: &AFN is "22" (from the ORA-1110 portion of the error) &RFN is "7" (from the "file #" in the ORA-1578) &BL is "12698" (from the "block #" in the ORA-1578) &FILENAME is '/oracle1/oradata/V816/oradata/V816/users01.dbf' &TSN etc.. should be determined from the above SQL For other errors (ORA-600 , ORA-1498 etc...) the above values should either be given to you by Oracle Support, or be given to you from the article which covers the relevant error. Overview of Steps to handle a Corruption There are many possible causes of a block corruption including: - Bad IO hardware / firmware - OS problems - Oracle problems - Recovering through "UNRECOVERABLE" or "NOLOGGING" database actions (in which case ORA-1578 is expected behaviour - see below) The point in time when an Oracle error is raised may be much later than when any corruption initially occurred. As the root cause is not usually known at the time the corruption is encountered, and as in most cases the key requirement is to get up and running again, then the steps used tackle corruption problems in this article are: 1) Determine the extent of the corruption problems and also determine if the problems are permanent or transient. If the problem is widespread or the errors move about then focus on identifying the cause first (check hardware etc..). This is important as there is no point recovering a system if the underlying hardware is faulty. 2) Replace or move away from any faulty or suspect hardware. 3) Determine which database objects are affected. 4) Choose the most appropriate database recovery / data salvage option. For all steps above it is sensible to collect evidence and document exactly what actions are being taken. The 'Evidence>>' tags in this article list the information which should be collected to assist with identifying the root cause of the problem. Corruption due to NOLOGGING or UNRECOVERABLE If a NOLOGGING (or UNRECOVERABLE) operation is performed on an object and the datafile containing that object is subsequently recovered then the data blocks affected by the NOLOGGING operation are marked as corrupt and will signal an ORA-1578 error when accessed. In Oracle8i an ORA-26040 is also signalled ("ORA-26040: Data block was loaded using the NOLOGGING option" ) which makes the cause fairly obvious, but earlier releases have no additional error message. If a block is corrupt due to recovery through a NOLOGGING operation then you can use this article from Section 3 "Which Objects are Affected ?" onwards but note that: (a) Recovery cannot retrieve the NOLOGGING data (b) No data is salvagable from inside the block (1) Determine the Extent of the Corruption Problem Whenever a corruption error occurs note down the FULL error message/s and look in the instance's alert log and trace files for any associated errors. It is important to do this first to assess whether this is a single block corruption, an error due to an UNRECOVERABLE operation or a more severe issue. It is a good idea to scan affected files (and any important files) with DBVERIFY to check for other corruptions in order to determine the extent of the problem. For details of using DBVERIFY see Note 35512.1 Once you have determined a list of corrupt file/block combinations then the steps below can be used to help determine what action can be taken. Evidence>> - Record the original error in full, along with details of the application which encountered the error. - Save an extract from the alert log from a few hours before the FIRST recorded problem up to the current point in time. - Save any tracefiles mentioned in the alert log. - Record any recent OS problems you have encountered. - Note if you are using any special features - Eg: ASYNC IO, fast write disk options etc.. - Record your current BACKUP position (Dates, Type etc...) - Note if your database is in ARCHIVELOG mode or not Eg: Issue "ARCHIVE LOG LIST" in SQL*Plus (or Server Manager) (2) Replace or Move Away from Suspect Hardware The vast majority of corruption problems are caused by faulty hardware. If there is a hardware fault or a suspect component then it is sensible to either repair the problem, or make disk space available on a separate disk sub-system prior to proceeding with a recovery option. You can move datafiles about using the following steps: 1. Make sure the file to be relocated is either OFFLINE or the instance is in the MOUNT state (not open) 2. Physically restore (or copy) the datafile to its new location eg: /newlocation/myfile.dbf 3. Tell Oracle the new location of the file. eg: ALTER DATABASE RENAME FILE '/oldlocation/myfile.dbf' TO '/newlocation/myfile.dbf'; (Note that you cannot RENAME a TEMPFILE - TEMPFILEs should be dropped and recreated at the new location) 4. Online the relevant file / tablespace (if database is open) IMPORTANT: If there are multiple errors (which are NOT due to NOLOGGING) OR You have OS level errors against the affected file OR The errors are transient and keep moving about then there is little point proceeding until the underlying problem has been addressed or space is available on alternative disks. Get your hardware vendor to check the system over and contact Oracle Support with details of all errors. Please note: Whilst a failed hardware check is a good indication that there is a hardware issue, a successful hardware check should not be taken as proof that there is no hardware related issue - it is very common for hardware tests to report success when there really is some underlying fault. If using any special IO options such as direct IO , async IO or similar it may be worth disabling them in order to eliminate such options as a potential source of problems. (3) Which Objects are Affected ? It is best to determine which objects are affected BEFORE making any decisions about how to recover - this is because the corruption/s may be on object/s which can easily be re-created. Eg: For a corruption on a 5 row lookup table it may be far quicker to drop and recreate the table than to perform a recovery. For each corruption collect the information in the following table. The steps to do this are explained below. Information to Record for each Corruption Original Error Absolute File# &AFN Relative File# &RFN Block# &BL Tablespace Segment Type Segment Owner.Name Related Objects Recovery Options The notes below will help you fill in this table for each corruption. "Original Error" This is the error as initially reported. Eg: ORA-1578 / ORA-1110 , ORA-600 with all arguments etc.. "Absolute File#", "Relative File#" and "Block#" The File# and Block# should have been given to you either by the error, by Oracle Support, or by the steps in an error article which directed you to this article. In Oracle8/8i/9i/10g: The absolute and relative file numbers are often the same but can differ (especially if the database has been migrated from Oracle7). It is important to get the correct numbers for &AFN and &RFN or you may end up salvaging the wrong object !! An ORA-1578 reports the RELATIVE file number, with the ABSOLUTE file number given in the accompanying ORA-1110 error. For ORA-600 errors you should be told an absolute file number. The following query will show the absolute and relative file numbers for datafiles in the database: SELECT tablespace_name, file_id "AFN", relative_fno "RFN" FROM dba_data_files; In Oracle8i/9i/10g: In addition to the notes above about Oracle8, Oracle8i onwards can have TEMPFILES. The following query will show the absolute and relative file numbers for tempfiles in the database: SELECT tablespace_name, file_id+value "AFN", relative_fno "RFN" FROM dba_temp_files, v$parameter WHERE name='db_files'; In Oracle7: Use the same file number for both the "Absolute File#" and the "Relative File#" "Segment Type", "Owner", "Name" and "Tablespace" The following query will tell you the object TYPE , OWNER and NAME of a segment given the absolute file number "&AFN" and block number "&BL" of the corrupt block - the database must be open in order to use this query: SELECT tablespace_name, segment_type, owner, segment_name FROM dba_extents WHERE file_id = &AFN and &BL between block_id AND block_id + blocks - 1 ; If the block is in a TEMPFILE the above query will return no data. For TEMPFILES the "Segment Type" will be "TEMPORARY". If the above query does not return rows, it can also be that the corrupted block is a segment header in a Locally Managed Tablespace (LMT). When the corrupted block is a segment header block in a LMT, the above query produces a corruption message in the alert.log but the query does not not fail. In that case use this query: SELECT owner, segment_name, segment_type, partition_name FROM dba_segments WHERE header_file = &AFN and header_block = &BL ; "Related Objects" and Possible "Recovery Options" by SEGMENT_TYPE: The related objects and recovery options which can be used depend on the SEGMENT_TYPE. The additional queries and possible recovery options are listed below for each of the most common segment types. CACHE CLUSTER INDEX PARTITION INDEX LOBINDEX LOBSEGMENT ROLLBACK TABLE PARTITION TABLE TEMPORARY TYPE2 UNDO Some other Segment Type "no rows" from the query CACHE - If the segment type is CACHE recheck you have entered the SQL and parameters correctly. If you get the same result contact Oracle support with all information you have. Options: The database is likely to require recovery. {Continue} {Back to Segment List} CLUSTER - If the segment is a CLUSTER determine which tables it contains. Eg: SELECT owner, table_name FROM dba_tables WHERE owner='&OWNER' AND cluster_name='&SEGMENT_NAME' ; Options: If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For non dictionary clusters possible options include: Recovery OR Salvage data from all tables in the cluster THEN Recreate the cluster and all its tables As the cluster may contain a number of tables, it is best to collect information for each table in the cluster before making a decision. {Collect TABLE information} {Back to Segment List} INDEX PARTITION - If the segment is an INDEX PARTITION note the NAME and OWNER and then determine which partition is affected thus: SELECT partition_name FROM dba_extents WHERE file_id = &AFN AND &BL BETWEEN block_id AND block_id + blocks - 1 ; then continue below as if the segment was an INDEX segment. Options: Index partitions can be rebuilt using: ALTER INDEX xxx REBUILD PARTITION ppp; (take care with the REBUILD option as described in "Recreating Indexes" below) INDEX - If the segment is an INDEX then if the OWNER is "SYS" contact Oracle support with all details. For a non-dictionary INDEX or INDEX PARTITIONs find out which table the INDEX is on: Eg: SELECT table_owner, table_name FROM dba_indexes WHERE owner='&OWNER' AND index_name='&SEGMENT_NAME' ; and determine if the index supports a CONSTRAINT: Eg: SELECT owner, constraint_name, constraint_type, table_name FROM dba_constraints WHERE owner='&TABLE_OWNER' AND constraint_name='&INDEX_NAME' ; Possible values for CONSTRAINT_TYPE are: P The index supports a primary key constraint. U The index supports a unique constraint. If the INDEX supports a PRIMARY KEY constraint (type "P") then check if the primary key is referenced by any foreign key constraints: Eg: SELECT owner, constraint_name, constraint_type, table_name FROM dba_constraints WHERE r_owner='&TABLE_OWNER' AND r_constraint_name='&INDEX_NAME' ; Options: If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For non dictionary indexes possible options include: Recovery OR Recreate the index (with any associated constraint disables/enables) (take care with the REBUILD option as described in "Recreating Indexes" below) {Continue} {Back to Segment List} ROLLBACK - If the segment is a ROLLBACK segment contact Oracle support as rollback segment corruptions require special handling. Options: The database is likely to require recovery. {Continue} {Back to Segment List} TYPE2 UNDO - TYPE2 UNDO is a system managed undo segment which is a special form of rollback segment. Corruptions in these segments require special handling. Options: The database is likely to require recovery. {Continue} {Back to Segment List} TABLE PARTITION - If the segment is a TABLE PARTITION note the NAME and OWNER and then determine which partition is affected thus: SELECT partition_name FROM dba_extents WHERE file_id = &AFN AND &BL BETWEEN block_id AND block_id + blocks - 1 ; then continue below as if the segment was a TABLE segment. Options: If all corruptions are in the same partition then one option at this point is to EXCHANGE the corrupt partition with an empty TABLE - this can allow the application to continue (without access to the data in the corrupt partition) whilst any good data can then be extracted from the table. For other options see the TABLE options below. TABLE - If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For a non-dictionary TABLE or TABLE PARTITIONs find out which INDEXES exist on the TABLE: Eg: SELECT owner, index_name, index_type FROM dba_indexes WHERE table_owner='&OWNER' AND table_name='&SEGMENT_NAME' ; and determine if there is any PRIMARY key on the table: Eg: SELECT owner, constraint_name, constraint_type, table_name FROM dba_constraints WHERE owner='&OWNER' AND table_name='&SEGMENT_NAME' AND constraint_type='P' ; If there is a primary key then check if this is referenced by any foreign key constraints: Eg: SELECT owner, constraint_name, constraint_type, table_name FROM dba_constraints WHERE r_owner='&OWNER' AND r_constraint_name='&CONSTRAINT_NAME' ; Options: If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For non dictionary tables possible options include: Recovery OR Salvage data from the table (or partition) THEN Recreate the table (or partition) OR Leave the corruption in place (eg: Use DBMS_REPAIR to mark the problem blocks to be skipped) {Continue} {Back to Segment List} IOT (Index Organized Table) The corruption in IOT table should be handled in the same way as in a heap or partitioned table. The only exception is if the PK is corrupted. PK of an IOT table is the table itself and can't be dropped and recreated. Options: If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For non dictionary tables possible options include: Recovery OR Salvage data from the table (or partition) THEN Recreate the table (or partition) OR Leave the corruption in place (DBMS_REPAIR cannot be used with IOTs) {Continue} {Back to Segment List} LOBINDEX - Find out which table the LOB belongs to: SELECT table_name, column_name FROM dba_lobs WHERE owner='&OWNER' AND index_name='&SEGMENT_NAME'; - If the table is owned by "SYS" then contact Oracle support with all details. The database is likely to require recovery. - It is not possible to rebuild LOB indexes and so you have to treat the problem as a corruption on the LOB column of the affected table. Get index and constraint information for the table which has the corrupt LOB index using the SQL in the TABLE section, then return here. Options: If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For non dictionary tables possible options include: Recovery OR Salvage data from the table (and its LOB column/s) THEN Recreate the table It is not generally sensible just to leave the corruption in place unless the table is unlikely to have any further DML on the problem column. {Continue} {Back to Segment List} LOBSEGMENT - Find out which table the LOB belongs to: Eg: SELECT table_name, column_name FROM dba_lobs WHERE owner='&OWNER' AND segment_name='&SEGMENT_NAME'; - If the table is owned by "SYS" then contact Oracle support with all details. The database is likely to require recovery. - For non-dictionary tables ... Get index and constraint information for the table which has the corrupt LOB data using the SQL in the TABLE section, then return here to find details of the exact rows affected. Finding the exact row which references the corrupt LOB block can be a challenge as the errors reported do not show any detail about which table row owns the lob entry which is corrupt. Typically one can refer to application logs or any SQL_TRACE or 10046 trace of a session hitting the error (if available) or see if having event "1578 trace name errorstack level 3" set in the session helps identify the current SQL/binds/row. eg: ALTER SYSTEM SET EVENTS '1578 trace name errorstack level 3'; Then wait for the error to be hit by the application and find the trace file. If there are no clues then you can construct a PLSQL block to scan the problem table row by row extracting the LOB column data which loops until it hits an error. Such a technique may take a while but it should be possible to get a primary key or rowid of any row which references a corrupt LOB block. eg: set serverout on exec dbms_output.enable(100000); declare error_1578 exception; pragma exception_init(error_1578,-1578); n number; cnt number:=0; badcnt number:=0; begin for cursor_lob in (select rowid r, &LOB_COLUMN_NAME L from &OWNER..&TABLE_NAME) loop begin n:=dbms_lob.instr(cursor_lob.L,hextoraw('AA25889911'),1,999999) ; exception when error_1578 then dbms_output.put_line('Got ORA-1578 reading LOB at '||cursor_lob.R); badcnt:=badcnt+1; end; cnt:=cnt+1; end loop; dbms_output.put_line('Scanned '||cnt||' rows - saw '||badcnt||' errors'); end; / It is possible to have a corrupt LOB block which is only present as an old version (for consistent read) and which has not yet been re-used in which case all table rows will be accessible but it may not be possible to insert / update the LOB columns once that block is reclaimed for reuse. Options: If the OWNER is "SYS" then contact Oracle support with all details. The database is likely to require recovery. For non dictionary tables possible options include: Recovery OR Salvage data from the table (and its LOB column/s) THEN Recreate the table OR Leave the corruption in place (It is not possible to use DBMS_REPAIR on LOB segments) {Continue} {Back to Segment List} TEMPORARY - If the segment type is TEMPORARY then the corruption does not affect a permanent object. Check if the tablespace where the problem occurred is being used as a TEMPORARY tablespace thus: SELECT count(*) FROM dba_users WHERE temporary_tablespace='&TABLESPACE_NAME' ; Options: If this is a TEMPORARY_TABLESPACE then it may be possible to create a NEW temporary tablespace and switch all users to that tablespace then DROP the problem tablespace. If this is not a temporary tablespace then the block should not be read again and should get re-formatted next time the block is used - the error should not repeat PROVIDED any underlying cause has been cured. No restore is normally required, although if the disk is suspect and the tablespace contains useful data then a database recovery of the affected file/s may be wise. {Continue} {Back to Segment List} Some other SEGMENT_TYPE - If the segment type returned is not covered above then contact Oracle support for advice with all information collected so far. {Continue} {Back to Segment List} "no rows returned" - If there appears to be no extent containing the corrupt block then first double check the figures used in the query. If you are sure the file and block are correct and do not appear as belonging to an object in DBA_EXTENTS then: - Double check if the file involved is a TEMPFILE. Note that TEMPFILE file numbers depend on the init.ora parameter DB_FILES so any changes to this parameter change the absolute file number reported in errors. - DBA_EXTENTS does not include blocks which are used for local space management in locally managed tablespaces. - If the database you are now querying is from a different point in time to the datafile with the error then the problem object may have been dropped and so queries against DBA_EXTENTS may show no rows. - If the error you are investigating was reported by DBVERIFY then DBV checks all blocks regardless of whether they belong to an object or not. This it is possible for a corrupt block to exist in the datafile but in a block not in use by any object. Options: An error on an UNUSED Oracle block can be ignored as Oracle will create a new block image should the block need to be used so any existing problem on the block will never get read. If you suspect that the block may be a space management block then you can use DBMS_SPACE_ADMIN to help check this by running: exec DBMS_SPACE_ADMIN.TABLESPACE_VERIFY('&TABLESPACE_NAME'); This should write inconsistencies to the trace file but if it encounters a fatally corrupt block it will report an error like: ORA-03216: Tablespace/Segment Verification cannot proceed An error on a bitmap space management block can often be corrected by running: exec DBMS_SPACE_ADMIN.TABLESPACE_REBUILD_BITMAPS('&TABLESPACE_NAME'); {Continue} {Back to Segment List} Evidence>> - For each corrupt block it is also a good idea to collect the following physical evidence if there is a need to try and identify the actual cause of the corruption: i) An operating system HEX dump of the bad block and the block either side of it. On UNIX: dd if=&FILENAME bs=&TS_BLOCK_SIZE skip=&BL-1 count=3 of=BL.dd ^^^^^^^^ ^^^^^^^^^^^^^^ ^^^ Eg: For BL=1224: dd if=ts11.dbf bs=4k skip=1223 count=3 of=1223_1225.dd On VMS: DUMP/BLOCKS=(start:XXXX,end:YYYY)/out=dump.out &FILENAME Where XXXX=Operating system block number (in 512 byte chunks) To calculate this multiply the block number reported by '&TS_BLOCK_SIZE/512'. ii) If you are in ARCHIVELOG mode make a safe copy of the archived log files around the time of the error, and preferably for a few hours before the error was reported. Also secure any backup/s of the problem datafile from before the errors as the before image PLUS redo can help point towards a cause. (DBV can often be used to check if the problem exists in a backup copy of a file). The ideal scenario is to have a datafile backup image which does not have any corruption and all the redo from that point in time up to and just past the time when the corruption is first reported. iii) Obtain an Oracle dump of the problem block/s: ALTER SYSTEM DUMP DATAFILE '&FILENAME' BLOCK &BL ; (The output will go to a tracefile in the USER_DUMP_DEST). {Continue} {Back to Segment List} (4) Choosing a Recovery Option The best recovery option now depends on the objects affected. The notes in Section (3) above should have highlighted the main options available for each affected object. The actual recovery method chosen may include a mix or one or more methods thus: Is any Recovery Required ? If the error is in a TEMPORARY tablespace, or is in a block which is no longer part of any database object then no action is required, although it may be wise to relocate the problem tablespace to a different storage device. See Warnings. Is Complete Recovery an option ? In order for complete recovery to be an option the following must be true: - The database is in ARCHIVELOG mode (The "ARCHIVE LOG LIST" command shows Archivelog Mode) - You have a good backup of affected files. Note that in some cases, the corruption may have been present, but undetected, for a long period of time. If the most recent datafile backup still contains the corruption, you can try an earlier backup as long as you have all the necessary ARCHIVELOGS. (You can often use the DBV START= / END= options to check if specific block/s in a restored copy of a backup file are corrupt) - All ARCHIVELOGS are available from the time of the backup to the current point in time - The current online log/s are available and intact - The errors are NOT due to recovery through a NOLOGGING operation When the above criteria are satisfied then complete recovery is usually the preferred option *BUT NOTE* (a) If the rollback of a transaction has seen a corrupt block on an object other than the rollback segment itself then UNDO may have been discarded. In this case you may need to rebuild indexes / check data integrity AFTER the recovery completes. (b) If the files to be recovered contain data from NOLOGGING operations performed since the last backup then those blocks will be marked corrupt if datafile or database recovery is used. In some cases this can put you in a worse scenario than the current position. If database recovery has already been performed and the corruption is still there then either all of your backups contain the corruption, the underlying fault is still present or the problem is replaying through redo. In these cases you will need to choose some other recovery option. See "(4A) Complete Recovery" for complete recovery steps. Can the object be Dropped or Re-created without needing to extract any data from the object itself ? It may be possible to lose the object, or to recreate it from a script / recent export. Once an object is dropped then blocks in that object are marked as "free" and will be re-formatted when the block gets allocated to a new object. It is advisable to RENAME rather than DROP a table unless you are absolutely sure that you do not need any data in it. In the case of a table partition then only the affected partition needs to be dropped. eg: ALTER TABLE ... DROP PARTITION ... If the corruption affects the partition segment header, or the file containing the partition header is offline, then DROP PARTITION may fail. In this case it may still be possible to drop the partition by first exchanging it with a table of the same definition. eg: ALTER TABLE .. EXCHANGE PARTITION .. WITH TABLE ..; The most common object which can be re-created is an index. Always address TABLE corruptions before INDEX problems on a table. See "(4B) Recreating Indexes" for more details. For any segment, a quick way to extract the DDL for an object, when you have the absolute file number and block number of the corrupt block, is: set long 64000 select dbms_metadata.get_ddl(segment_type, segment_name, owner) FROM dba_extents WHERE file_id=&AFN AND &BL BETWEEN block_id AND block_id + blocks -1; Is it required to salvage data before recreating the object ? If the problem is on a critical application table which is regularly updated then it may be required to salvage as much data from the table as possible, then recreate the table. See "(4C) Salvaging Data from Tables" for more details. Is it acceptable to leave the corruption in place for the moment? In some cases the best immediate option may be to leave the corruption in place and isolate it from application access. See "(4D) Leaving the Corruption In Place" for more details. Last Options Are any of the following possible ? Recovery to an old point-in-time (via point in time recovery) of either the database or tablespace point in time recovery OR Restore of a COLD backup from before the corruption OR Use of an existing export file See "(4E) Last Options" for more details. (4A) Complete Recovery If the database is in ARCHIVELOG mode and you have a good backup of the affected files then recovery is usually the preferred option. This is not GUARANTEED to clear a problem, but is effective for the majority of corruption issues. If recovery re-introduces the problem then return to the list of options above and choose another method. If you are using Oracle9i (or higher) then it may be possible to perform block level recovery using the RMAN BLOCKRECOVER command. If using an earlier Oracle release then you can either perform datafile recovery (which can be done while the rest of the database is still up and running), or database recovery (which requires the database to be taken down) . Block Level Recovery ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ As of Oracle9i RMAN allows individual blocks to be recovered whilst the rest of the database (including other blocks in the datafile) are available for normal access. Note that block level recovery can only be used to recover a block fully to the current point in time. It is not necessary to be using RMAN for backups to be able to use this option for recovery of individual blocks. eg: Consider that you have an ORA-1578 on file #6 block #30 which is likely due to a media corruption problem and there is a good cold backup image of that file which has been restored to '.../RESTORE/filename.dbf'. Provided all archivelogs exist (in the default location) then you can use RMAN to perform a block level recovery using a command sequence like: rman nocatalog connect target catalog datafilecopy '.../RESTORE/filename.dbf'; run {blockrecover datafile 6 block 30;} This will use the registered datafile backup image and any required archivelogs to perform block recovery of just the one problem block to current point in time. Please see the documentation for full details of the RMAN BLOCKRECOVER command and limitations. Datafile Recovery ~~~~~~~~~~~~~~~~~~ Datafile recovery of a file involves the following steps. If there are several files repeat the steps for each file or see "Database Recovery" below. These steps can be used if the database is either OPEN or MOUNTED. OFFLINE the affected data file eg: ALTER DATABASE DATAFILE 'name_of_file' OFFLINE; Copy it to a safe location (in case the backup is bad) Restore the latest backup of the file onto a GOOD disk Check the restored file for obvious corruptions with DBVERIFY For details of using DBVERIFY see Note 35512.1 Assuming the restored file is OK, then RENAME the datafile to the NEW location (if different from the old location) eg: ALTER DATABASE RENAME FILE 'old_name' TO 'new_name'; Recover the datafile eg: RECOVER DATAFILE 'name_of_file'; Online the file/s eg: ALTER DATABASE DATAFILE 'name_of_file' ONLINE; {Continue} Database Recovery ~~~~~~~~~~~~~~~~~ Database recovery generally involves the following steps: Shutdown (Immediate or Abort) Copy the current copy of all files to be recovered to a safe location Restore the backup files to a GOOD disk location DO NOT RESTORE THE CONTROL FILES or ONLINE REDO LOG FILES Check restored files with DBVERIFY For details of using DBVERIFY see Note 35512.1 Startup MOUNT Rename any relocated files eg: ALTER DATABASE RENAME FILE 'old_name' TO 'new_name'; Ensure all required files are online eg: ALTER DATABASE DATAFILE 'name_of_file' ONLINE; Recover the database eg: RECOVER DATABASE Open the database eg: ALTER DATABASE OPEN; After a Complete Recovery ~~~~~~~~~~~~~~~~~~~~~~~~~~ Once a complete recovery has been performed it is advisable to check the database before allowing it to be used: - Run "ANALYZE <table_name> VALIDATE STRUCTURE CASCADE" against each problem object to check for table/index mis-matches. If there has been any UNDO discarded this may show a mismatch requiring indexes to be re-created. - Check the logical integrity of data in the table at the application level. (4B) Recreating Indexes If the corrupt object is a user INDEX you can simply drop and re-create it PROVIDED the underlying table is not also corrupt. If the underlying table is also corrupt it is advisable to sort out the TABLE before recreating any indexes. If the information collected shows that the index has dependent FOREIGN KEY constraints then you will need to do something like this: - ALTER TABLE <child_table> DISABLE CONSTRAINT <fk_constraint>; for each foreign key - Rebuild the primary key using ALTER TABLE <table> DISABLE CONSTRAINT <pk_constraint>; DROP INDEX <index_name>; CREATE INDEX <index_name> .. with appropriate storage clause ALTER TABLE <table> ENABLE CONSTRAINT <pk_constraint>; - Enable the foreign key constraints ALTER TABLE <child_table> ENABLE CONSTRAINT <fk_constraint>; For an index partition you can: ALTER INDEX ... REBUILD PARTITION ...; Notes: (1) It is important not to REBUILD a non-partitioned corrupt index using an "ALTER INDEX .. REBUILD" command as this will usually try to build the new index from the existing index segment, which contains a corrupt block. "ALTER INDEX ... REBUILD ONLINE" and "ALTER INDEX ... REBUILD PARTITION ..." do not build the new index from the old index segment and so can be used. (2) Create INDEX can use the data from an existing index if the new index is a sub-set of the columns in the existing index. Hence if you have 2 corrupt indexes drop them BOTH before re-creating them. (3) Be sure to use the correct storage details when recreating indexes. (4C) Salvaging Data from Tables If the corrupt object is a TABLE or CLUSTER or LOBSEGMENT then it must be understood that the data within the corrupt block is lost. Some of the data may be salvageable from a HEX dump of the block, or from columns covered by indexes. Important: As it may be required to salvage data in the corrupt block from the indexes it is a good idea NOT to drop any existing index until any required data has been extracted. There are many ways to get data out of a table which contains a corrupt block. Choose the most appropriate method as detailed below. The aim of these methods is to extract as much data as possible from the table blocks which can be accessed. It is usually a good idea to RENAME the corrupt table so that the new object can be created with the correct name. Eg: RENAME <emp> TO <emp_corrupt>; Methods of extracting data from a corrupt table AROUND a corrupt block (1) From Oracle 7.2 onwards, including Oracle 8.0, 8.1, and 9i, it is possible to SKIP over corrupt blocks in a table. This is by far the simplest option to extract table data and is discussed in: Extracting data using DBMS_REPAIR.SKIP_CORRUPT_BLOCKS or Event 10231 Note 33405.1 If the corruption is in an IOT overflow segment then the same method should be followed, but using event 10233 together with a full index scan. Note that this method can only be used if the block "wrapper" is marked corrupt. Eg: If the block reports ORA-1578. If the problem is an ORA-600 or other error which does not report and ORA-1578 error then it is often possible to use DBMS_REPAIR to mark the problem blocks in a table as "soft corrupt" such that they will then signal ORA-1578 when accessed which then allows you to use DBMS_REPAIR.SKIP_CORRUPT_BLOCKS. Note: Any blocks which are marked corrupt by the "FIX_CORRUPT_BLOCKS" procedure will also be marked corrupt following any restore / recover operation through the time of the FIX_CORRUPT_BLOCKS. Full details of using DBMS_REPAIR for this can be found in the documentation but in summary the steps are: - Use DBMS_REPAIR.ADMIN_TABLES to create the admin tables - Use DBMS_REPAIR.CHECK_OBJECT to find problem blocks - Get any good data out of problem blocks before corrupting them. - Use DBMS_REPAIR.FIX_CORRUPT_BLOCKS to mark the found problem blocks as corrupt so that they will then signal ORA-1578 - If required use DBMS_REPAIR.SKIP_CORRUPT_BLOCKS to skip corrupt blocks on the table. (2) From Oracle 7.1 onwards you can use a ROWID range scan. The syntax for this is a little tricky but it is possible to select around a corrupt block using a ROWID hint. As the format of ROWIDs changed between Oracle7 and Oracle8 there are 2 articles which discuss this: Using ROWID Range Scans to extract data in Oracle8 and higher Note 61685.1 Using ROWID Range Scans to extract data in Oracle7 Note 34371.1 (3) If there is a primary key you can select table data via this index. It may also be possible to select some of data via any other index. This can be slow and time consuming and is only normally needed for Oracle 7.0 releases. This method is described in Note 34371.1 (which also describes the ROWID range scans) (4) There are various salvage programs / PLSQL scripts which can be used to salvage data from a table. These can take longer to set up and use than the above methods but can often cope with various kinds of corruption besides an ORA-1578. As these methods typically require much hand-holding from support then some of these articles may not be visible to customers. These require Pro*C to be available and an understanding of how to build Pro*C executables: SALVAGE.PC for Oracle7 Note 2077307.6 These requires manual interaction: SALVAGE.SQL for Oracle7/8 Note 2064553.4 Methods of extracting data from a table with a corrupt LOBSEGMENT block It is not possible to used DBMS_REPAIR on LOB segments. If the corrupt LOB block is NOT referenced by any row in the table then it should be possible to CREATE TABLE as SELECT (CTAS) or export / drop / import the table as is. If the corrupt LOB block is referenced by a row then it should be possible to select or export with a WHERE predicate that excludes the problem row/s. WARNING: It is possible to update the LOB column value of a problem row to NULL which will then clear ORA-1578 on SELECT operations *BUT* the corrupt block will then be waiting to be reclaimed and will eventually signal an ORA-1578 on attempts to get a new LOB for INSERT or UPDATE operations on any row which can be a worse situation than having a corruption on a known row. Hence you should only really set the LOB column to NULL if you intend to immediately recreate the table. Extracting data from the corrupt block itself As the corrupt block itself is "corrupt" then any data extracted from the block should be treated as suspect. The main methods of getting the rows from the corrupt block itself are: - For TABLE blocks Oracle Support can use a tool which attempts to interpret the block contents. - Use any existing indexes on the table to extract data for columns covered by the index where the ROWID falls inside the corrupt block. This is described towards the end of the ROWID range scan articles mentioned above: For Oracle8/8i see Note 61685.1 For Oracle7 see Note 34371.1 - It may be possible to use LogMiner on the redo stream to find the original inserts/updates which loaded the data to the problem block. The main factor here is WHEN the data was actually put in the block. eg; row 2 may have been inserted yesterday but row 1 may have been inserted 5 years ago. (4D) Leaving A Corruption In Place It is possible to leave a corruption in place and just accept the errors reported, or prevent access to the problem rows at an application level. eg: If the problem block / row is in a child table then it may be possible at application level to prevent access via the parent row/s such that the child rows are never accessed. (Be wary of cascade type constraints though) This may not help with reports and other jobs which access data in bulk so it may also be desirable to use the DBMS_REPAIR options shown in 4C above to prevent the block/s erroring when accessed. Marking a corruption like this and leaving it around may give a short term solution allowing full data salvage and/or recovery to be attempted at scheduled outage, or allowing time to check other recovery options on a second (clone) database. Note though that marking a block corrupt with DBMS_REPAIR.FIX_CORRUPT_BLOCKS will cause the marked block/s to also be corrupt after recovery through the time that FIX_CORRUPT_BLOCKS was executed. Leaving a corruption may be sensible for data which rapidly ages and is subsequently purged (eg: In a date partitioned table where older partitions are dropped at some point). Leaving Corruptions in LOB segments At application level it can be possible to leave a corrupt LOB column in place until such time as the table can be rebuilt. One way to ensure you do not hit the "WARNING" scenario above is to ensure that the table is only ever accessed via a view which includes a WHERE predicate to prevent the problem row/s from being seen. eg: Consider table MYTAB( a number primary key, b clob ) has one or more rows pointing at corrupt LOB data. ALTER TABLE MYTAB ADD ( BAD VARCHAR2(1) ); CREATE VIEW MYVIEW AS SELECT a,b FROM MYTAB WHERE BAD is null; Set BAD='Y' for any problem row/s If you only access MYTAB via MYVIEW and the row will never be visible and so cannot be updated keeping the corrupt entry isolated until it can be dealt with. Clearly this example is more of a design time solution but some applications may already have similar mechanisms and may only access data via a view (or via an RLS policy) giving some option/s to hide the problem row/s. Warnings when Leaving a Corruption in Place Whilst it is possible to leave a corruption in place it should be noted that the corrupt blocks will still show up in runs of DBVERIFY, in RMAN backup warnings / errors etc.. It is important to make a careful record of any corruption you expect to see from these tools, particularly any blocks you expect to skip with RMAN (eg: having MAX_CORRUPT set) and be sure to remove any "acceptance" of the errors once the corruptions have been cleared. eg: Consider that a corrupt block has been handled by leaving the corruption in place and avoiding the problem row/s at application level. RMAN may be configured to allow the corruptions during backup. The table is then recreated at a later date during some table reorganisation. If RMAN is not updated to reflect that no errors should now be expected then RMAN may ignore some other corruption which occurs at a later time. It is also important to note that leaving corrupt blocks around in table segments can lead to mismatched results from queries eg: different results can occur for tables with SKIP_CORRUPT set depending on whether an index scan or table access occurs. Other reports may just error . Note that leaving a corruption in place but marking the block with DBMS_REPAIR.FIX_CORRUPT_BLOCKS writes redo to corrupt the block which may limit subsequent recovery options. (4E) Last Options If you have a standby setup (physical or logical) then check that first. Whatever sort of block the problem occurred on, one possible option is to recover the database, or problem tablespace, to a point in time BEFORE the corruption appeared. The difficulty with this option is that it is not always possible to know when the problem first appeared. DBVERIFY can be often be used to check a restored file for corruptions. For details of using DBVERIFY see Note 35512.1 . In particular the START= / END= DBV options can be used to give a quick first test of whether the problem block itself is bad on a restored backup image. This section outlines some final options available for recovering. If you have come here then one or more of the following have happened: - You have lost a "vital" datafile (or have a corruption on it) and have no good backup of the problem file/s (without the corruption) - Are either not in ARCHIVELOG mode OR do not have all archivelogs since the file was first created - Complete recovery keeps reintroducing the problem Last chance: Please note if you have lost all copies of a datafile but DO still have the ARCHIVE logs from when the file was first created it is still possible to recover the file. Eg: ALTER DATABASE CREATE DATAFILE '....' [as '...'] ; RECOVER DATAFILE '....' ALTER DATABASE DATAFILE '....' ONLINE; If you are in this scenario try to recover the datafile using these steps before proceeding below. If you have reached this line there are no options left to recover to the current point in time. It is advisable to shutdown the instance and take a BACKUP of the current database NOW in order to provide a fall-back position if the chosen course of action fails. (Eg: if you find your backup is bad). Some outline options available are: Revert to an old COLD backup - eg: If in NOARCHIVELOG mode Set up a clone database from a COLD backup - and extract (export) the problem table/s or transport the problem tablespace Point in time recovery to an older point in time that is consistent - requires a good backup and any necessary archive logs - ALL files have to be restored and the whole DB rolled forward to a suitable point in time. - It may be possible to do the point in time recovery in a clone database and then transport the problem tablespace to the problem database, or export / import the problem table from the clone to the problem database . Tablespace point in time recovery - It may be possible to perform a point in time recovery of the affected tablespace only. There are many notes describing tablespace point in time recovery such as Note 223543.1. Rebuild of DB from some logical export / copy - Requires there to already be a good logical backup of the database - NB: You have to RE-CREATE the database for this option. - As with other options the rebuild could be in a clone database just to get a good image of the problem table/s. If you have a good backup then rolling forwards with DB_BLOCK_CHECKING=TRUE can help find the first point in time where something started to go wrong. It is not generally necessary to take the problem database down while investigating the recovery options. eg: You can restore the system tablespace and problem tablespace datafiles only to a totally different location and/or machine as a different instance to investigate how far you can roll forwards etc.. As of Oracle9i you can also use "Trial Recovery" options to save having to keep restoring a backup while looking into your options. -------------------------------------------------------------------------------- Document History 15-Oct-2008 Minor addition of script to get_ddl 24-Feb-2006 Major additions for LOBs, BLOCKRECOVER, TSPITR, further DBMS_REPAIR options 03-Mar-2005 Minor change to "dd" command to use 22-Nov-2001 Include 9i and multiple block sizes 13-Sep-2001 Add TEMPFILE details 12-Sep-2000 Major rewrite / merge Note 4: ======= Doc ID </help/usaeng/Search/search.html>: Note:47955.1 Content Type: TEXT/PLAIN Subject: Block Corruption FAQ Creation Date: 14-NOV-1997 Type: FAQ Last Revision Date: 17-AUG-2004 Status: PUBLISHED ORACLE SERVER ------------- BLOCK CORRUPTION ---------------- FREQUENTLY ASKED QUESTIONS -------------------------- 25-JAN-2000 CONTENTS -------- 1. What does the error ORA-01578 mean? 2. How to determine what object is corrupted? 3. What are the recovery options if the object is a table? 4. What are the recovery options if the object is an index? 5. What are the recovery options if the object is a rollback segment? 6. What are the recovery options if the object is a data dictionary object? 7. What methods are available to assist in pro-actively identifying corruption? 8. How can corruption be prevented? 9. What are the common causes of corruption? QUESTIONS & ANSWERS 1. What does the error ORA-01578 mean? An Oracle data block is written in an internal binary format which conforms to a defined structure. The size of the physical data block is determined by the "init.ora" parameter DB_BLOCK_SIZE set at the time of database creation. The format of the block is similar regardless of the type of data contained in the block. Each formatted block on disk has a wrapper which consists of a block header and footer. Unformatted blocks should be zero throughout. Whenever a block is read into the buffer cache, the block wrapper information is checked for validity. The checks include verifying that the block passed to Oracle by the operating system is the block requested (data block address) and also that certain information stored in the block header matches information stored in the block footer in case of a split (fractured) block. On a read from disk, if an inconsistency in this information is found, the block is considered to be corrupt and ORA-01578: ORACLE data block corrupted (file # %s, block # %s) is signaled where file# is the file ID of the Oracle datafile and block# is the block number, in Oracle blocks, within that file. However, this does not always mean that the block on disk is truely physically corrupt. That fact needs to be confirmed. 2. How to determine what object is corrupted? The following query will display the segment name, type, and owner: SELECT SEGMENT_NAME, SEGMENT_TYPE, OWNER FROM SYS.DBA_EXTENTS WHERE FILE_ID = <f> AND <b> BETWEEN BLOCK_ID AND BLOCK_ID + BLOCKS - 1; Where <f> is the file number and <b> is the block number reported in the ORA-01578 error message. Suppose block 82817 from table 'USERS' is corrupt: SQL> select extent_id, block_id, blocks from dba_extents where segment_name='USERS'; EXTENT_ID BLOCK_ID BLOCKS ---------- ---------- ---------- 0 82817 8 1 82825 8 2 82833 8 3 82841 8 4 82849 8 SQL> SELECT SEGMENT_NAME, SEGMENT_TYPE, OWNER 2 FROM SYS.DBA_EXTENTS 3 WHERE FILE_ID = 9 4 AND 82817 BETWEEN BLOCK_ID AND BLOCK_ID + BLOCKS - 1; SEGMENT_NAME SEGMENT_TYPE OWNER --------------------------------------------------------------------------------- ------------------ USERS TABLE VPOUSERDB 3. What are the recovery options if the object is a table? The following options exist for resolving non-index block corruption in a table which is not part of the data dictionary: o Restore and recover the database from backup (recommended). o Recover the object from an export. o Select the data out of the table bypassing the corrupted block(s). If the table is a Data Dictionary table, you should contact Oracle Support Services. The recommended recovery option is to restore the database from backup. [NOTE:28814.1] <ml2_documents.showDocument?p_id=28814.1&p_database_id=NOT> contains information on how to handle ORA-1578 errors in Oracle7. References: ----------- [NOTE:28814.1] <ml2_documents.showDocument?p_id=28814.1&p_database_id=NOT> TECH ORA-1578 and Data Block Corruption in Oracle7 4. What are the recovery options if the object is an index? If the object is an index which is not part of the data dictionary and the base table does not contain any corrupt blocks, you can simply drop and recreate the index. If the index is a Data Dictionary index, you should contact Oracle Support Services. The recommended recovery option is to restore the database from backup. There is a possibility you might be able to drop the index and then recreate it based on the original create SQL found in the administrative scripts. Oracle Support Services will be able to make the determination as to whether this is a viable option for you. 5. What are the recovery options if the object is a rollback segment? If the object is a rollback segment, you should contact Oracle Support Services. The recommended recovery option is to restore the database from backup. 6. What are the recovery options if the object is a data dictionary object? If the object is a Data Dictionary object, you should contact Oracle Support Services. The recommended recovery option is to restore the database from backup. If the object is an index on a Data Dictionary table, you might be able to drop the index and then recreate it based on the original create SQL found in the administrative scripts. Oracle Support Services will be able to make the determination as to whether this is a viable option. 7. What methods are available to assist in pro-actively identifying corruption? ANALYZE TABLE/INDEX/CLUSTER ... VALIDATE STRUCTURE is a SQL command which can be executed against a table, index, or cluster which scans every block and reports a failure upon encountering any potentially corrupt blocks. The CASCADE option checks all associated indices and verifies the 1 to 1 correspondence between data and index rows. This is the most detailed block check available, but requires the database to be open. DB Verify is a utility which can be run against a datafile of a database that will scan every block in the datafile and generate a report identifying any potentially corrupt blocks. DB Verify performs basic block checking steps, however it does not provide the capability to verify the 1 to 1 correspondence between data and index rows. It can be run when the database is closed. Export will read the blocks allocated to each table being exported and report any potential block corruptions encountered. References: ----------- [NOTE:35512.1] <ml2_documents.showDocument?p_id=35512.1&p_database_id=NOT> DBVERIFY - Database file Verification Utility (7.3.2 onwards) 8. How can corruption be prevented? Unfortunately, there is no way to totally eliminate the risk of corruption. You can only minimize the risk and plan accordingly. 9. What are the common causes of corruption? o Bad I/O, H/W, Firmware. o Operating System I/O or caching problems. o Memory or paging problems. o Disk repair utilities. o Part of a datafile being overwritten. o Oracle incorrectly attempting to access an unformatted block. o Oracle or operating system bug. Note 77587.1 <ml2_documents.showDocument?p_id=77587.1&p_database_id=NOT> discusses block corruptions in Oracle and how they are related to the underlying operating system and hardware. References: ----------- [NOTE:77587.1] <ml2_documents.showDocument?p_id=77587.1&p_database_id=NOT> BLOCK CORRUPTIONS ON ORACLE AND UNIX Note 5: ======= ORA-00600: Internal message code, arguments: [01578] [...] [...] [] [] []. ORA-01578: Oracle data block corrupted (file ..., block ...). Having encountered the Oracle data block corruption, we must firstly investigate which database segment (name and type) the corrupted block is allocated to. Chances are that the block belongs either to an index or to a table segment, since these two type of segments fill the major part of our databases. The following query will reveil the segment that holds the corrupted block identified by <filenumber> and <blocknumber> (which were given to you in the error message): SELECT ds.* FROM dba_segments ds, sys.uet$ e WHERE ds.header_file=e.segfile# and ds.header_block=e.segblock# and e.file#=<filenumber> and <blocknumber> between e.block# and e.block#+e.length-1; If the segment turns out to be an index segment, then the problem can be very quickly solved. Since all the table data required for recreating the index is still accessable, we can drop and recreate the index (since the block will reformatted, when taken FROM the free-space list and reused for the index). If the segment turns out to be a table segment a number of options for solving the problem are available: - restore and recovery of datafile the block is in - imp table - sql The last option involves using SQL to SELECT as much data as possible FROM the current corrupted table segment and save the SELECTed rows into a new table. SELECTing data that is stored in segment blocks that preceede the corrupted block can be easily done using a full table scan (via a cursor). Rows stored in blocks after the corrupted block cause a problem. A full table scan will never reach these. However these rows can still be fetched using rowids (single row lookups). 2.1 Table was indexed Using an optimizer hint we can write a query that SELECTs the rows FROM the table via an index scan (using rowid's), instead of via a full table scan. Let's assume our table is named X with columns a, b and c. And table X is indexed uniquely on columns a and b by index X_I, the query would look like: SELECT /*+index(X X_I) */ a, b, c FROM X; We must now exclude the corrupt block FROM being accessed to avoid the internal exception ORA-00600[01578]. Since the blocknumber is a substring of the rowid ( ) this can very easily be achieved: SELECT /*+index(X X_I) */ a, b, c FROM X WHERE rowid not like <corrupt_block_number>||'.%.'||<file_number>; But it is important to realize that the WHERE-clause gets evaluated right after the index is accessed and before the table is accessed. Otherwise we would still get the ORA-00600[01578] exception. Using the above query as a subquery in an insert statement we can restore all rows of still valid blocks to a new table. Since the index holds the actual column values of the indexed columns we could also use the index to restore all indexed columns of rows that reside in the corrupt block. The following query, SELECT /*+index(X X_I) */ a, b FROM X WHERE rowid like <corrupt_block_number>||'.%.'||<file_number>; retreives only indexed columns a and b FROM rows inside the corrupt block. The optimizer will not access the table for this query. It can retreive the column values using the index segment only. Using this technique we are able to restore all indexed column values of the rows inside the corrupt block, without accessing the corrupt block at all. Suppose in our example that column c of table X was also indexed by index X_I2. This enables us to completely restore rows inside the corrupt block. First restore columns a and b using index X_I: create table X_a_b(rowkey,a,b) as SELECT /*+index(X X_I) */ rowid, a, b FROM X WHERE rowid like <corrupt_block_number>||'.%.'||<file_number>; Then restore column c using index X_I2: create table X_c(rowkey,c) as SELECT /*+index(X X_I2) */ rowid, c FROM X WHERE rowid like <corrupt_block_number>||'.%.'||<file_number>; And finally join the columns together using the restored rowid: SELECT x1.a, x1.b, x2.c FROM X_a_b x1, X_c x2 WHERE x1.rowkey=x2.rowkey; In summary: Indexes on the corrupted table segment can be used to restore all columns of all rows that are stored outside the corrupted data blocks. Of rows inside the corrupted data blocks, only the columns that were indexed can be restored. We might even be able to use an old version of the table (via Import) to further restore non-indexed columns of these records. 2.2 Table has no indexes This situation should rarely occur since every table should have a primary key and therefore a unique index. However when no index is present, all rows of corrupted blocks should be considered lost. All other rows can be retrieved using rowid's. Since there is no index we must build a rowid generator ourselves. The SYS.UET$ table shows us exactly which extents (file#, startblock, endblock) we need to inspect for possible rows of our table X. If we make an estimate of the maximum number of rows per block for table X, we can build a PL/SQL-loop that generates possible rowid's of records inside table X. By handling the 'invalid rowid' exception, and skipping the corrupted data block, we can restore all rows except those inside the corrupted block. declare v_rowid varchar2(18); v_xrec X%rowtype; e_invalid_rowid exception; pragma exception_init(e_invalid_rowid,-1410); begin for v_uetrec in (SELECT file# file, block# start_block, block#+length#-1 end_block FROM uet$ WHERE segfile#=6 and segblock#=64) -- Identifies our segment X. loop for v_blk in v_uetrec.start_block..v_uetrec.end_block loop if v_uetrec.file<>6 and v_blk<>886 -- 886 in file 6 is our corrupted block. then for v_row in 0..200 -- 200 is maximum number of rows per block for segment X. loop begin SELECT a,b,c into v_rec FROM x WHERE rowid=chartorowid('0000'||hex(v_blk)||'.'|| hex(v_row)||'.'||hex(v_uetrec.file); insert into x_saved(a,b,c) values(v_rec.a,v_rec.b,v_rec.c); commit; exception when e_invalid_rowid then null; end; end loop; /*row-loop*/ end if; end loop; /*blk-loop*/ end loop; /*uet-loop*/ end; / The above code assumes that block id's never exceed 4 hexadecimal places. A definition of the hex-function which is used in the above code can be found in the appendix. Note 6: ======= Doc ID </help/usaeng/Search/search.html>: Note:33405.1 Content Type: TEXT/PLAIN Subject: Extracting Data from a Corrupt Table using SKIP_CORRUPT_BLOCKS or Event 10231 Creation Date: 24-JAN-1996 Type: BULLETIN Last Revision Date: 13-SEP-2000 Status: PUBLISHED ***************** *** *** ***************** This note is an extension to article [NOTE:28814.1] <ml2_documents.showDocument?p_id=28814.1&p_database_id=NOT> about handling block corruption errors where the block wrapper of a datablock indicates that the block is bad. (Typically for ORA-1578 errors). The details here will not work if only the block internals are corrupt (eg: for ORA-600 or other errors). Please read [NOTE:28814.1] <ml2_documents.showDocument?p_id=28814.1&p_database_id=NOT> before reading this note. Introduction ~~~~~~~~~~~~ This short article explains how to skip corrupt blocks on an object either using the Oracle8i SKIP_CORRUPT table flag or the special Oracle event number 10231 which is available in Oracle releases 7 through 8.1 inclusive. The information here explains how to use these options. Before proceeding you should: a) Be certain that the corrupt block is on a USER table. (i.e.: not a data dictionary table) b) Have contacted Oracle Support Services and been advised to use event 10231 or the SKIP_CORRUPT flag. c) Have decided how you are to recreate the table. Eg: Export , and disk space is available etc.. d) You have scheduled down-time to attempt the salvage operation. e) Have a backup of the database. f) Have the SQL to rebuild the problem table, its indexes constraints, triggers, grants etc... This SQL should include relevant storage clauses. What is event 10231 ? ~~~~~~~~~~~~~~~~~~~~~ This event allows Oracle to skip certain types of corrupted blocks on full table scans ONLY hence allowing export or "create table as select" type operations to retrieve rows from the table which are not in the corrupt block. Data in the corrupt block is lost. The scope of this event is limited for Oracle versions prior to Oracle 7.2 as it only allows you to skip 'soft corrupt' blocks. Most ORA 1578 errors are a result of media corruptions and in such cases event 10231 is useless. From Oracle 7.2 onwards the event allows you to skip many forms of media corrupt blocks in addition to soft corrupt blocks and so is far more useful. It is still *NOT* guaranteed to work. [NOTE:28814.1] <ml2_documents.showDocument?p_id=28814.1&p_database_id=NOT> describes alternatives which can be used if this event fails. What is the SKIP_CORRUPT flag ? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In Oracle8i the functionality of the 10231 event has been externalised on a PER-SEGMENT basis such that it is possible to mark a TABLE or PARTITION to skip over corrupt blocks when possible. The flag is set or cleared using the DBMS_REPAIR package. DBA_TABLES has a SKIP_CORRUPT column which indicates if this flag is set for an object or not. Setting the event or flag ~~~~~~~~~~~~~~~~~~~~~~~~~ The event can either be set within the session or at database instance level. If you intend to use a CREATE TABLE AS SELECT then setting the event in the session may suffice. If you want to EXPORT the table data then it is best to set the event at instance level, or set the SKIP_CORRUPT table attribute if on Oracle8i. Oracle8i ~~~~~~~~ Connect as a DBA user and mark the table as needing to skip corrupt blocks thus: execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('<schema>','<tablename>'); or for a table partition: execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('<schema>','<tablename>'.'<partition>'); Now you should be able to issue a CREATE TABLE AS SELECT operation against the corrupt table to extract data from all non-corrupt blocks, or EXPORT the table. Eg: CREATE TABLE salvage_emp AS SELECT * FROM corrupt_emp; To clear the attribute for a table use: execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('<schema>','<tablename>', flags=>dbms_repair.noskip_flag); execute DBMS_REPAIR.SKIP_CORRUPT_BLOCKS('VPOUSERDB','USERS', flags=>dbms_repair.noskip_flag); Setting the event in a Session ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Connect to Oracle as a user with access to the corrupt table and issue the command: ALTER SESSION SET EVENTS '10231 TRACE NAME CONTEXT FOREVER, LEVEL 10'; Now you should be able to issue a CREATE TABLE AS SELECT operation against the corrupt table to extract data from all non-corrupt blocks, but an export would still fail as the event is only set within your current session. Eg: CREATE TABLE salvage_emp AS SELECT * FROM corrupt_emp; Setting the event at Instance level ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This requires that the event be added to the init$ORACLE_SID.ora file used to start the instance: shutdown the database Edit your init<SID>.ora startup configuration file and ADD a line that reads: event="10231 trace name context forever, level 10" Make sure this appears next to any other EVENT= lines in the init.ora file. STARTUP If the instance fails to start check the syntax of the event parameter matches the above exactly. Note the comma as it is important. SHOW PARAMETER EVENT To check the event has been set in the correct place. You should see the initial portion of text for the line in your init.ora file. If not check which parameter file is being used to start the database. Select out the data from the table using a full table scan operation. Eg: Use a table level export or create table as select. Export Warning: If the table is very large then some versions of export may not be able to write more than 2Gb of data to the export file. See [NOTE:62427.1] <ml2_documents.showDocument?p_id=62427.1&p_database_id=NOT> for general information on 2Gb limits in various Oracle releases. Salvaging data from the corrupt block itself ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SKIP_CORRUPT and event 10231 extract data from good blocks but skip over corrupt blocks. To extract information from the corrupt block there are three main options: - Select column data from any good indexes This is discussed towards the end of the following 2 articles: Oracle7 - using ROWID range scans [NOTE:34371.1] <ml2_documents.showDocument?p_id=34371.1&p_database_id=NOT> Oracle8/8i - using ROWID range scans [NOTE:61685.1] <ml2_documents.showDocument?p_id=61685.1&p_database_id=NOT> - See if Oracle Support can extract any data from HEX dumps of the corrupt block. - It may be possible to salvage some data using Log Miner Once you have the data extracted ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Once you have the required data extracted either into an export file or into another table make sure you have a valid database backup before proceeding. The importance of this cannot be over-emphasised. Double check you have the SQL to rebuild the object and its indexes etc.. Double check that you have any diagnostic information if requested by Oracle support. Once you proceed with dropping the object certain information is destroyed so it is important to capture it now. Now you can: If 10231 was set at instance level: Remove the 'event' line from the init.ora file SHUTDOWN and RESTART the database. SHOW PARAMETER EVENT Make sure the 10231 event is no longer shown RENAME or DROP the problem table If you have space it is advisable to RENAME the problem table rather than DROP it at this stage. Recreate the table. Eg: By importing. Take special care to get the storage clauses correct when recreating the table. Create any indexes, triggers etc.. required Again take care with storage clauses. Re-grant any access to the table. If you RENAMEd the original table you can drop it once the new table has been tested. . #################################################################################################### SECTION 8: Other important RMAN notes: #################################################################################################### article 1: ========== Subject: RMAN: RAC Backup and Recovery using RMAN Doc ID: 243760.1 Type: BULLETIN Modified Date : 26-JAN-2009 Status: PUBLISHED "Checked for relevance on 21-Dec-2008" RAC Backup and Recovery using RMAN Objectives: =========== 1. Verify the database mode and archive destination. 2. Verify connectivity using sqlnet for target and catalog. 3. Determine your backup device 4. Understand how to create an RMAN persistent configuration for a RAC env. 5. Create backups to disk using 6. Backupset Maintenance using the configured retention policy 7. Restore and Recover a. complete b. incomplete 8. Review and understand the impact of resetlogs on the catalog. 9. RMAN Sample Commands Configuration: ============== This discussion is for a 2-node Oracle RAC Cluster. The logs are being archived to their respective node. We are allocating channels to each node to enable the autolocate feature of RMAN in a RAC env. 1. Verify the databases are in archivelog mode and archive destination. a. NODE 1: thread 1 SQL> archive log list; Database log mode Archive Mode Automatic archival Enabled Archive destination /u02/app/oracle/product/9.2.0/dbs/arch Oldest online log sequence 20 Next log sequence to archive 21 Current log sequence 21 b. NODE 2: thread 2 SQL> archive log list Database log mode Archive Mode Automatic archival Enabled Archive destination /u02/app/oracle/product/9.2.0/dbs/arch Oldest online log sequence 8 Next log sequence to archive 9 Current log sequence 9 2. Verify connectivity to the target nodes and catalog if used. a. % setenv TNS_ADMIN $ORACLE_HOME/network/admin b. % sqlplus /nolog c. SQL> connect sys/pwd@node1 as sysdba d. SQL> connect sys/pwd@node2 as sysdba e. SQL> connect rman/rman@rcat 3. Set your testing areas. Testing HOME for logs: /u02/home/usupport/rman Backups HOME Location: /rman/V920 4. Connect using RMAN to verify and set the controlfile persistent configuration. The controlfiles are shared between the instances so configuring the control- file on node 1 also sets it for all nodes in the RAC cluster. a. Alway note the target DBID connected to target database: V920 (DBID=228033884) b. Default Configuration RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u02/app/oracle/product/9.2.0/dbs/snapcf_V9201.f'; # default c. Make changes to the default that fit your business requirements. Note the retention policy can be set "TO REDUNDANCY x" or it can be set "TO RECOVERY WINDOW OF x DAYS", this is new in Oracle9i. In this example, using PARALLELISM 2 as 2 nodes are used. The PARALLELISM will than automaticly start 2 channels and will use the related CONFIGURE CHANNEL for additional clauses. CONFIGURE RETENTION POLICY TO REDUNDANCY 3; CONFIGURE BACKUP OPTIMIZATION OFF; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/V920/%F'; CONFIGURE DEVICE TYPE DISK PARALLELISM 2; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; CONFIGURE MAXSETSIZE TO UNLIMITED; CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/rman/V920/snapcf_V92321.f'; CONFIGURE CHANNEL 1 DEVICE TYPE DISK connect 'SYS/rac@node1'; CONFIGURE CHANNEL 2 DEVICE TYPE DISK connect 'SYS/rac@node2'; d. Review/Verify your new configuration. RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 3; CONFIGURE BACKUP OPTIMIZATION OFF; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/V920/%F'; CONFIGURE DEVICE TYPE DISK PARALLELISM 2; CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'SYS/rac@node1'; CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/rac@node2'; CONFIGURE MAXSETSIZE TO UNLIMITED; CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/rman/V920/snapcf_V92321.f'; 5. Make a backup using the new persistent configuration parameters. a. Backup database with differential incremental 0 and then archived logs using the delete input option. backup incremental level 0 format '/rman/V920/%d_LVL0_%T_%u_s%s_p%p' database; backup archivelog all format '/rman/V920/%d_AL_%T_%u_s%s_p%p' delete input; b. Backup again using differential inremental level 1 backup incremental level 1 format '/rman/V920/%d_LVL1_%T_%u_s%s_p%p' database; backup archivelog all format '/rman/V920/%d_AL_%T_%u_s%s_p%p' delete input; c. To simplify this in Oracle9i we can also use PLUS ARCHIVELOG Note: This uses a different alorithm then backup database and backup archivelog in separate commands. BACKUP incremental level 0 format '/rman/V920/%d_LVL0_%T_%u_s%s_p%p' database PLUS ARCHIVELOG format '/rman/V920/%d_AL_%T_%u_s%s_p%p' delete input; Algorithm for PLUS ARCHIVELOG: 1. Archive log current 2. Backup archived logs 3. Backup database level 0 4. Archive log current 5. Backup any remaining archived log created during backup 6. Backupset Maintenance using the configured retention policy RMAN> list backup summary; list backup by datafile; list backup of database; list backup of archivelog all; list backup of controlfile; Note: these above can be enhanced with the "until time" clause as well as the archivelog backups using "not backed up x times" to cut down on many copies of a log in several backupsets. Then continuing with SMR Server Managed Recovery use the change archivelog from...until...delete to remove old logs no longer needed on disk. RMAN> report obsolete; RMAN> delete obsolete; or delete noprompt obsolete; RMAN> report schema; 7. Restore and Recover Complete Recovery a. With the database mounted on the node1 and nomount on node2 connect to the target and catalog using RMAN. rman target / catalog rman/rman@rcat This script will restore and recover the database completely and open. All previous backup will still be available for use because there was not RESETLOGS command given. run { restore database; recover database; alter database open; } Incomplete Recovery Note: If you are using instance registration the database must be mounted to register with the listener. This means you must use the current control file for restore and recovery or setup a dedicated listener if not already done. RMAN requires a dedicated server connection and does not work with using instance registration before mounting the controlfile. Using the autobackup controlfile feature requires the DBID of the TARGET database. It must be set when the database is not mounted and only the controlfile and spfile (in 9.2>) can be restored this way. a. shutdown node1 and node2 b. startup nomount node2 and node1 c. start rman > rman trace reco1.log RMAN> connect catalog rman/rman@rcat RMAN> set dbid=228033884; RMAN> connect target d. Restore the controlfile from autobackup % rman trace recocf.log RMAN> SET DBID=228033884; RMAN> CONNECT TARGET RUN { SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE disk TO '/rman/V920/%F'; ALLOCATE CHANNEL d1 DEVICE TYPE disk; RESTORE CONTROLFILE FROM AUTOBACKUP MAXSEQ 5 # start at sequence 5 and count down (optional) MAXDAYS 5; # start at UNTIL TIME and search back 5 days (optional) MOUNT DATABASE; } e. Verify what is available for incomplete recovery. We will recover to the highest scn log sequence and thread. We will use the log sequence in this case. Your options are "until time", "until scn", or "until sequence". SQL> select max(sequence#) from v$archived_log 2 where thread#=1; MAX(SEQUENCE#) -------------- 25 SQL> select max(sequence#) from v$archived_log 2 where thread#=2; MAX(SEQUENCE#) -------------- 13 Note: In this case the scn is greater in thread 2 sequence# 13 then in sequence 25 from thread 1. So we will set the seqeunce to 14 for rman recovery because log recovery is always sequence+1 to end at +1 after applying the prior sequence. SQL> select sequence#, thread#, first_change#, next_change# 2 from v$archived_log 3 where sequence# in (13,25); SEQUENCE# THREAD# FIRST_CHANGE# NEXT_CHANGE# ---------- ---------- ------------- ------------ 25 1 1744432 1744802 13 2 1744429 1744805 SQL> select sequence#, thread#, first_change#, next_change# 2 from v$backup_redolog 3 where sequence# in (13,25); SEQUENCE# THREAD# FIRST_CHANGE# NEXT_CHANGE# ---------- ---------- ------------- ------------ 25 1 1744432 1744802 13 2 1744429 1744805 f. If using LMT Temporary tablespace the controlfile will have the syntax to add the tempfile after recovery is complete. SQL> alter database backup controlfile to trace; Example: # Commands to add tempfiles to temporary tablespaces. # Online tempfiles have complete space information. # Other tempfiles may require adjustment. ALTER TABLESPACE TEMP ADD TEMPFILE '/dev/usupport_vg/rV92B_temp_01.dbf' SIZE 41943040 REUSE AUTOEXTEND OFF; # End of tempfile additions. # g. Since log sequence 13 thread 2 next_change# is 3 changes ahead of thread 1 sequence 25 we are using dequence 14 to stop recovery. This will restore the datafiles and recover them completely using the online logs. run { set until sequence 14 thread 2; restore database; recover database; alter database open resetlogs; } 8. Review and understand the impact of resetlogs on the catalog. RMAN> list incarnation of database V920; Note: After resetlogs there are 2 incarnations in the recovery catalog. Only one incarnation can be current at one time for a given dbid. The Inc Key keeps track of the database incarnations. List of Database Incarnations DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time ------- ------- -------- ---------------- --- ---------- ---------- 2656 2657 V920 228033884 NO 1 29-MAY-03 2656 3132 V920 228033884 YES 1744806 13-JUN-03 9. RMAN Sample Commands a. With a dedicated listener (not using instance registration) restoring the controlfile. run { allocate channel d1 type disk connect 'sys/rac@node1'; allocate channel d2 type disk connect 'sys/rac@node2'; set until sequence 14 thread 2; restore controlfile; alter database mount; release channel d1; release channel d2; } b. Backup Archivelog backup archivelog all not backed up 3 times; backup archivelog until time 'sysdate-2' not backed up 2 times; #################################################################################################### SECTION 9: Other: #################################################################################################### ----- Note: ----- IO04207: CM8.3 FP1 WITH ORACLE: ORA-01455 ERROR MESSAGES FROM THE LS MONITOR IN THE ICMSERVER.LOG. APAR status Closed as program error. Error description CM8.3 Fix Pack 1 with Oracle. The ICMSERVER.LOG contains the following ORA-01455 error messages from the LS Monitor: Library Server Monitor ConnectToLS ... Library Server Monitor has connected Library Server Monitor LoadSysControlTable ... Loaded SysControl Library Server Monitor RMStatusThread ... Start RM Status loop - interval 60 Library Server Monitor RMStatusLoadTable ... ORA-01455: converting column overflows integer datatype The cause for this error seems to be the use of a PORT larger that 9999 (e.g. 49000). Local fix Workaround: Use a PORT less than 10000. Problem summary This is caused when the port for a resoource manager is set to something greater than 10000, which results in column data overflow since the column is an INTEGER. Problem conclusion The problem has been fixed in Fix Pack3. Temporary fix Comments APAR information APAR number IO04207 Reported component name LIBRARY SERVER Reported component ID 5724B1907 Reported release 830 Status CLOSED PER PE NoPE HIPER NoHIPER Special Attention NoSpecatt Submitted date 2006-04-06 Closed date 2006-08-28 Last modified date 2006-08-28 ----- Note: ----- Problem This technote describes an error that can occur when a IBM® Rational® Portfolio Manager user copies the calculated results when using Oracle 10g with Tomcat 5.5. Cause The error ORA-00600 with arguments [kkslpbp], it is related to CURSOR_SHARING initial parameter for the instance. Steps to reproduce: Create a proposal Create two tasks underneath the proposal (Task1: 2 days and Task2: 2 days) Assign resources to the tasks created in Step 2 Set dependencies (Task1 finish and Task2 start) Copy proposal to plan Calculate/level the project from June 1 2006 Copy calculated results Calculate/level the project from August 1, 2006 Copy calculated results again Go to Communication view and you will see Error:ORA-600 appears in the notification record Solution You have two options to resolve this issue. Contact Oracle Technical Support to resolve ORA-600 error without changing the *.cursor_sharing value from SIMILAR to EXACT. -OR- Change the *.cursor_sharing value from SIMILAR to EXACT. Note: This change can cause performance issues. Your DBA needs to monitor database performance and should tune the database accordingly. If performance issues are identified you should increase the library cache by increasing the SHARED_POOL_SIZE parameter for the instance. Steps for changing *.cursor_sharing value from SIMILAR to EXACT Shutdown the Oracle Instance: Login with sqlplus as a user with SYSDBA privileges. At SQL command prompt enter the following: SQL> create pfile from spfile; File created. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. Update the pfile; Navigate to the \%ORACLE_HOME%\database\ directory and locate the pfile. The name of the file should be INITXXXX.ORA where XXXX is your database name. Example: if the database is IBMRPM62, the file name would be INITibmrpm62.ORA. Open the file and set the *.cursor_sharing value from SIMILAR to EXACT Example: *.cursor_sharing='EXACT' Save your changes Enabling your changes: 1. At SQL command prompt SQL> startup pfile=INITibmrpm62.ORA ORACLE instance started. SQL> create spfile from pfile; File created. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. SQL> select value from v$parameter where name = 'cursor_sharing'; VALUE ---------------------------------------------------------- EXACT SQL>exit 2. Stop Tomcat 3. Start Tomcat 4. Log into RPM ----- Note: ----- Old stuff: ORA-00600 errors running TEC v3.8 + FP01 and Oracle 9.2 Technote (troubleshooting) Problem(Abstract) Running TEC 3.8 (FP01) on an AIX Regatta system, there are generic Oracle ORA-00600 errors. Cause There are select statements being issued on the 'defroles' table, and this is causing other SQL queries - e.g. console refreshes, to error when they would normally work. This in turn is causing the TEC server to eventually crash. Resolving the problem There are select statements being issued on the 'defroles' table, and this is causing other SQL queries - e.g. console refreshes, to error when they would normally work. This in turn is causing the TEC server to eventually crash. Ensure that you have installed Oracle patch 9.2.04 ----- Note: ----- Impromptu and ORA-600 ORA-00600: internal error code Technote (troubleshooting) Problem(Abstract) Error: ORA-00600: internal error code, arguments: [], [], [], [], [], [], [] when attempting to create a Impromptu report with a division in the list footer. Resolving the problem THis issue may be resolved with changing the processing to Flexible Processing in both the Catalog and Report. Catalog --> User Profiles --> Client Server --> Check Flexible Processing Check Report --> Query --> Client Server --> Check Flexible Processing ----- Note: ----- Toad displays error 'IN' is not a valid integer value Submitted by kurtvm on Mon, 01/26/2009 - 06:05. Problem Description You are using TOAD version that is less than 8.6.1 and is connecting to Oracle database release 2(10.2.0.2 or higher) , then while looking source of the stored procedure toad displays error message TOAD ERROR: 'IN' is not a valid integer value in a pop-up window. This problem remains if you try to connect to oracle database 11g with toad version less than 8.6.1. Cause of the Problem The problem happens because Oracle made a change to the ALL_ARGUMENTS view at release 10.2.0.2 and this 'broke' TOAD. Until 10.2.0.1 there is no problem. But starting with 10.2.0.2 oracle has added a new column named SUBPROGRAM_ID in the ALL_ARGUMENTS view and this causes toad unusable. Have a look at ALL_ARGUMENTS view between two releases. In 10.2.0.1, SQL> desc all_arguments; Name Null? Type ----------------------------------------- -------- ---------------------------- OWNER NOT NULL VARCHAR2(30) OBJECT_NAME VARCHAR2(30) PACKAGE_NAME VARCHAR2(30) OBJECT_ID NOT NULL NUMBER OVERLOAD VARCHAR2(40) ARGUMENT_NAME VARCHAR2(30) POSITION NOT NULL NUMBER SEQUENCE NOT NULL NUMBER DATA_LEVEL NOT NULL NUMBER DATA_TYPE VARCHAR2(30) DEFAULT_VALUE LONG DEFAULT_LENGTH NUMBER IN_OUT VARCHAR2(9) DATA_LENGTH NUMBER DATA_PRECISION NUMBER DATA_SCALE NUMBER RADIX NUMBER CHARACTER_SET_NAME VARCHAR2(44) TYPE_OWNER VARCHAR2(30) TYPE_NAME VARCHAR2(30) TYPE_SUBNAME VARCHAR2(30) TYPE_LINK VARCHAR2(128) PLS_TYPE VARCHAR2(30) CHAR_LENGTH NUMBER CHAR_USED VARCHAR2(1) In 11g, SQL> desc all_arguments Name Null? Type ----------------------------------------- -------- ---------------------------- OWNER NOT NULL VARCHAR2(30) OBJECT_NAME VARCHAR2(30) PACKAGE_NAME VARCHAR2(30) OBJECT_ID NOT NULL NUMBER OVERLOAD VARCHAR2(40) SUBPROGRAM_ID NUMBER ARGUMENT_NAME VARCHAR2(30) POSITION NOT NULL NUMBER SEQUENCE NOT NULL NUMBER DATA_LEVEL NOT NULL NUMBER DATA_TYPE VARCHAR2(30) DEFAULTED VARCHAR2(1) DEFAULT_VALUE LONG DEFAULT_LENGTH NUMBER IN_OUT VARCHAR2(9) DATA_LENGTH NUMBER DATA_PRECISION NUMBER DATA_SCALE NUMBER RADIX NUMBER CHARACTER_SET_NAME VARCHAR2(44) TYPE_OWNER VARCHAR2(30) TYPE_NAME VARCHAR2(30) TYPE_SUBNAME VARCHAR2(30) TYPE_LINK VARCHAR2(128) PLS_TYPE VARCHAR2(30) CHAR_LENGTH NUMBER CHAR_USED VARCHAR2(1) Solution of the Problem 1.With toad version less than 8.6.1 don't connect to oracle version 10.2.0.2 or higher. Not a actual solution. 2.Upgrade to toad version. On version 9.5.0 it works fine. 3.Alter the ALL_ARGUMENTS view and move the SUBPROGRAM_ID column to the end on the database. This is not supported according to oracle. However on your test database it is safer to do it. But it is not recommended to do it on your production database though no side effect I ever get. In your 11.1g database connect as "sys as sysdba" and create the view as below. CREATE OR REPLACE FORCE VIEW "SYS"."ALL_ARGUMENTS" ("OWNER", "OBJECT_NAME", "PACKAGE_NAME", "OBJECT_ID", "OVERLOAD", "ARGUMENT_NAME", "POSITION", "SEQUENCE", "DATA_LEVEL", "DATA_TYPE", "DEFAULT_VALUE", "DEFAULT_LENGTH", "IN_OUT", "DATA_LENGTH", "DATA_PRECISION", "DATA_SCALE", "RADIX", "CHARACTER_SET_NAME", "TYPE_OWNER", "TYPE_NAME", "TYPE_SUBNAME", "TYPE_LINK", "PLS_TYPE", "CHAR_LENGTH", "CHAR_USED") AS select u.name, /* OWNER */ nvl(a.procedure$,o.name), /* OBJECT_NAME */ decode(a.procedure$,null,null, o.name), /* PACKAGE_NAME */ o.obj#, /* OBJECT_ID */ decode(a.overload#,0,null,a.overload#), /* OVERLOAD */ a.argument, /* ARGUMENT_NAME */ a.position#, /* POSITION */ a.sequence#, /* SEQUENCE */ a.level#, /* DATA_LEVEL */ decode(a.type#, /* DATA_TYPE */ 0, null, 1, decode(a.charsetform, 2, 'NVARCHAR2', 'VARCHAR2'), 2, decode(a.scale, -127, 'FLOAT', 'NUMBER'), 3, 'NATIVE INTEGER', 8, 'LONG', 9, decode(a.charsetform, 2, 'NCHAR VARYING', 'VARCHAR'), 11, 'ROWID', 12, 'DATE', 23, 'RAW', 24, 'LONG RAW', 29, 'BINARY_INTEGER', 69, 'ROWID', 96, decode(a.charsetform, 2, 'NCHAR', 'CHAR'), 100, 'BINARY_FLOAT', 101, 'BINARY_DOUBLE', 102, 'REF CURSOR', 104, 'UROWID', 105, 'MLSLABEL', 106, 'MLSLABEL', 110, 'REF', 111, 'REF', 112, decode(a.charsetform, 2, 'NCLOB', 'CLOB'), 113, 'BLOB', 114, 'BFILE', 115, 'CFILE', 121, 'OBJECT', 122, 'TABLE', 123, 'VARRAY', 178, 'TIME', 179, 'TIME WITH TIME ZONE', 180, 'TIMESTAMP', 181, 'TIMESTAMP WITH TIME ZONE', 231, 'TIMESTAMP WITH LOCAL TIME ZONE', 182, 'INTERVAL YEAR TO MONTH', 183, 'INTERVAL DAY TO SECOND', 250, 'PL/SQL RECORD', 251, 'PL/SQL TABLE', 252, 'PL/SQL BOOLEAN', 'UNDEFINED'), default$, /* DEFAULT_VALUE */ deflength, /* DEFAULT_LENGTH */ decode(in_out,null,'IN',1,'OUT',2,'IN/OUT','Undefined'), /* IN_OUT */ length, /* DATA_LENGTH */ precision#, /* DATA_PRECISION */ decode(a.type#, 2, scale, 1, null, 96, null, scale), /* DATA_SCALE */ radix, /* RADIX */ decode(a.charsetform, 1, 'CHAR_CS', /* CHARACTER_SET_NAME */ 2, 'NCHAR_CS', 3, NLS_CHARSET_NAME(a.charsetid), 4, 'ARG:'||a.charsetid), a.type_owner, /* TYPE_OWNER */ a.type_name, /* TYPE_NAME */ a.type_subname, /* TYPE_SUBNAME */ a.type_linkname, /* TYPE_LINK */ a.pls_type, /* PLS_TYPE */ decode(a.type#, 1, a.scale, 96, a.scale, 0), /* CHAR_LENGTH */ decode(a.type#, 1, decode(bitand(a.properties, 128), 128, 'C', 'B'), 96, decode(bitand(a.properties, 128), 128, 'C', 'B'), 0) /* CHAR_USED */ from obj$ o,argument$ a,user$ u where o.obj# = a.obj# and o.owner# = u.user# and (owner# = userenv('SCHEMAID') or exists (select null from v$enabledprivs where priv_number in (-144,-141)) or o.obj# in (select obj# from sys.objauth$ where grantee# in (select kzsrorol from x$kzsro) and privilege# = 12)); View created. After creating now try to connect to oracle database with your existing toad and problem should go away. ----- Note: ----- Old stuff: ORA-00600 ORA-600 [2103] PURPOSE: This article discusses the internal error "ORA-600 [2103]", 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 [2103][a][b][c][d] VERSIONS: versions 7.3.X through 9.x DESCRIPTION: Oracle is attempting to acquire an enqueue. If this operation times out, an ORA-600 [2103] error is reported. There are three formats of this error depending on Oracle release and operation. Each format is identified by the number of additional arguments. Prior to Oracle Server release 7.3.4 (one additional argument) ------------------------------------------------------ ORA-600 [2103] [a] Meaning: Oracle has waited too long for the control file enqueue. ARGUMENTS: Arg [a] Time out - the time waited for the enqueue, in seconds. (normally 900 seconds ie 15 Minutes) From Oracle 7.3.4 through 9.x (4 additional arguments) -------------------------------------------------------- ORA-600 [2103] [a] [b] [c] [d] Meaning: Oracle has waited too long for the control file enqueue. This error has the same meaning as the single argument case above - we simply output additional information. ARGUMENTS: Arg [a] 1 (Read only indicator - 0 for updates, 1 for read only) Arg [b] 0 (Type indicator - 0 and 4 for ENQUEUE) Arg [c] 1 (Wait indicator - 1 indicates we should wait for the request) Arg [d] Time out - the time waited for the enqueue, in seconds. (normally 900 seconds ie 15 Minutes) Oracle Server Release 9.x ------------------------- ORA-600 [a] [b] Meaning: Oracle is trying to write a Checkpoint Progress record and has waited too long for the enqueue. ARGUMENTS: ORA-600 [a] [b] --------------- Arg [a] 1 (Wait indicator - 1 indicates we should wait for the request) Arg [b] 256 (indicates we skip to the front of the convert queue) FUNCTIONALITY: CONTROL FILE MANAGEMENT COMPONENT IMPACT: Possible Instance Failure SUGGESTIONS: Check the alert log to see how often a logfile switch is taking place. Try and ensure that REDO log files are sized such that a log switch takes place approximately every half hour during heavy load. This will reduce the number of times we need to obtain the control file enqueue. Tune your datafile layout to resolve I/O contention. Check with the Hardware vendor to ensure there are no hardware problems and that you are on the latest OS patch level. In the case of IBM, see [NOTE:1058194.6] to obtain the correct OS patch. Known issues: Bug:1223914 OERI:2103 Concurrent ALTER TABLESPACE READ WRITE/READ ONLY Fixed in Oracle releases 8.1.6.3 and 8.1.7.0 Bug:1390375 DEFUNCT CHECKPOINT PROCESS HOLDS LOCK CAUSING ORA-600 [2103] An AIX port specific issue. (Note:1058194.6) ----- Note: ----- ORA-00600 ORA-600 [kkslgop1] in SELECT when CURSOR_SHARING IS NOT EXACT. Error code: ORA-00600: internal error code, arguments: [kkslgop1], [], [], [], [], [], [], [] Current SQL statement for this session: SELECT COMP_TIME FROM CSTMAPSTATUS WHERE CSTID = :"SYS_B_0" AND SLOTNO = :"SYS_B_1" Oracle kernel function from which the problem is raised: kkslgop(). This is a function of Oracle Compilation Layer. Process state: PROCESS STATE ------------- ... ---------------------------------------- SO: 404c6264, type: 3, owner: 403cde98, pt: 0, flag: INIT/-/-/0x00 (session) trans: 40e83928, creator: 403cde98, flag: (8000041) USR/- BSY/-/-/-/-/- DID: 0001-0014-00000002, short-term DID: 0000-0000-00000000 txn branch: 40f8201c oct: 3, prv: 0, user: 24/APPMGR O/S info: user: Administrator, term: CIMMB, ospid: 219:228, machine: PDP1_MES_DOM\CIMMB program: TIME_GAP.exe last wait for 'SQL*Net message from dblink' blocking sess=0x0 seq=60687 wait_time=-1 driver id=54435000, #bytes=1, =0 ---------------------------------------- ... Problem explanation: As you see in your SQL statement, your bind variables are system generated bind variables. In other words, cursor sharing is enabled in your database. Also, as seen in the process state, your last wait event is SQL*Net message from dblink. That means a dblink operation had been done before. Workaround: Use cursor_sharing=exact Bug: Bug:2169897 ORA-600 ARGUMENTS: [KKSLGOP1] VIA SELECT ACROSS DB_LINK Bug:2159152 CURSOR_SHARING=FORCE MAY NOT SHARE STATEMENTS USING VIEWS IN 8172/8173 Back to top [ Show » ] ubTools Support - 15/Jul/07 05:42 PM Error code: ORA-00600: internal error code, arguments: [kkslgop1], [], [], [], [], [], [], [] Current SQL statement for this session: SELECT COMP_TIME FROM CSTMAPSTATUS WHERE CSTID = :"SYS_B_0" AND SLOTNO = :"SYS_B_1" Oracle kernel function from which the problem is raised: kkslgop(). This is a function of Oracle Compilation Layer. Process state: PROCESS STATE ------------- ... ---------------------------------------- SO: 404c6264, type: 3, owner: 403cde98, pt: 0, flag: INIT/-/-/0x00 (session) trans: 40e83928, creator: 403cde98, flag: (8000041) USR/- BSY/-/-/-/-/- DID: 0001-0014-00000002, short-term DID: 0000-0000-00000000 txn branch: 40f8201c oct: 3, prv: 0, user: 24/APPMGR O/S info: user: Administrator, term: CIMMB, ospid: 219:228, machine: PDP1_MES_DOM\CIMMB program: TIME_GAP.exe last wait for 'SQL*Net message from dblink' blocking sess=0x0 seq=60687 wait_time=-1 driver id=54435000, #bytes=1, =0 ---------------------------------------- ... Problem explanation: As you see in your SQL statement, your bind variables are system generated bind variables. In other words, cursor sharing is enabled in your database. Also, as seen in the process state, your last wait event is SQL*Net message from dblink. That means a dblink operation had been done before. Workaround: Use cursor_sharing=exact Bug: Bug:2169897 ORA-600 ARGUMENTS: [KKSLGOP1] VIA SELECT ACROSS DB_LINK Bug:2159152 CURSOR_SHARING=FORCE MAY NOT SHARE STATEMENTS USING VIEWS IN 8172/8173 ----- Note: ----- thread from internet http://www.experts-exchange.com/Database/Oracle/10.x/Q_23217596.html Solaris OS patch causes ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1] ... Asked by rdannels in Oracle 10.x, Sun Solaris, Oracle Database The sys admins applied some upgrades on this Sun Sparc 2000 box running Solaris 10. Right after, when trying to restart the Oracle 10.2.0.3.0 database there, it would only give ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1] which says that Oracle could not find the hostname in /etc/hosts. The hostname is plainly there and readable by all. From where and what hostname is Oracle trying to find at instance startup time? We have tried reinstalling the product, editing the hosts file, and bouncing the box with no change in the error. ----- Note: ----- Configuration Summary: Oracle Database 10g Release 2 (Single Instance) and Oracle Real Application Clusters (RAC) on SUSE Enterprise Server 9 x86-64 using Fibre Channel attached storage Publication Date: June 12, 2006 Version: 1.1 Server Platform: IBM BladeCenter HS20 Storage: IBM TotalStorage DS4500 Oracle Software: Oracle Database 10g Release 2 (10.2.0.2) for Linux x86-64 Linux Distribution: SLES 9 Service Pack 2 x86-64 Server and Storage Platform Details 2 x IBM BladeCenter HS20 2 x Intel(R) Xeon(TM) with Extended Memory 64 Technology (EM64T) 3.0 GHz 8 GB RAM 1 x 40 GB IDE HD 2 x integrated Gigabit Ethernet ports (Broadcom) 1 x addon BladeCenter Fibre Channel Expansion Card (2 ports, QLogic) 1 x IBM TotalStorage DS4500 28 x 73 GB 15K RPM HD Additional models covered by this configuration IBM System x: x3400 (x226) x3500 (x236) x3800 (x260) x3550 (x336) x3650 (x346) x3850 (x366) IBM System Storage DS4000 Family: DS4100 DS4300 and DS4300 Turbo DS4700 DS4800 Linux Distribution Details SLES 9 Service Pack 2 x86-64 (default install) kernel-smp-2.6.5-7.201.x86_64.rpm (updated kernel) Additional packages needed from distribution binutils-2.15.90.0.1.1-32.10.x86_64.rpm gcc-3.3.3-43.34.x86_64.rpm gcc-c3.3.3-43.34.x86_64.rpm glibc-devel-2.3.3-98.47.x86_64.rpm glibc-devel-32bit-9-200506062332.x86_64.rpm glibc-2.3.3-98.47.x86_64.rpm glibc-32bit-9-200506071326.x86_64.rpm libaio-0.3.102-1.2.x86_64.rpm libstdc+++3.3.3-43.34.x86_64.rpm libstdc+++-devel-3.3.3-43.34.x86_64.rpm make-3.80-184.1.x86_64.rpm pdksh-5.2.14-780.7.x86_64.rpm sysstat-5.0.1-35.4.x86_64.rpm xscreensaver-4.16-2.6.x86_64.rpm Additional packages needed from IBM IBM FAStT FC-2 and DS4000 FC2-133 Host Bus Adapter non-failover device driver for Linux Kernel 2.6 IA-32, IA-64, AMD-64 Version 8 IBM TotalStorage DS4000 Linux RDAC for 2.6.x kernel Version 9 Boot options selinux=0 elevator=deadline /etc/modprobe.conf.local: options qla2xxx displayConfig=1 ql2xfailover=0 remove qla2xxx /sbin/modprobe -r --first-time --ignore-remove qla2xxx && { /sbin/modprobe -r --ignore-remove qla2xxx_conf; } /etc/sysctl.conf settings fs.file-max=327679 fs.aio-max-nr=3145728 kernel.msgmni=2878 kernel.msgmax=8192 kernel.msgmnb=65536 kernel.sem=250 32000 100 142 kernel.shmmni=4096 kernel.shmall=3279547 # set to value half the size of physical memory kernel.shmmax=3700000000 kernel.sysrq=1 net.core.rmem_default=262144 # rmem_max can be tuned based on workload to balance performance versus lowmem usage net.core.rmem_max=262144 net.core.wmem_default=262144 net.core.wmem_max=262144 # needed to enable hugepage usage vm.disable_cap_mlock=1 /etc/security/limits.conf: # depending on size of db, these may need to be larger oracle soft nofile 131072 oracle hard nofile 131072 oracle soft nproc 131072 oracle hard nproc 131072 oracle soft memlock 50000000 oracle hard memlock 50000000 Driver Modules The network driver module use (tg3) is the version supplied with SLES 9 SP2 x86-64 The hangcheck-timer module used is the version supplied with SLES 9 U2 x86-64 Miscellaneous The swap partition is the size of physical RAM. 2 gigabit networks configured: public and interconnect Oracle Software Details Oracle Database 10g Release 2 (10.2.0.2) Single Instance and Oracle Real Application Clusters (RAC) for Linux x86-64 patch 5071492 patch 4639236 patch 4690794 patch 5036588 oracleasm-2.6.5-7.201-smp-2.0.1-1.x86_64.rpm oracleasm-support-2.0.1-1.x86_64.rpm oracleasmlib-2.0.1-1.x86_64.rpm init.ora settings: filesystemio_options=directio (required for RAC) Filesystems tested: ext2 ASM using block devices ASM using ASMLib RAC ocr and voting disk files raw devices Configuration Feedback Bug Summary Number 5041764 CFQ io scheduler can delay/hang io (bz 151368) affects: heavy io access to raw/block devices symptom: io requests will start to hang or take a long to complete RAC node could be evicted workaround: boot w/ elevator=deadline 5071492 LMS crash with ORA-00600: internal error code, arguments: [kclastf_1], [2], [], affects: 10.2.0.2 RAC symptom: the instance could terminate solution: apply patch 5071492 4639236 ORA-600 [kclcls_5] in RAC instance affects: 10.2.0.2 RAC symptom: the instance could terminate solution: apply patch 4639236 4690794 "ERROR IN KQLMBIVG SEE LCK TRACE FILE" [LT] [LB] KJUSERCLIENTLOCK affects: 10.2.0.2 RAC symptom: Error messages in the alert logs solution: apply patch 4690794 5215593 unable to start RAC with db_cache_size > 4gb affects: RAC instances with > 4gb db_cache_size symptom: nodes that started up correctly with 10.2.0.1 may fail to startup with ORA-4031 errors in 10.2.0.2 workaround: set _ksmg_granule_size=33554432 in the init.ora. Larger sga sizes may need a higher value. 5215622 libknlopt.a not relinked affects: 10.2.0.2 RAC (did not occur in 10.1) symptom: may get ORA-7445 errors during startup workaround: manually relink on each node 5041394 relink errors after upgrading from 10.1 to 10.2 affects: 10.1 -> 10.2 upgrade process symptom: during 10.2 upgrade, relink step will fail with 'undefined reference' errors workaround: after doing 10.2 prereq steps, rename $ORACLE_HOME/lib/stubs to $ORACLE_HOME/lib/stubs.10.1 $ORACLE_HOME/lib32/stubs to $ORACLE_HOME/lib32/stubs.10.1 then start installing 10.2.0.1 4639236 ORA-600 [kclcls_5] in RAC instance affects: 10.2.0.2 RAC symptom: the instance could terminate solution: apply patch 4639236 4690794 "ERROR IN KQLMBIVG SEE LCK TRACE FILE" [LT] [LB] KJUSERCLIENTLOCK affects: 10.2.0.2 RAC symptom: Error messages in the alert logs solution: apply patch 4690794 5036588 LMD0 PROCESS RECEIVED OS SIGNAL #11 affects: 10.2.0.2 RAC symptom: the instance could terminate solution: apply patch 5036588 5021707 CSS should open block device voting disk with o_direct affects: 10.2.0.2 RAC when voting or ocr disk is a block device symptom: RAC reconfiguration may not occur properly solution: use raw devices for ocr and voting disks 5219517 failing RAC interconnect causes ASM to hang affects: 10.2.0.2 RAC using ASM (2-node) symptom: ifconfig down of RAC interconnect on node 1 causes surviving node 2 ASM instance to hang. This may occur during testing to simulate interconnect failure. solution: RAC properly handles this failure case when the interconnect is physically disconnected vs. ifconfig down which is simulating the failure 5058952 e1000 flow control defaults to none in the 2.6 kernel affects: e1000 network interfaces with heavy traffic symptom: RAC interconnect may get lost blocks solution: load e1000 with FlowControl1=1 (Rx) 5292056 encountering "bad page state at prep_new_page" while shutting the database affects: RAC instances symprom: encountering "bad page state at prep_new_page" in /var/log/messages workaround: none at the moment ----- Note: ----- ORA-00600 ORA-600 [qks3tAssert:1] Old stuff: An ORA-00600 internal error occurs when using JDBC with Oracle 9i Technote (troubleshooting) Problem(Abstract) The following internal Oracle error occurs when accessing an Oracle 9.2 database. This error occurs when using Java™ Database Connectivity (JDBC) with the Oracle thin driver, although the problem might not be limited to that combination. All occurrences of the ORA-00600 error contain the same qks3tAssert:1 and 2304 arguments. ORA-00600: internal error code, arguments: [qks3tAssert:1], [2304], [], [], [], [], [], [] Cause This error typically occurs when multiple inserts, reads, and updates are made using an Oracle XA data source. Oracle bug 3970630 tracks this problem. The error might also occur while using Service Data Objects (SDO) to access the database, but might not be limited to that scenario. Resolving the problem IBM® is working with Oracle on a fix for the problem. Until that fix is available, an alternative solution is to upgrade to Oracle 10g. ----- Note: ----- thread from internet http://oradbatips.blogspot.com/2007/10/tip-62-ora-600-librarycachenotemptyoncl.html ORA-00600 ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE] TIP 62#: ORA-600 [LIBRARYCACHENOTEMPTYONCLOSE] DURING DB 10g SHUTDOWN (2) If you follow my blog, in previous post I suggested to put "Before shutdown" trigger to resolve ORA-600 error during database shutdown. Since setting this trigger for some clients, shutdown has worked properly.However there were some odd situations which I found the following message in Alert log. ORA-00604: error occurred at recursive SQL level 1 ORA-12663: Services required by client not available on the server ORA-36961: Oracle OLAP is not available. ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1 ORA-06512: at line 15 Above situation would be fixed by disabling SYS.OLAPISTARTUPTRIGGER and SYS.OLAPISHUTDOWNTRIGGER triggers. As the result, shutdown trigger can be something like this : CREATE or replace TRIGGER flush_shared_pool BEFORE SHUTDOWN ON DATABASE BEGIN execute immediate 'alter TRIGGER SYS.OLAPISTARTUPTRIGGER DISABLE'; execute immediate 'ALTER TRIGGER SYS.OLAPISHUTDOWNTRIGGER DISABLE'; execute immediate 'ALTER SYSTEM FLUSH SHARED_POOL'; execute immediate 'alter TRIGGER SYS.OLAPISTARTUPTRIGGER ENABLE'; execute immediate 'ALTER TRIGGER SYS.OLAPISHUTDOWNTRIGGER ENABLE'; EXCEPTION WHEN OTHERS THEN RAISE_APPLICATION_ERROR (num => -20000, msg => 'Error flushing pool'); END; Please let me know whether or not this piece of code resolves the issue. P.S :Latest update from Oracle indicates that this bug will be fixed in 10.2.0.4. ----- Note: ----- Buglist Oracle 10.2.x Windows: ============================== Subject: 10.2.0.x Oracle Database and Networking Patches for Microsoft Platforms Doc ID: 342443.1 Type: BULLETIN Modified Date : 14-FEB-2009 Status: PUBLISHED Overview The following article provides a full list of bug fixes included in the 10.2.0.x patch bundles (patch set exception bundles) for the Microsoft Windows platforms, for additional information and target availability dates please refer to Note 161549.1 : 10.2.0.4.0 Patch Bundles 10.2.0.4.0 Patch Set 10.2.0.3.0 Patch Bundles 10.2.0.3.0 Patch Set 10.2.0.2.0 Patch Bundles 10.2.0.2.0 Patch Set 10.2.0.1.0 Patch Bundles For details of the fixes included in the Generic Patch Set 10.2.0.x please refer to Note 316900.1. Wherever possible Oracle tries to keep the contents of patch set exception bundles consistent between 32-Bit, 64-Bit (x64) and 64-Bit (Itanium / IA64). However because they are released on different dates, in some instances, the later dated bundle may contain some additional fixes. Where this occurs these fixes will be included in the next patch bundle. In the following table, additional fixes in the 32-Bit bundle are highlighted in green, additional fixes in the 64-Bit (Itanium) bundle are highlighted in red and additional fixes in the 64-Bit (x64) bundle are highlighted in orange. Some bugs listed below may not be published, in these cases the abstract has been enhanced: 10.2.0.4.0 Patch 16 (10.2.0.4.16P) 32-Bit Patch 8225197 64-Bit (x64) Patch 8225198 BaseBug Abstract Bug 6656309 ASM: All ASM operations hang during the offline of all disks in a failgroup. Bug 7516867 DICTIONARY: Wrong results from literal replacement with fix for Bug 6163785. Bug 6991626 EXTENSIBILITY: Data pump exports fail to write large volumes of data and return "ORA-22813: operand value exceeds system limits". Bug 7519687 OPTIMIZER: The presence of a subquery in the select list of an outer query block could cause a crash / ORA-7445 [intel_new_memcpy] if complex view merging was carried out. Bug 8201796 OPTIMIZER: Merge of optimizer fixes: Bug 6319761 : ORA-1476 from DBMS_STATS.GATHER_SCHEMA_STATS. Bug 7509689 : ORA-940 on startup with _FIX_CONTROL. Bug 7654407 : Query using extended stats fails with ORA-7445 [kkestGetColGroupNdv]. Bug 7690331 : Wrong Results (duplicate rows) with unique subquery and star / temp transformation. Bug 5099019 : dbms_stats does not account for empty blocks when gathering index leaf blocks while ANALYZE does. Bug 7229351 : Users may see dbms_stats fail when the object name contains special characters such as '\'. Bug 6894671 OPTIMIZER: Join elimination in a query block with an outer join can cause wrong results. Bug 7170213 PARAEXEC: ORA-12842 can be reported to a user session when executing a parallel query, this is normal but can cause problems for some applications. Bug 6896371 PARTITIONING: Dictionary corruption from partition maintenance DDL resulting in ORA-1008 from DBMS_STATS. Bug 6155146 QRYREWRITE: Wrong results can occur due to query rewrite if a filter predicate is pushed inside a named view prior to rewrite. Bug 5849687 RDBMS: ORA-7445 [kghssapage] / core dumo can occur (using XML with varrayStoreAsTable = True). Bug 6379441 RDBMS: ORA-600 [kdlm_merge_lobs] during a LONG to LOB or LOB to LOB parallel migration. Bug 7296258 RDBMS: SQL executing against remote objects that have undergone literal replacement might return incorrect results. Bug 7634610 RDBMS: NLS_COMP = ANSI gives wrong results comparing CHAR with VARCHAR2 when values contain trailing spaces. Bug 6737765 RDBMS: PMON fails with ORA-7445 [kgskrecalc] causing an instance crash when cleaning up dead processes. Bug 5686407 RDBMS: SGA memory corruption / instance crash with various ORA-600 [171XX] when using XDB. Bug 7828479 SPATIAL: Query using SDO_ARC_DENSIFY fails with ORA-7445 [mdcgarcseggen]. Bug 6313035 SQLEXEC: ORA-600 [kdibc3position] can occur when executing a query which uses a BITMAP MERGE row source. Bug 6491175 XDB: A stack overflow condition can occur under qmxtriCheckAndRewriteQb_rec when re-writing an XDB query with very complex predicate structure. Bug 7003718 XDKC: XVM transform produces duplicate values. 10.2.0.4.0 Patch 15 (10.2.0.4.15P) 32-Bit Patch 7715044 64-Bit (x64) Patch 7715057 BaseBug Abstract Bug 6270137 ASM: Unnecessary acquisition of the list header block in ASM. Bug 6730125 BUFFERCACHE: During instance recovery a space operation may return ORA-600 [kcbnew_3]. Bug 7513673 FLASHBACK: ORA-38754 issuing FLASHBACK DATABASE to a timestamp. Bug 7305703 ODP.NET: ORA-24373, ORA-1036, access violation after ODP.NET encounters ORA-54. Bug 7450460 ODP.NET: LOBS (OracleBlob / OracleClob) which are created as temporary LOBS in a PL/SQL procedures and returned as out parameters / return values are not freed properly. Bug 7486155 ODP.NET: When calling stored procedure with output parameters (ParameterDirection.Output in ODP.net) and specifying a size attribute, the data packet is padded with blank spaces. This causes huge data packets if the out parameter is for example a VARCHAR2 of size 32767. This takes up tremendous bandwidth on the network bind variable on the way to Oracle to it's specified size. Bug 7447345 ODP.NET: Unhandled Exception: System.InvalidOperationException: Dynamic SQL generation failed. No key information found. Bug 6113018 OLEDB: Support for PL/SQL comment '--' added to the OLEDB parser. Bug 7597059 OPTIMIZER: If there is a bitmap index on a fact table and the index hint is used on this fact table while it is joined with other dimensional tables, the session may crash with ORA-3113 / ORA-7445 [kkojnp]. Bug 4902697 PLSQL: Calling LOB built-in functions (from package Standard) can leak memory or leak temporary LOBs and certain LOB built-in functions may not compute the correct results if the function result was assigned to a variable which was the same as one of their input parameters. Bug 6452035 RAC: SLTS core dump if an un-initialized mutex is destroyed. Bug 6936368 RDBMS: ORA-7445 [findSE] when a very large row is inserted into a compressed block, more likely during bulk loads. Bug 7484102 RDBMS: Insert into an IOT with a secondary index causes ORA-7445 / core dump in kdtDelRow. Bug 7648406 RDBMS: High version counts may be observed for pseudo cursors, when nls_length_semantics is set to CHAR. Bug 7558379 REPLICATION: ORA-22927 during conflict resolution with user-defined procedure on a lob column. Bug 6047490 SQLEXEC: Queries containing a CONNECT_BY_ROOT can fail with ORA-932 or ORA-600 [qctcte1][0]. Bug 7372337 SQLEXEC: Create Table As Select with "WITH" clause may crash or ORA-600 [kglunp-bad-pin]. Bug 6640411 STREAMS: AQ propagation may fail after changing queue_to_queue=>true. 10.2.0.4.0 Patch 14 (10.2.0.4.14P) 32-Bit Patch 7677780 64-Bit (x64) Patch 7677781 BaseBug Abstract Bug 7207932 ASM: ORA-600 [kgeade_is_0] when renaming a file from ASM to a filesystem. Bug 7385253 BUFFERCACHE: DBWR may use a lot of CPU and seem to spin in or around kcbo_write_q due to large number of free buffers on the object reuse queue or checkpoint queue. Bug 6870047 BUFFERCACHE: ORA-8175 may be reported with the fix for Bug 5028099 present. Without the fix the session would typically have gotten ORA-600 [kcbzwb_4]. Bug 6454634 CDC: Unexpected or unrecognizable data can occur in the change table. Bug 7241059 CSSCAN: CSSCAN gives different scan results in lossy CLOBs when run several times. Bug 7196532 DATAGUARD: Upon instantiation or reinstatement, the dbid, resetlogs scn, branch id and start scn for the session do not correspond with the log miner dictionary dumped on the last failed over primary. Bug 7272297 DICTIONARY: Memory corruption and various ORA-600 [17xxx] heap corruption errors can occur if CURSOR_SHARING = SIMILAR/FORCE and statements have a large number of binds. Bug 7254367 DICTIONARY: SMON process may fail due to an ORA-600 [kglhdunp2_2] leading to an instance crash. Bug 7592319 EXPORT: Constraints for XML schema tables not imported properly. Bug 5638228 JAVAVM: ORA-600 [17099] / Instance Crash when using JDBC XA in high load scenarios. Fix rebuilt in patch 14. Bug 7501180 JAVAVM: Processing invalid zip files can result in "ORA-29516: Aurora assertion failure: Assertion failure at eoxdebug.c:93" jonzf_get_zip_message is not yet implemented. Bug 7361423 MVIEW: Drop materialized view fails with ORA-1422, when there is any materialized view in any schema with a base table name the same as that materialized view and this base table is in a remote schema. Bug 7573151 MVIEW: Wrong results can be returned from a table that has undergone online redefinition. Bug 7415038 NLSRTL: When ignorable characters (for example, punctuation characters in AI or CI setting) appear in a source or pattern strings, the LIKE behaviour is unpredictable, leading to wrong results. Bug 7509964 ODBC: NULL password error (ORA-1005) when MTS is enabled. Bug 7458976 ODBC: Access violation dereferencing a NULL pointer and trying to compare the de-referenced value with SQL_NTS. Bug 7295298 OPTIMIZER: Sub-queries may get a suboptimal filter order which in some cases can show as poor execution times for certain SQL (for example queries against ALL_OBJECTS can be slow). Bug 7375077 OPTIMIZER: When a SQL statement uses a TABLE operator on a PL/SQL collection the query optimizer did not know the size of the collection. So it assumed a default number of rows when generating execution plans. This can lead to plans that performs badly. Bug 6083292 OPTIMIZER: Query with having clause or connect by, that undergoes join predicate pushdown (View Pushed predicate or Union All Pushed Predicate appears in plan) gives wrong results. The plan will show a fictitious correlation variable in the predicate dump. Bug 5586604 OPTIMIZER: Dynamic sampling is not used for a query when current_schema is set. Bug 6939835 OPTIMIZER: A predicate involving an operator with no column argument and a constant placed in an OR-chain can cause a ORA-7445 [kkexusl] / [kkeuslf]. Bug 7579079 OPTIMIZER: ORA-600 [qctopn1] during Join Predicate Push Down. Bug 7439689 OPTIMIZER: Worker process of IMPDP utility consumes CPU, spinning. Bug 7515898 OSS: Wallet Manager will not open a trusted certificated. Bug 7395972 PARTITIONING: Collecting statistics on an index of a partitioned table while that index is being rebuilt online can result in the statistics collection process failing with ORA-7445 [kkpamPartNumFGet]. Bug 5701723 PLSQL: DBMS_ASSERT.SCHEMA_NAME can fail with ORA-44001 even for valid schema names. This can affect products which use DBMS_ASSERT, such as EXPDP. Bug 6629890 RAC: Some resources do not start automatically after creating OracleCRSToken (crsd.log shows GetUserToken failed). Bug 7606362 RAC: Sessions waiting on 'cursor pin S wait on X' wait events (the resource is in KJR_OPENSENT state and all converting locks are blocked without any apparent holder at the master instance). Bug 7314091 RDBMS: When linguistic feature is enabled, the database may fail to open with ORA-7445 [kokmcmp]. Bug 7263061 RDBMS: DBCA returns ORA-12560 / oradim reports an error (DIM-19 / O/S-Error 1388) during service creation on Windows 2008 server configured as a Primary Domain Controller.. Bug 6994490 RDBMS: NLS / Multi byte characters in the client side information fields (username, host/machine and program name) may not be correctly populated in v$session. Bug 7318276 RDBMS: An unexpected ORA-918 error may be reported if the fix for Bug 5368296 is installed. This may mask some other (expected) error. Bug 6013981 RDBMS: Ending a cursor before the end of a fetch happens can leak memory in the form of a duration leak. If this occurs often then an ORA-21780 is reported. Bug 7008262 RDBMS: If a trigger assigns an EMPTY_CLOB or EMPTY_BLOB to a :NEW.column then the inserted data may actually contain NULL instead of the EMPTY_CLOB / BLOB value. Bug 7453155 RDBMS: Memory consumption per connection in 10.2 is higher than 10.1. Bug 6661393 SECURITY: Whenever CLIENT_INFO is set using DBMS_APPLICATION_INFO.SET_CLIENT_INFO, the client identifier in session context (equivalent of DBMS_SESSION.SET_IDENTIFIER) should also be set to the SAME value if required. Bug 6759910 SPACE: DBA_TABLESPACE_USAGE_METRICS USED_PERCENT may be wrong. Bug 7444320 SPATIAL: ORA-6502 on SDO_CS.MAP_EPSG_SRID_TO_ORACLE when NLS_TERRITORY=GERMANY. Bug 6145687 SQLEXEC: Wrong (invalid) ORA_ROWSCN values may be seen in queries. Bug 6282093 SQLEXEC: Some CONNECT BY queries do not undergo OR expansion when processing the START WITH predicates. Bug 6811031 SQLEXEC: ORA-600 [qernsRowP] can occur when using linguistic comparison (nls_comp='LINGUISTIC'). Bug 7007924 SQLEXEC: Some bitmap queries that access indexes with common keys may produce wrong results. Bug 5718815 SQLEXEC: Wrong results are possible when NLS_SORT is set to any value other than 'BINARY', NLS_COMP to be 'LINGUISTIC', and the query has a nested query or inline view. Bug 5229627 SQLLDR: A direct path load of a table with unused columns may fail with ORA-600 [klaevcbk_1]. Bug 6350579 SQLPLUS: Performance improvement when spooling with Trimspool and Linesize set. Bug 6896554 XDB: ORA-31043 can occur when instantiating a schema-based XMLType (schemavalidate) if the root element belongs to an imported namespace Bug 6144426 XDB: A memory leak can occur during implicit conversion of an XMLType to char. Bug 6652767 XDKC: Applications processing multi byte data (CDATA section), may see square brackets instead of the original data. 10.2.0.4.0 Patch 13 (10.2.0.4.13P) 32-Bit Patch 7584866 64-Bit (x64) Patch 7584867 BaseBug Abstract Bug 6770417 CDC: ORA-39127 / ORA-16000 error occurs during remote database export (of standby / read only database). Bug 6904068 DICTIONARY: Very high CPU consumption may be seen when there are a large number of "cursor: pin S" wait events. Bug 7145872 NET: NETCA crashes when using Microsoft Active Directory as a directory server on Windows 2008. Bug 5951091 OID: Multiple EUS connections fail with ORA-7445 [ACCESS_VIOLATION] [unable_to_trans_pc] in sgsluuiInit / Crash the database. Bug 6833602 OPTIMIZER: Wrong results are possible from queries using OR predicates if a bitmap access path is chosen. Bug 6782437 OPTIMIZER: Poor performance may be seen for a query with a multi-level view which is a child view with a CONNECT BY clause due to lack of predicate pushing. Bug 6430500 OPTIMIZER: The optimizer may choose an index range scan over a fully qualified unique index access as it may cost the range scan as cheaper. This fix allows the optimizer to be instructed to always prefer the latter path (unique access), even if it is more expensive. Bug 7211965 OPTIMIZER: Bad selectivity may be used for BETWEEN predicates with bind variables. Bug 7498506 OPTIMIZER: Query trying join predicate push-down transformation fails with ORA-600: [kkocxj : pjpCtx] Bug 5648287 OPTIMIZER: Possible under estimate of join back cardinality in star transformation. Bug 7439957 OPTIMIZER: Divide by zero error (ORA-600 [15160]) was possible with fix for Bug 7211965 applied. Bug 7430474 OPTIMIZER: FIRST_ROWS_K re-cost for ORDER BY elimination may not find best plan. Bug 7429070 OPTIMIZER: High resource use (CPU / Memory consumption) is possible during parse of queries with nested inlists. Bug 7325597 OPTIMIZER: Suboptimal plan may be chosen if index-only access is available and the fix for Bug 6120483 is present in 10.2 releases. Bug 7257160 OPTIMIZER: ORA-600 [15160] can occur with star transformation. Bug 7189447 OPTIMIZER: Wrong results are possible when the connecting condition of a subquery refers to an aggregating column of a group-by view. The problem is that the column is not recognized as a correlating column and consequently the view is merged when it should not be. Bug 7236148 OPTIMIZER: Under first_rows_k mode the chained row count is not prorated which can lead to a suboptimal execution plan if the table has a lot of chained rows. Bug 7477691 PLSQL: Wrong Java method being executed. Bug 7144872 RAC: Remote copy during RAC install fails on Windows for directories that has space character in their names. Bug 7448543 RAC: Memory leak in crsd when resources are owned by users other than system. Bug 6775231 RDBMS: ORA-7445 [kglivl0] / core dump in a RAC system with the trace showing that the KGL handle being invalidated is read only. Bug 6452766 RDBMS: 10046 trace does not always show the correct "obj#" value in the trace. Bug 6395755 RDBMS: ORA-600 [qcopcovm2] can occur from a SELECT query with 2 or more asterix in the select list elements. This can occur when the sub-query is wrapped under a [NOT] EXISTS operator and it has 2 (or more) select items with an asterix. Bug 7462072 RDBMS: There are certain scenarios where a session can wait for event 'cursor: pin S wait on X' even though the mutex was never acquired in exclusive mode. This causes an unnecessary 10ms wait for event 'cursor: pin S wait on 'X'. Bug 7395472 RDBMS: With the version 9 (or higher) time zone data an ORA-1804 "failure to initialize timezone information" can occur. Bug 7330258 RDBMS: Calls to DBMS_TRANSACTION.local_transaction_id may result in an ORA-600 [15470]. Bug 6519198 RDBMS: ksesetmav implemented on Windows (signal handler arranges to resume from access violation with a call to a procedure which signals error 602). Bug 5709135 SQLEXEC: High PGA memory consumption is possible during execution of queries using the inlist iterator, if the iterator is restarted multiple times in the execution plan. Bug 7190477 TEXT: Access Violation in CTXHX. Bug 6216149 XDB: ORA-7445 [INTEL_FAST_MEMCPY] when updateXML is called with NULL as replace a value of XMLType. Fixes included for Critical Patch Update - January 2009 10.2.0.4.0 Patch 12 (10.2.0.4.12P) 32-Bit Patch 7522473 64-Bit (x64) Patch 7522474 BaseBug Abstract Bug 7372915 DBCONTROL: Database workload capture job submitted from Database Control fails due to the inability to locate a file in the $ORACLE_HOME/sysman/admin/scripts/db/workload directory. Bug 7121074 ISQLPLUS: iSQL*Plus service fails to start in Windows x64 platform. Bug 6967923 JAVAVM: ORA-7445 [access_violation] [unable_to_trans_pc] using shared server. Bug 6766956 ODBC: Generic fixes forward merged to 10.2.0.4 on Windows. Bug 6766884 ODBC: Generic fixes backported from 11.1.0.6 to 10.2.0.4 on Windows. Bug 6742924 OLAP: ORA-7445 [lnxnucoptg]. Bug 5879865 OPTIMIZER: A query with an Exists SubQuery involving non mergeable view may fail with ORA-7445 [evaopn2]. Bug 6627593 PROCOBOL: Hang while pre-compiling source code, if the source code file ends with erroneous DDL in an EXEC-SQL statement. Bug 7151667 RAC: Oracle listener will not start when run from shared Oracle Home on OCFS. Bug 6791019 RAC: Periodically, a message about recycle bin directory on an OCFS drive will appear: "recyclebin is corrupt, do you want to empty it?" OCFS directories will not be accessible via explorer on Windows 2008 Server or Vista systems. Attempts to access them fail with "not accessible" message. Bug 7523839 RAC: CRSTMPL.EXE fails to open file causing CRS_PROFILE command to fail on Windows 2008. Bug 7521336 RAC: OCFSINSTALL does not recognize Windows 2008 OCFS driver. Bug 7129643 RAC: RunCluvfy support for Windows 2008 included. Bug 6924458 RAC: RunCluvfy support for Windows 2008 included. Bug 6054929 RAC: racgimon process does not terminate (spins in clsrceunsubevt) even though the corresponding instance is stopped. Bug 7196894 RAC: ORA-600 [525] [KJCT flow control latch] [gcs partitioned table hash] in LMD process. Bug 7154052 RDBMS: .NET Stored procedure dll's using Extproc do not work on Windows 2008. Bug 7165026 RDBMS: Upgrade from 10102 to 10104 to 10204 will fail (ORA-4045 / ORA-4031) on 64bit windows. Bug 6685261 RDBMS: ORA-7445 [lnxmin] when using ancillary operators with inline views. Bug 6923450 RDBMS: ORA-7445 [kotgtsch]. Bug 4695511 RDBMS: ORA-600 [kxfqupp_bad_cvl] can occur when creating bitmap index on a large table in parallel. Bug 7430745 RDBMS: DBMS_STATS may fail with ORA-1422 when trying to gather statistics for X$KTFBUE. Bug 7413928 SPATIAL: SDO_AGGR_UNION holes are created with inner polygons. Bug 6359490 TEXT: ORA-29902 from complex Text query. Bug 6415531 TEXT: Long Text queries may fail to parse returning only ORA-20000 without DRG errors. 10.2.0.4.0 Patch 11 (10.2.0.4.11P) 32-Bit Patch 7494876 64-Bit (x64) Patch 7494877 BaseBug Abstract Bug 5573896 CORE: DCD does not work when the time set is greater than one minute. Bug 5945647 DV: Datapump export and import operations fail when Data Valut is enabled if the objects being exported are realm-protected or if the user performing the datapump job has a realm protecting the schema. Bug 7118478 NET: TCPS connection process may spins between read() and poll(). Bug 7388606 ODBC: Application hang or Access Violation when making additional connection requests (SQLDriverConnect). Bug 6368000 OLEDB: Executing multi-byte SQL having characters KATAKANA-HIRAGANA PROLONGED SOUND MARK-0x30fc in the column name, leads to heap corruption since parsing the SQL statement in the OraOLEDB parse does not support this character parsing. Bug 7336032 OLEDB: Multiple step operation generates errors when updating date values (when dealing with times like "00:00:00 AM"). Bug 7188610 OO4O: De-queuing multiple JMS messages fails after the first message with OCI-22060. Bug 7155655 OPTIMIZER: Wrong query results possible from predicate push. Bug 6917874 OPTIMIZER: Multi-level push of a join predicate can cause wrong results. The presence of a predicate of the form :B = <LITERAL> in the execution plan is a potential sign of this defect. Bug 6845871 OPTIMIZER: A query with a ROWNUM predicate may get a suboptimal plan. Bug 7138405 OPTIMIZER: Predicate not pushed into UNION view with OR chain. Bug 7037203 RAC: OracleCRStoken service fails to start when using Domain Operating System Acccount, with the "GetUserToken, loc:user_name2bi, OS error: 0, other: username to long" message in the CRSD log Bug 6955040 RAC: Sessions connected using default database service names get disconnected after CRSD process is killed. Bug 7251909 RDBMS: Clients using database event notifications may crash with ORA-24912 with "Incoming call failed" comment. Bug 6768289 RMAN: Some "BACKUP ARCHIVELOG" commands can result in no archive log being found leading to RMAN-6004 / RMAN-20242 errors when not expected. (Only an RMAN-20242 informational message is expected). Bug 7002207 SECURITY: Creating a compound index on a TDE column and a non-encrypted column where the non-encrypted column is modified by a function such as DESC or + 1, fails with ORA-28337. Bug 6670740 SPATIAL: Support for EPSG method 9621 (similarity transformation) was found to be required by the customer base. Bug 7433792 SPATIAL: SDO_RELATEAND SDO_COVEREDBY gives results different from SDO_GEOM.RELATE. Bug 5883691 SQLEXEC: ORA-7445 [kxhrunpack] from query referencing constant from remote row source. Bug 7246117 XDKC: XVM ignores namespace for the xsl:element. 10.2.0.4.0 Patch 10 (10.2.0.4.10P) 32-Bit Patch 7480785 64-Bit (x64) Patch 7480786 BaseBug Abstract Bug 7359366 AQ: Server side interrupt to the dequeue shadow may result in a ORA-7445 [kwqidafc0+155]. Bug 6774830 ASM: ORA-7445 [kfiofib_detach] possible when opening a file. Bug 6605106 ASM: ORA-600 [kfclUpdateBuffers20] can occur in ASM as a null converted buffer may be accessed. Bug 5926711 DATAVAULT: Realm audit report shows "?" as the account violating the realm. Bug 5996457 DATAVAULT: The return code in a DV audit record is set to 0 when a command rule violation occurs. Bug 7326738 DATAVAULT: DBMS_REDEFINITION.START_REDEF_TABLE fails (ORA-42008) on DV realm protected tables. Bug 6619922 DATAVAULT: A synonym cannot be dropped in a Data Vault system with the fix for Bug 6391193 installed. Bug 7315642 DATAGUARD: Reinstatement of a failed primary into a logical standby after a failover fails (ORA-16653 / ORA-1281) due to the processing of log files from an incorrect branch. Bug 6874522 DATAGUARD: The Value column of V$DATAGUARD_STATS is Null on a logical standby and the primary SCN is greater than 4294967295. Bug 7331929 DATAPUMP: Performing expdp with network_link and physical standby database generates ORA-16000. Bug 6746196 DICTIONARY: If multiple users are executing identical SQL statements, then under high concurrency some users may get false ORA-942 (or other parsing errors) even though the underlying object exists and they have privileges. At least one "legitimate" ORA-942 (or similar) error must occur in order to start the chain of events which can then lead to other sessions unexpectedly getting the same error. Bug 7362653 IMPORT: Import may drop a pre-existing table when an export file is corrupted. Bug 5638228 JAVAVM: ORA-600 [17099] / Instance Crash when using JDBC XA in high load scenarios. Bug 6451626 LOGMINER: Selecting a SQL_REDO or SQL_UNDO from V$LOGMNR_CONTENTS, or UNDO_SQL from FLASHBACK_TRANSACTION_QUERY whilst mining undo data generated whilst no supplemental logging was in force can lead to a ORA-7445 [memcpy] / core dump. Bug 6472286 MVIEW: ORA-7445 [qsmqbtss_build_table_inlineview_subordsets] can occur during a create MATERIALIZED VIEW which has a query with an inline view which accesses a remote table. Bug 5059447 OPTIMIZER: ORA-979 from subquery in select list. Bug 5490816 OPTIMIZER: A nested query that has several functions in the select of an outer query block pointing to the same function in the inner query block when "_simple_view_merging" is set to be true, the column corresponding to the first function displays the correct results, but the columns corresponding to other functions return nothing. Bug 4440589 OPTIMIZER: Wrong results are possible from queries on tables with check constraints if the query has inlist predicates or a series of ORs predicates against one of the columns in the constraint, and one of those ORs or inlist positions has a bind variable. Bug 5343559 OPTIMIZER: ORA-600 [kkqcscpcky:ficand] errors may occur during optimization of queries with sub-queries, if a table used in a subquery has functional indexes. Bug 7144891 OPTIMIZER: ORA-600 [qctopn1] occurs for select statements having a nested full outer join and under going join predicate push down. Bug 5944239 PLSQL: ORA-6554 during database creation. Bug 5386874 RDBMS: ORA-7445 can occur using an extensible aggregate function based on an object type, i.e. when executing an ODCIAggregateTerminate call. Fix re-included, earlier versions of this fix caused memory corruptions (see Note 737957.1) Bug 6674196 RDBMS: ORA-600 [kddummy_blkchk] / buffer cache corruption using ASM, OCFS or any ksfd client like ODM. Bug 4561087 RDBMS: Change Data Capture fails with ORA-1438 when tables have greater than 128 columns. Bug 7411865 RDBMS: Updates on a table involving a trigger fail with ORA-600 [13030]. Bug 6067825 RDBMS: OracleService<SID> does not start because of error 998. Bug 6932206 RDBMS: Query rewrite with a merge statement can result in an ORA-600 [kkmupsViewDestFro_4]. Bug 7309458 RDBMS: ORA-932 might be incorrectly returned when a CHAR bind is used in a statement that undergoes bind peeking. Bug 6865378 RDBMS: When auditing is enabled in the database it is possible for some commands to result in a ORA-7445 [kcmstn]. Bug 7191744 RDBMS: PL/SQL cursor may execute under the wrong schema which can lead to wrong results or logical data corruption. This problem can only happen where the client uses separate (unbundled) calls for each of the parse / bind / execute steps of executing a cursor, as can be the case with OCI7 clients. Bug 6877038 RDBMS: Object owner information is missing from the execution plans which are produced by a remote test execute, via a database link. SQL performance uses this information during performance comparison to detect changes in execution plan structures. Bug 6854919 RDBMS: ORA-600 [kesutlGetBindValue-2] when running SQL Tuning Advisor. Bug 6455412 RDBMS: ORA-600 [kturacf1] raised by internal exception handler. Bug 7038750 RDBMS: ORA-7445 [ksuklms] / Instance Crash following a kill of a system process. Bug 5348308 RDBMS: A deadlock can sometimes occur with the PE enqueue while modifying a parameter. Bug 6193945 RECOVERY: High LGWR CPU utilization and increased commit latency as measured by the 'log file sync' wait event. Bug 6606749 SECURITY: Self deadlock when using DBMS_EPG to change the password of the currently connected user. Bug 6375150 SQLEXEC: When a large amount of data needs to be sorted and it spills to disk an ORA-600 [15851] can occur. Bug 7364935 SQLLDR: Direct path load may fail with a ORA-600 [klaevc_10]. Bug 7356443 STREAMS: DML Handlers and User-defined transformations causing gradual slowdown of performance. Bug 7342082 XDB: XMLDOM different behaviour after fix for Bug 5401776 applied. Bug 6506818 XDB: Memory leak from "session heap" -> "koh dur heap d" while converting XMLType to CHAR repeatedly. 10.2.0.4.0 Patch 9 (10.2.0.4.9P) 32-Bit Patch 7386320 64-Bit (x64) Patch 7386321 BaseBug Abstract Bug 7113299 DICTIONARY: ORA-7445 [kkslmtl] may occur with the fix for Bug 6163785 applied. Bug 5712781 NET: Beq connections on windows may fail intermittently. Bug 4235212 ODBC: Driver returns wrong data for stored procedures having NCLOB as OUT Parameter. Bug 7348412 OLAP: Aggregate function aggregating formula may crash in xsAGVDict* or xsagprop. Bug 7237571 OPTIMIZER: Bad execution plan a query with 1=1 predicate. Bug 6782276 RAC: RAC instance on Windows may get failures such as : ORA-27508 ORA-27300 ORA-27301 ORA-27302 Bug 6134368 RDBMS: An UPDATE with a RETURNING clause against a table with a row level trigger may fail with ORA-1407 or cause block corruption. Fix removed, Bug:7411865 supersedes this and is included in patch 10. Bug 5131180 RDBMS: Wrong NLS settings after querying tables with DATE related constraints. Bug 7046751 RDBMS: ORA-22905 with Union All and ADT column as view column result. Bug 7190270 RDBMS: Under heavy load a CTAS cursor is getting invalidated (ORA-12842 / ORA-600 [ktsircinfo_num1]) with the fix for Bug 6274465 applied. Bug 6672737 RDBMS: ORA-7445 [slcts] may occur due to an invalid result from the call to localtime or localtime_r in these functions. Bug 7269450 SQLEXEC: ORA-20000 / DRG-100 [50600],[drexr.c],[2399] intermittently returned for queries where prefetching is active. Fixes included for Critical Patch Update - October 2008 10.2.0.4.0 Patch 8 (10.2.0.4.8P) 32-Bit Patch 7357454 64-Bit (x64) Patch 7313130 BaseBug Abstract Bug 6959964 DICTIONARY: Anonymous PL/SQL block using sequence invalidates other cursors. Bug 6262792 HS: MTA Extproc process can leak memory. Bug 7340474 NET: MTA Extproc process can leak memory. Bug 7142215 OPTIMIZER: Wrong results for query using Exists and Group By. Bug 6122097 OPTIMIZER: SQL trying to use a function based index may dump under ORA-445 [evaopn2] or give wrong results with the fix for Bug 2747052 and Bug 5015557 in place. Bug 7210296 RAC: Registering many application resources with crsd causes memory leak. Bug 7216535 RAC: On Windows platforms, service resource start / stop actions may fail to modify the service_names parameter of the instance if the instance name has upper case character. Bug 6797677 RAC: ORA-7445 [kggchk] may crash the instance during reconfiguration. Bug 6978876 RDBMS: Unable to open more than 7500 dedicated sqlplus sessions to the database on Windows 64-Bit. Bug 7013768 RDBMS: ORA-7445 [kkfdmrk] when star transformation is enabled and some of the dimension are parallel bitmap sub-queries. Bug 7123643 RDBMS: Select against a compressed table can return NULL data for columns which contain data in certain scenarios. This problem only affects compressed tables where the data has been loaded using bulk load (CTAS, import, Insert as select etc...). Bug 6133008 RDBMS: ORA-600 [4412] can occur When the tablespace containing SYS.AUD$ is full. Bug 7154415 RDBMS: Using a CAST() operator can give wrong results / corruption. This problem is introduced in 10.2.0.4 by the fix for Bug 5838153. Bug 6635214 SPACE: ASSM segments can grow rapidly for highly concurrent inserts (included by Merge Bug 7287289). Bug 6844739 SPACE: ASSM Truncate very slow even with fix for Bug:6086497 (included by Merge Bug 7287289). Bug 6527074 SPATIAL: Large memory allocation when using SDO_GEOM.RELATE. Bug 6678845 SQLEXEC: Wrong results are possible from queries involving "OR" predicates if projection pushdown occurs and the execution plan involves a Concatenation operation. Bug 6399597 SQLEXEC: Poor performance for subquery filters using Hash Group By. Bug 6875111 SQLEXEC: ORA-600 [qkacon:FJfsrwo] can occur executing a CONNECT BY query which has an ORDER BY .. DESC. Bug 6594005 TEXT: Queries that are larger than 8K bytes and are used with CTXRULE indexes may fail with ORA-600 [kgherrordmp]. 10.2.0.4.0 Patch 7 (10.2.0.4.7P) Only available in 32-Bit Patch 7313129 BaseBug Abstract Bug 6736159 DICTIONARY: If domain index on an ADT column is specified during semantic processing of a delete, memory corruption can occur (ORA-7445 [kotgtsch] / [kghfrmrg:nxt] / [15201]). Bug 6725634 DICTIONARY: DDL against an object dependent on a synonym may invalidate the synonym object. Bug 7195088 OLAP: Merge Patch A including: Bug 6607486 : In an instance that is configured for a typical Data Vault deployment it is not possible to create an analytic workspace. Bug 6822672 : API queries may fail intermittently with ORA-33858: value of the ampersand-substitution expression is NA, beneath ODCITableDescribe. Bug 6687129 : OLAP may report ORA-36875 "limitmap is missing or is not a string literal". Bug 6655657 : Parallel refresh using DBMS_CUBE.BUILD fails on Windows. Bug 6355282 : ORA-7445 [kghfrempty] can occur under load. Bug 6489332 : ORA-29532 java.lang.OutOfMemoryError in OLAP load of AW (XML commands that call dbms_lob and interactionexecute). Bug 6789923 : Attaching an analytic workspace using AWM or the AWXML API can use a great deal of Java memory in the RDBMS JVM. Bug 6454468 : Attempting full aggregation of cubes can fail with ORA-600 [CC node unlock failed to match n] / ORA-600 [XSOOPS]. Bug 7005671 : ORA-600 [XSOOPS], [XSBACLOSE01]. Bug 7140644 : Regression, xsTokISIDN() may reads past the end of the string. Bug 7039080 : Out-of-memory condition during DIMSHOW when event 37383, level 2 is set. Bug 6695247 : DBMS_ODM.CREATEDIMOWB / DBMS_ODM.CREATEFACTOWB do not have any line breaks. Bug 7014646 OPTIMIZER: Complex query can fail during parse with ORA-600 [kkocxj : pjpCtx] Bug 6972343 OPTIMIZER: Wrong results are possible with join predicate pushdown and transitive predicate generation. Bug 7210921 PARTITIONING: Selectivity may be evaluated on the wrong sub partition. Bug 6876196 QRYREWRITE: ORA-600 [kkqvmrvl] may occur When a query is rewriting with multiple equivalences in the presence of inline views. Bug 6504899 RAC: Archived files under ~/evm/log are not removed after 40 days. Bug 6134368 RDBMS: An UPDATE with a RETURNING clause against a table with a row level trigger may fail with ORA-1407 or cause block corruption. Bug 7127618 RDBMS: Lengthy text query interrupted by alter session kill may spin on CPU. Bug 6805009 RDBMS: ORA-7445 [kzagetcid] with AUDIT_TRAIL = DB_EXTENDED. Bug 5095023 RDBMS: Possible ORA-7445 [kzaxfga] / Core dump when XML format audit trail is used. Bug 6870937 RDBMS: Small memory leak / ORA-600 [729] using SHARED_CONTEXT_SENSITIVE RLS policy. Bug 6809093 RDBMS: Hang due to TT enqueue waits on an UNDO tablespace. Bug 6897966 SCHEDULER: Service names are case insensitive but scheduler treats them as case sensitive, jobs are not picked up unless the same case is used. Bug 7017637 SCHEDULER: Very occasionally there can be latch contention in RAC in scheduler code resulting in an ORA-600 [504]. Bug 6936964 SPATIAL: SDO_GEOM.VALIDATE_GEOMETRY_WITH_CONTEXT returns wrong results. Bug 7244238 SQLEXEC: When using XA and database links, segmentation faults (ORA-7445's) in routines such as kpuhhalo, kpudfn, or kpucHTtoIL can occur. Bug 6689334 TEXT: Text indexing using a URL datastore may fail with ORA-7445 [lxscop] if a top level URL returns a redirected URL value. Bug 6445329 XDB: DBMS_XMLGEN.GETXML() may return wrong results when the table / view data has null values. 10.2.0.4.0 Patch 6 (10.2.0.4.6P) Only available in 32-Bit Patch 7253058 BaseBug Abstract Bug 6600051 AQ: Time manager hang / core dump. Bug 5690152 DATAPUMP: Package comments not imported when using datapump schema import. Bug 6374297 DICTIONARY: Drop column on a virtual column returns ORA-39726 with fix for Bug 6268371. Bug 6119017 DICTIONARY: ORA-600 [kgscReleaseCursor_1] during parallel DML / DDL. Bug 7004914 DV: DBMS_SNAPSHOT.REFRESH fails with insufficient privileges for a realm-protected schema regardless of whether the user performing the refresh operation is authorized to the realm or is the object owner. Bug 6862248 ODP.NET: Re-architecture of commandtimeout implementation for better performance. Bug 6440977 OPTIMIZER: Queries with predicates that would otherwise be generated transitively can get a different execution plan to the same query without those extra predicates. Bug 6221403 OPTIMIZER: Incorrect selectivity with extended statistics and out-of-range values. Bug 7188932 OPTIMIZER: Query with top-level AND predicates and an OR-chain may go into a loop during optimization (stuck in function kkompr). Bug 6972291 OPTIMIZER: The 10.2.0.4 optimizer can use the selectivity of column groups but this option is disabled if there is a histogram defined on any of the columns of the column group. Bug 6082292 ORAMTS: RM is committed even when ServiceDomain.Leave() returns TransactionStatus.Aborted. Bug 5208177 RDBMS: NLSSORT may return NULL instead of an error for a large non-null input value. Bug 6653934 RDBMS: Online Segment Shrink on a table with ROWDEPENDENCIES set will either cause the shrink to fail with an ORA-7445 [kdrwric] or block corruption. Bug 6679303 SQLEXEC: ORA-932 returned from a SELECT statement if the SELECT statement selects a LONG RAW column that was amended to a BLOB previously. Bug 6724838 TEXT: Indexing a MS Word document that contains Greek headers/footers returns incorrect results. Bug 6344497 XDB: Case statement generates wrong filter. 10.2.0.4.0 Patch 5 (10.2.0.4.5P) 32-Bit Patch 7218676 64-Bit (x64) Patch 7218677 BaseBug Abstract Bug 6771400 ASM: ORA-600 [kfgFinalize_2] can occur in ASM when mounting a disk group. Bug 6511850 NLSRTL: ORA-923 from DBMS_STATS.gather_table_stats and related stats gathering calls. Bug 6956212 OPTIMIZER: Bad cardinality for Non-Equi joins with concatenation if dynamic sampling is used. Bug 6130317 OPTIMIZER: ORA-7445 [nsoexc] when optimizing a SQL statement. Bug 6934892 OPTIMIZER: Using Histograms for a Varchar columns can give an incorrect cardinality estimation, when column values are more than 6 character long. Bug 5251842 OPTIMIZER: Queries against V$DATAFILE / GV$DATAFILE may get a suboptimal execution plan due to a RULE hint within the view definition. Fix re-included after base label was recreated. Bug 6714608 PARTITIONING: Wrong results are possible from queries involving star transformations in which the transformation is driven by temporary tables in parallel query slaves when subquery pruning occurs. Bug 5688060 PLSQL: Compilation of very large packages can run out of process memory (ORA-4030). Bug 6913090 RDBMS: Queries using multiple user-defined aggregates window functions (or regular user defined aggregates) may produce wrong results. Bug 7027551 RDBMS: ORA-600 [kclnini_1] can occur at startup with very large SGA sizes in a RAC environment. Bug 6935367 RDBMS: ORA-600 [kksCallPopCallback] even though no prior ORA-4030 was raised. Bug 5868257 RDBMS: ORA-7445's, Core dumps or memory corruption from Update DML. Bug 5386874 RDBMS: ORA-7445 can occur using an extensible aggregate function based on an object type, i.e. when executing an ODCIAggregateTerminate call. Bug 6432837 RDBMS: Internally handled ORA-19809 and ORA-19804 errors may appear in the alert log and RVWR tracefile. Bug 5883585 RDBMS: Excess memory use / ORA-4030 can occur executing a long running XMLAGG query. Bug 4033868 RDBMS: When using the COLLECT function, Oracle creates a TYPE dynamically "on the fly" in the SYS schema. When the SQL completes, the TYPE is left behind. Bug 6336234 RDBMS: Stack overflow can kill the oracle instance and service when deep recursion occurs. Bug 6667800 RDBMS: Client, server hang or ORA-600[12333] can occur when using a multi-threaded OCI client which uses OCILob() functions. Bug 6944036 RDBMS: OCI applications may get wrong error codes after failover for non-fatal errors. Bug 6327692 RDBMS: Wrong results may be returned due to incorrect data passed to DFO (Data Flow Operation) in a parallel query. Bug 6795880 RDBMS: A session may go into an infinite spin just after a wait for 'kksfbc child completion'. The spin occurs with a stack including kksSearchChildList -> kkshgnc where kksSearchChildList loops forever. ORA-600 [kksSearchChildList1], ORA-600 [kksSearchChildList2], ORA-600 [kksSearchChildList3], ORA-600 [kkshgnc-nextchild] my also be observed. Bug 6163785 RDBMS: Intermittent Wrong Results with Database Link and cursor_sharing. Bug 6925163 SECURITY: No audit record is made if an "ALTER SYSTEM" command fails with an ORA-1031 error and "AUDIT ALTER SYSTEM" has been enabled. Bug 7022905 SPACE: Alter tablespace drop datafile finishes with "tablespace altered" even if the datafile contains extents from different tables. This leads to a corrupted database as the datafile is also dropped at OS level. Bug 7003151 SPATIAL: sdo_anyinteract much slower in 10.2.0.4 and 11.1.0.6 than 10.2.0.3 Bug 6952800 SPATIAL: sdo_filter memory leak against particularly partitioned tables but can be a problem on ALL spatial Tables. Bug 5190885 SQLEXEC: ORA-600 [smbput_3] from queries with large non-distinct aggregates and a group by rollup which uses the temporary tablespace (i.e. the sort does not fit in memory). Bug 7036589 SQLEXEC: High CR gets count may be seen for a query against a partitioned table which uses PARTITION HASH SINGLE node in its plan. Bug 6471770 SQLEXEC: Group-By queries can fail with ORA-32695 when operating on a large volume of data if hash group by aggregation is used. Bug 6076414 SQLEXEC: Remote query containing the TO_DATE() operator may be executed on the local host even if there is a DRIVING_SITE hint. ORA-7445 [kkssct] is also possible. Bug 6798910 SQLEXEC: Index usage in v$object_usage may become 'YES' after EXPLAIN PLAN or DBMS_STATS, monitoring is turned on. Bug 6898054 XDB: xmldom.setDocType may reverse the positions of pubID and sysID Bug 6656630 XDB: XmlAgg with GROUP BY can leak memory. Fixes included for Critical Patch Update - July 2008 10.2.0.4.0 Patch 4 (10.2.0.4.4P) Only available in 32-Bit Patch 7154241 BaseBug Abstract Bug 6660648 AQ: Increased PGA usage may be seen over time with a long running application executing 'dequeue by conition'. The session will show a large number of cached cursors with similar text due to statement caching under AQ. Bug 6163771 ASM: During instance recovery, mounting a diskgroup can fail with ORA-600 [kfcema02]. There is a mismatch between the FCN recorded in the block and the FCN recorded in the ACD. block FCN < ACD fcn. Bug 5213488 AWR: "rows per sort" in AWR report overflows and only shows ########. Bug 6530171 DV: When event 47998 is enabled realm creation may fail with a ORA-7445 [strlen] / Core dump when executing DBMS_RLS Bug 6207468 OPTIMIZER: ORA-7445 [kkofkrProrateStat] optimizing SQL in FIRST_ROWS mode. Bug 6607505 RDBMS: ORA-600 [15201] / ORA-600 [mal0-size-too-large] errors can occur during DML operations on objects having functional indexes containing LOB columns. Bug 6455659 RDBMS: Stored outlines are not used when expected in a multi byte character set database. Bug 5944121 RDBMS: When using collections with elements that have non-final types, an ORA-600 [kghufree_06] can occur. Bug 5843814 RDBMS: XA_RECOVER is very slow or query on GV$GLOBAL_TRANSACTION is very slow. Bug 6954829 RECOVERY: ORA-600 [kcramr_8] can occur during media recovery. Bug 5970301 SPACE: Corruption / ORA-600 [ktspfsall] can occur during Insert into an ASSM segment if the ASSM segment has a large Initial extent. This problem is most likely to occur against a LOB segment but can affect other segments. 10.2.0.4.0 Patch 3 (10.2.0.4.3P) Only available in 32-Bit Patch 7117709 BaseBug Abstract Bug 6193802 ANO: Connect error using PKCS11 wallet. Bug 5900004 ADVREP: When updating a table containing an ADT column and a check constraint, an after row trigger :old bind value for the ADT column incorrectly gets set to the :new bind value, causing ORA-1403. Bug 6826661 CORE: Wrong data in NUMBER column for specific FLOAT values (SQLT_FLT). Bug 7019835 CORE: Enterprise User Security proxy with - connect [targetuser]/@<tnsname> does not work. Bug 7011807 ODBC: Calling SQLSetParm() with a string which is non NULL terminated results in application crash. Bug 6883418 ODBC: SQLExecDirect may cause an application crash when the SQL string is very large. Bug 6833159 ODP.NET: Unable to get XML from XMLType (exception is thrown from GetXmlDocument() at xmlDocument.LoadXml(val) with parsing error). Bug 6896701 ODP.NET: OracleGlobalization class truncates Sort and Comparison values. Bug 5251842 OPTIMIZER: Queries against V$DATAFILE / GV$DATAFILE may get a suboptimal execution plan due to a RULE hint within the view definition. Bug 6241222 RAC: OraFenceDrv.sys prints unnecessary debug statements. Bug 4393920 RDBMS: Enterprise User Security proxy with - connect [targetuser]/@<tnsname> does not work. Bug 6759032 RDBMS: Query with GROUP BY, set operations and NULL columns may incorrectly return "ORA-979: not a GROUP BY expression". Bug 6645719 RDBMS: ORA-7445 [kgccgmtf] / core dump from RMAN with compress option. Bug 6956461 SPATIAL: Support for Irish grid (ig) polynomial TFM. 10.2.0.4.0 Patch 2 (10.2.0.4.2P) Only available in 32-Bit Patch 7006942 BaseBug Abstract Bug 6200820 AQ: After RAC reconfiguration intermittently the QMNC processes cannot communicate with each other in order to allow repartitioning to occur. This results in node affinity not changing and propagation schedules remaining on a non-primary node and messages not being propagated. Bug 5880921 AWR: Time inconsistency between V$SYSMETRIC_HISTORY and SYSDATE. Bug 6994160 LOGMINER: Logminer reader process writes repeated "LET: next scn before krvxrolf" to tracefile. Bug 6595426 NET: ORA-12539 occurs when client receives large NSPTRD packets from remote_listener. Bug 6688740 NLSRTL: ORA-7445 [lxoVldStr] / ORA-7445 [lxoMonoCmp] when using NLS_SORT=xczech. Bug 5961436 ODBC: Driver may report an error on executing a procedure after execution of insert statement. e.g. "CALL XX_TEST_1(? ,? )" [Oracle][ODBC][Ora]ORA-00936: missing expression (936)". Bug 6986658 ODP.NET: Attempts to use statement caching for Ref Cursors. Bug 6372848 OLAP: ORA-600 [XSOOPS], [XSBATCHNEXT00], during EIF Import. Bug 6414616 OLAP: DBMS_AW.ADVISE_SPARSITY yields ORA-1405 (Fetched column value is null). Bug 6822995 OLAP: Slow OLAP performance when using BIEE - Oracle Answers. Bug 6195891 OLAP: Error during AW UPDATE MULTI, when PGA_AGGREGATE_TARGET is not high enough. Bug 5902962 OPTIMIZER: Access by rowid is not always possible for DML statements with rowid predicates against tables with versioning enabled. This can occur if the statement uses a view with a rowid predicate and the predicate is not pushed inside the view. Bug 5234947 OPTIMIZER: ORA-904 can occur during dbms_stats.gather_table_stats and similar statistics gathering calls. Bug 6369463 OPTIMIZER: Wrong results are possible from a query containing the ORA_ROWSCN pseudo column - the execution plan has a missing table. Bug 6917874 OPTIMIZER: Multi-level push of a join predicate can cause wrong results. The presence of a predicate of the form :B = <LITERAL> in the execution plan is a potential sign of this problem. Bug 6626018 OPTIMIZER: The cost of evaluating a subquery as a filter may be computed too low, resulting in a suboptimal execution plan. Bug 5410059 ORAMTS: Aborted distributed transaction causes ORA-24761 and "Unable to enlist" errors. Bug 6506617 PARTITIONING: Wrong results may be produced from star transformation when extended pruning occurs (multi-column pruning) and the join method used is a hash join. Bug 6823287 PLSQL: Subsequent iterations of the same cursor (where in the first iteration it went fine) may throw ORA-1001. Bug 6705635 RDBMS: Under certain conditions the "CREATE TABLE" DDL generated by impdp may be formatted in a way such that a line is wrapped in the middle of a default value clause of a column. As a result, the default value gets changed compared to the original table. Bug 5923486 RDBMS: When a streams operation is performed the streams pool size and buffer cache size may be incorrectly written to the spfile. Bug 6151380 RDBMS: ORA-600 [qerpx_res_qcrange] can occur while running a parallel query with an Order By in the query if there are operations above the Order By in the plan. Bug 6110752 RDBMS: Parallel bitmap merge operations can fail with ORA-600 [qerbuNStrp:eridgt]. Bug 6725855 RDBMS: ORA-7445 can occur with OCI7 remote fetch of OCI8 piecewise fetch across a database link. Bug 6121357 RDBMS: ORA-600 [17051] can occur during query rewrite when the summary which was expected to be used is in an INVALID status. Bug 6972843 RDBMS: Hourly trace files containing '[kdl_trim]: newlen:'. Bug 5368296 RDBMS: ORA-918 is not reported for an ambiguous column in a query involving an ANSI join of more than two tables / objects. Bug 6768114 RDBMS: The decimal precision for numeric types INTEGER, INT, SMALLINT may show incorrect scale / precision during describe operations. Bug 6143047 RDBMS: DBTIMEZONE may automatically get reset to 00:00. Bug 5890312 SPACE: Space leak in ktspfsall can cause create CATCTX index to hang. Bug 5386204 SPACE: Block corruption / ORA-600 [kddummy_blkchk][18038] can occur on a segment which has been direct loaded. The corruption shows as a PAGETABLE SEGMENT HEADER having blocks in the "Auxillary Map" outside of the "Extent Map" range. Bug 6760697 SPACE: DBMS_SPACE_ADMIN.ASSM_SEGMENT_VERIFY does not detect certain segment header block corruption. Bug 5704108 SPACE: Insert as select into a partitioned table can hang / spin when using the DBA search cache with a stack including ktspfsrch. Bug 5934363 SPACE: Create CTXCAT index may hang in RAC environments. Bug 6604020 SPATIAL: SDO_CS.FROM_USNG spins (appearing to hang) with invalid data. Bug 5895190 SQLEXEC: Wrong results are possible from a hash join outer with a hash semi join as an input. Bug 6456530 SQLLDR: ORACLE_DATAPUMP access driver for an external table leaks pga memory marked as "kpudplalloc". Bug 6670579 XDB: A PGA memory leak can occur when using XMLSequence. The leak occurs in the heap "koh dur heap d" with memory tagged as "kolaGetRfcHeap". Bug 6506816 XDB: A ORA-4030 memory leak can occur in the session heap when CHAR to XMLTYPE conversions are performed in a SQL statement. Bug 6345197 XDB: ORA-7445 [qmxsaxNSStartElement] parsing XML documents with "space" attributes. 10.2.0.4.0 Patch 1 (10.2.0.4.1P) Only available in 32-Bit Patch 6981215 BaseBug Abstract Bug 6082832 DATAPUMP: Data pump client does not correctly mask out password for ENCRYPTION_PASSWORD parameter. Bug 6084232 DATAPUMP: In some cases the unloading of encrypted column data can result in corrupt data written to a Data Pump dump file. An "ORA-28344: fails to decrypt data" error will be encountered when trying to perform a load operation with this dump file. Bug 5756769 MVIEW: Deadlock (row cache) between create materialized view and DML on tables of mview. Bug 4551675 ODBC: Client memory leak executing PL/SQL that returns a REF cursor. Bug 5714944 OPTIMIZER: INDEX SKIP SCAN may be selected instead of an INDEX UNIQUE SCAN when statistics indicate that the table / index is empty. Bug 6815733 OPTIMIZER: ORA-600 [qctcte1] errors during optimization of a query that has views or sub queries as well as scalar sub queries in the ORDER BY clause. Bug 6376928 OPTIMIZER: ORA-3113 can occur for a GROUP BY query which has predicates on a functional index column duplicately defined with the same functional index column also being present in the ORDER BY list. Bug 6329318 OPTIMIZER: Selectivity of between predicate with binds is lower than the equality predicate. Bug 6120483 OPTIMIZER: Query with an in-list doesn't choose cheaper index. Bug 6783426 PLSQL: ORA-3113 / ORA-7445 [pevm_BNDUC] when a bind is a host bind and the bind datatype is a refcursor, which is essentially the same cursor to which the bind is bound to. Bug 6324944 RECOVERY: ORA-600 [ksfdref3] can occur. Bug 6024730 RECOVERY: Intermittent 'UNKNOWN ERROR' can show in the STATUS column of the V$BACKUP view. Bug 6607676 RDBMS: OCI application may leak critical sections and or fail with an Access Violation in OraClient10!kpufhndl0. Bug 5747462 RDBMS: Degradation in performance of 'analyze table validate structure cascade' in 10.2 on tables with indices. Bug 6670551 RDBMS: Index statistics are not populated on Create Index when the base table is empty and unanalyzed. Bug 6051177 RDBMS: If 'alter index modify partition coalesce' and 'dbms_stats.gather_table_stats' are run on the same object at the same time, there is a small window where the two operations could deadlock. Bug 4169479 RDBMS: DBVerify is extremely slow due to synchronous read on some filesystems. Bug 5623467 SPACE: ALTER TABLESPACE ... DROP DATAFILE ... produces bad redo which typically does not then drop the datafile either during recovery or at a standby. This can lead to subsequent errors such as ORA-600 [3689] if subsequent redo tries to add new datafile. Bug 5935935 SQLEXEC: Block sampling queries may perform poorly. Bug 6778404 XDB: SQL that converts a lot of rows in a statement, may encounter large growth in "callheap" - "qmu subheap" / ORA-4030. -------------------------------------------------------------------------------- 10.2.0.3.0 Patch 30 (10.2.0.3.30P) 32-Bit Patch 8199865 64-Bit (Itanium) Patch 8199866 64-Bit (x64) Patch 8199867 BaseBug Abstract Bug 6804815 DATAPUMP: Jobs exported and then imported by datapump are owned by the connected user after import rather than the original user, even when imported by a DBA. Bug 5515882 DATAPUMP: Data Pump Export fails with ORA-1427 if there are duplicate rows in secobj$ table. Bug 4352110 DATAPUMP: ORA-39125 from expdp / impdp of triggers with nulls in WHEN clause. Bug 6635956 DATAPUMP: DBMS_METADATA.GET_DDL can fail with ORA-6502 /LPX-7 error when retrieving metadata, causing IMPDP to fail with similar errors. Bug 7254367 DICTIONARY: SMON process may fail due to an ORA-600 [kglhdunp2_2] leading to an instance crash. Bug 7131656 DICTIONARY: Loading a KGL object fails with ORA-600 [16605]. Fix re-included because it was not built in patch 28. Bug 7450460 ODP.NET: LOBS (OracleBlob / OracleClob) which are created as temporary LOBS in a PL/SQL procedures and returned as out parameters / return values are not freed properly. Bug 6887866 RDBMS: Long bind to LOB update operation fails with ORA-1551, a subsequent retry fails with ORA-22922. Bug 7484102 RDBMS: Insert into an IOT with a secondary index causes ORA-7445 / core dump in kdtDelRow. Bug 5364143 RDBMS: Bind Peeking is not carried out upon query reload, Execution Plan changes. Bug 7646952 SECURITY: Running DBMS_SESSION.CLEAR_ALL_CONTEXT could consume large amounts of CGA memory if there were a large number of global contexts defined, resulting in ORA-4030. Bug 5957325 SQLLDR: Direct Path load can fail loading very large rows with ORA-600 [6944]. 10.2.0.3.0 Patch 29 (10.2.0.3.29P) 32-Bit Patch 7631956 64-Bit (Itanium) Patch 7631958 64-Bit (x64) Patch 7631957 BaseBug Abstract Bug 7568350 EXPORT: RLS policy is changed to dynamic from context sensitive after export/import. Bug 7388606 ODBC: Application hang / Access Violation waiting for more connection requests. Bug 6520661 RAC: OracleRemExecService memory utilization keeps increasing as cluvfy commands are being executed. Bug 6936368 RDBMS: ORA-7445 [findse] inserting a very large row into a compressed block. Bug 7395472 RDBMS: With the version 9 (or higher) time zone data an ORA-1804 "failure to initialize timezone information" can occur. Bug 7298722 SPACE: ORA-600 [2025] on insert into a large LOB. Bug 6852866 TEXT: After applying the patch to Bug 6724003 the issue in Bug 6504287 still exists. Bug 6504287 TEXT: Oracle Text search with MIXED_CASE attribute of basic lexer fails (DRG-00100). Fix re-built. Bug 5162489 XDB: ORA-932 when importing schema-based xml tables, with binary storage. 10.2.0.3.0 Patch 28 (10.2.0.3.28P) 32-Bit Patch 7558097 64-Bit (Itanium) Patch 7558087 64-Bit (x64) Patch 7558071 BaseBug Abstract Bug 6074620 DATAGUARD: LGWR unconditionally writes to trace file (tkcrrpa / tkcrrsarc). Bug 7131656 DICTIONARY: Loading a KGL object fails with ORA-600 [16605]. Bug 6768069 FLASHBACK: The oldest_flashback_scn of v$flashback_database_log is zero on a RAC physical standby preventing FLASHBACK DATABASE operations. Bug 6267310 IMPORT: Using imp to load a table with a timestamp or ROWID column can take a very long time. Bug 6074789 OLAP: Dimension with HIERLIST metadata cannot be viewed in AWM because the metadata appears to be missing (error ORA-36844). Bug 7395972 PARTITIONING: Collecting statistics on an index of a partitioned table while that index is being rebuilt online can result in the statistics collection process failing with ORA-7445 [kkpamPartNumFGet] Bug 5506702 RAC: Dequeue delay experienced after RAC reconfiguration. Bug 6760382 RDBMS: The use of triggers in conjunction with functional indexes can sometimes lead to a ORA-7445 [evaopn2]. This problem can occur when the index is built on an abstract data type column and that same column is passed into a trigger. Bug 6113861 RDBMS: Heapdumps can fail on Windows Itanium with "Inaccessible memory range". Bug 7238163 RDBMS: Bind peeking is disabled if _optim_peek_user_bind flag is set to FALSE and enabled when you set it TRUE (default it's true). Bug 5058758 RECOVERY: Test recovery fails to suggest a correct file name for an OMF archive log file stored in an ASM diskgroup. Bug 7002207 SECURITY: Creating a compound index on a TDE column and a non-encrypted column where the non-encrypted column is modified by a function such as DESC or + 1, fails with ORA-28337. Bug 5218905 SPACE: ORA-600 [kcbnew_3] can occur when segment advisor has been running on an instance, as it can read blocks into the cache as Current when it should have read them as CR. Bug 6783812 SPACE: Process / SMON hang may occur with 'enq: SS - contention'. Bug 5416118 SQLEXEC: ORA-600 [qkacon:NFswrwo] from CONNECT BY query with subqueries. Bug 5757106 SQLEXEC: An aggregate query with constant argument may fail with ORA-600 [15851] when literal replacement is enabled. Bug 6975521 SQLEXEC: ORA-7445 [_MEMCPY] under qknsrAllocate->memcpy may be returned for a remote database query. 10.2.0.3.0 Patch 27 (10.2.0.3.27P) 32-Bit Patch 7353782 64-Bit (Itanium) Patch 7353784 64-Bit (x64) Patch 7353785 BaseBug Abstract Bug 7005789 DATAVAULT: Running FNDDBVEBS.SQL to configure Data Vault takes 30+ hours. Bug 5688676 OLAP: Parallel load uses Full Table Scan and a second but correct query for each sub partition. Bug 7188610 OO4O: Dequeuing multiple JMS messages fails after first message with OCI-22060. Bug 6378112 RAC: LMS can fails with ORA-600 [kjblpkeydrmqscchk:pkey] bringing down the RAC instance. Bug 5654013 SECURITY: EUS shared server connection fails with ORA-28030. Bug 6442431 RDBMS: In a RAC cluster Server-Side load balancing can cause one of the nodes to stop receiving any new connections even though it is idle. Bug 6777940 TEXT: Can not index MS Word document. Bug 5252061 XDB: PGA memory corruption can occur (ORA-600 [17456]) when creating a domain index. The corrupted memory contains the tail end of the table name on which the index is being created. Fixes included for Critical Patch Update - October 2008 10.2.0.3.0 Patch 26 (10.2.0.3.26P) 32-Bit Patch 7277355 64-Bit (Itanium) Patch 7277356 64-Bit (x64) Patch 7277357 BaseBug Abstract Bug 6615740 DATAGUARD: Logical Standby may use a lot of PGA memory and fail with ORA-4030 with long running transactions. Heap dumps indicate "knas:shtrans" subheap as highest consumer. Bug 6869009 ODP.NET: Finalizer deadlock / crash when using proxy connections. Bug 6316585 OPTIMIZER: Type check may fail with ORA-7445 [opitca] when complex view merging occurs and the select list item in the outer query block contains arithmetic or boolean expressions. Fix re-included, as it was not correctly merged into the Windows bundle. Bug 6749470 RAC: Oracle Object service fails to start on x64 Windows when MSCS is also installed on the same cluster. Bug 6520661 RAC: OracleRemExecService consumes more and more memory as cluvfy commands are being executed. Bug 5671929 SPATIAL: Large memory allocations when using SDO_GEOM.RELATE. Fix was removed from this bundle due to regressions. Bug 6965540 SQLEXEC: ORA-904 may be returned when query involves database link / remote co-located join. The following fixes have been missing since 10.2.0.3 patch 1 on Windows x64 : Bug 5439588, Bug 5397953, Bug 5093837, Bug 4724074, Bug 5471453, Bug 5088977, Bug 5403398, Bug 4377659, Bug 5569805, Bug 5716932, Bug 5108234 and Bug 5558356. They have been include here. 10.2.0.3.0 Patch 25 (10.2.0.3.25P) 32-Bit Patch 7252496 64-Bit (Itanium) Patch 7252497 64-Bit (x64) Patch 7252498 BaseBug Abstract Bug 5566439 RAC: Dropping a partitioned table can be slow with long waits on 'enq: RO - fast object reuse'. Fix re-included due to Bug 7218461 which caused ORA-7445 [kgghtIterInit2]. Bug 7251811 RDBMS: Pga spare variable KSPAPV10 used by 10.2.0.3 patch set conflicts mechanism for one off patches. Fixes included for Critical Patch Update - July 2008 (Representative Bug 7255442) 10.2.0.3.0 Patch 24 (10.2.0.3.24P) 32-Bit Patch 7142318 64-Bit (Itanium) Patch 7142319 64-Bit (x64) Patch 7142320 BaseBug Abstract Bug 5213488 AWR: "rows per sort" in AWR report overflows and only shows ########. Bug 6804150 EXPORT: 9.2.0.x export fails with ORA-01406 exporting a 11.1.0.x database. Bug 5767661 OPTIMIZER: Wrong results are possible from queries using functional indexes that have terms that do not reference columns. Bug 5879865 OPTIMIZER: ORA-7445 [_evaopn2+153] from query with EXISTS subquery involving non mergeable view. Bug 5901254 RAC: A starting node may not be able to join the cluster. Bug 4743582 RDBMS: A table scan with predicates of the form COL1 relop COL2 can return wrong results intermittently. Bug 5843814 RDBMS: XA_RECOVER is very slow or query on GV$GLOBAL_TRANSACTION is very slow. Bug 5155885 RDBMS: ORA-600 [KKSLGBV0] / Segmentation Violation can occur accessing bind values while deciding to shared a cursor (cursor_sharing = similar). Fix rebuilt on Windows x64. Bug 5117577 SPATIAL: SDO_CS.TRANSFORM() is not supported with EPSG CRS (3005). Attempting to use it fail with ORA-13282. Bug 6952800 SPATIAL: SDO_FILTER memory leak against particularly partitioned tables but can be a problem on ALL spatial Tables, can manifest as a performance degradation. Bug 6863983 SPATIAL: Index creation of dataset with point data fails with ora-29855. Bug 6759032 SQLEXEC: Some queries with GROUP BY, set operations and NULL columns may report a false "ORA-00979: not a GROUP BY expression". Bug 5844617 SQLPLUS: Returns wrong exit status using 'whenever' clause. Bug 5763576 XDB: XMLForest() can return wrong results (returns an empty element) if there is a NOT NULL constraint on the column in an outer-joined query. Bug 4766344 XDB: XDB should not use DBMS_SYS_SQL. Bug 7003718 XDKC: XVM transform produces duplicate values in 10.x.x, but not in 9.2.x. 10.2.0.3.0 Patch 23 (10.2.0.3.23P) 32-Bit Patch 6998002 64-Bit (Itanium) Patch 6998003 64-Bit (x64) Patch 6998004 BaseBug Abstract Bug 6600051 AQ: Enqueue after alter queue can cause a hang (time manager hang or core dump) in RAC environments. Bug 6771400 ASM: ORA-600 [kfgFinalize_2] can occur in ASM when mounting a disk group. Bug 5576584 ASM: Poor ASM parallel read performance. Bug 5238386 DATAGUARD: Standby Redo Log (SRL) header is not written by the correct routine which can lead to ORA-322 on reading the log for specific timing scenarios. Bug 5844945 DATAGUARD: Bystander cannot receive missing log files from the old branch after a failover. Bug 6676049 DATAPUMP: Importing tables which have XMLType column fails with ORA-904, if system generated REF cols exists in the DDL of the tables that have columns based on xmlschema with xdb:SQLInline="faise". Bug 6845066 ODP.NET: Re-registration of is not required for RAC, HA and RLB. Bug 6986658 ODP.NET: Statement caching is not required for REF Cursors. Bug 6862248 ODP.NET: Command Timeout may cause poor performance due to limited Threadpool. Bug 6166400 OLEDB: Cannot fetch a row using a bookmark from OLE DB provider "OraOLEDB.Oracle" using linked server Microsoft SQL server management studio. Fix was lost from at least patch 20, so is re-included here. Bug 6528963 OLEDB: Executing a stored procedures on 64-Bit platforms, results in a PLS-306 error or hang on AMD64 platforms. Fix was lost from at least patch 20, so is re-included here. Bug 7005671 OLAP: Adding a value to a relation with more than one billion values returns ORA-600 [xsbaClose01]. Bug 6822995 OLAP: Slow OLAP performance when using BIEE Bug 6815733 OPTIMIZER: ORA-600 [qctcte1] can occur during optimization of queries with views or subqueries if they have an ORDER BY clause using scalar subqueries. Bug 6940486 PLSQL: ORA-1001 or ORA-604 may be raised after applying the patch for Bug 6701716. Bug 6239052 RAC: Instance may crash due to LMS failing with ORA-600 [kjbrchkinteg:last]. Bug 5643036 RDBMS: Code which performs a lot of object manipulation may incur some small performance overhead in koc* code. Bug 5208177 RDBMS: NLSSORT may return NULL instead of an error for a large non-null input value. Bug 6620517 RDBMS: Attempts to do TSPITR (Tablespace Point In Time Recovery) can fail needlessly with "ORA-29308: view TS_PITR_CHECK failure" if there is an IOT with a LOB column. Bug 5118272 RDBMS: Instance crash with ORA-600 [1433] [60] due to log writer filling up message blocks. (Messages could be for LGWR or ARCH). Bug 5063635 RDBMS: ORA-600[kccdagf_3] can occur during file creation when a RMAN deletion policy configuration is applied on the standby. Bug 6493830 RDBMS: Database does not honour the OID password policy to lock user account in OID when a user attempts invalid logins for more than the allowed number of times. Bug 6471770 RDBMS: Group-By queries can fail with ORA-32695 when operating on a large volume of data if hash group by aggregation is used. Bug 6870469 RDBMS: Real application testing (capture feature) support. Bug 6974999 RDBMS: Real application testing (replay feature) support. Bug 5860221 STREAMS: Apply aborts with OERI[17147] / memory corruption with FUNCTION BASED index. Bug 6914897 XDB: ORA-600 [qmxtcFlushTrxob:hsh] with direct patch / append hint. 10.2.0.3.0 Patch 22 (10.2.0.3.22P) 32-Bit Patch 6991039 64-Bit (Itanium) Patch 6991040 64-Bit (x64) Patch 6991041 BaseBug Abstract Bug 6887041 AQ: Merge of Advanced Queuing fixes: Bug 5857313 : ORA-600 [kwqbmcrcpts101] can occur after dropping propagation using DBMS_PROPAGATION_ADM.DROP_PROPAGATION Bug 5093060: Unnecessary Streams flow control can occur even though the apply site is fast enough. Bug 6527427 ASM: ORA-600 [kfclDoLockOp35] in ASM on certain SMP environments. Bug 6939234 ASM: Merge of ASM fixes: Bug 5502365 : ORA-600 [kfcDel20] can occur in ASM. Bug 6069360 : DBW can spin while holding a latch in kfcRunnableWaiter(), LMS / LGWR can get then blocked by the DBW. Bug 6069085 DATAGUARD: Merge of Data Guard fixes (included by MLR Bug 6943415: Bug 4684070 : Passwords changed via the SQL*Plus password utility are not propagated to the Logical Standby instances. Bug 5190392 : In a logical standby environment, dropping a table with triggers on the primary fails on the standby with : ORA-16227: DDL skipped due to missing object. Bug 6939290 RAC: Merge of fixes for RAC bundled patch: New in Patch 22: Bug 5556174, Bug 5728380, Bug 5118012, Bug 5573238, Bug 6114137, Bug 4699720, Bug 6527427 Included in prior bundled patches: Bug 5165885, Bug 5376770, Bug 6001617, Bug 6501007, Bug 6017420, Bug 6646613 Bug 6939219 RAC: Merge of RAC fixes: Bug 4441119 : Not enough information dumped when RAC detects a deadlock. Bug 5863926 : ORA-7445 [kjddopt] from LMON in RAC during deadlock detection. Bug 6939227 RAC: Merge of RAC fxies: Bug 5900401 : Instance crash by LMON due to "skgpgpstack: read() ..." error. Bug 5081798 : Additional diagnostics for ORA-600 [2103] when ASM is involved. Bug 5952530 : If a process reports 'IPC Send timeout' and cluster reconfiguration completes within 30 seconds from the report then the process may spin in / under ksxpwait consuming high CPU. Depending on the resources held this can lead to a wider hang scenario. Bug 6087793 : LMS process when running at elevated priority (RealTime), sometimes begins to spin on CPU causing system hangs. Bug 5526245 : QMNC process trace file may grow at a constant rate with warnings from ksxplookup. Bug 5556174 RAC: Dropping a partitioned table can be slow in a RAC environment (waits for 'gc current grant busy'). Bug 6114137 RAC: Running LMS in real-time can cause CSS crash and node reboot. Bug 5958244 RAC: LMS processes running in real-time can spin. Bug 5964485 RAC: LCK0 may suffer a delay receiving lock ASTs, depending on how busy it is. This can lead to various resource waits in a RAC environment (e.g. Library Cache Lock / Cursor: Pin S Wait on X). Included by MLR Bug 6939256. Bug 6797677 RAC: ORA-7445 [kggchk] possible during reconfiguration. Bug 5872943 RDBMS: OCI application returns ORA-1460 if it adjusts the OCI_ATTR_MAXCHAR_SIZE attribute when executing SQL with a VARCHAR bind variable. Fix re-included as earlier version was incomplete. Bug 5118012 RDBMS: Instance crash with ORA-600 [kclswrite_3] with multiple DBWRS processes. Bug 5573238 RDBMS: Shared pool memory use / ORA-4031 due to "obj stat memo" in one subpool. Bug 5721821 RDBMS: SGA corruption, ORA7445 [kglobcl], instance crash can occur in a RAC environment if objects are dropped and created in the same namespace but with a different object type. Included by MLR Bug 6939248. Bug 4336528 RDBMS: Parallel Query may be slower than expected due to excessive timeouts waiting for "PX Deq: Signal ACK". Bug 5728380 RDBMS: DML operations, such as INSERTs, may spin when looking for space in ASSM managed segments. This can occur for inserts into table data blocks or for inserts to index blocks. Stacks for the spinning process show that it spins in ktspffc Bug 4699720 RDBMS: MMON spin in ksrpublish() / PMON spin in ksrccolc() in RAC environments. Bug 5079978 RDBMS: RAC performance slowdown, with high US enqueue contention on the same US enqueue. Bug 5755010 RDBMS: Listener registration does not complete with some listeners even though there is no indication of registration failure. Bug 5556152 RDBMS: Dropping a partitioned can be slow (Waits on 'dfs lock handle' for CI[1][2]). Included by MLR Bug 6939270 Bug 5366893 RDBMS: After an instance has been aborted for some reason CF enqueue contention may be seen during first pass redo scan in a RAC environment as LMD is not posted. 10.2.0.3.0 Patch 21 (10.2.0.3.21P) 32-Bit Patch 6932785 64-Bit (Itanium) Patch 6932786 64-Bit (x64) Patch 6932788 BaseBug Abstract Bug 6445864 AQ: Frequent ORA-2049 errors can occur using OC4J AQ. Bug 6376928 CBO: ORA-3113 from GROUP BY query with predicates on functional index column. Bug 6869828 CBO: Merge of optimizer fixes: Bug 6122097 : ORA-7445 [evaopn2] / Core dump using a function based index. Bug 5903829 : ORA-600 [qkshtTabInf2:1] can occur parsing a query. Bug 6909784 DATAGUARD: Merge of Data Guard fixes (Bug 6067600): Bug 6128197 : ORA-600 [kcrfr_resize2] can occur during recovery if the redo log was generated in earlier versions. Bug 5206649 - Logical standby finish apply time is highly variable on an idle system. Bug 5512840 - Logical standby fetch slave stops with ORA-600 [knahfgx704]. Bug 5087369 - Logical standby potential data loss during failover. Bug 5225733 - After flashback operation, new logs are not applied in logical standby. Bug 5865842 - DBA_REGISTERED_ARCHIVED_LOG.DICTIONARY_END contains extra space for 'NO' value. Bug 5602452 - Streams capture gets stuck in 'dictionary initialization' after recovery. Bug 5883622 - Streams Capture crashes or reports errors after restart in CCA mode. Bug 5867943 - Streams capture aborts with ORA-600 [knlcloop-200] mining "ALTER TABLE SPLIT PARTITION ...". Bug 5723260 - Logminer slow / excess memory use processing batch inserts with LOBs. Bug 5170394 - Logminer incorrect memory estimation may lead to unnecessary latch contention. Bug 5515703 - Streams table diverges after partial rollback on primary. Bug 6643194 NET: Database service and SQLPlus hang if sqlnet.outbound_connect_timeout is set. Bug 6688740 NLSRTL: ORA-7445 [lxoVldStr] or ORA-7445 [lxoMonoCmp] using NLS_SORT=xczech. Bug 6686309 PROCOBOL: Applications using indicators can get ORA-1400 or ORA-1841 errors at runtime. Bug 6001677 DATAVAULT: Users cannot reset their own password following expiration with Data Vault enabled. Bug 6870047 RDBMS: ORA-8175 with fix for Bug 5028099. Bug 5949116 RDBMS: Flashback logs are not purged when archiver is out of disk space. Bug 5248932 RDBMS: XML audit filenames do not include the process id. With this fix the XML audit filename on all platforms should be of the form "<ProcName>_<ProcessId>.xml". Bug 6122696 RDBMS: ORA-7445 [osnsgl] after an ORA-3115 has been signalled. Bug 5925224 RDBMS: Compression does not correctly handle rows that are larger than the block size leading to ORA-600 [kdblcflush:#row] errors. Bug 5363584 RDBMS: Array insert into partitioned table can corrupt redo. Bug 6455161 RDBMS: Higher CPU / Higher "cache buffer chains" latch gets / Higher "consistent gets" after truncate/Rebuild. Bug 6872071 TEXT: Merge of text fixes: Bug 6694515 : Stemming query for similar words / MIXED_CASE gives words with incorrect case. Bug 6646504 : Stemming query for similar words / MIXED_CASE and German returns incorrect results. Bug 6504287 : Oracle Text search with MIXED_CASE attribute of basic lexer fails (DRG-00100). 10.2.0.3.0 Patch 20 (10.2.0.3.20P) 32-Bit Patch 6867054 64-Bit (Itanium) Patch 6867055 64-Bit (x64) Patch 6867056 BaseBug Abstract Fixes included for Critical Patch Update - April 2008 (Representative Bug 6864208) 10.2.0.3.0 Patch 19 (10.2.0.3.19P) Only available in 32-Bit Patch 6867052 64-Bit (x64) Patch 6867053 BaseBug Abstract Bug 6200820 AQ: Node affinity not reconfigured after RAC reconfiguration (QMNC timeouts). Bug 6316585 CBO: Type check may fail with ORA-7445 [opitca] when complex view merging occurs and the select list item in the outer query block contains arithmetic or boolean expressions. Bug 6112946 CBO: The performance of running gather_database_stats() can be a lot worse than running gather_database_stats_job_proc(). Bug 6084796 DBCONTROL: After applying CPUAPR2007 the job library is inaccessable. Bug 6776276 INTERMEDIA: CPUJAN2008 causes invalid spatial objects. Bug 6688495 ODP.NET: Inserting values into BINARY_FLOAT column using ORACLEDECIMAL fails. Bug 6327248 OLEDB: When attempting to query numeric data through to SQL Server 2005 running on an Itanium (IA64) system, Numeric columns, such as 9999 return 00 instead of the correct results. Bug 6701716 PLSQL: ORA-7445 [peircmov] returning a REF CURSOR from EXECUTE IMMEDIATE. Bug 6808369 RAC: OCSSD.EXE is not installed properly when applying Windows bundled patches. Bug 6751527 RDBMS: ORA-7445 [INT_DIVIDE_BY_ZERO] [_kcblclc] Bug 6756089 RDBMS: OCI rounds off floating point numbers with a decimal precision greater than 5 when they are used as part of an OBJECT / TYPE. e.g. Input value 321.12345678 gets inserted as 321.12346. Bug 6043854 RDBMS: Short stack dumps do not work on 64-Bit Windows. Bug 6684124 RDBMS: Shutdown immediate hangs with the foreground stack showing RTLCriticalSection, RTLHeapAlloc etc Bug 6720712 RDBMS: Under high load current execution of 'alter table ... add subpartition' can result in mutlple subpartitions for the same partition ID. Bug 6607676 RDBMS: OCI applications may leak critical section's and fail with an Access Violation in OraClient10!kpufhndl0. Bug 5890312 RDBMS: Hang observed when creating CTXCAT index / potential space leak. Bug 5934363 RDBMS: Create CTXCAT INDEX my hang (spin in space allocation). Bug 5704108 RDBMS: Insert as select into partitioned table hangs when using DBA search cache. Bug 4927563 RDBMS: Access violation in qerixGetKey(). Bug 6503023 SPATIAL: After applying CPUJULY2007, SDO_TOPO-GEOMETRY, SDO_IDX, SDO_SAM become invalid. 10.2.0.3.0 Patch 18 (10.2.0.3.18P) 32-Bit Patch 6812783 64-Bit (Itanium) Patch 6812784 64-Bit (x64) Patch 6812785 BaseBug Abstract Bug 6075522 CBO: Query containing ora_rowscn on top of a view with no_merge hint returns wrong results. Bug 4752814 CBO: Query using a predicate with a VARCHAR2 column and an ANSI CHAR bind variable can get a suboptimal plan as the selectivity of the predicate may be miscalculated. Bug 6653704 CBO: Query using a Nested Loop join of a Bitmap accessed table using functional indexes and another table which has an index filter that involves the functional index expression returns an ORA-7445 [evaopn2]. Bug 6525496 CBO: Bitmap combination of functional indexes with common virtual column could produce wrong results. Bug 6474804 CBO: Old style push predicate could cause crash / ORA-7445 [evaopn2] if functional index was involved in access path in the view or parent query block. Bug 6121357 CBO: ORA-600 [17051] during rewrite, the summary which was expected to be used is in INVALID status. Bug 5407480 DV: AQ calls fail with insufficient privileges (ORA-1031) errors, when the Database Vault option is enabled. Fix re-included after a new base label was produced. Bug 6626431 DV: Cannot create, alter or drop a user from a trigger with Data Vault. Bug 5128625 NLSRTL: ORA-600 [17147], ORA-600 [17182] or NULL results from NLSSORT when processing a long source value for a multi-lingual sort. Bug 6169451 OCCI: Connections can hang after TAF failover in a multi-threaded OCCI application that uses OCISessionPool. Bug 6669139 OLEDB: Errors occur when executing SQL Statements using a TO_CHAR literal. Bug 6490207 OLEDB: ORAOLEDB.ORACLE with ADO.NET and a number greater than 28 digits of precision returns Accessor is not a parameter accessor error. Bug 6445241 INTERMEDIA: Quality of jpeg thumbnails generated with processcopy is low. Bug 6082292 ORAMTS: RM is committed even when SERVICEDOMAIN.LEAVE() returns TRANSACTIONSTATUS.ABORTED. Bug 6755847 OUI: Some OLEDB files do not get copied oveer when installing the Windows bundled patch. Bug 5365683 RAC: CRS repeatedly stops and restarts VIPs while recovering multiple nodes. Bug 4882822 RAC: VIPs for down nodes can lead to a bounce at node join time unnecessarily. This can delay node failover processing. Bug 5190596 RAC: LMON dumps LMS0 too frequently (few seconds apart) during DRM and LMS0 is subsequently stalled leading to "IPC send timeout" and an instance crash. Bug 5376770 RAC: Spin in KCLDLE causes a cluster hang. Bug 6012053 RDBMS: Grouping sets queries can fail with ORA-600 [qctcte1]. Bug 5883112 RDBMS: Fake deadlocks can show up in RAC environments due to a duplicate Instance Lock ID for a cache id in the row cache. The blocked session shows as waiting on "row cache lock", but the instance lock covering this has an ID which clashes with a different item. Bug 6452485 RDBMS: ORA-600 [17182] error can occur when using SQL which binds object (ADT) datatypes when the fix for Bug 6085625 is installed. Fix re-included due to build issues. Bug 6136074 RDBMS: Recompilation of a view might lead to inconsistent timestamps for some of the view's PL/SQL dependents. ORA-4068 / ORA-4065 ORA-6508 signalled on valid objects. Bug 5745084 RDBMS: OAR-600 [ksmals] [sql txt in kkslod] querying V$ views which access X$KGLLK. Bug 5024703 RDBMS: When altering a spatial index to parallel queries using the index may not parallelize when expected with the execution plan showing: PX COORDINATOR FORCED SERIAL. Bug 6815548 RDBMS: Readme instructions for 10.2.0.3 patch 17 instant client are incorrect. Bug 4611578 RDBMS: ORA-600 [15570] can occur with a SQL statement with a UNION ALL on the right hand side of a NESTED LOOPS JOIN when the query is run in parallel. Bug 5254759 RDBMS: ORA-12801 / ORA-1008 can occur if literal replacement is enabled and there are user bind in the query and the query executes in parallel. Bug 5893331 RDBMS: ORA-7445 [kksEndOfCompile] / ORA-4031 when memory_target is set. Bug 6119884 RDBMS: Wrong results with query with OR operator with OR expansion. Bug 5880921 RDBMS: In certain situations, the time displayed from v$sysmetric_history is in the wrong time zone. Fix re-included after base bug was re-fixed. Bug 6845234 RDBMS: Readme instructions for 10.2.0.3 patch 17 incorrect for ODP.NET. Bug 5581472 STREAMS: Capture process may generates excessive I/O requests during periods of low or idle redo generation. Fix re-included after a new base label was produced. 10.2.0.3.0 Patch 17 (10.2.0.3.17P) 32-Bit Patch 6724003 64-Bit (Itanium) Patch 6724004 64-Bit (x64) Patch 6724005 BaseBug Abstract Bug 5512478 ASO: Multi threaded application making multiple simultaneous connections causes erroneous replay cache errors. Bug 5381446 CBO: Core Dump or wrong results can occur during execution of queries undergoing Star transformation with temporary table transformations if an index join is used inside the temporary table load. Bug 6035809 CBO: SQL Analyzer query failed with ORA-7445 [lnxsni] Bug 5693303 DV: SYSDBA cannot login using OS authentication when Data Vault is enabled. Bug 6530171 DV: When event 47998 is enabled realm creation may fail with a ORA-7445 [strlen] / Core dump when executing DBMS_RLS. Bug 6456110 DV: Create, Access or Delete of an OLAP workspace in a realm protected schema using the dbms_aw package, may fail with a realm violation error (ORA-33263) even if the user is authorized to the realm. Bug 6680993 INSTCLIENT: Failure to register an ODBC connection using the Microsoft provider with Instant Client. Bug 6342503 HS: Streams apply process is slow when applying to SQLServer through transparent gateway. Bug 6607486 OLAP: ORA-33263 from OLAP with Data Vault. Bug 6629890 RAC: Some resource may not start automatically after creating OracleCRSToken. Bug 6155791 RAC: "kjdrpkey2hv: called with pkey" messages are repeatedly generated. Bug 5566439 RAC: Dropping a partitioned table can be slow with long waits on 'enq: RO - fast object reuse'. Bug 6501007 RAC: DRM sync timeout because of failing to quiesce a local lock. Bug 5891737 RDBMS: ORA-7445 [kcblsod] or an ORA-600 [723] due to a PGA memory leaks, usually in an ASM/RAC scenario if connections to the Cluster Manager are lost frequently. Bug 6607505 RDBMS: ORA-600 [15201] / ORA-600 [mal0-size-too-large] errors can occur during DML operations on objects having functional indexes containing LOB columns. Bug 6005525 RDBMS: V$SQL PARSING_SCHEMA_NAME is not populated for schema owners. Bug 6346393 RDBMS: Conventional import of tables containing SYS.ANYDATA columns which contain object data can cause untranslated (opaque) ANYDATA content to be loaded into the database. Such data can then lead to spins and/or internal errors as ANYDATA columns should not contain the opaque form of the data. Bug 5336968 RDBMS: PQ slaves killed because of resource manager max idle time. Bug 5023410 RDBMS: Parallel Query QC can wait on "PX Deq: Join ACK" even when a slave is available. Bug 5120476 RDBMS: Blank padding does not occur for SQLT_CHAR and SQLT_AFC define types for OCI / Pro* clients if there is no character set conversion for a multibyte character set. Notable this affects external procedure callouts. Bug 6646613 RDBMS: Index Organized Tables created / updated with COMPATIBLE <= 9.2.0.8 which are subsequently used with COMPATIBLE >= 10.1.0.2 can become corrupt. The initial corruption does not show any external symptoms, but subsequent operations on a corrupt block can lead to noticeable corruptions and resulting ORA-600 errors or dumps. Bug 4865755 RDBMS: An error during an DBMS_LOB operation can appear as an ORA-600 [9999]. Bug 6282093 RDBMS: Some CONNECT BY queries do not undergo OR expansion when processing the START WITH predicates. Bug 4344935 RDBMS: ORA-600 can occur during DMLs / rollback on a temporary table after the temporary table is truncated in an autonomous transaction. Bug 5384248 RDBMS: PMON can crash the instance because it tries to acquire a DX lock while holding another one that is not yet cleaned up. It crashes with ORA-600 [K2GTElock: !k2gtca] Bug 5387030 RDBMS: When undo tablespace is using NON-AUTOEXTEND datafiles, V$UNDOSTAT.TUNED_UNDORETENTION may be calculated too high preventing undo blocks from being expired and reused. Bug 6163622 STREAMS: KGL library lock leakage degrades streams apply performance as transaction size grows larger and there is a transformation defined for apply rules. Bug 6504287 TEXT: Oracle Text search with MIXED_CASE attribute of basic lexer fails (DRG-00100). Bug 5018532 XDB: Insertion or validation of valid instance document can fail with ORA-600 [qmxargetelem2] or a Core dump. Bug 6491175 XDB: Stack overflow condition can occur under qmxtriCheckAndRewriteQb_rec when re-writing an XDB query with very complex predicate structure. 10.2.0.3.0 Patch 16 (10.2.0.3.16P) 32-Bit Patch 6637237 64-Bit (Itanium) Patch 6637238 64-Bit (x64) Patch 6637239 BaseBug Abstract Fixes included for Critical Patch Update - January 2008 (Representative Bug 6647106) 10.2.0.3.0 Patch 15 (10.2.0.3.15P) Only available in 32-Bit Patch 6637235 64-Bit (x64) Patch 6637236 BaseBug Abstract Bug 6407114 ASM: Instance crash with ORA-600 [kfnDisconnect]. Bug 5939241 ASM: Following a rejected disk offline (either via a command or implicitly after an I/O error) the diskgroup configuration may appear inconsistent. Bug 5481520 CBO: Wrong results are possible with a ROWNUM predicate when bind peeking is used for user defined binds when the fix for Bug 4513695 is present. Bug 5395270 CBO: Wrong results, ORA-600 [qctcte1] or Core Dump from : View with select list subquery which is referenced in multiple places in the outer query block (view merging of the view). Bug 5071931 DATAPUMP: Import of a schema with a REMAP tablespace option takes long time doing METADATA CONVERT. Bug 4570768 NET: CMAN not able do connection over two hops (ORA-12564 is returned). Bug 5961436 ODBC: Executing a stored procedure after Execution of insert query fails with ORA-936. Bug 6126083 ODP.NET: ORA-24814 / Exception -3001 accessing temporary LOBs. ODP.NET / OO4O / OLEDB fixes are now included in x64 Windows bundles. Bug 5043675 OLEDB: Attempts to update or delete a record in an Oracle Table via a SqlServer2005 link for 64-Bit Window fails with Msg 7333, Level 16, State 2, Line 1 Cannot fetch a row using a bookmark. Bug 6166400 OLEDB: Cannot fetch a row using a bookmark from OLE DB provider "OraOLEDB.Oracle" using linked server Microsoft SQL server management studio. Bug 6528963 OLEDB: Executing a stored procedures on 64-Bit platforms, results in a PLS-306 error or hang on AMD64 platforms. Bug 6277322 OLEDB: PLS-306 error, when using a stored procedure with an out refcursor on 64-Bit Windows platforms. Bug 6526468 PLSQL: Leaking element pages in a session on insert / delete with one session. Bug 5893340 RDBMS: ORA-600 [32695] [hash aggregation can't be done] can occur for a GROUP BY query. Bug 6452485 RDBMS: ORA-600 [17182] error can occur when using SQL which binds object (ADT) datatypes when the fix for Bug 6085625 is installed. Bug 5898210 RDBMS: Hang from concurrent MV refresh and library cache invalidation in RAC. Bug 4531589 RDBMS: ORA-22370 "incorrect usage of method" can occur when trying to pass SYS.AnyData containing a collection to a method. Bug 6347380 RDBMS: ASM does not find necessary ASM disks when any other non-ASM disks are exclusive mode by CLUSTERPRO. Bug 5704314 RDBMS: ORA-7445 [opihmi] / Core dump. Bug 6376915 RDBMS: HW enqueue contention can occur for LOB segments which are ASSM managed as space allocation only acquires one block at a time. Bug 5211863 RDBMS: CONNECT BY query containing a subquery in the START WITH clause may be slow (poor plan). Bug 6168288 RDBMS: Executing a date function may corrupt the session's internal date context leading subsequent operations to ORA-7445 / Core dump. Bug 6087793 RDBMS: LMS process when running at elevated priority (RealTime), sometimes begins to spin on CPU causing system hangs. Bug 6315932 SPATIAL: ORA-13249 when using SDO_JOIN() with long table bames. 10.2.0.3.0 Patch 14 (10.2.0.3.14P) 32-Bit Patch 6627412 64-Bit (Itanium) Patch 6627413 64-Bit (x64) Patch 6627414 BaseBug Abstract Bug 3786828 ANO: Connection using OMSFT (Microsoft internal credential cache) fail with ORA-12638 on a MULTIBYTE Windows client machine. Bug 4334700 AQ: DDL fails with ORA-600 [17020] during datapump import. Bug 5949981 CBO: Poor selectivity calculations are possible during optimization for predicates against columns with frequency histograms, if the constant value used matches a single-row histogram bucket. Bug 5696532 DATAVAULT: CREATE TRIGGER can fail with ORA-6502 when the triggering object name is not fully qualified. Bug 5471564 JAVAVM: ORA-7445 / Core Dump in joe_run_vm while trying to call interface method. Bug 5583712 MVIEW: ORA-942 can occur on primary key based materialized view creation against a remote view. Bug 5561244 ODBC: SQLGetConnectOption (SQL_ATTR_CONNECTION_DEAD, ...) fails with access violation. Fix re-included after base bug fix was amended. Bug 6499241 ODP.NET: Access Violation when OracleCommand.Commandtimeout is used. Bug 6616290 ODP.NET: Access Violation on double free with OCIDescriptor in the context of OpoSqlValCtx. Bug 6616345 ODP.NET: Introduction of a registry key for odp.net to turn metadata poling on/off Bug 6616352 ODP.NET: Access Violation when the same statement is executed through different threads through adapter.fill or reader.executereader. Bug 6154479 ODP.NET: Application sometimes hangs when using LOBS, when an exception is encountered. Bug 6489976 ODP.NET: Heap corruption at OraOps10w!OpsPrmFreeOpoPrmCtx when odp.net is used with w3wp process. Bug 5183045 PLSQL: ORA-7445 [pevm_MOVN] executing PL/SQL. Bug 6145177 RAC: Single resource self-deadlock on zero DID. Bug 5362021 RDBMS: ORA-7445 [lnxmin] during execution of SQL which involves user defined functions. Bug 6165874 RDBMS: ORA-600 [kksfbc-reparse-infinite-loop] from a select on views which are dependent on such subtype which was dropped by drop subtype validate and then recreated. Bug 6118038 RDBMS: ORA-600 [koputilcvto2n] after alter type during upgrade / downgrade. Bug 4367986 RDBMS: Parallel execution cursors are not shared when bind peeking is used. Bug 5556555 RDBMS: ORA-1003 during re-execute (using same statement handle, executing same statement in previously execute), if parse error is reported during previous execute. Bug 5411244 RDBMS: ORA-4022 raised while rebuilding index partitions concurrently. Bug 5896963 RDBMS: High LGWR CPU utilization and increased commit latency as measured by the 'log file sync' wait event. Bug 6056632 RDBMS: ORA-7445 [.rpiswu2] caused by optimizer optimizations. Bug 6044413 RDBMS: Intermittent wrong results when table prefetch occurs. Bug 6145687 RDBMS: Queries may return incorrect row-scn's. Bug 5883691 RDBMS: ORA-7445 [kxhrUnpack] is returned for a query where a constant string column obtained from a remote rowsource is involved. Bug 6029469 RDBMS: Index range scan (min/max) used to get Max value instead of Index Min/Max First Row. Bug 4439469 TEXT: Analyze index (table) can block DML operations with Text indexes. Bug 4739114 XDB: Session log off can Core dump in kghfrf in a shared server connection after using DBMS_XMLDOM. Bug 6506816 XDB: Memory leak in session heap (memory has comment "qmxtgConsXMLFro"), from statements where CHAR type is being converted to XML TYPE, can cause ORA-4030. Bug 5003275 XDKCPP: XSLT VM may Core dump when processing style sheets with a large number of patterns. 10.2.0.3.0 Patch 13 (10.2.0.3.13P) 32-Bit Patch 6503506 64-Bit (Itanium) Patch 6503507 64-Bit (x64) Patch 6503508 BaseBug Abstract Bug 5629724 ANO: Support mapping of > 30 character Kerberos principle to database schema. Bug 6193802 ANO: SQLPLUS reports error when using PKCS11 wallet with 10.2.0.3 patch 6. Bug 5192858 CBO: Dropping a table with an object type column where the type has associated statistics can fail with ORA-7445 [kknerd]. Bug 5103126 CBO: Inserting duplicate rows into a table with a unique constraint / primary key takes much longer to execute in 10.x.x than in 9.x.x. The main CPU overhead occurs underneath kauerr(). Bug 5494240 CBO: ORA-600 [15201] can occur when an IOT unique secondary index is used. Bug 6050882 CBO: Wrong results are possible from ANSI outer joins (when the fix for Bug 4967068 or Bug 5864217 are applied) as the outer join table elimination may incorrectly eliminate the table. Bug 6319761 CBO: DBMS_STATS.GATHER_SCHEMA_STATS fails with ORA-1476 (division by zero error). Bug 6131467 CBO: Wrong results are possible from queries using tables having functional indexes using SUBSTR() on CHAR columns in databases with multi byte character sets. Bug 6061623 CBO: ORA-932 when INSERT AS SELECT contains TO_LOB in the top-level SELECT query block. Bug 6181488 DATAGUARD: Logical Standby terminates with ORA-4030. Bug 5852921 DATAPUMP: EXPDP fails with ORA-29913 / ORA-29400 / KUP-554 / KUP-1006 / KUP-562 incorrectly trying to interpret the backslash character as an escape character. Bug 5135951 DATAPUMP: ORA-22337 on import if database schema has been evolved (importing a varray). Bug 6401347 DATAVAULT: CREATE PACKAGE / PROCEDURE / FUNCTION may fail with ORA-6512 in a system using a multi-byte character set (e.g., AL32UTF8) if Data Vault is enabled. Bug 5385973 HS: ODP.NET gets truncated char / varchar data in HSODBC environments using multi byte character sets. Bug 6342823 INTERMEDIA: VID-706 unsupported or corrupted input format with MP4 format files. Bug 5527479 JDBC: Data corruption when BigDecimal is bound and the JDK version is 1.5. Bug 4727401 LOGMINER: LogMiner incorrectly generates timestamp values with 0 as the fractional seconds portion of the timestamp. The SQL_REDO generated for a DML involving a timestamp column will ALWAYS be 0. Bug 5955732 NLSRTL: Two child cursors created when querying ku$_10_1_fhtable_view. Bug 6142534 OCCI: Fetching a varray of numbers in an OCCI program can result in null elements in the varray being marked not null. Bug 5396837 OSS: File handle leak from nzcrlGetCRLFromFile. Bug 6431995 ODP.NET: Heap corruption at OraOps10w!OpsPrmResetOpoPrmCtx when ODP.NET used with w3wp process. Bug 5581731 PLSQL: Wrapped packages with trailing blank lines and a Unicode database fail with PLS-103. Bug 6134126 RAC: Backups may fail when OCR tries to check block headers when it should not. Bug 6336234 RDBMS: 64-bit Oracle instance / service may crash with stack overflow (qmxtriCheckAndRewriteQb). Bug 5552515 RDBMS: The heap statistics for memory type "ktcmvcb" are incorrect in V$SGASTAT which can make it look like there is an SGA memory leak occurring when there is no problem with such allocations. Bug 4311273 RDBMS: Executing a MERGE statement over database link can fail with ORA-2064 Bug 4644425 RDBMS: The shared pool can be corrupted (ORA-7445 SIGBUS in koksrvc / ORA-600 [17147]) when updating a table with a functional domain index on it. Bug 4216668 RDBMS: INSERT or MERGE commands might core dump / ORA-600 [17175] if operating on object types and internal columns. Bug 6168297 RDBMS: OCIDirPathColArrayToStream function fails with a "ORA-12899: value too large for column" error when the number of characters in the string is approaching the limit allowed for the field, when using using UTF8 encoding. Bug 5131157 RDBMS: OCI may error re-executing a statement against a table with an altered column type Bug 5933477 RDBMS: Client <= 9.2.0.7 / 10.1.0.4 can core dump when running against higher versioned databases. Bug 5768710 RDBMS: ALTER TABLE ... SHRINK SPACE CASCADE takes a very long time on a table with LOB columns. Bug 4591936 RDBMS: Unnecessary "kccsga_update_ckpt ..." media recovery messages are logged at startup. Bug 5188321 RDBMS: Wrong results (no rows) can be returned with a query involving a very large select list count when ANSI OUTER JOIN syntax is used. Bug 5872943 RDBMS: OCI application returns ORA-1460 if it adjusts the OCI_ATTR_MAXCHAR_SIZE attribute when executing SQL with a VARCHAR bind variable. Bug 5455632 RDBMS: Core dump / ORA-7445 can occur accessing data over a database link with a stack of the form: memcpy kpccclr ttccfpg ttcfour kpufcpf kpufch0 kpufch qerrmOFBu qerrmFBu qerrmFetch ... Bug 2837580 RDBMS: ORA-3113 / ORA-7445 can occur if query has > ~35000 literals when literal replacement is enabled. Bug 6343883 RDBMS: ORA-932 when using OCI_DESCRIBE_ONLY with user binds. Bug 6150438 RDBMS: ORA-932 when a select uses a collect() function in two different schema having the same type constructs. Bug 5750711 SPATIAL: ORA-3113 / ORA-7445 [mdgoplun] querying spatial data. Bug 6215662 SQLLDR: SQL*Loader swaps bytes during direct path loads into BINARY_DOUBLE or BINARY_FLOAT columns when the client and server are on different byte order platforms Bug 5278539 STREAMS: ORA-23605 can occur when creating streams capture when archive logs have been backed up, deleted, then restored using RMAN. Bug 5259741 XDB: DBMS_XMLGEN.CONVERT can return wrong (truncated) results or signal ORA-29275 when decoding a multi byte string. Bug 5512159 XDB: DOCTYPE may get appended after parsing when the document comes from an external sources(the parser API). 10.2.0.3.0 Patch 12 (10.2.0.3.12P) 32-Bit Patch 6430171 64-Bit (Itanium) Patch 6430173 64-Bit (x64) Patch 6430174 BaseBug Abstract Fixes included for Critical Patch Update - October 2007 (Note 455284.1 / Representative Bug 6404873) 10.2.0.3.0 Patch 11 (10.2.0.3.11P) Only available in 32-Bit Patch 6430168 64-Bit (x64) Patch 6430169 BaseBug Abstract Bug 6405018 ANO: Shared server dies (ORA-7445 [[_sslIsTerminalServerSupported] trying to access authentication information after the client has abnormally terminated its connection. Bug 5594352 AQ: JMS-120 / OCI-1858 can occur when dequeuing an AQ bytes message with JDBC-OCI in some non Amercian NLS_LANG settings. i.e.: when dequeuing an AQ$_JMS_BYTES_MESSAGE type message Bug 5526987 ASM: A file creation rollback in ASM can lead to an ASM instance hang when the rolling back session tries to get the FA enqueue in X mode but it is already held. This can lead to an ORA-600 [2103] on the database instance. Bug 6145570 CBO: Query returns wrong results, when it contains a like predicate that undergoes join predicate pushdown and the like predicate is on a column with a SUBSTR function-based index. Bug 6310653 CBO: ORA-600 [kkqctmdcq: ...] on an INSERT as SELECT. Bug 5707754 CBO: ORA-3113 / Oracle.exe crash when executing very large query (stack overflow on Windows, stack shows apaqbd or kkqvmTrMrg, vopqbc in 10.1 and 10.2). Fix re-included because the label was incorrect. Bug 5864217 CBO: ORA-600 [kkoljt] can occur in ANSI select statement with join elimination. Fix remove because it has dependencies that can not be handled in a bundled patch. Bug 5874989 DATAPUMP: Datapump import can cause data corruption (data which exceeds its maximum size) after import with character set conversion. No error is signalled during the import, but ORA-7445 [kdstsrp0km] may be returned when creating an index on it or performing the query against the table. Bug 4440013 DATAGUARD: CRS startup of RAC fails when Fast Start FailOver (FSFO) is enabled. The alert log of the secondary instances will have ORA-16649 and the instance will have been shutdown aborted. Bug 4703814 DBCONTROL: NMO crashes with code 0xc0000005 when attempting to run / execute a job on Windows. Bug 6084823 HS: ORA-2070 deleting from a table using a where clause referencing a NVARCHAR column. Bug 6072906 ODP: CLOB Data is corrupted when selected using OLEDB with adUseServer. Bug 6273343 ODBC: SQLGetData() returns wrong number of bytes, for multi byte data. Bug 6354816 OLAP: Merge of OLAP fixes : Bug 6334646 / Bug 6195891 Bug 5934559 Bug 5689723 OO4O: Critical section is not released causing clients to hang. Bug 5081798 RAC: Additional diagnostics for ORA-600 [2103] when ASM is involved. Bug 5338035 RAC: DBCA fails with PRKR-1008 creating a database / adding an instance when the username and groupname of the Oracle user contains non-ASCII characters. Bug 4963729 RAC: Global hanganalyze can leak memory / signal ORA-600 [kghGetHpSz1] in a RAC environment. The memory leak has chunks of type "Blockers array api". Bug 6268598 RAC: ORA-600 [kjblocalobj_nolock:lt] and/or ORA-600 [kjsmesm:svrmode] can occur after applying the fix to Bug 5165885. Bug 5532110 RDBMS: Unpivot query can fail with ORA-600 [qcscpqbTxt] Bug 5452234 RDBMS: "GETS" column in V$LIBRARYCACHE can be wrong leading to reports of an incorrect hit ratio on the library cache. Bug 5631915 RDBMS: Spin can occur while selecting from X$KGLLK or its derivative views. (The spinning occurs in function kglLockIterator). Bug 5085288 RDBMS: ORA-600 [13013] generated by merge with update and delete clauses when another session simultaneously updates the target table. Bug 4309607 RDBMS: VARRAY data is not converted correctly as a result of type evolution (ALTER TYPE ... CASCADE will fail / ORA-600 [koputilcvto2n]). Bug 6315144 RDBMS: ORA-7445 [kkpamDInfo] from a select query on a partition table with a composite partition. Bug 6280961 RDBMS: OCCI application on RAC dumps core during instance failover. Bug 6276419 RDBMS: OCIAQLISTEN2 is not available for developing applications on Windows. Bug 5752105 RDBMS: ANALYZE TABLE VALIDATE STRUCTURE CASCADE ONLINE is slow after applying fix for Bug 4430244. Bug 6010833 RDBMS: Recovery following flashback does not utilize changes in online redo log. Bug 6001617 RDBMS: LCK0 consumes CPU Spinning on ksrbwait reading an ever increasing list of messages in "obj stat del channel" and holding "channel operations parent latch". ORA-4031's are also possible as messages are stored in the shared pool. Bug 4430244 RDBMS: Segment advisor code (eg: DBMS_SPACE.OBJECT_GROWTH_TREND) can load blocks into the cache for dropped objects as CURRENT, leading to subsequent operations seeing an incorrect (old) version of a block. This can lead to related errors such as ORA-600 [kcbnew_3] / ORA-600 [kcbz_check_objd_typ_3]. Bug 5017909 RDBMS: V$SQLAREA.SQL_FULLTEXT / V$SQL.SQL_FULLTEXT can contain an incorrect / corrupt SQL statement in a multi byte database. Bug 5471994 RDBMS: LCK may accumulate CPU time and and hold the "channel operations parent latch" when SMON does serial transaction recovery. Bug 4605569 RDBMS: In some circumstances on a RAC cluster the LCK0 process in one instance starts consuming a large amount of CPU effectively spinning in ksrbwait. Bug 5097326 SPATIAL: NLS_TERRITORY=GERMAN causes problems with numeric representatiion. Bug 5671929 SPATIAL: Large memory allocations when using SDO_GEOM.RELATE Bug 5350590 TEXT: CTX_DOC.MARKUP could fail with ORA-2000 and no further Text errors in the case of illegal characters in the document. Bug 5710143 TEXT: CTX_DOC.MARKUP highlights the wrong Thai and Japanese characters. Bug 5437241 XDB: ORA-7445 can occur while accessing XML DOM documents in a PL/SQL table in a call, other than the call which created the documents (using dbms_xmldom package functions). 10.2.0.3.0 Patch 10 (10.2.0.3.10P) 32-Bit Patch 6344567 64-Bit (Itanium) Patch 6344568 64-Bit (x64) Patch 6344569 BaseBug Abstract Bug 6009358 AQ: Memory leak in Q000 process when streams is running. Bug 5962680 AQ: ORA-7445 [kwqicgsubname1] may be raised on enqueue call. Bug 5452715 AQ: ORA-600: [kwqbgqc: bad state] is reported on an enqueue for single consumer buffered Queue, after a restart of a database. Bug 5960268 CBO: ORA-7445 [kkoiodoi] from query using bitmap index. Bug 5670294 CBO: ORA-07445 [qknviAllocate] error can occur during select, when star_transformation_enabled=TRUE. Bug 5397482 CBO: Star transformation can produce wrong results in presence of the fix for Bug 4728348 if a transitive join predicate can produced for join between 2 dimension tables. Bug 5169247 CBO: ORA-7445 [qkarid] on SELECT ... FOR UPDATE. Bug 5113934 CBO: ORA-7445 [qerixGetKey] from query with a parallel plan using a bitmap index access, typically from a star transformation. Bug 5842961 CBO: ORA-7445 [kkqjpddic] executing a query. Bug 6041535 CBO: Wrong results are possible if a query has a UNION ALL that undergoes join predicate pushdown and the fix to Bug 5302124 has been installed. Bug 5746682 CORE: During a write of flashback logs the database might generate an ORA-600:[krfw_blkmap1] on x64 platform. Bug 5407480 DV: AQ calls fail with insufficient privileges (ORA-1031) errors, when the Database Vault option is enabled. Bug 6147148 DV: Certain SQL queries throw a 'no data found' error when executed with the Database Vault option enabled. Bug 5870738 DV: GATHER_STATS_JOB raises ORA-1031 for DVSYS objects. Bug 6065183 JAVAVM: ORA-7445 / Core dump in AccessControlContext methods. Bug 6085754 ODBC: Driver reports memory leak calling stored procedure multiple times. Bug 5620504 ODP.NET: ORA-923 using case statement and dataadapter.fill. Bug 5951091 OID: Multiple EUS connects crashes oracle.exe in sgsluuiinit. Bug 5971606 OLEDB: Clob data truncated : UTF8 DB,CUR=ADOPENSTATIC,LCK=ADLOCKBATCHOPTIMISTIC Bug 5639774 OLEDB: Error messages are masked when executing "openschema" against a down database. Bug 5589819 OLEDB: Access Violation in oraoledbrst10 executing a query with schema table and pseudo column. Bug 5732149 OLEDB: Accessor is not a parameter accessor with number and math. Bug 6017614 OO4O: Access violation occurs in DLL_PROCESS_DETACH. Bug 5920360 OO4O: Runtime error occurs when using enlist MTS option under COM+ transaction. Bug 5982749 PLSQL: Native compilation might fail with PLS-923 : native compilation failed Bug 5637147 PLSQL: TRUNC of a TIMESTAMP is rounded instead of truncated. Bug 6074454 RAC: Service resource doesn't become offline when VIP fails over. Bug 5442534 RDBMS: ORA-7445 [kokscold] may occur if DML is attempting to assign null to CLOB. Bug 5527753 RDBMS: Enterprise Security Manager GUI tool raise exception when accessing the enterprise role, which is created by ESM command line tool. Bug 6207959 RDBMS: *_UPDATABLE_COLUMNS family of views was not maintained correctly when using the transparent data encryption feature (TDE). Bug 5944121 RDBMS: ORA-600 [kghufree_06] when using collections with elements that have non-final types. Bug 6158287 RDBMS: Executing a parallel query with an EXISTS subquery which accesses columns from the outer query block under a different DFO can return wrong results. Bug 6057203 RDBMS: ORA-1551 or ORA-600 [kcbchg1_6] may be raised during parallel query update (array update). Bug 6128197 RDBMS: ORA-600 [kcrfr_resize2] can occur during recovery if the redo log was generated in earlier versions. Bug 6085625 RDBMS: Wrong child cursor may be executed which has mismatching bind information to the binds issued by the client. This can lead to various errors such as ORA-1483. Bug 6163785 RDBMS: Intermittent Wrong Results on a query that uses a database link and its literals are replaced by CURSOR_SHARING = {SIMILAR|FORCE}. Bug 6317851 RDBMS: Signal 11 IN SQL Execution. Bug 6069409 RDBMS: ORA-979 (not a Group By expression), when NLS_COMP is set to LINUISTIC and a subquery is present in the group by query. Bug 5987000 RDBMS: ORA-600 [qkxrPXformQbc1] from "with" clause query. Bug 5880921 RDBMS: In certain situations, the time displayed from v$sysmetric_history is in the wrong time zone. Bug 6017420 RDBMS: Oracle instance can crash (typically starting with ORA-600 [kcbo_link_q_1]). Bug 4582210 SPATIAL: Local partitioned spatial index fails on Transportable Tablespace import. Bug 5983683 XDB: ORA-600 [17182] / Core dump on commit, on createResource / deleteResource in XA transactions. Bug 5324773 XDB: Constraint checks involving LTRIM() fail (ORA-2290) for valid data. Bug 5735091 XDB: Memory corruption when using xmlagg. Bug 4486516 XDB: Nested xmlaggs with gby crashes in koke2. Bug 4892567 XDB: dbms_xmlparser does not validate an xml document correctly against a dtd correctly. 10.2.0.3.0 Patch 9 (10.2.0.3.9P) 32-Bit Patch 6215383 64-Bit (Itanium) Patch 6215384 64-Bit (x64) Patch 6215385 BaseBug Abstract Bug 6016075 CBO: Wrong Results for query with correlated subquery and predicate pull up. Bug 5889331 CBO: ORA-7445 [kkfies] errors are possible during optimization of INSERT..SELECT statements if cost-based query transformations are used and functional indexes are present. Bug 5972794 DATAPUMP: Export over a network link with parallel > 1 fails with KUP-4038 internal error: kupax-meta1. Bug 6132986 DBCA: Incorrect OID entry during database registration. Bug 5258410 JAVAVM: ORA-7445 [eoscan_joe_stack_seg] when application uses Java threads. Fix re-included as the 10.2.0.3.0 Patch 2 fix was not built correctly. Bug 5691585 JDBCTHIN: getProcedureColumns return extra rows when the procedure takes an ADT or a collection parameter. Bug 5128512 ODBC: Fetching a number value which is converted to SQL_C_CHAR returns zero. Bug 5734069 ODBC: Wrong DLL picked by SHIPIT Bug 5598828 ODP.NET: ORAOPS10W calling the COINITIALIZE on a thread that it didn't create, causes a leak. Bug 5739350 OLAP: System error XSRS64UPDATEINDEX01 during EIF import. Bug 6164538 OLAP: Cannot export AW to EIF after 2 EIF imports an assignment. Bug 5101615 OLEDB: ORA-936 with * and multiple inner joins Bug 4018739 OLEDB: Testing OLEDB connection on 64 BIT Windows results in Windows handle (Bad Value). Bug 6068126 PLSQL: ORA-600 [15419], ORA-6544 [78402], ORA-1001 or ORA-7445 [pevm_INSTC2] passing ref cursor via IN OUT or OUT parameters. Bug 5334661 RAC: ocssd.logs refer to "undefined nodes". Bug 5454831 RDBMS: Deadlocks may be observed involving working set latches. Fix included in 10.2.0.3 patch 6 was removed because it caused regressions. Bug 6017420 RDBMS: Oracle instance can crash (typically starting with ORA-600 [kcbo_link_q_1]). Fix is listed in readme but is incomplete. Bug 6110331 RDBMS: Instance crash ( PMON fails with ORA-600 [kcbget_37], ORA-600 [1100], looping in kcbzchkpin) or hangs waiting on cache buffer chains latch. Bug 5147006 RDBMS: DML error logging fails when schema / table /column identifiers contains lower case characters. Bug 5956127 RDBMS: Global role created by ESM command line is not visible with ESM GUI. Bug 5175364 RDBMS: Data truncation / NULL data while fetching from NCHAR / NVARCHAR2 columns of more than 191 bytes long using TG4MSQL. Bug 5759075 RDBMS: Wrong results from Parallel Query with HASH on ANSI CHAR join. Bug 6156762 RDBMS: When reading multiple scalar values in OCCI, subsequent scalar values can be returned incorrectly. Bug 5683652 RDBMS: Poor performance from OCI client applications calling OCIHANDLEFREE. Bug 5753629 RDBMS: Repeatedly executing a query can lead to ORA-7445 [kpopfr]. Bug 5549410 RDBMS: OCILobRead() may not consistently returns the number of characters read when called for fix-width client character set. Bug 5636728 RDBMS: After shrinking an ENABLE STORAGE IN ROW LOB column, attempting to read the LOBs can return ORA-1555. Bug 5120780 RDBMS: EXP / EXPDP fails with ORA-6502 PL/SQL numeric or value error when exporting a scheduler job with a long program name. Bug 4927753 RDBMS: GRANT and ALTER USER statements may hang indefinitely (stack kzdspi kzppsr gradrv). Bug 5765958 RDBMS: ORA-600 [qcsfbdnp:1]/[qcscpqbTxt] with join query having local variable. Bug 5130732 RDBMS: Query using "WITH" clause can fail with ORA-942. Bug 5686711 RDBMS: Wrong cursor may be executed if schemas have objects with same names and users have permissions on the other schemas objects. Bug 6038412 RDBMS: OCI7 clients using "CALL" SQL may execute the wrong shared cursor and thus execute code in the wrong schema. Bug 5985594 RDBMS: Wrong results returned from query using "OR" with shared expressions. Bug 4899479 RDBMS: Redo / undo corruption and associated core dumps / ORA-600's can occur from a transaction which uses the "in memory undo" pool memory if the transaction also includes distributed operations. Bug 6036151 RDBMS: Query with predicate not lnnvl (or some combination thereof) crashes (ORA-7445 [_qctcopn]). Bug 5022127 RMAN: Catalog re-sync fails with RMAN-20098. Bug 5118210 SPATIAL: Insert as Select fails with ORA-600 [KOPUIGPFX1] when table contains triggers and SDO_GEOMETRY columns. Bug 6087105 SPATIAL: SDO_LRS.OFFSET_GEOM_SEGMENT returns Null Values for several geometries. Bug 6038442 SPATIAL: Wrong results from SDO_GEOM.SDO_INTERSECTION. Bug 6027858 SPATIAL: SDO_RELATE returns wrong results. Bug 5581472 STREAMS: Capture process may generates excessive I/O requests during periods of low or idle redo generation. Bug 5274156 TEXT: ORA-600 drexuAnalyzeQuery running select statement. Bug 4563159 XDB: SYS_XMLAGG fails with ORA-24347 for NULL columns. 10.2.0.3.0 Patch 8 (10.2.0.3.8P) 32-Bit Patch 6116131 64-Bit (Itanium) Patch 6038242 64-Bit (x64) Patch 6116139 BaseBug Abstract Fixes included for Critical Patch Update - July 2007 (Note 432865.1 / Representative Bug 6079615 / MLR Bug 6079591) 10.2.0.3.0 Patch 7 (10.2.0.3.7P) Only available in 32-Bit Patch 6038241 64-Bit (x64) Patch 6038243 BaseBug Abstract Bug 5640593 AQ: ORA-600 [kwqbmcrcpts101] can occur in queue slave during spill or ORA-600 [kwqbdrcp101] in job process during propagation, after a drop propagation. Bug 5523578 AQ: dbms_aqadm.add_subscriber() may return ORA-1925 / ORA-28031 for some users that have a lot of roles granted to them. Bug 5571643 ASM: SMON fails with ORA-600 [kfclAttachBuffer10] after getting ORA-27545. Bug 5757752 ASM: DBW0 in an ASM instance can fail with ORA-600 [kfcbCkpt04] when the disk group is mounted in multiple instances. Bug 5580497 CBO: Query involving tables with composite indexes can fail with memory access violation error (kkeais). Bug 4664788 CBO: ORA-7445 [kkqudhus] with kkquhcus above it in the stack trace. Bug 4683638 CBO: ORA-600 [nsoexc] raised from CREATE TABLE AS SELECT (CTAS). Bug 4684209 CBO: Running a query against a view where the execution plan includes a transitive predicate generated from a CHECK constraint can fail at execution time with a Core Dump / ORA-7445 under an eva* function. Fix was previously mistakenly listed as fixed in 10.2.0.3 patch 1. Bug 5961654 CORE: LdiInterFromTZ returns wrong offset during DST fallback Bug 5292551 DATAPUMP: IMPDP is very slow when importing a table with a column of type VARRAY. Bug 5910237 DATAPUMP: ORA-39083 failure to import nested table when row movement is enabled. Bug 5870523 DATAVAULT: ORA-1031 when using AQ on Data Vault. Bug 6042995 INTERMEDIA: IMG-705: unsupported or corrupted input format error when processing MONOCHROME1 DICOM Image. Bug 5892966 JDBC: No columns obtained when includeSynonym=true when a synonym is defined for a table. Bug 5962344 LOGMINER: Mining logs causes a buffer overflow that corrupts the stack leading to an access violation. Bug 5860680 NET: Oracle client module ORANL10 calls COINITIALIZE but leaves a hanging reference. Bug 5970288 OCCI: Checking embedded null objects in OCCI with isNull() can return incorrect results. Instant Client version of this fix. Bug 5956137 OCCI: Can not create POBJECT derived class instance on the stack. Bug 4519067 ODBC: Multi threaded applications may access violation when a query contains comments (select /*comment*/ ...) Bug 5747525 ODBC: Installation mapfiles are pointing to the odbc/translation directory for picking up sqresus.dll. Instead it should point to odbc/bin directory. Bug 5115926 ODBMIG: Support for cloning XE database to EE (Enterprise Edition) Bug 5638080 RDBMS: Query returns records out of the expected order when using a combination of with subquery factoring and analytic functions. Bug 5165885 RDBMS: ORA-600 [kclcls_8] during Star Execution test. Bug 5527665 RDBMS: ORA-600 [kcbkzx_3] or ORA-600 [kcbkzs_6] when flushing the buffer cache. Bug 5173642 RDBMS: Second execution of a query on a bigger object takes almost same time when NUMA optimization is enabled for cache. Bug 5181547 RDBMS: After executing a merge statement with insert clause only, a query that uses the unique index to access the table, may incorrectly return fewer than the actual number of rows in the table Bug 5753801 RDBMS: Orakill doesn't kill the shadow thread spawned through local/bequeth connections. Bug 3748430 RDBMS: I_*PART$, I_*PART_OBJ$ should be created as unique indexes. Bug 5008674 RDBMS: Rewrite fails with ORA-600 [kkqsfcsi-1] partial text match on MIN and MAX. Bug 4904904 RDBMS: Jobs that run a program which has metadata arg Job_start fail with ORA-1877: string is too long for internal buffer. Bug 5292883 RDBMS: ORA-7445 memcmp, kpzgkvl, kziaia, kpolnb, kpolon when client is using olog to connect to the database. Bug 5893779 RDBMS: Wrong results or a core dump can occur when server side prefetch is enabled and active. Bug 5758870 RDBMS: ORA-3135 after pulling out the network cable in select type failover. Bug 6029647 RDBMS: ORA-12714 reurned when accessing a TABLE function and typed coulmn in collection expression. Bug 4686909 RDBMS: ORA-1482 returned by convert function when used anywhere except a select list. Bug 5940550 RDBMS: Repeated connection / disconnection causes memory leak on Windows x64. Bug 5882947 RDBMS: Incomplete stack dumps on Windows x64. Bug 6011024 SPATIAL: SDO_GEOM.RELATE with 'determine' mask returns unknown mask. Bug 5871002 SPATIAL: SDO_TOPO_GEOMETRY constructor fails on versioned topology. Bug 5327658 STREAMS: Logical Standby Apply is slow when applying a single transaction with very large number (millions) of DMLs. Bug 5618295 TEXT: CTXDOC.FILTER shows part of the text duplicated in the result. Bug 4562807 TEXT: Gisting corrupted documents may return ORA-600 [kole_t2u]. Bug 5415594 XA: During RAC failover, DTP service could be allowed to start too early, resulting in missed prepared transactions. This could result in transactions getting "stuck" in prepared state or in xa_commit returning XAER_NOTA (-4). Bug 5920672 XDB: DBMS_XMLDOM ignores xml:space="preserve". 10.2.0.3.0 Patch 6 (10.2.0.3.6P) 32-Bit Patch 6012742 64-Bit (Itanium) Patch 6012743 64-Bit (x64) Patch 6012743 BaseBug Abstract Bug 5529797 AQ: PGA leak may occur in job queue process during streams propagation, with a subsequent ORA-600 [KWQPCBK179]. Bug 5574966 CBO: Core dump / ORA-7445 / ORA-3113 possible with push of join predicate involving virtual column into a view. Bug 5606145 CBO: ORA-7445 [QCTPRM] during compilation for IN subquery, that is a set (e.g. MINUS) query block. Bug 4605810 CBO: Index may not be chosen to eliminate ORDER BY SORT. Bug 5939115 CBO: ORA-600 [kghstack_underflow_internal_1] [pcols in kkpapDASQuerySLvl] were possible during the parse of queries with partitioned tables, if subquery partition pruning was attempted but the construction of the subquery failed. Bug 4899105 CBO: Multi table join can return ORA-600 [19004], if some of the join columns have histograms. Bug 5001547 CBO: ORA-7445 [kkoVerifyBindEquivalence] / Instance Crash Bug 5023743 CBO: ORA-7445 [kkqucpon] / Core dump Bug 5854634 CBO: Query with connect by may return ORA-600 [qkshtQBGet:1]. Bug 5573896 CORE: DCD does not work when the time is set to more than one minute. Bug 5759876 DATAGUARD: DMON may fail with ORA-7445 [rfm_get_chief_lock] causing the broker to fail to start. Bug 5399901 DATAGUARD: May spend long periods of time scanning the entire set of archived log entries for gap determination. Bug 5152232 DATAPUMP: When a table with a domain index is exported, EXPDP may lose the global parameters used in creating the local domain index (partitioned local domain index). Bug 5464834 DATAPUMP: ORA-4030 [kxs-heap-c,temporary memory] / unable to choose cost base optimizer for metadata in datapump job. Bug 4659157 JDBCTHIN: Some of the WE8MSWIN1252 characters are not inserted properly, causing ORA-942 on select. Bug 5470375 NLS: CHARACTERCONVERTER does not have TOUNICODECHARS like TOUNICODESTRING. Bug 5757315 NLSRTL: Loop when comparing 2 strings (VARCHAR2) using a monolingual sort method (NLS_SORT=XCZECH). Bug 5202103 ODBC: Re-Executing a query without re-parse on a Read Only connection returns incorrect / old data. Bug 5389003 ODBC: 10.1.0 / 10.2.0 Driver does not round off Double Data if the connection is to a 10.x Database. Bug 4555147 OSS: NZUMALLOC wil never return an error in function NZOS_FETCHCRL. Bug 5910731 PLSQL: Calling a stored procedure that calls a MULTISET function on two nested tables may fail with ORA-7445 [_pfsadt+40]. Bug 5890966 PLSQL: Sometimes, access to package-level associative arrays will incorrectly give ORA-6502 [associative array shape is not consistent with session parameters] errors when NLS parameters are being modified at the session level (even if such modifications do not impact associative array collation order.) Bug 5735768 RAC: When one node fails, the CRSD daemon on the surviving nodes may core dump or crash because OCR did not process a key operation request. Bug 4930431 RAC: During cluster startup, a problematic node (failed CSSD) could hang the whole cluster. Bug 5964083 RAC: VIP repeatedly fails over and fails back when LAN-PORT of PUBLIC-LAN is disabled. Bug 5245451 RDBMS: ORA-904 can sometimes be raised intermittently when referencing a remote object's columns in a database version below 9.x.x. Bug 5045992 RDBMS: SQL statement may fail with ORA-600 [kxspoac : EXL 1] when executed by a parallel execution slave when that SQL statement has numeric binds. Bug 5907779 RDBMS: Process may hang with a self deadlock typically when executing DBMS_STATS. The hung process shows itself waiting on a "cursor: pin S wait on X" waitevent waiting for an object that it has pinned itself. Bug 5115882 RDBMS: UPDATE .. RETURNING .. can return the wrong values into the "returning" variables if there is a BEFORE UPDATE FOR EACH ROW trigger which updates the :NEW values of the columns. The value from before the trigger fires is returned instead of the actual value used when the row is updated. Bug 5961454 RDBMS: DML operation may return ORA-29861, if a partition maintenance operation is performed at the same time as the DML on a different partition. Bug 5514109 RDBMS: It is possible for sessions to fail with unexpected ORA-955 or ORA-600 [kql-hash-collision] errors if two objects exist with very similar names in similarly named schemas. Bug 5454831 RDBMS: Deadlocks may be observed involving working set latches. Bug 5605370 RDBMS: Various core dumps / ORA-600 errors and ultimately an instance crash can occur as data may have been freed by another process. Bug 5973217 RDBMS: Fractional second precision is taken as N instead of M, when an object is created in OCCI and flushed to the table (object type table with an "INTERVAL DAY(N) TO SECOND(M)" attribute). Bug 5058318 RDBMS: Memory leaks with a UROWID instance inside a OCIAnyData structure. Bug 5970288 RDBMS: Checking embedded null objects in OCCI with isNull() can return incorrect results. Bug 5513561 RDBMS: OCI.DLL may change the dll loading search path even if ORACLE_HOME was not set in the environment. Bug 5352587 RDBMS: Columns assigned a value via a DML trigger may be incorrect or the trigger may fail with ORA-600 [1407] if the datatype of the column is timestamp. Bug 5640904 RDBMS: ORA-7445 [kcsgrsn()+320] / Core dump may be encountered while dumping redo of buffers in the pinned buffer history especially when the session has encountered an error condition earlier. Bug 5455880 RDBMS: Excessive recursive query on TS$ when using a "tablespace group" as temporary tablespace. Bug 5837795 RDBMS: Executing a connect by query with a table join, can produce wrong results or returns an ORA-600 at [sortgetqb]. Bug 5952123 SPATIAL: EPSG method 9812 a slight change to the formula. Bug 5770059 STREAMS: Required checkpoint SCN from DBA_CAPTURE view can take too long to display or it may provide an incorrect value. Bug 5881229 STREAMS: Reduced Audit Vault capture performance. Bug 5575674 STREAMS: Capture parameter _ignore_transaction does not correctly eliminate transactions that are rolled back at the source. Bug 5470592 TEXT: ORA-7445 in drsparAbsoluteURL() while indexing a URL that redirects to an https site. Bug 5471712 XDB: updateXML() may fail with ORA-31067 when XML text included unescaped general entities. Bug 4424952 XDB: EXTRACTVALUE returns wrong results. Bug 4515075 XDKCPP: C++ parser using SAX, may core dump while trying to access attributes. 10.2.0.3.0 Patch 5 (10.2.0.3.5P) 32-Bit Patch 5946186 64-Bit (Itanium) Patch 5946187 64-Bit (x64) Patch 5946188 BaseBug Abstract Bug 4733582 AQ: Stats on AQ tables are locked and deleted when upgrading to 10.2 (A1001000.SQL). Bug 5893614 ASM: Table scans are very slow on ASM, not on File Systems. Bug 5385629 CBO: Query containing inline view allows join-predicate pushdown ("VIEW PUSHED PREDICATE" or "UNION ALL PUSHED PREDICATE" appears in plan), but if the inline view is replaced with a reference to a view (with the same definition), join-predicate pushdown is no longer chosen. Bug 5382842 CBO: ORA-600 [qctcte1] can occur cost-based transformation is enabled when query contains a nested subquery. Bug 5371149 CBO: Connect by queries which include a nested connect by query and subquery with a correlated column in the start with predicates, may fails with ORA-600 [QCTCTE1]. The failure does not happen when the cost based transformation for connect by is disabled. Bug 5199213 CBO: Query with union all view may appear to run forever due to poor plan if there is a constant filter pushed inside the set query block. Bug 5128368 CBO: ORA-7445 [kkoeqv] from query with many nested views and one of the inner view predicates references a column from the outer blocks. Bug 5126645 CBO: ORA-600 [kkqcscorcbk: correlated string n] from query with connect by. Bug 4204383 CBO: ORA-7445 [kkqtnlocbk] / Core Dump can occur during optimization of ANSI outer joins with subqueries. Bug 5864217 CBO: ORA-600 [kkoljt] can occur in ANSI select statement with join elimination. Bug 5707754 CBO: ORA-3113 / Oracle.exe crash when executing very large query (stack overflow on Windows, stack shows apaqbd or kkqvmTrMrg, vopqbc in 10.1 and 10.2). Bug 3140249 DATAGUARD: Broker hangs when standby listener is down. Bug 4254868 NET: LDAP naming using Active Directory loops when trying to lookup a invalid name. Bug 5561244 ODBC: SQLGetConnectOption (SQL_ATTR_CONNECTION_DEAD, ...) fails with access violation. Bug 5617238 ODBC: Driver may crash, on executing a query (SQLExecDirect) where the length passed equal to number of characters excluding terminating null character. Bug 5943671 OLAP: Optimization when MEASDIM is on a page. Bug 5882816 OLAP: ALIASLIST Command does not work. Bug 5066528 PLSQL: DBMS_TRACE.SET_PLSQL_TRACE causes various non-exception related rows to be inserted in the table PLSQL_TRACE_EVENTS. Bug 5721941 RDBMS: Additional diagnostic trace is now produced when an ORA-600 [kgmgchd1] is raised. Bug 5648872 RDBMS: Intermittent ORA-7445 [OPIDSA] when describing a cursor. Bug 5095815 RDBMS: DRG errors stating column is not indexed, select from view with UNION ALL / CONTAINS (in spite of predicate of pushdown we are unable to do domain index scan). Bug 4634662 RDBMS: ORA-600[kolaslGetLength-1] selecting from V$SQL on a RAC database with varying width character set. Bug 5755471 RDBMS: Upgrade of a database which was originally created in Oracle with a different word size to 10.2.0.3 fails with ORA-600 [22635]. Bug 4932527 RDBMS: Processing of nested objects causes a core dump in kopp2atsize (client side PL/SQL). Bug 5892355 RDBMS: ORA-600 [22635] may be encountered when upgrading. Bug 5206570 RDBMS: Using Oracle SQL Developer it is possible to get a Core dump in ksusrs() or kprball() when disconnecting after the session has been marked as sniped due to idle time limitation. Bug 5841624 RDBMS: ORA-600 : [kokeicadd2] when dereferencing a object containing embedded, substitutable attributes. Bug 5871314 RDBMS: Pickler does add Null values in Image for KOTT* when pointer is Null. Bug 4447712 RDBMS: DML does not execute in parallel within an autonomous transaction. Bug 4695511 RDBMS: ORA-600 [kxfqupp_bad_cvl] can occur when creating bitmap index on a large table in parallel Bug 4686006 RDBMS: ORA-600 [kkqsaljg:nobjs is 0] can occur with a view with an exists and a having clause. Bug 5084757 RDBMS: ORA-600 errors executing explain plan in VPD. Bug 5386204 RDBMS: ORA-600 [KDDUMMY_BLKCHK] with code 18038. Bug 5345571 RDBMS: Expressions are mistakenly removed from the operand list from one of the select statements in a union which leads to invalid union operations / wrong results. Bug 5847521 RDBMS: Connect by queries on index-organized tables with sub-queries in the START WITH clause may produce incorrect results. Bug 5119354 RDBMS: ORA-600 [qkacon:FJswrwo] / Incorrect results from queries with connect by clauses and correlated columns in the start with predicates. Bug 5254539 RDBMS: SQL statement involving hierarchical query using cursor statements in select list may return ORA-600 [qkacon:FJfsrwo]. Bug 5743792 SPATIAL: LOAD_TOPO_MAP can not be called multiple times in the same transaction. Bug 5840592 SPATIAL: SDO_LRS.OFFSET_GEOM_SEGMENT returns null values. Bug 5390154 TEXT: Optimizer may choose a suboptimal execution plan for internal SQL used in SYNC_INDEX when the empty base table is analyzed. As the result, SYNC_INDEX can take an unexpectedly long time to lock base table rows. Bug 5947653 XDB: XE to Enterprise Edition fails in XDB phase. Bug 5437716 XDB: No rows returned with multiple subqueries against the same nested table (XML Table Operators). Bug 5392772 XDB: SQLX query returns corrupt XML output (SQL/XML data corruption). Bug 5477912 XDB: Memory leak, if DTD is parsed with in a loop and freeDocType is not called. Bug 5668025 XDB: xmlparser.parse() functions may leak memory when called without getDocument and freeDocument. Bug 5253806 XDB: PL/SQL dbms_xmldom transformation functions, should stream the output for non-xml output types. Bug 5667235 XDB: New overloaded procedure ProcessXSL is introduced. This has an OUT Boolean to indicate if the style sheet output method is XML or not. Bug 4967236 XDKC: ORA 600[17282] while performing data import. 10.2.0.3.0 Patch 4 (10.2.0.3.4P) 32-Bit Patch 5948242 64-Bit (Itanium) Patch 5916262 64-Bit (x64) Patch 5948243 BaseBug Abstract Fixes included for Critical Patch Update - April 2007 (Note 420055.1 / Representative Bug 5901923 / MLR Bug 5901891) 10.2.0.3.0 Patch 3 (10.2.0.3.3P) Only available in 32-Bit Patch 5916257 64-Bit (x64) Patch 5923281 BaseBug Abstract Bug 5686412 CBO: Queries using functional indexes may Core Dump / ORA-7445 [evaopn2] when executed where there is a functional index inlist in the plan. Bug 5667683 CBO: PQuery using a bitmap index may spin in kkosbn(). Bug 5487686 CBO: SQL involving a CONNECT BY can produce wrong results with cost based connect by enabled if the SQL has a filter pushed inside a union all branch with a connect by operation. Bug 4712638 CBO: Parse of a SQL statement may Core Dump / ORA-7445 [kkogbro] or signal ORA-600 [15160]. Bug 5022061 CBO: ORA-7445 [kkessc] is possible during the optimization of queries with inequality joins if index skip scan is considered. Bug 5117099 CORE: Access violation from sltmarm / sltmini -> timerQueue_sltmcx Bug 5871774 DBCONTROL: Remote operations (such as DB Shutdown / Startup, Host / SQL Jobs) fail without report valid errors on Windows Vista. Bug 5528974 DBCONTROL: MGMT Job packages appear invalid on installation. Bug 5871799 DBCONTROL: NullPointerException when clicking on Operating System details link for Vista targets. Bug 4269423 DBCONTROL: Creating a System using a multi-byte characters, the name becomes corrupted. Bug 5556081 DBCONTROL: Securing Database Control on Windows fails.. Bug 4722328 JDBC: Core dump executing a PL/SQL procedure with a CURSOR OUT parameter multiple times without re-creating the statement. Bug 4898580 MVIEW: DBMS_METADATA.GET_DEPENDENT_DDL() does not display comments on Materialized View columns correctly. It is displayed as a comment on the MView instead of on the column. Bug 4054238 MVIEW: Materialized views cannot be created (ORA-12899 ) if they contain complex aggregate expressions. Bug 5073249 MVIEW: Materialized View defined using the 'WITH ... AS' clause may crash / core dump after a fast fresh. Bug 5892178 ODBC: Driver reports error "Input string too long, limit 4096" on executing query containing token of length greater than 4096. Bug 5002155 OID: LDAP Dynamic discovery (Autodiscovery) fails (ORA-12154) using 10.2 clients. Bug 5325821 OSS: Computer hangs when creating or dropping a object / synonym that refers to a non existent database link. Bug 5899479 RAC: DBCA fails to discover Oracle Cluster Synchronization service (CSS) is already configured. Bug 4587572 RDBMS: APPSST102 :ORA-12801/ORA-00060 IS RAISED FOR PARALLEL DML Bug 5173642 RDBMS: Second execution of a query on a bigger object takes almost same time when NUMA optimization is enabled for cache. This fix was incorrectly built causing Bug 6035999, it will be re-included at a later date. Bug 5863277 RDBMS: ORA-1008 raised when using cursor_sharing=force/similar if the SQL also has user binds. Bug 5902261 RDBMS: When OCIEnvCreate() is called in InstantClient mode, the client will crash in LocalFree (on Windows Vista). Bug 4745114 RDBMS: ORA-600[kolrrdl-0rfc] freeing session duration temporary lobs before the end of the session. Bug 4966417 RDBMS: Various Core dumps / ORA-600 errors and ultimately an instance crash can occur when a session performs a rollback to a savepoint type operation. Bug 4592596 RDBMS: Corruption can occur using a multi-table insert SQL with direct load operations (e.g. if the SQL goes parallel). This can result in subsequent ORA-1410 type errors on selects from the target table/s. Bug 5444539 RDBMS: UPI calls in v8 mode (e.g. upiver) that encounter "ORA-1089 immediate shutdown in progress", may not release the server handle it acquired at the beginning of the session, causing applications to hang / fail to failover. Bug 5617311 RDBMS: ORA-01017 for proxy authentication of a globally identified user with Distinguished Name as the credentials and using JDBC thin / OCI drivers. Bug 4663793 RDBMS: Select on ALL_OBJECTS from a non-SYS user raises ORA-16224, if the database has Data Guard enabled (Logical Standby). Bug 4624183 RDBMS: ORA-1017 reported when using Database Links with Externally Identified accounts. Bug 5742678 RDBMS: Index Range Scan used to get Max value instead of index MIN/MAX First Row. Bug 4925103 RDBMS: SQL including a MAX() function can return a wrong result (NULL) if the execution plan uses "FIRST ROW" from an "INDEX RANGE SCAN (MIN/MAX)" and the column contains NULL values in addition to non NULLs. Bug 5900199 SPATIAL: ORA-29885 / ORA-29400 data cartridge error OCI_NODATA when attempting to create a spatial index. Bug 5596325 TEXT: Queries against indexes with more than 200 million documents can fail with "ORA-1410: invalid rowid" errors, or wrong results may be returned. Bug 5491132 XDB: xslprocessor.newStylesheet() fails when XSL document includes OS files.. Bug 5694997 XDKC: Add new API XMLXVMCOMPILEDOM that accepts BASEURI. 10.2.0.3.0 Patch 2 (10.2.0.3.2P) 32-Bit Patch 5846376 64-Bit (Itanium) Patch 5846377 64-Bit (x64) Patch 5846378 BaseBug Abstract Bug 3667025 ANO: In a windows 2003 cross-realm environment, if a user tries to login using his local Kerberos domain identity, to the remote database belonging to the remote Kerberos domain, the login fails. Bug 5723241 ANO: Kerberos cross realm authentication fails using Microsoft credential cache (osmsft), LsaCallAuthenticationPackage pkgStatus failed with status: -1073741429. Bug 5654680 AQ: Listener worker thread may hang if users' ONMESSAGE method raises an error. Bug 5580871 AQ: Unable to dequeue messages for bytes payload, using OJMS APIs for payload sizes <= 2K, if messages were enqueued using PL/SQL APIs and vice versa. Bug 5757752 ASM: ORA-600 [KGHSTACK_ALLOC] [KFCBCKPT SAVEDCE] from ASM. Bug 5555908 ASM: ORA-600 [KGHSTACK_UNDERFLOW_INTERNAL_2] from ASM. Bug 5554692 ASM: Block header invalid (ORA-15196) after ORA-600 [KFCGETBUFFER10]. Bug 5842576 ASM: During the "Select Configuration Option" of OUI, kfod.exe crashes. Bug 5246372 CBO: ORA-600 [OPIDSII] errors are possible when parsing distributed queries that use views defined across multiple database links. Bug 5299546 CBO: ORA-942 possible when create materialized view statement is executed with a join between remote and local tables. Bug 5690241 CBO: ORA-7445 (or wrong results) when a query contains an OR predicates on the partition columns. Bug 5060402 CBO: ORA-600 [12325] from view that queries ORA_ROWSCN. Bug 4380471 CBO: Rewrite of queries containing order by expression which is not in the select list will fail with ORA-600 [KKQSFCSI-1] during text match. Bug 5597046 CORE: OCIEnvCreate (SlfMmap) fails with ACCESS_DENIED error when run as a non-admin process. Bug 5718757 DATAPUMP: ORA-31693 / ORA-6502 during network import. Bug 5115926 DBMIG: DBCA template creation functionality now includes support for XE to EE migration / cloning. Bug 4864563 HS: Where clause removed from query sent to foreign database, when the where clause requires implicit data type conversion. Bug 5258410 JAVAVM: ORA-7445 [eoscan_joe_stack_seg] when application uses Java threads. Bug 5231687 JDBC: ORA-600 [kokeeiix3] while selecting an updated ADT which has evolved.. Bug 5660734 JDBC: Evolved type not updated properly in the database. Bug 5370578 LOGMINER: Capture process slow on startup, due to inefficient search algorithm coupled with a misuse of a read/write control file transaction. Bug 5472702 LOGMINER: Logical Standby or Streams Apply may stop with ORA-1403 while applying LOB changes (LOB WRITE, LOB TRIM or a LOB ERASE). Bug 5623403 LOGMINER: Streams capture fails with : ORA-26773 invalid data type from MALFORMED REDO. Bug 5214373 NET: 10.2.0.x Listener crashes due to memory fault in module ORANL10.DLL Bug 5860680 NET: Oracle client module ORANL10 calls COINITIALIZE but leaves a hanging reference. Bug 5604120 NLSDATA: Performance degradation after applying calendar deviation (calculations depending on Hijrah dates). Bug 4519067 ODBC: Process crash / Access Violation on executing query containing comments in multi-threaded mode. Bug 5376170 ODBC: Driver may report ORA-904 on executing query a containing a column name having blank spaces. Bug 5868135 OLAP: Error loading flat dimension with mapped attributes. Bug 5603293 OLAP: DML sort command kills OLAP Web Agent session. Bug 5746153 OLAP: Merge patch for Oracle OLAP including Bug 5326419 Bug 5384375 Bug 5614957 Bug 5436458 Bug 5753198 Bug 5684721 Bug 5762192 Bug 5141636 Bug 5574866 Bug 5355084 Bug 5850452 Bug 5507506 Bug 5572284 Bug 5676244 Bug 5361171 Bug 5413763 Bug 5510511 Bug 5551964 Bug 5470076 Bug 5360207 Bug 5347785 Bug 5344103 Bug 5336254 Bug 5190530 Bug 4480756 Bug 5764338 Bug 5757025 Bug 5703138 Bug 5700725 Bug 5360145 Bug 5578127 Bug 5620700 Bug 5642311 Bug 5604376 Bug 5639880 Bug 4689285 Bug 4455156 Bug 5700568 Bug 5652733 Bug 5326417 Bug 5357405 Bug 4482161 Bug 5415410 PLSQL: When a OCI application connects to the database with the environment variable ORA_DEBUG_JDWP set to initiate server-side PL/SQL and Java debugging, it may get an exception indicating that the ORA_DEBUG_JDWP value is improper even though it is proper. Bug 5389854 PLSQL: Execution of a procedure using bulk insert with save exceptions will consume large amounts of PGA memory during execution (ORA-4030). If run with an extremely large number of rows or for a long period of time. Bug 5168043 RAC: VIPCA returns : Invalid node name "<hostname>" entered in an input argument, if the node names supplied in VIPCA silent mode are uppercase. Bug 5760062 RAC: CLSSNMREADDSKHEARTBEAT error, ownership checks for undefined nodes are now skipped. Bug 5192194 RAC: CSS may not start "Takeover aborted due to unknown nodes". Bug 5845104 RAC: OPMD.EXE shipped in 10.2.0.3.0 on Windows AMD/EM64T fails to start the Oracle process manager services. Bug 5201883 RDBMS: 10.2.0.x Database generates redundant MMAN trace files containing "AUTO SGA: Not free 0x39cbe6e18, 1, 1, 1" text. Bug 5527665 RDBMS: Flush buffer cache fails with ORA-600 [KCBKZX_3] Or ORA-600 [KCBKZS_6]. Bug 5579055 RDBMS: ORA-7445 [KXCCRES] when trying to validate referential integrity constraints, while updating a view having instead of trigger. Bug 4969005 RDBMS: ORA-7445 / Core dump in KGLLOCKITERATOR Bug 5177766 RDBMS: Applications that require a large number of child cursors (with session_cached_cursors enabled) may fail with ORA-600 [17059]. Bug 5485914 RDBMS: Self-deadlock possible when Explain / Tracing remotely mapped statement. Bug 4726702 RDBMS: ORA-3113 / ORA-7445 [KOKTUPD_DPLVL] during ALTER TYPE due to ref dependency. Bug 5205552 RDBMS: On Windows x64 / EM64T the database consumes unnecessarily high memory due to incorrect thread stack sizing. Bug 5844903 RDBMS: Unable to start database on Dual Core Itanium machines. Bug 5618049 RDBMS: Repeated / Looping DDL on partitioned tables can cause ORA-4031 (a number allocations with the "comment "mvobj part des" will be observed). Bug 4865959 RDBMS: Java stored procedure returns exception / all row data is NULL except for the last row, when trying to fetch more than one row from a remote database. Bug 5051602 RDBMS: ORA-600 [17182] in kposcfree on execute of a select with duplicate column using scrollable cursor mode. Bug 5586253 RDBMS: While fetching rows from a remote table using DBMS_AW (OLAP), all rows may not be returned. Bug 5065418 RDBMS: Connect by without filtering option, may perform poorly or if the sort spills to disk may return less rows than expected. Bug 5509707 RDBMS: Wrong results are possible when table lookup by rowid used a prefetch child row source. Bug 5403855 RDBMS: Wrong results are possible with SQL_TRACE = TRUE and prefetch is active. Bug 4864581 RDBMS: ORA-600 [KKQTNLOP2CBK : 1] can occur parsing SQL with unnecessary parenthesis in the query. Bug 5751731 XDB: Oracle XE to Enterprise Edition upgrade fails with ORA-600 [qmxiUnpPacked2]. Bug 4959294 XDB: Data inserted with dbms_xmlstore.insertxml() may be corrupted on multi byte databases. Fixes included for Critical Patch Update - January 2007 (Note 403335.1 / Representative Bug 5901923 / MLR Bug 5901891) 10.2.0.3.0 Patch 1 (10.2.0.3.1P) 32-Bit Patch 5731535 64-Bit (Itanium) Patch 5731536 64-Bit (x64) Patch 5731537 BaseBug Abstract This bundled patch includes "version 3" of the Oracle Time Zone files and was re-released in February 2007 because the original README did not include instructions regarding how to correct pre-existing data. Please refer to Note 359145.1 followed by Note 415912.1 for further information. Bug 5439588 AQ: Notifications may not not be delivered to OCI clients where client machine has multiple Network Interface cards. Bug 5512415 CBO: Star transformation could cause wrong result for queries with EXISTS sub queries (semi join used as dimension). Bug 5403398 CBO: ORA-7445 / ORA-600's are possible during the costing of user-defined operators / functions. Bug 5240607 CBO: In first_rows_k mode the optimizer sometimes could choose inefficient Nested Loops with full scan on right side. Bug 4724074 CBO: Fix to substantially decrease in parse time for complex predicates can cause simple predicates to parse more slowly (re-computing the results is faster than the lookup). Bug 5607984 CORE: With DCD enabled the database may have a large number of hung threads performing timer related activity (close_wait state) and consume resources. Bug 5632264 CORE: Version 4 of the timezone files and including timezone rule changes for: Egypt, Brazil and Western Australia. Bug 5638228 JAVAVM: ORA-600 [17099] / Instance Crash when using JDBC XA in high load scenarios. Bug 5541589 NET: Outbound Connect Timeout with ADDRESS_LIST does not handle refuse correctly (no failover). Bug 5518312 NET: Small memory leak, when niotns fails (vpxoci). Bug 5549203 NET: Sqlplus consumes 100% CPU / Spins when OCTO (OUTBOUND_CONNECT_TIMEOUT) is set. Bug 5711282 ODBC: Executing query having token length greater than 4096 characters causes program to exit. Bug 5706095 RAC: Regression causing CRS Core Dump on Windows. Bug 5471453 RDBMS: ORA-29701 or CSS errors just prior to ORA-600 [kfkFilRqArr01] error in ASM environment Bug 5705795 RDBMS: SQL using bind variables with different bind sizes can lead to a large number of child cursors being created leading to excess shared pool usage and latch contention. Bug 5577046 RDBMS: Adding or dropping attributes into one of the object hierarchies causes subsequent union queries to throw ORA-1970 error after the fix for Bug 4990803. Bug 5548895 RDBMS: Datapump export of anydata rows fails with errors ORA-600 [OCIKCallPush: deprecated]. Bug 5397953 RDBMS: ORA-7445 [KKPAPITGETALL] / Access Violation when accessing a partitioned table using multicolumn in-lists. Bug 5558356 RDBMS: Describe information may be lost in statement handle. Bug 5560256 RDBMS: Multi-threaded OCI program may hang when OCILobLocatorAssign is called. Bug 5155885 RDBMS: ORA-600 [KKSLGBV0] / Segmentation Violation can occur accessing bind values while deciding to shared a cursor (cursor_sharing = similar) Bug 5093837 RDBMS: After running the "alter table shrink" command, blocks are filled with rows above the PCTFREE limit also. Precisely, PCTFREE is not considered when shrink reinserts rows. Bug 5029528 RDBMS: ORA-600 [QKACON:QKACONGETPATHOPS:1] for SQL statements using the SYS_CONNECT_BY_PATH function. Bug 5088977 RDBMS: Intermittent ORA-7445 [_KELTFILL+86] errors. Bug 5108234 RDBMS: 10.2.0.x per connection memory consumption higher than 10.1.0.x. Bug 5606847 SPATIAL: Creation of a Spatial RTree index can fail with ORA-29855 with valid spatial data. Bug 5451092 TEXT: Wrong characters highlighted by CTX_DOC.MARKUP(). Bug 5438110 TEXT: DRG-11513 "unable to open or write to file" creating a text index with multi byte filenames (filename_charset attribute for the file datastore has been added). Bug 5716932 XDB: ORA-7445 [INTEL_NEW_COPY] / ORA-7445 [17147] can occur with select from path_view if there are more than 16 ACEs in an ACL. Bug 4377659 XDB: Schema validation of XML Document which has >65536 nodes at one level fails with LSX-201. Bug 4877048 XDB: ORA-7445 [QMTMODELGETMCA] / Core dump registering XML schema using groups. Bug 5569805 XDB: Wrong results from XMLElement() with outer join on dual. Bug 5573534 XDKC: Memory Leak from XMLACCESS(). -------------------------------------------------------------------------------- 10.2.0.2.0 Patch 18 (10.2.0.2.18P) 32-Bit Patch 7213940 64-Bit (Itanium) Patch 7213941 64-Bit (x64) Patch 7213942 BaseBug Abstract Bug 5880921 AWR: Time inconsistency between V$SYSMETRIC_HISTORY and SYSDATE. Bug 6826661 CORE: Wrong data in NUMBER column for specific FLOAT values (SQLT_FLT). Bug 7168928 OPTIMIZER: Merge of optimizer fixes Bug 6618120 Bug 6740811 Bug 6819865 Bug 7021805 Bug 4878299 OPTIMIZER: Bad plan from join with FIRST_ROWS_N or a ROWNUM predicate. Bug 4567767 OPTIMIZER: Execution Plan changes upon rowcache reload. Bug 4724074 OPTIMIZER: Small CPU performance overhead during optimization. Bug 6660162 OPTIMIZER: The fix to Bug 5705257 introduces approximation of "not fully matched" equality only predicates using index NDK. This fix enhances that to also cover the case when the index key contains range predicates, equijoin. Bug 6626018 OPTIMIZER: Cost of filter operation computed as too low a value. Bug 6440977 OPTIMIZER: Redundant predicates are not recognized across a join. Bug 6316993 OPTIMIZER: Wrong results / ORA-600 [qernsRowP] from join back elimination of 1 row table. Bug 6251917 OPTIMIZER: Optimizer selects the merge join cartesian despite the hints. Bug 6239971 OPTIMIZER: Optimizer costing can differ greatly for =< compared to <. Bug 6120483 OPTIMIZER: Query with INLIST does not choose cheapest index (suboptimal plan). Bug 6062266 OPTIMIZER: It is possible for a query to get a computed cardinality of 0 for a range predicate on a column that has no histograms. Bug 5747462 RDBMS: Poor performance of 'analyze table ... validate structure cascade' on large tables with indices defined on them as compared to 9.x.x. Bug 6646613 RDBMS: Index Organized Tables (IOTs) created / updated with COMPATIBLE <= 9.2.0.8 which are subsequently used with Compatible >= 10.1.0.2 can become corrupt. The initial corruption does not show any external symptoms, but subsequent operations on a corrupt block can lead to noticeable corruptions and resulting ORA-600 [kcbgtcr_1] errors or core dumps. Bug 6870469 RDBMS: Real application testing (capture feature) support. Bug 7133360 SPACE: Merge of space management fixes: Bug 7022905 : Alter tablespace drop datafile completes with "tablespace altered" even if the datafile contains extents from different tables, leading to a corrupt database. Bug 5623467 : Alter tablespace drop datafile produces bad redo which typically does not then drop the datafile either during recovery or at a standby. This can lead to subsequent errors such as ORA-600 [3689] of subsequent redo tries to add new datafile. Bug 5076617 : ORA-3236 can occur attempting to drop a datafile using the "alter tablespace" command even though the datafile is not the first file. Bug 6159522 SQLEXEC: ORA-600 [qkaffsindex3] can occur during an ANALYZE TABLE command when query_rewrite_enabled is set to false. Bug 5895190 SQLEXEC: Wrong results are possible from a hash join outer with a hash semi join as an input. Bug 7001465 XDB: Bug 4765136 missing from Windows 10.2.0.2 patch set. 10.2.0.2.0 Patch 17 (10.2.0.2.17P) 32-Bit Patch 6731567 64-Bit (Itanium) Patch 6731568 64-Bit (x64) Patch 6731569 BaseBug Abstract Bug 6011182 CBO: High elapsed time and high memory consumption during parse can occur for queries with large numbers of query blocks (e.g. many views, subqueries or UNION ALL branches). Bug 6007259 CBO: OR expansion may not be chosen for a query even if it is cheaper. Bug 5882954 CBO: Very slow query plan computation for tables with a large number of partitions if histograms are used. Bug 5763245 CBO: Spins are possible during parse of queries using partitioned objects if there are potential multicolumn inlists against the partitioning keys. A stack trace of the spinning process will show kkpapRTPruningSetup() as the offending function. Bug 5718007 CBO: Session may spin (in qcopxla / qcopx0la) during parse of a query using partitioned objects if there are OR predicates (not an INLIST) using partition key columns. Bug 5131645 CBO: Noticeable degradation of hard parse compilation time for some queries after upgrading from a 9.x release to a 10.x release for SQL involving a number of tables. Stacks of the process show CPU use under appopd->qksfrochild. Bug 4708389 CBO: Nested Loops Join plan when outer table is serial, but inner index is parallel is costed as a serial plan which can lead to Hash Join being preferred. Bug 6077514 CBO: DBMS_STATS.GATHER_FIXED_OBJECT_STATS can be slow with large buffer cache. Bug 6350462 CBO: Scaling calculation for index statistics uses the wrong base (uses cardinality from the first_rows(k) statistics rather than from all_rows). Bug 6151963 CBO: Join cardinality based on histograms may be under-estimated. Bug 6147372 CBO: Column usage statistics are kept for in-memory temporary tables which can lead to data dictionary growth (COL_USAGE$ has been reorganiized). Bug 6087237 CBO: Query with OR chain chooses expensive HASH join instead of cheaper NESTED LOOPS with OR expansion. Bug 5117099 CORE: CORE: Access violation from sltmarm / sltmini -> timerQueue_sltmcx Bug 5573544 DATAGUARD: Trace files generated on DG primary by sqlplus sessions. Bug 4670363 DATAGUARD: Harmless message "LGWR: Archivelog for thread N sequence M will NOT be compressed" is continually reported even though no tracing is enabled. Bug 5399901 DATAGUARD: Archived log entries can take a long time to search when dataguard scans for gaps etc.. This can lead to CF enqueue contention. Bug 4367986 RDBMS: Parallel execution cursors are not shared when bind peeking is used. Bug 6086497 RDBMS: ORA-600 [ktspgetmyb-1] / bitmap segment corruption is possible on ASSM segments. Bug 6447320 RDBMS: Select on a partition will hang when shrink compact is being executed on it and will not complete until shrink compact is completed. Bug 6140309 RDBMS: ORA-600 [ktssupd_seg_2] can occur while running DBMS_SPACE_ADMIN.TABLESPACE_FIX_SEGMENT_EXTBLKS. Fixes included for Critical Patch Update - January 2008 (Representative Bug 6647086)) 10.2.0.2.0 Patch 16 (10.2.0.2.16P) 32-Bit Patch 6397028 64-Bit (Itanium) Patch 6397029 64-Bit (x64) Patch 6397030 BaseBug Abstract Bug 4733582 AQ: Statistics on AQ tables are locked and deleted when upgrading to 10.2 (in the script a1001000.sql). Bug 6321245 CBO: Merge request for the following Cost Based Optimizer fixes: Bug 5397482 CBO: Star transformation can produce wrong results in presence of the fix for Bug 4728348 if a transitive join predicate can produced for join between 2 dimension tables. Bug 5705630 CBO: Poor plans are possible for queries using OR-expansion if single table predicates can be extracted from larger OR chains. An EXPLAIN PLAN will show extra single table predicates generated from the OR chain being expanded. Bug 5709414 CBO: DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO takes a considerable amount of time running "delete from mon_mods*" or col_usage$ tables. Bug 5838613 CBO: Suboptimal plans are possible for queries with large numbers of tables if star transformation is chosen. e.g.: CARTESIAN product may be chosen where not the best choice. Bug 5842686 CBO: DBMS_STATS computes the wrong average row length for tables which contain a LONG RAW column which can lead to suboptimal execution plans. Bug 5944076 CBO: Poor plans are possible for queries in first_rows(k) optimization if index-only access is possible. Bug 5949981 CBO: Poor selectivity calculations are possible during optimization for predicates against columns with frequency histograms, if the constant value used matches a single-row histogram bucket. Bug 5976822 CBO: Poor estimates are possible for index access cost during nested loops joins, if the same index gives a single table access path and can also be used in the join with a join predicate as a key and dynamic sampling is used. Bug 5990716 CBO: Query using index join can core dump / ORA-07445 [evaopn2] - the wrong index gets chosen for the index join but the required columns are not part of the chosen index. Bug 6134565 CBO: FIRST_ROWS hint was not honoured when _sort_elimination_cost_ratio set to 10. Bug 6051211 CBO: Join cardinality is wrongly calculated for some cases for equijoins when histogram is present. Bug 6070954 CBO: Poor plans using index skip scan are possible where index range scan is preferable. This can occur if the index keys are a leading set of equality predicates. Bug 5381446 CBO: Core dump or wrong results can occur during execution of queries undergoing star transformation with temporary table transformations if an index join is used inside the temporary table load. Bug 5284303 CBO: Poor selectivity estimates are possible for predicates against character columns containing numeric data if the strings are more than six characters long. Bug 5172444 CBO: ORA-600 [15160] errors are possible during optimization of queries using star transformation if there are multiple single row tables, and joinback elimination is possible. Bug 5089444 CBO: ORA-7445 [kkodsel] from select with a subquery with star transformation. Bug 4772145 CBO: Gathering statistics on large indexes can be slow : If the index is either a concatenated index or a bitmap index with more than a few million rows in the base table and the index or index partition has more than a few hundred blocks and serial execution is forced by dbms_stats. Bug 6082745 CBO: Poor plans are possible for queries having predicates against columns with a single distinct value, if the predicate value does not match the column value and a patch which includes the fix for Bug 5483301 is installed. Bug 4372359 CBO: Wrong results are possible with a query doing star transformation and using temporary table transformation when join back elimination is used. The plan shows a join back eliminated table missing. Bug 4599763 CBO: DBMS_STATS may throw ORA-600 [qospgtbc] during statistics gathering. Bug 5941030 DATAPUMP: Direct Path import of a LONG / LONG RAW column can create corrupt blocks in the database. If DB_BLOCK_CHECKING is enabled then an ORA-600 [6917] error can be signalled. If not then the corrupt block can cause subsequent problems. Bug 5308692 LOGMINER: ORA-1426 can occur when running DBMS_STATS.GATHER_FIXED_OBJECTS_STATS. The error occurs when DBMS_STATS accesses the SCN columns for system.logmnr_log$ . Bug 5500044 RDBMS: Executing DDL on partitioned tables that have CLOB / BLOB columns might cause other sessions to block or fail with ORA-44203. Sessions block on 'cursor: pin X' and 'kksfbc child completion'. The 'cursor: pin X' is waiting on a pseudo cursor (a cursor with a name that starts with "table_") Bug 4969005 RDBMS: ORA-7445 [kglLockIterator] when querying certain V$ views which reference X$KGLLK such as V$open_cursors. Bug 5724540 RDBMS: ORA-1 errors could be incorrectly reported by clients during queries using subquery partition pruning. The error occurs due to kkpapiItOpen() reporting an ORA-0 error , which then gets reported as an ORA-1. Bug 6315913 RDBMS: ORA-3106 is possible from select statements after a failover with BLOB columns in RAC environments. Bug 5765361 SQLLDR: OCI clients may core dump using OCIDirPathPrepare in OCI_UTF16ID mode. 10.2.0.2.0 Patch 15 (10.2.0.2.15P) 32-Bit Patch 6013105 64-Bit (Itanium) Patch 6013118 64-Bit (x64) Patch 6013121 BaseBug Abstract Bug 5766310 CBO: The presence of frequency histogram can lead to low cardinality estimation and poor plan. Bug 5129407 CBO: Queries with multiple or-branches can get sub-optimal plans (the cost of the query with /*+use_concat*/ hint is lower, than without the hint). Bug 5884780 CBO: Query that uses a list-of-values table joined to a table, should be a candidate for star transformation, either the transformation is not done, or the list-of-values table is not used in a generated subquery. Bug 5966822 CBO: Merge of optimizer fixes for Applications vendor. Bug 5912195 CBO: Merge of optimizer fixes for Applications vendor. Bug 5680702 CBO: Poor plan is possible for queries using nested loops antijoin or semijoin if there is index access to the anti / semijoined table and multiple indexes are available. Bug 5635254 JDBC: Corrupted inserts (with BLOBs) while using batching. Fix was incorrectly missed from the readme. Bug 5692368 RDBMS: Poor performance on library cache or shared cursors-related fixed views even when the lookup is expected to be an index lookup based on hash value. Bug 5705795 RDBMS: SQL using bind variables with different bind sizes can lead to a large number of child cursors being created leading to excess shared pool usage and latch contention. Incorrectly listed as fixed in readme. Bug 4883635 RDBMS: Merge (with delete) gives incorrect incorrect results in the context of rowid fast refresh materialized views. Bug 5638146 RDBMS: ORA-600 [kqlfFillBindData:1] may be raised against a SQL statement containing thousands of bind varaibales. Bug 5605370 RDBMS: Various core dumps / ORA-600 errors (e.g. ORA-600 [kssadpm: null parent] or ORA-600 [kokcup:01]) and ultimately an instance crash can occur as data may have been freed by another process. Bug 5752105 RDBMS: Analyze table validate structure cascade online is slow with patch for Bug 5667736 applied. Bug 5636728 RDBMS: After shrinking an ENABLE STORAGE IN ROW LOB column, ORA-1555 is returned when attempting to read the LOBs. Bug 5386204 RDBMS: ORA-600 [kddummy_blkchk] with internal check code 18038 on tables which have had bulk deletions. Bug 5728380 RDBMS: DML operations , such as INSERTs, may spin when looking for space in ASSM managed segments. This can occur for inserts into table data blocks or for inserts to index blocks. Stacks for the spinning process show that it spins in ktspffc Bug 5093837 RDBMS: After running "alter table shrink" blocks are filled with data above the PCTFREE limit. Bug 4631530 RDBMS: DBVerify reports corrupted blocks even if they are not in use by any segment. Bug 3901785 RDBMS: ORA-600[13009] can occur on SELECT FOR UPDATE with a LONG column. Bug 5530958 RDBMS: Long running transactions which touch large numbers of blocks and involve numerous SQL executions can slow down over time with a large buffer cache with excess CPU time spent in ktaifm(). Bug 5345999 RDBMS: Crash in query from v$spparameter where a really long value is in SPFILE. Fixes included for Critical Patch Update - July 2007 (Note 432865.1 / Representative Bug 6079613 / MLR Bug 6079588) 10.2.0.2.0 Patch 14 (10.2.0.2.14P) 32-Bit Patch 5912173 64-Bit (Itanium) Patch 5912176 64-Bit (x64) Patch 5912179 BaseBug Abstract Bug 5632264 CORE: Version 4 of the timezone files and including timezone rule changes for: Egypt, Brazil and Western Australia Bug 5399282 CBO: Larger index cost bias under First K Rows mode produces better plans. Bug 5649765 CBO: ORA-7445 [evaopn2] can occur during execution of a query that has uses a temporary table star transformation, and there is a view which has a join predicate to one of the replaced dimension tables. Bug 5762598 CBO: Poor cardinality calculations are possible during optimization of queries having predicates using character constants that represented numbers, if the constants are more than six characters long. Bug 5705257 CBO: Wrong index may be chosen (incorrect estimate of index selectivity) when there are multiple concatenated indexes and index filter predicates are simple equality predicates. Bug 5741121 CBO: Poor plans are possible for queries with 'not equals' predicates. Bug 5031712 RDBMS: DBV reports DBV-200 for all kinds of corruptions, including less serious "soft corrupted" blocks caused by invalid redo application. DBV-201 is now reported for these blocks as these can validly exist (e.g.:after application of NOLOGGING redo). Bug 5636728 RDBMS: ORA-1555 may be returned when reading a LOB after shrinking an ENABLE STORAGE IN ROW LOB column. Fixes removed from bundled patch 14 due to serious regressions : Bug 3279497, Bug 4624183, Bug 5302124 Fixes included for Critical Patch Update - April 2007 (Note 420055.1 / Representative Bug 5901922 / MLR Bug 5901881) 10.2.0.2.0 Patch 13 (10.2.0.2.13P) 32-Bit Patch 5735481 64-Bit (Itanium) Patch 5735485 64-Bit (x64) Patch 5735497 BaseBug Abstract This bundled patch includes "version 3" of the Oracle Time Zone files and was re-released in February 2007 because the original README did not include instructions regarding how to correct pre-existing data. Please refer to Note 359145.1 followed by Note 415912.1 for further information. Bug 5483301 CBO: Presence of frequency histogram on an equality predicate column leads to poorly performing plan with nested loops join(s). Bug 4698023 CBO: 10053 trace indicates a predicate is out-of-range, when it is actually in [min,max] range. Bug 5547058 CBO: Column statistics are not always promoted when using old-style predicate push into UNION [ALL] views which can lead to suboptimal plans. Bug 5199213 CBO: Query with union all view may appear to run forever due to poor plan if there is a constant filter pushed inside the set query block. Bug 5691091 CBO: Push of join predicate involving a PL/SQL function into a view can cause Core dump / ORA-7445 [kkqjpdMarkPushedFiltersCB]. Bug 5690241 CBO: ORA-7445 (or wrong results) for queries that contains OR predicates on partition columns. Bug 5694984 CBO: Poor plans are possible in first_rows(k) optimization if an index is available with equality predicates against all key columns. Bug 4924149 CBO: Predicates are not pushed into a view, or a view is not merged (even with a hint) due to a predicate containing a zero-argument function outside of a view owned by another user. Bug 5533982 CDC: When an update is performed and one of the columns is set to NULL, the new value data for that column will not reflect NULL but rather the data that it originally was. Bug 5597046 CORE: CreateFileMapping in SlfMmap fails with ACCESS_DENIED error from XP SP2, Vista. Bug 5135951 DATAPUMP: Importing / Exporting a varray may fail with ORA-22337 when type evolution has occurred. Bug 5658207 JDBCTHIN: SQLEXCEPTION: while using auto-generated keys with clearParameters. Bug 5561244 ODBC: SQLGetConnectOption (SQL_ATTR_CONNECTION_DEAD, ...) fails with access violation. Bug 5706095 RAC: Core dump in clusterware on Windows while running regression suite. Bug 5728502 RDBMS: ORA-7445 [qeroicso] after latest CPU applied. Bug 4668719 RDBMS: ORA-600 [kdtDelRow-2] can occur following a non-data error (such as ORA-4030, ORA-4031) during a BULK insert with a SAVE EXCEPTIONS clause. Bug 5548895 RDBMS: Datapump export of anydata rows fails with ORA-600 [OCIKCallPush: deprecated]. Bug 5374225 RDBMS: SDO_FILTER QUERY returns ORA-600 [kdsgrp1] when it is used as nested query within PL/SQL statement. Bug 5350076 RDBMS: Loss of precision data with sys.anydata get, set and access functions for TIMESTAMP,YMINTERVAL, etc. Bug 4932527 RDBMS: Processing of nested objects causes a core dump in kopp2atsize (client side PL/SQL). Bug 5618049 RDBMS: ORA-4031 during partitioning DDL (allocations will show comment "mvobj part des"). Bug 4937225 RDBMS: ORA-22 can occur on OCIStmtExecute after OCISessionBegin. Bug 4742607 RDBMS: Concurrent index range-scan initializations can lead to contention on the "cache buffers chains" hash latches due to latch upgrades. This can show as high "shared hash latch upgrade" statistic counts and high "latch free" wait events, and in extreme situations, excessive CPU consumption without any user-SQL activity. Bug 5352807 RDBMS: Creating a 10.2 partitioned index with the compute option does not gather statistics. Bug 5188321 RDBMS: Wrong results can be returned with a query involving a very large select list count when ANSI OUTER JOIN syntax is used. Bug 4771672 RDBMS: Create index in parallel for large indexes does not update the segment number of blocks which results in a wrong number of blocks in the seg$ entry and DBA_* views based on SEG$. Bug 5376783 RDBMS: dbms_space.object_growth_trend call generates many disk reads (db file scattered read). Bug 3279497 RDBMS: An interrupted (Ctrl-C) TRUNCATE can corrupt ASSM managed table (ORA-600 [ktspgetmyb-1]). Bug 5158529 RDBMS: Query with "contains" clause may fail with ORA-7445 [qeroicso]. Bug 4899479 RDBMS: Redo / undo corruption and associated Core dumps and/or ORA-600 errors / memory corruption can occur from a transaction which uses "in memory undo" pool memory if the transaction also includes distributed operation/s. Bug 5108234 RDBMS: Memory consumption (Virtual Bytes) per connection in 10.2 is higher than 10.1. Bug 5057695 RDBMS: SHUTDOWN IMMEDIATE can be slower in 10.2 than in earlier releases (particularly with a large number of sessions) due to a change in how processes are terminated. Bug 5197581 SPATIAL: CREATE_FEATURE generates ORA-29532 edge id 9 not found in cache. Bug 5197624 SPATIAL: CREATE_FEATURE generates ORA-29532 attempted to add a node to at an edge terminus. Bug 5700527 XDKC: XSL transformation fails for large XML documents. 10.2.0.2.0 Patch 12 (10.2.0.2.12P) 32-Bit Patch 5716143 64-Bit (Itanium) Patch 5699824 64-Bit (x64) Patch 5699839 BaseBug Abstract This bundled patch includes "version 3" of the Oracle Time Zone files and was re-released in February 2007 because the original README did not include instructions regarding how to correct pre-existing data. Please refer to Note 359145.1 followed by Note 415912.1 for further information. Fixes included for Critical Patch Update - January 2007 (Note 403335.1 / Representative Bug 5694722 / MLR Bug 5689957) 10.2.0.2.0 Patch 11 (10.2.0.2.11P) Only available in 32-Bit Patch 5695266 BaseBug Abstract This bundled patch includes "version 3" of the Oracle Time Zone files and was re-released in February 2007 because the original README did not include instructions regarding how to correct pre-existing data. Please refer to Note 359145.1 followed by Note 415912.1 for further information. Bug 5580871 AQ: Unable to dequeue messages for byte payloads using the OJMS APIs for payload sizes <= 2K, if messages were enqueued using PL/SQL APIs and vice versa. Bug 5031224 ANO: When the Kerberos realm-name of the DB and the DNS domain name of the host on which DB is running are the same, and there is no mapping between them in the Kerberos client configuration file, the login to DB via Kerberos fails. Bug 5095984 ANO: Credential cache created by MIT kinit utility will not be recognized by Oracle Kerberos utilities and kerberized applications like SQLPLUS.. Bug 5471453 ASM: ORA-29701 or CSS errors just prior to ORA-600 [kfkFilRqArr01] error in ASM environment. Bug 4949257 CBO: Wrong results possible from unnested subquery. Bug 4722328 JDBC: Crash while executing a PL/SQL procedure with a CURSOR OUT parameter multiple times without re-creating the statement. Bug 4608183 ODBC: Poor performance driver is binding Number columns that may contain Float data (table scans avoided). Bug 5389003 ODBC: Driver does not round off Double data if connecting to 10.x.x Databases Bug 5063279 RDBMS: When a partitioned bitmap index is being updated, ORA-600 [kdiblLockRange:not validated] could erroneously be raised. Bug 4669305 RDBMS: New diagnostics for ORA-600 [12333] Bug 4277241 RDBMS: xmlagg() with a GROUP BY can fail with ORA-22813 if the result is too large (this can be expect behaviour). Bug 5567934 RDBMS: NCHAR CHARS inserted with JDBC or iSQLPLUS from a single byte character set using N' PREFIX plus embedded single-quotes (even if escaped) end up as corrupted values. Bug 4430244 RDBMS: Segment advisor (eg: DBMS_SPACE.OBJECT_GROWTH_TREND) can load blocks into the cache for DROPPED objects as CURRENT leading to subsequent operations seeing an incorrect (old) version of a block. This can lead to various internal buffer cache related errors such as ORA-600 [kcbnew_3] / ORA-600 [kcbz_check_objd_typ_3]. Bug 5150177 TEXT: Text Index Creation using Master-Detail Datastore is very slow. SQL trace shows that the Master Detail query is doing full index scan on the master table. Bug 5392772 XDB: Corruption of SQL/XML data due to DAT optimization. Bug 5416292 XDKC: XPATH query against large XML file fails with ORA-31186. 10.2.0.2.0 Patch 10 (10.2.0.2.10P) 32-Bit Patch 5639232 64-Bit (Itanium) Patch 5639237 64-Bit (x64) Patch 5639240 BaseBug Abstract This bundled patch includes "version 3" of the Oracle Time Zone files and was re-released in March 2007 because the original README did not include instructions regarding how to correct pre-existing data. Please refer to Note 359145.1 followed by Note 415912.1 for further information. Bug 5031220 ANO: OSD errors parsing KRB5CCNAME location, when okinit is run (Kerberos) Bug 5629724 ANO: Support the mapping of Kerberos principal names with more than 30 character to the database schema. Bug 4273361 CBO: Incorrect execution plan (range scan with fully satisfied unique index predicates, one of them is inlist). Bug 4483240 CBO: Unique index may not be chosen where expected when an INLIST predicate exists on the unique index column. Bug 4722645 CBO: Core dump can occur during execution of queries undergoing star transformation with temporary tables if an index join is used inside the temporary table load. Bug 4904838 CBO: The INDEX_SS hint is not always obeyed where index skip scan is a valid option. Additionally the costing for index skip scan with no keys can be wrong. Bug 5043097 CBO: ORA-600 [15160] can occur during query optimization as the plan cost may appear as infinity. Bug 5113934 CBO: ORA-12805 / ORA-7445 [qerixGetKey] with a parallel plan using bitmap index access. Bug 5245494 CBO: Two new parameters to allow more control over the use of star transformations when it is hinted have been included. Bug 5302124 CBO: Join-predicate pushdown transformation does not take place for queries with window function in view. Bug 5371149 CBO: Connect by queries which include a nested connect by query and subquery with a correlated column in the start with predicates, may fails with ORA-600 [QCTCTE1]. The failure does not happen when the cost based transformation for connect by is disabled. Bug 5449488 CBO: Suboptimal plans are possible for queries with negated predicates that are transitively generated if BITMAP MINUS access paths are used. Bug 5548510 CBO: Use of the _fix_control parameter causes SGA memory leak. Bug 5084239 CBO: Use of the FACT hint can lead to suboptimal subquery usage during star transformation. This fix was not included in the readme until 10.2.0.2 patch 12, the fix is actually included from patch 10 onwards. Bug 5607984 CORE: With DCD enabled, the database may have many hung threads performing timer related activity, consuming resources. Bug 4667071 DBCONTROL: Metadata only exports fail with ORA-39001 / ORA-39178. Bug 4919496 IMP: ORA-14048 importing a partitioned table. Bug 4751145 JDBCTHIN: ArrayOutOfBoundsException can occur when the fetchsize is changed between executes without fetching. Bug 5347395 JDBCTHIN: ORA-910 while performing JDBC batching of derived type. Bug 5499751 JDBCTHIN: Exception when clearParameters is used with AutoGenerated keys feature. Bug 4054238 MVIEW: ORA-12899 Materialized views cannot be created if they contain complex aggregate expressions. Bug 5389003 ODBC: Driver does not round off double data when connecting to 10.x.x databases. Bug 5507506 OLAP: Total function takes a long time in 10.2.x. but runs quickly in Oracle Express. Bug 5572284 OLAP: Maintain on Integer Dimension broken. Bug 5415410 PLSQL: When a OCI application connects to the database with the environment variable ORA_DEBUG_JDWP set to initiate server-side PL/SQL and Java debugging, it may get an exception indicating that the ORA_DEBUG_JDWP value is improper even though it is proper. Bug 5106909 RAC: Instance terminated with ORA-600 [KJBRASR:PKEY]. Bug 5485242 RAC: ORA-29701, CSS altered to increase the maximum connection limit to 5000 to allow more concurrent connections. Bug 4767699 RDBMS: A query referring to a table (having a functional index) and having a join may spin in qcsjFindFroInQbc. Bug 4655998 RDBMS: Some SQL statements involving sorts, particularly on data of type DATE, can fail with ORA-600 [15851]. Bug 5095815 RDBMS: Select with contains predicate on the view column fails (DRG-50857 / DRG-10502) even though the predicate pushdown has taken place. Bug 5115882 RDBMS: An UPDATE .. RETURNING .. can return the wrong values into the "returning" variables if there is a BEFORE UPDATE FOR EACH ROW trigger which updates the :NEW values of the columns. The value from before the trigger fires is returned instead of the actual value used when the row is updated. Bug 5119354 RDBMS: Some queries with connect by clauses and correlated columns in the start with predicates returned incorrect results / ORA-600 [qkacon:FJswrwo]. Bug 5212539 RDBMS: If a LOB is created in an ASSM tablespace without the CACHE option then LOB corruption can result during rollforward (on a standby or following recovery) if a rollback to savepoint is done between 2 lob writes in the same transaction. Bug 5292883 RDBMS: On 64-Bit machines ORA-7445 in memcmp()<-kpzgkvl()<-kziaia()<--kpolnb()<-kpolon() can occur when the client is using olog to connect to the database. Bug 5345437 RDBMS: Reloaded cursors that have NLS sensitive data (typically date formats) may return incorrect data or return NLS related errors such as ORA-1801. This is more likely to occur if the shared pool is under load and if sessions have altered their NLS settings. Bug 5378742 RDBMS: Performance of some connect by queries worsens after applying the fix for Bug 4528339 and Bug 4741394. Bug 5385973 RDBMS: Data truncation is possible with multibyte character set in HSODBC if the client application gets the size of columns with OCI_ATTR_CHAR_SIZE and uses this size to allocate the define buffer. Bug 5507887 RDBMS: Incorrect results may be returned for connect by queries using the connect_by_isleaf construct. Bug 5560256 RDBMS: Multi-threaded OCI programs hang when OCILobLocatorAssign is called. Bug 5571916 RDBMS: Parallel execution of star transformed query may produce wrong results. Bug 5438110 TEXT: DRG-11513 in ctx_user_index_errors when creating text index that includes multi byte characters in file path or file name. Bug 5391686 XDB: VALUE().GETNAMESPACE() returns null. Bug 5399932 XDB: GETROOTELEMENT() returns null even for valid single element nodes. Bug 4967236 XDKC: ORA-600 [17282] / ORA-600 [kghfrempty:ds] importing data. Bug 4515075 XDKCPP: Core dump when using the C++ parser using SAX. This fix is listed in the readme but is not included in the 10.2.0.2 bundled patches because of a problem with the base label. 10.2.0.2.0 Patch 9 (10.2.0.2.9P) 32-Bit Patch 5604010 64-Bit (Itanium) Patch 5604017 64-Bit (x64) Patch 5604021 BaseBug Abstract This bundled patch includes "version 3" of the Oracle Time Zone files and was re-released in March 2007 because the original README did not include instructions regarding how to correct pre-existing data. Please refer to Note 359145.1 followed by Note 415912.1 for further information. Bug 5162241 CBO: Optimization of a query with a "WITH" subquery with aggregation or a distinct clause can cause spinning or a ORA-3113 / Core dump. Bug 5153824 CBO: ORA-7445 [QKABXO] executing query with FIRST_ROWS hint. Bug 5382842 CBO: Queries may return ORA-600 [QCTCTE1] if cost-based transformations are enabled and the query contains a nested subquery. Bug 4689959 CORE: Version 3 of the timezone files (TIMEZLRG.DAT / TIMEZONE.DAT) including timezone rule information in force at the end of 2005. Bug 5186784 DATAPUMP: ORA-600 [ktecgetsh-inc] can occur during DML against a tablespace which has been transported into the database. Bug 3140249 DGUARD: Broker hangs when standby Listener is down. Bug 5074285 JAVAVM: ORA-7445 [EOREALIZE_XREF()+20] SIGSEGV / Core dump with joe_init_class in the stack. Bug 4411462 MVIEW: Materialized Aggregate View fast refresh may be slow due to the use of incorrect hinted cardinality information. Bug 5073249 MVIEW: Materialized View with a 'with ... as' clause crashes after fast refresh. Bug 5549203 NET: OCI clients consume 100% CPU when connecting to a server with SQLNET.OUTBOUND_CONNECT_TIMEOUT set. Bug 5541589 NET: When SQLNET.OUTBOUND_CONNECT_TIMEOUT is set and the First entry in the address list has an Up Listener that does not know about the service, connections do not failover. Bug 5015342 ODBC: ODBC driver SQLColumns() returns wrong information for a few column types. Bug 4880062 ODBC: Calling SQLBindCol() after SQLColumns returns 0 as the Datatype. Bug 4735799 ODBC: ODBC driver can truncate data retrieved with SQLFetchScroll(). Bug 5572656 ODBC: Merge of fixes: Bug 4878228 : Driver may dump due to an Array Bound Read error under _uCnvCharToDate / bcoConvertOciToOdbc. Bug 4886344 : Un-initialized memory read. Bug 4878347 : Valgrind report shows that 2 overlapped buffers are passed memcpy() function. Bug 4888315 : Memory not initialized for StmtServerError buffer. Bug 4886366 : Un-initialized memory read. Bug 4961312 : Driver memory leak for SQLBulkOperations. Bug 4878377 : Valgrind driver Memory Leak. Bug 4758162 RAC: ORA-7445 [BREAKPOINT] [UNABLE_TO_TRANS_PC] as a consequence of retrying a socket creation attempt, that fails due to a low memory condition. Bug 5089217 RDBMS: Connect BY queries that have an ORDER SIBLINGS BY clause with columns that use special nlssort functions sometimes fail with an internal error such as ORA-600 [qkacon:NFswrwo] Bug 5458753 RDBMS: If different schemas have tables / views etc.. with identical names and sessions from different schemas execute IDENTICAL SQL statements then it is possible for such SQL sentences to get executed against the wrong schema objects Bug 5201883 RDBMS: Lots of MMAN trace files containing text like : "AUTO SGA: Not free 0x39cbe6e18, 1, 1, 1" Bug 4966417 RDBMS: Various Core dumps / ORA-7445 / ORA-600 errors and ultimately an instance crash can occur when a session performs a rollback to a savepoint type operation. Bug 5128946 RDBMS: Memory leak due to DDL reparse. Bug 5476507 RDBMS: ORA-600 [15868] while running stats pack reports. Bug 5045992 RDBMS: ORA-0600 [KXSPOAC : EXL 1] may be raised by a parallel execution slave when attempting to bind a numeric bind. Bug 5254759 RDBMS: ORA-1008 may be raised when literal replacement is enabled and there are user binds present and the query is going parallel. Bug 5043975 RDBMS: ORA-600[OPIXRM-1] [invalid handle] can occur using remote cursors with SESSION_CACHED_CURSORS set. Bug 5254198 RDBMS: "Alter User sys Identified By Values" does not update the password file. Fix was re-included after a new label was created. Bug 4966512 STREAMS: ORA-600 [KWQBCFROBJ123] possible when Capture or Apply processes share queue tables. 10.2.0.2.0 Patch 8 (10.2.0.2.8P) 32-Bit Patch 5502226 64-Bit (Itanium) Patch 5500894 64-Bit (x64) Patch 5500921 BaseBug Abstract Bug 5385629 CBO: Query containing inline view allows join-predicate pushdown ("VIEW PUSHED PREDICATE" or "UNION ALL PUSHED PREDICATE" appears in plan), but if the inline view is replaced with a reference to a view (with the same definition), join-predicate pushdown is not chosen. Bug 4686006 CBO: ORA-600 [KKQSALJG:NOBJS IS 0] from join graph equivalency code. Bug 4639977 CBO: CONNECT BY query may fail with ORA-600 [kkqcby: qbcfkkc not zero]. Bug 4204383 CBO: ORA-7445 during optimization of a query using ANSI outer join, where the query has views with nested subqueries. Trace file will show the failure in the kkqt* routines. Bug 4648181 CBO: Queries using pushed join predicates can fail with ORA-600 [15160]. Bug 5400311 CBO: Some connect by queries that the use old connect by (_old_connect_by_enabled has been set to true), can receive unexpected results and / or errors (such as ORA-1436). Bug 5402870 CORE: The oracle.sql.TIMESTAMPTZ object may return data offset by an hour when the timestamp value is near to the day light switch time. Bug 4380928 MVIEW: ALTER MATERIALIZED VIEW LOG add filter columns may core dump (ORA-7445 / ORA-3113) or cause memory corruption. Bug 5015547 MVIEW: ORA-942 can occur while creating a Materialized View on a View over a Non-Owner Database Link. Bug 5365475 ODBC: Unused input CLOB parameter is stored procedure corrupts outcome. Bug 4965677 ODBC: Second invocation of SQLEXECUTE while inserting NCLOB data fails with ORA-12704. Bug 5406681 ODBC: ORA-1036 error when calling a function using Schema.FunctionName. Bug 5146470 OLAP: B Patch. Bug 4968975 OSS: Memory leak in SSL code when self-signed certificate is used for certificate authentication. Bug 5066528 PLSQL: Enabling PL/SQL exception tracing (using DBMS_TRACE.SET_PLSQL_TRACE (DBMS_TRACE.TRACE_ALL_EXCEPTIONS)) causes various non-exception related rows to be inserted in the table sys.plsql_trace_events. Bug 4643322 PLSQL: ORA-22167 possible from BULK DML RETURNING INTO (the error reports that the size of the collection is 1). Bug 4151363 RAC: Drop / Truncate table operations can be slow in a RAC environment in 10.2 with lots of time waiting on "lms flush message acks". Bug 4446899 RAC: SRVCTL commands fail with Exception Violation JAVA HOT SPOT Virtual Machine error. Bug 4723824 RAC: CSS Core Dump during memory allocations. Bug 4416063 RAC: OUI-35073 starting services on a remote node during the "remote operations" stage of installation (trying to start OracleClusterVolumeService on the remote node). Bug 4592596 RDBMS: Corruption (ORA-1410) is possible from multi-table inserts with direct load (APPEND or Parallel Query). Bug 4587572 RDBMS: ORA-60 / ORA-12801 can occur with Parallel DML statements involving Grouping Sets. Bug 5254539 RDBMS: A SQL statement involving hierarchical query using cursor statements in select list does results in ORA-600 [qkacon:FJfsrwo]. Bug 5097836 RDBMS: Wrong results in Parallel Query when there is more than one range TQ seen in the plan. Bug 5363584 RDBMS: If in memory undo is in effect, array inserts can cause buffer cache corruption and / or ORA-600 [kddummy_blkchk] (if block checking is turned on). Bug 4582764 RDBMS: Wrong results from SQL using mixed Oracle style OUTER join with an ANSI FULL OUTER join and an inline view. Bug 5276400 RDBMS: Wrong results possible from query rewrite when using joins and grouping. Bug 5136863 RDBMS: ORA-600 [QKAPIDSQKN1] from a query when the optimizer incorrectly attempts to build a plan for a full partition wise join between a partitioned table and a non-partitioned domain index. Bug 5380055 RDBMS: ORA-1555 / index block corruption when switching to a Standby then back to a Primary after the database was upgraded to 10.1.0.5 or higher. Bug 5163569 RDBMS: There is a timing window at background process spawn time that can cause an ORA-00600 [784]. Bug 4450497 SPATIAL: Spatial metadata is not upgraded properly when a database is upgraded from 9.0 to 10.1 (or 10.2). Causing SDO_INDEX_METADATA null fetch errors (ORA-29875 / ORA-13209 / ORA-29400 / ORA-1405). Bug 5117856 XDB: Merge of fixes: Bug 4568043 : xmldom.substringdata() may dump or give empty data, when trying to get the data after the offset 4000. Bug 4699502 : xmldom.setAttribute() and xmldom.removeAttribute() behave incorrectly when the attribute given is of the form "prefix:name". Bug 5125886 XDB: Merge of fixes: Bug 4970030 : xmlparser.parseclob() and xmlparse.parsebuffer() ignore white spaces even after setting setPreservewhitespace to true. Bug 4955476 : DTD reference may be removed after parsing XML using parseClob. Bug 5253806 XDB: For PL/SQL dbms_xmldom transformation functions, the output should be streamed for non-xml output types. Bug 4744317 XDKC: XSLT transform fails when tag contains '_' at beginning. Fixes included for Critical Patch Update - October 2006 (Note 391558.1 / Representative Bug 5490937 / MLR Bug 5490848) 10.2.0.2.0 Patch 7 (10.2.0.2.7P) BaseBug Abstract This bundled patch was skipped due to software regressions. 10.2.0.2.0 Patch 6 (10.2.0.2.6P) 32-Bit Patch 5413245 64-Bit (Itanium) Patch 5438679 64-Bit (x64) Patch 5438688 BaseBug Abstract Bug 5089630 ASM: ORA-15012 while running Log Miner to process log files that are on an ASM diskgroup. Bug 4722900 CBO: Incremental Materialized View refresh can be slow, because of incorrect estimation of join selectivity in a Merge operation. Bug 5015557 CBO: ORA-7445 [kkoNewExtractedBMKey] / ORA-7445 [qerixGetKey] / Core dump can occur with a bitmap plan and function based indexes. Bug 5369855 CBO: Star transformation optimization can cause a hang / spinning (qksopLogSame in the stack). Bug 5103126 CBO: Poor performance of inserts involving unique constraints. Bug 4625102 CBO: Wrong results are possible from queries with ANSI syntax outer joins if there are multiple tables on the right-hand side and more than one of these has a single table predicate. Bug 5241586 DBCONTROL: Agent fetchlet causes process handle leak. Bug 5181800 DGUARD: Async LNS holds C/F Transaction while issue network calls RFSOPEN / RFSCLOSE affecting primary system performance. Bug 5368791 NET: sqlnet.outbound_connect_timeout should apply to each entry of an "address_list" separately. Bug 5214373 NET: TNS Listener crashes due to Memory Fault in Module ORANL10.DLL (stack snlpcenvini, nlpcPersonaUpdFinal, nlpcaini, etc). Bug 4878372 ODBC: Memory Leak in ODBC Driver (bcoInitNLS / bcoTermNLS). Bug 5396837 OSS: File handle leak from nzcrlGetCRLFromFile. Bug 5249142 PLSQL: Executing an RPC in signature remote dependency mode when a formal of the remote procedure is of flexible character form results in an ORA-4062 error because signature matching failed. Bug 4750469 RAC: Releasing a unchecked resource to the shared pool can cause ORA-600 [kjrfr7] in RAC systems. Bug 4151363 RAC: Drop / truncate table operations can be slow in a RAC environment in 10.2 with lots of time waiting on "lms flush message acks". Bug 5338035 RAC: PRKR-1008 attempting to create RAC Instance (with DBCA or SRVCTL) on German Windows. Bug 5205552 RDBMS: Oracle on Windows 2003 AMD64 / EM64T consume more memory (Virtual) due to incorrect thread stack sizing. Bug 5388136 RDBMS: A trigger referring to :OLD or :NEW when these are of type NVARCHAR2 or NCHAR can ORA-7445 [pfrust] / Core dump if the database character set is multi byte. Bug 4752541 RDBMS: Intermittent PLS-306 / ORA-1722 / ORA-1858 under load Bug 4544444 RDBMS: Incorrect code path in KPUINISG causing timezone file problem. Bug 5126551 RDBMS: ORA-7445 [KKDCACR] / Core dump loading foreign key constraint metadata. Bug 5155885 RDBMS: ORA-600 [KKSLGBV0] / Core dump accessing bind values (both literal replaced and user bind) when CURSOR_SHARING=SIMILAR or user bind peeking is enabled. Bug 5251964 RDBMS: Internal heap error 17112 (in kpuexec) when using notifications and statement caching. Bug 5254198 RDBMS: "Alter User sys Identified By Values" does not update the password file. Bug 5208840 RDBMS: Audit records may not be created when a Fine Grained Access policy is defined against a view, and the policy defines an "audit column" but doesn't define an "audit condition". Bug 4932843 RDBMS: Wrong results from queries with a full outer join involving a table function when the execution plan contains a nested loops anti join. Bug 4771851 RDBMS: Insert as Select with complex query and tables with foreign keys can cause ORA-7445 [KXCCSRW]. Bug 5206570 RDBMS: Shadow thread / process crashes with kokaocl on the call stack (and either kprball or ksusrs) when disconnecting after the session has been marked as sniped due to idle time limitation. Bug 4883174 RDBMS: Archiver produces "KCRRWKX: NOTHING TO DO (END)" messages without debug enabled. Bug 4912371 RDBMS: Segmentation fault (core dump) importing objects / types (IMP-58). Bug 5118210 SPATIAL: Insert as Select fails with ORA-600 [KOPUIGPFX1] when table contains triggers and SDO_GEOMETRY columns. Bug 5263631 XDB: If a schema has a substitution group whose head element's type does not have any global sub-types, and all the group members locally extend the head element's type, then using such a schema to associate with a table or column, will raise ORA-31196, during DML operations. Bug 5353622 XDB: Re-write does not happen completely for simple XQuery statements having a FLWR causing poor performance. Bug 4759183 XDB: Corrupt XML values can be produced by SQL/XML statements with XMLAgg() operations. 10.2.0.2.0 Patch 5 (10.2.0.2.5P) 32-Bit Patch 5383042 64-Bit (Itanium) Patch 5388866 64-Bit (x64) Patch 5388871 BaseBug Abstract Bug 5240607 CBO: In first_rows_k mode the optimizer sometimes can choose inefficient Nested Loops with a full scan on the right side. Bug 5078743 CBO: Some queries may fail with ORA-7445 [QKABXO] if a bitmap access path is chosen in first k rows optimizer mode. Bug 5018513 DGUARD: Failover takes too long and the target standby is not in the process of terminal recovery (BYSTANDERS should be ignored). Bug 5191972 DGUARD: Merge of fixes: Bug 5011019 : ORA-600 [2103] on BYSTANDER standby during target standby failover. Bug 5146287 : BROKER REINSTATE command on bystander standby because FLASHBACK will not work across ACTIVATION ID boundary Bug 3807408 NET: Externally authenticated usernames containing a '(',')' or '=' can not be authenticated, additionally if a program name / path contains these characters, it may not be possible to connect (ORA-12154). Bug 4546618 ODBC: ORA-1406 when selecting calculated number with large precision from a view. Bug 5220440 ODBC: Driver truncates CLOB data with UNICODE charactersets on the client. Bug 5214109 PLSQL: Attempting to unpickle an index of binary integer table (via a call to a stored procedure) which has elements with indices -1 and 0 can fail with an ORA-600 [kopp2ucoll700]. IBBI tables with any negative indices which were pickled and unpickled may be corrupted: all elements with negative indices may have been shifted by one index. Bug 4437727 RAC: VIPCA complains that an interface is private even though it has been configured it to be public. Bug 4741394 RDBMS: Connect by queries with complex subqueries in the start with clause can sometimes fail with an ORA-600 [12406] error. Bug 4736557 RDBMS: Selecting from a global temporary table using a read only transaction can fail with ORA-1466 unable to read data -- object definition has changed. Bug 4417341 RDBMS: ORA-07445 [ktbgfi()+109] / Core dump because transaction has completed while cursor fetch is still in progress. Bug 4904743 RDBMS: NLS settings are not completed if an 'alter session set NLS%' is first executed in parse only mode and then in normal execute mode. Bug 5257698 RDBMS: 9.x NLS data compatibility files lx40030.nlb and lx40003.nlb were missing from 10.2. Bug 4370351 RDBMS: Large queries can take a long time to compile due to unnecessary looping on the code. Bug 5381980 RDBMS: Merge of fixes: Bug 5109749 : Wrong results are possible from queries using functional indexes and advanced subquery unnesting. Bug 4939157 : ORA-07445 [EVAOPN2] / Core Dump when using a functional index column in an equality predicate. Bug 5092688 : Wrong results are possible with function based index that use subquery unnesting. Bug 4900129 : High CPU consumption during parse for unused CHECK constraints. Bug 5243019 SPATIAL: Memory lean in SDO_GEOM.WITHIN_DISTANCE, SDO_WITHIN_DISTANCE, SDO_NN Bug 5226671 SQLLDR: Can not load large CLOB's - the maximum READSIZE has been increased (this is platform specific). 10.2.0.2.0 Patch 4 (10.2.0.2.4P) 32-Bit <Patch 5251025 64-Bit (Itanium) Patch 5251026 64-Bit (x64) Patch 5251028 BaseBug Abstract Fixes included for Critical Patch Update - July 2006 (Note 372927.1 / Representative Bug 5242650 / MLR Bug 5225799) 10.2.0.2.0 Patch 3 (10.2.0.2.3P) Only available in 32-Bit Patch 5251024 BaseBug Abstract Bug 5114330 ANO: Was included in 10.2.0.2 patch 2, but is re-listed here because it is additionally included in the Instant Client in this bundled patch. Bug 4622729 CBO: Wrong results for NOT IN sub-query converted to ANTI JOIN. Bug 4900129 CBO: High CPU consumption during parse for unused CHECK constraints. Bug 4967676 CDC: Creating change tables with valid schema names that are in double quotes will fail. Bug 5077897 CORE: Server exhibits a thread Handle leak which is observed for every TCP connect / disconnect to a 10.2 database. Bug 4693439 EXP: Full database export with system auditing options fails with ORA-1406 fetched column value was truncated. Bug 4864563 HS: Where clause removed from query sent to foreign database when the where clause requires implicit data type conversion. Bug 4688040 JDBC: Does not support batch sizes greater than 65535 in 10.x.x.x. Bug 4998582 JDBC: Driver throws exception when PL/SQL functions or procedures, having OUT parameter types are executed using the CALL statement. Bug 4690147 ODBC: Using array binds with stored procedures where the first element is NULL data may cause the statement execution to crash. Bug 4672767 PLSQL: PL/SQL native compilation with MINGW compiler can not find LIBPNCRT.A. Bug 5092725 RAC: CRSCTL DEBUG does not accept resource names with '-', the name is truncated. Bug 4537790 RAC: After node reboot, startup of CRS stack can be very slow on Windows platforms. Bug 4416063 RAC: OUI-35073 attempting to start services on remote node during installation. Bug 4707226 RDBMS: DBMS_ADVISOR AUTO_SPACE_ADVISOR_JOB may fail with ORA-2000 if the tablespace to be processed does not exist any more. Bug 4712729 RDBMS: ORA-21780 when executing large number of updates on a table with a before row trigger. Bug 5151675 RDBMS: ORA-354, ORA-353 signalled during log archiving when there are multiple good log members Bug 4950942 RDBMS: Views may not describe NUMBER datatypes correctly if there is a FLOAT present in the select list and the view uses a SET operator query block. Bug 4952782 RDBMS: Query with group-by and order-by desc can cause ORA-600 [QERNSROWP] when index is picked by Oracle optimizer. Bug 5092688 RDBMS: Wrong results from query with specific access predicates using function based index. Bug 4939157 RDBMS: ORA-7445 / Core Dump can occur (in avaopn2) when using a functional index column in an equality predicate. Bug 4862218 XDB: ORA-3113 / Core Dump while using regular expressions which use regexp_replace. Bug 5212798 XDB: The primitive type xsd:dateTime could not be automatically mapped to TIMESTAMP WITH TIME ZONE. Bug 4587761 XDB: XMLType.getNamespace() returns NULL for Non Schema Based documents. 10.2.0.2.0 Patch 2 (10.2.0.2.2P) 32-Bit Patch 5211342 64-Bit (Itanium) Patch 5211348 64-Bit (x64) Patch 5211354 BaseBug Abstract Bug 5114330 ANO: ORA-12640 authentication adapter initialization fails if Operating System User does not have admin rights. Bug 4960705 ASM: On cluster reconfiguration, ASM can wait longer than necessary before rechecking status. Bug 4376021 CBO: Wrong results (caused by lost OR predicate) in a query having an inlist with a function based index expression. Bug 4953737 DGUARD: When a database is running in a Primary role, Data Guard uses an archive process to prepare the Standby Redo Log Files for use when the database transitions to a Standby role. This can cause hangs if there are no Standby Redo Logs. Bug 5039679 DBCONTROL: Collecting Host statistic without the timezone environment variable (TZ) set causes NMEO.EXE to fail with Access Violation (DR WATSON) errors. Bug 4951251 INSTCLI: If an application loads OCI.DLL dynamically and frees it, the application may crash and the instant client DLL will remain loaded in memory even when OCI.DLL is freed. Bug 4758632 LOGMINER: Reader Slaves consume unusually large proportion of CPU when idle. Bug 5123958 NET: ORA-12571 / ORA-12536 with SQLNET.OUTBOUND_CONNECT_TIMEOUT and Listener redirects. Bug 4933023 NET: With an outbound connect timeout set in SQLNET.ORA connections using a bequeath driver can fail with ORA-12569 TNS:packet checksum failure. Bug 4906807 NLSRTL: INSTR operation sometimes returns incorrect results for searches of zht16mswin950, zht16hkscs or zht16hkscs31 encoded source data. Bug 5147229 ODBC: ORA-1008 when MFC applications try to re-query (CRECORDSET.REQUERY) tables. Bug 4150034 ODBC: Catalogue functions should not use the Rule Hints, when the new option Disable Rule Hint is checked. Bug 4622561 ODBC: Driver reports errors on executing a stored procedure containing REF CURSOR parameters. Bug 4371966 ODBC: Driver may report "Input string too long, limit 4096" when the long string contains either a CR (\r) or an LF (\n) character. Bug 4705928 PLSQL: Memory leak using small varrays when trimming the whole collection and inserting into it in a loop. Bug 5127434 RAC: Merge of RAC Fixes: Bug 4452690 : When _IMR_DISK_VOTING_INTERVAL is set to 0, LMON crashes. Bug 4690368 : Instance or node crash takes a long time to be detected and process the CGS reconfiguration. Bug 5127459 RAC: Merge of Fixes: Bug 4874273 : GES : SMON waits in '"GES ENTER SERVER MODE" for more than 1 second.. Bug 5061068 : GES : Foregrounds may wait longer for commit when using broadcast-on-commit SCN scheme. Bug 4960746 : DRM : Takes about 2 seconds even when manually driven via lkdebug -m command. Bug 4755405 : DRM : Sync can take a very time as LMON is waiting for LMSES to empty their send queues Bug 4682861 : ASM : ORA-600 [kfclNullConvert20] can occur in an ASM instance. Bug 4709214 : ASM : ORA-00600 [kfclGetLock40] can be signalled from an ASM instance Bug 4709210 : ASM : LMS process in an ASM instance can crash with error ORA-600 [504] with kfclDoLazyCloses() on the call stack. Bug 4943406 : ASM : Delay of up to 3 seconds may occur for ASM instance recovery to takes place after a cluster reconfiguration. Bug 5095887 : GRD : Foreground waits too long before exiting server mode after instance recovery. Bug 4744859 RDBMS: ORA-600 [kkbncre: SQ_LEN3] during import. Bug 4712199 RDBMS: If there are dependent services on the Database service (e.g. ASM), the Database may not automatically start-up on a reboot. Bug 4593537 RDBMS: Database may crash with call stack kqlr, ...., kpumfs, kghfrf on when using UPI / accessing remote objects (procedures, tables etc) over a database link. Bug 5016142 RDBMS: When SMON is cleaning up very large dead transactions, it may not service other work like cleaning up temporary space, handling sort-segment requests or performing instance recovery. Bug 4927753 RDBMS: Grant and alter user statement may hang indefinitely (RowCache Hang). Bug 4865959 RDBMS: Java exception when trying to fetch more than one row from a remote database with a java stored procedure. Bug 4956438 RDBMS: ORA-1404 when altering a table with an index on it (index key size constraint was wrongly calculated). Bug 5037103 RDBMS: Selecting from a view with Union all in which both statements (of Union all) select from a remote table gives an internal error (ORA-7445 [_QERRMOIEB()+612] [SIGSEGV]). Bug 4967266 RDBMS: RAC Instance Recovery may have to wait for ASM diskgroup recovery, when FAST_START_MTTR_TARGET is set to a few seconds. Bug 5098050 RDBMS: Log writer does not close a stale log member until max error is reached. Bug 5127482 RDBMS: Merge of Recovery Fixes: Bug 4868650 : Periodic bursty writes observed when FAST_START_MTTR_TARGET is set less than 10 seconds for fast crash recovery. Bug 4733738 : If either FAST_START_MTTR_TARGET or _FAST_START_INSTANCE_RECOVERY_TARGET is set below the Checkpoint background process timeout of 3 seconds, it adjusts the timeout down to 1 second. Bug 4935707 : Log Writer (LGWR) encounters waits for "redo writing latch" of several seconds. Bug 4933038 : _FAST_START_INSTANCE_RECOVERY_TARGET should include the whole instance recovery time. Bug 5065930 : Timeouts may be observed for the "log file sync" wait event, particularly in a workload where a small number of users exist. Bug 4928371 RDBMS: Connections can still be routed to an aborting instance while PMON is waiting for DIAG to dump diagnostics. Bug 5080775 RDBMS: Alter System Kill Session Immediate can take up to 15 minutes to start process cleanup. Bug 4925189 TEXT: CATSEARCH may return less rows than expected when multiple terms are specified in the text part and a multi-column ORDER BY is specified in the structure part. Bug 4694045 XDB: Insert into XML Document (Copy Evolve) causes memory growth, linearly proportional to the number of rows being evolved. 10.2.0.2.0 Patch 1 (10.2.0.2.1P) 32-Bit Patch 5140461 64-Bit (Itanium) Patch 5140508 64-Bit (x64) Patch 5140567 BaseBug Abstract Bug 4698119 ADVREP: Trace files are created for every replication DML statement. Bug 5089814 CBO: Wrong results are possible from queries using outer joins if the deficient table has a "col(+) = NULL" predicate. Bug 4639977 CBO: ORA-600: [KKQCBY: QBCFKKC NOT ZERO] during CONNECT BY optimization. Bug 5033476 CBO: ORA-7445 / Core Dump when performing DML where the statement has a connect by subquery and the column in the condition connecting the outer query and the subquery has a trigger defined on it. Bug 4712638 CBO: Parsing a SQL statement may fail with ORA-7445 in kkogbro() or signal ORA-600 [15160]. Bug 4901291 CBO: Wrong results with Left Outer joins on a view with a function. Bug 4692059 CBO: Wrong results possible from SQL with subqueries that have correlation conditions with multiple columns on one side of the predicate, if the subquery is converted to a semijoin that is then eliminated. Bug 4744469 DATAPUMP: IMPDP Grants all roles to user creating them exceeding max enabled roles (ORA-316). Bug 4522561 DGUARD: Repeated : "%s: Failed to archive thread %ld sequence %ld (%ld)" / "%s: Archiving not possible: No %s destinations" alert log messages when archiver is stuck. Bug 4380928 MVIEW: ORA-3113 / ORA-7445 during alter materialized view log when adding filter columns. Bug 4610806 NET: Names Executable may crash (stack contains nnflfrm calling ldap_mem_free). Bug 4769781 NET: With names.no_persistent_resources=true, consecutive connections can hang or fail with ORA-7445 / SIGSEGV. Bug 4114966 NET: TNSPING core dumps when names.no_persistent_resources=true is set in sqlnet.ora Bug 3306350 NET: Client connections using NAMES do not close the connection to the names server. Bug 4991478 NET: ORA-21561 / ORA-22 when using COM threading or Freethreaded Marshaller. Bug 4727495 ODBC: Application crash when executing a stored procedure which has a large number of parameters. Bug 4690201 ODBC: Driver sets the value corresponding to attribute SQL_ATTR_PARAMS_PROCESSED_PTR improperly in case of stored procedure execution with array binds. Bug 4643322 PLSQL: ORA-22167 (where the size of the collection is 1) when trying to do a BULK update with returning into. Bug 4690794 RAC: Global enqueue ordering may be violated causing "ERROR IN KQLMBIVG SEE LCK TRACE FILE" messages. Bug 4990803 RDBMS: ORA-7445 / new attributed not added to tables column after type evolution. Bug 5033218 RDBMS: ORA-6502 "character string buffer too small" can occur when inserting >= 1001 characters into a VARCHAR2 column having a trigger using the data inserted in a variable if NLS_LENGTH_SEMANTICS=CHAR. Bug 4583177 RDBMS: Slow performance when inserting SubType Constructor into Polymorphic Column. Bug 4748222 RDBMS: ORA-600 [ztsmdwl failed] using triggers in conjunction with transparent data encryption (TDE). Bug 4962247 RDBMS: Client side optimization for faster RDBMS data access. Bug 4644048 RDBMS: Type Extension fails with inconsistent DataType (ORA-932). Bug 4726702 RDBMS: ORA-3113 / ORA-7445 [KOKTUPD_DPLVL] during ALTER TYPE due to ref dependency. Bug 4440681 RDBMS: ORA-7445 [KGHALP] when creating a table when using regular expressions which use table expressions. Bug 4908068 RDBMS: ORA-1400 from an insert with a subquey when the table being inserted into has a before insert trigger. Bug 4698156 RDBMS: ORA-12850 may be returned by questies on gv$ views when cursor_sharing=force. Bug 4523125 RDBMS: ORA-3106 can occur with a select which is executed twice followed by an "alter system flush shared_pool" followed by another execute Bug 4669305 RDBMS: Diagnostics added to assist in resolution of ORA-600 [12333] errors. Bug 4460775 RDBMS: ORA-21700 when compiling objects after an upgrade from 9.2 to 10 cause by missing time based types. Bug 4604970 RDBMS: Wrong results possible from the result of a non-distinct aggregation with a group by (such as sum(col)) when HASH GROUP BY is used. The wrong results show as missing values from the aggregate. Bug 4592596 RDBMS: Corruption (ORA-1410) from multi-table insert with direct load Bug 4587572 RDBMS: Parallel DML statements involving Grouping Sets can incorrectly return ORA-60 errors because of potential deadlock. Bug 4717280 RDBMS: When using a Sequence in an Insert statement where a trigger exists, a NULL value may be incorrectly placed in the column. Bug 4704594 RDBMS: OCIGetAttr may return the wrong maximum length for cast null as number(1). Bug 5101403 RDBMS: OCI statement caching optimization for ODP.NET Bug 4752108 SPATIAL: The optimizer should "not" apply the domain index operator against SQL statements in a UNION ALL view that does not contain a spatial column. Bug 5021540 XDB: ORA-30937 inserting an instance doc into a table based on a schema that has no target namespace and has subsgroup elements. Bug 4587607 XDB: ORA-31187 in 10.2, ORA-30930 in 9.2 when inserting an XML Document into SB table where the schema has substituteGroup elements which have refs to global elements. Bug 3703236 XDB: When using a small session timeout for XDB on Windows, transfers of non-xml files often fail before the timeout is reached. Fixes included for Critical Patch Update - April 2006 (Note 360044.1 / Representative Bug 5079038 / MLR Bug 5079037) -------------------------------------------------------------------------------- 10.2.0.1.0 Patch 9 (10.2.0.1.9P) 32-Bit Patch 5695784 64-Bit (Itanium) Patch 5695785 64-Bit (x64) Patch 5695786 BaseBug Abstract Fixes included for Critical Patch Update - January 2007 (Note 403335.1 / Representative Bug 5694720 / MLR Bug 5689937) 10.2.0.1.0 Patch 8 (10.2.0.1.8P) 32-Bit Patch 5500927 64-Bit (Itanium) Patch 5500951 64-Bit (x64) Patch 5500954 BaseBug Abstract Bug 4900129 CBO: High CPU consumption occurs during parse for the recursive query 'select condition from cdef$ where rowid=:1' obtaining constraint information for constraints that are not actually use for the parse. Bug 5109749 CBO: Wrong results or ORA-1428 are possible from queries using functional indexes and advanced subquery unnesting. Bug 4546618 ODBC: ORA-1406 when Selecting Calculated Number with Large Precision from View. This was only listed in the 32_bit Readme, but the fix is included in the x64 and Itanium patches. Bug 4939157 RDBMS: ORA-7445 [EVAOPN2] / Core Dump possible when using a functional index column in an equality predicate. Bug 5092688 RDBMS: Wrong results are possible if a function based index exists on a table used in a query. Fixes included for Critical Patch Update - October 2006 (Note 391558.1 / Representative Bug 5490936 / MLR Bug 5490846) 10.2.0.1.0 Patch 7 (10.2.0.1.7P) 32-Bit Patch 5239698 64-Bit (Itanium) Patch 5239699 64-Bit (x64) Patch 5239701 BaseBug Abstract Fixes included for Critical Patch Update - July 2006 (Note 372927.1 / Representative Bug 5242648 / MLR Bug 5225798) 10.2.0.1.0 Patch 6 (10.2.0.1.6P) 32-Bit Patch 5059238 64-Bit (Itanium) Patch 5059251 64-Bit (x64) Patch 5059261 BaseBug Abstract Fixes included for Critical Patch Update - April 2006 (Note 360044.1 / Representative Bug 5049088 / MLR Bug 5049080) 10.2.0.1.0 Patch 5 (10.2.0.1.5P) 32-Bit Patch 5059233 64-Bit (Itanium) Patch 5059245 64-Bit (x64) Patch 5059258 BaseBug Abstract Bug 4671216 ASM: Creating / deleting / resizing to a large ASM file may block other ASM operations for an extended period of time and may cause instances to crash with ORA-600 [2103] or ORA-600 [2116] errors. Bug 4901291 CBO: Query with left outer join on a view with a function gets wrong results. Bug 4542082 CBO: Performance degradation for Connect by Query using First N rows (HASH JOIN plan with FTS or index FULL SCAN). Bug 4496863 DGUARD: ORA-38860 is raised when FSFO attempts to flashback the old primary, and DI2LD_SCN and DI2LR_SCN in X$KCCDI2 are non-zero. Bug 4546618 ODBC: ORA-1406 when selecting Calculated Number with large Precision from View. Bug 4537790 RAC: After node reboot, startup of CRS stack can be very slow on Windows platforms. Bug 4748797 RAC: CSS daemon fails with error messages in the CSSD log indicating that voting disk failure has caused the CSSD to fail. Bug 5012796 RDBMS: ORA-7445 / Core dump in function 'kglhdgsc()' when using distributed transactions. Bug 4447168 RDBMS: ORA-7445 / Core dump during transaction commit, rollback or abort with auditing enabled and kzaPrecmt_Cbk is shown in stack trace. Bug 4745114 RDBMS: ORA-600[kolrrdl-0rfc] freeing session duration temp lobs before the end of the session. Bug 4458790 RDBMS: A PL/SQL block which selects a MAX or MIN into a fixed CHAR variable can fail with an unexpected ORA-6502 "character string buffer too small" error. Bug 4698156 RDBMS: ORA-12850 from queries against GV$ tables when cursor_sharing =force. Bug 4570793 RDBMS: Table and indexes can get out of sync after doing array inserts. Deletes may report ORA-8102 and validate structure cascade reports ORA-1499. Bug 4523125 RDBMS: ORA-3106 for a select which is executed twice followed by "alter system flush shared_pool" followed by another execute. Bug 4644048 RDBMS: Oracle Type Extension fails with inconsistent DATATYPE (ORA-932) Bug 4515623 RDBMS: Update .. RETURNING with a trigger can return produce corrupt column data. Bug 4767699 RDBMS: Query referring a table (having a functional index) and having a join can hang (in qcsjFindFroInQbc) using 100% CPU. Bug 4908068 RDBMS: Insert with subquery in values clause raises ORA-1400, when before insert triggers exist. Bug 4884408 RDBMS: Instance health monitoring code creates a large number of Windows thread Handles that are not being cleaned up properly. Bug 4712199 RDBMS: Database does not automatically start after reboot when it has many dependent services. Bug 4686909 RDBMS: Convert function used anywhere except select list throws ORA-1482. Bug 3748430 RDBMS: Was included in 10.2.0.2 patch 4 but was re-included here because the base bug fix was reworked. Bug 4898338 TEXT: World lexer crashes when indexing documents that contain the characters chr(15711384), chr(15711372), chr(15711634). Bug 4751888 XDB: Schema registration fails with ORA-31038 "Invalid enumeration value" for substitution. 10.2.0.1.0 Patch 4 (10.2.0.1.4P) 32-Bit Patch 4923768 64-Bit (Itanium) Patch 4923780 64-Bit (x64) Patch 4923787 BaseBug Abstract Bug 4626732 CBO: Predicate pull up does not type check operands properly leading to dumps / internal errors (e.g.: ORA-600 [evapls1]) at execution time. Bug 3807408 NET: Unable to connect if host or program names contain '(', ')' or '=' characters. Or if using remote OS authentication and the username contains single quotes authentication fails. Bug 4584509 NET: ASM service can not connect to the database (PRKS-1009 / CRS-0215) using LocalSystem account on a windows 2003 server configured as Primary domain controller. Bug 4690147 ODBC: Returning an array of varchars from a stored procedure call crashes when an element is null. Bug 4573573 RAC: CSS connections may be found to listen on IPADDR_ANY, potentially leading to failures during cable pull testing. Bug 4865122 RDBMS: Poor database performance / intermittent hangs caused by scanning of memory for stack unwinds (linked Bug 4727131). Bug 4686909 RDBMS: ORA-1482 from convert function when used anywhere other than a select list. Bug 4619452 RDBMS: ORA-600 [koklGetLocAndFlag1] can occur instead of ORA-1 during a LOB array insert. Bug 4690401 RDBMS: 10g introduces a special performance feature called "row shipping". However, there is no way to disable this feature for diagnostic purposes. This fix introduces an event which disables the "row shipping" feature. Bug 4868255 RDBMS: Select query which makes use of wide table select fails with ORA-7445 [kpofdr]. Bug 4573980 RDBMS: Core dump cam occur in qeesTraverseExpr using a GROUPING operator in a GROUP BY clause. Bug 4902585 RDBMS: Using APPLICATION CONTEXT, ATTRIBUTE name greater than 30 bytes and DML triggers, DELETE / INSET / UPDATE fails with ORA-00600 [510]. 10.2.0.1.0 Patch 3 (10.2.0.1.3P) 32-Bit Patch 4751539 64-Bit (Itanium) Patch 4751549 64-Bit (x64) Patch 4770480 BaseBug Abstract Fixes included for Critical Patch Update - January 2006 (Note 343382.1 / Representative Bug 4754888 / MLR Bug 4751931) 10.2.0.1.0 Patch 2 (10.2.0.1.2P) Only available in 32-Bit Patch 4751342 64-Bit (Itanium) / 64-Bit (x64) - Not available BaseBug Abstract Bug 4554846 CBO: DBMS_STATS.GATHER_INDEX_STATS can be slow for a partitioned table with bitmap indexes in 10.2 when compared to the performance in earlier releases. Bug 4652261 JDBC: Calling setNull() then setBytes() over 2K for a stream (blob) in JDBC can result in a NULL being inserted rather than the byte data. Bug 4114966 NET: If names.no_persistent_resources = true in sqlnet.ora with the fix for Bug 3306350 installed then TNSPING will core dump. Bug 4727495 ODBC: Memory allocation error executing stored procedure with a large parameter list. Bug 4309867 ODBC: ODBC help file does not open under Instant Client environment. Bug 4517846 RDBMS: Attempting to connect to a remote 10.2+ database fails if the instance has row source statistics tracing enabled. e.g.: SQL_TRACE set with EVENT:10046. 10.2.0.1.0 Patch 1 (10.2.0.1.1P) Only available in 32-Bit Patch 4667809 64-Bit (Itanium) / 64-Bit (x64) - Not available BaseBug Abstract Bug 4629844 CBO: A query involving a condition on a column which has a CHECK constraint on it where the CHECK constraint includes an OR list (e.g.: col1 in (...)) can give wrong results or dump. Bug 4629654 JDBC: ORA-12705 on JDBC connect when using a mixed language / country for the locale. e.g.: en_de. Bug 4562889 NET: A small memory leak can occur in Net (LDAP client). Bug 4577670 PLSQL: ORA-22921 when using a multi byte character set database and DBMS_DDL.WRAP with a table of varchar2's. Bug 4439465 RDBMS: ORA-600 [kdtdelrow-2] / ORA-604 may be signalled by BULK inserts in BATCH ERROR mode. Bug 4383610 RDBMS: A space may appear between each character in V$SESSION attributes if you create an environment with OCI_UTF16 and OCIAttrset OCI_ATTR_ACTION, MODULE and CLIENT_INFO Bug 4505011 XDB: Xquery variable processing can perform poorly. Bug 4529672 XDB: ORA-19276 from xquery expression containing specific namespaces. Bug 4569842 XDB: Suboptimal query plans can occur when using XMLtable(). Bug 4554682 XDB: Upload of large XML documents through FTP in to Nested Storage tables can leak memory and fail with ORA-4030. ----- Note: ----- Subject: 10.2.0.4 Patch Set - List of Bug Fixes by Problem Type Doc ID: 401436.1 Type: README Modified Date : 03-FEB-2009 Status: PUBLISHED Bugs fixed in the 10.2.0.4 Patch Set See Note 316900.1 for Support Status and Alerts affecting 10.2.0 releases. This note lists the customer bugs fixed in the 10.2.0.4 Patch Set. Bugs are listed by product. RDBMS (Server) bugs are listed under significant headings relating to either a feature or a characteristic of the bug. Some bugs are listed in more than one section. Each bug number is hyperlinked to a Support Bug Description. '*' against a bug indicates that an alert exists for that issue. '+' indicates a particularly notable bug. 'P' indicates a port specific bug. "OERI:nnnnn is used as shorthand for ORA-600 [nnnnn]. The term "Undocumented" is used to indicate bug fixes for which there is no published description of the issue/fix. Notable exceptions and omissions Enterprise Manager / Database Control fixes are NOT listed. Port specific bug fixes are not usually listed . Security Alert Issues fixed in the 10.2.0.4 Patch Set Fixed Bug# Security Alert# Document Summary 10.2.0.4 - / - Note 467881.1 Critical Patch Update (Apr 2008) 10.2.0.4 Bug Categories Oracle Server ANSI Joins ASSM Space Management (Bitmap Managed Segments) Advanced / Secure Networking Advanced Queuing Analytic SQL (Windowing etc..) Application Context Automatic Memory Management Automatic Storage Management (ASM) Bitmap Indexes Change Data Capture Cluster Ready Services / Parallel Server Management Code Improvement Compressed Data Storage Compressed Key Index / IOT Connect By / Hierarchical Queries Constraint Related Corruption Corruption (Dictionary) Corruption (Incorrect / Missing Corruption Checks) Corruption (Index) Corruption (Logical) Corruption (Physical) DBVerify Utility Database Link / Distributed Datapump Export/Import Datatypes (AnyData) Datatypes (LOBs/CLOB/BLOB/BFILE) Datatypes (Objects/Types/Collections) Datatypes (TIMESTAMP) Deadlock Diagnostic Output Problem / Improvement Direct Path Operations Domain Indexes Excessive CPU Usage Export/Import Expression Filters / Rules External Tables Flashback Function Based Index (Including DESC Indexes) Gateways / Heterogeneous Services Gateways / ODBC Gateways / Transparent Gateway For DRDA Gateways / Transparent Gateway For SQL Server Global Temporary Tables Globalization Support (NLS) Hang (Involving Shared Resource) Hang (Process Hang) Hang (Process Spins) Hash Join Index Organized Tables (IOT) Install Is Not Performed Correctly Instance May Crash Instance Startup Interoperability (Between Releases) JDBC JavaVM / JSP / Corba etc.. Job Queues LDAP / Oracle Internet Directory Latch Contention Leak (Memory Leak / Growth) Leak (Resources Eg: File Handles) Literal Replacement (CURSOR_SHARING) LogMiner Memory Corruption Merge SQL (MERGE .. USING) Migration / Upgrade / Downgrade Multi Table Insert SQL NCOMP NUMA Related Network OCCI OCI Online DDL Optimizer Optimizer (Stored Outlines) Optimizer (Subquery Factoring - WITH clause) Optimizer Bad Cardinality Oracle Data Mining Oracle Disk Manager Oracle Label Security Oracle OLAP Oracle Text (Formerly interMedia Text) Oracle Univeral Installer PL/SQL PL/SQL (DBMS Packages) PL/SQL External Procedures (EXTPROC) Parallel Query (PQO) Partitioned Tables Performance Affected (General) Performance Monitoring Performance Of Certain Operations Affected Performance Of Query/ies Affected Physical Standby Database / Dataguard Pro* Precompiler Query Rewrite (Including Materialized Views) RAC (Real Application Clusters) / OPS RMAN (Recovery Manager) Read Only Tablespace/s Recovery Recycle Bin Regular Expressions Resource Manager Row Level Security / FGA SQL*Loader Security ( Authentication / Privileges / Auditing ) Shared Pool Affected Shared Server (formerly MTS) Space Management (Locally Managed Tablespaces) Spatial / Spatial Advisor Spatial Data Star Transformation Star Transformation With Temp. Tables Storage Space Usage Affected Streams / Logical Standby System Managed Undo (SMU) Transparent Application Failover Transparent Data Encryption Transportable Tablespaces Triggers Truncate Wallet Manager Workload repository / reporting Wrong Results Wrong/Bad Shared Cursor XA / Distributed Transactions XDB XML Error May Occur Internal Error May Occur (ORA-600) Process May Dump (ORA-7445) / Abend / Abort Miscellaneous Notable change of behaviour introduced in 10.2.0.4 Notable change of behaviour introduced in 11.1.0.6 PL/SQL Oracle Database Gateway for DRDA SQL*Plus Precompilers Oracle Net Services Oracle interMedia Oracle Text Advanced Networking Option Oracle Database Gateway for WebSphere MQ Oracle Internet Directory Oracle Database Configuration Assistant Oracle Database Gateway for Sybase Oracle ODBC Driver JPublisher Oracle Spatial Oracle Ultra Search Oracle Database Upgrade Assistant JDBC Oracle Security Service Oracle Application Server 10g Oracle XML Developers Kit Net Manager - NetMgr Oracle OLAP Oracle Globalization Development Kit 10.2.0.4 Bug Fixes by Category Oracle Server ANSI Joins 4204383 Dump [kkqtnlocbk] optimizing ANSI OUTER JOINs with subqueries 4702830 OERI[kkoljt1] when using star transformation with an ANSI outer join 4901291 Wrong results with left outer joins on view with a function 5188321 wrong results (no rows) from ANSI outer join 5590396 Dump or Wrong Results with ANSI JOINS and CONNECT BY 5652086 OERI[15160] from ANSI join 5765958 OERI[qcscpqbTxt] / OERI[qcsfbdnp:1] from ANSI query in PLSQL 5964193 OERI[kkqsRewriteCorrCols-1] during query rewrite with ANSI joins 5988085 Dump [kkodsel] from STAR transformation with ANSI view 6006457 Suboptimal plan from ANSI outer join 6033480 High parse time of query when using ANSI style joins ASSM Space Management (Bitmap Managed Segments) 5530583 ASSM managed INDEX updates can be slow compared to non-ASSM 5557421 Self-deadlock (ORA-60) on FB enqueue if session killed during INSERT in ASSM 5637976 ORA-8103/ORA-1410 from concurrent INSERT / export on ASSM tables 5695131 HW enqueue deadlock / OERI:1153 from array insert with SAVE EXCEPTIONS to READ ONLY ASSM segment 5728380 DML may spin under ktspffc searching for space in ASSM segment 6075487 OERI[kddummy_blkchk] for DDL on plugged ASSM tablespace with FLASHBACK 6086497 OERI[ktspgetmyb-1] / bitmap segment corruption for ASSM segments 6376915 HW enqueue contention for ASSM LOB segments Advanced / Secure Networking 4395849 ESM tool hangs connecting to directory server on SSL port 5079968 SSL auth client connections create erroneous trace files in udump 5584798 Unnecessary trace files using EUS with LDAP_DIRECTORY_PASSWORD='PASSWORD' 6005762 SYS_CONTEXT('USERENV','AUTHENTICATION_METHOD') returns NULL Advanced Queuing 4478139 ORA-28031 "maximum of 148 enabled roles" when creating queue table 4618808 AQ operation requiring exclusive lib cache lock may hang 4715375 OERI[kwqmtdel] in q00 process in RAC when any instance goes down 4719848 Streams DELETE_ERROR does not maintain AQ$_QTABLE_I 4733582 Upgrade to 10.2 deletes statistics on AQ tables 4745691 OERI[kghufree_06] from AQ propogation of XML payload 5018886 OERI:[kwqitnmptme:wait] in Qnnn during propagation of delayed messages 5092843 Dump (kpceclose) in EMON 5095889 PGA leak during propagation in "kwqpcbk:koioalm" and "kwqpcbk:csid" 5225596 AQ propogation does not work after failover 5358598 EMN0 not posted for ha notification 5408664 Messages not marked as undeliverable after transformation failure 5415506 ORA-4020 when dbms_aqadm.purge_queue_table and select are run 5439588 Notifications not delivered when client machine has multiple NICs 5452715 OERI[kwqbgqc: bad state] reported after restart of database 5494866 PLS-302 'dbver_10i' importing 10g export into 9i with AQ 5506702 Dequeue delay experienced after reconfiguration 5523578 DBMS_AQADM.add_subscriber fails with ORA-1925 "maximum of x roles exceeded" 5526245 "ksxplookup: warning cnh incarnation number" messages in QMNC trace 5545530 EMON may spin in kpcopen 5561130 Performance of long running transaction using AQ degrades over time 5580871 AQ bytes message <= 2000 bytes incompatible between PLSQL and Java 5590163 Message dequeued more than once from single consumer queue 5594352 JMS-120 / OCI-1858 when dequeueing AQ bytes message with JDBC-OCI 5605319 Cursor leak from QMON coordinator exceptions 5608198 Memory leak by advanced queuing XML transformation 5648610 ORA-25235 during AQ propagation 5654680 JMS worker thread does not end if exception thrown in onMessage() method 5655612 AQ$_PENDING_MESSAGES table can grow indefinitely 5666374 FIFO does not occur when multiple listens are followed by dequeues 5717536 Dequeue can suffer from a memory leak 5725109 Hang if AQ listener onMessage() method raises an error 5734276 Queue slave process may spin in kwqitptm 5751016 AQ messages enqueued at non-owner instance not moved from WAIT to READY 5758963 UGA memory leak possible from AQ dequeue 5852253 ORA-25316 from AQ after rollback to savepoint with loopback database link 5857313 OERI[kwqbmcrcpts101] after drop propagation 5941601 TM deadlock from concurrent dbms_aqadm_sys.alter_subscriber() 5955596 DBMS_AQ.LISTEN hangs after datapump has executed 5962680 Dump[kwqicgsubname1] on an AQ enqueue call 6001290 Node down events not posted in AQ when node leaves the cluster 6016707 OERI[kwqpuspse0-hwmack] from propogation 6044513 Cannot dequeue a message with a correlation padded with spaces 6049324 Memory leak from array dequeue 6057422 ORA-25228 occurs every 30 seconds in racgimon session trace file 6065604 DBMS_AQ.DEQUEUE_ARRAY PGA memory leak 6143688 node startups cAN spend up to 2 mins in AQ partition code 6154655 QMON fails to update queue table affinity for several minutes after failover Analytic SQL (Windowing etc..) 4436832 False ORA-979 "not a group by expression" with literal replacement 4587572 ORA-12801/ORA-60 possible from parallel DML with grouping sets 4597871 ORA-904 from query using CUBE 5162852 Dump from FIRST / LAST aggregations on a NULL table 5196061 Dump in evaopn2() from WITH query using WINDOW functions 5216642 Dump from SQL using window functions 5286826 Wrong results from complex view merge with windowing 5302124 Join Predicates are not push inside window functions -- superceeded fix 5638080 Wrong sort order using window functions 5641873 ORA-904 using a WITH clause that includes a UNION 5670585 OERI [kxfxsSendCounter1] / OERI [15574] / spin from WINDOW query 5847881 ORA-3001 from GROUPING SET query against a view containing a function 5906937 Wrong result using ROW_NUMBER in SQL using a WITH query block 5942097 OERI:qernsRowP from SQL with GROUP BY , ROLLUP and DISTINCT aggregates 6012053 OERI [qctcte1] from GROUPING SETs query 6026281 OERI[qeshCloseHTI.2] from spreadsheet query 6051782 Wrong results using GROUPING SETS with ORDER BY and DISTINCT Application Context 4902585 OERI[510] and ORA-28106 using application context over 30 bytes long 6005762 SYS_CONTEXT('USERENV','AUTHENTICATION_METHOD') returns NULL Automatic Memory Management 4433838 Resizing cache crashes instance with OERI[kmgs_pre_process_request_6] 5702177 Instance crash from OERI[kghchoose_grow_1] 6528336 Automatic SGA may repeatedly shrink / grow the shared pool Automatic Storage Management (ASM) 5526987* ASM instance hang / OERI [2103] on DB instance. This bug is alerted in Note 468572.1 5081798+ Additional diagnostics for OERI[2103] when ASM involved 6453944+ ORA-15196 with ASM disks larger than 2TB 6051728P* HPUX Itanium: Cannot use ASM (ORA-15059). This bug is alerted in Note 434500.1 4110313 ASM disk resize fails for OS devices grown after ASM instance startup 4319031 Wrong header_status in V$ASM_DISK when disk is offline 4380450 Unbalanced space usage if diskgroup has only two disks, both of different size 4431215 "backup archivelog all delete input" from RMAN removes ASM directory 4489948 ASM hangs during a parallel mount and shutdown in RAC 4708822 OERI[kfiounidentify01] from PMON 4767278 OERI[kcrrupirfs.20] archiving redo to standby with ASM 5230765 LGWR spins while waiting for 'log file parallel write' using ASM 5471453 OERI[kfkfilrqarr01] using ASM 5472917 DBVERIFY may error if ASM disk disconnected 5483613 OERI [kfgscAcquireLcl_6] in ASM 5502365 OERI [kfcDel20] in ASM 5504989 PMON dump [kfgGlobalClose] / instance crash 5554692 Error ORA-15196 reporting ASM block header invalid ora-15196 after ORA-600[kfcgetbuffer10] 5555908 OERI[kghstack_underflow_internal_2] in kfrcsoDelete 5556674 V$ASM* dynamic views leak cursors (ORA-01000) 5571643 OERI:[kfclAttachBuffer10] in ASM 5575584 Failure of an entire failure group is detected one disk at a time 5576584 Poor ASM parallel read performance 5682184 OERI[kfdAuDealloc2] from resize/drop more than 16TB ASM file 5743325 ASM instance fails with OERI[kfaDropCOP04] 5757711 ORA-15080 during file creation / resize on ASM with HARD 5757752 OERI:kghstack_alloc / OERI:kfcbCkpt04 / ASM crash 5761185 ORA-15041 diskgroup space exhausted after adding disks to a diskgroup 5891737 Dump (kcblsod) / OERI:723 / Memory leak in ASM/RAC 5893614 Full table scan very slow on ASM 5899033 SMON dump (kfrCheckCtx) diskgroup instance recovery 5909894 ASM datafile lost after rename (ORA-1157) 5922733 ASM dump in kfkdumprq with event=15199 level=1050631 5939241 Inconsistent diskgroup configuration after rejected DISK OFFLINE 6013983 ASM signals OERI [kfdasecondaries01] / [kffrelocate87] during rebalance 6069360 DBW can spin in kfcRunnableWaiter holding a latch in ASM 6139547 Shadow process leak on ASM instance when diskspace exhausted (ORA-20) 6334552 Hang / ORA-4031 / OERI:kfrcsoDelete_3 on rollback of ASM file resize 6597063 OERI [kfrpass2_03] can occur in ASM 6655999 ASM instance hangs on clssgsgetmemberpublicinfo 6674196 OERI / buffer cache corruption using ASM, OCFS or any ksfd client like ODM Bitmap Indexes 4596807 OERI[6002] on update statement with concurrent ONLINE rebuild of bitmap indexes 4697632 OERI[atbbjie2] from exchange partition with bitmap join indexes 5063279 OERI[kdibllockrange:not validated] updating a partitioned bitmap index 5113934 PQ slave dump in qerixGetKey() when using bitmap index access 5262017 Query on partitioned table with bitmap index gives OERI[qernsRowP] 5331374 OERI [kdiblsorget:rowidIllegal] updating partitioned table with row migration 5401876 wrong results when optimizer uses "BITMAP CONVERSION" over "BITMAP OR" 5449488 Suboptimal plan for SQL with negated predicates (BITMAP MINUS) 5667683 Parse of query can spin in kkosbn 5960268 Dump (kkoiodoi) when FIRST_K_ROWS considers bitmap index 6694548 Suboptimal execution plan using bitmap full index scan Change Data Capture 5165904 Materialized View DDL may execute when it should wait 5252389 CDC apply changes lead to maximum open cursors exceeded (ORA-1000) 5533982 Updated columns set to null show old not-null values in change table using async CDC 5693948 ORA-31466 error when setting up CDC with table names using multibyte characters 5881493 CDC ordered sequence causes large performance degradation on RAC 6064864 Archives containing DDL for not replicated objects take longer to process 6314151 '1/1/1988 0:0:0' in COMMIT_TIMESTAMP$ column when CDC apply error is re-executed Cluster Ready Services / Parallel Server Management 6001843P cluvfy error during CRS post installation check 5667023P+ Linux: CRS does not start after applying 10.2.0.3 5495242PI HPUX: CRS may not install 5845104PI Win64: 10.2.0.3 OPMD.EXE does not work 3602716 EVMD unable to detect EOF while reading configuration file 4440013 CRS startup of RAC fails when FSFO enabled 4566428 cluvfy displays duplicate names in the output 4574574 crs_start opens a physical standby database as opposed to mounting the instances 4587300 Improve CRS shutdown sequence 4598992 "Action script for resource 'ora.xxx.vip' stdout redirection" errors in crsd.log 4692561 cluvfy reports a failure if ssh banned enabled 4882822 Service failover blocked on VIP 4906820 EVMD deadlocks on disconnect 4930431 Failure of 1 CSSD can hang starting CSSD on other nodes 4951464 CRS shutdown stops and then restarts EVMD 4996577 CVU does not recognise long device names 5003881 Value of restart_attempts wrong after DB policy is changed 5014134 Improved diagnostics for oclsomon (do not overwrite log file) 5093126 FCF does not respond to SRV_PRECONNECT events 5101517 VIP does not failover with auto_start=2 5125957 Cannot start CRS after CRS ugprade 5129769 CLUVFY check subsystems which are not configured 5131219 CSS shuts down the node when disk IO is suspended momentarily 5137401 oprocd logfile is cleared after a reboot 5168043 VIPCA silent mode cannot handle upper case characters in hostnames 5169752 SRVM OCR keys not security consistent with respective CRS resources 5184535 PRKR-1008 from SRVCTL ADD INSTANCE / DBCA 5188493 crsd.bin can use excess CPU on reboot 5192194 CSS does not start on one of the nodes ("takeover aborted due to unknown nodes") 5207138 Add support for 'toc' for reboot in HPUX 5220760 Dump in NetLocalGroupGetMembers 5236370 OCR cache invalidation error with delete key operation 5274513 VIP,ONS,GSD check fails in cluvfy when nodename is in capital letters 5278777 CRSD version is 10.2.0.1 after applying 10.2.0.2 patchset 5297925 Disabling one instance disables restart of all the instances in the node 5303454 Better diagnostics when CSS voting disk IO hangs but later resumes 5334170 racgevtf can dump in lmmstfree 5334661 ocssd.log refers to non-existing node 0 5336797 EVMD and CSSD core files are overwritten 5338035 PRKR-1008 using DBCA to create RAC instance 5348062 A 500 ms delay can occur until CSS starts reconfiguration after vendor CM reconfiguration 5365683 CRS repeatedly stops and restarts VIPs while recovering multiple nodes 5377165 Dump from crsctl when invalid parameters are passed 5388818 cluvfy should not use remote shell for local node 5437462 CSS does not monitor vendor clusterware network 5442229 VIP does not failover when public LAN disconnected pulled (crsd communicating on public LAN) 5442867 Deadlock can occur by terminating multiple CSS clients 5446160 RLB information cannot be forwarded 5448707 Better tolerance of CRS init scripts to low system resource conditions 5451987 CSSD could run as root if oracle_user not set 5454307 CLWS OCSSD dump during startup 5454388 OPROCD dumps with fix for bug 5015469 5458333 racgimon should do more checking for connections 5461281 Reconfiguration delayed due to diskping seen after reboot was issued 5467456 Directory $ORA_CRS_HOME/crs/auth was unexpectedly removed 5479767 CLWS instance going down not noticed for 10 min 5487604 CRSD core dump 5488977 scls_process_spawn provides insuficient diagnostics on execve() failure 5503111 racgimon startd <dbname> uses a lot of CPU 5507883 CRS install fails in CRS root.sh due to node panics 5513471 cluvfy needs easy to parse output for each nodes status 5529659 OCSSD fails to join the cluster 5533311 crsctl debug log res:<name> does not check name 5549682 High CPU usage by srvctl 5553318 CRSD dump before node rebooted when killed CSSD in CRSD master 5555728 Some peer-to-peer connections between EVMD's not established properly 5556681 OCR does not correctly compare OCR configurations 5568399 CRS upgrade can corrupt OCR 5601369 OCSSD dump in clssgmmbrdatacmpl() 5623137 CSS time out during reconfiguration (timeout in clssgmMasterCMSync) 5629557 CRS does not receive reconfig from CSS on SAN failure 5651085 Session disconnection blocks service resource stop action 5664042 Internal change to diagcollection.pl script 5668854 CRSD may dump if resource unregistered/re-registered as it starts 5679560 Unexpected node reboot on death of "init.cssd fatal" 5690258 Default VIP check_interval should be less than 60 seconds 5698321 Wrong return code from srvctl from failed "modify nodeapps" operation 5709121 CRS startup can hang 5734797 CSSD abort possible from concurrent startup 5735507 Dump in procr_open_key 5735768 killed ocssd.bin on a node causes other nodes's crsd restart 5736843 WaitOnEvictions can wait too long (another misscount) 5843485 Unnecessary VIP failback trial makes VIP unavailable for 14s on network down 5852975 Shared storage check does not discover shared disks 5853909 CSSD permission problems (skgxninit errors in CSSD log) 5854172 VIPCA fails with exception thread main error 5855383 CRS bundle patch does not apply on some platforms 5858733 cvu checks for exact package versions 5861703 CSSD failure 139 and node reboot if nfs mounted voting disk is remounted 5862719 init.crsd does not set a high file limit on all platforms (notable Linux) 5893629 crsd dumps after being unable to delete backup OCR file 5901176 Memory corruption in CLSC async connect handling 5901254 Starting node cannot join the cluster 5903964 EVMD does not shut down when OCR is corrupted 5911174 Hang in CLSC in nsevwait 5911855 Split brain resolution can fail 5929527 racgimon dump in clsrcwrft() during instance startup 5929833 OCR cannot determine the latest update 5932861 VIP does not switch over when CRS is stopped 5938788 False split brain 5949311 False split brain result 5974219 Cluster hang when node dies during reconfig 6001290 Node down events not posted in AQ when node leaves the cluster 6005526 CSS will not shutdown evmd.bin with fix for bug 5442229 6022204 oprocd enhanced error reporting mechanisms 6029676 OPEN/CLOSED messages from userid 0 after CRS shutdown 6051925 racgimon dump under slzgetevar -> getenv 6054978 Locked resources are not recovered by CRSD even once they are unlocked 6057422 ORA-25228 occurs every 30 seconds in racgimon session trace file 6087596 OCR can hang 6114137 Running LMS in real-time can cause CSS crash and node reboot 6117687 CRS slow memory leak from repeated "crsctl check crs" 6134126 OCR backup can fail 6655999 ASM instance hangs on clssgsgetmemberpublicinfo Code Improvement 5238255 Timezone changed data in CSV format 5245494 Improved control over whether star transformation is performed 5614566 Enh: Allow library cache heaps to be purged manually 5932060 Enh: Add support for direct SQL on partitioned table/index 5933469 ORA-20 does not show in any trace / alert 5966238 Better diagnostics for OERI[kcbgtcr_1] 6022204 oprocd enhanced error reporting mechanisms 6875865 Database instrumentation for OCM Compressed Data Storage 4061534 OERI[krvtadc] / dump in capture mining redo for COMPRESSed table 4600946 Dump / OERI[kghstack_free1] on array insert to COMPRESSed table 5496041 OERI[6006] / index corruption on compressed index 5577788 Block corruption / OERI:6585 updating row in compressed block 5599596 Block corruption / OERI [kddummy_blkchk] on clustered or compressed tables 5621677 Logical corruption with parallel update on compressed partition 5912350 Dump (kdr9ir2f0rst4srp0) on select of compressed table having > 255 columns 6268371 ORA-12996 / ORA-12998 / corruption from ALTER TABLE DROP UNUSED COLUMNS CHECKPOINT Compressed Key Index / IOT 4545196 Corrupt index leaf from cross platform transport of compress-key indexes 5034323 Dictionary corruption when adding a subpartition to a table with a key compressed local index Connect By / Hierarchical Queries 4770292 Wrong results from CONNECT BY query on IOT with secondary index/es 5033488 Dump in kokmrwo from CONNECT BY 5061079 Poor CONNECT BY plan 5065418 CONNECT BY performance degrades when temp space needed on disk 5119354 OERI from CONNECT BY and correlated START WITH columns 5126645 OERI [kkqtcorcbk: correlated string no] from CONNECT BY 5150562 Dump expCheckExprEquiv from pipelined function in hierarchical query 5211863 Poor plan for CONNECT BY 5225168 Dump (evaopn2) from CONNECT BY 5234379 Dump in qknlazopn() from hierarchical query 5254539 OERI[qkacon:FJfsrwo] on executing hierarchical query 5371149 OERI[qctcte1] from query with CONNECT BY 5391575 OERI:[qkaconCompareOpn:dty] from CONNECT BY with HAVING clause 5487686 Wrong results from CONNECT BY query 5488174 Dump [evaopn2] on a CONNECT BY query 5507887 Wrong results for CONNECT BY using CONNECT_BY_ISLEAF 5526851 Wrong Results (missing rows) on CONNECT BY when using function-based index 5590396 Dump or Wrong Results with ANSI JOINS and CONNECT BY 5594381 OERI[qkacon:FJswrwo] from CONNECT BY query 5837795 Wrong results / OERI from cost based CONNECT BY 5847521 Hierarchical (CONNECT BY) query on IOT returns wrong results 5854634 OERI[qkshtQBGet:1] from CONNECT BY query 5872956 Slow or Wrong Results on CONNECT BY queries with constant predicates 5882372 Wrong results from CONNECT BY 5903581 Wrong Results with "Connect By with Filtering" 6027610 Wrong results from CONNECT BY query 6333108 Wrong results (duplicates) from CONNECT BY query Constraint Related 4580190 Bulk insert to partitioned table can insert constraint violating rows 4618715 Dump inserting into a view with OLS policy on tables 4620832 Dump in kzrtppg with multiple referential constraints and OLS policy 4771851 Dump (kxccsrw) from INSERT .. AS SELECT / MERGE 5324773 Constraints using LTRIM() may fail for valid data 5462687 CHECK constraint can cause wrong results 5472523 Non violated deferred CHECK constraint fails (ORA-2290) at COMMIT 5504961 ORA-2292 slow to be signalled with many child rows 5579055 Dump (kxccres) updating view with instead of trigger 5766196 ORA-942 on schema level import of table with foreign key and XMLSchema 5923497 Select with constraints fails with OERI[12863] Corruption 6453944+ ORA-15196 with ASM disks larger than 2TB 4201573 ALTER SYSTEM RESET of an spfile parameter can corrupt the SPFILE 4344935 OERI from DML on TEMPORARY TABLE after autonomous TRUNCATE 5690593 Datafile corrupt for ASM datafiles copied using xdb/ftp 5892080 updateXML corrupts repeating elements 6075487 OERI[kddummy_blkchk] for DDL on plugged ASSM tablespace with FLASHBACK 6086497 OERI[ktspgetmyb-1] / bitmap segment corruption for ASSM segments 6132301 OERI[kcb_pre_apply_1] when db_block_checksum is set to FULL Corruption (Dictionary) 5034323 Dictionary corruption when adding a subpartition to a table with a key compressed local index 5632050 OERI[kkpolpd12] / dictionary corruption from CONCURRENT partition DDL 5936058 Corrupt metadata from tablespace transport 6136074 ORA-4068 / ORA-4065 ORA-6508 on VALID objects 6436867 Recompilation may skip compilation of some dependent objects (ORA-4068) Corruption (Incorrect / Missing Corruption Checks) 3569503 PQ may signal a false ORA-8103 under load Corruption (Index) 4545196 Corrupt index leaf from cross platform transport of compress-key indexes 5179313 INSERT /*append parallel*/ can corrupt an index 5181547 Index corruption after insert-only merge /*+ append */ into table 5496041 OERI[6006] / index corruption on compressed index Corruption (Logical) 5686711+ Wrong cursor may be executed if schemas have objects with same names 3419260 Silent truncation on insert via DB link from single to multibyte charset 4193047 Sequences / synonyms / indexes not created in logical standby database 4580190 Bulk insert to partitioned table can insert constraint violating rows 4714295 It is possible to drop an OLS group which is still in use in an existing label 4883635 MERGE (with delete) can produce wrong results 4904743 ALTER SESSION SET NLS% does not work if OCI_PARSE_ONLY used 4933222 Apply update of clob in multibyte charset double spaces characters 4959294 DBMS_XMLSTORE does not follow CHAR based semantics 5019803 Wrong data inserted for INSERT INTO .. SELECT DISTINCT with DEFAULT values 5024737 Streams LCRs may be filtered when using distributed commit SCN 5087369 logical standby potential data loss during failover 5104257 SQLLoader truncates nested table columns 5165904 Materialized View DDL may execute when it should wait 5182679 INSERT as remote SELECT using CASE can produce wrong data 5190543 Wrong timestamp from oracle.sql.TIMESTAMPLTZ near daylight savings transition 5256791 Trigger "UPDATING('col')" clause can return TRUE when column not updated 5352587 Triggers not working correctly with timestamp datatype 5436371 Image corruption / spin loading multiple nested objects in multibyte 5515703 Streams table diverges after partial rollback on primary 5554692 Error ORA-15196 reporting ASM block header invalid ora-15196 after ORA-600[kfcgetbuffer10] 5567934 NCHAR literal replacement can produce corrupt N literals 5577788 Block corruption / OERI:6585 updating row in compressed block 5588615 Single source streams with DML handler duplicates CLOB column value 5616820 Triggers using :OLD values of TIMESTAMP columns see :NEW values instead 5621677 Logical corruption with parallel update on compressed partition 5685411 Updating columns to NULL in a trigger may have no effect 5872835 Multiple trigger execution from SERIAL insert as Parallel select 5873852 sqlldr inserts character data longer than the column length (CHAR length semantics) 5874989 Datapump import can load data longer than column definition 5936058 Corrupt metadata from tablespace transport 6329316 Wrong number of rows inserted by ARRAY insert into partitioned table with concurrent DDL Corruption (Physical) 6646613* IOT corruption after upgrade from <= 9.2 to >= 10g. This bug is alerted in Note 471479.1 4450606+ LOB corruption / ORA-600 [ktsbvmap1] when updating a LOB 5363584+ Array insert into table can corrupt redo 4592596 Corruption (ORA-1410) from multi-table insert with direct load 4899479 Undo/redo corruption if distributed transactions used 5599596 Block corruption / OERI [kddummy_blkchk] on clustered or compressed tables 5609096 MERGE / UPDATE to IOT can cause corruption 5636728 LOB corruption / ORA-1555 when reading LOBs after a SHRINK operation 5909894 ASM datafile lost after rename (ORA-1157) 5941030 Datapump import can produce corrupt blocks when there is a LONG / LONG RAW 6268371 ORA-12996 / ORA-12998 / corruption from ALTER TABLE DROP UNUSED COLUMNS CHECKPOINT 6674196 OERI / buffer cache corruption using ASM, OCFS or any ksfd client like ODM DBVerify Utility 5031712 DBV reports blocks "soft corrupted" blocks as bad 5472917 DBVERIFY may error if ASM disk disconnected Database Link / Distributed 3419260 Silent truncation on insert via DB link from single to multibyte charset 4311273 ORA-2064 using MERGE statement over a database link 4351422 Dump from CREATE TABLE AS SELECT (CTAS) over DB link 4373687 SET_SCHEMA_INSTANTIATION_SCN does not error if database link unavailable 4490782 Unparse operations give wrong date for BC TO_DATE literals 4491223 Dump selecting ROWID with a remote join 4581334 Cursors accessing remote tables may be repeatedly rebuilt and not used 4624183 ORA-1017 reported using DB links with IDENTIFIED EXTERNALLY accounts 4648039 PLSQL hangs with database links and autonomous_transaction 4658456 ORA-920 from distributed query using CASE against remote table/s 4701527 Cursors not shared when executing procedures over a dblink 4768022 ALTER TABLE can fail with ORA-60 4865959 Wrong results / exception from Java Stored Procedure accessing data over DBLINK 4889807 False ORA-904 from co-located join (over database link) 4899479 Undo/redo corruption if distributed transactions used 4913460 Soft parsing re-occurs for select using database link 5015321 OERI[qerrmObnd1] [932] using binds with some functions over a DBLINK 5015547 Cannot create a materialized view over a database link (ORA-942) 5024737 Streams LCRs may be filtered when using distributed commit SCN 5128933 Dump from DBMS_SQL selecting TIMESTAMP data over a database link 5182679 INSERT as remote SELECT using CASE can produce wrong data 5216523 OERI[16608] from create materialize view on remote table with objects / types 5223587 OERI[4400] from distributed PDML with DDL 5245451 Intermittent ORA-904 referencing remote objects columns 5246372 OERI[opidsii1] accessing remote database accessing 3rd remote database 5299546 ORA-942 from create materialized view with join between local and remote tables 5327132 Wrong results from colocated OUTER join over DBLINK with TO_DATE 5354469 Poor performance of remote fetch with high fetch counts 5405345 OERI[kkofkrMarkK] when running a query using a database link 5455632 Dump accessing tables over a database link 5467520 PLSQL errors accessing synonym to remote object 5509293 Query with subquery across DB link has poor performance 5852253 ORA-25316 from AQ after rollback to savepoint with loopback database link 6028753 ORA-907 / ORA-933 from DML over database link 6029071 Wrong results from distributed SQL with OUTER joins 6145525 Dump selecting > 34 columns from HS (FDS) Datapump Export/Import 4352110 ORA-39125 from expdp/impdp of triggers with nulls in WHEN clause 4517481 ORA-904 / ORA-20000 loading metadata with IMPDP using varying width characterset 4595736 ORA-6502 during impdp due to wrong logging_level put in export dump 4660745 TABLESPACE GROUP clause not generated by DBMS_METADATA.GET_DLL 4996004 EXPDP fails with ORA-31642 when NLS_SORT=binary_ci and NLS_COMP=ansi 5027003 ORA-39068 from EXPDP if parallel > 1 5071931 Datapump import with remap tablespace and schema is very slow 5095025 ORA-4030 (kxs-heap-c,temporary memory) using expdp 5120780 Long text for job gets EXP-85 ORA-6502 on dbms_sched_job_export 5135951 ORA-22337 on import if database schema has been evolved 5152232 EXPDP loses global index parameters for local domain indexes 5157602 Datapump export/import modifies the chains created with dbms_scheduler 5220845 Large packages imported via data pump are not shipped to logical standby 5292551 IMPDP slow when importing a table with initialized column of type varray 5352426 Data pump import dumps (lxinitc) 5464834 ORA-4030 (kxs-heap-c,temporary memory) using EXPDP 5472417 EXPDP on RAC fails with ORA-39014 / ORA-12801 (error signaled in parallel query server) 5502124 ORA-39096 importing 10.1 EXPDP file with 10.2 data pump 5515882 ORA-1427 from EXPDP 5548895 OERI [OCIKCallPush: deprecated] from EXPDP of ANYDATA column 5550618 Dump [nszgclient] from EXPDP 5555463 Slow performance of datapump IMPORT with small LOBs 5576865 Dumps in strlen/kpodpmop/kpodpp errors during IMPDP 5590185 Consistent export data pump job (flashback_time) has poor performance 5620375 PLS-103 from datapump import of dbms_scheduler jobs with PLSQL_BLOCK 5632683 EXPDP / IMPDP may error for DDL modified tables 5680970 ORA-39001 when attempting to export partition defined as an object type 5713912 ORA-39125 / ORA-6502 from datapump import via network 5714205 EXPDP / IMPDP do not support long lists for parameters 5718757 ORA-31693 / ORA-6502 during datapump net import 5857884 EXPDP fails with ORA-39125 / ORA-6502 5874989 Datapump import can load data longer than column definition 5875568 IMPDP can error on create table in multibyte with ORA-39125 / ORA-6502 5891213 ORA-6502 / LPX-7 from DBMS_METADATA.GET_DDL with domain index present 5910237 EXPDP / DBMS_METADATA has wrong syntax for for nested table with row movement enabled 5941030 Datapump import can produce corrupt blocks when there is a LONG / LONG RAW 5972794 EXPDP via network_link with parallel > 1 fails with KUP-4038 6063940 Datapump export / import does not handle tablespace groups 6080303 Datapump export does not unload data until all metadata unloaded with PARALLEL > 1 6140330 imp / impdp cannot create object views with circular dependencies 6379123 EXPDP/IMPDP ORA-39083 due to changes in MERGE privilege between 10.1 and 10.2 Datatypes (AnyData) 4531589 ORA-22370 when passing sys.anydata containing collection to a method 5307199 OERI:OCIOpaqueDataLoad1 can occur using ODCI with AnyData / AnyDataSet 5350076 Anydata and timestamp can loose precision 5548895 OERI [OCIKCallPush: deprecated] from EXPDP of ANYDATA column Datatypes (LOBs/CLOB/BLOB/BFILE) 4450606+ LOB corruption / ORA-600 [ktsbvmap1] when updating a LOB 4559728 Select lob from view loops / OERI [17059] if synonym dropped 4583442 ORA-22877 during move hash partition with LOB 4680009 Insert LOB data fails with ORA-3106 or ORA-8176 4745114 OERI[kolrrdl:0rfc] using temporary LOBs in PLSQL 4865755 OERI[9999] during DBMS_LOB operation 4933222 Apply update of clob in multibyte charset double spaces characters 5051432 DBMS_LOB does not execute with the privileges of the calling procedure 5176017 Exp/imp loses "RETENTION" settings of LOB columns 5196175 OERI[kghstack_underflow_internal_1] with supplemental logging for LOBS 5374820 Client side dump on import of table with more than one LOB column into 32k block size 5396550 Spin in ktsplbfmb holding HW enqueue during LOB segment management 5413989 OCIStmtSetPieceInfo() does not work for piece sizes > 16777180 5442534 Dump in kokscold assigning NULL to CLOB 5447395 Shared server tied to session when BFILE used 5472702 ORA-1403 during SQL Apply of redo from table import (redo issue) 5500044 ORA-44203 on table_x_x child from concurrent LOB append and drop partition 5510345 ORA-22282 with LOB buffering enabled 5549410 Inconsistent characters read returned from OCILobRead 5555463 Slow performance of datapump IMPORT with small LOBs 5560256 Multi threaded OCI program hang when calling OCILobLocatorAssign 5588615 Single source streams with DML handler duplicates CLOB column value 5636728 LOB corruption / ORA-1555 when reading LOBs after a SHRINK operation 5644951 OERI[rworupo.2] querying outline LOB with ORDER BY clause 5654094 ORA-3106 for SQL with RETURNING clause with indicator binds 5666733 LOB segment does not use free space from freelist in RAC database 5674184 ORA-22282 when using LOB buffering 5676637 OERI[17114] using EMPTY_CLOB() in a trigger 5682121 Multithreaded OCI clients do not mutex properly for LOB operations (ORA-21500 [17099]) 5721994 Unexpected errors from non blocking OCI LOB calls 5723140 Temp LOB space not released after commit 5723260 Logminer slow / excess memory use processing batch inserts with LOBs 5870781 DBMS_LOB.INSTR() function does not find patterns across the 4gig boundary 5879179 ORA-22925 from CSSCAN when reading CLOB data 5926074 OERI [12333] on update of more than one CLOB column 5941355 "Split partition" does not move LOB to correct tablespace 5974207 Unexpected ORA-1031 from LOB access - affects NCOMPed PLSQL 6148212 Dump [qmuhshget_internal] can occur accessing LOBs 6315913 ORA-3106 for SQL using BLOBs after TAF failover 6376915 HW enqueue contention for ASSM LOB segments Datatypes (Objects/Types/Collections) 4309607 ALTER TYPE CASCADE fails adding attributes to various types 4554026 Pinning TDO may fail for extensibility types 4583492 Dump possible using ADT columns when table has many columns 4643723 After type evolution extracting attributes gets OERI[17280] 4691237 High "library cache" latch gets from SQL using objects in PLSQL 4726702 ALTER TYPE may dump (koktupd_dplvl) due to a REF dependency 4895068 Dump [kopxccc] during pickling 5022188 Direct SQLLOAD of partitioned object table of non final types fails 5076729 OERI[pmucitnxt] doing type manipulation 5104257 SQLLoader truncates nested table columns 5135951 ORA-22337 on import if database schema has been evolved 5182299 Dump on grant / revoke of privileges on a TYPE 5192858 DROP TABLE with object type column with statistics can dump (kknerd) 5216523 OERI[16608] from create materialize view on remote table with objects / types 5225836 DROP TYPE .. VALIDATE dumps for large partitioned table 5292551 IMPDP slow when importing a table with initialized column of type varray 5368266 ORA-904 using multiple TABLE() objects in the FROM clause 5436371 Image corruption / spin loading multiple nested objects in multibyte 5520937 Cannot upgrade images for dictionary types to 8.1 image format 5577046 ADD or DROP attribute causes UNION query to fail with ORA-1790 5721821 SGA corruption / Dump[kglobcl] / crash if objects dropped / recreated 5725761 Objects with debug privilege are not shown in the ALL_OBJECTS view 5763434 Spin in kokes2q when sorting on VARRAY column over 4k long 5763538 Wrong results / dump with object type column in SQL 5841624 OERI[kokeicadd2] accessing object with embedded substitutable attributes 5910237 EXPDP / DBMS_METADATA has wrong syntax for for nested table with row movement enabled 6029647 ORA-12714 accessing typed column from TABLE() function 6118038 OERI[koputilcvto2n] on an ALTER TYPE 6140330 imp / impdp cannot create object views with circular dependencies 6145841 OERI[kologsf2] on COLLECT(..) with wrong datatype 6150438 COLLECT() does not work correctly for ADTs residing in different schemas 6452485 SGA memory corruption / OERI [17182] with fix for bug 6085625 Datatypes (TIMESTAMP) 4992603 TIMESTAMP.timestampValue(Calendar) does not exist 5126270 Version 3 TIMEZONE check script (utltzuv2.sql) 5128933 Dump from DBMS_SQL selecting TIMESTAMP data over a database link 5190543 Wrong timestamp from oracle.sql.TIMESTAMPLTZ near daylight savings transition 5238255 Timezone changed data in CSV format 5350076 Anydata and timestamp can loose precision 5350339 ORA-979 using TIMESTAMP in triggers and GROUP BY clause 5352587 Triggers not working correctly with timestamp datatype 5417281 oracle.sql.DATE looses a year when constructed from BC Timestamp 5468695 TIMESTAMPTZ wrong near daylight switch 5616820 Triggers using :OLD values of TIMESTAMP columns see :NEW values instead 5632264 Version 4 TIMEZONE files 5688685 JVM timezone changes for Western Australia December 2006 (superceeded) 5726033 timezdif.csv for version 4 timezone files 5865568 JVM timezone changes (version 4 timezone data for JVM) 5885079 Incorrect output from INTERVALDS.stringValue() for negative intervals 5910187 No bind peeking for implicit string bind to timestamp 5923970 Include objects/nested tables in utltzuv2.sql 5961654 ldiinterfromtz returns wrong offset during DST fallback 5973217 OCCI::intervalds object attribute uses day precision for fractional seconds 6156762 OCCI fractional seconds portion can be wrong Deadlock 5907779+ Self deadlock hang on "cursor: pin S wait on X" (typically from DBMS_STATS) 4441119 Not enough information dumped when RAC detects a deadlock 4587572 ORA-12801/ORA-60 possible from parallel DML with grouping sets 4768022 ALTER TABLE can fail with ORA-60 5334733 Deadlock resolution can be slow in RAC 5415506 ORA-4020 when dbms_aqadm.purge_queue_table and select are run 5454831 RAC deadlock possible on working set latches 5470095 Self deadlock should provide more targeted diagnostics 5485914 Mutex self deadlock on explain / trace of remote mapped SQL 5557421 Self-deadlock (ORA-60) on FB enqueue if session killed during INSERT in ASSM 5604698 Deadlock between 'library cache lock' and 'library cache pin' using Streams 5685189 Self deadlock on dc_objects after DBMS_SPACE.UNUSED_SPACE errors 5695131 HW enqueue deadlock / OERI:1153 from array insert with SAVE EXCEPTIONS to READ ONLY ASSM segment 5883112 False deadlock in RAC 5941601 TM deadlock from concurrent dbms_aqadm_sys.alter_subscriber() 5983020 MMON deadlock with user session executing ALTER USER 5998048 Deadlock on COMMIT updating AUD$ / Performance degradation when FGA is enabled 6057351 AWR deadlock between Mxxx processes during snapshot purging process 6267208 OERI:2103 due to deadlock between PV enqueue and "slave class create" latch 6496514 RAC deadlock between "libary cache lock" and TX enqueue Diagnostic Output Problem / Improvement 5963785P HPUX: Missing Short Stack in tracefiles 3995047 Explain plan does not show a part of the execution path 4995756 Enhanced diagnostics for index code 5385614 Need diagnostics for OERI:ktrviupk_4 5470095 Self deadlock should provide more targeted diagnostics 5696474 Diagnostic enhancement for ORA-600 errors on global temporary tables 5721941 Additional diagnostict for OERI[kgmgchd1] 5843585 Additional diagnostics for "ges inquiry response" RAC hangs 5854415 RAC diagnostic enhancement for corrupt messages 6155905 Additional diagnostics Direct Path Operations 5022188 Direct SQLLOAD of partitioned object table of non final types fails 5179313 INSERT /*append parallel*/ can corrupt an index 5181547 Index corruption after insert-only merge /*+ append */ into table 5228136 ORA-26065 from SQLLDR direct path load of objects containing a LOB and constraints 5510918 Log miner slow mining direct load redo 5941030 Datapump import can produce corrupt blocks when there is a LONG / LONG RAW 5944227 SQLloader direct path load into IOT can dump [kdblldrp] 5953355 OERI[klaprs_30] / OERI[klaprs_10] during SQLLOADER direct path load 5973648 ORA-54 during concurrent parallel direct SQLLOAD in RAC Domain Indexes 4566516 Transportable tablespace does not handle domain indexes 4644425 SGA corruption on UPDATE with functional domain index 5136863 OERI from join between partitioned table and domain index 5152232 EXPDP loses global index parameters for local domain indexes 5228074 OERI[12455] raised from SQL with DOMAIN index when FOR UPDATE option is used 5252061 PGA memory corruption / OERI[17456] creating a domain index 5307199 OERI:OCIOpaqueDataLoad1 can occur using ODCI with AnyData / AnyDataSet 5370332 ODCITableFetch fails with ORA-28579 5403398 Dump when costing user defined operators / functions 5530761 ORA-1031 from EXP of domain index 5656948 Dump returning collection from ODCIAggregate 5891213 ORA-6502 / LPX-7 from DBMS_METADATA.GET_DDL with domain index present 5908945 Dump [qxopqdca] with ancilliary operator Excessive CPU Usage 6455161+ Higher CPU / Higher "cache buffer chains" latch gets / Higher "consistent gets" after truncate/Rebuild 4605569 LCK may accumulate CPU time on one instance 4697189 High CPU usage for large sorts 5362897 Non linear CPU increase when adding more shared server sessions 5399325 Mutex latch spin causes high CPU on non-CAS platforms 5471994 LCK may accumulate CPU time when SMON does Serial Transaction recovery 5530958 Larger SGAs and SQL in long running transactions can use excess CPU in ktaifm 5734276 Queue slave process may spin in kwqitptm 5896963 High LGWR CPU and longer "log file sync" with fix for bug 5065930 5958244 LMS processes running in realtime can spin 6001617 LCK may accumulate CPU time / ORA-4031 possible 6356566 Memory leak / high CPU selecting from V$SQL_PLAN (affects statspack) 6407273 LGWR spins during slow log switch Export/Import 3370858 Import fails (ORA-932) using FROMUSER / TOUSER for schema based xmltype 4038803 IMP-3 / ORA-1722 when using nls_numeric_characters != '.,' 4328909 Resource plans and resource groups not imported during full import 4559546 Cannot used exp/imp of MVIEW with XMLTYPE column 4912371 Dump possible in kohrsmc() 5120780 Long text for job gets EXP-85 ORA-6502 on dbms_sched_job_export 5176017 Exp/imp loses "RETENTION" settings of LOB columns 5349808 IMP-60 hit when importing a table with an XML schema based XMLType column 5374820 Client side dump on import of table with more than one LOB column into 32k block size 5391326 ORA-942 importing functional indexes as SYS 5402151 ORA-439 when importing into Standard Edition db using streams_instantiation=y 5494866 PLS-302 'dbver_10i' importing 10g export into 9i with AQ 5530761 ORA-1031 from EXP of domain index 5664206 ORA-6502 during export of functional index expression over 4k 5766196 ORA-942 on schema level import of table with foreign key and XMLSchema 5872788 ORA-29821 importing OPERATORS 6140330 imp / impdp cannot create object views with circular dependencies Expression Filters / Rules 6349820 Expression filter indexable attributes truncates length to 500 characters External Tables 4644351 OERI[15819] / wrong results from parallel select 5195356 Dump (memcpy) under kudmprcbk() when accessing external table 5600425 wrong results from select on external table 5676948 OERI [qxxmslSelectLocator_10] from SQL*Loader Flashback 4459574 FLASHBACK_TRANSACTION_QUERY shows multi row INSERT as SELECT as only one row 5172559 ora-600's during reinstate of logical standby after fast-start failover 5209867 ORA-38777 is thrown by MRP when flashback through resetlogs 5225733 After flashback operation, new logs are not applied in logical standby 5385614 Need diagnostics for OERI:ktrviupk_4 5486023 "GLOBAL CACHE ELEMENT DUMP" in LMS trace with FLASHBACK 5891280 MRP0 on standby may not start (OERI:krfg_aset_1) 5933838 Database crash (ORA-449) after ALTER DATABASE FLASHBACK OFF in RAC 5949116 Flashback logs are not purged when archiver is out of disk space 6010833 Recovery following flashback does not utilize changes in online redo log 6075487 OERI[kddummy_blkchk] for DDL on plugged ASSM tablespace with FLASHBACK 6168063 High "Flashback buf free by RVWR" waits 6406880 System hang possible after killing processes when waiting for flashback logs 6768069 Cannot FLASHBACK DATABASE on RAC physical standby Function Based Index (Including DESC Indexes) 4619997 Function based index may not be used for INLIST predicate 4916783 Wrong results from query using INLIST predicate if FUNCTION BASED index 5377092 Wrong results from FAST FULL SCAN of an index on a CASE expression 5391326 ORA-942 importing functional indexes as SYS 5513123 DUmp [kkfies] from SQL using functional indexes with subqueries 5526851 Wrong Results (missing rows) on CONNECT BY when using function-based index 5574966 Dump (evaopn2) or Wrong Results with views and function-based index 5619833 Dump (qerixGetKey) from query rewrite on join including functional index 5664206 ORA-6502 during export of functional index expression over 4k 5686412 Dump (evaopn2) from query using functional index 5698193 Wrong Results when using TRIM on check constraints or function based indexes. 5796376 Dump [kkobrak] from index join with a FUNCTION based index 5843316 Wrong results with index join and function-based index 5860221 Apply aborts with OERI[17147] / memory corruption with FUNCTION BASED index 5889331 Dump from cost based optimization of INSERT .. SELECT with function based index Gateways / Heterogeneous Services 3197358 Dump when DBMS_HS_RESULT_SET is fetched out of sequence 4767996 Dump in HS with very long TNS connect string 4864563 HS does not send to_number predicate to HS database 4998706 Gateway agent trace does not work 5175364 Data truncation / null data selecting NVARCHAR2 over TG4MSQL 5229137 PLS-201 compiling program units referencing tables on RDB 5489166 INSERT SQL over HS may error 5550614 Wrong results selecting BIGINT data from MySQL using MySQL ODBC driver 5601756 HS does not supply size for large objects (ORA-28500) 5610906 HSODBC dump invoking Data Dictionary translation query multiple times 5738652 Intermittent lost RPC connection when executing FDS stored procedure 5898868 SELECT FOR UPDATE errors over HS to Teradata 5900857 ORA-23619 from HS log based replication 5935527 Cursor leak with fix for bug 5260266 6053772 Dump [kpubsuuc] for SQL over HS using binds 6145525 Dump selecting > 34 columns from HS (FDS) Gateways / ODBC 5385973 ODP.NET gets truncated char/varchar data in HSODBC environment Gateways / Transparent Gateway For DRDA 5877437 TG4DRDA gets sqlcode=-102, sqlstate=54002 using concat function Gateways / Transparent Gateway For SQL Server 4552393 Heterogenous apply fails for updates with WHERE .. IS NULL 5733637 Select for update fails against TG4MSQL 5844876 ORA-28550 from TG4SYBS Global Temporary Tables 4344935 OERI from DML on TEMPORARY TABLE after autonomous TRUNCATE 4736557 ORA-1466 on read only transaction 5081271 PMON may crash the instance with OERI:kcblibr_1 during temp table cleanup 5689991 ORA-8176 fetching from global temporary table with INSERTS between fetches 5696474 Diagnostic enhancement for ORA-600 errors on global temporary tables Globalization Support (NLS) 3419260 Silent truncation on insert via DB link from single to multibyte charset 3945156 ORA-979 from DBMS.GATHER_TABLE_STATS when NLS_COMP=LINGUISTIC 4346448 NLS_COMP = ANSI gives wrong results comparing CHAR with VARCHAR2 4517481 ORA-904 / ORA-20000 loading metadata with IMPDP using varying width characterset 4730249 Logical Standby or Adhoc query fails with ORA-1801 when using a different characterset 4904743 ALTER SESSION SET NLS% does not work if OCI_PARSE_ONLY used 4905638 Wrong results / errors in session that opens the database for certain NCHAR characterset 4933222 Apply update of clob in multibyte charset double spaces characters 4959294 DBMS_XMLSTORE does not follow CHAR based semantics 4996004 EXPDP fails with ORA-31642 when NLS_SORT=binary_ci and NLS_COMP=ansi 5017909 V$SQL / V$SQLAREA.SQL_FULLTEXT corrupt for multibyte 5120476 No blank padding with multibyte charset if no character set conversion 5126270 Version 3 TIMEZONE check script (utltzuv2.sql) 5128625 OERI[17147] / OERI [17182] / NULL result from NLSSORT 5175364 Data truncation / null data selecting NVARCHAR2 over TG4MSQL 5252496 Wrong result when using a LIKE predicate with NLS_COMP = LINGUISTIC 5257698 9idata NLS files missing leading to file handle leak 5259741 DBMS_XMLGEN.CONVERT trims output for multibyte database 5285966 Dump [lxhlod] on select passing NULL for NLS parameter to a function 5326327 OERI[qctbyt : bfc] using NLS_LENGTH_SEMANTICS=CHAR 5436371 Image corruption / spin loading multiple nested objects in multibyte 5444175 glb files created in gdk_custom.zip by ginstall are ignored by Java 5494008 Wrong results from LIKE in multibyte when NLS_COMP=linguistic and NLS_SORT=binary_ci(ai) 5526851 Wrong Results (missing rows) on CONNECT BY when using function-based index 5567934 NCHAR literal replacement can produce corrupt N literals 5576865 Dumps in strlen/kpodpmop/kpodpp errors during IMPDP 5594352 JMS-120 / OCI-1858 when dequeueing AQ bytes message with JDBC-OCI 5604120 Performance problems after applying calendar deviation 5632264 Version 4 TIMEZONE files 5685296 Logical apply stops with PLS-103 due to NLS_NUMERIC_CHARACTERS setting 5693948 ORA-31466 error when setting up CDC with table names using multibyte characters 5712086 OERI[17147] / dump from TO_CHAR(date) with over long FORMAT string in multibyte 5757315 Spin possible comparing 2 strings with monolingual sort (NLS_SORT) 5838153 CAST operator does consider NLS_LENGTH_SEMANTICS 5873852 sqlldr inserts character data longer than the column length (CHAR length semantics) 5875568 IMPDP can error on create table in multibyte with ORA-39125 / ORA-6502 5879179 ORA-22925 from CSSCAN when reading CLOB data 5903706 ISO2022-JP-OUTLOOK has no mapping for the katakana middle dot character 5985257 Wrong results from UTL_I18N.TRANSLITERATE using 'hwkatakana_fwkatakana' 6168288 Dump instead of ORA-1863 6357601 Romanian base letter mapping missing for some characters 6460895 CSSCAN may hang / run slowly 6494820 CSSCAN fails with ORA-1455 on tables with more than 2^31-1 blocks Hang (Involving Shared Resource) 5526987* ASM instance hang / OERI [2103] on DB instance. This bug is alerted in Note 468572.1 4489948 ASM hangs during a parallel mount and shutdown in RAC 5057695 SHUTDOWN IMMEDIATE can be slow 5079641 Switchover hangs attempting to recover a log file from a previous primary 5188493 crsd.bin can use excess CPU on reboot 5230765 LGWR spins while waiting for 'log file parallel write' using ASM 5376770 Spin in kcldle in RAC can cause a cluster hang 5387017 Primary hang when physical standby "shutdown immediate" 5688403 'IPC Send timeout' error just after 'flush_cache' event in RAC 5931789 Database hang possible as CKPT cannot get controlfile enqueue (CF) 5955955 DWB may spin when collecting object level statistics with concurrent DDL 6069360 DBW can spin in kfcRunnableWaiter holding a latch in ASM 6310591 DB hang with CKPT waiting for enquiry response in RAC 6406880 System hang possible after killing processes when waiting for flashback logs Hang (Process Hang) 5898210+ Hang from concurrent MV refresh and library cache invalidation in RAC 5907779+ Self deadlock hang on "cursor: pin S wait on X" (typically from DBMS_STATS) 3140249 Data guard broker hangs when standby listener is down 4618808 AQ operation requiring exclusive lib cache lock may hang 4648039 PLSQL hangs with database links and autonomous_transaction 4927753 GRANT / ALTER USER can hang 4930431 Failure of 1 CSSD can hang starting CSSD on other nodes 5023410 QC can wait on "PX Deq: Join ACK" when slave is available 5166735 DBMS_SCHEDULER "EXECUTABLE" jobs with large amounts of data output to STDERR can hang 5225733 After flashback operation, new logs are not applied in logical standby 5378806 xa_rollback cannot interrupt a long running SELECT branch 5382088 Fast start failover can hang on broker MIV mismatch 5392993 DDL can hang if EXPLAIN PLAN issued previously for the same DDL statement 5396550 Spin in ktsplbfmb holding HW enqueue during LOB segment management 5399901 Archived log entries can take a long time to search in Dataguard 5444539 Database connections not released after database failover or recycle 5454831 RAC deadlock possible on working set latches 5500044 ORA-44203 on table_x_x child from concurrent LOB append and drop partition 5503590 Logminer Adhoc can hang or error mining logs from a RAC database 5511675 OCCI hang in terminateStatelessConnectionPool 5560256 Multi threaded OCI program hang when calling OCILobLocatorAssign 5567141 OERI[526] / hang with fix for bug 5508574 installed with > 31 CPUs 5602452 Capture gets stuck in 'dictionary initialization' after recovery 5604698 Deadlock between 'library cache lock' and 'library cache pin' using Streams 5654680 JMS worker thread does not end if exception thrown in onMessage() method 5725109 Hang if AQ listener onMessage() method raises an error 5746223 Old primary hangs after a FSFO and prevents automatic reinstatement 5955596 DBMS_AQ.LISTEN hangs after datapump has executed 5974219 Cluster hang when node dies during reconfig 5983020 MMON deadlock with user session executing ALTER USER 6013968 Hang / OERI:504 with patch for bug 5863519 installed 6019084 RAC hang possible when node leaves the cluster with fix for bug 5844816 6057351 AWR deadlock between Mxxx processes during snapshot purging process 6144079 Instance crash in RAC (OERI:2103) 6334552 Hang / ORA-4031 / OERI:kfrcsoDelete_3 on rollback of ASM file resize 6496514 RAC deadlock between "libary cache lock" and TX enqueue Hang (Process Spins) 6110331+ OERI[kcbget_37] / OERI[1100] / spin possible 5452672P A database hang can occur (DBW spin) 3551896 Dump / spin from SELECT on V$SESSTAT 4387531 Spin running XPATH on SB table with IOT structured varrays 4553025 Large inserts into hash clustered tables can spin 4605569 LCK may accumulate CPU time on one instance 4697189 High CPU usage for large sorts 4699720 MMON or PMON spin in RAC 5369855 OERI:733 or Spin (qksopLogSame) from star transformation 5376770 Spin in kcldle in RAC can cause a cluster hang 5417292 Query compilation may spin in kkogtp 5436371 Image corruption / spin loading multiple nested objects in multibyte 5471994 LCK may accumulate CPU time when SMON does Serial Transaction recovery 5484652 QMNC process spin in Streams 5545530 EMON may spin in kpcopen 5631915 Select from V$ views using X$KGLLK can spin 5667683 Parse of query can spin in kkosbn 5670585 OERI [kxfxsSendCounter1] / OERI [15574] / spin from WINDOW query 5718007 Spin (in qcopxla / qcopx0la) with OR predicates on PARTITION key columns 5728380 DML may spin under ktspffc searching for space in ASSM segment 5734276 Queue slave process may spin in kwqitptm 5757315 Spin possible comparing 2 strings with monolingual sort (NLS_SORT) 5763245 Parse may spin in kkpapRTPRuningSetup 5763434 Spin in kokes2q when sorting on VARRAY column over 4k long 5952530 Spin / hang after cluster reconfiguration 5955955 DWB may spin when collecting object level statistics with concurrent DDL 5958244 LMS processes running in realtime can spin 6001617 LCK may accumulate CPU time / ORA-4031 possible 6041084 Spin during parse of query with INLIST against list partition key 6069360 DBW can spin in kfcRunnableWaiter holding a latch in ASM 6084108 Dump / CPU spin possible after an ORA-3115 6460895 CSSCAN may hang / run slowly 6640950 Update of LONG can cause Streams capture to spin / spill 6753486 PMON spins if dead process hold library cache mutex Hash Join 5383936+ Wrong results from Parallel Query with OUTER join and HASH join 4540971 Hash group by significantly over allocates memory and breaks V$SQL_XX statistics 4566991 Hash group-by is not reported in v$sql_workarea_active 5376015 Wrong results with hash semijoin when build rows do not fit in memory/Spill to disk 5759075 Wrong results from PQ with HASH on ANSI CHAR join 5893340 OERI [32695] [hash aggregation can't be done] from hash aggregation 5947623 Excess PGA memory used by hash joins Index Organized Tables (IOT) 6646613* IOT corruption after upgrade from <= 9.2 to >= 10g. This bug is alerted in Note 471479.1 4387531 Spin running XPATH on SB table with IOT structured varrays 4719798 DBMS_STREAMS_ADM.maintain_schemas incorrectly requests supplemental log for IOT with overflow 4725385 DBMS_STATS on partitioned IOT with additional indexes can be slow 4770292 Wrong results from CONNECT BY query on IOT with secondary index/es 5236908 Primary key index not used for IOT 5255455 DML error logging not working for primary key violation with insert on IOT table 5494240 OERI[15201] during select from an IOT 5558244 OERI[kcbnew_3] can occur 5567937 False ORA-1 / ORA-1403 from logminer rolling back IOT redo 5609096 MERGE / UPDATE to IOT can cause corruption 5685645 Logminer does not support IOT with OVERFLOW if table has been altered 5847521 Hierarchical (CONNECT BY) query on IOT returns wrong results 5924538 Logical standby apply fails with ORA-1427 for operations on IOTs 5944227 SQLloader direct path load into IOT can dump [kdblldrp] 6070548 Dump (qertbGetPartitionNumber) / wrong results from bitmap access to IOT Install Is Not Performed Correctly 6051728P* HPUX Itanium: Cannot use ASM (ORA-15059). This bug is alerted in Note 434500.1 5495242PI HPUX: CRS may not install 5845104PI Win64: 10.2.0.3 OPMD.EXE does not work 5161782 Dump installing XDB 5507883 CRS install fails in CRS root.sh due to node panics Instance May Crash 5605370* Various dumps / instance crash possible. This bug is alerted in Note 454464.1 6017420* OERI[kcbo_link_q_1] / crash with fix for bug 5454831 installed. This bug is alerted in Note 453309.1 6656824P DBW can crash with fix for bug 6087207 installed 4422686 LMD/LMS cannot be frozen during reconfig 4433838 Resizing cache crashes instance with OERI[kmgs_pre_process_request_6] 4744529 OERI:kclpred_1 / crash possible in RAC 5081271 PMON may crash the instance with OERI:kcblibr_1 during temp table cleanup 5118012 Instance crash with OERI[kclswrite_3] with multiple DBW processes 5118272 Instance crash with ORA-600 [1433], [60] due to lgwr filling up msg blocks (Messages could be for LGWR or ARCH) 5131219 CSS shuts down the node when disk IO is suspended momentarily 5190596 LMON dumps LMS0 too often during DRM leading to IPC send timout 5324905 nsprecv() can corrupt the SGA when using shared servers 5375583 LMS process dies with OERI[kclexpandlock_1] 5377099 Dump [kksfreeheap] / OERI:504 / SGA corruption / crash possible 5384248 OERI[k2gtelock: !k2gtca] / instance crash cleaning up distributed transaction 5412994 Dump in ksrchconnect_ctx leading to instance crash 5476873 Instance crash due to PMON ORA-601 / OERI[ksudlp1] 5504989 PMON dump [kfgGlobalClose] / instance crash 5512921 Instance crash caused by SMON OERI[kcblus_1] / dump 5554692 Error ORA-15196 reporting ASM block header invalid ora-15196 after ORA-600[kfcgetbuffer10] 5578157 Instance crash with ORA-600 [1433] (RSM has all message blocks) 5587421 LMS fails with OERI [kjmpmsg_1] 5600050 LMON may fails with OERI [kjbrref:pkey] during DRM 5690100 RAC instance crash with OERI[kjbmpwrite:wip2] 5702177 Instance crash from OERI[kghchoose_grow_1] 5721821 SGA corruption / Dump[kglobcl] / crash if objects dropped / recreated 5730717 OERI:kclchkinteg_18 / LMS crashes the instance 5736850 SGA corruption / crash from PQO bloom filter 5757752 OERI:kghstack_alloc / OERI:kfcbCkpt04 / ASM crash 5762514 DBWR crashes instance with OERI[kcbbctsc_3] 5863519 Instance crash due to LMS dump (in kclcsr) 5899033 SMON dump (kfrCheckCtx) diskgroup instance recovery 5933838 Database crash (ORA-449) after ALTER DATABASE FLASHBACK OFF in RAC 5962344 Dump from Logminer due to stack corruption under krvtgct_GetColumnTranslation 5983403 PMON may crash the instance with OERI[kksStatsRecovery-Bad-Opcode] 6005113 OERI[kclrwrite_7] in DBWn process followed by instance crash in RAC 6013983 ASM signals OERI [kfdasecondaries01] / [kffrelocate87] during rebalance 6018125 Instance crash during dynamic remastering or instance reconfiguration 6035614 Instance crash / dump [kghunphy] with fix for bug 5922239 6075582 OERI[kjbmpref:sh] / dump [kjmpbmsg] in LMS causing instance crash 6144079 Instance crash in RAC (OERI:2103) 6239052 LMS can crash instance with OERI[kjbrchkinteg:last] 6271689 RAC instance crash possible 6501007 DRM sync timeout in RAC 6674196 OERI / buffer cache corruption using ASM, OCFS or any ksfd client like ODM Instance Startup 5752399P+ Sol: Mandatory Patch to use Oracle with Veritas or Solstice Disk Suite on Solaris 4440013 CRS startup of RAC fails when FSFO enabled 4771560 Open resetlogs can fail with ORA-1667 5087787 ORA-29702 starting RAC with large buffer cache 5247609 RMAN slow performance during register database/open resetlogs 5572026 ORA-942 / ORA-1031 in tracefile when starting the database as SYSOPER 5744546 MMON OERI [1403] 5855896 Reconfiguration takes a long time restarting instance in active/standby RAC 5857949 Startup may fail due to dump [rfmsoexinst] from DMON 6143688 node startups cAN spend up to 2 mins in AQ partition code 6781496 OERI[KGHLATCH_REG4] on STARTUP with >61 CPUs in RAC with fix for 5508574 Interoperability (Between Releases) 5933477* Client <= 9.2.0.7 / 10.1.0.4 can dump when running against higher level database. This bug is alerted in Note 455832.1 5245451 Intermittent ORA-904 referencing remote objects columns JDBC 4308334 OERI[12314] during XA commit/rollback/prepare while attached to different transaction 4992603 TIMESTAMP.timestampValue(Calendar) does not exist 5190543 Wrong timestamp from oracle.sql.TIMESTAMPLTZ near daylight savings transition 5417281 oracle.sql.DATE looses a year when constructed from BC Timestamp 5468695 TIMESTAMPTZ wrong near daylight switch 5734901 JDBC Thin XMLType.getDOM fails with SQLException 5885079 Incorrect output from INTERVALDS.stringValue() for negative intervals 5945463 XA clients should not require execute privilege on DBMS_SYSTEM 6278984 java.awt.font.glyphvector.getglyphoutline returns empty shape JavaVM / JSP / Corba etc.. 4865959 Wrong results / exception from Java Stored Procedure accessing data over DBLINK 4898765 NullPointerException from stored Java when maxAdvance of glyph computed 5074285 Dump [eorealize_xref] from stored Java using reflective methods 5258410 Dump [eoa_scan_mark_object] using stored Java threads 5372831 OERI:26599 / dumps in JVM after database has been closed for recovery / opened 5400158 OERI[17078] / dump running Java DDL (loadjava) concurrently 5688685 JVM timezone changes for Western Australia December 2006 (superceeded) 5711011 "SocketException: socket is closed" using RMI with shared servers 5862057 Oracle JVM incorrectly returns true for "x instanceof object[]" when "x" is a class 5865568 JVM timezone changes (version 4 timezone data for JVM) 5963041 Socket.shutdownOutput() closes the socket in the Oracle JVM 6065183 A dump in AccessControlContext methods in the Oracle JVM 6065728 Oracle JVM performance enhancement 6120084 Dump (eoistrnrep->strncpy) in Oracle JVM Job Queues 4552696 DBMS_Scheduler is suppressing no_data_found exceptions in jobs 4904904 Problems with DBMS_SCHEDULER JOB_START time (eg ORA-1877) 5111250 DBMS_SCHEDULER jobs fail silently with OLS / OID 5120780 Long text for job gets EXP-85 ORA-6502 on dbms_sched_job_export 5140631 V$SESSION.sql_address not set by DBMS_SCHEDULER 5157602 Datapump export/import modifies the chains created with dbms_scheduler 5166735 DBMS_SCHEDULER "EXECUTABLE" jobs with large amounts of data output to STDERR can hang 5377153 DBMS_SCHEDULER call heap memory leak when changing attributes of a job 5593617 Job scheduler cannot be used on logical standby (ORA-16224) 5620375 PLS-103 from datapump import of dbms_scheduler jobs with PLSQL_BLOCK 5928612 V$SESSION SQL_ADDRESS / SQL_HASH_VALUE not set for DBMS_JOBs LDAP / Oracle Internet Directory 4571240 ESM denies access to non-orcladmin users if anonymous binds disabled 5111250 DBMS_SCHEDULER jobs fail silently with OLS / OID Latch Contention 6455161+ Higher CPU / Higher "cache buffer chains" latch gets / Higher "consistent gets" after truncate/Rebuild 4691237 High "library cache" latch gets from SQL using objects in PLSQL 5749075 High Requests on dc_rollback_segments. latch / US enqueue contention 5918642 Heavy latch contention with DB_CACHE_ADVICE on 6333663 Shared pool latch contention due to fragmentation of large pool 6356566 Memory leak / high CPU selecting from V$SQL_PLAN (affects statspack) Leak (Memory Leak / Growth) 4475206 Excess PGA memory use with many hash joins 4540971 Hash group by significantly over allocates memory and breaks V$SQL_XX statistics 4566991 Hash group-by is not reported in v$sql_workarea_active 4587117 ORA-384 can occur even if there is free space in some pool/s 5058318 Memory leak (in "koh-kghu" heap of type "kolccst obj") 5089522 Memory leak in niotns in MRP process 5095025 ORA-4030 (kxs-heap-c,temporary memory) using expdp 5095889 PGA leak during propagation in "kwqpcbk:koioalm" and "kwqpcbk:csid" 5220562 ORA-4030 (sort subheap,sort key) on insert a partitioned table with concurrent DDL 5377153 DBMS_SCHEDULER call heap memory leak when changing attributes of a job 5377973 Register schema fails with ORA-4031 5382621 OCCI memory leak in getColumnListMetaData() 5386986 Leak / ORA-4031 leak when DROP UNUSED COLUMN issued on large partitioned table 5391505 High PGA consumption for query (kxs-heap-c) from OR expansion 5408970 Memory leak using XMLType() constructor on ADT in a loop 5464834 ORA-4030 (kxs-heap-c,temporary memory) using EXPDP 5477912 Memory leak parsing DTD 5482555 Shared server does not release memory 5485417 Memory leak of "blockers api immd" during global hang analyze 5516917 Excessive mermory usage when running a query using nested loops 5529797 PGA leak / OERI KWQPCBK179 during Streams propogation 5548510 _FIX_CONTROL parameter leaks memory in the shared pool 5556674 V$ASM* dynamic views leak cursors (ORA-01000) 5573238 Shared pool memory use / ORA-4031 due to "obj stat memo" in one subpool 5608198 Memory leak by advanced queuing XML transformation 5618049 "mvobj part des" leaked memory after partition DDL (ORA-4031) 5629416 Client memory leak after switching schema 5668025 XMLParser.Parse() can leak memory 5717536 Dequeue can suffer from a memory leak 5723260 Logminer slow / excess memory use processing batch inserts with LOBs 5758963 UGA memory leak possible from AQ dequeue 5891737 Dump (kcblsod) / OERI:723 / Memory leak in ASM/RAC 5947623 Excess PGA memory used by hash joins 6011182 Parsing of large query takes long time / memory leak / ORA-4030 /4031 6043052 Leak in perm allocations with "library cache" comments (ORA-4031) 6049324 Memory leak from array dequeue 6065604 DBMS_AQ.DEQUEUE_ARRAY PGA memory leak 6356566 Memory leak / high CPU selecting from V$SQL_PLAN (affects statspack) Leak (Resources Eg: File Handles) 4584641 Cursor leak using DBMS_XMLGEN with a PLSQL function returning sys_refcursor 4918946 OCCI terminateEnvironment can leave threads 4966024 VLM buffer leak on if an error occurs 5141429 "skgspawn 27142" errors and defunct Oracle processes 5166745 Excessive redo generation with auditing enabled 5252389 CDC apply changes lead to maximum open cursors exceeded (ORA-1000) 5257698 9idata NLS files missing leading to file handle leak 5557660 ORA-20 / process group leak from OCI Connection Pool connections 5605319 Cursor leak from QMON coordinator exceptions 5935527 Cursor leak with fix for bug 5260266 6139547 Shadow process leak on ASM instance when diskspace exhausted (ORA-20) Literal Replacement (CURSOR_SHARING) 5146740+ Wrong results with bind variables/CURSOR_SHARING 2837580 Dump if SQL has > ~35000 literals 4202503 Parse errors possible using CONTAINS with cursor_sharing=similar/force 4436832 False ORA-979 "not a group by expression" with literal replacement 4513695 Poor performance for SELECT with ROWNUM=1 with literal replacement 5155885 OERI[kkslgbv0] with CURSOR_SHARING=similar 5177766 OERI[17059] with SESSION_CACHED_CURSORS 5254759 ORA-12801/ORA-1008 occurs on a parallel query with bind variables 5364819 OERI[kkslpbp:1] when using literal replacement 5476507 OERI[15868] / OERI[15160] can occur with cursor sharing 5757106 OERI[15851] selecting aggregate of a constant with literal replacement 5762750 ORA-907 when cursor_sharing is enabled 5863277 ORA-1008 from SQL on second run when cursor_sharing=similar/force LogMiner 5035058 V$LOGMNR_CONTENTS.MineValue may not show an UNDO value 5299237 Inconsistent results from v$logmnr_contents with committed_data_only 5388885 Hang / OERI[krvxbpns01] accessing V$LOGMNR_CONTENTS from RAC 5437445 Incorrect username displayed from logminer adhoc query when auditing is on 5503590 Logminer Adhoc can hang or error mining logs from a RAC database 5510918 Log miner slow mining direct load redo 5518651 ORA-1301 from dbms_logmnr_d.build 5531784 V$LOGMNR_CONTENTS CSF may be wrong 5567937 False ORA-1 / ORA-1403 from logminer rolling back IOT redo 5685645 Logminer does not support IOT with OVERFLOW if table has been altered 5723260 Logminer slow / excess memory use processing batch inserts with LOBs 5744428 dbms_logmnr_d.build may get a downstream build failure 5888733 Wrong results from V$LOGMNR_CONTENTS referencing AUDIT_SESSIONID 5962344 Dump from Logminer due to stack corruption under krvtgct_GetColumnTranslation 6064864 Archives containing DDL for not replicated objects take longer to process 6114833 Logminer does not signal error if log unavailable in continuous_mine 6124804 Dump [krvxbpc_processcommit] selecting from v$logmnr_contents Memory Corruption 4583492 Dump possible using ADT columns when table has many columns 4644425 SGA corruption on UPDATE with functional domain index 4745691 OERI[kghufree_06] from AQ propogation of XML payload 4899479 Undo/redo corruption if distributed transactions used 5128625 OERI[17147] / OERI [17182] / NULL result from NLSSORT 5172559 ora-600's during reinstate of logical standby after fast-start failover 5252061 PGA memory corruption / OERI[17456] creating a domain index 5324905 nsprecv() can corrupt the SGA when using shared servers 5583634 OERI [17147] / dump after inserting a text node of size 64000 5671774 Memory corruption due to TDE with imported certificate 5681955 SGA corruption in RAC (OERI [17114] / OERI [17112]) 5712086 OERI[17147] / dump from TO_CHAR(date) with over long FORMAT string in multibyte 5716932 Memory corruption / OERI [17147] / dump selecting from PATH_VIEW 5721821 SGA corruption / Dump[kglobcl] / crash if objects dropped / recreated 5735091 Memory corruption when using XMLAGG 5736850 SGA corruption / crash from PQO bloom filter 5860221 Apply aborts with OERI[17147] / memory corruption with FUNCTION BASED index 5900857 ORA-23619 from HS log based replication 6136494 Capture process aborts with OERI [17112] / OERI [17147] 6143117 Rare intermittent mutex problem 6452485 SGA memory corruption / OERI [17182] with fix for bug 6085625 6674196 OERI / buffer cache corruption using ASM, OCFS or any ksfd client like ODM Merge SQL (MERGE .. USING) 4216668 Dump from INSERT / MERGE on internal columns 4311273 ORA-2064 using MERGE statement over a database link 4406211 Dump (insLoadRowInfo) from MERGE SQL with false condition 4572043 DML monitoring is incorrect for MERGE / MTI 4771851 Dump (kxccsrw) from INSERT .. AS SELECT / MERGE 5181547 Index corruption after insert-only merge /*+ append */ into table 5387478 ORA-28132 for user with EXEMPT ACCESS POLICY privilege 5609096 MERGE / UPDATE to IOT can cause corruption 5731952 MERGE statement does not insert rows if source is a (inline) view with parallel 6379123 EXPDP/IMPDP ORA-39083 due to changes in MERGE privilege between 10.1 and 10.2 Migration / Upgrade / Downgrade 6646613* IOT corruption after upgrade from <= 9.2 to >= 10g. This bug is alerted in Note 471479.1 5501528I ORA-6545 recompiling with PLSQL_WARNINGS set 5841554I OERI:kqludp2 during upgrade to 10.2.0.3 5892355I+ Upgrade to 10.2.0.3 can fail with ORA-600 [22635] 4733582 Upgrade to 10.2 deletes statistics on AQ tables 4882839 ORA-4068 / ORA-4065 after upgrade 5094908 Dump (kokbBuildExplodedTree) recompiling a view after upgrade to 10.2 5125957 Cannot start CRS after CRS ugprade 5520937 Cannot upgrade images for dictionary types to 8.1 image format 5568399 CRS upgrade can corrupt OCR 5640527 ORA-1403 running utlu102i.sql on an 8.1.7.4 database 5715079 ORA-1281 when applying a Patch Set on a logical standby 5871314 Pickler fix needed to allow some DB upgrade / downgrade to work 5947653 XE to EE upgrade fails in XDBx 5955764 OERI[kccirsd_4] during CONTROLFILE upgrade from pre 10.2 version 6052351 Dump running catupgrd.sql when creating/replacing streams$transformation_info 6379123 EXPDP/IMPDP ORA-39083 due to changes in MERGE privilege between 10.1 and 10.2 Multi Table Insert SQL 4397693 Dump (apaqba) from multi table insert with WHEN clause under RBO 4592596 Corruption (ORA-1410) from multi-table insert with direct load NCOMP 5974207 Unexpected ORA-1031 from LOB access - affects NCOMPed PLSQL NUMA Related 5173642 Data not read from cache on second execution with NUMA optimization enabled Network 4767996 Dump in HS with very long TNS connect string 4998706 Gateway agent trace does not work 5406976 Dump (lxhscn) if DB calls out over NET with a FAILOVER clause 5755010 Listener registration never completes 6083037 Server side load balancing does not work 6390420 TNS-12535 is logged twice to sqlnet.log at time-out with shared servers OCCI 4918946 OCCI terminateEnvironment can leave threads 5382621 OCCI memory leak in getColumnListMetaData() 5511675 OCCI hang in terminateStatelessConnectionPool 5956137 OCCI dumps using stack instance of pObject derived classes 5970288 OCCI isNull() on object column always returns false even when object is null 5973217 OCCI::intervalds object attribute uses day precision for fractional seconds 6156762 OCCI fractional seconds portion can be wrong OCI 4730906 "ilibociei" target in ins_rdbms.mk does not work 5120476 No blank padding with multibyte charset if no character set conversion 5131157 OCI may error reexecuting a statement against a table with an altered column type 5242942 Client dump (OCIPClearMxCtr) using stateless connection pool 5292883 Dump from OCI client using OCI7 olog() call 5413989 OCIStmtSetPieceInfo() does not work for piece sizes > 16777180 5444539 Database connections not released after database failover or recycle 5497630 ORA-3124 from NULL LONG bind for an UPDATE which matches no rows 5510345 ORA-22282 with LOB buffering enabled 5549410 Inconsistent characters read returned from OCILobRead 5557660 ORA-20 / process group leak from OCI Connection Pool connections 5558356 Bad describe information using change notification 5560256 Multi threaded OCI program hang when calling OCILobLocatorAssign 5629416 Client memory leak after switching schema 5643527 OCILobOpen/OCILobGetChunkSize do not return OCI_STILL_EXECUTING in non blocking mode 5682121 Multithreaded OCI clients do not mutex properly for LOB operations (ORA-21500 [17099]) 5683652 OCIHandleFree performance issue. PeopleTools Mandatory 5694101 OCI piecewise operation returns wrong piece length for long / long varchar data 5715788 genezi -v reports 32-bit library instead of 64-bit 5721502 Non blocking client may dump executing PLSQL 5721702 Error information may be lost in non-blocking OCI 5721994 Unexpected errors from non blocking OCI LOB calls 5722178 ORA-1002 in non blocking mode 5736739 Compressed fetching can fail in non blocking mode 5736747 Resumed OCIStmtExecute can fail in non-blocking mode 5765361 Client dump using OCIDirPathPrepare in OCI_UTF16ID mode 5932089 FAN OCI clients not aborted by OCI on public network down Online DDL 4596807 OERI[6002] on update statement with concurrent ONLINE rebuild of bitmap indexes Optimizer 599680 Unnecessary sort for SELECT DISTINCT 3748430 i_*part$, i_*part_obj$ should be created as unique indexes 3945156 ORA-979 from DBMS.GATHER_TABLE_STATS when NLS_COMP=LINGUISTIC 3995047 Explain plan does not show a part of the execution path 4204383 Dump [kkqtnlocbk] optimizing ANSI OUTER JOINs with subqueries 4215910 DBMS_STATS may use a 100% row sample size when not expected 4226736 Wrong clustering factor when DBMS_STATS.GATHER_INDEX_STATS runs in parallel 4273361 Unique index access not used with INLIST predicate 4397693 Dump (apaqba) from multi table insert with WHEN clause under RBO 4422100 Sort merge join on inequality should have control parameter 4444536 Unnecessary sorting when access made through a global index 4483240 INLIST may use suboptimal index 4513695 Poor performance for SELECT with ROWNUM=1 with literal replacement 4545802 Poor Outer Join Cardinality estimation with filters on outer table 4567767 Execution Plan changes upon rowcache reload 4581014 DBMS_STATS issues gathering SIZE AUTO / SKEWONLY 4587431 Dump (in kkqucsv) / spin from query with a multi column IN subquery predicate 4605810 Index may not be chosen to eliminate ORDER BY SORT 4619997 Function based index may not be used for INLIST predicate 4652100 Poor plan with bind peeking for SQL against LIST partitioned tables 4664788 Query with UNION can dump in kkqudhus 4684209 Dump (under evaopn2) with transitive predicate from CHECK constraint 4698023 CBO trace may treat a predicate value as 'out-of-range' 4704779 Incorrect histogram type shown (frequency/height-balanced) 4708389 Nest loop join costing ignores parallelism of index used to probe in right side 4712638 OERI[15160] / dump [kkogbro] 4724074 Small CPU performance overhead during optimization 4725385 DBMS_STATS on partitioned IOT with additional indexes can be slow 4733582 Upgrade to 10.2 deletes statistics on AQ tables 4752814 Wrong selectivity on comparision of VARCHAR2 column with CHAR variable 4868646 Dump from cost based query transformation 4872602 Sub-query is unnested even though cost is higher 4878299 Bad plan from join with FIRST_ROWS_N or a ROWNUM predicate 4899105 OERI[19004] from multi table join 4905112 CREATE OUTLINE on DML using an indexed partitioned table may dump (kauxalo) 4924149 Push predicate not working when function in the filter 5022061 Dump [kkessc] optimizing query with inequality join if INDEX SKIP SCAN considered 5040753 Optimal index is not picked on simple query / Column group statistics 5058503 Dump[kkogtp] can occur selecing ROWID from a join view 5061079 Poor CONNECT BY plan 5082178 Bind peeking may occur when it should not 5089444 Dump (kkodsel) from select with a subquery with star transformation 5101017 Trace files with "table_stats(failed sampling n)" messages 5112856 OERI[kghstack_underflow_internal_1]... [kkocxj : predtailpp] 5128368 Dump [kkoeqv] optimizing a query with nested views 5129407 Suboptimal plan for SQL with multiple OR branches 5163554 OERI[qctopn1] during join predicate pushdown 5169247 Dump (eg in qkarid) from SELECT FOR UPDATE after table elimination 5199213 Very bad plan for UNION ALL and push constant predicate / Wrong Results 5211863 Poor plan for CONNECT BY 5211984 Parse errors with USE_STORED_OUTLINES 5220356 Partition pruning predicates not cost pushed into UNION ALL views 5236881 Wrong Results (More rows) with a CONCATENATE of ANTI joins 5236908 Primary key index not used for IOT 5240607 FIRST_K_ROWS may choose inefficient NESTED LOOPS join 5245494 Improved control over whether star transformation is performed 5259048 Optimizer does not recognize/use HASH clusted index access with OR list 5263572 Wrong cardinarity for predicates of form "col like func(:bind)" 5284303 Poor plan for predicates against character columns containing numeric data 5288623 CBO may not choose the best index for ORDER BY elimination 5302124 Join Predicates are not push inside window functions -- superceeded fix 5308692 ORA-1426 error when running DBMS_STATS.GATHER_FIXED_OBJECTS_STATS 5333268 DBMS_STATS.GATHER_INDEX_STATS can be slow 5337352 OERI[kkqtcpopn: 0] during parse with subquery unnesting 5352807 CREATE INDEX with COMPUTE option does not gather statistics 5358150 Dump (apaqbd) using CAST with cost based transformation 5362021 Dump from SQL using user defined functions 5364143 Bind Peeking is not done upon query reload, Execution Plan changes 5382842 Select fails with OERI[qctcte1] using cost based transformation 5385629 Push predicate optimization does not occur 5387148 View not merged even though the cost is lower 5391505 High PGA consumption for query (kxs-heap-c) from OR expansion 5395270 OERI[qctcte1] / dump / wrong results from view merging 5396162 Suboptimal plan from ANSI query with semi join 5399282 First k rows optimization may not always pick best plan 5417292 Query compilation may spin in kkogtp 5434872 OERI[qolgenol-1] when executing dbms_outln.create_outline 5440119 Dump in kkogast 5449488 Suboptimal plan for SQL with negated predicates (BITMAP MINUS) 5454975 Dump executing DBMS_OUTLN.CREATE_OUTLINE 5468809 Predicate order can affect execution plan 5482831 Suboptimal plan with FIRST_ROWS_K or EXISTS subquery 5483301 Cardinality of 1 when predicate value non-existent in frequency histogram 5487686 Wrong results from CONNECT BY query 5488174 Dump [evaopn2] on a CONNECT BY query 5490501 Wrong Results with COALESCE or NVL2 on aggregations inside subqueries 5505157 Predicates are not pushed in UNION ALL views 5519856 Wrong cardinality from CBO for "col LIKE function(:bind)" 5526851 Wrong Results (missing rows) on CONNECT BY when using function-based index 5547058 Poor plan with old_style predicate push into UNION ALL views 5547895 No transitive predicates produced for user defined deterministic function 5548510 _FIX_CONTROL parameter leaks memory in the shared pool 5570942 Query Rewrite causes high parse time with high hits on 'latch: row cache objects' and dc_object_ids / Dump in STRLEN 5573425 Wrong results from subquery unnesting with complex view merge 5580497 Dump (kkeais) during query optimization 5585187 Wrong Results doing MERGE JOIN with a correlated subquery on the right side 5592012 Wrong results with INLIST and UNION/UNION ALL 5608992 Wrong results from filter push with OUTER join 5611962 CBO MAX/MIN optimization may not occur 5618040 FIRST_ROWS may give poor plan if index chosen to eliminate a SORT 5620485 Non code based push predicate into UNION view can get poor plan 5624216 Wrong cardinality for UNION ALL with no WHERE clause 5632128 Materialized View refresh looses statistics on primary key 5632192 Wrong Results with Max/Min in subquery/view 5634346 Multi-column INLIST may not use INLIST ITERATOR 5645718 ORA-1476 gathering statistics with DBMS_STATS 5650477 Poor plan possible due to lack of view merging 5680702 Suboptimal execution path for semi / anti join 5682441 Wrong Results (no rows) joining views with predicates using PLSQL functions 5694466 OERI[15160] from subquery unnesting 5694984 Index distinct key count scaling is wrong for first_rows(k) 5698193 Wrong Results when using TRIM on check constraints or function based indexes. 5705630 Suboptimal plan from 'or' expansion 5707754 Dump can occur executing a large query 5708897 Wrong results from ROWNUM with semi/anti join 5709414 DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO call is very expensive 5741044 Suboptimal execution plan as 1 row table not detected 5741121 Suboptimal plan for "not equals" predicates 5742678 Index range scan used to get MAX value instead of index min/max first row 5754362 Plans can change after deleting statistics on a partitioned table 5762598 Suboptimal plan due to bad cardinality for numeric string constants 5766310 Bad join cardinality is in the presence of histograms 5766450 Dump [kkomprf] when attempting STAR transformation 5796376 Dump [kkobrak] from index join with a FUNCTION based index 5837795 Wrong results / OERI from cost based CONNECT BY 5842686 Poor plan due to bad average column length for tables with LONG RAW 5843316 Wrong results with index join and function-based index 5845347 Dump [kkogbys] parsing SQL with GROUP BY 5872956 Slow or Wrong Results on CONNECT BY queries with constant predicates 5882954 Long parse time for query against tables with many partitions 5889331 Dump from cost based optimization of INSERT .. SELECT with function based index 5891471 Poor cardinality estimates with check constraints 5893396 Wrong results possible due to invalid stored outline 5903581 Wrong Results with "Connect By with Filtering" 5903829 OERI[qkshtTabInf2:1] can occur parsing a query 5913871 FGA records are written for recursive SQL under DBMS_STATS 5932203 Wrong result when comparing same column with values of different datatypes 5939115 ora-600 [kghstack_underflow_internal_1][pcols in kkpapdaextsqueryslvl] 5944076 Suboptimal plan in FIRST_ROWS(K) mode 5949981 Bad cardinality with histogram 5960268 Dump (kkoiodoi) when FIRST_K_ROWS considers bitmap index 5976822 Suboptimal plan possible 6006300 Push predicate does not occur 6007259 CBO does not consider ORA concatenation 6011182 Parsing of large query takes long time / memory leak / ORA-4030 /4031 6016075 Wrong Results for query with correlated subquery and predicate pull up 6016087 OERI[15160] from subquery unnesting 6019818 ORA-1422 from DBMS_STATS auto granularity 6020789 Dump [vopplog] pushing join predicates 6029071 Wrong results from distributed SQL with OUTER joins 6038461 Wrong results from SQL with UNION and a fast DUAL subquery 6042205 High parse time for a query using ORDER BY 6051211 Too High Join Cardinality with Histograms Present 6062266 Cardinality of 0 for range predicate and no histograms 6070954 Skip scan may be used instead of a better range scan 6075238 OERI[qctcte1] on parse of query with views / subqueries 6077514 DBMS_STATS.GATHER_FIXED_OBJECT_STATS can be slow with large buffer cache 6082745 Bad plan with fix for bug 5483301 6084811 MERGE JOIN CARTESIAN not considered 6087237 CBO may not choose best join order 6114166 Pre-10g outlines may not work in later releases 6119884 Wrong results with query with OR operator with OR expansion 6122894 Poor plan from UNION / INTERSECT views with OR predicates 6123567 Dump [kkosbn] optimizing query on partitioned table 6134565 FIRST_ROWS hint is not honored with "_sort_elimination_cost_ratio" parameter set 6151963 Wrong join cardinality with histograms 6159522 OERI[qkaffsindex3] from ANALYZE TABLE .. ESTIMATE STATISTICS 6163564 Poor cardinality from "LIKE" predicates and binds 6188881 Index selectivity adjustment for anti/semi join causes wrong index to be chosen 6239971 CBO costing can differ greatly for =< compared to < 6251917 Optimizer selects the merge join cartesian despite the hints 6350462 Incorrect index statistics scaling for first_rows(k) 6400795 Wrong results from view merging 6408017 OERI[12811] optimizing a query against fixed view/s Optimizer (Stored Outlines) 5211984 Parse errors with USE_STORED_OUTLINES 5893396 Wrong results possible due to invalid stored outline Optimizer (Subquery Factoring - WITH clause) 4702284 ORA-604 / ORA-902 from WITH clause with scalar subquery involving an object column 5073249 Dump from fast refresh of MV using "WITH .. AS" 5130732 Query using "WITH" clause can fail with ORA-942 5196061 Dump in evaopn2() from WITH query using WINDOW functions 5470034 ORA-1436 from TKPROF EXPLAIN of query using a WITH clause 5497168 Wrong results isolation_level=serializable and WITH clause 5641873 ORA-904 using a WITH clause that includes a UNION 5708633 Wrong results / dump [ldxite] from materialized WITH clause 5906937 Wrong result using ROW_NUMBER in SQL using a WITH query block 5987000 OERI:qkxrPXformQbc1 can occur for SQL using a WITH clause 6360220 ORA-21780 from subquery factoring SQL WITH clause Optimizer Bad Cardinality 4545802 Poor Outer Join Cardinality estimation with filters on outer table 4567767 Execution Plan changes upon rowcache reload 4652100 Poor plan with bind peeking for SQL against LIST partitioned tables 4752814 Wrong selectivity on comparision of VARCHAR2 column with CHAR variable 5263572 Wrong cardinarity for predicates of form "col like func(:bind)" 5284303 Poor plan for predicates against character columns containing numeric data 5364143 Bind Peeking is not done upon query reload, Execution Plan changes 5483301 Cardinality of 1 when predicate value non-existent in frequency histogram 5519856 Wrong cardinality from CBO for "col LIKE function(:bind)" 5624216 Wrong cardinality for UNION ALL with no WHERE clause 5741121 Suboptimal plan for "not equals" predicates 5762598 Suboptimal plan due to bad cardinality for numeric string constants 5766310 Bad join cardinality is in the presence of histograms 5891471 Poor cardinality estimates with check constraints 5949981 Bad cardinality with histogram 6051211 Too High Join Cardinality with Histograms Present 6062266 Cardinality of 0 for range predicate and no histograms 6082745 Bad plan with fix for bug 5483301 6151963 Wrong join cardinality with histograms 6163564 Poor cardinality from "LIKE" predicates and binds Oracle Data Mining 4509805 Model build fails with dm_nested_* and special characters 5374844 ABN model build fails using dataset in excess of 100,000 rows Oracle Disk Manager 5698225 ORA-17507 can occur using 16k block size with ODM 5909894 ASM datafile lost after rename (ORA-1157) 6377317 OERI[ksfdrfms3] using ODM if a log corruption is detected Oracle Label Security 4304023 Logical Standby does not support OLS properly 4618715 Dump inserting into a view with OLS policy on tables 4620832 Dump in kzrtppg with multiple referential constraints and OLS policy 4714295 It is possible to drop an OLS group which is still in use in an existing label 5111250 DBMS_SCHEDULER jobs fail silently with OLS / OID 5162768 Wrong results using more than one OLS policy on a table 5480607 OERI:kghstack_underflow_internal_3] from DROP_POLICY 5674756 OLS does not set selectivity of predicates causing bad execution plans 5839280 OERI[15265] dropping OLS policy Oracle OLAP 5586253 Dataload from remote table does not work using DBMS_AW (OLAP) Oracle Text (Formerly interMedia Text) 4202503 Parse errors possible using CONTAINS with cursor_sharing=similar/force 4614980 OERI:15448 from Text query 5095815 Select with CONTAINS predicate on view fails 5147225 Poor performance of parallel context query with ROWNUM predicate 5259868 Text query using index in another schema fails (ORA-20000, DRG-50857) 5677420 ORA-20000 from Text query against partitioned table 5728347 ORA-20000, DRG-10599 occurs during text query through synonym 5867231 OERI:qernsRowP on Text query with NLS_COMP / NLS_SORT set 5908945 Dump [qxopqdca] with ancilliary operator 6357601 Romanian base letter mapping missing for some characters Oracle Univeral Installer 6474976P HPUX Itanium: OUI overwrites libnmapi2.so.1 when uninstalling PL/SQL 5501528I ORA-6545 recompiling with PLSQL_WARNINGS set 2834295 ORA-12714 declaring cursor for a function that returns a table of NVARCHAR2 4493741 Cannot see SQL_TEXT for procedure calls from EXECUTE IMMEDIATE 4580190 Bulk insert to partitioned table can insert constraint violating rows 4587556 OERI:17069 compiling a package with a self referencing synonym 4609147 ORA-918 if PLSQL block has same package and function name 4648039 PLSQL hangs with database links and autonomous_transaction 4691237 High "library cache" latch gets from SQL using objects in PLSQL 4725022 Wrong results from a function call using a CONCAT of a NULL 4745114 OERI[kolrrdl:0rfc] using temporary LOBs in PLSQL 4882839 ORA-4068 / ORA-4065 after upgrade 5051432 DBMS_LOB does not execute with the privileges of the calling procedure 5076729 OERI[pmucitnxt] doing type manipulation 5118104 Dump compiling PLSQL using pseudo columns with INSERT .. RETURNING 5150562 Dump expCheckExprEquiv from pipelined function in hierarchical query 5229137 PLS-201 compiling program units referencing tables on RDB 5298826 Wrong results from SQL using DETERMINISTIC function/s 5367514 Wrong number of exceptions returned executing a bulk insert 5467520 PLSQL errors accessing synonym to remote object 5547895 No transitive predicates produced for user defined deterministic function 5564384 ORA-6502 assigning values from SQL to PLSQL variables 5685189 Self deadlock on dc_objects after DBMS_SPACE.UNUSED_SPACE errors 5721502 Non blocking client may dump executing PLSQL 5765958 OERI[qcscpqbTxt] / OERI[qcsfbdnp:1] from ANSI query in PLSQL 5847881 ORA-3001 from GROUPING SET query against a view containing a function 5933883 ORA-918 error creating a package 5934741 Dump (kgmtncch) from CALL statement with OUT CHAR arguments 5974207 Unexpected ORA-1031 from LOB access - affects NCOMPed PLSQL 6136074 ORA-4068 / ORA-4065 ORA-6508 on VALID objects 6494146 OERI [kksfbc-reparse-infinite-loop] can occur PL/SQL (DBMS Packages) 4430244+ Segment advisor can load blocks of dropped objects into buffer cache (KCB OERI errors) 4226736 Wrong clustering factor when DBMS_STATS.GATHER_INDEX_STATS runs in parallel 4552696 DBMS_Scheduler is suppressing no_data_found exceptions in jobs 4581014 DBMS_STATS issues gathering SIZE AUTO / SKEWONLY 4667479 ORA-16224 when using UTL_FILE / ORA-1031 using a DIRECTORY under GUARD ALL 4898580 DBMS_METADATA.GET_DEPENDENT_DDL does not show comments on materialized view columns correctly 5040555 DBMS_SPACE.OBJECT_GROWTH_TREND output is not correct 5128933 Dump from DBMS_SQL selecting TIMESTAMP data over a database link 5140631 V$SESSION.sql_address not set by DBMS_SCHEDULER 5333268 DBMS_STATS.GATHER_INDEX_STATS can be slow 5376783 DBMS_SPACE.OBJECT_GROWTH_TREND can perform excessive IO 5645718 ORA-1476 gathering statistics with DBMS_STATS 5672041 Wrong information returned by DBMS_METADATA 5685189 Self deadlock on dc_objects after DBMS_SPACE.UNUSED_SPACE errors 5709414 DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO call is very expensive 5842686 Poor plan due to bad average column length for tables with LONG RAW 5910237 EXPDP / DBMS_METADATA has wrong syntax for for nested table with row movement enabled 5913871 FGA records are written for recursive SQL under DBMS_STATS 5985257 Wrong results from UTL_I18N.TRANSLITERATE using 'hwkatakana_fwkatakana' 6005996 DBMS_METADATA.GET_DDL generates incorrect DDL with UNUSED columns 6017760 DBMS_METADATA.GET_DDL does not show changed datafile attributes 6019818 ORA-1422 from DBMS_STATS auto granularity 6077514 DBMS_STATS.GATHER_FIXED_OBJECT_STATS can be slow with large buffer cache 6140309 OERI[ktssupd_seg_2] from DBMS_SPACE_ADMIN.TABLESPACE_FIX_SEGMENT_EXTBLKS PL/SQL External Procedures (EXTPROC) 5120476 No blank padding with multibyte charset if no character set conversion 5130238 ORA-28583 in external procedure 6397073 Cannot open SYSDBA connection in EXTPROC callout Parallel Query (PQO) 5383936+ Wrong results from Parallel Query with OUTER join and HASH join 3569503 PQ may signal a false ORA-8103 under load 4336528 PQ may be slower than expected (timeouts on "PX Deq: Signal ACK") 4367986 Bind peeked parallel cursors do not share 4407269 Wrong result with nested loop parallel query with ROWNUM pushdown 4532105 pqsnap does not report parallelism for alter table modify lob rebuild freepools 4581220 OERI:kzaSqlTxtLob1 with fine grained auditing and parallel query 4587572 ORA-12801/ORA-60 possible from parallel DML with grouping sets 4644351 OERI[15819] / wrong results from parallel select 4753238 OERI[kxfpgetsumpms] from PQ 4755448 Dump [kxfxgf] on parallel slave processes when using PQ trace 5023410 QC can wait on "PX Deq: Join ACK" when slave is available 5024703 PARALLEL on Spatial index is ignored 5030215 Excessive waits on PX Deq Signal ACK when RAC enabled 5045992 OERI[kxspoac : EXL 1] from PQ with a numeric bind 5097836 Wrong results / OERI:15818 from parallel query with range TQ 5113934 PQ slave dump in qerixGetKey() when using bitmap index access 5161523 Wrong results / slow Parallel query due to data skew on multi-key table queues 5179313 INSERT /*append parallel*/ can corrupt an index 5223587 OERI[4400] from distributed PDML with DDL 5228711 ORA-604 trace from PQ slaves with FGA policy 5254759 ORA-12801/ORA-1008 occurs on a parallel query with bind variables 5258521 OERI[kkpapDimToLevel1] from parallel query with partitioned tables 5370626 Wrong results (more rows) on a parallel query over one partition with anti/semi join NL. 5409593 Parallel insert as select into partitioned table can dump 5455093 Wrong results from PQ with hash distribution with fixed CHAR join keys 5488790 Wrong results from Parallel Query 5566580 OERI:15817 using parallel query with a large number of columns 5571916 wrong (duplicate) values with parallel and STAR (missing "PX block iterator") 5586632 Dump (qkaGranuleIteratorTraverse) on query on partitioned tables 5611623 Parallel query slave dump (kkpapitsize) 5621677 Logical corruption with parallel update on compressed partition 5645771 No pruning for Nested Loops Join on a range-list partitioned table in parallel 5673934 ORA-12801 / OERI 15810 during parallel DML 5731952 MERGE statement does not insert rows if source is a (inline) view with parallel 5736850 SGA corruption / crash from PQO bloom filter 5759075 Wrong results from PQ with HASH on ANSI CHAR join 5872835 Multiple trigger execution from SERIAL insert as Parallel select 5903293 Wrong Results for Parallel Query using Group By or Distinct or has correlation 5910422 SESSIONS_PER_USER resource limit works inconsistently for PQ processes 5947231 Wrong results from parallel STAR query (with temp_disable) 5981212 Wrong results (SORT ORDER BY STOPKEY pushed below a FILTER) in PQ 6057203 Corruption / OERI [kcbchg1_6] from Parallel update 6158287 Wrong results from PQO with EXISTS subquery 6241497 Resource manager with PQ enabled does not use parallelism 6274465 DML / queries run serially instead of parallel when there is concurrent DDL Partitioned Tables 3748430 i_*part$, i_*part_obj$ should be created as unique indexes 4444536 Unnecessary sorting when access made through a global index 4580190 Bulk insert to partitioned table can insert constraint violating rows 4583442 ORA-22877 during move hash partition with LOB 4652100 Poor plan with bind peeking for SQL against LIST partitioned tables 4668012 Wrong results from IS_ALTER_COLUMN / IS_DROP_COLUMN for partition operations 4697632 OERI[atbbjie2] from exchange partition with bitmap join indexes 4904223 ALTER TABLE EXCHANGE PARTITION may dump / OERI 4905112 CREATE OUTLINE on DML using an indexed partitioned table may dump (kauxalo) 4959915 ORA-39083 / ORA-1647 during TTS import of a range-list partition table 5022188 Direct SQLLOAD of partitioned object table of non final types fails 5034323 Dictionary corruption when adding a subpartition to a table with a key compressed local index 5063279 OERI[kdibllockrange:not validated] updating a partitioned bitmap index 5099909 Partition not eliminated when joined to non mergeable view 5136863 OERI from join between partitioned table and domain index 5139572 OERI[qkauix2] on drop partition with parallelism 5213452 Fast refresh fails with ORA-936 after truncation of default LIST partition 5220356 Partition pruning predicates not cost pushed into UNION ALL views 5220562 ORA-4030 (sort subheap,sort key) on insert a partitioned table with concurrent DDL 5225836 DROP TYPE .. VALIDATE dumps for large partitioned table 5226383 Dump (kkpapDiGetRange) from subquery pruning with composite partitions 5245038 Wrong results with query against a list partitioned table with null partition key 5262017 Query on partitioned table with bitmap index gives OERI[qernsRowP] 5331374 OERI [kdiblsorget:rowidIllegal] updating partitioned table with row migration 5370626 Wrong results (more rows) on a parallel query over one partition with anti/semi join NL. 5397953 Dump [kkpapItgetAll] accessing partitioned table using multi column INLIST 5409593 Parallel insert as select into partitioned table can dump 5411244 ORA-4022 raised while rebuilding index partitions concurrently 5472523 Non violated deferred CHECK constraint fails (ORA-2290) at COMMIT 5479902 Dump qertbStart running query on partitioned table 5500044 ORA-44203 on table_x_x child from concurrent LOB append and drop partition 5524408 Wrong result when query has 256+ bind variables on partitioning column 5556025 Wrong Results from partition pruning and ORs 5556152 Dropping a partitioned can be slow (Waits on 'dfs lock handle' for CI[1][2]) 5556174 Dropping a partitioned table slow (waits for 'gc current grant busy') 5566439 Dropping a partitioned table is slow ('enq: RO - fast object reuse' waits) 5576013 Wrong results (no rows) with partition pruning [PARTITION LIST ALL (LAST)] 5586632 Dump (qkaGranuleIteratorTraverse) on query on partitioned tables 5604940 Wrong results from a join and extended partition naming 5611623 Parallel query slave dump (kkpapitsize) 5618049 "mvobj part des" leaked memory after partition DDL (ORA-4031) 5621677 Logical corruption with parallel update on compressed partition 5630149 ORA-22877 from partition / subpartition MOVE of HASH partition 5632050 OERI[kkpolpd12] / dictionary corruption from CONCURRENT partition DDL 5649326 OERI[kksfbc-reparse-infinite-loop] can occur after DDL on partitioned table 5650372 Wrong results / OERI[kkpapdrmfkk1] from predicate elimination on partitioned table 5652906 Spatial DML fails if there is concurrent partition DDL 5677420 ORA-20000 from Text query against partitioned table 5680970 ORA-39001 when attempting to export partition defined as an object type 5690241 Dump / wrong results from OR predicate on partition columns 5718007 Spin (in qcopxla / qcopx0la) with OR predicates on PARTITION key columns 5724215 No query rewrite if materialized view is partitioned 5724540 False ORA-1 from subquery partition pruning 5747782 Update of a partition table with UNUSED columns dumps [kdddcp or kdtInsRow] 5754362 Plans can change after deleting statistics on a partitioned table 5763245 Parse may spin in kkpapRTPRuningSetup 5882954 Long parse time for query against tables with many partitions 5932060 Enh: Add support for direct SQL on partitioned table/index 5939115 ora-600 [kghstack_underflow_internal_1][pcols in kkpapdaextsqueryslvl] 5941355 "Split partition" does not move LOB to correct tablespace 5961454 ORA-29861 on DML with concurrent partition maintenance on different partition 5984440 Dump [prsatb] from ALTER TABLE .. MODIFY SUBPARTITION 5996430 Reading extent maps for unanalyzed partitions can be expensive 6025805 ORA-14403 raised when executing select for update 6041084 Spin during parse of query with INLIST against list partition key 6059327 ORA-39083 / ORA-1647 during TTS import of subpartioned table 6123567 Dump [kkosbn] optimizing query on partitioned table 6329316 Wrong number of rows inserted by ARRAY insert into partitioned table with concurrent DDL 6776107 TRUNCATE of highly partitioned table can be slow Performance Affected (General) 5705795P* Many child cursors possible for SQL using BINDS. This bug is alerted in Note 403616.1 5079978 High US enqueue contention in RAC 5087592 "log file sync" waits from read only commits 5173642 Data not read from cache on second execution with NUMA optimization enabled 5518811 Long latencies (several seconds) on BOC acks when one instance is idle 5751672 "In memory undo latch" contention from kturimugur 5896963 High LGWR CPU and longer "log file sync" with fix for bug 5065930 5964485 High waits in RAC due to LCK0 delay receiving ASTs 6319685 LGWR posts do not scale on some platforms 6450342 Process uses too many async IO descriptors 6528336 Automatic SGA may repeatedly shrink / grow the shared pool Performance Monitoring 5052029P HPUX-PA: "ksugetosstat failed" / no rows from V$OSSTAT 1798853 sppurge.sql does not run in batch mode 4493741 Cannot see SQL_TEXT for procedure calls from EXECUTE IMMEDIATE 4572043 DML monitoring is incorrect for MERGE / MTI 4969005 Dump [kglLockIterator] querying V$ views 5010879 V$SESSION slow and does not show any BLOCKING_SESSION column data 5087155 DBA_DATA_FILES and V$DATAFILE views do not show all files 5452234 V$LIBRARYCACHE "gets" accounted wrong 5470034 ORA-1436 from TKPROF EXPLAIN of query using a WITH clause 5485914 Mutex self deadlock on explain / trace of remote mapped SQL 5518550 Prefetch does not occur if event 10046 is set 5545735 Wrong values for V$SYSSTAT "open cursors current" 5552515 Incorrect V$SGASTAT information for "ktcmvcb" 5649377 V$GCSPFMASTER_INFO.REMASTER_CNT is never updated 5658143 DBMS_MONITOR.SERV_MOD_ACT_TRACE_ENABLE cannot set trace 5692368 Poor performance of queries against GV$ / V$ views on library cache / shared cursors 5917836 V$LOCK does not show locks for attached XA sessions 5918642 Heavy latch contention with DB_CACHE_ADVICE on 5928612 V$SESSION SQL_ADDRESS / SQL_HASH_VALUE not set for DBMS_JOBs 6075099 ORA-1476 from spreport (statspack) 6356566 Memory leak / high CPU selecting from V$SQL_PLAN (affects statspack) Performance Of Certain Operations Affected 4215910 DBMS_STATS may use a 100% row sample size when not expected 4725385 DBMS_STATS on partitioned IOT with additional indexes can be slow 4736971 Delayed XA transaction recovery 4920266 RMAN backup / restore of ARCHIVELOG can be slow 5057695 SHUTDOWN IMMEDIATE can be slow 5064356 RMAN backup to NFS slow due to "noac" requirement / ORA-27054 if not set 5071931 Datapump import with remap tablespace and schema is very slow 5093060 Streams unnecessary flow control at apply site 5116414 Cleanup of non-existence objects by SMON takes a long time 5219484 RMAN catalog resyncs can be very slow 5292551 IMPDP slow when importing a table with initialized column of type varray 5327658 Dataguard logical standby can be slow 5333268 DBMS_STATS.GATHER_INDEX_STATS can be slow 5354469 Poor performance of remote fetch with high fetch counts 5364613 Performance of XSL transform extremely slow 5370578 Capture process slow on startup on 'control file sequential read' 5455880 Excessive recursive query on TS$ when using a "tablespace group" as temporary tablespace 5504961 ORA-2292 slow to be signalled with many child rows 5510918 Log miner slow mining direct load redo 5521682 RMAN DUPLICATE with SKIP can be slow 5523619 DBMS_LOGSTDBY.INSTANIATE_TABLE can be slow 5530583 ASSM managed INDEX updates can be slow compared to non-ASSM 5556152 Dropping a partitioned can be slow (Waits on 'dfs lock handle' for CI[1][2]) 5556174 Dropping a partitioned table slow (waits for 'gc current grant busy') 5561130 Performance of long running transaction using AQ degrades over time 5566439 Dropping a partitioned table is slow ('enq: RO - fast object reuse' waits) 5576584 Poor ASM parallel read performance 5590185 Consistent export data pump job (flashback_time) has poor performance 5604120 Performance problems after applying calendar deviation 5683652 OCIHandleFree performance issue. PeopleTools Mandatory 5709414 DBMS_STATS.FLUSH_DATABASE_MONITORING_INFO call is very expensive 5723260 Logminer slow / excess memory use processing batch inserts with LOBs 5752105 ANALYZE TABLE VALIDATE STRUCTURE CASCADE ONLINE is slow with fix for 4430244 5764993 Unnecessary "buffer busy waits" timeout during index block split 5846062 DROP TABLESPACE takes a long time on very large buffer cache 5861536 Slow DDL due to Tablespace lookup with large number of tablespaces 5881229 AV capture is slow 5893614 Full table scan very slow on ASM 5893704 Occassional 1 second timeouts on "gc buffer busy" wait 5899994 RMAN resync is slow when the standby becomes primary (during switchover) 5922239 ALTER SYSTEM KILL SESSION IMMEDIATE pauses for 30s increments 5936294 SWITCH DATABASE TO COPY / LIST COPY OF DATABASE RECOVERABLE are slow 5955732 Two child cursors created when querying ku$_10_1_fhtable_view 5996430 Reading extent maps for unanalyzed partitions can be expensive 5998048 Deadlock on COMMIT updating AUD$ / Performance degradation when FGA is enabled 6017440 Streams capture / CDC / apply slow mining DMLs for tables with REFRESH ON COMMIT Materialized Views 6034995 RMAN slow SYNC due to too many rows in ROUT table 6037872 Reconfiguration slow in active / passive with large buffer cache 6064864 Archives containing DDL for not replicated objects take longer to process 6077514 DBMS_STATS.GATHER_FIXED_OBJECT_STATS can be slow with large buffer cache 6080303 Datapump export does not unload data until all metadata unloaded with PARALLEL > 1 6135499 Wrong Streams rule for bidirectional setup from MAINTAIN_* APIs 6143688 node startups cAN spend up to 2 mins in AQ partition code 6163622 SQL apply degrades with larger transactions 6168063 High "Flashback buf free by RVWR" waits 6376915 HW enqueue contention for ASSM LOB segments 6529008 Slow create tablespace / add datafile 6776107 TRUNCATE of highly partitioned table can be slow Performance Of Query/ies Affected 6455161+ Higher CPU / Higher "cache buffer chains" latch gets / Higher "consistent gets" after truncate/Rebuild 599680 Unnecessary sort for SELECT DISTINCT 4226736 Wrong clustering factor when DBMS_STATS.GATHER_INDEX_STATS runs in parallel 4273361 Unique index access not used with INLIST predicate 4336528 PQ may be slower than expected (timeouts on "PX Deq: Signal ACK") 4444536 Unnecessary sorting when access made through a global index 4483240 INLIST may use suboptimal index 4513695 Poor performance for SELECT with ROWNUM=1 with literal replacement 4545802 Poor Outer Join Cardinality estimation with filters on outer table 4567767 Execution Plan changes upon rowcache reload 4583239 INSERT .. SELECT with OR chains with identical predicates slower than same SELECT 4605810 Index may not be chosen to eliminate ORDER BY SORT 4619997 Function based index may not be used for INLIST predicate 4652100 Poor plan with bind peeking for SQL against LIST partitioned tables 4697189 High CPU usage for large sorts 4708389 Nest loop join costing ignores parallelism of index used to probe in right side 4752814 Wrong selectivity on comparision of VARCHAR2 column with CHAR variable 4872602 Sub-query is unnested even though cost is higher 4878299 Bad plan from join with FIRST_ROWS_N or a ROWNUM predicate 4913460 Soft parsing re-occurs for select using database link 4924149 Push predicate not working when function in the filter 5010879 V$SESSION slow and does not show any BLOCKING_SESSION column data 5029334 Queries against DBA_EXTENTS slow for locally managed tablespace 5030215 Excessive waits on PX Deq Signal ACK when RAC enabled 5040753 Optimal index is not picked on simple query / Column group statistics 5061079 Poor CONNECT BY plan 5065418 CONNECT BY performance degrades when temp space needed on disk 5082178 Bind peeking may occur when it should not 5099909 Partition not eliminated when joined to non mergeable view 5103126 Insert of duplicate rows with unique constraint slow 5129407 Suboptimal plan for SQL with multiple OR branches 5138741 High waits on 'row cache lock' when using materialized views on RAC 5147225 Poor performance of parallel context query with ROWNUM predicate 5161523 Wrong results / slow Parallel query due to data skew on multi-key table queues 5162867 Sort operation on a table that selects encrypted column slows down 5199213 Very bad plan for UNION ALL and push constant predicate / Wrong Results 5211863 Poor plan for CONNECT BY 5220356 Partition pruning predicates not cost pushed into UNION ALL views 5236908 Primary key index not used for IOT 5240607 FIRST_K_ROWS may choose inefficient NESTED LOOPS join 5258887 Queries on DBA_FREE_SPACE_COALESCED Slow 5259025 The fixed table x$ktfbue has no statistics 5263572 Wrong cardinarity for predicates of form "col like func(:bind)" 5284303 Poor plan for predicates against character columns containing numeric data 5288623 CBO may not choose the best index for ORDER BY elimination 5302124 Join Predicates are not push inside window functions -- superceeded fix 5364143 Bind Peeking is not done upon query reload, Execution Plan changes 5385629 Push predicate optimization does not occur 5387148 View not merged even though the cost is lower 5396162 Suboptimal plan from ANSI query with semi join 5403489 Poor performance on 64-bit systems 5449488 Suboptimal plan for SQL with negated predicates (BITMAP MINUS) 5468809 Predicate order can affect execution plan 5482831 Suboptimal plan with FIRST_ROWS_K or EXISTS subquery 5483301 Cardinality of 1 when predicate value non-existent in frequency histogram 5505157 Predicates are not pushed in UNION ALL views 5509293 Query with subquery across DB link has poor performance 5518550 Prefetch does not occur if event 10046 is set 5519856 Wrong cardinality from CBO for "col LIKE function(:bind)" 5530958 Larger SGAs and SQL in long running transactions can use excess CPU in ktaifm 5547058 Poor plan with old_style predicate push into UNION ALL views 5547895 No transitive predicates produced for user defined deterministic function 5570942 Query Rewrite causes high parse time with high hits on 'latch: row cache objects' and dc_object_ids / Dump in STRLEN 5611962 CBO MAX/MIN optimization may not occur 5618040 FIRST_ROWS may give poor plan if index chosen to eliminate a SORT 5620485 Non code based push predicate into UNION view can get poor plan 5620640 Slow OPEN RESETLOGS with FLASHBACK RECOVERY AREA 5624216 Wrong cardinality for UNION ALL with no WHERE clause 5634346 Multi-column INLIST may not use INLIST ITERATOR 5645771 No pruning for Nested Loops Join on a range-list partitioned table in parallel 5650477 Poor plan possible due to lack of view merging 5674756 OLS does not set selectivity of predicates causing bad execution plans 5680702 Suboptimal execution path for semi / anti join 5692368 Poor performance of queries against GV$ / V$ views on library cache / shared cursors 5694984 Index distinct key count scaling is wrong for first_rows(k) 5705630 Suboptimal plan from 'or' expansion 5741044 Suboptimal execution plan as 1 row table not detected 5741121 Suboptimal plan for "not equals" predicates 5742678 Index range scan used to get MAX value instead of index min/max first row 5754362 Plans can change after deleting statistics on a partitioned table 5766310 Bad join cardinality is in the presence of histograms 5838613 Suboptimal plan from STAR transformation 5842686 Poor plan due to bad average column length for tables with LONG RAW 5844495 Suboptimal plan with VPD and DML statement 5872956 Slow or Wrong Results on CONNECT BY queries with constant predicates 5882954 Long parse time for query against tables with many partitions 5884519 V$SESSION is slow with fix for bug 5010879 5884780 Suboptimal plan for STAR transformation 5891471 Poor cardinality estimates with check constraints 5903581 Wrong Results with "Connect By with Filtering" 5910187 No bind peeking for implicit string bind to timestamp 5944076 Suboptimal plan in FIRST_ROWS(K) mode 5949981 Bad cardinality with histogram 5976822 Suboptimal plan possible 6006300 Push predicate does not occur 6006457 Suboptimal plan from ANSI outer join 6007259 CBO does not consider ORA concatenation 6011182 Parsing of large query takes long time / memory leak / ORA-4030 /4031 6033480 High parse time of query when using ANSI style joins 6042205 High parse time for a query using ORDER BY 6051211 Too High Join Cardinality with Histograms Present 6070954 Skip scan may be used instead of a better range scan 6082745 Bad plan with fix for bug 5483301 6084811 MERGE JOIN CARTESIAN not considered 6087237 CBO may not choose best join order 6114166 Pre-10g outlines may not work in later releases 6122894 Poor plan from UNION / INTERSECT views with OR predicates 6134565 FIRST_ROWS hint is not honored with "_sort_elimination_cost_ratio" parameter set 6151963 Wrong join cardinality with histograms 6188881 Index selectivity adjustment for anti/semi join causes wrong index to be chosen 6239971 CBO costing can differ greatly for =< compared to < 6251917 Optimizer selects the merge join cartesian despite the hints 6274465 DML / queries run serially instead of parallel when there is concurrent DDL 6328110 Select COUNT() with an encrypted column is slow 6694548 Suboptimal execution plan using bitmap full index scan Physical Standby Database / Dataguard 3140249 Data guard broker hangs when standby listener is down 4193047 Sequences / synonyms / indexes not created in logical standby database 4230058 ORA-1219 on connect to RMAN after physical standby is opened read only 4398691 DG broker does not set FAL_SERVER correctly in RAC 4404952 DG broker does not support cold-failover clusters 4538727 Applied column is not updated in V$ARCHIVED_LOG 4663793 ORA-16224 on select from ALL_OBJECTS on standby with DataGuard 4690705 Repeated ORA-1041 from heartbeat ping 4767278 OERI[kcrrupirfs.20] archiving redo to standby with ASM 4969780 Dump (krvxdts) from RFS 5022127 RMAN catalog resync fails RMAN-20098 5063635 OERI[kccdagf_3] during file creation 5079641 Switchover hangs attempting to recover a log file from a previous primary 5089522 Memory leak in niotns in MRP process 5209867 ORA-38777 is thrown by MRP when flashback through resetlogs 5238386 ORA-322 possible reading standby redo log header 5327658 Dataguard logical standby can be slow 5372831 OERI:26599 / dumps in JVM after database has been closed for recovery / opened 5382088 Fast start failover can hang on broker MIV mismatch 5387017 Primary hang when physical standby "shutdown immediate" 5396680 dgmgrl returns success for a failed reinstate 5399901 Archived log entries can take a long time to search in Dataguard 5526409 FAL gaps reported at standby for log not yet written at primary 5532046 Deadlock on metadata lock during quiesce of old primary 5573544 Trace files generated on DG primary by sqlplus sessions 5576816 FAL gap resolution does not work with max_connection set in some scenario 5578157 Instance crash with ORA-600 [1433] (RSM has all message blocks) 5743829 DG Broker process dump 5746174 MRP hangs with async LNS and parallel archival 5746223 Old primary hangs after a FSFO and prevents automatic reinstatement 5757282 Broker commands to standby can error (ORA-16613) 5759876 Dump [rfm_get_chief_lock] on Broker startup 5844816 Fast Start Failover (FSFO) occurs after planned primary shutdown 5844945 Bystander cannot receive missing logfiles from the old branch after failover 5857949 Startup may fail due to dump [rfmsoexinst] from DMON 5891280 MRP0 on standby may not start (OERI:krfg_aset_1) 5893318 Broker reinstate after failover fails with ORA-38777 in RAC 5894403 MRP0 process fails with SIGFPE in kcrarmb 5899994 RMAN resync is slow when the standby becomes primary (during switchover) 5930819 RMAN ignores Streams when deleting logs if both streams and DG are implemented 5934150 MRP at standby ignores entries created when database was primary 5942620 Archivelog gap may not get resolved 5951587 Unresolved gap after FSFO (fast start fail over) 5981084 OERI[kcrrtcln.seqvio] can occur 5999200 FSFO fails with ORA-16750 "failed to activate logical standby" 6029425 ORA-1207 recovering datafile from standby 6035495 ORA-19909 during MRP / RMAN-600 on resync 6039415 ORA-355 can occur during real time apply 6082660 Old primary stays up after failover 6143316 Cannot rebuild DG broker config files without bouncing primary in FSFO 6311900 RFS writes misleading messages to the alert log 6680806 ORA-16139 from ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY 6762914 ORA-326 during Managed Standby Recovery after thread disable 6768069 Cannot FLASHBACK DATABASE on RAC physical standby Pro* Precompiler 5674184 ORA-22282 when using LOB buffering Query Rewrite (Including Materialized Views) 5898210+ Hang from concurrent MV refresh and library cache invalidation in RAC 386181 ORA-12014 when creating a refresh complete / refresh force materialized view 4054238 ORA-12899 with complex aggregate expressions in a materialized view 4119210 OERI[kkqgSetFields.2] possible from query rewrite 4200563 OERI[kkqsfcsi-1] from query rewrite 4226141 Materialized view reports NOT NULL column as nullable 4380471 OERI[kkqsfcsi-1] from query rewrite with an ORDER BY 4482978 OERI[qkagby.noexec] on materialized view recompile 4483439 ORA-904 error during Materialized View fast refresh 4485775 OERI [qsmqLockTableSummarySubheap-1] selecting from materialized view with TDE enabled 4559546 Cannot used exp/imp of MVIEW with XMLTYPE column 4681323 Query rewrite not occurring if query references a materialized view 4740187 ORA-30353 creating materializer view with SYSDATE in the refresh clause 4768022 ALTER TABLE can fail with ORA-60 4864149 Query rewrite with ORDER BY of grouping_id dumps in evagrp 4883635 MERGE (with delete) can produce wrong results 5008674 OERI [kkqsfcsi-1] from query rewrite 5015547 Cannot create a materialized view over a database link (ORA-942) 5073249 Dump from fast refresh of MV using "WITH .. AS" 5096560 Dump (selexe) when recompiling a materialized view with a UNION 5136425 ORA-32337 from ON COMMIT MATERIALIZED VIEW after a direct load 5138741 High waits on 'row cache lock' when using materialized views on RAC 5165904 Materialized View DDL may execute when it should wait 5169684 Wrong results (all rows no filtering) when rewrite enabled on a view 5182679 INSERT as remote SELECT using CASE can produce wrong data 5217296 ORA-32411 reported on materialized view refresh 5261145 OERI[12261] from dbms_mview.explain_rewrite 5299546 ORA-942 from create materialized view with join between local and remote tables 5354437 ORA-1435 on create materialized view of UNION ALL from different sites 5363258 Query rewrite can fail with OERI[voprvl1] 5487101 Complete refresh does not preserve parallelism of indexes 5493858 ORA-604 / ORA-1422 from materialized view operations 5501349 Compilation errors from materialized iew with OUTER JOIN 5530043 OERI [kkzg_add_ref_stmt_lst.1] can occur during materialized view refresh 5564090 Rewrite does not occur for join with selection predicate connected by OR 5570942 Query Rewrite causes high parse time with high hits on 'latch: row cache objects' and dc_object_ids / Dump in STRLEN 5572957 Dump (under kkqssjsce) with query rewrite enabled and heavy load 5583712 ORA-942 on create materialized view on remote view 5619833 Dump (qerixGetKey) from query rewrite on join including functional index 5632128 Materialized View refresh looses statistics on primary key 5660643 OERI[kkqsfcsi-1] during query rewrite of SQL with set operator 5669051 Query rewrite may dump in kkqsMMVNormalizeQBC 5724215 No query rewrite if materialized view is partitioned 5845901 Dump from concurrent CREATE MATERIALIZED VIEW and DDL on base tables 5850776 OERI[kkqsMMVReAggRewriteExp:notoptfou] from query rewrite 5872368 ORA-22160 from DBMS_ADVISOR.TUNE_MVIEW 5964193 OERI[kkqsRewriteCorrCols-1] during query rewrite with ANSI joins 6017440 Streams capture / CDC / apply slow mining DMLs for tables with REFRESH ON COMMIT Materialized Views 6041713 OERI[kkzdgdefq_oci - stexec] refreshing through definer rights procedure RAC (Real Application Clusters) / OPS 6017420* OERI[kcbo_link_q_1] / crash with fix for bug 5454831 installed. This bug is alerted in Note 453309.1 5898210+ Hang from concurrent MV refresh and library cache invalidation in RAC 4398691 DG broker does not set FAL_SERVER correctly in RAC 4422686 LMD/LMS cannot be frozen during reconfig 4441119 Not enough information dumped when RAC detects a deadlock 4489948 ASM hangs during a parallel mount and shutdown in RAC 4584985 OERI[kclexpand_9] can occur 4605569 LCK may accumulate CPU time on one instance 4634662 OERI:kolaslGetLength-1 from V$SQL in RAC 4699720 MMON or PMON spin in RAC 4715375 OERI[kwqmtdel] in q00 process in RAC when any instance goes down 4744529 OERI:kclpred_1 / crash possible in RAC 4760728 ORA-38301 during DROP TABLE when already dropped from a different node 4936689 Crash dump (cdmp) generation cannot be limited dynamically 4963729 Global hanganalyze can leak memory / OERI[kghgethpsz1] 4966024 VLM buffer leak on if an error occurs 5030215 Excessive waits on PX Deq Signal ACK when RAC enabled 5064356 RMAN backup to NFS slow due to "noac" requirement / ORA-27054 if not set 5079978 High US enqueue contention in RAC 5118012 Instance crash with OERI[kclswrite_3] with multiple DBW processes 5138741 High waits on 'row cache lock' when using materialized views on RAC 5165885 OERI[kclcls_8] or OERI[Kjbrchkpkeywait:Timeout] can occur in RAC 5179008 Dump (kjzhablar) possible in RAC 5225596 AQ propogation does not work after failover 5304233 DBW endlessly writes error "kjbhistory[0xaa19.27000.." 5334733 Deadlock resolution can be slow in RAC 5353526 GCS reconfiguration performance improvement 5360289 Startup in RAC can be slow 5361398 Longer deadlock token (DI enqueue) get time with higher number of nodes 5366893 CF enqueue contention during first pass redo scan 5370641 Inefficient interconnecct lost packet handling 5375583 LMS process dies with OERI[kclexpandlock_1] 5376770 Spin in kcldle in RAC can cause a cluster hang 5379206 SMON blocked waiting for CF enqueue during 1st pass recovery (for 1 second) 5388885 Hang / OERI[krvxbpns01] accessing V$LOGMNR_CONTENTS from RAC 5403150 ORA-603 when cannot get lock within Resource Manager "switch_time" in RAC 5415594 xa_commit returns -4 (XA_NOTA) after RAC failover 5454831 RAC deadlock possible on working set latches 5470095 Self deadlock should provide more targeted diagnostics 5471994 LCK may accumulate CPU time when SMON does Serial Transaction recovery 5485242 ORA-29701 in RAC environment 5486023 "GLOBAL CACHE ELEMENT DUMP" in LMS trace with FLASHBACK 5503590 Logminer Adhoc can hang or error mining logs from a RAC database 5506702 Dequeue delay experienced after reconfiguration 5518811 Long latencies (several seconds) on BOC acks when one instance is idle 5526996 OERI[kjhn_post_ha_alert0-784] can occur in RAC due to racgimon problem 5530697 OERI[kjshash:!esm2] in PQ slave process in RAC querying GV$ view 5556152 Dropping a partitioned can be slow (Waits on 'dfs lock handle' for CI[1][2]) 5556174 Dropping a partitioned table slow (waits for 'gc current grant busy') 5566439 Dropping a partitioned table is slow ('enq: RO - fast object reuse' waits) 5587421 LMS fails with OERI [kjmpmsg_1] 5593693 Connection load balancing does not work if db_domain is set 5596032 LMON may wait in network validation 5599293 RAC instance termination may unexpectedly stall for several seconds than needed 5600050 LMON may fails with OERI [kjbrref:pkey] during DRM 5649377 V$GCSPFMASTER_INFO.REMASTER_CNT is never updated 5663447 ORA-27544 using HMP protocol in RAC 5666733 LOB segment does not use free space from freelist in RAC database 5681955 SGA corruption in RAC (OERI [17114] / OERI [17112]) 5688403 'IPC Send timeout' error just after 'flush_cache' event in RAC 5690100 RAC instance crash with OERI[kjbmpwrite:wip2] 5695610 OERI[kxfpgsg] isolation_level = serializable in RAC 5697333 ORA-25402 from TAF in RAC 5721821 SGA corruption / Dump[kglobcl] / crash if objects dropped / recreated 5730717 OERI:kclchkinteg_18 / LMS crashes the instance 5744546 MMON OERI [1403] 5751016 AQ messages enqueued at non-owner instance not moved from WAIT to READY 5764556 OERI[kctdsb_internal_03] 5843585 Additional diagnostics for "ges inquiry response" RAC hangs 5844816 Fast Start Failover (FSFO) occurs after planned primary shutdown 5854415 RAC diagnostic enhancement for corrupt messages 5855896 Reconfiguration takes a long time restarting instance in active/standby RAC 5857949 Startup may fail due to dump [rfmsoexinst] from DMON 5863519 Instance crash due to LMS dump (in kclcsr) 5881493 CDC ordered sequence causes large performance degradation on RAC 5883112 False deadlock in RAC 5884519 V$SESSION is slow with fix for bug 5010879 5891737 Dump (kcblsod) / OERI:723 / Memory leak in ASM/RAC 5893318 Broker reinstate after failover fails with ORA-38777 in RAC 5893704 Occassional 1 second timeouts on "gc buffer busy" wait 5899033 SMON dump (kfrCheckCtx) diskgroup instance recovery 5900401 Instance crash by LMON due to "skgpgpstack: read() ..." error 5933838 Database crash (ORA-449) after ALTER DATABASE FLASHBACK OFF in RAC 5939241 Inconsistent diskgroup configuration after rejected DISK OFFLINE 5942620 Archivelog gap may not get resolved 5950708 'gcs resources' and 'gcs shadows' are imbalanced across shared pool subpools 5952530 Spin / hang after cluster reconfiguration 5958244 LMS processes running in realtime can spin 5964485 High waits in RAC due to LCK0 delay receiving ASTs 5968965 xa_recover on RAC may not return all prepared transactions 5973648 ORA-54 during concurrent parallel direct SQLLOAD in RAC 5974572 WRH$_SERVICE_STAT can grow very large in RAC 6001617 LCK may accumulate CPU time / ORA-4031 possible 6005113 OERI[kclrwrite_7] in DBWn process followed by instance crash in RAC 6013968 Hang / OERI:504 with patch for bug 5863519 installed 6018125 Instance crash during dynamic remastering or instance reconfiguration 6019084 RAC hang possible when node leaves the cluster with fix for bug 5844816 6037872 Reconfiguration slow in active / passive with large buffer cache 6057703 OERI[kclchkblkdma_3] can occur in RAC 6075582 OERI[kjbmpref:sh] / dump [kjmpbmsg] in LMS causing instance crash 6083037 Server side load balancing does not work 6114833 Logminer does not signal error if log unavailable in continuous_mine 6123145 Dump [ksxpunmap] in RAC 6143688 node startups cAN spend up to 2 mins in AQ partition code 6144079 Instance crash in RAC (OERI:2103) 6154655 QMON fails to update queue table affinity for several minutes after failover 6239052 LMS can crash instance with OERI[kjbrchkinteg:last] 6271689 RAC instance crash possible 6310591 DB hang with CKPT waiting for enquiry response in RAC 6442431 A node may stop receiving connections with RAC load balancing 6496514 RAC deadlock between "libary cache lock" and TX enqueue 6501007 DRM sync timeout in RAC 6768069 Cannot FLASHBACK DATABASE on RAC physical standby 6781496 OERI[KGHLATCH_REG4] on STARTUP with >61 CPUs in RAC with fix for 5508574 RMAN (Recovery Manager) 4230058 ORA-1219 on connect to RMAN after physical standby is opened read only 4431215 "backup archivelog all delete input" from RMAN removes ASM directory 4457221 Dump [under kdxcom] doing RMAN compressed backup 4538727 Applied column is not updated in V$ARCHIVED_LOG 4541506 RMAN OERI[1880] when MAXPIECESIZE is set 4659734 RMAN-6900 RMAN-6901 ORA-19921 during RMAN commands 4920266 RMAN backup / restore of ARCHIVELOG can be slow 5016125 RMAN convert with parallelism > 1 fails (RMAN-3009 / ORA-19927) 5022127 RMAN catalog resync fails RMAN-20098 5063635 OERI[kccdagf_3] during file creation 5064356 RMAN backup to NFS slow due to "noac" requirement / ORA-27054 if not set 5207044 RMAN "backup validate check logical" fails with OERI[krbbfmx_notfound] 5219484 RMAN catalog resyncs can be very slow 5247609 RMAN slow performance during register database/open resetlogs 5278539 ORA-23605 on create of new capture 5448714 ORA-1455 on RMAN backup database for files over 4Tb in size 5521682 RMAN DUPLICATE with SKIP can be slow 5620640 Slow OPEN RESETLOGS with FLASHBACK RECOVERY AREA 5705762 Duplicate may fail on RESTORE 5742127 RMAN backup sometimes fails if datafile grows during backup 5870989 RMAN restore failover gives ORA-19864 error 5899994 RMAN resync is slow when the standby becomes primary (during switchover) 5902410 V$RECOVERY_FILE_DEST.SPACE_RECLAIMABLE and V$BACKUP_FILES.OBSOLETE wrong for retention policy NONE 5928555 OERI[krastrso_reserve] during BACKUP BACKUPSET 5930819 RMAN ignores Streams when deleting logs if both streams and DG are implemented 5932029 ORA-21000 when running RMAN "resync catalog" 5932181 RESYNC of RMAN catalog fails with ORA-1 (on TF_U2) or RMAN-20042 after switchover 5936294 SWITCH DATABASE TO COPY / LIST COPY OF DATABASE RECOVERABLE are slow 5971763 RMAN-20098 during CATALOG SYNC 5977767 RMAN "minimize load" with "duration" causes backup to timeout 6013213 OERI[17183] selecting from X$KRBAFF 6034995 RMAN slow SYNC due to too many rows in ROUT table 6035495 ORA-19909 during MRP / RMAN-600 on resync 6253529 RMAN duplicate/restore database fails restoring archivelog ORA-19636 6451722 RSR table in RMAN catalog database never gets cleaned Read Only Tablespace/s 5693140 OERI[kdtdelrow-2] from array insert with concurrent ALTER TABLESPACE READ ONLY 5695131 HW enqueue deadlock / OERI:1153 from array insert with SAVE EXCEPTIONS to READ ONLY ASSM segment Recovery 6128197* OERI[kcrfr_resize2] / cannot recover database. This bug is alerted in Note 453259.1 4577403 OERI [kcbr_pending_3] during parallel recovery 4736971 Delayed XA transaction recovery 4899479 Undo/redo corruption if distributed transactions used 5387683 ORA-27103 / ORA-27129 during media recovery 6010833 Recovery following flashback does not utilize changes in online redo log 6029425 ORA-1207 recovering datafile from standby 6251003 Reduce maximum reads that can be issued by a recovery slave 6267094 OERI[kghstack_underflow_internal_1] recovering logical standby Recycle Bin 5083393 DBA_FREE_SPACE FILE_ID / REL_FNO may be wrong 6113520 Cannot add table into single table cluster (ORA-25136) Regular Expressions 5194354 DUMP[kghalp] when executing query with index using REGEXP_SUBSTR 5682195 Dump (lstmclo) evaluating regular expression in case insensitive mode Resource Manager 4886649 OERI[kgskthrexit3] possible from resource manager 5403150 ORA-603 when cannot get lock within Resource Manager "switch_time" in RAC 5910422 SESSIONS_PER_USER resource limit works inconsistently for PQ processes 6040079 DBMS_SESSION.SWITCH_CURRENT_CONSUMER_GROUP does not work 6241497 Resource manager with PQ enabled does not use parallelism 6816727 Resource manager does not handle errors correctly Row Level Security / FGA 4581220 OERI:kzaSqlTxtLob1 with fine grained auditing and parallel query 5084679 OERI from EXPLAIN_REWRITE CLOB interface with VPD 5084757 OERI when executing explain_plan with VPD 5228711 ORA-604 trace from PQ slaves with FGA policy 5387478 ORA-28132 for user with EXEMPT ACCESS POLICY privilege 5844495 Suboptimal plan with VPD and DML statement 5860927 FGA records are not written for view on remote table 5913871 FGA records are written for recursive SQL under DBMS_STATS 5938452 VPD does not work when a CURSOR expression is used against a synonym 5998048 Deadlock on COMMIT updating AUD$ / Performance degradation when FGA is enabled SQL*Loader 4766696 Loader LDR-297 / ORA-1756 from SQL / expression ending with a single quote 5022188 Direct SQLLOAD of partitioned object table of non final types fails 5104257 SQLLoader truncates nested table columns 5228136 ORA-26065 from SQLLDR direct path load of objects containing a LOB and constraints 5579610 SQLLoaded message and error return code for SKIP INDEX MAINTENANCE 5651245 ORA-1801 from SQL Loader instead of the elapsed time of the load message 5676948 OERI [qxxmslSelectLocator_10] from SQL*Loader 5716353 ORA-12899 from SQL Loader for valid data 5873852 sqlldr inserts character data longer than the column length (CHAR length semantics) 5944227 SQLloader direct path load into IOT can dump [kdblldrp] 5953355 OERI[klaprs_30] / OERI[klaprs_10] during SQLLOADER direct path load 5973648 ORA-54 during concurrent parallel direct SQLLOAD in RAC Security ( Authentication / Privileges / Auditing ) 4069679 USERENV of SESSIONID returns 0 when used in a logon TRIGGER WHEN clause 4254770 OERI:kzaSqlBindLob1 can occur with AUDIT_TRAIL = DB_EXTENDED for sql using binds 4395849 ESM tool hangs connecting to directory server on SSL port 4596532 Wrong results from V$XML_AUDIT_TRAIL 5021304 V$PARAMETER view of AUDIT_SYSLOG_LEVEL looses all characters after a "." 5078627 Audit sessionid is zero for jobs invoked by job scheduler 5081050 No audit for logout action with audit_trail=xml 5162867 Sort operation on a table that selects encrypted column slows down 5166745 Excessive redo generation with auditing enabled 5182299 Dump on grant / revoke of privileges on a TYPE 5248932 XML audit filenames should be based on process id 5254198 ALTER USER SYS IDENTIFIED BY VALUES does not change the password file 5376108 ORA-1109 when shutting down the database with AUDIT_TRAIL=DB 5437445 Incorrect username displayed from logminer adhoc query when auditing is on 5514908 SYS.AUD$.CLIENTID not set for ALTER DATABASE SQL 5617311 ORA-1017 cannot connect through proxy using distinguished name 5634026 Dump using SYSLOG auditing on SYS operations 5654013 EUS shared server connection fails with ORA-28030 5660888 OERI[kzspvcr:1] using proxy authentication with > 16 roles 5711129 XML audit file does not record all bind variables correctly 5924763 Rows missing from V$XML_AUDIT_TRAIL 5945463 XA clients should not require execute privilege on DBMS_SYSTEM 5977486 Password changes not propogated to logical standby when password expires 5998048 Deadlock on COMMIT updating AUD$ / Performance degradation when FGA is enabled 6018252 Insert statement with RETURNING clause fails with ORA-1031 6035889 ORA-28003 from create / alter user if password verification function contains special character 6041317 OERI when inserting ASCII 0x0 into CHAR/VARCHAR2 with AUDIT_TRAIL=DB_EXTENDED 6152756 Audit trail string value not quoted 6322324 OS audit trail should include length of attribute values Shared Pool Affected 5705795P* Many child cursors possible for SQL using BINDS. This bug is alerted in Note 403616.1 4367986 Bind peeked parallel cursors do not share 4467058 IO requests can flush the pool / signal a hidden ORA-4031 error 4581334 Cursors accessing remote tables may be repeatedly rebuilt and not used 4701527 Cursors not shared when executing procedures over a dblink 5082178 Bind peeking may occur when it should not 5386986 Leak / ORA-4031 leak when DROP UNUSED COLUMN issued on large partitioned table 5465597 SQL apply does not use bind variables while processing sequence updates 5479172 ORA-4031 with multiple partially-allocated permanent chunks 5508505 ORA-4031 while shared heap still has unused reserved extents 5548389 Library cache allocation for 'column mapping' not using uniform sized extents 5548510 _FIX_CONTROL parameter leaks memory in the shared pool 5555683 Intermittent ORA-1801 when shared pool under pressure 5573238 Shared pool memory use / ORA-4031 due to "obj stat memo" in one subpool 5618049 "mvobj part des" leaked memory after partition DDL (ORA-4031) 5841488 Extra child cursors for INSERT or MERGE SQL with fix for bug 4701527 5950708 'gcs resources' and 'gcs shadows' are imbalanced across shared pool subpools 6011182 Parsing of large query takes long time / memory leak / ORA-4030 /4031 6043052 Leak in perm allocations with "library cache" comments (ORA-4031) 6333663 Shared pool latch contention due to fragmentation of large pool Shared Server (formerly MTS) 4739114 Dump in shared server after using DBMS_XMLDOM 5324905 nsprecv() can corrupt the SGA when using shared servers 5362897 Non linear CPU increase when adding more shared server sessions 5447395 Shared server tied to session when BFILE used 5482555 Shared server does not release memory 5654013 EUS shared server connection fails with ORA-28030 5711011 "SocketException: socket is closed" using RMI with shared servers 6056865 Intermittent OERI [kcblci_1] using shared servers 6333663 Shared pool latch contention due to fragmentation of large pool 6390420 TNS-12535 is logged twice to sqlnet.log at time-out with shared servers Space Management (Locally Managed Tablespaces) 5029334 Queries against DBA_EXTENTS slow for locally managed tablespace 6017760 DBMS_METADATA.GET_DDL does not show changed datafile attributes Spatial / Spatial Advisor 5652906 Spatial DML fails if there is concurrent partition DDL Spatial Data 5024703 PARALLEL on Spatial index is ignored 5118210 OERI[kopuigpfx1] on insert to table with sdo_geometry column with INSTEAD OF trigger 5374225 SDO_FILTER query fails with OERI[kdsgrp1] 5959987 Spatial aggregations fail with ORA-22813 Star Transformation 4372359 Wrong results from temp table star transformation 4702830 OERI[kkoljt1] when using star transformation with an ANSI outer join 5089444 Dump (kkodsel) from select with a subquery with star transformation 5113934 PQ slave dump in qerixGetKey() when using bitmap index access 5245494 Improved control over whether star transformation is performed 5369855 OERI:733 or Spin (qksopLogSame) from star transformation 5397482 Wrong results from Star transformation with transitive join predicate 5512415 Wrong result from star transformation with EXISTS subquery 5568316 Wrong results from star transformation 5571916 wrong (duplicate) values with parallel and STAR (missing "PX block iterator") 5612751 OERI:qertqosSetPart4 if STAR transformation is considered and rejected 5670294 Dump (qknviAllocate) using star transformation 5766450 Dump [kkomprf] when attempting STAR transformation 5838613 Suboptimal plan from STAR transformation 5884780 Suboptimal plan for STAR transformation 5947231 Wrong results from parallel STAR query (with temp_disable) 5988085 Dump [kkodsel] from STAR transformation with ANSI view Star Transformation With Temp. Tables 5381446 Wrong results / dump from STAR transformation with INDEX join 5649765 Dump [evaopn2] from star transformation with pushed predicate Storage Space Usage Affected 4380450 Unbalanced space usage if diskgroup has only two disks, both of different size 5093837 ALTER TABLE SHRINK does not take PCTFREE into account 5387030 Automatic tuning of undo_retention causes unusual extra space allocation 5442919 Expired extents not being reused (ORA-30036) 5655612 AQ$_PENDING_MESSAGES table can grow indefinitely 5666733 LOB segment does not use free space from freelist in RAC database 5723140 Temp LOB space not released after commit 5974572 WRH$_SERVICE_STAT can grow very large in RAC 6147372 COL_USAGE$ may keep growing in size Streams / Logical Standby 3023540 "Create index ... online" does not create index on logical standby 4061534 OERI[krvtadc] / dump in capture mining redo for COMPRESSed table 4304023 Logical Standby does not support OLS properly 4369756 Log apply may dump [krvsmso] 4373687 SET_SCHEMA_INSTANTIATION_SCN does not error if database link unavailable 4408041 Dropped foreign key column puts wrong table name in DDL redo for streams 4552393 Heterogenous apply fails for updates with WHERE .. IS NULL 4556298 Auto delete turned off after ACTIVATE LOGICAL STANDBY APPLY 4567042 Logical standby log apply may stop with OERI[knacend910] 4627457 ORA-24042 from REMOVE_STREAMS_CONFIGURATION if queue_to_queue is true 4667479 ORA-16224 when using UTL_FILE / ORA-1031 using a DIRECTORY under GUARD ALL 4681763 ORA-6502 from DBMS_STREAMS_ADM.maintain_schemas if schema is empty 4681796 DBMS_STREAMS_ADM.maintain_schemas gives unhelpful ORA-2019 error 4682527 ORA-26762 from maintain_* scripts if source db name does not include dot (.) 4684070 Password changes not propogated to logical standby 4719798 DBMS_STREAMS_ADM.maintain_schemas incorrectly requests supplemental log for IOT with overflow 4719848 Streams DELETE_ERROR does not maintain AQ$_QTABLE_I 4730249 Logical Standby or Adhoc query fails with ORA-1801 when using a different characterset 4933222 Apply update of clob in multibyte charset double spaces characters 4959652 Streams may get OERI [kwqbespayl518] 5024737 Streams LCRs may be filtered when using distributed commit SCN 5040073 ORA-27047 from DBMS_STREAMS_TABLESPACE_ADM pull tablespace 5058318 Memory leak (in "koh-kghu" heap of type "kolccst obj") 5087279 User DDL incorrectly skipped on logical standby 5087369 logical standby potential data loss during failover 5093060 Streams unnecessary flow control at apply site 5095889 PGA leak during propagation in "kwqpcbk:koioalm" and "kwqpcbk:csid" 5116197 Queue_to_Queue propagation cannot be configured with ADD_GLOBAL_PROPAGATION_RULES 5154689 OERI[kql_tab_diana:new dep] / table dependency deleted in Streams 5183594 Logical standby apply stops / OERI [kghstack_underflow_internal_2] with SKIP / UNSKIP on SYS tables 5190392 Drop of table with triggers fails (ORA-16227) on logical standby 5196175 OERI[kghstack_underflow_internal_1] with supplemental logging for LOBS 5197305 NON_SCHEMA_DDL option skip() setting causes type bodys to be skipped 5205636 Apply fails with ORA-26687 while dropping a table with referential constraints 5206649 Logical standby finish apply time is highly variable on an idle system 5220845 Large packages imported via data pump are not shipped to logical standby 5225733 After flashback operation, new logs are not applied in logical standby 5261453 Standby "apply skip failed transaction" fails 5278539 ORA-23605 on create of new capture 5287523 ORA-16216 starting SQL apply after rolling upgrade completion 5327658 Dataguard logical standby can be slow 5350292 ORA-16210 logical standby coordinator process terminates with error 5360422 Datapump export from logical standby fails with ORA-39004 / ORA-39091 / ORA-44004 5370578 Capture process slow on startup on 'control file sequential read' 5394563 DBMS_STREAMS_ADM.maintain_simple_tts does not check if tablespace exists 5399050 Logical standby does not ignore data pump external table creations (Apply stops ORA-955) 5406025 DDL on primary can invalidate related objects on logical standby 5465597 SQL apply does not use bind variables while processing sequence updates 5472702 ORA-1403 during SQL Apply of redo from table import (redo issue) 5484652 QMNC process spin in Streams 5496852 Skipping grant object skips every grant 5512840 Logical standby fetch slave stops with OERI [knahfgx704] 5515703 Streams table diverges after partial rollback on primary 5517195 Logical standby table INSTANTIATE_TABLE may silently fail 5523619 DBMS_LOGSTDBY.INSTANIATE_TABLE can be slow 5529797 PGA leak / OERI KWQPCBK179 during Streams propogation 5567641 Streams capture terminates on restart with OERI[krvuatla] 5567937 False ORA-1 / ORA-1403 from logminer rolling back IOT redo 5575674 CAPTURE_IGNORE_TRANSACTION parameter handles rolled back transaction incorrectly 5581472 Streams capture excessive IO during low / idle redo generation 5584105 ORA-1 against I_STREAMS_APPLY_SPILL_TXN in Streams apply 5584790 PURGE_SESSION not deleting archive logs that are no longer needed 5588615 Single source streams with DML handler duplicates CLOB column value 5593617 Job scheduler cannot be used on logical standby (ORA-16224) 5602452 Capture gets stuck in 'dictionary initialization' after recovery 5604698 Deadlock between 'library cache lock' and 'library cache pin' using Streams 5623403 ORA-26773 invalid data type for "malformed redo" in Streams Capture 5640593 Streams OERI:kwqbmcrcpts101 while spilling messages 5653824 DBMS_LOGSTDBY.build may use wrong logs 5677680 Starting SQL apply fails with ORA-1426 5685296 Logical apply stops with PLS-103 due to NLS_NUMERIC_CHARACTERS setting 5685645 Logminer does not support IOT with OVERFLOW if table has been altered 5715079 ORA-1281 when applying a Patch Set on a logical standby 5723260 Logminer slow / excess memory use processing batch inserts with LOBs 5744428 dbms_logmnr_d.build may get a downstream build failure 5769961 Excessive trace from DML errors on logical standby 5770059 DBA_CAPTURE . required_checkpoint_scn not moving forward 5837643 Ignored transactions not excluded from oldest_scn computation on restart 5860221 Apply aborts with OERI[17147] / memory corruption with FUNCTION BASED index 5865842 DBA_REGISTERED_ARCHIVED_LOG.DICTIONARY_END contains extra space for 'NO' value 5867943 Capture aborts with OERI[knlcloop-200] mining "ALTER TABLE SPLIT PARTITION ..." 5881229 AV capture is slow 5883622 Capture dump / error after restart 5886044 No way to purge v$streams_transactions 5924538 Logical standby apply fails with ORA-1427 for operations on IOTs 5930819 RMAN ignores Streams when deleting logs if both streams and DG are implemented 5942476 OERI [kcrrcomp.4] can occur in Streams 5977486 Password changes not propogated to logical standby when password expires 6004936 Standby apply stops after ORA-16146 6017440 Streams capture / CDC / apply slow mining DMLs for tables with REFRESH ON COMMIT Materialized Views 6034040 Apply aborts with OERI [knlcfpactx:any_knlso] using RENAME_SCHEMA 6043052 Leak in perm allocations with "library cache" comments (ORA-4031) 6064864 Archives containing DDL for not replicated objects take longer to process 6135499 Wrong Streams rule for bidirectional setup from MAINTAIN_* APIs 6136494 Capture process aborts with OERI [17112] / OERI [17147] 6154377 REQUIRED_CHECKPOINT_SCN not moving 6163622 SQL apply degrades with larger transactions 6267094 OERI[kghstack_underflow_internal_1] recovering logical standby 6640950 Update of LONG can cause Streams capture to spin / spill 6644215 OERI[krvxradfd] during autodelete of partial log on logical standby System Managed Undo (SMU) 5079978 High US enqueue contention in RAC 5387030 Automatic tuning of undo_retention causes unusual extra space allocation 5439554 "buffer busy wait" timeouts with automatic undo management and in memory undo 5442919 Expired extents not being reused (ORA-30036) 5512921 Instance crash caused by SMON OERI[kcblus_1] / dump 5749075 High Requests on dc_rollback_segments. latch / US enqueue contention 6499872 ORA-01628: max # extents (32765) for rollback seg Transparent Application Failover 5406976 Dump (lxhscn) if DB calls out over NET with a FAILOVER clause 5415594 xa_commit returns -4 (XA_NOTA) after RAC failover 5444539 Database connections not released after database failover or recycle 5697333 ORA-25402 from TAF in RAC 5758870 ORA-3135 from TAF with SELECT type FAILOVER 6315913 ORA-3106 for SQL using BLOBs after TAF failover Transparent Data Encryption 4485775 OERI [qsmqLockTableSummarySubheap-1] selecting from materialized view with TDE enabled 5667253 Dump while selecting from encrypted table with CHAR column and subquery 5671774 Memory corruption due to TDE with imported certificate 6057069 Wrong results possible when the columns are encrypted 6207959 DBA_UPDATABLE_COLUMNS shows view as not updatable when TDE enabled 6328110 Select COUNT() with an encrypted column is slow Transportable Tablespaces 4087161 Tranport tablespace import ORA-904 for tables with XMLType columns 4545196 Corrupt index leaf from cross platform transport of compress-key indexes 4566516 Transportable tablespace does not handle domain indexes 4959915 ORA-39083 / ORA-1647 during TTS import of a range-list partition table 5037851 ORA-31000 from DBMS_TTS.TRANSPORT_SET_CHECK with XDB 5936058 Corrupt metadata from tablespace transport 6059327 ORA-39083 / ORA-1647 during TTS import of subpartioned table 6075487 OERI[kddummy_blkchk] for DDL on plugged ASSM tablespace with FLASHBACK Triggers 5115882+ Wrong returned value from UPDATE .. RETURNING with before ROW trigger 4069679 USERENV of SESSIONID returns 0 when used in a logon TRIGGER WHEN clause 4352110 ORA-39125 from expdp/impdp of triggers with nulls in WHEN clause 4768022 ALTER TABLE can fail with ORA-60 4893136 OERI:17287 dropping / creating triggers that use the "CALL" statement 5118210 OERI[kopuigpfx1] on insert to table with sdo_geometry column with INSTEAD OF trigger 5256791 Trigger "UPDATING('col')" clause can return TRUE when column not updated 5350339 ORA-979 using TIMESTAMP in triggers and GROUP BY clause 5579055 Dump (kxccres) updating view with instead of trigger 5616820 Triggers using :OLD values of TIMESTAMP columns see :NEW values instead 5676637 OERI[17114] using EMPTY_CLOB() in a trigger 5685411 Updating columns to NULL in a trigger may have no effect 5872835 Multiple trigger execution from SERIAL insert as Parallel select Truncate 4344935 OERI from DML on TEMPORARY TABLE after autonomous TRUNCATE 5213452 Fast refresh fails with ORA-936 after truncation of default LIST partition 6086497 OERI[ktspgetmyb-1] / bitmap segment corruption for ASSM segments 6776107 TRUNCATE of highly partitioned table can be slow Wallet Manager 5551624 ORA-28353 creating a wallet Workload repository / reporting 4632024 MMON reports spurious high version count SQL 4748642 ORA-6502 error encountered in top blocking sessions in ASH 5088977 MMON dump (in keltfill) intermittently 5239294 ORA-1403 failure in AUTO_SPACE_ADVISOR_JOB_PROC 5245039 Tablespace space used % alert not triggered when used space is > 320gb 5376783 DBMS_SPACE.OBJECT_GROWTH_TREND can perform excessive IO 5486074 OERI [keltnfy-ldminit] when DNS is not available 5974572 WRH$_SERVICE_STAT can grow very large in RAC Wrong Results 6646613* IOT corruption after upgrade from <= 9.2 to >= 10g. This bug is alerted in Note 471479.1 4925103+ Wrong results using MAX() on column containing NULLs 5115882+ Wrong returned value from UPDATE .. RETURNING with before ROW trigger 5146740+ Wrong results with bind variables/CURSOR_SHARING 5383936+ Wrong results from Parallel Query with OUTER join and HASH join 5686711+ Wrong cursor may be executed if schemas have objects with same names 6044413+ Intermittent wrong results when table prefetch occurs 5010657P HPUX-Itanium: No rows from V$OSSTAT / incorrect CPU_COUNT 4319031 Wrong header_status in V$ASM_DISK when disk is offline 4346448 NLS_COMP = ANSI gives wrong results comparing CHAR with VARCHAR2 4372359 Wrong results from temp table star transformation 4407269 Wrong result with nested loop parallel query with ROWNUM pushdown 4424952 extractValue returns wrong result 4459574 FLASHBACK_TRANSACTION_QUERY shows multi row INSERT as SELECT as only one row 4490782 Unparse operations give wrong date for BC TO_DATE literals 4538727 Applied column is not updated in V$ARCHIVED_LOG 4552696 DBMS_Scheduler is suppressing no_data_found exceptions in jobs 4596532 Wrong results from V$XML_AUDIT_TRAIL 4644351 OERI[15819] / wrong results from parallel select 4668012 Wrong results from IS_ALTER_COLUMN / IS_DROP_COLUMN for partition operations 4692059 Wrong results from SQL with subquery with multi-column correlation predicate 4694156 TIMESTAMP column in DBA_TAB_MODIFICATIONS not updated 4704779 Incorrect histogram type shown (frequency/height-balanced) 4725022 Wrong results from a function call using a CONCAT of a NULL 4743582 Intermittent wrong results from TABLE SCAN with COL1 relop COL2 predicate 4770292 Wrong results from CONNECT BY query on IOT with secondary index/es 4865959 Wrong results / exception from Java Stored Procedure accessing data over DBLINK 4874013 INTEGER may show SCALE as -127 4892567 DBMS_XMLPARSER does not validate XML document against a DTD correctly 4898580 DBMS_METADATA.GET_DEPENDENT_DDL does not show comments on materialized view columns correctly 4901291 Wrong results with left outer joins on view with a function 4904743 ALTER SESSION SET NLS% does not work if OCI_PARSE_ONLY used 4905638 Wrong results / errors in session that opens the database for certain NCHAR characterset 4916783 Wrong results from query using INLIST predicate if FUNCTION BASED index 5010879 V$SESSION slow and does not show any BLOCKING_SESSION column data 5017909 V$SQL / V$SQLAREA.SQL_FULLTEXT corrupt for multibyte 5021304 V$PARAMETER view of AUDIT_SYSLOG_LEVEL looses all characters after a "." 5035058 V$LOGMNR_CONTENTS.MineValue may not show an UNDO value 5040555 DBMS_SPACE.OBJECT_GROWTH_TREND output is not correct 5049938 Wrong result order from query with ORDER BY of COUNT(col) 5083393 DBA_FREE_SPACE FILE_ID / REL_FNO may be wrong 5087155 DBA_DATA_FILES and V$DATAFILE views do not show all files 5097836 Wrong results / OERI:15818 from parallel query with range TQ 5119354 OERI from CONNECT BY and correlated START WITH columns 5120476 No blank padding with multibyte charset if no character set conversion 5126270 Version 3 TIMEZONE check script (utltzuv2.sql) 5161523 Wrong results / slow Parallel query due to data skew on multi-key table queues 5162768 Wrong results using more than one OLS policy on a table 5169684 Wrong results (all rows no filtering) when rewrite enabled on a view 5175364 Data truncation / null data selecting NVARCHAR2 over TG4MSQL 5179313 INSERT /*append parallel*/ can corrupt an index 5182679 INSERT as remote SELECT using CASE can produce wrong data 5188321 wrong results (no rows) from ANSI outer join 5190543 Wrong timestamp from oracle.sql.TIMESTAMPLTZ near daylight savings transition 5197305 NON_SCHEMA_DDL option skip() setting causes type bodys to be skipped 5199213 Very bad plan for UNION ALL and push constant predicate / Wrong Results 5205394 Corrupt XML element data converting to generalized object 5236881 Wrong Results (More rows) with a CONCATENATE of ANTI joins 5245038 Wrong results with query against a list partitioned table with null partition key 5252496 Wrong result when using a LIKE predicate with NLS_COMP = LINGUISTIC 5258521 OERI[kkpapDimToLevel1] from parallel query with partitioned tables 5259741 DBMS_XMLGEN.CONVERT trims output for multibyte database 5286826 Wrong results from complex view merge with windowing 5298826 Wrong results from SQL using DETERMINISTIC function/s 5299237 Inconsistent results from v$logmnr_contents with committed_data_only 5302124 Join Predicates are not push inside window functions -- superceeded fix 5327132 Wrong results from colocated OUTER join over DBLINK with TO_DATE 5345571 Wrong results with UNION and a subquery 5348010 Wrong results using ROWNUM < # and optimizer uses bitmap conversion count 5350076 Anydata and timestamp can loose precision 5367514 Wrong number of exceptions returned executing a bulk insert 5370626 Wrong results (more rows) on a parallel query over one partition with anti/semi join NL. 5376015 Wrong results with hash semijoin when build rows do not fit in memory/Spill to disk 5377092 Wrong results from FAST FULL SCAN of an index on a CASE expression 5381446 Wrong results / dump from STAR transformation with INDEX join 5395270 OERI[qctcte1] / dump / wrong results from view merging 5397482 Wrong results from Star transformation with transitive join predicate 5401876 wrong results when optimizer uses "BITMAP CONVERSION" over "BITMAP OR" 5403791 Wrong results for query with ROWNUM and ORDER BY 5403855 Wrong result with sql_trace = true when prefetch is active 5415881 Wrong sort order returned by query 5417281 oracle.sql.DATE looses a year when constructed from BC Timestamp 5437445 Incorrect username displayed from logminer adhoc query when auditing is on 5452234 V$LIBRARYCACHE "gets" accounted wrong 5455093 Wrong results from PQ with hash distribution with fixed CHAR join keys 5462687 CHECK constraint can cause wrong results 5468695 TIMESTAMPTZ wrong near daylight switch 5475037 Feature usage statistics incorrectly show 'Advanced Security' to be used. 5481520 Wrong results with ROWNUM and bind peeking with fix for bug 4513695 5481650 GV$SESSION.blocking_session has incorrect value 5487686 Wrong results from CONNECT BY query 5488790 Wrong results from Parallel Query 5490501 Wrong Results with COALESCE or NVL2 on aggregations inside subqueries 5494008 Wrong results from LIKE in multibyte when NLS_COMP=linguistic and NLS_SORT=binary_ci(ai) 5497168 Wrong results isolation_level=serializable and WITH clause 5507887 Wrong results for CONNECT BY using CONNECT_BY_ISLEAF 5512415 Wrong result from star transformation with EXISTS subquery 5524408 Wrong result when query has 256+ bind variables on partitioning column 5526851 Wrong Results (missing rows) on CONNECT BY when using function-based index 5527591 DBA_TABLESPACE_USAGE_METRICS USED_PERCENT/USED_SPACE may be wrong 5527727 Show parameter UTL_FILE_DIR may not show the parameter value 5531784 V$LOGMNR_CONTENTS CSF may be wrong 5533982 Updated columns set to null show old not-null values in change table using async CDC 5545735 Wrong values for V$SYSSTAT "open cursors current" 5549410 Inconsistent characters read returned from OCILobRead 5550614 Wrong results selecting BIGINT data from MySQL using MySQL ODBC driver 5552515 Incorrect V$SGASTAT information for "ktcmvcb" 5556025 Wrong Results from partition pruning and ORs 5568316 Wrong results from star transformation 5569805 XMLelement query using outer join returns wrong results 5571916 wrong (duplicate) values with parallel and STAR (missing "PX block iterator") 5573425 Wrong results from subquery unnesting with complex view merge 5574966 Dump (evaopn2) or Wrong Results with views and function-based index 5576013 Wrong results (no rows) with partition pruning [PARTITION LIST ALL (LAST)] 5580871 AQ bytes message <= 2000 bytes incompatible between PLSQL and Java 5585187 Wrong Results doing MERGE JOIN with a correlated subquery on the right side 5590163 Message dequeued more than once from single consumer queue 5590396 Dump or Wrong Results with ANSI JOINS and CONNECT BY 5592012 Wrong results with INLIST and UNION/UNION ALL 5600425 wrong results from select on external table 5604940 Wrong results from a join and extended partition naming 5608992 Wrong results from filter push with OUTER join 5632192 Wrong Results with Max/Min in subquery/view 5632264 Version 4 TIMEZONE files 5638080 Wrong sort order using window functions 5642214 Wrong results / ORA-1427 from scalar subquery in SELECT list with complex view merging 5650372 Wrong results / OERI[kkpapdrmfkk1] from predicate elimination on partitioned table 5666374 FIFO does not occur when multiple listens are followed by dequeues 5672041 Wrong information returned by DBMS_METADATA 5682441 Wrong Results (no rows) joining views with predicates using PLSQL functions 5690241 Dump / wrong results from OR predicate on partition columns 5694101 OCI piecewise operation returns wrong piece length for long / long varchar data 5698193 Wrong Results when using TRIM on check constraints or function based indexes. 5708633 Wrong results / dump [ldxite] from materialized WITH clause 5708897 Wrong results from ROWNUM with semi/anti join 5715742 XMLTransform() truncates output without error message 5725761 Objects with debug privilege are not shown in the ALL_OBJECTS view 5731952 MERGE statement does not insert rows if source is a (inline) view with parallel 5759075 Wrong results from PQ with HASH on ANSI CHAR join 5762846 wrong results from filter push down with non-deterministic function 5763538 Wrong results / dump with object type column in SQL 5763576 Wrong results from XMLForest() 5837795 Wrong results / OERI from cost based CONNECT BY 5838153 CAST operator does consider NLS_LENGTH_SEMANTICS 5840483 ORA-937 / ORA-979 not occurring with subquery GROUP BY 5843316 Wrong results with index join and function-based index 5847521 Hierarchical (CONNECT BY) query on IOT returns wrong results 5862057 Oracle JVM incorrectly returns true for "x instanceof object[]" when "x" is a class 5865842 DBA_REGISTERED_ARCHIVED_LOG.DICTIONARY_END contains extra space for 'NO' value 5870781 DBMS_LOB.INSTR() function does not find patterns across the 4gig boundary 5872956 Slow or Wrong Results on CONNECT BY queries with constant predicates 5879627 Wrong results with ROWNUM restriction 5882372 Wrong results from CONNECT BY 5885079 Incorrect output from INTERVALDS.stringValue() for negative intervals 5888733 Wrong results from V$LOGMNR_CONTENTS referencing AUDIT_SESSIONID 5889927 Wrong results from view with un-correlated subqueries 5893396 Wrong results possible due to invalid stored outline 5893779 Intermittent wrong results when table prefetch occurs - superceded fix 5902410 V$RECOVERY_FILE_DEST.SPACE_RECLAIMABLE and V$BACKUP_FILES.OBSOLETE wrong for retention policy NONE 5903293 Wrong Results for Parallel Query using Group By or Distinct or has correlation 5903581 Wrong Results with "Connect By with Filtering" 5906937 Wrong result using ROW_NUMBER in SQL using a WITH query block 5921386 Wrong result doing view merging and outer join 5923491 ALL_UPDATABLE_COLUMNS shows view is not updatable when it is 5924763 Rows missing from V$XML_AUDIT_TRAIL 5932203 Wrong result when comparing same column with values of different datatypes 5938452 VPD does not work when a CURSOR expression is used against a synonym 5947231 Wrong results from parallel STAR query (with temp_disable) 5961654 ldiinterfromtz returns wrong offset during DST fallback 5970288 OCCI isNull() on object column always returns false even when object is null 5981212 Wrong results (SORT ORDER BY STOPKEY pushed below a FILTER) in PQ 5985257 Wrong results from UTL_I18N.TRANSLITERATE using 'hwkatakana_fwkatakana' 5985594 Wrong (empty) result set for queries using "OR" 6005762 SYS_CONTEXT('USERENV','AUTHENTICATION_METHOD') returns NULL 6005996 DBMS_METADATA.GET_DDL generates incorrect DDL with UNUSED columns 6016075 Wrong Results for query with correlated subquery and predicate pull up 6017760 DBMS_METADATA.GET_DDL does not show changed datafile attributes 6027610 Wrong results from CONNECT BY query 6029071 Wrong results from distributed SQL with OUTER joins 6038461 Wrong results from SQL with UNION and a fast DUAL subquery 6050882 Wrong results from ANSI outer join with fix for bug 4967068 or 5864217 6051782 Wrong results using GROUPING SETS with ORDER BY and DISTINCT 6057069 Wrong results possible when the columns are encrypted 6070548 Dump (qertbGetPartitionNumber) / wrong results from bitmap access to IOT 6084485 Wrong result when aggregate column selected twice with ORDER BY 6084512 DBA_UNDO_EXTENTS shows dropped undo segments 6085625 Wrong child cursor may be executed which has mismatching bind information 6088227 Wrong Results with with count() and IS NULL 6114833 Logminer does not signal error if log unavailable in continuous_mine 6119884 Wrong results with query with OR operator with OR expansion 6156762 OCCI fractional seconds portion can be wrong 6158287 Wrong results from PQO with EXISTS subquery 6207959 DBA_UPDATABLE_COLUMNS shows view as not updatable when TDE enabled 6266023 V$ARCHIVE_DEST_STATUS reports false "destination has a gap" for disabled redo thread 6314151 '1/1/1988 0:0:0' in COMMIT_TIMESTAMP$ column when CDC apply error is re-executed 6316993 Wrong results / dump (qernsRowP) from join back elimination of 1 row table 6333108 Wrong results (duplicates) from CONNECT BY query 6400795 Wrong results from view merging 6450021 Wrong results from X$ / V$ / DBA_* views for file numbers > 32k 6653652 Wrong results from simple view merging Wrong/Bad Shared Cursor 5686711+ Wrong cursor may be executed if schemas have objects with same names 5555683 Intermittent ORA-1801 when shared pool under pressure 6085625 Wrong child cursor may be executed which has mismatching bind information XA / Distributed Transactions 4308334 OERI[12314] during XA commit/rollback/prepare while attached to different transaction 4377584 OERI[18201] from concurrent xaorollback and xaoprepare 4736971 Delayed XA transaction recovery 4899479 Undo/redo corruption if distributed transactions used 5378806 xa_rollback cannot interrupt a long running SELECT branch 5384248 OERI[k2gtelock: !k2gtca] / instance crash cleaning up distributed transaction 5415594 xa_commit returns -4 (XA_NOTA) after RAC failover 5917836 V$LOCK does not show locks for attached XA sessions 5945463 XA clients should not require execute privilege on DBMS_SYSTEM 5968965 xa_recover on RAC may not return all prepared transactions 5983683 OERI[17182] creating / deleting XDB resource in XA environment XDB 3370858 Import fails (ORA-932) using FROMUSER / TOUSER for schema based xmltype 4277241 ORA-22813 for large xmlagg() with GROUP BY 4377659 Schema validation with number of nodes > 64k results in LSX-201 4387531 Spin running XPATH on SB table with IOT structured varrays 4424952 extractValue returns wrong result 4563159 SYS_XMLAGG fails with ORA-24347 if null value passed 4584641 Cursor leak using DBMS_XMLGEN with a PLSQL function returning sys_refcursor 4739114 Dump in shared server after using DBMS_XMLDOM 4877048 Dump (qmtModelGetMCA) on registering XML schemas using group 4887880 OERI:[qkactasrowvector_13] from CTAS with XML related operations 4892567 DBMS_XMLPARSER does not validate XML document against a DTD correctly 4931883 FTP PUT in XDB can be slow 4959294 DBMS_XMLSTORE does not follow CHAR based semantics 5018532 Insert / validate of valid document may OERI / dump 5037851 ORA-31000 from DBMS_TTS.TRANSPORT_SET_CHECK with XDB 5161782 Dump installing XDB 5205394 Corrupt XML element data converting to generalized object 5210484 ORA-21700 with xsd:restriction where parent has sqlinline="false" 5211545 Select with EXTRACT dumps in lxXmlGEntEsc2 5221989 ORA-30937 with chameleon schemas 5252061 PGA memory corruption / OERI[17456] creating a domain index 5253806 PLSQL DBMS_XMLDOM transformations may produce wrong non XML output 5259741 DBMS_XMLGEN.CONVERT trims output for multibyte database 5263631 EXTRACT query fails with ORA-31196 for XML schema using substitution groups 5326319 XMLType transform fails with spaces in parameters ORA-31011 5330677 XMLDB reports a validation error by mistake 5332686 Parsing XMLType (Opaque type) in Java fails 5347371 Dump [kkoojt] on a query against XML / XDB 5349808 IMP-60 hit when importing a table with an XML schema based XMLType column 5364613 Performance of XSL transform extremely slow 5377973 Register schema fails with ORA-4031 5382590 ALTER TABLE MOVE does not move all underlying objects of XDB table 5385791 ORA-932 with enumeration and complextype / simplecontent 5389917 ORA-30992 / ORA-1830 from XDB with DATE with TIMEZONE info 5391686 value().getnamespace() returns null 5392772 Corrupt XML output from SQLX 5399932 getrootelement() returns null even for valid single element node 5408970 Memory leak using XMLType() constructor on ADT in a loop 5437241 Dump accessing XML DOM in PLSQL 5437716 Wrong results with nested XML table operators 5471712 ORA-31067 from updateXML() with unescaped entities 5477912 Memory leak parsing DTD 5491132 xslprocessor.newStylesheet failS when XSL Document includes OS files 5497611 OERI[qctVCO:csform] from Xquery using XMLType constructor 5512159 doctype is appended to the XML when parsed against a DTD 5555833 Dump [kokees2c] from Xquery 5563913 EXTRACT is producing 'xsi:type="simple"' attribute after fix to 4713210 5569805 XMLelement query using outer join returns wrong results 5583634 OERI [17147] / dump after inserting a text node of size 64000 5586842 ORA-4045 / ORA-22973 from DBMS_METADATA with XML schemas 5655708 LPX-1 parsing a file using DTD loaded via parsedtdclob and setdoctype 5667235 ProcessXSL does not indicate if style sheet output is XML or not 5668025 XMLParser.Parse() can leak memory 5669015 Invalid ORA-29875 after creating number index on XML index 5687843 PGA memory leak inserting XMLDocument with many out of line elements 5690593 Datafile corrupt for ASM datafiles copied using xdb/ftp 5715742 XMLTransform() truncates output without error message 5716932 Memory corruption / OERI [17147] / dump selecting from PATH_VIEW 5734901 JDBC Thin XMLType.getDOM fails with SQLException 5735091 Memory corruption when using XMLAGG 5736250 Dump [kpotcpop] using XDB 5763576 Wrong results from XMLForest() 5766196 ORA-942 on schema level import of table with foreign key and XMLSchema 5856727 Query on schemaValidate XMLtype table fails with OCI-30937 5864763 ORA-30951 inserting valid XML document 5865159 Dump (in lxxmlgentesc2) accessing text node with size close to 64k 5872480 LPX-224 can occur in XDB 5892080 updateXML corrupts repeating elements 5920672 DBMS_XMLDOM ignores xml:space="preserve" 5947653 XE to EE upgrade fails in XDBx 5983683 OERI[17182] creating / deleting XDB resource in XA environment 6051977 DBMS_XMLGEN fails with OERI[qmxtcCtxConvertString] converting unescaped ampersand 6079393 ORA-918 on select from xmltype schema based table with 2 xmltable() used 6154575 XmlTransform does not have an option for 'pretty printing' XML 4087161 Tranport tablespace import ORA-904 for tables with XMLType columns 4745691 OERI[kghufree_06] from AQ propogation of XML payload Error May Occur 5501528I ORA-6545 recompiling with PLSQL_WARNINGS set 5752399P+ Sol: Mandatory Patch to use Oracle with Veritas or Solstice Disk Suite on Solaris 386181 ORA-12014 when creating a refresh complete / refresh force materialized view 2834295 ORA-12714 declaring cursor for a function that returns a table of NVARCHAR2 3370858 Import fails (ORA-932) using FROMUSER / TOUSER for schema based xmltype 3569503 PQ may signal a false ORA-8103 under load 3945156 ORA-979 from DBMS.GATHER_TABLE_STATS when NLS_COMP=LINGUISTIC 4038803 IMP-3 / ORA-1722 when using nls_numeric_characters != '.,' 4054238 ORA-12899 with complex aggregate expressions in a materialized view 4087161 Tranport tablespace import ORA-904 for tables with XMLType columns 4110313 ASM disk resize fails for OS devices grown after ASM instance startup 4277241 ORA-22813 for large xmlagg() with GROUP BY 4311273 ORA-2064 using MERGE statement over a database link 4377659 Schema validation with number of nodes > 64k results in LSX-201 4387531 Spin running XPATH on SB table with IOT structured varrays 4436832 False ORA-979 "not a group by expression" with literal replacement 4478139 ORA-28031 "maximum of 148 enabled roles" when creating queue table 4483439 ORA-904 error during Materialized View fast refresh 4517481 ORA-904 / ORA-20000 loading metadata with IMPDP using varying width characterset 4549673 ORA-30926 / OERI:13030 during update 4559546 Cannot used exp/imp of MVIEW with XMLTYPE column 4563159 SYS_XMLAGG fails with ORA-24347 if null value passed 4583442 ORA-22877 during move hash partition with LOB 4587117 ORA-384 can occur even if there is free space in some pool/s 4587572 ORA-12801/ORA-60 possible from parallel DML with grouping sets 4595736 ORA-6502 during impdp due to wrong logging_level put in export dump 4597871 ORA-904 from query using CUBE 4599177 Allow > 255 arguments to an operator 4609147 ORA-918 if PLSQL block has same package and function name 4624183 ORA-1017 reported using DB links with IDENTIFIED EXTERNALLY accounts 4627457 ORA-24042 from REMOVE_STREAMS_CONFIGURATION if queue_to_queue is true 4658456 ORA-920 from distributed query using CASE against remote table/s 4659734 RMAN-6900 RMAN-6901 ORA-19921 during RMAN commands 4663793 ORA-16224 on select from ALL_OBJECTS on standby with DataGuard 4680009 Insert LOB data fails with ORA-3106 or ORA-8176 4681763 ORA-6502 from DBMS_STREAMS_ADM.maintain_schemas if schema is empty 4682527 ORA-26762 from maintain_* scripts if source db name does not include dot (.) 4686909 CONVERT function reports ORA-1482 4690705 Repeated ORA-1041 from heartbeat ping 4730249 Logical Standby or Adhoc query fails with ORA-1801 when using a different characterset 4736557 ORA-1466 on read only transaction 4740187 ORA-30353 creating materializer view with SYSDATE in the refresh clause 4760728 ORA-38301 during DROP TABLE when already dropped from a different node 4766696 Loader LDR-297 / ORA-1756 from SQL / expression ending with a single quote 4889807 False ORA-904 from co-located join (over database link) 4904904 Problems with DBMS_SCHEDULER JOB_START time (eg ORA-1877) 4905638 Wrong results / errors in session that opens the database for certain NCHAR characterset 4959915 ORA-39083 / ORA-1647 during TTS import of a range-list partition table 4966024 VLM buffer leak on if an error occurs 4996004 EXPDP fails with ORA-31642 when NLS_SORT=binary_ci and NLS_COMP=ansi 5015547 Cannot create a materialized view over a database link (ORA-942) 5017909 V$SQL / V$SQLAREA.SQL_FULLTEXT corrupt for multibyte 5027003 ORA-39068 from EXPDP if parallel > 1 5037851 ORA-31000 from DBMS_TTS.TRANSPORT_SET_CHECK with XDB 5040073 ORA-27047 from DBMS_STREAMS_TABLESPACE_ADM pull tablespace 5064356 RMAN backup to NFS slow due to "noac" requirement / ORA-27054 if not set 5095815 Select with CONTAINS predicate on view fails 5120780 Long text for job gets EXP-85 ORA-6502 on dbms_sched_job_export 5130238 ORA-28583 in external procedure 5130732 Query using "WITH" clause can fail with ORA-942 5131157 OCI may error reexecuting a statement against a table with an altered column type 5135951 ORA-22337 on import if database schema has been evolved 5136425 ORA-32337 from ON COMMIT MATERIALIZED VIEW after a direct load 5141429 "skgspawn 27142" errors and defunct Oracle processes 5147006 DML error logging fails with lower case identifiers 5179313 INSERT /*append parallel*/ can corrupt an index 5190392 Drop of table with triggers fails (ORA-16227) on logical standby 5205636 Apply fails with ORA-26687 while dropping a table with referential constraints 5209867 ORA-38777 is thrown by MRP when flashback through resetlogs 5211984 Parse errors with USE_STORED_OUTLINES 5213452 Fast refresh fails with ORA-936 after truncation of default LIST partition 5217296 ORA-32411 reported on materialized view refresh 5220562 ORA-4030 (sort subheap,sort key) on insert a partitioned table with concurrent DDL 5221989 ORA-30937 with chameleon schemas 5228136 ORA-26065 from SQLLDR direct path load of objects containing a LOB and constraints 5228711 ORA-604 trace from PQ slaves with FGA policy 5229137 PLS-201 compiling program units referencing tables on RDB 5238386 ORA-322 possible reading standby redo log header 5245451 Intermittent ORA-904 referencing remote objects columns 5252389 CDC apply changes lead to maximum open cursors exceeded (ORA-1000) 5254198 ALTER USER SYS IDENTIFIED BY VALUES does not change the password file 5254759 ORA-12801/ORA-1008 occurs on a parallel query with bind variables 5259868 Text query using index in another schema fails (ORA-20000, DRG-50857) 5263631 EXTRACT query fails with ORA-31196 for XML schema using substitution groups 5278539 ORA-23605 on create of new capture 5287523 ORA-16216 starting SQL apply after rolling upgrade completion 5299546 ORA-942 from create materialized view with join between local and remote tables 5308692 ORA-1426 error when running DBMS_STATS.GATHER_FIXED_OBJECTS_STATS 5324773 Constraints using LTRIM() may fail for valid data 5326319 XMLType transform fails with spaces in parameters ORA-31011 5330677 XMLDB reports a validation error by mistake 5349808 IMP-60 hit when importing a table with an XML schema based XMLType column 5350339 ORA-979 using TIMESTAMP in triggers and GROUP BY clause 5354437 ORA-1435 on create materialized view of UNION ALL from different sites 5360422 Datapump export from logical standby fails with ORA-39004 / ORA-39091 / ORA-44004 5368266 ORA-904 using multiple TABLE() objects in the FROM clause 5370332 ODCITableFetch fails with ORA-28579 5374844 ABN model build fails using dataset in excess of 100,000 rows 5376108 ORA-1109 when shutting down the database with AUDIT_TRAIL=DB 5386986 Leak / ORA-4031 leak when DROP UNUSED COLUMN issued on large partitioned table 5387478 ORA-28132 for user with EXEMPT ACCESS POLICY privilege 5387683 ORA-27103 / ORA-27129 during media recovery 5389756 False ORA-29907 error when using domain index operator 5389917 ORA-30992 / ORA-1830 from XDB with DATE with TIMEZONE info 5391326 ORA-942 importing functional indexes as SYS 5391505 High PGA consumption for query (kxs-heap-c) from OR expansion 5400311 ORA-1436 using "_old_connect_by_enabled"=true 5402151 ORA-439 when importing into Standard Edition db using streams_instantiation=y 5411244 ORA-4022 raised while rebuilding index partitions concurrently 5413989 OCIStmtSetPieceInfo() does not work for piece sizes > 16777180 5415506 ORA-4020 when dbms_aqadm.purge_queue_table and select are run 5417204 ORA-19639 on RECOVER COPY OF RMAN 5442919 Expired extents not being reused (ORA-30036) 5448714 ORA-1455 on RMAN backup database for files over 4Tb in size 5464834 ORA-4030 (kxs-heap-c,temporary memory) using EXPDP 5467520 PLSQL errors accessing synonym to remote object 5470034 ORA-1436 from TKPROF EXPLAIN of query using a WITH clause 5472523 Non violated deferred CHECK constraint fails (ORA-2290) at COMMIT 5479172 ORA-4031 with multiple partially-allocated permanent chunks 5485242 ORA-29701 in RAC environment 5493858 ORA-604 / ORA-1422 from materialized view operations 5494866 PLS-302 'dbver_10i' importing 10g export into 9i with AQ 5497630 ORA-3124 from NULL LONG bind for an UPDATE which matches no rows 5500044 ORA-44203 on table_x_x child from concurrent LOB append and drop partition 5502124 ORA-39096 importing 10.1 EXPDP file with 10.2 data pump 5508505 ORA-4031 while shared heap still has unused reserved extents 5514109 OERI [kql-hash-collision] / false ORA-955 5515882 ORA-1427 from EXPDP 5518651 ORA-1301 from dbms_logmnr_d.build 5523578 DBMS_AQADM.add_subscriber fails with ORA-1925 "maximum of x roles exceeded" 5530761 ORA-1031 from EXP of domain index 5531989 ALTER SYSTEM REGISTER may take a few seconds before connections allowed 5548389 Library cache allocation for 'column mapping' not using uniform sized extents 5551624 ORA-28353 creating a wallet 5555683 Intermittent ORA-1801 when shared pool under pressure 5557660 ORA-20 / process group leak from OCI Connection Pool connections 5564384 ORA-6502 assigning values from SQL to PLSQL variables 5567937 False ORA-1 / ORA-1403 from logminer rolling back IOT redo 5572026 ORA-942 / ORA-1031 in tracefile when starting the database as SYSOPER 5573238 Shared pool memory use / ORA-4031 due to "obj stat memo" in one subpool 5576828 ALTER PACKAGE does not always break NULL locks 5577046 ADD or DROP attribute causes UNION query to fail with ORA-1790 5583712 ORA-942 on create materialized view on remote view 5584105 ORA-1 against I_STREAMS_APPLY_SPILL_TXN in Streams apply 5594352 JMS-120 / OCI-1858 when dequeueing AQ bytes message with JDBC-OCI 5605319 Cursor leak from QMON coordinator exceptions 5613040 ORA-370 from DML against transported tablespace 5617311 ORA-1017 cannot connect through proxy using distinguished name 5618049 "mvobj part des" leaked memory after partition DDL (ORA-4031) 5623403 ORA-26773 invalid data type for "malformed redo" in Streams Capture 5630149 ORA-22877 from partition / subpartition MOVE of HASH partition 5632683 EXPDP / IMPDP may error for DDL modified tables 5636728 LOB corruption / ORA-1555 when reading LOBs after a SHRINK operation 5637976 ORA-8103/ORA-1410 from concurrent INSERT / export on ASSM tables 5641873 ORA-904 using a WITH clause that includes a UNION 5642214 Wrong results / ORA-1427 from scalar subquery in SELECT list with complex view merging 5643527 OCILobOpen/OCILobGetChunkSize do not return OCI_STILL_EXECUTING in non blocking mode 5645718 ORA-1476 gathering statistics with DBMS_STATS 5648610 ORA-25235 during AQ propagation 5653824 DBMS_LOGSTDBY.build may use wrong logs 5654013 EUS shared server connection fails with ORA-28030 5663447 ORA-27544 using HMP protocol in RAC 5664206 ORA-6502 during export of functional index expression over 4k 5674184 ORA-22282 when using LOB buffering 5677680 Starting SQL apply fails with ORA-1426 5689991 ORA-8176 fetching from global temporary table with INSERTS between fetches 5693948 ORA-31466 error when setting up CDC with table names using multibyte characters 5697333 ORA-25402 from TAF in RAC 5698225 ORA-17507 can occur using 16k block size with ODM 5699967 ORA-1120 executing "drop tablespace ... including contents'. 5711011 "SocketException: socket is closed" using RMI with shared servers 5713912 ORA-39125 / ORA-6502 from datapump import via network 5715079 ORA-1281 when applying a Patch Set on a logical standby 5716353 ORA-12899 from SQL Loader for valid data 5718757 ORA-31693 / ORA-6502 during datapump net import 5722178 ORA-1002 in non blocking mode 5724540 False ORA-1 from subquery partition pruning 5728347 ORA-20000, DRG-10599 occurs during text query through synonym 5733637 Select for update fails against TG4MSQL 5743325 ASM instance fails with OERI[kfaDropCOP04] 5757282 Broker commands to standby can error (ORA-16613) 5757711 ORA-15080 during file creation / resize on ASM with HARD 5758870 ORA-3135 from TAF with SELECT type FAILOVER 5762750 ORA-907 when cursor_sharing is enabled 5769454 CREATE INDEX fails with unexpected ORA-54 5840434 ORA-1200 if instance crashes / is aborted right after a datafile RESIZE operation 5844876 ORA-28550 from TG4SYBS 5847881 ORA-3001 from GROUPING SET query against a view containing a function 5852253 ORA-25316 from AQ after rollback to savepoint with loopback database link 5857884 EXPDP fails with ORA-39125 / ORA-6502 5863277 ORA-1008 from SQL on second run when cursor_sharing=similar/force 5870989 RMAN restore failover gives ORA-19864 error 5872000 Healthcheck errors for 32bit database on 64bit OS with fix for 4526916 5872368 ORA-22160 from DBMS_ADVISOR.TUNE_MVIEW 5872480 LPX-224 can occur in XDB 5872788 ORA-29821 importing OPERATORS 5879179 ORA-22925 from CSSCAN when reading CLOB data 5891213 ORA-6502 / LPX-7 from DBMS_METADATA.GET_DDL with domain index present 5900857 ORA-23619 from HS log based replication 5903293 Wrong Results for Parallel Query using Group By or Distinct or has correlation 5910237 EXPDP / DBMS_METADATA has wrong syntax for for nested table with row movement enabled 5924208 ORA-1031 from DDL due to using wrong shared DDL cursor 5924538 Logical standby apply fails with ORA-1427 for operations on IOTs 5932029 ORA-21000 when running RMAN "resync catalog" 5932181 RESYNC of RMAN catalog fails with ORA-1 (on TF_U2) or RMAN-20042 after switchover 5959987 Spatial aggregations fail with ORA-22813 5961454 ORA-29861 on DML with concurrent partition maintenance on different partition 5972794 EXPDP via network_link with parallel > 1 fails with KUP-4038 5973648 ORA-54 during concurrent parallel direct SQLLOAD in RAC 5974207 Unexpected ORA-1031 from LOB access - affects NCOMPed PLSQL 5977767 RMAN "minimize load" with "duration" causes backup to timeout 5999200 FSFO fails with ORA-16750 "failed to activate logical standby" 6018252 Insert statement with RETURNING clause fails with ORA-1031 6025805 ORA-14403 raised when executing select for update 6028753 ORA-907 / ORA-933 from DML over database link 6029647 ORA-12714 accessing typed column from TABLE() function 6035495 ORA-19909 during MRP / RMAN-600 on resync 6035889 ORA-28003 from create / alter user if password verification function contains special character 6059327 ORA-39083 / ORA-1647 during TTS import of subpartioned table 6075099 ORA-1476 from spreport (statspack) 6085625 Wrong child cursor may be executed which has mismatching bind information 6113520 Cannot add table into single table cluster (ORA-25136) 6136074 ORA-4068 / ORA-4065 ORA-6508 on VALID objects 6139547 Shadow process leak on ASM instance when diskspace exhausted (ORA-20) 6140330 imp / impdp cannot create object views with circular dependencies 6150438 COLLECT() does not work correctly for ADTs residing in different schemas 6162163 Wrong order of operations when mapping a buffer in the buffer cache 6268371 ORA-12996 / ORA-12998 / corruption from ALTER TABLE DROP UNUSED COLUMNS CHECKPOINT 6315913 ORA-3106 for SQL using BLOBs after TAF failover 6334552 Hang / ORA-4031 / OERI:kfrcsoDelete_3 on rollback of ASM file resize 6360220 ORA-21780 from subquery factoring SQL WITH clause 6379123 EXPDP/IMPDP ORA-39083 due to changes in MERGE privilege between 10.1 and 10.2 6436867 Recompilation may skip compilation of some dependent objects (ORA-4068) 6494820 CSSCAN fails with ORA-1455 on tables with more than 2^31-1 blocks 6680806 ORA-16139 from ALTER DATABASE COMMIT TO SWITCHOVER TO STANDBY 6762914 ORA-326 during Managed Standby Recovery after thread disable Internal Error May Occur (ORA-600) 5526987* ASM instance hang / OERI [2103] on DB instance. This bug is alerted in Note 468572.1 5605370* Various dumps / instance crash possible. This bug is alerted in Note 454464.1 6017420* OERI[kcbo_link_q_1] / crash with fix for bug 5454831 installed. This bug is alerted in Note 453309.1 6128197* OERI[kcrfr_resize2] / cannot recover database. This bug is alerted in Note 453259.1 6646613* IOT corruption after upgrade from <= 9.2 to >= 10g. This bug is alerted in Note 471479.1 4430244+ Segment advisor can load blocks of dropped objects into buffer cache (KCB OERI errors) 4450606+ LOB corruption / ORA-600 [ktsbvmap1] when updating a LOB 5081798+ Additional diagnostics for OERI[2103] when ASM involved 6110331+ OERI[kcbget_37] / OERI[1100] / spin possible 5841554I OERI:kqludp2 during upgrade to 10.2.0.3 5892355I+ Upgrade to 10.2.0.3 can fail with ORA-600 [22635] 3901785 SELECT FOR UPDATE with LONG may OERI[13009] 4061534 OERI[krvtadc] / dump in capture mining redo for COMPRESSed table 4095802 Concurrent DROP / LOCK against same table can fail with OERI[16608] 4119210 OERI[kkqgSetFields.2] possible from query rewrite 4200563 OERI[kkqsfcsi-1] from query rewrite 4254770 OERI:kzaSqlBindLob1 can occur with AUDIT_TRAIL = DB_EXTENDED for sql using binds 4308334 OERI[12314] during XA commit/rollback/prepare while attached to different transaction 4309607 ALTER TYPE CASCADE fails adding attributes to various types 4344935 OERI from DML on TEMPORARY TABLE after autonomous TRUNCATE 4377584 OERI[18201] from concurrent xaorollback and xaoprepare 4380471 OERI[kkqsfcsi-1] from query rewrite with an ORDER BY 4387531 Spin running XPATH on SB table with IOT structured varrays 4433838 Resizing cache crashes instance with OERI[kmgs_pre_process_request_6] 4440918 OERI[kewucmb_1] can occur 4482978 OERI[qkagby.noexec] on materialized view recompile 4485775 OERI [qsmqLockTableSummarySubheap-1] selecting from materialized view with TDE enabled 4541506 RMAN OERI[1880] when MAXPIECESIZE is set 4549673 ORA-30926 / OERI:13030 during update 4559728 Select lob from view loops / OERI [17059] if synonym dropped 4567042 Logical standby log apply may stop with OERI[knacend910] 4577403 OERI [kcbr_pending_3] during parallel recovery 4581220 OERI:kzaSqlTxtLob1 with fine grained auditing and parallel query 4584985 OERI[kclexpand_9] can occur 4587556 OERI:17069 compiling a package with a self referencing synonym 4596807 OERI[6002] on update statement with concurrent ONLINE rebuild of bitmap indexes 4600946 Dump / OERI[kghstack_free1] on array insert to COMPRESSed table 4614980 OERI:15448 from Text query 4634662 OERI:kolaslGetLength-1 from V$SQL in RAC 4643723 After type evolution extracting attributes gets OERI[17280] 4644351 OERI[15819] / wrong results from parallel select 4655998 OERI / dump from SQL involving SORT operations 4668719 OERI[kdtdelrow-2] from bulk insert 4674037 OERI:kclscrs_9 dumping processstate 4686006 OERI:[kkqsaljg:nobjs is 0] from view with exists and having clause 4694073 OERI[kgmgcdty2] possible from SQL using LIKE 4697252 OERI[kglsim_unpinhp2] can occur 4697632 OERI[atbbjie2] from exchange partition with bitmap join indexes 4702830 OERI[kkoljt1] when using star transformation with an ANSI outer join 4708822 OERI[kfiounidentify01] from PMON 4712638 OERI[15160] / dump [kkogbro] 4715375 OERI[kwqmtdel] in q00 process in RAC when any instance goes down 4744529 OERI:kclpred_1 / crash possible in RAC 4745114 OERI[kolrrdl:0rfc] using temporary LOBs in PLSQL 4745691 OERI[kghufree_06] from AQ propogation of XML payload 4767278 OERI[kcrrupirfs.20] archiving redo to standby with ASM 4864581 OERI [kkqtnlop2cbk : 1] on SELECT with extra parenthesis 4865755 OERI[9999] during DBMS_LOB operation 4868255 Dump (kpofdr) in executing a query with ORDER BY with row shipping enabled 4877360 OERI[kccscf_1] from CREATE CONTROLFILE with COMPATIBLE = 10.2 4887675 OERI[kgsclogoff-notempty] can occur during logoff 4887880 OERI:[qkactasrowvector_13] from CTAS with XML related operations 4893136 OERI:17287 dropping / creating triggers that use the "CALL" statement 4899105 OERI[19004] from multi table join 4899479 Undo/redo corruption if distributed transactions used 4902585 OERI[510] and ORA-28106 using application context over 30 bytes long 4904223 ALTER TABLE EXCHANGE PARTITION may dump / OERI 4939224 OERI[18095] during distributed autonomous transaction 4941795 OERI[kdtdelrow-2] during array DML if ORA-2049 occurs 4959652 Streams may get OERI [kwqbespayl518] 5008674 OERI [kkqsfcsi-1] from query rewrite 5015321 OERI[qerrmObnd1] [932] using binds with some functions over a DBLINK 5018532 Insert / validate of valid document may OERI / dump 5018886 OERI:[kwqitnmptme:wait] in Qnnn during propagation of delayed messages 5028099 OERI:kcbzwb_4 can occur using in memory undo 5029528 OERI:[qkacon:qkaconGetPathOps:1] from SYS_CONNECT_BY_PATH 5045992 OERI[kxspoac : EXL 1] from PQ with a numeric bind 5051602 OERI[17182] from SCROLLABLE select with duplicate columns 5060402 OERI[12325] can occur 5063279 OERI[kdibllockrange:not validated] updating a partitioned bitmap index 5063635 OERI[kccdagf_3] during file creation 5076729 OERI[pmucitnxt] doing type manipulation 5081271 PMON may crash the instance with OERI:kcblibr_1 during temp table cleanup 5084679 OERI from EXPLAIN_REWRITE CLOB interface with VPD 5084757 OERI when executing explain_plan with VPD 5099891 OERI using SQL with a SAMPLE clause 5112856 OERI[kghstack_underflow_internal_1]... [kkocxj : predtailpp] 5118012 Instance crash with OERI[kclswrite_3] with multiple DBW processes 5118210 OERI[kopuigpfx1] on insert to table with sdo_geometry column with INSTEAD OF trigger 5118272 Instance crash with ORA-600 [1433], [60] due to lgwr filling up msg blocks (Messages could be for LGWR or ARCH) 5119354 OERI from CONNECT BY and correlated START WITH columns 5126645 OERI [kkqtcorcbk: correlated string no] from CONNECT BY 5128625 OERI[17147] / OERI [17182] / NULL result from NLSSORT 5136863 OERI from join between partitioned table and domain index 5139572 OERI[qkauix2] on drop partition with parallelism 5154689 OERI[kql_tab_diana:new dep] / table dependency deleted in Streams 5155885 OERI[kkslgbv0] with CURSOR_SHARING=similar 5162852 Dump from FIRST / LAST aggregations on a NULL table 5163554 OERI[qctopn1] during join predicate pushdown 5165885 OERI[kclcls_8] or OERI[Kjbrchkpkeywait:Timeout] can occur in RAC 5177766 OERI[17059] with SESSION_CACHED_CURSORS 5183594 Logical standby apply stops / OERI [kghstack_underflow_internal_2] with SKIP / UNSKIP on SYS tables 5196175 OERI[kghstack_underflow_internal_1] with supplemental logging for LOBS 5216523 OERI[16608] from create materialize view on remote table with objects / types 5218905 OERI[kcbnew_3] when segment advisor has been used 5223587 OERI[4400] from distributed PDML with DDL 5228074 OERI[12455] raised from SQL with DOMAIN index when FOR UPDATE option is used 5234379 Dump in qknlazopn() from hierarchical query 5246372 OERI[opidsii1] accessing remote database accessing 3rd remote database 5252061 PGA memory corruption / OERI[17456] creating a domain index 5254539 OERI[qkacon:FJfsrwo] on executing hierarchical query 5258521 OERI[kkpapDimToLevel1] from parallel query with partitioned tables 5261145 OERI[12261] from dbms_mview.explain_rewrite 5262017 Query on partitioned table with bitmap index gives OERI[qernsRowP] 5307199 OERI:OCIOpaqueDataLoad1 can occur using ODCI with AnyData / AnyDataSet 5326327 OERI[qctbyt : bfc] using NLS_LENGTH_SEMANTICS=CHAR 5331374 OERI [kdiblsorget:rowidIllegal] updating partitioned table with row migration 5337352 OERI[kkqtcpopn: 0] during parse with subquery unnesting 5345999 Dump / OERI accessing V$SPPARAMETER 5347371 Dump [kkoojt] on a query against XML / XDB 5363258 Query rewrite can fail with OERI[voprvl1] 5364819 OERI[kkslpbp:1] when using literal replacement 5369855 OERI:733 or Spin (qksopLogSame) from star transformation 5371149 OERI[qctcte1] from query with CONNECT BY 5372831 OERI:26599 / dumps in JVM after database has been closed for recovery / opened 5374225 SDO_FILTER query fails with OERI[kdsgrp1] 5375583 LMS process dies with OERI[kclexpandlock_1] 5382842 Select fails with OERI[qctcte1] using cost based transformation 5384248 OERI[k2gtelock: !k2gtca] / instance crash cleaning up distributed transaction 5385614 Need diagnostics for OERI:ktrviupk_4 5385791 ORA-932 with enumeration and complextype / simplecontent 5387049 ALTER TABLE MOVE with 255 columns or more can dump / OERI 5388885 Hang / OERI[krvxbpns01] accessing V$LOGMNR_CONTENTS from RAC 5391575 OERI:[qkaconCompareOpn:dty] from CONNECT BY with HAVING clause 5395270 OERI[qctcte1] / dump / wrong results from view merging 5399670 OERI[keltgtyp] [22303] can occur 5400158 OERI[17078] / dump running Java DDL (loadjava) concurrently 5403150 ORA-603 when cannot get lock within Resource Manager "switch_time" in RAC 5405345 OERI[kkofkrMarkK] when running a query using a database link 5434872 OERI[qolgenol-1] when executing dbms_outln.create_outline 5452715 OERI[kwqbgqc: bad state] reported after restart of database 5454975 Dump executing DBMS_OUTLN.CREATE_OUTLINE 5471453 OERI[kfkfilrqarr01] using ASM 5476507 OERI[15868] / OERI[15160] can occur with cursor sharing 5476873 Instance crash due to PMON ORA-601 / OERI[ksudlp1] 5480607 OERI:kghstack_underflow_internal_3] from DROP_POLICY 5482174 pick release database error ora-00600 and ora-00036 after upgrade to 10g 5483613 OERI [kfgscAcquireLcl_6] in ASM 5486074 OERI [keltnfy-ldminit] when DNS is not available 5494240 OERI[15201] during select from an IOT 5496041 OERI[6006] / index corruption on compressed index 5496727 OERI[7005] possible with null bind 5497611 OERI[qctVCO:csform] from Xquery using XMLType constructor 5502365 OERI [kfcDel20] in ASM 5508574 OERI[504] / OERI[99999] / Dump [kgscdump] with > 31 CPUs 5512840 Logical standby fetch slave stops with OERI [knahfgx704] 5512921 Instance crash caused by SMON OERI[kcblus_1] / dump 5514109 OERI [kql-hash-collision] / false ORA-955 5526996 OERI[kjhn_post_ha_alert0-784] can occur in RAC due to racgimon problem 5527665 OERI[kcbkzx_3] / OERI[kcbkzs_6] for SCURRENT prewarm buffers 5529797 PGA leak / OERI KWQPCBK179 during Streams propogation 5530043 OERI [kkzg_add_ref_stmt_lst.1] can occur during materialized view refresh 5530697 OERI[kjshash:!esm2] in PQ slave process in RAC querying GV$ view 5532110 OERI[qcscpqbTxt] can occur 5548895 OERI [OCIKCallPush: deprecated] from EXPDP of ANYDATA column 5555908 OERI[kghstack_underflow_internal_2] in kfrcsoDelete 5558244 OERI[kcbnew_3] can occur 5566580 OERI:15817 using parallel query with a large number of columns 5567141 OERI[526] / hang with fix for bug 5508574 installed with > 31 CPUs 5567641 Streams capture terminates on restart with OERI[krvuatla] 5571643 OERI:[kfclAttachBuffer10] in ASM 5578157 Instance crash with ORA-600 [1433] (RSM has all message blocks) 5579699 OERI [smbGetNxtAloSiz:max] from query with large sort 5580497 Dump (kkeais) during query optimization 5583634 OERI [17147] / dump after inserting a text node of size 64000 5587421 LMS fails with OERI [kjmpmsg_1] 5590396 Dump or Wrong Results with ANSI JOINS and CONNECT BY 5594381 OERI[qkacon:FJswrwo] from CONNECT BY query 5599596 Block corruption / OERI [kddummy_blkchk] on clustered or compressed tables 5600050 LMON may fails with OERI [kjbrref:pkey] during DRM 5603197 OERI[qctvco:csform] from UPDATE SQL with a subquery 5612751 OERI:qertqosSetPart4 if STAR transformation is considered and rejected 5617382 OERI[qctcte1] with the fix from bug 5259868 5631836 OERI[kghalo4] can occur 5632050 OERI[kkpolpd12] / dictionary corruption from CONCURRENT partition DDL 5638146 OERI:kqlfFillBindData:1 for SQL with thousands of binds 5640593 Streams OERI:kwqbmcrcpts101 while spilling messages 5644951 OERI[rworupo.2] querying outline LOB with ORDER BY clause 5649326 OERI[kksfbc-reparse-infinite-loop] can occur after DDL on partitioned table 5650372 Wrong results / OERI[kkpapdrmfkk1] from predicate elimination on partitioned table 5652086 OERI[15160] from ANSI join 5654584 OERI[qernsRowP] when using DISTINCT on CONNECT_BY_ROOT 5660643 OERI[kkqsfcsi-1] during query rewrite of SQL with set operator 5660888 OERI[kzspvcr:1] using proxy authentication with > 16 roles 5669051 Query rewrite may dump in kkqsMMVNormalizeQBC 5670585 OERI [kxfxsSendCounter1] / OERI [15574] / spin from WINDOW query 5673934 ORA-12801 / OERI 15810 during parallel DML 5676637 OERI[17114] using EMPTY_CLOB() in a trigger 5676948 OERI [qxxmslSelectLocator_10] from SQL*Loader 5681955 SGA corruption in RAC (OERI [17114] / OERI [17112]) 5682184 OERI[kfdAuDealloc2] from resize/drop more than 16TB ASM file 5690100 RAC instance crash with OERI[kjbmpwrite:wip2] 5693140 OERI[kdtdelrow-2] from array insert with concurrent ALTER TABLESPACE READ ONLY 5694466 OERI[15160] from subquery unnesting 5695131 HW enqueue deadlock / OERI:1153 from array insert with SAVE EXCEPTIONS to READ ONLY ASSM segment 5695610 OERI[kxfpgsg] isolation_level = serializable in RAC 5702177 Instance crash from OERI[kghchoose_grow_1] 5707822 'alter table .. deallocate unused keep ..' fails with OERI[kcbgcur_2] 5712086 OERI[17147] / dump from TO_CHAR(date) with over long FORMAT string in multibyte 5730717 OERI:kclchkinteg_18 / LMS crashes the instance 5735146 OERI[6704] during SELECT FOR UPDATE 5736850 SGA corruption / crash from PQO bloom filter 5742127 RMAN backup sometimes fails if datafile grows during backup 5743325 ASM instance fails with OERI[kfaDropCOP04] 5744546 MMON OERI [1403] 5757106 OERI[15851] selecting aggregate of a constant with literal replacement 5757752 OERI:kghstack_alloc / OERI:kfcbCkpt04 / ASM crash 5762514 DBWR crashes instance with OERI[kcbbctsc_3] 5764556 OERI[kctdsb_internal_03] 5765958 OERI[qcscpqbTxt] / OERI[qcsfbdnp:1] from ANSI query in PLSQL 5837795 Wrong results / OERI from cost based CONNECT BY 5839280 OERI[15265] dropping OLS policy 5841624 OERI[kokeicadd2] accessing object with embedded substitutable attributes 5850776 OERI[kkqsMMVReAggRewriteExp:notoptfou] from query rewrite 5854634 OERI[qkshtQBGet:1] from CONNECT BY query 5855995 OERI:kksCallPopCallback possible after ORA-4030 5857313 OERI[kwqbmcrcpts101] after drop propagation 5860221 Apply aborts with OERI[17147] / memory corruption with FUNCTION BASED index 5864217 OERI [kkoljt1] from ANSI query with join elimination 5867231 OERI:qernsRowP on Text query with NLS_COMP / NLS_SORT set 5867943 Capture aborts with OERI[knlcloop-200] mining "ALTER TABLE SPLIT PARTITION ..." 5885908 OERI[12259] can occur instead of ORA-1001 5891280 MRP0 on standby may not start (OERI:krfg_aset_1) 5891737 Dump (kcblsod) / OERI:723 / Memory leak in ASM/RAC 5893340 OERI [32695] [hash aggregation can't be done] from hash aggregation 5894422 OERI[525] / OERI[kglsim_rebalru2] 5903829 OERI[qkshtTabInf2:1] can occur parsing a query 5923497 Select with constraints fails with OERI[12863] 5923866 OERI[2103] when database is suspended 5926074 OERI [12333] on update of more than one CLOB column 5928555 OERI[krastrso_reserve] during BACKUP BACKUPSET 5939115 ora-600 [kghstack_underflow_internal_1][pcols in kkpapdaextsqueryslvl] 5942097 OERI:qernsRowP from SQL with GROUP BY , ROLLUP and DISTINCT aggregates 5942476 OERI [kcrrcomp.4] can occur in Streams 5953355 OERI[klaprs_30] / OERI[klaprs_10] during SQLLOADER direct path load 5955764 OERI[kccirsd_4] during CONTROLFILE upgrade from pre 10.2 version 5964193 OERI[kkqsRewriteCorrCols-1] during query rewrite with ANSI joins 5981084 OERI[kcrrtcln.seqvio] can occur 5983403 PMON may crash the instance with OERI[kksStatsRecovery-Bad-Opcode] 5987000 OERI:qkxrPXformQbc1 can occur for SQL using a WITH clause 6005113 OERI[kclrwrite_7] in DBWn process followed by instance crash in RAC 6012053 OERI [qctcte1] from GROUPING SETs query 6013213 OERI[17183] selecting from X$KRBAFF 6013968 Hang / OERI:504 with patch for bug 5863519 installed 6013983 ASM signals OERI [kfdasecondaries01] / [kffrelocate87] during rebalance 6015158 OERI [kkshgnc-nextchild] can occur 6016087 OERI[15160] from subquery unnesting 6016707 OERI[kwqpuspse0-hwmack] from propogation 6026281 OERI[qeshCloseHTI.2] from spreadsheet query 6034040 Apply aborts with OERI [knlcfpactx:any_knlso] using RENAME_SCHEMA 6041317 OERI when inserting ASCII 0x0 into CHAR/VARCHAR2 with AUDIT_TRAIL=DB_EXTENDED 6041713 OERI[kkzdgdefq_oci - stexec] refreshing through definer rights procedure 6051977 DBMS_XMLGEN fails with OERI[qmxtcCtxConvertString] converting unescaped ampersand 6056865 Intermittent OERI [kcblci_1] using shared servers 6057203 Corruption / OERI [kcbchg1_6] from Parallel update 6057703 OERI[kclchkblkdma_3] can occur in RAC 6075238 OERI[qctcte1] on parse of query with views / subqueries 6075487 OERI[kddummy_blkchk] for DDL on plugged ASSM tablespace with FLASHBACK 6075582 OERI[kjbmpref:sh] / dump [kjmpbmsg] in LMS causing instance crash 6086497 OERI[ktspgetmyb-1] / bitmap segment corruption for ASSM segments 6118038 OERI[koputilcvto2n] on an ALTER TYPE 6129874 Illegal ALTER SYSTEM SQL allowed 6132301 OERI[kcb_pre_apply_1] when db_block_checksum is set to FULL 6136494 Capture process aborts with OERI [17112] / OERI [17147] 6140309 OERI[ktssupd_seg_2] from DBMS_SPACE_ADMIN.TABLESPACE_FIX_SEGMENT_EXTBLKS 6143117 Rare intermittent mutex problem 6145841 OERI[kologsf2] on COLLECT(..) with wrong datatype 6159522 OERI[qkaffsindex3] from ANALYZE TABLE .. ESTIMATE STATISTICS 6239052 LMS can crash instance with OERI[kjbrchkinteg:last] 6267094 OERI[kghstack_underflow_internal_1] recovering logical standby 6267208 OERI:2103 due to deadlock between PV enqueue and "slave class create" latch 6334552 Hang / ORA-4031 / OERI:kfrcsoDelete_3 on rollback of ASM file resize 6377317 OERI[ksfdrfms3] using ODM if a log corruption is detected 6408017 OERI[12811] optimizing a query against fixed view/s 6436867 Recompilation may skip compilation of some dependent objects (ORA-4068) 6452485 SGA memory corruption / OERI [17182] with fix for bug 6085625 6494146 OERI [kksfbc-reparse-infinite-loop] can occur 6597063 OERI [kfrpass2_03] can occur in ASM 6644215 OERI[krvxradfd] during autodelete of partial log on logical standby 6651027 OERI:kgkprrpicknext1 / dumps from DBRM 6674196 OERI / buffer cache corruption using ASM, OCFS or any ksfd client like ODM 6781496 OERI[KGHLATCH_REG4] on STARTUP with >61 CPUs in RAC with fix for 5508574 Process May Dump (ORA-7445) / Abend / Abort 5605370* Various dumps / instance crash possible. This bug is alerted in Note 454464.1 5648872* Dump (opidsa) from DESCRIBE of a cursor. This bug is alerted in Note 418531.1 5933477* Client <= 9.2.0.7 / 10.1.0.4 can dump when running against higher level database. This bug is alerted in Note 455832.1 6656824P DBW can crash with fix for bug 6087207 installed 2837580 Dump if SQL has > ~35000 literals 3197358 Dump when DBMS_HS_RESULT_SET is fetched out of sequence 3551896 Dump / spin from SELECT on V$SESSTAT 4095802 Concurrent DROP / LOCK against same table can fail with OERI[16608] 4202503 Parse errors possible using CONTAINS with cursor_sharing=similar/force 4204383 Dump [kkqtnlocbk] optimizing ANSI OUTER JOINs with subqueries 4216668 Dump from INSERT / MERGE on internal columns 4308334 OERI[12314] during XA commit/rollback/prepare while attached to different transaction 4335601 Dump can occur in lxsCntByte 4351422 Dump from CREATE TABLE AS SELECT (CTAS) over DB link 4369756 Log apply may dump [krvsmso] 4397693 Dump (apaqba) from multi table insert with WHEN clause under RBO 4406211 Dump (insLoadRowInfo) from MERGE SQL with false condition 4457221 Dump [under kdxcom] doing RMAN compressed backup 4491223 Dump selecting ROWID with a remote join 4583492 Dump possible using ADT columns when table has many columns 4587431 Dump (in kkqucsv) / spin from query with a multi column IN subquery predicate 4600946 Dump / OERI[kghstack_free1] on array insert to COMPRESSed table 4618715 Dump inserting into a view with OLS policy on tables 4620832 Dump in kzrtppg with multiple referential constraints and OLS policy 4655998 OERI / dump from SQL involving SORT operations 4664788 Query with UNION can dump in kkqudhus 4683638 Dump [nsoexc] raised from CREATE TABLE AS SELECT (CTAS) 4684209 Dump (under evaopn2) with transitive predicate from CHECK constraint 4687581 Dump (kcsgrsn) during SHUTDOWN 4702284 ORA-604 / ORA-902 from WITH clause with scalar subquery involving an object column 4712638 OERI[15160] / dump [kkogbro] 4726702 ALTER TYPE may dump (koktupd_dplvl) due to a REF dependency 4739114 Dump in shared server after using DBMS_XMLDOM 4755448 Dump [kxfxgf] on parallel slave processes when using PQ trace 4767996 Dump in HS with very long TNS connect string 4771851 Dump (kxccsrw) from INSERT .. AS SELECT / MERGE 4864149 Query rewrite with ORDER BY of grouping_id dumps in evagrp 4868255 Dump (kpofdr) in executing a query with ORDER BY with row shipping enabled 4868646 Dump from cost based query transformation 4877048 Dump (qmtModelGetMCA) on registering XML schemas using group 4895068 Dump [kopxccc] during pickling 4899479 Undo/redo corruption if distributed transactions used 4905112 CREATE OUTLINE on DML using an indexed partitioned table may dump (kauxalo) 4912371 Dump possible in kohrsmc() 4927556 A dump can occur in kewmprepspsylstat() 4927563 Dump in qerixGetKey 4929094 Client side dump under OCISessionGet using OCISessionPoolCreate with OCI_SPC_HOMOGENEOUS 4932527 Dump (under kopp2atsize) processing nested objects 4969005 Dump [kglLockIterator] querying V$ views 5001547 Dump (kkoVerifyBindEquivalence) can occur 5018532 Insert / validate of valid document may OERI / dump 5022061 Dump [kkessc] optimizing query with inequality join if INDEX SKIP SCAN considered 5023743 Dump (kkqucpon) from query with aggregate subquery 5033488 Dump in kokmrwo from CONNECT BY 5034323 Dictionary corruption when adding a subpartition to a table with a key compressed local index 5058503 Dump[kkogtp] can occur selecing ROWID from a join view 5073249 Dump from fast refresh of MV using "WITH .. AS" 5074285 Dump [eorealize_xref] from stored Java using reflective methods 5088977 MMON dump (in keltfill) intermittently 5089444 Dump (kkodsel) from select with a subquery with star transformation 5092843 Dump (kpceclose) in EMON 5094908 Dump (kokbBuildExplodedTree) recompiling a view after upgrade to 10.2 5096560 Dump (selexe) when recompiling a materialized view with a UNION 5113934 PQ slave dump in qerixGetKey() when using bitmap index access 5118104 Dump compiling PLSQL using pseudo columns with INSERT .. RETURNING 5120395 Dump [ksupgpq] queryung X$KSUPGP (eg by DBMS_STATS) 5128368 Dump [kkoeqv] optimizing a query with nested views 5128933 Dump from DBMS_SQL selecting TIMESTAMP data over a database link 5150562 Dump expCheckExprEquiv from pipelined function in hierarchical query 5161782 Dump installing XDB 5163554 OERI[qctopn1] during join predicate pushdown 5169247 Dump (eg in qkarid) from SELECT FOR UPDATE after table elimination 5179008 Dump (kjzhablar) possible in RAC 5182299 Dump on grant / revoke of privileges on a TYPE 5183729 Dump (kkmins) from insert into a view 5192858 DROP TABLE with object type column with statistics can dump (kknerd) 5194354 DUMP[kghalp] when executing query with index using REGEXP_SUBSTR 5195356 Dump (memcpy) under kudmprcbk() when accessing external table 5196061 Dump in evaopn2() from WITH query using WINDOW functions 5206570 Dump (ksusrs) when session is sniped 5211545 Select with EXTRACT dumps in lxXmlGEntEsc2 5216642 Dump from SQL using window functions 5220760 Dump in NetLocalGroupGetMembers 5225168 Dump (evaopn2) from CONNECT BY 5225836 DROP TYPE .. VALIDATE dumps for large partitioned table 5226383 Dump (kkpapDiGetRange) from subquery pruning with composite partitions 5234379 Dump in qknlazopn() from hierarchical query 5242942 Client dump (OCIPClearMxCtr) using stateless connection pool 5243259 Dump (lxgcnv) can occur using CONVERT with bind variables 5258410 Dump [eoa_scan_mark_object] using stored Java threads 5285966 Dump [lxhlod] on select passing NULL for NLS parameter to a function 5292883 Dump from OCI client using OCI7 olog() call 5334170 racgevtf can dump in lmmstfree 5337099 Dump using oradebug during shutdown 5345999 Dump / OERI accessing V$SPPARAMETER 5358150 Dump (apaqbd) using CAST with cost based transformation 5362021 Dump from SQL using user defined functions 5364819 OERI[kkslpbp:1] when using literal replacement 5372831 OERI:26599 / dumps in JVM after database has been closed for recovery / opened 5377099 Dump [kksfreeheap] / OERI:504 / SGA corruption / crash possible 5381446 Wrong results / dump from STAR transformation with INDEX join 5387049 ALTER TABLE MOVE with 255 columns or more can dump / OERI 5395270 OERI[qctcte1] / dump / wrong results from view merging 5397953 Dump [kkpapItgetAll] accessing partitioned table using multi column INLIST 5400158 OERI[17078] / dump running Java DDL (loadjava) concurrently 5403150 ORA-603 when cannot get lock within Resource Manager "switch_time" in RAC 5403398 Dump when costing user defined operators / functions 5406976 Dump (lxhscn) if DB calls out over NET with a FAILOVER clause 5409593 Parallel insert as select into partitioned table can dump 5412994 Dump in ksrchconnect_ctx leading to instance crash 5437241 Dump accessing XML DOM in PLSQL 5440119 Dump in kkogast 5442534 Dump in kokscold assigning NULL to CLOB 5446630 Dump (nszgclient) using USERENV of AUTHENTICATION_METHOD 5454388 OPROCD dumps with fix for bug 5015469 5455632 Dump accessing tables over a database link 5459023 Dump (krccrpio) can occur 5479902 Dump qertbStart running query on partitioned table 5487604 CRSD core dump 5488174 Dump [evaopn2] on a CONNECT BY query 5504989 PMON dump [kfgGlobalClose] / instance crash 5508574 OERI[504] / OERI[99999] / Dump [kgscdump] with > 31 CPUs 5513123 DUmp [kkfies] from SQL using functional indexes with subqueries 5550618 Dump [nszgclient] from EXPDP 5555833 Dump [kokees2c] from Xquery 5570942 Query Rewrite causes high parse time with high hits on 'latch: row cache objects' and dc_object_ids / Dump in STRLEN 5572957 Dump (under kkqssjsce) with query rewrite enabled and heavy load 5574966 Dump (evaopn2) or Wrong Results with views and function-based index 5576865 Dumps in strlen/kpodpmop/kpodpp errors during IMPDP 5579055 Dump (kxccres) updating view with instead of trigger 5586632 Dump (qkaGranuleIteratorTraverse) on query on partitioned tables 5590396 Dump or Wrong Results with ANSI JOINS and CONNECT BY 5606145 Dump parsing query with IN subquery with SET operation 5610906 HSODBC dump invoking Data Dictionary translation query multiple times 5611623 Parallel query slave dump (kkpapitsize) 5619833 Dump (qerixGetKey) from query rewrite on join including functional index 5634026 Dump using SYSLOG auditing on SYS operations 5640904 Dump (kcsgrsn) while writing redo buffers to trace 5649765 Dump [evaopn2] from star transformation with pushed predicate 5656948 Dump returning collection from ODCIAggregate 5667253 Dump while selecting from encrypted table with CHAR column and subquery 5670294 Dump (qknviAllocate) using star transformation 5682195 Dump (lstmclo) evaluating regular expression in case insensitive mode 5686412 Dump (evaopn2) from query using functional index 5690241 Dump / wrong results from OR predicate on partition columns 5703276 Dump [kxtogiop] 5707754 Dump can occur executing a large query 5708633 Wrong results / dump [ldxite] from materialized WITH clause 5712202 Dump [qcuCatNames] can occur when trying to signal an ORA-904 error 5715079 ORA-1281 when applying a Patch Set on a logical standby 5721502 Non blocking client may dump executing PLSQL 5721821 SGA corruption / Dump[kglobcl] / crash if objects dropped / recreated 5743829 DG Broker process dump 5747782 Update of a partition table with UNUSED columns dumps [kdddcp or kdtInsRow] 5753629 Query may dump [in kpopfr / kposdi] 5759876 Dump [rfm_get_chief_lock] on Broker startup 5763538 Wrong results / dump with object type column in SQL 5765361 Client dump using OCIDirPathPrepare in OCI_UTF16ID mode 5766450 Dump [kkomprf] when attempting STAR transformation 5796376 Dump [kkobrak] from index join with a FUNCTION based index 5845347 Dump [kkogbys] parsing SQL with GROUP BY 5845901 Dump from concurrent CREATE MATERIALIZED VIEW and DDL on base tables 5857949 Startup may fail due to dump [rfmsoexinst] from DMON 5863519 Instance crash due to LMS dump (in kclcsr) 5865159 Dump (in lxxmlgentesc2) accessing text node with size close to 64k 5868656 MMAN dump (kghlkaftf) 5889331 Dump from cost based optimization of INSERT .. SELECT with function based index 5891737 Dump (kcblsod) / OERI:723 / Memory leak in ASM/RAC 5892453 Dump [ldxeti] from certain DATE expressions 5894403 MRP0 process fails with SIGFPE in kcrarmb 5908945 Dump [qxopqdca] with ancilliary operator 5912350 Dump (kdr9ir2f0rst4srp0) on select of compressed table having > 255 columns 5922733 ASM dump in kfkdumprq with event=15199 level=1050631 5933643 Dump under msqidn 5934741 Dump (kgmtncch) from CALL statement with OUT CHAR arguments 5944227 SQLloader direct path load into IOT can dump [kdblldrp] 5951591 Dump in kkecdn due to exponent overflow 5960268 Dump (kkoiodoi) when FIRST_K_ROWS considers bitmap index 5962344 Dump from Logminer due to stack corruption under krvtgct_GetColumnTranslation 5962680 Dump[kwqicgsubname1] on an AQ enqueue call 5984440 Dump [prsatb] from ALTER TABLE .. MODIFY SUBPARTITION 5988085 Dump [kkodsel] from STAR transformation with ANSI view 5989589 Dump (qctcopn) from create force view 5990716 Query using index join dumps [evaopn2] 6020789 Dump [vopplog] pushing join predicates 6035614 Instance crash / dump [kghunphy] with fix for bug 5922239 6036151 Dump (qctcopn) when LNNVL() gets used in a query 6052351 Dump running catupgrd.sql when creating/replacing streams$transformation_info 6053772 Dump [kpubsuuc] for SQL over HS using binds 6065183 A dump in AccessControlContext methods in the Oracle JVM 6070548 Dump (qertbGetPartitionNumber) / wrong results from bitmap access to IOT 6075582 OERI[kjbmpref:sh] / dump [kjmpbmsg] in LMS causing instance crash 6084108 Dump / CPU spin possible after an ORA-3115 6120084 Dump (eoistrnrep->strncpy) in Oracle JVM 6123145 Dump [ksxpunmap] in RAC 6123567 Dump [kkosbn] optimizing query on partitioned table 6124804 Dump [krvxbpc_processcommit] selecting from v$logmnr_contents 6139254 Dump (perdcs) with fix for bug 6061892 6145525 Dump selecting > 34 columns from HS (FDS) 6148212 Dump [qmuhshget_internal] can occur accessing LOBs 6168288 Dump instead of ORA-1863 6316993 Wrong results / dump (qernsRowP) from join back elimination of 1 row table 6651027 OERI:kgkprrpicknext1 / dumps from DBRM 6674196 OERI / buffer cache corruption using ASM, OCFS or any ksfd client like ODM Miscellaneous 5918964P HPUX: trace files may not dump all memory 6087207P False WARNING in alert log indicating lack of OS KERNEL I/O RESOURCES 4591936 Unnecessary "kccsga_update_ckpt ..." media recovery messages are logged at startup 4929809 sysresv not showing shared memory correctly when more segments 4936689 Crash dump (cdmp) generation cannot be limited dynamically 4999743 "cannot open symbol table" errors possible 5111399 Archiver error message should be tagged with 'ORA-' prefix 5201883 Unnecessary MMAN trace lines 5362226 PMON may not clean up dead processes 5390964 Connect time limit takes 60 seconds longer than defined (ORA-2399) 5454792 Require faster restart of non-fatal background processes 5555371 CURSORTRACE event cannot be turned off fully 5673171 Async LNS writes trace messages even when LOG_ARCHIVE_TRACE=0 Notable change of behaviour introduced in 10.2.0.4 5082178 Bind peeking may occur when it should not 5483301 Cardinality of 1 when predicate value non-existent in frequency histogram 6085625 Wrong child cursor may be executed which has mismatching bind information Notable change of behaviour introduced in 11.1.0.6 6085625 Wrong child cursor may be executed which has mismatching bind information 6322324 OS audit trail should include length of attribute values Undocumented Oracle Server 1641830 2107554 3328206 3519123 3639234 3750258 4047619 4338536 4376208 4396553 4409481 4428921 4432352 4447737 4457984 4478825 4494261 4520630 4526053 4544061 4557534 4637849 4661499 4671485 4697792 4698775 4713979 4716096 4733886 4861707 4881930 4905742 4919496 4921418 4940771 4944768 4963246 4967676 5003715 5005581 5007913 5013480 5015431 5035494 5044700 5051196 5071507 5079213 5084315 5084399 5084541 5087200 5087584 5087859 5108234 5112202 5123630 5146782 5152141 5164551 5166612 5168995 5172550 5173165 5173408 5178508 5179574 5183826 5185262 5186226 5192934 5206057 5220972 5229082 5234600 5236480 5244897 5317510 5318331 5321020 5325277 5335993 5344876 5345044 5345593 5352626 5355300 5357808 5358586 5360518 5362985 5371506 5381630 5382718 5382807 5382820 5387396 5387862 5389786 5394193 5394395 5394403 5402113 5402870 5404921 5412601 5413025 5414286 5417185 5417355 5434708 5444738 5447228 5447985 5461412 5463428 5463688 5463845 5464405 5467320 5470385 5478966 5488425 5493889 5495664 5496713 5497395 5497455 5499284 5499323 5501269 5505447 5507237 5509220 5518184 5526229 5527095 5527753 5529472 5534322 5534883 5545471 5546194 5546616 5548340 5548455 5549073 5549249 5550536 5556113 5559689 5563114 5563727 5564781 5564866 5568394 5570170 5570483 5570494 5572871 5577769 5579614 5580104 5582158 5584570 5585245 5587115 5599096 5605290 5605818 5607040 5607728 5613032 5613308 5614841 5617399 5618471 5618621 5631379 5631760 5633009 5633073 5636065 5636254 5637389 5638182 5638686 5640167 5645793 5646598 5647304 5647512 5654236 5658289 5660845 5661783 5664019 5664495 5668244 5669659 5674938 5675559 5682392 5683807 5684836 5685211 5685715 5687305 5687510 5692304 5692725 5696581 5698937 5699005 5699039 5701109 5703443 5703450 5703484 5703761 5704636 5709060 5710268 5714377 5714562 5714639 5715271 5717666 5719417 5720234 5720734 5723480 5726425 5726895 5727878 5728269 5728286 5730414 5731352 5732260 5732346 5732366 5737820 5739680 5742842 5746099 5746268 5746535 5748587 5748964 5752694 5752700 5752711 5752714 5752886 5752905 5755869 5756296 5762916 5764363 5766424 5768025 5769278 5840089 5840350 5840553 5841304 5843417 5845045 5845153 5849556 5850326 5853495 5854745 5855705 5855824 5855909 5856342 5857475 5857575 5862287 5862424 5865565 5865935 5867998 5868049 5868103 5870213 5875447 5875941 5877934 5877983 5878206 5880835 5884797 5885418 5885920 5887993 5888324 5890516 5892157 5893006 5895730 5896174 5898105 5900239 5900506 5900544 5900597 5902795 5906191 5906428 5909968 5911095 5911432 5913327 5913493 5918546 5918577 5918604 5918610 5919487 5921992 5922192 5924180 5924631 5925874 5928867 5933017 5933486 5937934 5939287 5939669 5941547 5941950 5942522 5943719 5943737 5946044 5949611 5959683 5963586 5967615 5968443 5971338 5972943 5976951 5977733 5978516 5979305 5979421 5980520 5981452 5984774 5986306 5986435 5988209 5996230 5996801 6000980 6001230 6002065 6002072 6002087 6003071 6003108 6003685 6004012 6006373 6006388 6006407 6009616 6011453 6014542 6017294 6018192 6020007 6022256 6025844 6025984 6028557 6029550 6030413 6034018 6034451 6034721 6036889 6037196 6039329 6039956 6040862 6041939 6042387 6043161 6045345 6046844 6051831 6053567 6053591 6053788 6054240 6054489 6055452 6056710 6058885 6059173 6062044 6064453 6066548 6067932 6071289 6071678 6072574 6073597 6079069 6082586 6083916 6084901 6086362 6087286 6087708 6111479 6111732 6114196 6117573 6118087 6119621 6120019 6121044 6125341 6125559 6126205 6126508 6127175 6130202 6131293 6132918 6137968 6137981 6141333 6142937 6146463 6162120 6162909 6168086 6168375 6169660 6180943 6181175 6184271 6194087 6199373 6203196 6208093 6213612 6217433 6239184 6239779 6257877 6269865 6272721 6272739 6272784 6272811 6272817 6272819 6272854 6272856 6273187 6273395 6273696 6273708 6273713 6273720 6273725 6273727 6273732 6273734 6273743 6273748 6273749 6273750 6273752 6273758 6273764 6273765 6273768 6273770 6273827 6275133 6275135 6277183 6282391 6311966 6316892 6318919 6320437 6330542 6331591 6336519 6339686 6340058 6343633 6346676 6349653 6356355 6361253 6361433 6361436 6361440 6361443 6361469 6361470 6361473 6361587 6361984 6363132 6368102 6378161 6379631 6396410 6404766 6407054 6407066 6407082 6408911 6414483 6417500 6430615 6431152 6432075 6439912 6442149 6442499 6442747 6444726 6450420 6450989 6452406 6467580 6468247 6487210 6491820 6492075 6492624 6494943 6495698 6503450 6508722 6509008 6510362 6511034 6513210 6513356 6519218 6522994 6524616 6526103 6528990 6529095 6531519 6594835 6594915 6595761 6597692 6599610 6600521 6600986 6602212 6602428 6603832 6604431 6604780 6605063 6605162 6605229 6605908 6606435 6608873 6610714 6610739 6610762 6613719 6614282 6615830 6616666 6619406 6621082 6624297 6625823 6625846 6634066 6634158 6634634 6634746 6638094 6639406 6642072 6644670 6649094 6652325 6658931 6659054 6660857 6664213 6668097 6668134 6670312 6672307 6672370 6674318 6676631 6677727 6680380 6681637 6684364 6684841 6685674 6686885 6689904 6697717 6698680 6700022 6701103 6702527 6709709 6709773 6712314 6712414 6713408 6714415 6718527 6718662 6720691 6724635 6724666 6725314 6727500 6727520 6728620 6731134 6737648 6739098 6741557 6743634 6744654 6748772 6749185 6749532 6749786 6750019 6758230 6770121 6775201 6776065 6777078 6780180 6785949 6786411 6790199 6797072 PL/SQL PL/SQL 709811 PLS-123 / dump compiling package with PLSQL_DEBUG = true 4381035 ORA-932 if not all select items in PLSQL dynamic select statement are defined 4435282 PLSQL cannot use database link with name longer than 30 chars 4507743 ORA-6502 is not raised for number precision overflow in PLSQL 4619731 PLSQL may see wrong (old) value for a package variable 4644108 Dump assigning BINARY FLOATs or DOUBLES to a BIND in PLSQL 4686467 Spin using UTL_TCP / UTL_HTTP 5015298 OERI[kpotcprc: uga depth exceeded] can occur after an ORA-1000 5029092 ORA-12713 not reported for RPCs with NLS_NCHAR_CONV_EXCP set 5066528 DBMS_TRACE enhancements 5123798 ORA-4067 from client side PLSQL 5131945 PLS-801 during PLSQL interop between 11g and 10.2 5168773 Poor performance of fetch with nested tables/ADTs in 10g 5183045 PLSQL dump under pevm_MOVN 5214109 Corruption / OERI:kopp2ucoll700 calling PLSQL using negative array out parameters 5249142 ORA-4062 from PLSQL RPC 5252427 Collections (arrays) passed from JDBC to PLSQL show up as NULL 5389854 Memory leak using bulk insert with SAVE EXCEPTIONS 5394728 Errors / wrong results running SQL in PLSQL from old front end (eg Forms) 5415410 ORA_DEBUG_JDWP may get corrupted 5436549 Dump [pevm_bcsrwc] after FORALL array operation 5483284 PLSQL 10g/11g interoperability problem with binary_float / binary_double literals / constants 5484847 Dump (koputilassert) from 8.0 RPC to >=9i server 5575771 UTL_HTTP cannot handle https connections without a content-length 5581731 Errors loading wrapped PLSQL in multibyte from client other than SQLPLUS 5589275 PLSQL BULK COLLECT INTO can spin 5597014 PLS-707[2603] occurs while compiling a package 5599607 FORMAT_ERROR_BACKTRACE returns wrong line number for exceptions inside loop 5613128 PLS-707 from ALTER TABLE DROP TYPE then ADD METHOD 5637147 Wrong Results from TRUNC of a timestamp in PL/SQL 5693291 PLSQL optimizer incorrectly optimizes common subexpressions 5859164 10g PLSQL compile time slower than 9.2 5878041 plsql_optimize_level=2 can significantly impact compile time of complex procedures 5890966 Intermittent ORA-6502 with package level associative array 5910731 Dump (pfsadt) using multiset in PLSQL 5911891 Wrong results with timestamp binds in PLSQL 5924384 ORA-21780 in PLSQL 5957181 ORA-4043 on SYS_PLSQL_% types if similar named synonyms / objects exist 5958121 Timezone problems when calling a pipelined table-function 5978646 Ctrl-C when executing PLSQL can dump [pfrdlunam] 5980005 ORA-6533 while indexing a collection inside FORALL 6034173 ORA-3106 error when fetching into a cursor from PLSQL 6061892 Memory Leak on 'PLS non-lib hp' by recursive PLSQL calls / ORA-4030 AND ORA-21780 6067804 ORA-910 not signaled when pipelined function tries to return > 4000 byte varchar2 6068126 Dump (pevm_instc2) using REF cursors in PLSQL 6075168 Memory leak if PLSQL callout using OBJECT arguments returns an error 6121452 Client PLSQL dump attempting an RPC in OCI mode without a database connection 6139946 Wrong results from TIMESTAMP with TIMEZONE arithmetic in PLSQL 6214869 Dynamically invoked PLSQL calls from AQ looses package globals Undocumented PL/SQL 4686355 5001170 5368764 5706508 5866120 5918614 5944772 6040276 6071378 6273273 6273275 6273278 6273280 6275158 6361423 6361425 6416327 6435593 Oracle Database Gateway for DRDA Oracle Database Gateway for DRDA 5606511 ORA-28500 calling a DB2 stored procedure with DECIMAL 5745055 Error in table/index statistics cache lookup in HS 5923091 Placeholder bug for TG4DRDA part of fix for bug 5877437 6007665 TG4DRDA dictionary update to ALL_TABLES SQL*Plus SQL*Plus 4768243 OSERROR not caught by SQLPLUS in 10g 4901089 SP2-310 unable to open file error when file name ending with "$" 5474008 SQLPLUS does not failover with RAC and DataGuard 5844617 SQLPLUS returns wrong exit status using 'whenever' clause 6334570 Need a target to rebuild SQLPLUS shared libraries Precompilers Precompilers 5214846 Procobol clients may insert NULLs using host-tables with indicators 5674966 ORA-1727 from ProCobol with PACKED DECIMAL Undocumented Precompilers 5551558 5589879 6272839 Oracle Net Services Oracle Net Services 4417761 Net listener cannot contact ONS daemon in different ORACLE_HOME 4570363 JavaNet throws exception with nested/multiple ADDRESS_LIST clauses 4570768 CMAN not able do connection over two hops - ORA-12564 5076238 Dump [nstotoqgetkey] after Net error 5128376 Aliases in non-default context not removed by NetCA 5236140 Memory leak in clients when using TAF 5351620 ORA-12559 from JDBC OCI driver 5518312 Small memory leak when niotns fails 5541589 Connect timeout with ADDRESS_LIST does not handle refuse correctly 5549203 Client spins when sqlnet.outbound_connect_timeout is set 5594035 Unable to change the listener password 5663043 Memory leak in nsbGet / dump possible under nsbrfr 5701515 Only first 5 LDAP server entries used (directory_servers) in ldap.ora 5713832 ORA-12637 using DESCRIPTION_LISTS with multithreaded client 5754150 ORA-12152 from non-blocking OCI 5837468 EMON hangs when client application suspended 5854698 Listener dumps / corrupted listener.ora after save_config Undocumented Oracle Net Services 4723343 6410510 6700564 Oracle interMedia Oracle interMedia 6445892I ORDSYS objects invalid in the SYS schema after upgrade 4765206 Processing JPEG file fails with IMG-703 5505981 IMG-703: unable to read image data using set.properties() on TIFFfiles 5748273 Failed Image process() corrupts original LOB 5770164 ORDX_HTTP_SOURCE leaks connections (ORA-29270) 5978773 processCopy fails with IMG-2 "unrecoverable error" 6042995 Extract of JPEG image from DICOM file fails with IMG-705 6255772 IMG-2 from ORDSYS.ORDIMAGE.process Undocumented Oracle interMedia 5174238 5637901 5692668 5717209 6161898 6450327 Oracle Text Oracle Text 2553707 CTX_DOC.HIGHLIGHT returns only first query term when NOT operator is used 4360454 Wrong results using Japanese V-GRAM Lexer 4439469 Analyze index (table) can block DML operations with Text indexes 4531863 Cursors are not closed when creating text index with multi_lexer and user_lexer 4562807 OERI:[kole_t2u] / dump using gist / theme against corrupt documents 4605900 DRG-51030 when using wildcard with chinese_lexer 4901547 Text markup does not work properly on special characters in XMLType columns 5221677 High CPU with many Text indexes 5223027 CTX_DOC.MARKUP does not work with Japanese lexer 5226126 Create text index fails with huge number of documents 5232076 Korean morph lexer stores lower case string in $I table 5274156 Dump (drexuAnalyzeQuery) from Text query 5326179 No error reported in multi_column_datastore if filter fails 5329098 Placeholder bug for Text Verity filter fixes 5336737 A dump can occur using Japanese stemming 5345988 HTML section does not index some section data 5350590 CTX_DOC.MARKUP fails with ORA-20000 if document contains illegal characters 5354012 Negative numbers not excluded with stopclass numbers when printjoins is set 5365424 Text indexing BFILES does not index all valid documents 5378039 Dump (drexudmcx) using sync (on commit) Text index with shared servers 5390154 SYNC_INDEX can be slow 5438110 DRG-11513 creating text index with multibyte file names 5451092 Wrong characters highlighted by ctx_doc.markup() 5456354 Text query on XML data can return wrong results due to XML attribute size limit 5470592 Text indexing a URL can dump 5533182 Create text index spins 5563839 CTX_DOC.markup() highlights wrong characters 5587976 Dump [drurnew] using Text 5596325 Text query gives wrong results or fails with ORA-1410 ORA-29903 5631223 Wrong results from progressive relaxation when table is partitioned 5687645 DRVODM data mining function may fail with DRG-50857 / ORA-955 5707554 DRG-11301 when creating text index with long user-lexer procedure name 5710143 ctx_doc.markup() highlights wrong characters 5714888 ORA-1002 when creating Text index with direct datastore 5738457 ORA-20000 from Text query with no further information 5738539 DRG-10502 from Sync with parallelism for another users index 5751742 JAPANESE_LEXER can spin 5859738 DRG-11308 when creating context index 5905735 Text query can dump (in drexrdstqx) 6068474 Dump (drlaload) calling CTX_QUERY.browse_words with a null 6073036 Dump[dred1cm] from Text query using progressive relaxation 6122785 Inconsistent results / errors from fuzzy parallel CONTAINS query Undocumented Oracle Text 5237224 5401928 5567066 5576706 5663785 5714713 5917938 6072096 6598793 Advanced Networking Option Advanced Networking Option 887753 Services do not register with ASO encryption turned on 3667025 Kerberos cross realm authentication fails using Microsoft Credential Cache (//osmsft) 3786828 ORA-12638 using kerberos on Windows 4518385 TNS-12637 / dump from simultaneous Kerberos connections 4764518 Internal code needed by OID 5031220 Incorrect parsing of KRB5CCNAME environment variable (Kerberos) 5031224 Default realm clause of client side krb5.conf is not compatible 5095984 Kerberos adapter does not support type 4 credential cache file created by kinit 5629724 Add support for mapping of > 30 character kerberos principal to DB schema Oracle Database Gateway for WebSphere MQ Oracle Database Gateway for WebSphere MQ 5713766 Setting MQPMO_NO_SYNCPOINT results in mqput/mqget error 2046 6415898 ORA-28511 / ORA-29400 from PG4MQ Oracle Internet Directory Oracle Internet Directory 5223331 Memory corruption from DBMS_LDAP_UTL.NORMALIZE_DN_WITH_CASE 5237812 Client hangs if the an OID DIRECTORY_SERVERS entry in ldap.ora is down 5386748 A non-privileged user can perfom config operations in oiddas 5497683 Cannot sync LDAP entries with UTF8 characters when using mapping operators 5586373 Login with special characters fails with NullPointErexception in ismemberofgroup 5632861 DIP_GEN_CREATECHG_EXCEPTION when source contains > 10 object classes 5705503 SearchDeltaSize ignored on DIP synchronization 5742856 Dump on login if NIS has LDAP configured 5943019 ldapsearch fails to connect to Active Directory server Oracle Database Configuration Assistant Oracle Database Configuration Assistant 5690286 DBCA does not show all available disks 5710808 DBCA errors if ORACLE_HOME contains a directory called "bin" 5875729 DBCA silent carries on and completes 'successfully' despite fatal errors 6132986 DBCA creates wrong OID entry during DB registration Oracle Database Gateway for Sybase Undocumented Oracle Database Gateway for Sybase 6182186 Oracle ODBC Driver Oracle ODBC Driver 5202103 Requery of data returns old data using ODBC 5376170 ODBC ORA-904 for SQL with column names containing spaces 5389003 ODBC driver does not round off double data 5706606 ODBC driver dump when fetching TIMESTAMP / INTERVAL types 5747525 ODBC has wrong sqresus.dll Undocumented Oracle ODBC Driver 5758953 5760923 5763138 5763172 5770374 5838037 5846726 5879622 5888808 5915427 5948621 6077885 JPublisher JPublisher 5206270 JPUB plsql_wrapper.sql uses undefined preprocessor directives 5847296 JPublishers errors processing package with name length of 29 characters Oracle Spatial Oracle Spatial 4582210 Local partitioned spatial index fails on tablespace transport 5097326 NLS_TERRITORY=german causes problems with numeric representation in Spatial 5117577 SDO_CS.transform() not supported with EPSG CRS (3005) 5197581 ORA-29532 from CREATE_FEATURE 5253336 shortestPathAStar() NDM Java API loops when no path can be found 5411907 REMOVE_DUPLICATE vertices adds more vertices to the end of the geometry 5497674 VALIDATE_GEOMETRY_WITH_CONTEXT reports false errors 5507634 SDO_RELATE returns wrong results 5512782 SDO_TOPO_MAP.add_point_geometry - edge should split, but does not 5554484 Unable to correct invalid geometry with rectify_geometry or migrate.to_current 5632711 Spatial partition code cannot create more than 2k partitions 5671929 Large memory allocation when using SDO_GEOM.RELATE 5675163 ORA-29532 from SDO_TOPO_MAP.ADD_EDGE attempting to add an edge ends 5694168 SDO_ANYINTERACT performs slowly on feature layers with lots of features 5738090 Offseting a single straight segment produces a spurious circular arc 5743792 LOAD_TOPO_MAP cannot be called multiple times in the same transaction 5750711 Dump [mdgoplun] querying Spatial data 5766563 Parallel create of Spatial index with SDO_NON_LEAF_TBL fails 5838363 Spatial Unit of length issue in wkt 5840592 SDO_LRS.OFFSET_GEOM_SEGMENT returns null values 5871002 SDO_TOPO_GEOMETRY constructor fails on versioned topology 5873149 Projection name problem in Spatial 5900199 ORA-29885 ORA-29400 attempting to create a Spatial index 5912272 Behaviour of SDO_NET.validate_network inconsistent with manual 5929643 Performance problem while deleting features in hierarchical topology model 5949568 Need distance stopping condition so SDO_NN/SDO_BATCH_SIZE do not scan entire table 5982684 Placeholder bug for network data model fixes 5983129 Partitioned local spatial index needs a way to set status to valid 6000704 Wrong result returned by sdo_sam.simplify_geometry() 6004768 Queries against ALL_SDO_GEOM_METADATA are slow 6011024 SDO_GEOM.RELATE with 'determine' mask returns unknown mask 6027858 Wrong results from SDO_RELATE 6038442 Wrong results from the SDO_GEOM.sdo_intersection() function 6055668 Wrong results from SDO_RELATE 6059034 ORA-13363 when using 2D query windows to view 3D data 6070096 Wrong results from SDO_RELATE 6070333 NETWORK.addnode(link,distanceratio,istemporary) creates incorrect link geometry 6087105 SDO_LRS.OFFSET_GEOM_SEGMENT returns Null for some geometries 6087331 SDO_TOPO_OBJECT_ARRAY size is too small 6114292 Intermittent OERI from Spatial queries 6119611 bandNumbers / layerNumbers of getRasterSubset over 99 fails (ORA-13410) 6193816 Errors using Spatial with index created with layer_gtype=POINT 6194209 ORA-4030 / excess memory use loading new geometry 6196135 Topology FACE$ has invalid MBR for faces with inner island faces 6272191 Wrong results from SDO_INSIDE on touch and disjoint 6315932 ORA-13249 using SDO_JOIN() with long table / schema names 6368037 Spatial READ_NETWORK can be slow 6485701 Decimal degree conversion factor not accurate in spatial 6602344 RELATE can be slow for very large (10k vertices) geometries Undocumented Oracle Spatial 4450253 5115167 5149238 5357619 5404430 5899894 5946382 5968582 5968833 5971691 5985754 6054474 6065691 6070136 6085696 6122040 6122642 Oracle Ultra Search Oracle Ultra Search 4474426 Schema version 10.2 is not compatible for Ultrasearch component 4743226 Fix for bug 3680460 incorrectly reintroduced bug 3588054 4994742 Content with meta redirect not working correctly during Portal crawling 5684293 RTF documents incorrectly displayed when opened Oracle Database Upgrade Assistant Oracle Database Upgrade Assistant 5115926 DBCA does not support XE to EE database cloning / migration 6399599 DBUA alters NLS_DATE_FORMAT in newly created spfile resulting in ORA-1830 6505158 DBUA hangs with patch 5115926 during 32-bit to 64-bit upgrade JDBC JDBC 3844473 getString on a CLOB does not work with ScrollableResultSet 4439777 JDBC SQLException binding user ADT to PLSQL 4485954 JDBC describe of CHAR semantics column gives wrong size 4523729 JDBC XAConnection / XAResource should have one-to-one mapping 4563894 Cache parameter of createTemporary API in oracle.sql.clob is ignored 4659157 WE8MSWIN1252 characters not converted properly by JDBC Thin 4711863 setBigDecimal corrupts number for negative values 4722328 Unread CallableStatement refcursor OUT parameter causes dump 4999817 getIndexInfo() slow (performs ANALYZE operations) 5069831 SQLException "internal error" using JDBC batching 5086162 "character set not supported" occurs in JDBC using user defined character set 5124016 Implicit connection cache getConnection() blocked during up event processing 5176155 JDBC unable to properly locate the scope of an ADT 5231687 OERI:kokeeiix selecting an updated ADT which has evolved in JDBC 5256848 Corrupt results changing fetch size in JDBC 5347395 JDBC batch update returns ORA-910 5347429 handleAbandonedConnection is called every "property-check-interval" seconds 5354004 ArrayOutOfBoundsException selecting > 200 columns in JDBC 5356342 updateCharacterStream() causes ORA-1401 and ORA-12899 5385803 JDBC KRPB can dump [lxgu2t] 5499691 Non-recoverable ORA-1460 exception on a select 5499751 JDBC clearParameters destroys hidden generated key parameter 5506478 Using a scrollable resultSet can lead to a hang 5597215 Memory leak in Jdbc XA 5614685 Suspended transaction cannot be ended from another connection in JDBC XA 5635254 Wrong values can be inserted when using JDBC batch inserts 5657975 FCF does not work for 10.2 JDBC to 10.1 database 5658207 SQLException "missing in or out parameter at index" with clearParameters 5658909 connection.rollback() does not clear outstanding batches 5660734 JDBC does not update evolved types properly 5691585 getProcedureColumns method returns wrong number of rows when running against 10g 5721063 Retries fail after XAER_RMERR during xa_commit from JDBC 5752856 ArrayOutOfBoundsException with NCHAR literal in JDBC 5867781 NullPointerException from StructMetadata of a STRUCT with an ARRAY in it 5875110 NullPointerException closing OracleConnectionCacheImpl 5892966 No columns from getColumns() when includeSynonyms=true 5892995 JDBC XA should not need execute permission on DBMS_SYSTEM 5910901 OERI[17278] / OERI[17282][1001] from JDBC using REF CURSORS 5998293 No XA_PROTO ending a transaction that has not been started in XA 5998987 Incorrect values inserted when first row bound as NULL in JDBC 6006898 JDBC OCI driver does not failover on receipt of OCI FAN 6275369 JDBC Thin driver does not close the socket on IOException 6731468 Stored Java does not work with a custom NLS characterset Undocumented JDBC 5327559 5475615 5500494 5742117 5927522 6045785 6658792 Oracle Security Service Oracle Security Service 4407719 SSL variables may not display properly 4895416 Unable to import ANCERT CA certificate into wallet manager 5131722 OWM will not import Verisign ECA certificate 5220448 Wallet manager limits the number of certificates that can be loaded (65k) 5396837 File handle leak from nzcrlGetCRLFromFile 5450462 OWM fails to import root CA from Microsoft certificate authority 5532208 Root certs not found in some cases 5851310 Unable to import trusted certificate into Wallet Manager 6124217 SSL NZ error 28757 / cannot use certificate due to Empty subject field Oracle Application Server 10g Oracle Application Server 10g 5749953PI+ Solaris: CRS crashes after applying 10.2.0.3 Patch Set 6083726 ONS does not receive NODEDOWN event Oracle XML Developers Kit Oracle XML Developers Kit 4292142 cdata-section-elements attribute ignored when using DBMS_XMLGEN.setxslt 4318081 extract query does not extract all nodes if the number of nodes exceeds 64k 4515075 C++ SAX parser can fail when trying to access attributes 4886354 XQuery on a collection leads to ORA-1000 "maximum open cursors exceeded" 4967236 OERI[17282] processing XML 5003275 Dump in XSL API for stylesheets with large number of patterns 5105337 XVM processor adds linefeed in every line 5255317 Memory leak XslxPathSample / DOMSample 5258225 NullPointerException validating a schema using Oracle schema checker 5353998 XQuery encounters LPX-601, ORA-19202, ORA-31011 5354090 Leading space in XQuery results 5362697 LSX-204 in schemaValidate() for element in complextype defined as 'all' 5416292 XPath query against a large XML file fails with ORA-31186 5487993 Dumps handling XSL 5511036 LSX-290 with schemaValidate() 5573534 Memory leak from XMLAccess() 5579674 Wrong time stamp values are populated when using transx utility in XDK 5587299 Fix for bug 4443086 is incorrect 5655847 Stylesheet not working as expected in 10g 5689971 Dump (under ltxvmmatchkey) using DBMS_XMLPROCESSOR 5694997 xmlxvmcompiledom needs a BASEURI parameter 5700527 XSL transformation fails for large XML documents 5707711 LPX-242 occurs when XML documents include the ampersand (&) for attribute 5934591 XDK "runtimeexception: byte 31 149" when FilePageManager is used 5946122 Incorrect conversion from DTD to XSD Net Manager - NetMgr Net Manager - NetMgr 4661200 Net manager adds alias to incorrect context Oracle OLAP Oracle OLAP 5121436 Dump possible using OLAP (under xstfContextClean -> kghfrh_internal) 5146569 Line graph shows axis and labels but no line in the graph 5326419 Surrogate build error when loading dimension in AWM 5336254 Error with measure folder in two different schemas 5347785 OLAP drill down throws exception 5355084 AWM randomly gets OOPS with vcread01 and rsdepage02 errors 5357405 Session dumps using DBMS_AQ.INTERP 5360145 Error during load of AWM 5360207 Cannot rerun measure query to refetch data only without affecting edges 5361171 Upgrade to 10.2 in AWM hangs 5367686 OLAP trigger not working on relation 5384375 ORA-3115 from OLAP DB link measure load 5389170 Cannot load large cube in OLAP 5392882 cube maintenance from AWM dumps (xspgInitPool) 5436458 single allocmap and single allocate command return NA 5507506 TOTAL function takes a long time in 10g 5555067 OLAP ACROSS command wrong in second iteration 5574866 OLAP cubes will not update the cube with incremental data 5577196 Use of trigger function causes session to dump (in xsILFUNC) 5578127 AW attach / initialization in BI beans and D4O slow 5581628 OWB generated AW shows incorrect average results 5582161 AW measure folders may not show in Discoverer for OLAP or the addin 5603293 OLAP DML sort can dump 5604376 OLAP session dumps on permitreset 5633245 OERI[kghalo2] using OLAP_TABLE rank 5642311 BIA-4085 error writing back data to Excel when using permit_write program 5652733 OERI:xscbtAddUb401 from OLAP 5653421 Error using even numbers for forcasts 'median smoothing window' in OLAP 5676244 Values of a variable dimensioned by compressed composite cannot be modified 5684721 Dump (in xsAGMClearCompiled) compiling aggmap in OLAP 5687603 AW is cached across database sessions 5700568 OERI[xscbtaddub401] from OLAP 5700725 Query of measure DIM with constant source returns wrong numbers in OLAP 5703138 Top/bottom by comprising percent pattern ignores comparison operator 5739350 OERI [XSOOPS][XsRS64UpdateIndex01] importing EIF files 5746153 OLAP a patch for 10.2.0.3 5762192 Dump from compile of aggmap 5888194 Export AWM project to XML with french accents ( utf-8 ) 5889531 Retrieval of schema list is slow in OLAP 5934559 OERI[XSOOPS][rsalpage01] updating structures in OLAP 5941689 MovingTotal function fails in OLAP 5945656 Decode function fails with NA as the third argument in OLAP 6076154 OLAP dump executing package body GENDEFINITIONMANAGERINTERFACE 6119941 ORA-36188 from OLAP AVERAGE operator 6164538 Cannot export AW to EIF 6489332 ORA-29532 java.lang.OutOfMemoryError in OLAP load of AW ----- Note: ----- ----- Note: ----- ----- Note: ----- =================================================================================== ===================================================================================