on 06-14-2011 3:55 PM
Hi,
We are facing an issue in production XI system where in JDBC sender channel is not polling any data from the table. Business and DB technical guy confirmed that there is new data which matches select query of XI JDBC sender channel. However XI jdbc channel is not able to poll any data.
The channel is in green status for all server nodes. But no log (as polling) in communication channel monitoring. We tried the following.
1. general JDBC locks in VA (But no JDBC locks)
2. stopped and started the channel, but no luck
3. deactivated and reactivated the JDBC channel in ID.
DB system: Oracle (not sure about version)
SAP PI 7.0 service pack 21
Regards,
Praveen Gujjeti
Have u copied the sql statement mentioned in JDBC adapter and run it through toad and checked the result.
can u try to use select statement which select particular record and update some details in JDBC adapter- the idea is to just check whether records are ready by JDBC comm or not.
chirag.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
did u check the user authorization.
also check all the configuration parameter and confirm with them JDBC driver and connection.
I dont remember now but u have to increase JDBC session from netweaver admin...can u check that too....
chirag
Edited by: Chirag Gohil on Jun 14, 2011 9:07 PM
Edited by: Chirag Gohil on Jun 14, 2011 9:09 PM
Hi Guys,
Thanks for your replies. I found this is to be a weird issue. I created copy of this channel and attached to sender aggrement (by deactivating old channel). And now it is able to pool the data from the DB table.
Dont know the reason behind this. This interface has been in place for along time and running fine. May SAP team has to find this core level service issue.
Regards,
Praveen Gujjeti
Just Few cents....
a) Test the sql query using toad or other tools to confirm that whether data is available or not.
b) Go to sender jdbc adapter and go to advanced tab. add the following parameter
logSQLStatment and value true. This will help log tracing.
c) Reactivate the channel and do restart again.
d) Check with database guys whether password is changed recently for some security reasons. IF so try with the latest login credentials. This could be problem too.
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.