ADSM-L

Journal filling up and causing backups to fail?

2002-08-02 17:07:41
Subject: Journal filling up and causing backups to fail?
From: "Coats, Jack" <Jack.Coats AT BANKSTERLING DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 1 Aug 2002 08:12:04 -0500
Config is TSM 4.1.3 on NT 4 service pack 6, with IBM3583 library and 2 LTO
drives.

I am getting this message in the dsmerror.log on SOME of my clients:

[snip]
07/31/2002 14:20:31 NtliFlush: Error 10 sending data using t_snd.
07/31/2002 14:20:31 sessFlushVerb: Error from buffer flush, rc: -155
07/31/2002 14:20:31 NtliFlush: Error 10 sending data using t_snd.
07/31/2002 21:08:35 NtliFlush: Error 10 sending data using t_snd.
07/31/2002 21:08:35 sessRecvVerb: Error -155 from call to 'readRtn'.
07/31/2002 21:08:35 NtliFlush: Error 10 sending data using t_snd.
07/31/2002 21:08:35 ANS1809E Session is lost; initializing session reopen
procedure.
07/31/2002 21:08:36 ANS1809E Session is lost; initializing session reopen
procedure.
07/31/2002 21:08:51 ANS1811S TSM session could not be reestablished.
07/31/2002 21:26:03 NtliFlush: Error 4 sending data using t_snd.
07/31/2002 21:26:03 sessSendVerb: Error sending Verb, rc: -155
07/31/2002 21:26:03 ANS1809E Session is lost; initializing session reopen
procedure.
07/31/2002 21:26:06 cuSignOnResp: Server rejected session; result code: 65
07/31/2002 21:26:06 sessOpen: Error 65 receiving SignOnResp verb from server
07/31/2002 21:26:06 ANS1316E The server does not have enough recovery log
space to
continue the current operation

07/31/2002 21:26:06 ANS1512E Scheduled event 'DAILY_INCREMENTAL' failed.
Return code = 4.
07/31/2002 21:26:06 cuSignOnResp: Server rejected session; result code: 65
07/31/2002 21:26:06 sessOpen: Error 65 receiving SignOnResp verb from server
[snip]

My morning report shows my DB and Journals like:
[Database]
Available Assigned Maximum   Maximum   Page    Total     Used      Pct
Max.
Space     Capacity Extension Reduction Size    Usable    Pages     Util  Pct

(MB)      (MB)     (MB)      (MB)      (bytes) Pages
Util
--------- -------- --------- --------- ------- --------- --------- -----
-----
364       364      0         360       4,096   92,672    232       0.3
100.6

[Journal]
Available Assigned Maximum   Maximum   Page    Total     Used      Pct
Max.
Space     Capacity Extension Reduction Size    Usable    Pages     Util  Pct

(MB)      (MB)     (MB)      (MB)      (bytes) Pages
Util
--------- -------- --------- --------- ------- --------- --------- -----
-----
8,948     8,948    0         2,420     4,096   2,290,688 712,344   31.1
31.3

This report says the database was 'overfull', but I have been expiring a lot
(removed a file system with lots of
little files) so its use is way down.

Suggestions?

<Prev in Thread] Current Thread [Next in Thread>
  • Journal filling up and causing backups to fail?, Coats, Jack <=