Skip to Content
0

MaxDB - Command Timeout Error

May 15 at 02:54 PM

61

avatar image
Former Member

Hi All,

we are executing a Data Services extraction job that reads from a SAP on MaxDB.

The job ends with the following error:

[SAP AG][SDBODBC DLL][MaxDB] General error;-10807 Connection down: [3] command timeout

from the transaction sap DB59 the errors present are as follows: Communication Timeout - Command Timeout

what is the cause? how can the problem be solved?

Thanks and Best Regards

Davide


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

James Zhang
May 16 at 05:35 AM
0

Hi Davide,

Here is the return code explanation:

<
Explanation
The connection to the database instance was terminated. This error can occur if, for example, the database instance was shut down, or if there are network problems.<description> provides the internal error number and further information about the error.
User Response
Check the connection data. Check whether the database instance is ONLINE. If it is online, log on to the database instance again using the SQLDBC_Connection::connect method.
>

Besides above, do you have network firewall which will kill the network connection after certain threshold reached?

If note of above helps, please attach diagpack.tgz maxdb trace after executing command:

dbmcli -d <dbsid> -u superdba,<password> diag_pack


Best regards,

James

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 16 at 03:59 PM
0

Dear James,

our problem was due to default timeout for the database user.

Db session could need several minutes in ETL environment.

By extending the maxDB user timeout we avoided the error.

Thank you so much.

Hello

Share
10 |10000 characters needed characters left characters exceeded