Oracle Database Errors or Warnings from Error ORA-28546 to ORA-28557

SQLServerF1

ORA-28546: connection initialization failed, probable Net8 admin error
Cause: A failure occurred during initialization of a network connection from the Oracle server to a second process: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Net8 administrative setup for database links or external procedure calls. The most frequent specific causes are: — Database link setup for an Oracle-to-Oracle connection instead connects to a Heterogeneous Services agent or an external procedure agent. — Database link setup for a Heterogeneous Services connection instead connects directly to an Oracle server. — The extproc_connection_data definition in tnsnames.ora connects to an Oracle instance instead of an external procedure agent. — Connect data for a Heterogeneous Services database link, usually defined in tnsnames.ora, does not specify (HS=). — Connect data for an Oracle-to-Oracle database link, usually defined in tnsnames.ora, specifies (HS=).
Action: Check Net8 administration in the following ways: — When using TNSNAMES.ORA or an Oracle Names server, make sure that the connection from the ORACLE server uses the correct service name or SID. — Check LISTENER.ORA on the connection end point’s host machine to assure that this service name or SID connects to the correct program. — Confirm in TNSNAMES.ORA or the equivalent service definition that service ‘extproc_connection_data’ does NOT contain (HS=), or that the service definition used by a Heterogeneous Services database link DOES contain (HS=).
ORA-28547: connection to server failed, probable Oracle Net admin error
Cause: A failure occurred during initialization of a network connection from a client process to the Oracle server: The connection was completed but a disconnect occurred while trying to perform protocol-specific initialization, usually due to use of different network protocols by opposite sides of the connection. This usually is caused by incorrect Oracle Net administrative setup for database links or external procedure calls. The most frequent specific causes are: — The connection uses a connect string which refers to a Heterogeneous Services agent instead of an Oracle server. — The connection uses a connect string which includes an (HS=) specification.
Action: Check Oracle Net administration in the following ways: — When using TNSNAMES.ORA or an Oracle Names server, make sure that the client connection to the ORACLE server uses the correct service name or SID. — Check LISTENER.ORA on the connection end point’s host machine to assure that this service name or SID refers to the correct server. — Confirm in TNSNAMES.ORA or the equivalent service definition that the connect string does NOT contain (HS=).
ORA-28550: pass-through SQL: cursor not found
Cause: A value passed to a pass-through SQL function or procedure call as a cursor does not identify a currently open cursor.
Action: Use a cursor number returned by the pass-through SQL OPEN_CURSOR call.

ORA-28551: pass-through SQL: SQL parse error
Cause: A non-Oracle system rejected text supplied as a pass-through SQL statement.
Action: Ensure that the SQL supplied to the pass-through SQL PARSE call is legal for the non-Oracle system.
ORA-28552: pass-through SQL: call flow error
Cause: A pass-through SQL function was called 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: pass-through SQL: invalid bind-variable position
Cause: A pass-through SQL function referring to the position of a bind variable in the currently-parsed SQL statement supplied an invalid bind-variable position. Valid values are 1 through n, where n is the number of bind-variable place-holders in the SQL text.
Action: Verify that the bind-variable position parameter is in the correct range to represent a place-holder in the SQL text. Confirm that the SQL text uses the correct syntax for a bind-variable place-holder, as required by the non-Oracle system.

ORA-28554: pass-through SQL: out of cursors
Cause: The maximum number of open cursors has been exceeded.
Action: Close open cursors by using the pass-through SQL CLOSE_CURSOR function.
ORA-28555: pass-through 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 the DBA for the non-Oracle system. The DBA can grant permission to access the privileged table or columns.
ORA-28557: unknown string 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 the DBA to check setup of the connection and the Heterogeneous Services agent.

Above are list of Oracle Database Errors or Warnings from Error ORA-28546 to ORA-28557 received while performing certain operation against Oracle Database or related products.

What are Oracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Database Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *