commvault.com commvault.com
Question

DB2 logbackup issue

  • 20 January 2023
  • 3 replies
  • 763 views
M
Rank
Badge +4

Hi All,
 

After updating our Commvault agent on our AIX DB2 Servers to version 11.28.44, the logbackup is not working anymore.

Tried reinstalling the backup agent, but no success. Full backup is running.
Restarted the AIX Server without success.


Simpana status:
[ General ]
 Version = 11.28.44
 Media Revision = 1081
 CommServe Host Name = vmcv001
 CommServe Client Name = vmcv001
 Home Directory = /opt/commvault/Base
 Log Directory = /var/log/commvault/Log_Files
 Core Directory = /opt/commvault
 Temp Directory = /opt/commvault/Base/Temp
 Platform Type = 4
 Cvd Port Number = 8400
[ Package ]
 1002/CVGxBase = File System Core
 1101/CVGxIDA = File System
 1207/CVGxDB2 = DB2
[ Physical Machine/Cluster Groups ]
 Name = lpas011
  - Client Hostname = lpas011
  - Job Results Directory = /opt/commvault/iDataAgent/jobResults

Commvault registry for the DB2 agent:
cat /etc/CommVaultRegistry/Galaxy/Instance001/Db2Agent/.properties
.cv.filler
dHOME /opt/commvault/Db2DataAgent
nINSTALL 1
nLOGBACKUPTODISK_SCHEDULERCHANGE 1674033804
sDB2_ARCHIVE_PATH /db2/QRD/log_archive
sDB2_AUDIT_ERROR_PATH /db2/QRD/db2dump
sDB2_RETRIEVE_PATH /db2/QRD/log_retrieve
sDb2ThresholdALFN 2

cvd.log:
19136856 709  01/20 16:25:10 ### TPool [N/A]. Ser# [1] Tot [4], Pend [0], Comp [4], Max Par [3], Avg Work Time [2.29 ms], Avg Wait Time [3.08 ms]
19136856 125b 01/20 16:25:10 --- CCVDSpaceCheck::CleanupIdleEventConnections() - Invoking CleanUp Idle Event Connections.
19136856 125b 01/20 16:25:10 ### periodicallyCleanUpIdleEventConnections() - CleanUpIdleEventConnections  started
19136856 135d 01/20 16:25:11 --- CheckAndPruneDb2AuditErrorPath() - Pruning Log Media Offset files in the dir=[/db2/QRD/db2dump ] which have not been accessed for 4 days.
19136856 135d 01/20 16:25:11 --- CheckAndPruneDb2AuditErrorPath() - Failed to open the directory: /db2/QRD/db2dump
19136856 1c5a 01/20 16:25:11 ### PreProcessClientOwnerPeriodicTaskStatus() - Owner association is disabled till next cycle.
19136856 1c5a 01/20 16:25:11 ### UpdateOwnerPeriodic() - Client owner periodic thread is disabled for further processing. Will try again in next run.

Same issue on three of our DB2 servers after upgrade of the CV DB2 agent.

Any ideas are appreciated.

3 replies

G
Rank
Userlevel 4
Badge +12

Good day @Marcel Huisman 

 

Please restart db2 services and retry the backup

 

Please check the release notes from the documentation. 

https://documentation.commvault.com/2022e/expert/2621_planning_platform_release_installations.html

 

  • Stop the DB2 services on HP UNIX and Windows clients before you start the platform release installation

    We recommend that you stop the DB2 services before you start the Commvault platform release installation so that there are no errors when you install the platform release.

  • Recycle DB2 services on UNIX clients after the platform release installation completes

    Recycle the DB2 services on UNIX clients so that the DB2 log manager uses the new Commvault VENDOR library and that log archives are successful.

    This will prevent the following error from occurring during an online full backup job.

    SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved

M
Rank
Badge +4

Server has been restarted several times after full backups, etc but still not working. (this is a SAP Test environment, so less important). In DB2 Diag, I see serveral errors Below the last section after starting a full backup. I don’t see any logfiles disappearing during the backup
 

2023-04-24-15.31.38.933724+120 I1053303A3859        LEVEL: Error
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, oper system services, sqloReadVendorRC, probe:30
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not exist"

