Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
This section lists messages generated by replicatiuon.
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.
Cause: An external RepAPI operation failed.
Action: Consult detail error message.
Cause: An internal service failed and signalled an error.
Action: Consult the detailed error message which accompanies this one.
Cause: An unexpected internal RepAPI failure was detected.
Action: Contact Oracle Worldwide Support.
Cause: The caller requested a RepAPI operation that was not implemented.
Action: Do not issue this call.
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
Cause: The master connection handle was or became invalid.
Action: Verify that the master connection is valid. Then retry the operation.
Cause: The client connection handle was or became invalid.
Action: Verify that the client connection is valid.
Cause: An internal snapshot control structure could not be obtained.
Action: Check that the owner and users provided are correct.
Cause: The specified snapshot name was too long.
Action: Shorten the snapshot name.
Cause: A RepAPI operation was attempted against a non-existent or invalid master table.
Action: Verify that the master table object exists.
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.
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 administrator or DBA.
Cause: The specified object was expected but not found.
Action: Verify that the specified object exists and is valid.
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.
Cause: RepAPI was unable to confirm that the last pushed transaction was successfully committed 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.
Cause: The specified snapshot catalog control record was not found.
Action: Verify that the local snapshot catalog is valid and that the local snapshot is properly defined.
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 repush 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 snapshot logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.
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.
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.
Cause: An error occurred during the initialization of a PL/SQL RPC.
Action: Verify that the procedure to be invoked exists and is valid at the master site and is executable by the RepAPI user.
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.
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.
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.
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.
Cause: The client SQL snapshot definition query could not be properly parsed by the master Oracle site.
Action: Check that snapshot DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions.
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 states and notify Oracle Worldwide Support.
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 Worldwide Support.
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 Worldwide Support.
Cause: The snapshot control list could not be constructed. This is generally the result of an error while accessing the local snapshot catalog.
Action: Verify that the named snapshot(s) are properly defined and valid. Then retry the operation
Action: Event used to simulate site failure for parallel push testing.
Cause: A parallel push executed with the event ORA-26531 enabled raises this error to simulation failure of network or destination site.
Action: Do not enable the event for normal operation.
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 (ORA-26518).
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.
Cause: There are outstanding conflicts logged in the DEFERROR table at the snapshot's master site.
Action: Do one of the following:
Cause: An attempt was made to rename a replicated table, an updatable snapshot table, or the master table of a snapshot for which a snapshot log has been created.
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 snapshot.
Cause: The passed type of the given argument number does not match the type of the argument in the stored arguments.
Action: Invoke the correct type procedure (that is, GET_XXX_ARG).
Cause: An attempt was made to invoke the <type>_ARG procedure before starting a deferred call.
Action: Invoke the needed procedures in the correct order.
Cause: Failed to open connection using given DBLINK.
Action: Make sure that the DBLINK is valid and remote m/c is up.
Cause: sbtinit returned an error, additional information indicates error.
Action: Verify that vendor's storage subsystem product is operating correctly.
Cause: The specified device type is supported on this platform.
Action: Verify V$BACKUP_DEVICE for supported device types.
Cause: This is an internal error. Additional information indicates which function encountered error.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. A file is being created/retrieved on a device allocated with NOIO option. Additional information indicates which function encountered error.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. Blocksize specified is incorrect for the device on which file is being created. Additional information indicates blocksize specified, and the function that encountered the error.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an 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: Look for trace file, and contact Oracle Support.
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.
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.
Cause: This is an internal error. Additional information indicates which function encountered error
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error.
Action: Look for trace file, and contact Oracle Support.
Cause: sbtwrite returned error. Additional information indicates error returned from sbtwrite.
Action: Verify that vendor's storage subsystem product is operating correctly.
Cause: This is an internal error.
Action: Look for trace file, and contact Oracle Support.
Cause: sbtread returned error. Additional information indicates error returned from sbtread.
Action: Verify that vendor's storage subsystem product is operating correctly.
Cause: This is an internal error.
Action: Look for trace file, and contact Oracle Support.
Cause: Failure of sltln in skgfqpini.
Action: Examine additional return error for more information.
Cause: sbtclose returned error. Additional information indicates error returned from sbtclose.
Action: Verify that vendor's storage subsystem product is operating correctly.
Cause: Additional information indicates error returned from sbtinfo.
Action: Verify that vendor's storage subsystem product is operating correctly.
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 at least 64 (the limit specified for sbtinfo). Additional information indicates the media handle string length returned by sbtinfo, and the limit (SSTMXQMH).
Cause: User specified a blocking factor that is not a multiple of SSTKBLCK.
Action: Additional information indicates the blocking factor provided by user and the value of SSTKBLCK. Specify a value that is a multiple of SSTKBLCK.
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.
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 find what device types and names (if any) are available.
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.
Cause: This is an internal error.
Action: Look for trace file, and contact Oracle Support.
Cause: getrlimit system call returned an error.
Cause: ulimit system call returned an error.
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 system.
Cause: Logical block size for oracle files must be a multiple of the physical block size, and must be less than the maximum.
Action: Block size specified is returned as additional information. Verify init.ora parameters. Additional information also indicates which function encountered the error.
Cause: Additional information indicates sltln/slnrm error, and also indicates which function encountered the error.
Action: Examine additional information.
Cause: Stat system call returned an error. Additional information indicates which function encountered the error.
Cause: Trying to create a database file, but file by that name already exists.
Action: Verify that name is correct. Specify reuse if necessary.
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.
Cause: Create system call returned an error. Failure to create file.
Action: Verify filename and permissions.
Cause: Open system call returned an error. Additional information indicates which function encountered the error.
Cause: An attempt was made to seek and write the last block in file. Possibly, there is a shortage of space on device.
Cause: Seek system call failed. Additional information indicates which function encountered the error.
Cause: Write system call failed. Additional information indicates which function encountered the error.
Cause: Close system call failed. Additional information indicates which function encountered the error.
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.
Cause: Read system call failed. Additional information indicates which function encountered the error.
Cause: Possibly trying to use a non-database file as a database file.
Action: Verify that file is a database file.
Cause: An attempt was made to seek to and read the last block in file. Additional information indicates which function encountered error.
Cause: This is an internal error. Additional information indicates which function encountered error.
Action: Look for trace file, and contact Oracle Support.
Cause: This is just a simulated error (not a real one). Additional information indicates which function encountered the error.
Cause: fsync system call returned error. Additional information indicates which function encountered the error.
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.
Cause: Unlink system call returned error.
Cause: This is an internal error. Query is being asked about async vector I/O when the file does not support async I/O.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. Invalid query is being asked.
Action: Look for trace file, and contact Oracle Support.
Cause: ftruncate system call returned error.
Cause: fcntl system call returned error.
Cause: aiowait function returned error.
Cause: This is an internal error. There should have been some async I/Os in the system, but a blocking aiowait indicates that there are no more I/Os.
Action: Look for trace file, and contact Oracle Support.
Cause: The number of bytes read/written as returned by aiowait does not match the original number. Additional information indicates both these numbers.
Cause: This is an internal error. Asked to perform async I/O when IOV indicates that it cannot be performed on the file.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. Asked to perform async vector I/O when it cannot be performed on the file.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. Number of buffers in vector I/O exceeds maximum allowed by the OSD. Additional information indicates both these numbers.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. Buffer size is either 0, 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: Look for trace file, and contact Oracle Support.
Cause: This is an internal error. Buffer is not aligned to SSIOALIGN boundary. Additional information indicates where in function the error was encountered and the buffer pointer.
Action: Look for trace file, and contact Oracle Support.
Cause: This is an 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: Look for trace file, and contact Oracle Support.
Cause: aioread/aiowrite system call returned error. Additional information indicates starting block number of I/O.
Cause: lseek system call returned error. Additional information indicates block number in file to which seek was attempted.
Cause: Read/write/readv/writev system call returned error. Additional information indicates starting block number of I/O.
Cause: This is an 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: Look for trace file, and contact Oracle Support.
Cause: getrlimit system call returned error.
Cause: This is an internal error.
Action: Look for trace file, and contact Oracle Support.
Cause: setrlimit system call returned error.
Cause: This is an internal error. The number of files opened through skgfofi has reached the limit.
Action: Look for trace file, and contact Oracle Support.
Cause: Process operation attempted using invalid process ID.
Action: Contact Oracle Support.
Action: Examine errno, and if possible increase the number of processes.
Action: Examine errno, and contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Cause: Internal error, requested conversion too large for type.
Action: Contact Oracle Support.
Action: Examine errno, contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Cause: OS system called failed.
Action: Examine errno, and contact Oracle Support.
Cause: This is an internal error. Multiple post/wait creates attempted simultaneously.
Action: Examine errno, and contact Oracle Support.
Action: Examine errno, and contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Action: Check errno and contact Oracle Worldwide Support.
Cause: Client tried to allocate a zero length message.
Action: Refer to kgxp.h for information on the usage of kgxpvalo().
Cause: Client tried to allocate a zero length message.
Action: Refer to kgxp.h for information on the usage of kgxpvalo().
Cause: Client passed in a NULL pointer for deallocation.
Action: Refer to kgxp.h for information on the usage of kgxpvfre().
Cause: The specified port is invalid.
Cause: The global name service used by KGXP is not supported.
Action: Either use a different name service, of abort the current process/thread.
Cause: The connection identifier passed in is invalid.
Action: Check the connection identifier, or abort the process/thread.
Cause: The message that was sent is not aligned on the required boundaries.
Action: Use the KGXPALSZ() macro to get the alignment size of messages, and align all messages on this boundary.
Cause: An attempt was made to send a vectored message that exceeds the maximum vector size.
Action: Use a smaller vector size.
Cause: The message to multi-cast was not aligned on the proper boundary.
Action: Align the message appropriately.
Cause: The message that was posted for receive is not aligned on the required boundary.
Action: Use the KGXPALSZ() macro to get the alignment size of messages, and align all messages on this boundary.
Cause: Could not add an accept handle to the free pool.
Cause: The free pool of accept handles is empty.
Action: Add accept handles to the free pool.
Cause: The maximum communication channels that were specified are already in use for this process/thread.
Action: Destroy connections which are not needed.
Cause: Either the remote address was not valid, or the process was faulty.
Action: Destroy all connections, and try to re-establish them.
Cause: The OSD would not allow KGXP to queue up the storage necessary to accept new incoming connections.
Action: Check the parameters, if they are OK, then abort the process.
Cause: The OSD could not cancel an outstanding request immediately.
Action: Shutdown all connections and abort the process.
Cause: The platform does not support memory communication.
Action: Use the default send/receive.
Cause: Either the wrong password was entered the maximum number of times specified by the profile parameter FAILED_LOGIN_ATTEMPTS, or else the DBA has locked the account.
Action: Wait for PASSWORD_LOCK_TIME or contact the DBA.
For more security messages, see "28750-29249: Security Server Messages" on page 2¬686.
Cause: The account has expired and the password needs to be changed.
Action: Change the password or contact the DBA.
Cause: The account is about to about to expire and the password needs to be changed.
Action: Change the password or contact the DBA.
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 find out the rules for choosing the new password.
Cause: The password verification function did not have the required number and type of input/output arguments and/or the return argument.
Action: Check the Server Reference manual to find out the format of the password verification function.
Cause: The logon flags were not properly set or else conflicting flags were set in making calls.
Action: Call the function with appropriate flags set.
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX were both set. One parameter should be unlimited while other is set.
Action: Set the value of one parameter to UNLIMITED explicitly.
Cause: An attempt was made to reuse password after the specified number of days or after the specified number of password changes.
Action: Try the password that has not been used for the specified number of days or the specified number of password changes. Refer to the password parameters in the CREATE PROFILE statement.
Cause: The old password that was supplied is wrong. Authentication cannot proceed using the old password.
Action: Supply the correct old password for authentication and retry the operation.
Cause: CONNECT SYS/<password> ORA-is no longer a valid syntax.
Action: Try CONNECT SYS/<password> ORA-AS SYSDBA or CONNECT SYS/<password>ORA-AS SYSOPER.
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.
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
Action: Use only one IDENTIFIED GLOBALLY clause.
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.
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.
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.
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.
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
Action: Provide a valid external name.
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.
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.
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.
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.
These messages can be returned by the Heterogeneous Services feature.
Cause: The cause is explained in the forwarded message. Action
See the non-Oracle system's documentation of the forwarded message.
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.
Cause: A communication error internal to ORACLE's heterogeneous services has occurred. This should normally not occur.
Action: Contact Oracle Worldwide Support.
Cause: There are two possible causes. Either:
Action: Enable binds by setting the RESOLVE_BINDS initialization parameter to TRUE, or try to transform your SQL statement so that it does not use bind variables.
Cause: The rowid cache for Heterogeneous Services holds no entry that corresponds to the specified ROWID. Possibly the ROWID entry was overwritten in the rowid cache.
Action: Enlarge the Heterogeneous Services ROWID cache size by increasing the value of the initialization parameter ROWID_CACHE_SIZE.
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 data dictionary view.
Action: Verify that AGENT_ID and FDS_ID are set correctly in the Net8 service name definition used by the heterogeneous database link. The Net8 service name is defined in the TNSNAMES.ORA configuration file or in the Oracle Names Server. If these are correct, verify correct installation of Heterogeneous Services data dictionary information stored in dictionary tables viewable with the HS_CLASS_CAPS view.
Cause: A reference to an ORACLE Data Dictionary table or view name on a heterogeneous database link to a non-Oracle system cannot be translated. The ORACLE Data Dictionary tables viewable with view HS_CLASS_DD contains invalid SQL for the data dictionary translation.
Action: Contact customer support of the agent vendor.
Cause: Initialization parameter table for the Heterogeneous Services does not exist, or its structure (number of columns or column types) is incorrect.
Action: Verify correct installation of Heterogeneous Services' initialization parameter views, HS_CLASS_INIT and HS_INST_INIT. If these are not available, make sure you ran the script CATHO.SQL in the $ORACLE_HOME/rdbms/admin directory.
Cause: The value of the named Heterogeneous Services initialization parameter, as stored in the Oracle data dictionary, is not valid.
Action: Check Heterogeneous Services documentation to determine acceptable values and update that parameter in HS_INST_INIT using the procedures in the DBMS_HS package.
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:
Possible reasons for name mismatches are:
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.
Cause: A fatal error occurred in one of the following:
This error occurred after communication had been established successfully.
Action: Check first for network problems and remote host crashes. Most likely this is problem in the agent software. Contact a customer support representative of the agent vendor
Cause: Either the data dictionary transparency table does not exist, or its structure (number of columns or column types) is incorrect.
Action: Verify that AGENT_ID and FDS_ID, referenced by the database link definition, are set correctly in the Net8 service name defintion. If these are correct, verify that the Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHO.SQL script in the $ORACLE_HOME/rdbms/admin directory.
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.
Cause: The system date is not currently retrievable.
Action: Verify the system date.
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 AGENT_ID and FDS_ID are set correctly in the database link's connect parameters, or in the TNSNAMES.ORA entry referenced by the link definition. If these are correct, verify that the Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, execute the CATHO.SQL script in the $ORACLE_HOME/rdbms/admin directory.
Cause: This error can occur when running a script from the agent vendor to install the data dictionary information. A data dictionary translation specifies 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.
Action: Contact the customer support of the agent vendor.
Cause: The ORACLE Server's data dictionary does not define data dictionary translations for the connected non-Oracle system. The connected agent does not enable self-registration (automatic data dictionary upload).
Action: Make sure you ran the script to load the heterogeneous service data dictionary with information specific for the non-Oracle system. This script is provided by the agent vendor. If the script is run and the error persists, contact the customer support representative of the agent vendor.
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 malformed.
Action: Verify that AGENT_ID and FDS_ID are set correctly in the Net8 service name definition, which is used in the database link definition. If these are correct, verify the following:
If both scripts are executed and the error persists, contact the customer support representative of the agent vendor.
Cause: The ORACLE kernel's data dictionary does not contain capabilities for the connected non-Oracle system. The connected agent does not enable self-registration.
Action: Make sure the script to load the Heterogeneous Service data dictionary with information specific for the non-Oracle system was executed. This script is provided by the agent vendor. If the script is executed and the error persists, contact the customer support representative of the agent vendor.
Cause: An attempt to read capability definitions for a non-Oracle system from the ORACLE instance's data dictionary failed.
Action: Verify that AGENT_ID and FDS_ID are set correctly in the Net8 service name definition, which is used in the database link definition. If these are correct, verify
If the both scripts are run and the error persists, contact the customer support representative of the agent vendor.
Cause: An operation on a database link attempted to connect to a non-Oracle system. The ORACLE instance and the remote 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 Installation and User's Guide of your agent to find out what releases of the Oracle Server are supported.
Cause: Heterogeneous Services sets the maximum length of long columns to what the client defines. If the Heterogeneous Services receives a length that is not in the range of values it can handle, then this error will be signaled. This error normally should not be raised.
Action: Contact Oracle Worldwide Support.
Cause: Incorrect arguments were passed into the error message creation routine. This error normally should not be raised.
Action: Contact Oracle Worldwide Support.
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.
Cause: Mappings between Oracle datatypes and non-Oracle system datatypes are stored in the capability table in the data dictionary. This error could be raised for one of these reasons:
Action: Make sure that the script to load the heterogeneous service data dictionary was executed with information specific for the non-Oracle system. This script contains datatype capability information. This script is provided by the agent vendor. If the script is executed and the error persists, contact the customer support representative of the agent vendor.
Cause: The Heterogeneous Services was not able to convert a value from Oracle datatype to a value from the non-Oracle system datatype, or was not able to convert a value from the non-Oracle system datatype to an Oracle datatype. This could be due to one of the following reasons:
Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it might not be possible to convert the value.
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: Contact your DBA and make sure the information is correct and complete. The correct information that should be included in the Net8 service definition can be found in the agent's Installation and User's Guide.
Cause: An error occurred when initializing the Heterogeneous Services. This should not normally happen.
Action: Contact Oracle Worldwide Support.
Cause: On a Heterogeneous Services database link a setting for the two-phase commit capability (1029) is present for the connected FDS class name and/or instance name. This is supplied in either HS DD content (view HS_CLASS_CAPS or HS_INSTANCE_CAPS), or in equivalent information uploaded from the HS agent for this FDS. This mode can be set ONLY through the 2PC initialization parameter.
Action: If necessary to change the two-phase commit mode for this heterogeneous connection specify the mode ONLY in HS_CLASS_INIT or HS_INST_INIT, using INIT_VALUE_NAME = `2PC' and INIT_VALUE = `SS', `CC', `2P', `PREP', `2PCC', or `RO'.
Cause: The cursor passed by the function or procedure call is invalid.
Action: Use a cursor number returned by the API OPEN_CURSOR call.
Cause: An attempt was made to pass illegal SQL to the non-Oracle system.
Action: Ensure that the SQL supplied to the API parse call is accepted by the non-Oracle system.
Cause: An attempt was made to call a passthrough SQL function in an invalid order.
Action: Correct program flow by changing the order of API calls to match the flow described in the manual.
Cause: Passthrough parse SQL API: invalid position. A parameter notating the position is out of range.
Action: Verify the parameter is in range with the number of bind variables or select list items.
Cause: The allowed number of open cursors has been exceeded.
Action: Close open cursors by using Passthrough SQL API close call.
Cause: An attempt was made to pass a null value to a non-null parameter.
Action: Use a non-null value for the parameter.
Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.
Action: Contact your DBA. The DBA can grant permission to access the privileged table or columns.
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 your DBA to check setup of the connection and the Heterogeneous Services agent.
Cause: A database link to a non-Oracle system had no FDS_CONNECT_STRING initialization parameter in the ORACLE data dictionary for Heterogeneous Services. Without this parameter the connection could not be completed.
Action: Contact your DBA to verify correct setup of an FDS_CONNECT_STRING entry in the ORACLE Heterogeneous Services data dictionary (see HS_ALL_INITS view in the Oracle8 Server Reference Manual). It might be necessary to use PL/SQL procedures in the SYS.DBMS_HS package to create or replace an entry for the connection's FDS_CLASS_NAME and FDS_INST_NAME.
Cause: This message supplies supplementary information to assist diagnosis of an error reported in another message. FDS_CLASS_NAME and FDS_INST_NAME are used to access information in tables and views of the ORACLE data dictionary which 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.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|
