Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 28500-28549: Heterogeneous Services Messages

These messages can be returned by the Heterogeneous Services feature.

##### ORA-28500: connection from ORACLE to a non-Oracle system returned this message:

Cause: The cause is explained in the forwarded message.

Action: See the non-Oracle system's documentation of the forwarded message.

##### ORA-28501: communication error on heterogeneous database link

Cause: An unexpected communication failure occurred on a heterogeneous database link to a non-Oracle system. The message above will be followed by a second message generated by the connected non-Oracle system.

Action: See the documentation for the non-Oracle system for an explanation of the second error message.

##### ORA-28502: internal communication error on heterogeneous database link

Cause: A communication error internal to ORACLE's heterogeneous services has occurred. This should normally not occur.

Action: Contact Oracle Worldwide Support.

##### ORA-28503: bind value cannot be translated into SQL text for non-Oracle system

Cause: There are two possible causes. Either:

- the non-Oracle system connected on a heterogeneous database link does not support binds
- binds have been disabled with the RESOLVE_BINDS initialization parameter.

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.

##### ORA-28504: ROWID not found in rowid cache for heterogeneous database link

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.

##### ORA-28505: unable to get non-Oracle system capabilities from name

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.

##### ORA-28506: parse error in data dictionary translation for name stored in name

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.

##### ORA-28507: error in DD table name, when processing Heterogeneous Services initialization parameters

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.

##### ORA-28508: invalid value name for Heterogeneous Services initialization parameter name

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.

##### ORA-28509: unable to establish a connection to non-Oracle system

Cause: Initialization of a database link to a non-Oracle system failed to connect to the Heterogeneous Services agent process for this non-Oracle system.

Action

  Check the Net8 service name definition in the following places:

  - in the USING clause of the CREATE DATABASE LINK statement
  - in the TNSNAMES.ORA file
  - in the Oracle Names Server

  Possible reasons for name mismatches are:

  - The USING clause in the CREATE DATABASE LINK statement has to match the service name defined in TNSNAMES.ORA or in the Oracle Names Server
  - The service name definition to connect to a non-Oracle system, requires additional Heterogeneous Services information. This information is agent specific.Please see the agent's Installation and User's Guide for more information.
  - The protocol-specific information in the service name definition must match the protocol-specific definition of the listener.
  - The SID=<name> in the service name definition (TNSNAMES.ORA file or in Oracle Names Server) must match the value in the LISTENER.ORA file for the responding listener.

##### ORA-28510: heterogeneous database link initialization failed

Cause: Initialization of a heterogeneous database link to a non-Oracle system failed due to an error identified by the agent for this non-Oracle system.

Action: Make sure the non-Oracle system is up and running and that all of the environment and initialization values for the agent are set correctly.

##### ORA-28511: lost RPC connection to heterogeneous remote agent using SID=num

Cause: A fatal error occurred in one of the following:

- the connection between the ORACLE server and the agent
- the heterogeneous services remote agent itself
- the connection to the non-Oracle system.

This error occurred after communication had been established successfully.

Action: Check 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

##### ORA-28512: error while retrieving heterogeneous DD translation information from name

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.

##### ORA-28513: internal error in heterogeneous remote agent

Cause: An internal error has occurred in the Oracle remote agent supporting a heterogeneous database link.

Action: Make a note of how the error was produced and contact the customer support representative of the agent vendor.

##### ORA-28514: heterogeneous database link initialization could not convert system date

Cause: The system date is not currently retrievable.

Action: Verify the system date.

##### ORA-28515: unable to get heterogeneous definitions from name

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.

##### ORA-28518: data dictionary translation has illegal translation type

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.

##### ORA-28519: no heterogeneous data dictionary translations available

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.

##### ORA-28520: error initializing data dictionary translations

Cause: ORACLE was unable to retrieve data dictionary translations for the non-Oracle system instance, probably because the underlying data dictionary table does not exist or is 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:

- The Heterogeneous Services data dictionary was installed correctly. If the Heterogeneous Services data dictionary is not installed, run the CATHO.SQL script in the $ORACLE_HOME/rdbms/admin directory.
- You executed 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 both scripts are executed and the error persists, contact the customer support representative of the agent vendor.

##### ORA-28521: no heterogeneous capability information available

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.

##### ORA-28522: error initializing heterogeneous capabilities

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

- The correct installation of Heterogeneous Services data dictionary. If the Heterogeneous Services data dictionary is not installed, execute the CATHO.SQL script in the $ORACLE_HOME/rdbms/admin directory.
- You executed 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 both scripts are run and the error persists, contact the customer support representative of the agent vendor.

##### ORA-28523: ORACLE and heterogeneous agent are incompatible versions

Cause: An operation on a database link attempted to connect to a non-Oracle system. 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.

##### ORA-28524: invalid max length specified for heterogeneous table column

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.

##### ORA-28525: unable to create Heterogeneous Services error message text

