A db2 get db cfg for .... will include info on the "first active log file". That log file and subsequent log files (numbered sequentially-higher) are the active log files. Lower-numbered log files are inactive and candidates for archival. If the userexit is running OK, you should see very few, if any, lower-numbered filenames. The TSM user-exit normally writes to audit files in a directory specified by the DSMI_LOG environment variable (at least in my shop it does).
-----Original Message-----
From: steve freeman [mailto:db2udbdba-ezmlmshield-x46747847.[Email address protected]
Sent: Wednesday, September 28, 2005 6:11 PM
To: LazyDBA Discussion
Subject: disk full msg
Hi DBAs
Our environment configuration is as follows.
2 instances, each instance contains 2 databases. Userexit and logretain turned on in each db cfg. We are
using TSM for online backups.
We do a full online backup each night of the 4 databases (inst1 contains LIVE and STAGE, inst2 contains TST and TST2)
db2adutl reports online backups completed and "list history" shows successful backups. The following error is reported in
the db2diag.log on inst1.
DIA8312C Disk was full.
ZRC=0x850F000Cÿ
2005-09-28-10.40.46.719899 Instance:db2inst1 Node:000
PID:606402(db2loggr (TBP) 0) TID:1 Appid:none
data protection sqlpgCallGIFL Probe:2750
Error rc: -2062614516, when initializing log file: 108
I know that this is due to the logfile directory being full, but my question is regarding archive logs. My understanding is that
If USEREXIT=ON and LOGRETAIN = RECOVERY then full logs are archived and then reused. The userexit program db2uext2.ctsm should copy the archived logs to TSM and then reuse. My "db2adutl query" command shows no archived logs for my
LIVE and STAGE databases. How could this occur? Am I correct in thinking that no logs presently are full and ready for archiving?
And is there a command to tell me which logs are still active.
Instance1 databases do not show any archive logs, as if the userexit is not being called. When we updated the db cfg we stopped and restarted the databases.
$ db2adutl query logs
Query for database TST
Retrieving LOG ARCHIVE information.
Log file: S0000000.LOG, DB Partition Number: 0, Taken at: 2005-09-18-22.44.47
Log file: S0000001.LOG, DB Partition Number: 0, Taken at: 2005-09-19-04.44.54
Log file: S0000002.LOG, DB Partition Number: 0, Taken at: 2005-09-20-04.45.04
Log file: S0000003.LOG, DB Partition Number: 0, Taken at: 2005-09-21-04.45.35
Log file: S0000004.LOG, DB Partition Number: 0, Taken at: 2005-09-22-04.45.13
Log file: S0000005.LOG, DB Partition Number: 0, Taken at: 2005-09-23-04.45.30
Log file: S0000006.LOG, DB Partition Number: 0, Taken at: 2005-09-24-04.45.31
Log file: S0000007.LOG, DB Partition Number: 0, Taken at: 2005-09-25-04.45.23
Log file: S0000008.LOG, DB Partition Number: 0, Taken at: 2005-09-26-04.45.17
Log file: S0000009.LOG, DB Partition Number: 0, Taken at: 2005-09-27-04.46.04
Log file: S0000010.LOG, DB Partition Number: 0, Taken at: 2005-09-28-04.46.02
Query for database LIVE
Retrieving LOG ARCHIVE information.
No LOG ARCHIVE images found for LIVE
Query for database STAGE
Retrieving LOG ARCHIVE information.
No LOG ARCHIVE images found for STAGE
Query for database TST2
Retrieving LOG ARCHIVE information.
Log file: S0000000.LOG, DB Partition Number: 0, Taken at: 2005-09-08-17.19.31
Log file: S0000001.LOG, DB Partition Number: 0, Taken at: 2005-09-09-05.31.58
Log file: S0000002.LOG, DB Partition Number: 0, Taken at: 2005-09-09-05.34.50
Log file: S0000003.LOG, DB Partition Number: 0, Taken at: 2005-09-10-04.39.46
Log file: S0000004.LOG, DB Partition Number: 0, Taken at: 2005-09-10-04.42.46
Log file: S0000005.LOG, DB Partition Number: 0, Taken at: 2005-09-11-04.39.38
Log file: S0000006.LOG, DB Partition Number: 0, Taken at: 2005-09-11-04.42.37
Log file: S0000007.LOG, DB Partition Number: 0, Taken at: 2005-09-12-04.39.43
Log file: S0000008.LOG, DB Partition Number: 0, Taken at: 2005-09-12-04.42.40
Log file: S0000009.LOG, DB Partition Number: 0, Taken at: 2005-09-13-04.39.51
Log file: S0000010.LOG, DB Partition Number: 0, Taken at: 2005-09-13-04.42.50
Log file: S0000011.LOG, DB Partition Number: 0, Taken at: 2005-09-14-04.31.54
Log file: S0000012.LOG, DB Partition Number: 0, Taken at: 2005-09-14-04.34.52
Log file: S0000013.LOG, DB Partition Number: 0, Taken at: 2005-09-15-04.31.56
Log file: S0000014.LOG, DB Partition Number: 0, Taken at: 2005-09-15-04.34.55
Log file: S0000015.LOG, DB Partition Number: 0, Taken at: 2005-09-16-04.32.01
Log file: S0000016.LOG, DB Partition Number: 0, Taken at: 2005-09-16-04.35.20
Log file: S0000017.LOG, DB Partition Number: 0, Taken at: 2005-09-17-04.40.10
Log file: S0000018.LOG, DB Partition Number: 0, Taken at: 2005-09-17-04.43.16
Log file: S0000019.LOG, DB Partition Number: 0, Taken at: 2005-09-18-04.40.02
Log file: S0000020.LOG, DB Partition Number: 0, Taken at: 2005-09-18-04.42.58
Log file: S0000021.LOG, DB Partition Number: 0, Taken at: 2005-09-19-04.43.41
Log file: S0000022.LOG, DB Partition Number: 0, Taken at: 2005-09-20-04.43.50
Log file: S0000023.LOG, DB Partition Number: 0, Taken at: 2005-09-21-04.44.19
Log file: S0000024.LOG, DB Partition Number: 0, Taken at: 2005-09-22-04.43.59
Log file: S0000025.LOG, DB Partition Number: 0, Taken at: 2005-09-23-04.44.15
Log file: S0000026.LOG, DB Partition Number: 0, Taken at: 2005-09-24-04.44.16
Log file: S0000027.LOG, DB Partition Number: 0, Taken at: 2005-09-25-04.44.12
Log file: S0000028.LOG, DB Partition Number: 0, Taken at: 2005-09-26-04.44.05
Log file: S0000029.LOG, DB Partition Number: 0, Taken at: 2005-09-27-04.44.45
Log file: S0000030.LOG, DB Partition Number: 0, Taken at: 2005-09-27-12.46.59
Log file: S0000031.LOG, DB Partition Number: 0, Taken at: 2005-09-28-04.44.50
Log file: S0000032.LOG, DB Partition Number: 0, Taken at: 2005-09-28-11.59.42
Thanks in advance for any Tips, experience or pointers in the above
I
---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page