Re: Recovery log space problem
Hi. The log gets filled up all the time. When you backup the TSM database, it gets empty. So, you should define a backup trigger for the database ( Admin Guide ) and consider increasing the size of the log in case it gets filled up too soon. Ran. -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Monday, June 24, 2002 8:23 AM To: [EMAIL PROTECTED] Subject: Recovery log space problem Hi We have TSM server 3.7.0 with TDP for Informix 3.7. Yesterday we got following warning messages (blue font). 06/23/02 04:06:43 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:06:51 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. 06/23/02 04:07:01 ANR0314W Recovery log usage exceeds 94 % of its assigned capacity. 06/23/02 04:07:09 ANR0314W Recovery log usage exceeds 96 % of its assigned capacity. 06/23/02 04:07:16 ANR0314W Recovery log usage exceeds 98 % of its assigned capacity. 06/23/02 04:07:18 ANR0356I Recovery log compression started. 06/23/02 04:07:18 ANR0357I Recovery log compression ended. 06/23/02 04:07:42 ANR0400I Session 12186 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:07:44 ANR0403I Session 12186 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:09:03 ANR0400I Session 12187 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:09:06 ANR0403I Session 12187 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:12:40 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:12:46 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. Output of TSM query log is as follows Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 200 200 0 196 4,09650,688 254 0.5 99.6 Is it really a space problem or what could be reason ? Thanks regards Sachin Ganu IBM Global Services (I) Pvt. Ltd.
Re: Recovery log space problem
Only in ROLLFORWARD mode. In NORMAL mode the log is used to hold the current transaction(s) and when they are committed to the database are removed from the log. He doesn't indicate what mode he's using. If this is the only thing the TSM server is doing at the time, a single TDP Informix backup, then I would look to see what the backup is doing. Maybe expiring a lot of backup objects? He also doesn't say whether this has worked and then after a while received this error, or that it just never worked without getting the log full messages. Depending on the size of his DB, I would concider increasing the LOG space anyway. You don't want your important backups to fail because of a log full problem. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ran Harel Sent: Thursday, June 27, 2002 8:41 AM To: [EMAIL PROTECTED] Subject: Re: Recovery log space problem Hi. The log gets filled up all the time. When you backup the TSM database, it gets empty. So, you should define a backup trigger for the database ( Admin Guide ) and consider increasing the size of the log in case it gets filled up too soon. Ran. -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Monday, June 24, 2002 8:23 AM To: [EMAIL PROTECTED] Subject: Recovery log space problem Hi We have TSM server 3.7.0 with TDP for Informix 3.7. Yesterday we got following warning messages (blue font). 06/23/02 04:06:43 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:06:51 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. 06/23/02 04:07:01 ANR0314W Recovery log usage exceeds 94 % of its assigned capacity. 06/23/02 04:07:09 ANR0314W Recovery log usage exceeds 96 % of its assigned capacity. 06/23/02 04:07:16 ANR0314W Recovery log usage exceeds 98 % of its assigned capacity. 06/23/02 04:07:18 ANR0356I Recovery log compression started. 06/23/02 04:07:18 ANR0357I Recovery log compression ended. 06/23/02 04:07:42 ANR0400I Session 12186 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:07:44 ANR0403I Session 12186 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:09:03 ANR0400I Session 12187 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:09:06 ANR0403I Session 12187 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:12:40 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:12:46 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. Output of TSM query log is as follows Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 200 200 0 196 4,09650,688 254 0.5 99.6 Is it really a space problem or what could be reason ? Thanks regards Sachin Ganu IBM Global Services (I) Pvt. Ltd.
Re: Recovery log space problem
Thanks for the reply. Mine is NORMAL mode. When I received space problem message, my operation did not abort, neither backup failed. It was Level 0 backup of Informix using onbar was running and of course continuous logical logs are backed up as and when they are full. This error has been noticed for the first time since last two years. Do you see still increasing size is recommended Thanks regards Sachin -Original Message- From: Bill Boyer [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 11:54 PM To: [EMAIL PROTECTED] Subject:Re: Recovery log space problem Only in ROLLFORWARD mode. In NORMAL mode the log is used to hold the current transaction(s) and when they are committed to the database are removed from the log. He doesn't indicate what mode he's using. If this is the only thing the TSM server is doing at the time, a single TDP Informix backup, then I would look to see what the backup is doing. Maybe expiring a lot of backup objects? He also doesn't say whether this has worked and then after a while received this error, or that it just never worked without getting the log full messages. Depending on the size of his DB, I would concider increasing the LOG space anyway. You don't want your important backups to fail because of a log full problem. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Ran Harel Sent: Thursday, June 27, 2002 8:41 AM To: [EMAIL PROTECTED] Subject: Re: Recovery log space problem Hi. The log gets filled up all the time. When you backup the TSM database, it gets empty. So, you should define a backup trigger for the database ( Admin Guide ) and consider increasing the size of the log in case it gets filled up too soon. Ran. -Original Message- From: Ganu Sachin, IBM [mailto:[EMAIL PROTECTED]] Sent: Monday, June 24, 2002 8:23 AM To: [EMAIL PROTECTED] Subject: Recovery log space problem Hi We have TSM server 3.7.0 with TDP for Informix 3.7. Yesterday we got following warning messages (blue font). 06/23/02 04:06:43 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:06:51 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. 06/23/02 04:07:01 ANR0314W Recovery log usage exceeds 94 % of its assigned capacity. 06/23/02 04:07:09 ANR0314W Recovery log usage exceeds 96 % of its assigned capacity. 06/23/02 04:07:16 ANR0314W Recovery log usage exceeds 98 % of its assigned capacity. 06/23/02 04:07:18 ANR0356I Recovery log compression started. 06/23/02 04:07:18 ANR0357I Recovery log compression ended. 06/23/02 04:07:42 ANR0400I Session 12186 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:07:44 ANR0403I Session 12186 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:09:03 ANR0400I Session 12187 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:09:06 ANR0403I Session 12187 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:12:40 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:12:46 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. Output of TSM query log is as follows Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 200 200 0 196 4,09650,688 254 0.5 99.6 Is it really a space problem or what could be reason ? Thanks regards Sachin Ganu IBM Global Services (I) Pvt. Ltd.
Recovery log space problem
Hi We have TSM server 3.7.0 with TDP for Informix 3.7. Yesterday we got following warning messages (blue font). 06/23/02 04:06:43 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:06:51 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. 06/23/02 04:07:01 ANR0314W Recovery log usage exceeds 94 % of its assigned capacity. 06/23/02 04:07:09 ANR0314W Recovery log usage exceeds 96 % of its assigned capacity. 06/23/02 04:07:16 ANR0314W Recovery log usage exceeds 98 % of its assigned capacity. 06/23/02 04:07:18 ANR0356I Recovery log compression started. 06/23/02 04:07:18 ANR0357I Recovery log compression ended. 06/23/02 04:07:42 ANR0400I Session 12186 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:07:44 ANR0403I Session 12186 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:09:03 ANR0400I Session 12187 started for node BRAMHA (TDP Infmx AIX42) (ShMem). 06/23/02 04:09:06 ANR0403I Session 12187 ended for node BRAMHA (TDP Infmx AIX42). 06/23/02 04:12:40 ANR0314W Recovery log usage exceeds 90 % of its assigned capacity. 06/23/02 04:12:46 ANR0314W Recovery log usage exceeds 92 % of its assigned capacity. Output of TSM query log is as follows Available Assigned Maximum MaximumPage Total Used Pct Max. Space Capacity Extension ReductionSizeUsable Pages Util Pct (MB) (MB) (MB) (MB) (bytes) Pages Util - - - --- - - - - 200 200 0 196 4,09650,688 254 0.5 99.6 Is it really a space problem or what could be reason ? Thanks regards Sachin Ganu IBM Global Services (I) Pvt. Ltd.
