cancel
Showing results for 
Search instead for 
Did you mean: 

JDBCdriverreturnedthefollowingerrormessagejavasqlSQLExceptionORA-01747

mf_haq
Active Participant
0 Kudos

Hi,

Secnario From Proxy to JDBC facing below error in adapter engine, while trasfering data from ECC to DB system.

Database-level error reported by JDBC driver while accessing EO handling table 'PUSH_CUSTOMER_T'. JDBC driver returned the following error message: 'java.sql.SQLException: ORA-01747: invalid user.table.column, table.column, or column specification '. For details, contact your database server vendor.

Error:

ORA-01747: invalid user.table.column, table.column, or columns specification

Cause:

You tried to reference a column name, but the column name used is a reserved word in Oracle.

where as in the DB table in our case none of the column is the oracle reserved word.

Kindly suggest the suitable answer....

Thanks in Advance

MFH

Accepted Solutions (0)

Answers (3)

Answers (3)

mf_haq
Active Participant
0 Kudos

Hi,

Does anything needs to be change in the JDBC Receiver Data structure.

<ns1:MT_CustomerMaster>

u2212

<Statement>

u2212

<PUSH_CUSTOMER_T action="INSERT">

<table>PUSH_CUSTOMER_T</table>

u2212

<access>

<CUSTOMER_ID>111</CUSTOMER_ID>

<CUSTOMER_NAME>asdf</CUSTOMER_NAME>

</access>

u2212

<Key>

<CUSTOMER_ID>111</CUSTOMER_ID>

</Key>

</PUSH_CUSTOMER_T>

</Statement>

</ns1:MT_CustomerMaster>

Former Member
0 Kudos

set the logSQLStatement = true in JDBC adapter's advanced settings, so you can see how the parsed SQL query looks like ...

Rgds

Chris

former_member200962
Active Contributor
0 Kudos
<PUSH_CUSTOMER_T action="INSERT">
.
.
<Key>
<CUSTOMER_ID>111</CUSTOMER_ID>
</Key>

Help says key element is not to be used in an INSERT statement....for more information refer point 2 of Procedure section:

http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/7b67fffde93673e10000000a114a6b/content.htm

Regards,

Abhishek.

Former Member
0 Kudos

Hi,

This error occurs as a column name was specified improperly in the current SQL statement.....Check the statement and syntax, especially references to column names, and retry the statement...might help you...

Regds,

Pinangshuk.

Former Member
0 Kudos

Have you tried executing the query directly onto the DB? Did it result in successful execution?