Cause: Incorrect arguments were passed into the error message creation routine. This error normally should not be raised.

Action: Contact Oracle Worldwide Support.

##### ORA-28526: invalid describe information returned to Heterogeneous Services

Cause: The Heterogeneous Services received invalid describe information for a select list, bind list, or stored procedure from the Heterogeneous Services agent. This indicates a problem with the Heterogeneous Services' non-Oracle system agent.

Action: Contact customer support of the agent vendor.

##### ORA-28527: Heterogeneous Services datatype mapping error

Cause: 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:

- the Oracle datatype cannot be mapped onto an non-Oracle datatype system
- a non-Oracle system datatype cannot be mapped onto an Oracle datatype.

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.

##### ORA-28528: Heterogeneous Services datatype conversion error

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:

- overflow problems (in the case of numbers)
- length limitations (in the case of character strings)
- invalid values passed into the conversion routines

Action: Contact customer support of the agent vendor. If the problem is due to size discrepancies between Oracle and the non-Oracle system, it might not be possible to convert the value.

##### ORA-28529: invalid or missing parameter in Net8 service name definition

Cause: There was an invalid or missing Heterogeneous Services parameter in the Net8 service name definition stored in either the TNSNAMES.ORA file or in the Oracle Names server.

Action: 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.

##### ORA-28530: Heterogeneous Services initialization error

Cause: An error occurred when initializing the Heterogeneous Services. This should not normally happen.

Action: Contact Oracle Worldwide Support.

##### ORA-28532: Heterogeneous Services SQL generation error

Cause: The Heterogeneous Services were not able to generate the SQL statement to be sent to the non-Oracle system. This is most likely due to incorrect settings in either the capability table or data dictionary translation table.

Action: The capability table and data dictionary table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and the agent vendor to get the correct capability and data dictionary settings installed.

##### ORA-28533: Heterogeneous Services coercion handling error

Cause: The Heterogeneous Services encountered an error in coercion handling. The Heterogeneous Services can, if the agent vendor so chooses, do some extra processing on SQL statements that contain implicit coercions or that contain coercion functions like TO_CHAR, TO_NUMBER, or TO_DATE. This functionality is controlled by some coercion related capabilities. This error will be signalled when the Heterogeneous Services encounters an error in one of these capability settings.

Action: The capability table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and agent vendor and get the correct set of capabilities installed.

##### ORA-28534: Heterogeneous Services preprocessing error

Cause: One of the things that the Heterogeneous Services can do is to preprocess parts of SQL statements that contain implicit coercions or calls to explicit coercion functions like TO_CHAR TO_NUMBER or TO_DATE. For example, it could convert a call to TO_DATE to a bind variable, pre-evaluate the TO_DATE function call and pass the resulting value to the non-Oracle system as the bind value. This behavior is controlled by some coercion related capabilities. If the capabilities are set incorrectly, the Heterogeneous Services could encounter errors when it attempts to do the preprocessing. If it does then this error will be signalled.

Action: The capability table settings are controlled by the agent vendor and can be modified by the DBA. Contact your DBA and agent vendor and get the correct set of capabilities installed.

##### ORA-28535: invalid Heterogeneous Services Context

Cause: The implementor of the agent has called one of the HS service routines with an invalid context parameter.

Action: Contact Oracle customer support or your agent vendor.

##### ORA-28550: passthrough SQL: cursor not found

Cause: The cursor passed by the function or procedure call is invalid.

Action: Use a cursor number returned by the API OPEN_CURSOR call.

##### ORA-28551: passthrough SQL: SQL parse error

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.

##### ORA-28552: passthrough SQL: call flow error

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.

##### ORA-28553: passthrough SQL: API parameter error

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.

##### ORA-28554: passthrough SQL: out of cursors

Cause: The allowed number of open cursors has been exceeded.

Action: Close open cursors by using Passthrough SQL API close call.

##### ORA-28555: passthrough SQL: required parameter missing or null

Cause: An attempt was made to pass a null value to a non-null parameter.

Action: Use a non-null value for the parameter.

##### ORA-28556: authorization insufficient to access table

Cause: A query attempted to access a table in the non-Oracle system that is either privileged or has privileged columns.

Action: Contact your DBA. The DBA can grant permission to access the privileged table or columns.

##### ORA-28557: name unknown for database link to non-Oracle system

Cause: When attempting to connect to a non-Oracle system through a Heterogeneous Services database link, the agent supporting this non-Oracle system failed to return FDS_CLASS_NAME and/or FDS_INST_NAME. ORACLE requires these names to configure the heterogeneous database link.

Action: Contact your DBA to check setup of the connection and the Heterogeneous Services agent.

##### ORA-28558: FDS_CONNECT_STRING undefined for non-Oracle system

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.

##### ORA-28559: FDS_CLASS_NAME is name, FDS_INST_NAME is 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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index