For some reason one of our database backups failed on friday night because it was no longer enabled for online backups. This has been working for months on end and all of a sudden on friday it went bump in the night. I checked the system log for any su's to the id and the only id that did so was root (done during the backup process via a script).
What system table can I query to find out when the configuration was changed? It has been changed back to fix the problem but I dont' know how it was changed in the first place.
SQL2413N Online backup is not allowed
because either logretain or
userexit for roll-forward is not
activated, or a backup pending
condition is in effect for the
Explanation: Online backup cannot be
performed while the database is not logging for
forward recovery as forward recovery will be
required at restore time. Forward recovery is
placed into effect by setting either the database
configuration logretain parameter or the userexit
parameter, and then performing an offline
backup of the database.
User Response: Execute an offline backup or
reconfigure the database for roll-forward
recovery and issue an offline backup so that
subsequent online backups will be allowed.
check if the logretain or userexit is on
db2 get db cfg for <database_name>|grep -i LOG
You will also find the state of the database from the above statement.
try to connect to database(will give you an error, if the database is inconsistent mode).
i know what the problem is, I already fixed it but the problem is we had the database configured for online backups, it was working for 6 months and all of sudden on friday night it didn't work with the message you stated.
Nothing was changed and I can't find any evidence of any tampering with the ID on the AIX server.
I wanted to know if there was a way of querying the system tables to see when/what time the db cfg could have been changed to turn off the ability to perform online backups (like i stated above, I have already corrected the problem but my real dilemna is how do i find out when it was changed sometime after thursday night's backup (successful) and before friday nights (failed)