cancel
Showing results for 
Search instead for 
Did you mean: 

Database error for JDBC to Proxy Scenario

former_member190358
Participant
0 Kudos

Hello SAP PI Gurus,

I am having a JDBC to Proxy Scenario .And the interface is running at 10 min of duration.

However, my other interface are running fine with the same details.

But for this interface, it giving the belwo error :

Database-level error reported by JDBC driver

while executing statement 'call proc_dtdc_prod_summary'.

The JDBC driver returned the following error message: '

com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table

'dtdc_prod_summary_temp' already exists'. For details,

contact your database server vendor.

So increased the time from 10 min to 20 min to 30 min. But the erro remians.

So pls look into this and give your suggestion.

Regards,

Ravi

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Ravi,

Please check execution of your stored procedure is resulting with creation of Table : dtdc_prod_summary_temp.

Modify your stored procedure to just fetch records or insert records in the existing table. Or change the code to Create a table 'dtdc_prod_summary_temp only if it doesn't exits in the Table data base.

Regards

Praveen K

former_member190358
Participant
0 Kudos

Hi Praveen,

The creation of the temp table is automatic. we cannot stop it by creating. Since it says that the table already exists so we thought that the stored procedure is not getting completed duriing 10 min time . so we increased the duration. But still no change .

Any other suggestion pls .

baskar_gopalakrishnan2
Active Contributor
0 Kudos

This is your design flaw. What is the association in terms of functionality between stored procedure and table creation? The error says that table is already exists? .. Increasing timeout will not fix this error. Only if table is not there, the stored procedure might work as per your description. If some external apps create it then you might have to take control over there or change your logic in stored procedure.

stefan_grube
Active Contributor
0 Kudos

You have to fix the issue on db level, that means: change the code of the SP to make it run.

There is nothing that you can do in PI.