JDBC - logSQLStatement in PI 7.1

[Shabarish_Nair]

logSQLStatement - true used to work in other versions, but it doesnt seem to do so in PI 7.1

1. Can someone check if it is working on their PI 7.1 box?

2. Is there a work around to see the JDBC statement formed by the adapter?

We are having some issues on a SP call but since we are unable to see what is the statement being created by the adapter, it is getting tricky.

Thanks folks!!!

Regards,

Shabz

[Former Member · Accepted solution]

Hi Shabarish,

I think we should not have any issues with it. I am looking through the note:

Note 801367 - XI 3.0 JDBC Adapter: Additional Parameters

It says it is working from XI 3.0 SP9 itself. It is not mentioning anything for 7.1. But if it doesnot work for you the other option would be to see the trace for the jdbc adapter. If you have access can you see the trace and see you have any issues with the statement. We are also not on 7.1 to test for you.

Regards,

---Satish

[former_member604483]

Hello Shabarish,

I have the same problem in PI 7.1

Did you solve the problem?

Best regards,

Jürgen

[Shabarish_Nair]

no luck yet.

i was planning to raise a message with SAP

[former_member604483]

Okay. Thx for the info.

Juergen

[Former Member]

Hi Shabarish,

Can you update us on this tread? I am experiencing a similar issue.

PI 7.11

Thanks in advance,

Venkat.

[Former Member]

I am also facing the same issue .. PI 7.11

Please let me know

mike

[Former Member]

Hi guys,

Can anyone update us on this tread? We are facing a similar issue on java only 7.4

Thank you,

PM

[justin_santhanam]

Shabz,

Can you check if the Exchange Profile parameter value ?

Default - Default.DatabaseSettings - com.sap.aii.util.sql.loglevel

This parameter is used to log sql-accesses performed by the software (0 = no logging, 1 = log structure of SQL statement, 2 = log values, 3 = log stacktrace)

Thanks!

[Former Member]

Shabz,

1. Can someone check if it is working on their PI 7.1 box?

Yes, it works on 7.1. We have been using this in our non-prod environments. Just to add - SAP does not recommend to use this parameter in productive environment.

2. Is there a work around to see the JDBC statement formed by the adapter?

If you use this parameter, you can check the query formed in Audit Log. In case you are not using this, then the SQL statement comes into the Java Log.

Hope this helps.

Regards,

Neetesh