ADSM-L

Re: Error during Import

1997-11-17 19:49:30
Subject: Re: Error during Import
From: "Dwight E. Cook" <decook AT AMOCO DOT COM>
Date: Mon, 17 Nov 1997 18:49:30 -0600
     If you use the undocumented, unsupported, debug command "show node #"
     in this case show node 76 indicates that 76 houses tape drive
     information.
     I would check to see if some other process might have grabbed the
     drive you were using, see if the drive called for a cleaning between
     tape mounts, temp i/o error on the drive that might have flaked
     things...make sure you have the latest microcode for the drives...
     hope this helps...
     later
         Dwight

     show objects gives :
     Type=02, Name ->MMS.Drives<-,
       homeAddr=76,  create=0, destroy=0, savePointNum=0,
       info
     ->0000000C0000000200000000000000020000000A0000000000000000000000000000
     000000000000000000000000000000000000000000000000000000000000<-

     show node 76 gives
B-Tree ROOT node: PageAddr=76, Lsn=1040955.84.2615, ObjName=MMS.Drives
LeftSib=-1, RightSib=-1, Continuation=-1
NumRecs=5, Free=926, NextSlot=518, DirOff=0, PartKeyLen=0
Level=0, NumCols=12, KeyCols=2, PartCols=0, NodeAttr=80
MaxCapacity=1004, Capacity=1004, Occupancy=78, LowOccupancy=334
  Record 0 (KeyLen=16, DataLen=31):
    Key:  ->(INTLIB)(INTDRIVE)<-
    Data: ->(/dev/mt0)(00000000)(00000003)(Null)(_...49)(ZBEG01)(Null)(Null)(N-
ull)(Null)<-
  Record 1 (KeyLen=20, DataLen=33):
    Key:  ->(TDC3494LIB1)(TDCDR01)<-
    Data: ->(/dev/rmt1)(00000008)(00000011)(Null)(a...&5)(ZDEC23)(Null)(Null)(-
Null)(Null)<-
  Record 2 (KeyLen=20, DataLen=33):
    Key:  ->(TDC3494LIB1)(TDCDR02)<-
    Data: ->(/dev/rmt2)(00000008)(00000011)(Null)(a...'.)(ZDEC23)(Null)(Null)(-
Null)(Null)<-




______________________________ Reply Separator _________________________________
Subject: Re: Error during Import
Author:  ADSM-L at unix,mime/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date:    11/17/97 3:03 PM


I haven't seen it, but I think I remember reading about it. I believe
that errors can be caused by administrative clients, or client nodes
accessing the server during export-import functions can create errors,
and that access should be locked during these functions.

Elvin Peterson wrote:
>
> While doing an Import I received the following messages:
>
>         ANR9999D IMUTIL(2555): Lock acquisition (ixLock) failed
>           for Inventory node 76.
>         ANR0530W Transaction failed for session 94 for node
>           EPETERSO (server) - internal server error detected.
>         ANR0690E IMPORT NODE: Transaction failure - server aborted
>           the transaction (1).
>         ANR0728E IMPORT NODE: Processing terminated abnormally -
>           internal error.
>
> Has anyone seen something like this before?  I tried putting a lock on
> the node that I was doing the import on, and it didn't have an impact.
>
> Elvin Peterson
> epeterso AT scj DOT com
> 414-260-3366
<Prev in Thread] Current Thread [Next in Thread>