cancel
Showing results for 
Search instead for 
Did you mean: 

invalid identifier

Former Member
0 Kudos

Hi Experts,

I doing a interface HTTP--JDBC synchronous.While i test the scenario, i'm getting the following error

Result:

<SAP:Error><SAP:Category>XIAdapterFramework</SAP:Category><SAP:Code>MESSAGE.GENERAL</SAP:Code><SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'kss_activity_stg' (structure 'STATEMENT'): java.sql.SQLException: ORA-00904: "KEY": invalid identifier

</SAP:AdditionalText></SAP:Error>

Can you please help me out in this regard?

thanks

Pravin

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Rodrigo Pertierra.

I am using the following parameters in JDBC adapter

Drivers: oracle.jdbc.driver.OracleDriver

Connection:jdbc:oracle:thin:@10.190.16.2:1521:TRETAIL

Username and Password

Unchecked Key Tags Mandatory

Persistence : Local

Select Query

'SELECT esiid, address, city, state, zipcode, status, tdsp from tdsp_esiid WHERE tdsp = 'CPL_ENERGY'

THX

PC

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

in the Select Query field you are using an SP o u put the query? try put the query. also check if the user have permission to execute a SQL Query from an external app.

try to execute de SP into server to check if not error exists

rgds

RP

Former Member
0 Kudos

sorry it is not throwing any error in Oracle

rodrigoalejandro_pertierr
Active Contributor
0 Kudos

could you post the parameters you are putting in the JDBC adapter please

Rgds

Former Member
0 Kudos

VJ,

When i execute the same SQL statement in Oracle, it is throwing any error from the oracle side.has it got something to do with the configuration of the adapter

VijayKonam
Active Contributor
0 Kudos

Then if KEY belongs to your JDBC SQL XML message type, the problem could be in your mapping. Check the JDBC adaptor documentation and adjust the MT accordingly.

VJ

VijayKonam
Active Contributor
0 Kudos

This error is thrown by the ORACLE and caught in the adapter module. Ask you DB people to look into the error. They should be solving it in seconds..

VJ