Hi Khurram -
First off let me point out your #'s:
-----------------------------------------------------------------------
q nodedata bksa_db2
Node Name Volume Name Storage Pool Physical
Name Space
Occupied
(MB)
---------------- ------------------------------ ---------------- --------
bksa_db2 159ABZ DB2LTOPOOL 141,680.
64
bksa_db2 158ABZ COPYPOOL 10,585.3
3
bksa_db2 157ABZ COPYPOOL 131,095.
31
--------------------------------------------------------------------------------
Both Copypools add up exactly to the DB2LTOPOOL amount shown above - which probably means in your copy pool there you have 131 GB of DB Data and 10.5 GB of DB2 logs.
Make sense to you???
~
Keeping 12 database backups will keep 12 versions. ie, 1 backup + logs = 1 version.
How large is your SLA, and how many times do you back up your DB full - once a day?
Really?
~
I have to say - having the userexit off is perplexing me!
According to things I have read, it should really be set up for userexit.
Please read this excerpt taken directly from IBM's website:
"logretain - Log retain enable configuration parameter
Logretain [No;Recovery]
The values are as follows:
No, to indicate that logs are not retained.
Recovery, to indicate that the logs are retained, and can be used for forward recovery.
If logretain is set to Recovery or userexit is set to Yes, the active log files will be retained and become online archive log files for use in roll-forward recovery. This is called log retention logging.
After logretain is set to Recovery or userexit is set to Yes (or both), you must make a full backup of the database. This state is indicated by the backup_pending flag parameter.
If logretain is set to No and userexit is set to No, roll-forward recovery is not available for the database because logs are not retained. In this situation, the database manager deletes all log files in the logpath directory (including online archive log files), allocates new active log files, and reverts to circular logging. "
Read it from here:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0000247.htm
~
According to that, your LOGRETAIN value is correct - it means specifically "If set, this parameter indicates that log files are being retained for use in roll-forward recovery. "
~
I am not sure about the USEREXIT parameter being NO though -
Please read this excerpt taken directly from IBM's website:
"userexit - User exit enable configuration parameter
Userexit [No;Yes]
If this parameter is enabled, log retention logging is performed regardless of how the logretain parameter is set. This parameter also indicates that a user exit program should be used to archive and retrieve the log files. Log files are archived when the database manager closes the log file. They are retrieved when the ROLLFORWARD utility needs to use them to restore a database.
After logretain, or userexit, or both of these parameters are enabled, you must make a full backup of the database. This state is indicated by the backup_pending flag parameter.
If both of these parameters are de-selected, roll-forward recovery becomes unavailable for the database because logs will no longer be retained. In this case, the database manager deletes all log files in the logpath directory (including online archive log files), allocates new active log files, and reverts to circular logging. "
Read it from here:
http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0000249.htm
~
So I guess basically what this means - even though they never actually say it - is that you are log enabled for recovery, but you are not using the userexit. (I *think*)
Take a close look at all this and see if you can glean the meaning here.
Any chance you have any documentation of why it was setup this way?
Also - does anyone else out there have this setup - and have it working???
(LOGRETAIN=RECOVERY, USEREXIT=NO)