ORA-16808: primary database is not open
Cause: A prior attempt to open the primary database was disallowed because the fast-start failover status could not be evaluated. The fast-start failover status has since been evaluated and the database can now be opened.
Action: Open the database by issuing the SQL*Plus ALTER DATABASE OPEN command.
ORA-16809: multiple warnings detected for the database
Cause: The broker detected multiple warnings for the database.
Action: Check the StatusReport monitorable property of the specifed database to get a detailed status report.
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 specified database to get a detailed status report.
ORA-16811: apply instance not recorded by the Data Guard broker
Cause: The broker did not register 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 were not running on the instance the Data Guard broker expected 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 were not running on the instance the Data Guard broker expected 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 an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:
- The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.
- The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.
- The AlternateLocation property did 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.
- The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.
- The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused 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 an incorrect redo transport setting for a standby database AlternateLocation property. The incorrect setting could be one of the following:
- The AlternateLocation property was empty, but the redo transport to the standby database had an ALTERNATE setting.
- The AlternateLocation property was not empty and the redo transport to the standby database had no ALTERNATE setting.
- The AlternateLocation property did 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.
- The LOG_ARCHIVE_DEST_STATE_n parameter corresponding to the alternate location was not set to ALTERNATE.
- The flash recovery area was being used by the standby database for archived logs, but the redo transport to the standby database still had an ALTERNATE setting for the AlternateLocation property. Data Guard broker logs provide more details on which of the above cases caused the error.
Action: Reenable the primary database to clear the error.
ORA-16816: incorrect database role
Cause: The Data Guard broker detected that the specified database had a database role that was different from the database role recorded 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.
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 data to it. When the standby database has received all of the redo data from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then fail over 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 the primary database. This effectively restores the ability to automatically perform 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 host where the observer was running was not available.
- The network connection between the observer and this database was not available.
- The 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 host. Finally, use the DGMGRL START OBSERVER command to start the observer on the other host.
ORA-16821: logical standby database dictionary not yet loaded
Cause: The logical standby database had not loaded the dictionary. This status was detected by the broker health check mechanism. Alternatively, this status may be returned when attempting to switch or fail over to a logical standby database that had not yet loaded its dictionary.
Action: Start SQL Apply on the logical standby database, if it is not already running, 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 standby database failover operation, had not fully completed the failover operation. An attempt to reinstate a disabled standby database could not be completed until failover completed on the new primary database.
Action: Wait until the failover operation has completed on the new primary database. 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: multiple warnings, including fast-start failover-related warnings, detected for the database
Cause: The broker detected multiple warnings for the database. At least one of these warnings may have prevented fast-start failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
ORA-16825: multiple errors or warnings, including fast-start failover-related errors or warnings, detected for the database
Cause: The broker detected multiple errors or warnings for the database. At least one of these errors or warnings may have prevented 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:
- The apply service was started without specifying the real-time apply option or without the NODELAY option when the DelayMins property was set to zero.
- The apply service was started with the real-time apply option or with the NODELAY option when the DelayMins property was set to a value 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-16827: Flashback Database is disabled
Cause: The broker detected that the Flashback Database feature was disabled. With Flashback Database disabled, the broker would not be able to:
- reinstate a database that required reinstatement.
- convert a physical standby database to a snapshot standby database.
- convert a snapshot standby database to a physical standby database. Flashback Database may been disabled manually with the ALTER DATABASE FLASHBACK DATABASE OFF command or automatically by the database in the event of an error.
Action: Check the database alert log to determine whether Flashback Database was disabled due to errors and then correct the problem. If Flashback Database had been manually disabled, reenable Flashback Database with the ALTER DATABASE FLASHBACK DATABASE ON command. If, after enabling Flashback Database, the database still cannot be reinstated or converted, you must re-create the database from a copy of the primary database.
ORA-16828: invalid value specified for REDO_TRANSPORT_USER initialization parameter
Cause: An invalid value was specified for the REDO_TRANSPORT_USER initialization parameter. The length of the user name exceeded 30 characters.
Action: Check the documentation and specify a new value for the REDO_TRANSPORT_USER initialization parameter.
ORA-16829: fast-start failover configuration is lagging
Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.
Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.
ORA-16830: primary isolated from fast-start failover partners longer than FastStartFailoverThreshold seconds: shutting down
Cause: The primary database was isolated from both the observer and target standby database for longer than the seconds specified by the FastStartFailoverThreshold property. A fast-start failover probably occurred. If the FastStartFailoverPmyShutdown configuration property was set to TRUE, the broker will shut down the primary database in this situation.
Action: Ensure one instance of this database is running and the database is mounted on that instance so that the broker may reinstate the old primary database.
ORA-16831: operation disallowed on this standby database type
Cause: The Data Guard broker operation was disallowed on the standby database type.
Action: Check the documentation for the correct standby database type and reissue the Data Guard broker command to another standby database that is of the correct standby database type.
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-16959: Statement type has been disabled for SQL Analyze
Cause: The system attempted to analyze a type of statement that was disabled by the current feature.
Action: Try a different feature capable of analyzing this statement type.
ORA-16960: SQL Analyze could not reproduce the desired plan.
Cause: SQL Analyze failed to reproduce a particular plan using an outline.
Action: Check the outline data.
ORA-16961: SQL statement with SQL patch is ignored
Cause: SQL statements with SQL patches are not supported by SQL tuning advisor.
Action: Check the SQL patch information. Rerun SQL repair advisor on that SQL statement for a potential better SQL patch.
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-17512: Block Verification Failed
Cause: Block Verification after a read operation on a database file failed since the block is media corrupt.
Action: check additional error messages in the trace file and call Oracle Support Services
ORA-17610: file 'string' does not exist and no size specified
Cause: An attempt to create 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-17627: string
Cause: An error returned by OCI while sending/receiving message from remote instance
Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance
ORA-17628: Oracle error string returned by remote Oracle server
Cause: Oracle server on the remote instance has returned an error.
Action: Look at remote instance alert log/trace file for more information and take appropriate action or contact Oracle Support Services for further assistance
ORA-17629: Cannot connect to the remote database server
Cause: Connecting to the remote server specified by database connect string for netowrk file transfer failed.
Action: Check additional error messages
ORA-17630: Mismatch in the remote file protocol version client string server string
Cause: Cannot communicate with the remote database server as there is a mismatch in the Oracle file protocol version.
Action: Check additional error messages
ORA-17631: dbname 'string' specified by remote server does not match the instance name 'string'
Cause: The dbname specified by the remote server is not intended for this instance.
Action: Check the dbname specified in the command of the remote instance and look for further error messages.
ORA-17632: file 'string' is a formatted ASM disk
Cause: An attempt to create a datafile on a device that was formatted for ASM disk failed.
Action: Check that the device specified is not an ASM disk. If you would like to use the disk for datafiles, please clear the disk before you retry the operation.
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.
No hay comentarios:
Publicar un comentario