Database Gateway Gives error- The identifier that starts with <NAME> <Firs' is too long. Maximum length is 128. {HY000,NativeErr = 103 - Calling a Remote Procedure Using DBMS_HS_PASSTHROUGH
(Doc ID 2004074.1)
Last updated on AUGUST 18, 2021
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Using Database Gateway for ODBC (DG4ODBC) 11.2.0.4 with Data Direct ODBC driver 7.1.3 or Database Gateway for SQL*Server (Dg4MSQL) from Oracle 11g then calling a SQL*Server stored procedure using DBMS_HS_PASSTHROUGH it fails with the following error -
@testingcode.sql
before open
before parse
before fetch
inside fetch loop
error ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Oracle][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]The identifier that starts with TRANSACTIONINFO <Firs' is too long. Maximum length is 128. {HY000,NativeErr = 103
PL/SQL procedure successfully completed
before open
before parse
before fetch
inside fetch loop
error ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Oracle][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]The identifier that starts with TRANSACTIONINFO <Firs' is too long. Maximum length is 128. {HY000,NativeErr = 103
PL/SQL procedure successfully completed
The XML value being passed to the procedure is too long but this code worked successfully with the 10g gateways.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |