Avamar DB2 backup fails with Error "Unable to spawn Avdb2 for backup," and error SQL2025N in db2diag log

Summary: Avamar DB2 backup fails or completes with exceptions. The db2diag.log shows a vendor error and a SQL2025N I/O error shortly after the backup starts. With avdb2 debug enabled it shows a process file lock error. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Avamar DB2 backup fails or completes with exceptions. The db2diag.log shows a vendor error and a SQL2025N I/O error shortly after the backup starts. 

The avdb2 log shows the following:

2023-01-13 02:30:10 avdb2 Info <6688>: Process 965860 (/usr/local/avamar/bin/avdb2) finished (code 170: completed with errors, client log should be examined)
2023-01-13 02:30:10 avdb2 Warning <6690>: CTL workorder "DB2_DB_0220-DBNAMEXDS01_DB-1673547600007#1" non-zero exit status 'code 170: completed with errors, client log should be examined'
2023-01-13 02:30:10 avdb2 Error <16720>: Unable to spawn Avdb2 for backup/restore of [db2inst1/DBNAME db2inst1/DBNAME].
2023-01-13 02:30:10 avdb2 Info <6686>: Process 966206 (/usr/local/avamar/bin/avtar) for workorder DB2_DB_0220-DBNAMEXDS01_DB-1673547600007#201 started
2023-01-13 02:30:10 avdb2 Info <10684>: Setting ctl message version to 3 (from 1)
2023-01-13 02:30:10 avdb2 Info <16136>: Setting ctl max message size to 268435456
2023-01-13 02:30:13 avdb2 Info <6688>: Process 966206 (/usr/local/avamar/bin/avtar) finished (code 0: success)
2023-01-13 02:30:13 avdb2 Error <16729>: Unable to get the list of backup images from the child process.
2023-01-13 02:30:13 avdb2 Info <9772>: Starting graceful (staged) termination, Unable to get the list of backup images from the child process. (wrap-up stage)


With debug enabled, can also see errors similar to this regarding process file lock:

2023/01/12-18:20:04.79408 [ctl_conn_recv-DB2_DB_0220-DBNAMEXDS01_DB-1673547600007#1] ctl_connection::lowdata:
recv:<status_wrapup_summary pid="Hidden DB2 backup" exitcode="22" numbytes="0" startUTC="2023-01-12 18:20:04" pidnum="1055" newbytes="0" backuptime="0" finishUTC="2023-01-12 18:20:04" errorcode="10003" key=
"1009-DB2_DB_0220-DBNAMEXDS01_DB-1673547600007#1" cid="DBNAMExds01" mid="965949/965949/33" last_ctl_man_key="1009-DB2_DB_0220-DBNAMEXDS01_DB-1673547600007#1" wid="DB2_DB_0220-DBNAMEXDS01_DB-1673547600007#1"
errormessage="code 153: lock error - process already running or error creating local lock file" errorrealm="">

 

Errors from db2diag.log right after backup initiates: 
2023-01-17-03.30.03.849521+480 I300934E909 LEVEL: Error
PID : 9696 TID : 140540540610304 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : DBNAME
APPHDL : 0-55065 APPID: *LOCAL.db2inst1.230116193009
AUTHID : DB2INST1 HOSTNAME: db2hostname
EDUID : 32933 EDUNAME: db2med.30870.0 (DBNAME) 0
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:699
DATA #1 : String, 144 bytes
Vendor error: rc = 25 returned from function sqluvput.
Return_code structure from vendor library /usr/local/avamar/lib/libdb2_avamarloader.so:

DATA #2 : Hexdump, 48 bytes
0x00007FD47978F350 : 1701 0000 4176 7461 7220 496E 7075 742F ....Avtar Input/
0x00007FD47978F360 : 4F75 7470 7574 2065 7272 6F72 2E00 0000 Output error....
0x00007FD47978F370 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2023-01-17-03.30.04.850521+480 E301844E535 LEVEL: Error
PID : 9696 TID : 140540540610304 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : DBNAME
APPHDL : 0-55065 APPID: *LOCAL.db2inst1.230116193009
AUTHID : DB2INST1 HOSTNAME: db2hostname
EDUID : 32933 EDUNAME: db2med.30870.0 (DBNAME) 0
FUNCTION: DB2 UDB, database utilities, sqluMCWriteToDevice, probe:1304
MESSAGE : Media controller -- problem writing to vendor device. rc = -2025

2023-01-17-03.30.04.850898+480 E302380E571 LEVEL: Error
PID : 9696 TID : 140540540610304 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : DBNAME
APPHDL : 0-55065 APPID: *LOCAL.db2inst1.230116193009
AUTHID : DB2INST1 HOSTNAME: db2hostname
EDUID : 32933 EDUNAME: db2med.30870.0 (DBNAME) 0
FUNCTION: DB2 UDB, database utilities, sqluMCWriteToDevice, probe:1304
MESSAGE : SQL2025N An I/O error occurred. Error code: "". Media on which this
error occurred: "".

Cause

This error occurs because of incorrect user or permissions for the Avamar /usr/local/avamar/var/clientlogs directory. 

Example of incorrect permissions which caused the problem in this case: 
drwxr-xr-x 2 root root 20480 Jan 17 08:00 clientlogs

Resolution

The directory needs at minimum read+execute permission for the db2 user and group used for the backup job.

Below is an example command which can be used to resolve the issue. This must be adjusted to match the operating system Avamar path and db2 admin group name.

The commands must be run as the root user. 
chown root:db2iadm1 /usr/local/avamar/var/clientlogs

Example command to set minimum permissions: 
chmod 755 /usr/local/avamar/var/clientlogs


Affected Products

Avamar Client, Avamar Plug-in for IBM DB2, Avamar Server
Article Properties
Article Number: 000210810
Article Type: Solution
Last Modified: 02 Jun 2023
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.