Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: Initialization of a network connection to the extproc agent did not succeed. This can be caused by network problems, incorrect listener configuration or incorrect transfer code.
Action: Check listener configuration in LISTENER.ORA and TNSNAMES.ORA or Oracle Names Server.
Cause: A fatal error occurred in either an RPC network connection, the extproc agent, or the invoked 3GL after communication had been established successfully.
Action: First check the 3GL code you are invoking, and make sure there are no network problems. Most likely, the invoked "C" routine is terminating abnormally. If all components appear to be normal but the problem persists, this could be an internal logic error in the transfer code. Contact your customer support representative.
Cause: While transferring the external procedure arguments to the agent, an unsupported datatype was detected.
Action: Check your documentation for the supported datatypes of external procedure arguments.
Cause: An internal protocol error occurred while trying to execute a callback to the Oracle Server from the user's 3GL routine.
Action: Contact Oracle Worldwide Support.
Cause: An internal network error occurred while trying to execute a callback to the Oracle Server from the user's 3GL routine.
Action: Contact Oracle Worldwide Support.
Cause: A callback from within a user's 3GL routine resulted in the invocation of another external procedure.
Action: Make sure that the SQL executed in a callback does not directly call another external procedure, or indirectly results in another external procedure, for example, triggers calling external procedures, PL/SQL procedures calling external procedures, and so on.
Cause: An internal protocol error occurred while trying to execute an external procedure resulting from a callback in another external procedure.
Action: Contact Oracle Worldwide Support.
Cause: A user or a tool tried to establish a direct connection to either an external procedure agent or a Heterogeneous Services agent, for example:
SVRMGR> CONNECT SCOTT/TIGER@NETWORK_ALIASThis is not allowed.
Action: When executing the CONNECT statementake sure your database link or network alias is not pointing to a Heterogeneous Services agent or an external procedure agent.