cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC communication channel error

dipaks_patil
Explorer
0 Kudos

Hi Experts,

     I working on  SAP PI 7.31  proxy -> jdbc asynchronous scenario.

when checking comm channel in rwb it showing in green status. but when ping JDBC comm channel it showing below error.

and when checking rwb->message monitoring->message component->Adapter Engine<Host> -> select scenario ->audit log it showing following error.

JDBC driver was installed.

Thanks,

Dipak

Accepted Solutions (1)

Accepted Solutions (1)

dipaks_patil
Explorer
0 Kudos

Issue Resolved by basis team.

it because of patch level of abap stack and java stack is not equal of sap pi 7.31.

Answers (7)

Answers (7)

dipaks_patil
Explorer
0 Kudos

Hi

Does we required java install at Databse server box?

Thanks

former_member182004
Contributor
0 Kudos

Hi Dipak,

Maybe does a field called 'dsrPassportBytes' exists in target tables?

Wich DB motor and version are you using?

Regards,

  Juan.

dipaks_patil
Explorer
0 Kudos

Hi Juan,

Maybe does a field called 'dsrPassportBytes' exists in target tables? --> No, I check there is no field in DB

Wich DB motor and version are you using? I didn't get you, motor means?

Thanks & Regards,

Dipak.

former_member182004
Contributor
0 Kudos

Hi again Dipak,

I meant DataBase engine, sorry (SQL, Oracle, Informix..)

Regards,

dipaks_patil
Explorer
0 Kudos

hi juan manuel

             I m integrating with SQL Server 2008 database.

Thanks,

Dipak Patil

ambrish_mishra
Active Contributor
0 Kudos

Hi Dipak,

this seems like a adapter level issue. I would suggest to redeploy the driver and look at the services related to JDBC adapter in NWA. take basis help.

this is not related to connectivity to the target or field level mapping.

Ambrish

dipaks_patil
Explorer
0 Kudos

Hi

i have checked mapping with database fields it is perfect .no other JDBC scenario wokring.

    SQL Query is working on database.we are using Microsoft SQL Server 2008 database.payload is error free.

  i m able to access dbserver form pi server.driver is installed.

issue is still there

thanks

Former Member
0 Kudos

Hi Dipak,

What is the driver version you are using and also can you provide the JDBC Driver you have mentioned in the channel connfiguration.

This error might happen because of driver incompatibility.

Regards,

Anurag

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

Restart JAVA stack and try, i dont think it is driver issue .

If you have a time, create a one sender channel and dummy interface and try to connect to data base.

Thank you,

Raj

dipaks_patil
Explorer
0 Kudos

Hi Anurag,

What is the driver version you are using : JDBC version 3.0 (Which Deployed in PI Sever for connection SQL Server 2008 database).



can you provide the JDBC Driver you have mentioned in the channel configuration. :

Transport Protocol : JDBC 2.0

Message Protocol : XML SQL Format

Adapter Engine : Central Adapter Engine

JDBC Driver :com.microsoft.sqlserver.jdbc.SQLServerDriver

I tried with com.microsoft.jdbc.sqlserver.SQLServerDriver


Connection : jdbc:microsoft:sqlserver://XXXXXXX:1433;DatabaseName=XXXXXX

Thanks,

Dipak.

naveen_chichili
Active Contributor
0 Kudos

Hi Dipak,

  • Try to test the highlevel connectivity from your PI server to DB Server with the same user you are trying to connect.

  • Check the schema provided is correct and also the user has permissions to the schema you are trying to access.

  • check if the JDBC Drivers are correctly deployed.

Thanks,

Naveen

iaki_vila
Active Contributor
0 Kudos

Hi Dipak,

Have you tried to do the SQL sentence in the DB directly with the same user?, in this way you can check if you are putting a right db schema, user grants, etc.

What is the DB vendor?, you can check if there are any restriction or the driver installation is correct.

Have you checked that you are tipyng correctly all your parameters in the XML payload?.

Regards.

rajasekhar_reddy14
Active Contributor
0 Kudos

Can you check mapping out matching with data base field names? any other JDBC receiver scenario working?