ADSM-L

Re: TSM 3.7.3 log full - cannot restart server

2000-08-23 10:40:18
Subject: Re: TSM 3.7.3 log full - cannot restart server
From: "Cook, Dwight E" <cookde AT BP DOT COM>
Date: Wed, 23 Aug 2000 09:37:30 -0500
Allocate a new/additional recovery log file...
Find some file space and lay down a file with the dsmfmt command... like
Unix> dsmfmt -m -log /opt/IBMadsm-C/newlog 16

then do a
Unix> DSMSERV EXTEND LOG /opt/IBMadsm-C/newlog 16

After that you should be good to go, just start the dsmserv again...

Dwight


> ----------
> From:         Derrick Hazel[SMTP:derrick.hazel AT SOBEYS DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Wednesday, August 23, 2000 8:22 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      TSM 3.7.3 log full - cannot restart server
>
> When attempting to restart a crashed TSM 3.7.3 server, I get the
> following:
> --------------------------------------------------------------------------
> --
> -------------------------------
> ANR7800I DSMSERV generated at 23:08:28 on Apr 22 2000.
>
> Tivoli Storage Manager for AIX-RS/6000
> Version 3, Release 7, Level 3.0
>
> Licensed Materials - Property of IBM
>
> 5697-TSM (C) Copyright IBM Corporation 1999. All rights reserved.
> U.S. Government Users Restricted Rights - Use, duplication or disclosure
> restricted by GSA ADP Schedule Contract with IBM Corporation.
>
> ANR0900I Processing options file /usr/tivoli/tsm/server/bin/dsmserv.opt.
> ANR0990I Server restart-recovery in progress.
> ANR0200I Recovery log assigned capacity is 5000 megabytes.
> ANR0201I Database assigned capacity is 12072 megabytes.
> ANR0306I Recovery log volume mount in progress.
> ANR0353I Recovery log analysis pass in progress.
> ANR0354I Recovery log redo pass in progress.
> ANR0355I Recovery log undo pass in progress.
> ANR0352I Transaction recovery complete.
> ANR9999D logseg.c(498): Log space has been overcommitted (no empty segment
> found) -
> base LSN = 577969.0.0.
> ANR7838S Server operation terminated.
> ANR7837S Internal error LOGSEG871 detected.
> ANR7834S Thread 10 (tid a0b) terminating on signal 11 (Segmentation
> violation).
> ANR7834S GPR  0: 0xd00c6780,   1: 0x31267cb0,   2: 0x3012003c,   3:
> 0x00000000
> ANR7834S GPR  4: 0x31268268,   5: 0x00000008,   6: 0x00000002,   7:
> 0x00000000
> ANR7834S GPR  8: 0x1000b4d5,   9: 0x1000b4d5,  10: 0x3376ed70,  11:
> 0x3123bec4
> ANR7834S GPR 12: 0x1000e894,  13: 0x00000000,  14: 0x05efb00e,  15:
> 0x00000000
> ANR7834S GPR 16: 0x02000002,  17: 0x00000001,  18: 0x00000000,  19:
> 0x31267eb8
> ANR7834S GPR 20: 0x00000f80,  21: 0xf0108a00,  22: 0x3111b180,  23:
> 0x38000000
> ANR7834S GPR 24: 0x31267d68,  25: 0x00001e9d,  26: 0x31267d68,  27:
> 0x1000d61c
> ANR7834S GPR 28: 0x00000001,  29: 0x00000053,  30: 0x00000000,  31:
> 0x300037b8
> ANR7834S IAR: 0x1000e8a4   LR: 0x1000e894   CONTEXT: 0x31267930
>   0x1000E8A4 pkAbort
>   0x10060BDC LogAllocSegment
>   0x1005D490 ForceLogPages
>   0x1005DDE4 LogWriterThread
>   0x1000CDA0 StartThread
>   0xD00B535C _pthread_body
> ANR7833S Server thread 1 terminated in response to program abort.
> ANR7833S Server thread 2 terminated in response to program abort.
> ANR7833S Server thread 3 terminated in response to program abort.
> ANR7833S Server thread 4 terminated in response to program abort.
> ANR7833S Server thread 5 terminated in response to program abort.
> ANR7833S Server thread 6 terminated in response to program abort.
> ANR7833S Server thread 7 terminated in response to program abort.
> ANR7833S Server thread 8 terminated in response to program abort.
> ANR7833S Server thread 9 terminated in response to program abort.
> ANR7833S Server thread 10 terminated in response to program abort.
> ANR7833S Server thread 11 terminated in response to program abort.
> ANR7833S Server thread 12 terminated in response to program abort.
> ANR7833S Server thread 13 terminated in response to program abort.
> ANR7833S Server thread 14 terminated in response to program abort.
> ANR7833S Server thread 15 terminated in response to program abort.
> IOT/Abort trap(coredump)
> --------------------------------------------------------------------------
> --
> -----------------------------
>
> I assume this means I need to somehow add more space to the recovery log
> as
> I bring up the server, then perform a database backup.  Can someone please
> explain the process of getting more log space added... I am not the usual
> TSM-guy, just trying to fill some big shoes.
>
> TIA,
>
> Derrick
>
<Prev in Thread] Current Thread [Next in Thread>