2023-04-24-15.31.38.950957+120 I1060024A865         LEVEL: Error
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpWriteToVendorDevice, probe:2700
MESSAGE : ZRC=0x86100024=-2045771740=SQLP_SHRLIB_VENDOR_DEV_ERR
          "A vendor device reported a shared library error."
DATA #1 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x0000001E=30 -- see DB2 API Guide for meaning.
DATA #2 : Hexdump, 48 bytes
0x0A00020440158170 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0A00020440158180 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x0A00020440158190 : 0000 0000 0000 0000 0000 0000 0000 0000    .............…

2023-04-24-15.31.38.951994+120 I1060890A1659        LEVEL: Error
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, database utilities, sqluVendorCallWrapper, probe:264
MESSAGE : Error: Fenced vendor infrastructure not available.
DATA #1 : Hex integer, 4 bytes

 

2023-04-24-15.31.38.954635+120 I1062550A482         LEVEL: Error
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogVendor, probe:1860
MESSAGE : ZRC=0x86100024=-2045771740=SQLP_SHRLIB_VENDOR_DEV_ERR
          "A vendor device reported a shared library error."

2023-04-24-15.31.38.955827+120 E1063033A531         LEVEL: Warning
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3150
MESSAGE : ADM1848W  Failed to archive log file "S0220185.LOG" to "VENDOR chain
          24" from
          "/db2/QRD/log_dir/db2qrd/QRD/NODE0000/LOGSTREAM0000/C0000024/".

2023-04-24-15.31.38.958380+120 E1063565A631         LEVEL: Error
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgArchiveLogFile, probe:3160
MESSAGE : ZRC=0x86100024=-2045771740=SQLP_SHRLIB_VENDOR_DEV_ERR
          "A vendor device reported a shared library error."
DATA #1 : <preformatted>
Failed to archive log file S0220185.LOG to VENDOR chain 24 from /db2/QRD/log_dir/db2qrd/QRD/NODE0000/LOGSTREAM0000/C0000024/.

2023-04-24-15.31.38.959869+120 E1064197A538         LEVEL: Warning
PID     : 18678238             TID : 4628           PROC : db2sysc 0
INSTANCE: db2qrd               NODE : 000           DB   : QRD
HOSTNAME: lpas011
EDUID   : 4628                 EDUNAME: db2logmgr (QRD) 0
FUNCTION: DB2 UDB, data protection services, sqlpgCleanFailArchPath, probe:4940
DATA #1 : <preformatted>
Unable to archive log file 220185 from failarchpath /db2/QRD/log_dir/db2qrd/QRD/NODE0000/LOGSTREAM0000/C0000024/ for LOGARCHMETH1 due to rc -2045771740.

2023-04-24-15.31.38.997816+120 E1064736A436         LEVEL: Error
PID     : 15401272             TID : 258            PROC : db2wdog 0 [db2qrd]
INSTANCE: db2qrd               NODE : 000
HOSTNAME: lpas011
EDUID   : 258                  EDUNAME: db2wdog 0 [db2qrd]
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:8060
DATA #1 : <preformatted>
Beginning cleanup of Process id: 23200150, OSS term code: 0x101, signal: 11

2023-04-24-15.31.38.998815+120 E1065173A462         LEVEL: Error
PID     : 15401272             TID : 258            PROC : db2wdog 0 [db2qrd]
INSTANCE: db2qrd               NODE : 000
HOSTNAME: lpas011
EDUID   : 258                  EDUNAME: db2wdog 0 [db2qrd]
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:8212
DATA #1 : <preformatted>
A fenced vendor process crashed. Process id: 23200150, OSS term code: 0x101, signal: 11, bringDown: 0


If the Full backup is finished, I guess I can remove logfiles, but can I see which is the last log file that has been processed?

G
Rank
Userlevel 4
Badge +12

Hi @Marcel Huisman 

Could you login to the db2 server as root and run the following command

 

cvpkgchg -g <db2_group> 

 

replace db2_group with the group which is part of the db2 instance owner 

 

Rerun the backup.

 

Regards,

Gowri Shankar

Reply


Terms & ConditionsCookie settings