Symptom
In a Windows environment. a scheduled DB2 online backup consistently fails when executed via DB13.
BACKUP DATABASE <DB_NAME> ONLINE TO "<DRIVE>:\BACKUP" INCLUDE LOGS
The backup job starts successfully and establishes a connection to the database using the Database: +++DB6ADM user.
Backup_Dev:Database connection +++DB6ADM established successfully
During execution of the DB2 online backup command, the process terminates unexpectedly with an ADBC exception and DB2 communication error SQL30081N.
Backup_Dev: Message: ADBC error
The failure occurs during the backup operation after the database connection has been successfully established.
Reported error in the backup log:
SQL30081N Acommunication errorhas been detected. Comm <timestamp>
Backup_Dev: Communication protocol being used: "TCP/IP". Communication API being used <timestamp>
Backup_Dev: : "SOCKETS". Location where the error was detected: "IP Address". <timestamp>
Backup_Dev: Communication function detecting the error: "selectForRecvTimeout". <timestamp>
Backup_Dev: Protocol specific error code(s): "0", "*", "*". SQLSTATE=08001
Read more...
Environment
Db2 LUW IBM
Product
Keywords
SQL30081N, DB2, DB13, SAP backup, online backup failure, ADBC error, TCP/IP communication error, SOCKETS, selectForRecvTimeout, SQLSTATE 08001, db2diag.log, Windows Event Viewer, network timeout, connectivity issue, backup failure, DB6ADM, SM37, firewall, antivirus interference, remote system unresponsive, backup troubleshooting, SAP, local drive, Backup_Dev , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview