Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
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 re-create 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 the ORATAB file.
Action: Start Oracle with this SID on its designated PU (see the 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-09887 osnTXtt: Failed to create/open debug channel.
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 Oracle Customer Support.
ORA-09908 slkmnm: gethostname returned error code.
Cause: The system call GETHOSTNAME returned an error. This is most likely an internal error.
Action: Make sure GETHOSTNAME is successful in other contexts, and if so contact Oracle Customer 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 Customer 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 Customer Support.
ORA-09913 Malloc of dummy name failed.
Cause: Oracle was unable to allocate memory for the user name that is 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 Customer 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. This is an internal error.
Action: 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 Customer 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 Customer 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 Customer 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:
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:
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:
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. This is an internal error.
Action: Contact Oracle Customer 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 read only.
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. This is an internal error.
Action: Contact Oracle Customer Support.
ORA-09939 Restoration of signal handlers failed.
Cause: Oracle was unable to restore the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Customer 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 was 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 Customer 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 Customer 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 Customer 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 Oracle Customer Support.
ORA-09953 scggc: unexpected return of a lock convert
Cause: The Distributed Lock Manager returned an unexpected value.
Action: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Customer Support.
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 messages and refer to the Distributed Lock Manager documentation or contact Oracle Customer Support.
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 the Distributed Lock Manager documentation or contact Oracle Customer Support.
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 Oracle Customer Support.
ORA-09957 Unable to send termination request to IMON
Cause: The attempt to send a termination signal to IMON failed. This is an internal error.
Action: Contact Oracle Customer 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. This is an internal error.
Action: Contact Oracle Customer 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. This is an internal error.
Action: Contact Oracle Customer 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. This is an internal error.
Action: Contact Oracle Customer Support.
ORA-09961 Unable to restore termination signal handler
Cause: Oracle failed to set the handler for the termination signal to its previous value. This is an internal error.
Action: Contact Oracle Customer Support.
ORA-09962 lk_group_create error in scggrc
ORA-09963 lk_group_attach error in scggra
ORA-09964 lk_group_detach error in scggrd
ORA-09966 scumnt: translation error while expanding ?/dbs/lk
Cause: Failure of SLTLN in SCUMNT.
Action: Check additional returned error for more information.
ORA-09967 scumnt: unable to create or open file
Cause: Open system call returned an error.
Action: Check errno.
ORA-09968 scumnt: unable to lock file
Cause: Lock file operating system call returned an error.
Action: Check errno.
ORA-09969 scurls: unable to close lock file
Cause: Close system call returned an error.
Action: Check errno.
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 to 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 the number of bytes read from the 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 the instance and mount the 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-12000 a snapshot log already exists on table 'string'
Cause: An attempt was made to create a snapshot log on a table that already has a snapshot log. Each master table can have only one snapshot log.
Action: All snapshots on a table can use the same snapshot log for that table. To make changes to the existing log, use the ALTER SNAPSHOT LOG command or drop the snapshot log and create it again.
ORA-12001 cannot create log: table 'string' already has a trigger
Cause: Snapshot logs are filled by a trigger on the master table. That trigger cannot be created.
Action: To create a snapshot log, drop the current trigger on the master.
ORA-12002 there is no snapshot log on table "string"."string"
Cause: There is no snapshot log on the master table.
Action: Create the log.
ORA-12003 snapshot "string"."string" does not exist
Cause: The snapshot with the given owner and name does not exist.
Action: Verify inputs or create snapshot.
ORA-12004 REFRESH FAST cannot be used for snapshot "string"."string"
Cause: The snapshot log does not exist or cannot be used.
Action: Use just REFRESH, which will reinstantiate the entire table. If a snapshot log exists and the form of the snapshot allows the use of a snapshot log, REFRESH FAST will be available starting the next time the snapshot is refreshed.
ORA-12005 may not schedule automatic refresh for times in the past
Cause: An attempt was made to schedule an automated snapshot refresh for a time in the past.
Action: Choose a time in the future instead.
ORA-12006 a snapshot with the same user.name already exists
Cause: An attempt was made to create a snapshot with the name of an existing snapshot.
Action: Create the snapshot using a different name or drop the existing snapshot.
ORA-12007 snapshot reuse parameters are inconsistent
Cause: The CREATE SNAPSHOT .. or CREATE SNAPSHOT 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 snapshot refresh path
Cause: Table SNAP$_snapshot_name reads rows from the view MVIEW$_snapshot_name, 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 master_owner.MLOG$_master is also referenced.
Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_snapshot_name, MVIEW$_snapshot_name, mowner.master@dblink, mowner.MLOG$_master@dblink still exist.
ORA-12009 snapshots may not contain long columns
Cause: An attempt was made to create a snapshot with a long column.
Action: Do not attempt to create snapshot logs with long columns.
ORA-12010 cannot create snapshot log on table owned by SYS
Cause: CREATE SNAPSHOT LOG attempts to create a trigger on the table, but triggers cannot be created on SYS tables.
Action: Cannot create snapshot logs on SYS tables.
ORA-12011 execution of string jobs failed
Cause: Some kind of error was caught in DBMS_IJOB.RUN. One or more jobs which were due to be run produced errors which they could not handle.
Action: Look at the alert log for details on which jobs failed and why.
ORA-12012 error on auto execute of job string
Cause: Some kind of error was caught while doing an automatic execute of a job.
Action: Look at the accompanying errors for details on why the execute failed.
ORA-12013 updatable snapshots must be simple enough to do fast refresh
Cause: The updatable snapshot query has a join, subquery, union, connect by, order by, or group by.
Action: Make the snapshot simpler. If a join is really needed, make multiple simple snapshots then put a view on top of them.
ORA-12014 table 'string' does not contain a primary key constraint
Cause: The CREATE SNAPSHOT LOG command was issued with the WITH PRIMARY KEY option and the master table does not contain a primary key constraint or the constraint is 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 snapshot 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 snapshot.
ORA-12016 snapshot does not include all primary key columns
Cause: The query that instantiates the snapshot does 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 snapshot query or create a ROWID snapshot.
ORA-12017 cannot alter primary key snapshot 'string' to a rowid snapshot
Cause: Conversion of a primary key snapshot to a ROWID snapshot is not supported.
Action: Create a new snapshot or drop and re-create the snapshot.
ORA-12018 following error encountered during code generation for "string"."string"
Cause: The refresh operations for the indicated snapshot could not be regenerated due to errors. See following error text.
Action: Correct the indicated problem and repeat the operation.
ORA-12019 master table is a synonym to a remote object
Cause: Snapshot of remote synonyms or snapshot logs on remote synonym are not supported.
Action: Do not create the snapshot or snapshot log on a remote synonym.
ORA-12020 snapshot string is not registered
Cause: Attempt to unregister a snapshot that is not registered.
Action: No action is required.
ORA-12021 snapshot "string"."string" is corrupt
Cause: The snapshot indicated is no longer valid.
Action: Contact Oracle Customer Support.
ORA-12022 snapshot log on "string"."string" already has rowid
Cause: Snapshot log on the indicated table already has ROWID information.
Action: No action is required.
ORA-12023 missing index on snapshot "string"."string"
Cause: The specified ROWID snapshot does not have the required index on the ROWID column of its underlying table.
Action: The snapshot is corrupted. Drop and re-create the snapshot.
ORA-12024 snapshot log on "string"."string" does not have primary key columns
Cause: Snapshot log on the indicated table does not have primary key information.
Action: Add primary keys to snapshot log using the alter snapshot command.
ORA-12025 snapshot log on "string"."string" already has primary keys
Cause: Snapshot log on the indicated table already has primary key columns.
Action: No action is required.
ORA-12026 invalid filter column detected
Cause: One or more of the specified filter columns does not exist or is a primary key column.
Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns are not included in the list of filter columns.
ORA-12027 dulicate filter column
Cause: One or more of the specified filter columns is already begin recorded in the snapshot log.
Action: Describe the snapshot log table and reissue the SQL command with specifying the filter columns that are already begin recorded in the snapshot log.
ORA-12028 snapshot type is not supported by master site string
Cause: Pre-Oracle8 master sites are not able to support primary key or subquery snapshots that are able to perform a fast refresh.
Action: Create a ROWID snapshot or use a master table from an Oracle8 site.
ORA-12029 LOB columns may not be used as filter columns
Cause: LOB columns may not be used as filter columns.
Action: Remove LOB columns from the filter columns list and retry command.
ORA-12030 cannot create a fast refresh snapshot
Cause: The snapshot log does not exist or does not log the information needed by the snapshot to perform a fast refresh.
Action: Ensure that the snapshot log exists and logs the necessary information. For ROWID snapshots, the master table's ROWID must be logged. For primary key, snapshots the master table's primary key columns must be logged. For subquery snapshots filter, primary key, and ROWID values must all be logged.
ORA-12031 cannot use primary key columns from snapshot log on "string"."string"
Cause: The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh.
ORA-12032 cannot use rowid column from snapshot log on "string"."string"
Cause: The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh.
ORA-12033 cannot use filter columns from snapshot log on "string"."string"
Cause: The snapshot log either does not have primary columns logged, or the timestamp associated with the primary key columns is more recent than the last refresh time.
Action: A complete refresh is required before the next fast refresh.
ORA-12034 snapshot log on "string"."string" younger than last refresh
Cause: The snapshot log is younger than the last refresh.
Action: Perform a complete refresh of the snapshot before attempting another fast refresh.
ORA-12035 could not use snapshot log on "string"."string"
Cause: The snapshot log does not exist or cannot be used.
Action: Use just REFRESH, which will reinstantiate the entire table. If a snapshot log exists and the form of the snapshot allows the use of a snapshot log, REFRESH FAST will be available starting.
ORA-12036 updatable snapshot log is not empty, refresh snapshot
Cause: The updatable snapshot log must be empty before an updatable ROWID snapshot can be altered to a primary key snapshot.
Action: Ensure that updatable snapshot log is empty by refreshing the snapshot before converting the updatable ROWID snapshot to a primary key snapshot.
ORA-12037 unknown export format
Cause: An attempt was made to import a snapshot exported by an unknown export version (for example, from a newer release than the importing site)
Action: Re-export the file using a version of export known by the importing site.
ORA-12038 string literal has unexpected length
Cause: Corrupt or invalid information was detected during import of a snapshot.
Action: Ensure that the export log file has not been corrupted and that no errors were raised during export. Contact Oracle Customer Support if the problem persists.
ORA-12039 unable to use local rollback segment "string"
Cause: A local rollback segment was specified in the CREATE SNAPSHOT command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the snapshot and the local rollback segment cannot 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: The master site of the current snapshot does not allow users to specify a rollback segment to be used for snapshot 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 snapshot log that records the ROWIDs of an index-organized table cannot be created.
Action: Do not include the WITH ROWID option when using the CREATE SNAPSHOT command and do not include the ADD ROWID option when using the ALTER SNAPSHOT command if the master table is index-organized.
ORA-12042 cannot alter job_queue_processes in single process mode
Cause: There is no concept of detached processes in single process mode. Therefore altering the value of JOB_QUEUE_PROCESSES parameter is not allowed.
Action: Do not attempt to set JOB_QUEUE_PROCESSES in single process mode.
ORA-12043 invalid CREATE SNAPSHOT option
Cause: An invalid option was used in a CREATE SNAPSHOT statement.
Action: Specify only legal options.
ORA-12044 invalid CREATE SNAPSHOT LOG option
Cause: An invalid option was used in a CREATE SNAPSHOT LOG statement.
Action: Specify only legal options.
ORA-12045 invalid ALTER SNAPSHOT LOG option
Cause: An invalid option was used in an ALTER SNAPSHOT LOG statement.
Action: Specify only legal options.
ORA-12051 ON COMMIT attribute is incompatible with other options
Cause: The ON COMMIT refresh attribute is not allowed with other refresh options such as automatic periodic refresh.
Action: Specify only legal options.
ORA-12052 cannot fast refresh materialized view ('string'.'string')"
Cause: This materialized view is not always fast refreshable. Either ROWIDs of certain tables are missing in the definition or the inner table of an outer join does not have UNIQUE constraints on join columns.
Action: Issue a complete refresh. Refer to the documentation on materialized views.
ORA-12054 cannot set the ON COMMIT refresh attribute for the materialized view
Cause: The materialized view does not satisfy conditions for refresh at commit time.
Action: Specify only legal options.
ORA-12056 invalid REFRESH method
Cause: The NEVER REFRESH option may not be used under the following conditions:
Action: For updatable snapshots, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only snapshots, reissue the SQL command using ON DEMAND.
ORA-12057 snapshot "string"."string" is INVALID and must complete refresh
Cause: The status of the snapshot is INVALID and the snapshot may not be fast refreshed.
Action: Perform a complete refresh of the snapshot. Check the value of the STATUS column in DBA_SNAPSHOTS, ALL_SNAPSHOTS, or USER_SNAPSHOTS to verify that the snapshot is VALID after the complete refresh.
ORA-12058 snapshot cannot use prebuilt table
Cause: The snapshot cannot use the prebuilt table.
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 does 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 of a column in the prebuilt table does not match the snapshot definition query.
Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the snapshot definition query.
ORA-12061 invalid ALTER SNAPSHOT option
Cause: An invalid option was used in an ALTER SNAPSHOT statement.
Action: Specify only legal 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 are 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 is 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 does 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 SNAPSHOT command
Cause: The Replication API does not support the following options and types of snapshot:
Action: Create a PRIMARY KEY snapshot 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 does not contain any snapshots.
Action: Modify the template to include at least one snapshot.
ORA-12068 updatable snapshot log for snapshot "string"."string" does not exist
Cause: The updatable snapshot is missing the updatable snapshot log that is required to track updates made to the snapshot.
Action: Create the updatable snapshot log.
ORA-12069 invalid object for offline instantiation
Cause: Only snapshots can be offline instantiated. The object being offline instantiated is not a valid snapshot.
Action: Remove the object from the template or replace the object with a valid snapshot.
ORA-12070 cannot offline instantiate snapshot "string"."string"
Cause: Offline instantiation does not support snapshots using the following options:
Action: Remove the invalid options.
ORA-12071 definition query of "string"."string" is invalid for offline instantiation
Cause: Offline instantiation requires snapshot definition queries to observe the following constraints:
Action: Modify the snapshot definition query.
ORA-12072 updatable materialized view log data for 'string'.'string' cannot be created
Cause: The updatable materialized view is missing the updatable materialized view log that is required to track updates made to the materialized view.
Action: Create the 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 returns an unknown value.
Action: Re-issue the refresh request.
ORA-12079 snapshot options require COMPATIBLE parameter to be string or greater
Cause: The following snapshot options require 8.1 or higher compatibility setting:
Action: Shut down and restart with an appropriate compatibility setting.
ORA-12081, 00000 update operation not allowed on table string.string
Action: An attempt was made to update a read-only materialized view. Only Oracle is allowed to update a read-only materialized view.
Action: No action required.
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.
