[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::archive_backup

Title:Archive/Backup
Moderator:COOKIE::MHUAIG
Created:Wed Sep 08 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:479
Total number of notes:2283

467.0. "DEVICEOFFLINE hung all saverequests !!" by ATZIS3::KARTNER_M (HOUSTON, we have a problem) Thu May 22 1997 04:35

    Hi!
    
    I have seen a strange problem at a customer site.
    VMS V6.1,MDMSV2.8a, ABS V2.1
    
    When logging in to the customer site I found 6 scheduler jobs
    (the first 6 of all that should have run during the night) and
    they were all trieing to get volumes.
    
    The logfiles contained COORDINATOR:  Facility ABS: 
    ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
    
    and 
    
    NOSUCHPROCESS
    
    again and again
    
    -) All ABS/MDMS processes were OK
    -) storage show commands for the stated volumes in the logfiles worked
       and showed no problems with the volumes
    
    When enabling Replys for TAPES i got a
    
    DEVICEOFFLINE MKE500 which is one of the 6 Robot drives.
    
    After an REPLY/ABORT=xx
    
    all scheduled save requests started without problems.
    
    Is this a known BUG ? Even if one of the tapedrives is defective
    really there should be no reason for not using the other 5 ones.
    
    							thanks
    							Michael
T.RTitleUserPersonal
Name		DateLines
467.1COOKIE::MHUAThu May 22 1997 12:1593
    
    Michael,

    It will save a lot of time for both of us if you post one example of a 
    failed save request when you post a new problem UNLESS the request log
    is really huge.  If the same line is repeated many times, you can take
    out the repeated lines and comment that you took out repeated lines.

    We appreciate that you try to summarize what you see has happened, but
    the engineering may be looking for some other traces from the log.

    -----------------------------------------

    ABS/MDMS can utilize all 6 drives provided that in your tapestart.com,
    all 6 drives are listed in drives_n symbol associated with the media
    type.

    In other words, the tapestart.com should have lines look like :

    $ MTYPE_1  := TA90K
    $ DENS_1   :=
    $ DRIVES_1 := $1$MUA20:,$1$MUA21:,$1$MUA22:,$1$MUA23:,$1$MUA24:,$1$MUA25:

    Substitute with the media_type used and drive names used at the
    customer. 

    -------------------------------------------

    ABS issues "STORAGE SELECT" to MDMS API, and when that fails for some
    reason, it retries again and again like you have seen. For some reason
    STORAGE SELECT must have failed to select all of 6 drives.  Why that
    has happened is a mystery at this point.  It could have been hardware
    failure (DEVOFFLINE could indicate that), or media robot could have
    been having troubles.   Was SLS having temporary problem at that
    point? I do not know.

    If the problem still persists, you can issue the following command to
    simulate what ABS is doing .

    1. storage allocate (media_type)/pool=(pool_name)/location=(location
    name)

    will return an available volume (for example ABS000)

    2. storage select/volume=ABS000 (media_type)

    will select a drive which is compatible to the volume. In the situation
    reported, storage select will return some error.  That will indicate
    what could have happened.  IF NOSUCHPROCESS error is returned here,
    something went wrong under MDMS layer (MDMS/Media robot/controller/
    device). Do they have loose cable connections? Do they have
    intermittent hardware problem?  It is a good idea to check out this
    drive/robot thoroughly.
     
    After the test is done, make sure you $deallocate the drive and
    $storage deallocate the volume to cleanup.

    -------------------------------------------

    Also, you must already know how to issue MRU (robot) commands to
    see what is going on at the MRU layer. For example,

    $define mru_robot (robot_name)
    $robot show drive

    will show what is loaded to which drive.  If this command fails, there
    is something wrong under MRU or hardware/controller.

    There are lots of other MRU command which you can use to see if the
    robot is responding (such as load and unload).  One caution in using
    MRU to test robot and tapes is to put the drive and volumes back
    in the condition that matches with SLS volume database.  If SLS
    show volume ABS000 says this volume is loaded in drive $1$mua001,
    before you leave, put this volume back to the drive.  If SLS show
    volume ABS001 says this volume is in slot 15, it must be put back to
    slot 15 before another ABS save request executes.

    -------------------------------------------

    Last week, I was having trouble talking to one drive out of 6 drives
    in one robot, it turned out that something went really wrong with this
    entire robot and we ended up rebooting the controller, and then the
    node itself to clear the problem.

    ----------------------------------------

    Let us know if this problem is the HOTTEST issue for this customer,
    and if the engineering needs to reprioritize the work. Otherwise,
    we'll put our time solving the outstanding IPMT cases from this
    customer.
467.2Need log fileCOOKIE::HELLWIGThu May 22 1997 12:188
Please post one of the complete save request log files (scheduler log).
In order to analyze the problem we need the information contained within
the log file.

Thank you.
Kim
467.3savelog of one save requestATZIS3::KARTNER_MHOUSTON, we have a problemFri May 23 1997 06:56378
    Hi!
    
    Sorry! If I had had the logfile allready yesterday I would have
    added it here. The problem is not top urgent (I would have opened
    an IPMT instead)
    
    Following a truncated version of one savelog. The mounting of the
    tape happened after replieing to the operator message.
    
    MRU commands were not issued (and storage select) becouse we had some
    kind of stress at the customer environment. I hadn't all investigations
    done when I replied to the opcom message (I was not really hoping that
    everything eould work afterwards).
    
    I've instructed the customer for the next occurance of the problem.
    
    							thanks
    							Michael
Executing ABS LOGIN.COM
 
%You have changed the default DEC Rdb Version at a level other
%than /PROCESS. The RMU symbol may have to be set by users
%using DEC Rdb at this level. This can be done with the
%following DCL command: @SYS$SHARE:DECRDB$SETVER RESET
 
Current JOB     DEC Rdb environment is version V6.1-02 (MULTIVERSION)
Current JOB SQL environment is version V6.1-02 (MULTIVERSION)
Current JOB Rdb/Dispatch environment is version V6.1-02 (MULTIVERSION)
Completed execution of ABS LOGIN.COM
"@abs_system:coordinator.com B667B6E8-B00B-11D0-802A-AA000400522B" Executing, output follows :
------------------------------------------------------
---------------------------------------------------------------
Starting New Request at 22-MAY-1997 02:04:24.80
   Name:   SRD2_DSA80
   UID:    B667B6E8-B00B-11D0-802A-AA000400522B   

COORDINATOR:  Attempting to allocate volume set AMP242...
COORDINATOR:  Attempting to allocate volume set AMP243...
COORDINATOR:  Attempting to allocate volume set AMP250...
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Failed to mount volume set after 1 attempts
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 4404, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 9156, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block
COORDINATOR:     %SYSTEM-W-NONEXPR, nonexistent process
COORDINATOR:  Continuing to retry every 60 seconds...
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Failed to mount volume set after 10 attempts
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 4404, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 9156, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block
COORDINATOR:     %SYSTEM-W-NONEXPR, nonexistent process
COORDINATOR:  Continuing to retry every 60 seconds...
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Failed to mount volume set after 20 attempts
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 4404, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 9156, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block
COORDINATOR:     %SYSTEM-W-NONEXPR, nonexistent process
COORDINATOR:  Continuing to retry every 60 seconds...
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1

	.........  repeated for 8 hours 


COORDINATOR:  Failed to mount volume set after 470 attempts
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 4404, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SLS_SELECT_FAILED, Failed to select usable tape drive via SLS
COORDINATOR:     Line = 9156, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block
COORDINATOR:     %SYSTEM-W-NONEXPR, nonexistent process
COORDINATOR:  Continuing to retry every 60 seconds...
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:  Mounting volume set member: AMP250 RVN 1
COORDINATOR:     (Selected drive RBACS1$MKC0:)
%MOUNT-I-MOUNTED, AMP250 mounted on _RBACS1$MKC0:
COORDINATOR:  Skipping RBACS1$MKC0: to End of Tape...
THREAD #1:  Agent information has been altered 
THREAD #1:  Facility ABS:  ABS_AGENT_INFO_ALTERED, Agent information has been altered 
THREAD #1:     Line = 326, File = RESD$:[SRC]CHECKSUM_AGENT.C;1 
THREAD #1:  Facility ABS:  ABS_AGENT_CHECKSUM_ERROR, Error checksumming agent information 
THREAD #1:     File: ABS$TEMPLATES:VMS_BACKUP-2.PARSE_TEMPLATE 
THREAD #1:   

Operation #1 starting at 22-MAY-1997 10:11:42.31

   Data Movement Type:    INCREMENTAL_SAVE
   Incremental Level:     Level 4 Operation

   Object Set:
      Object Type:        VMS_FILES
      Include List:       DSA80:
      Exclude List:       

   Archive Information:
      Storage Class Name: R_SCD2
      Saveset Location:   AMP250
      Saveset Name:       22MAY19970204262.

   Execution Environment:
      Name:               R_ENV
      Number of retries:  0
      Retry Interval:     0 minute(s)


THREAD #1:  $  
THREAD #1:  SET NOON 
THREAD #1:  $ version = F$EXTRACT(0,4,f$getsyi("VERSION")) 
THREAD #1:  $ IF (VERSION .eqs. "V6.1") THEN $DEFINE BACKUP ABS$SYSTEM:ALTERNATE_BACKUP.EXE 
THREAD #1:  $ DEFINE SYS$COM 
THREAD #1:  MAND SYS$INPUT: 
THREAD #1:  $ BACKUP DSA80:[000000...]* - 
THREAD #1:  _$  - 
THREAD #1:  _$ /LIST=_MBA4217:/FULL - 
THREAD #1:  _$  - 
THREAD #1:  _$  - 
THREAD #1:  _$ /NOCRC/NOVERIFY - 
THREAD #1:  _$  - 
THREAD #1:  _$  - 
THREAD #1:  _$  - 
THREAD #1:  _$  - 
THREAD #1:  _$ RBACS1$MKC0:22MAY19970204262./SAVE - 
THREAD #1:  _$ /STOR=V2SLS/NOASSIST - 
THREAD #1:  _$ /EXACT_ORDER 
THREAD #1:  HDR122MAY19970204262.AMP25000010016000100 97142 97142 000000DECVMSBACKUP         
THREAD #1:  HDR122MAY19970204262.AMP25000010016000100 97142 97142 000000DECVMSBACKUP         
THREAD #1:  HDR2F0819208192                     M             00                             
THREAD #1:  HDR2F0819208192                     M             00                             
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_INS_ONL_0229_15.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_INS_ONL_0229_16.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_INS_ONL_0229_17.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_INS_ONL_0229_18.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_INS_ONL_0229_19.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_INS_ONL_0229_20.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_ONL_0229_1.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_ONL_0229_12.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_ONL_0229_13.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_ONL_0229_14.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_ONL_0229_2.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]AZJOU_ONL_0229_3.DAT;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.AZJOU]PAKJOU_INS_ONL_0229.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB.RDB;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_MIX.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_MIXIDX.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_SYS.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_UA_00001.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_UA_00002.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_UA_H0001.RDA;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_UA_H0002.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_UA_H0003.RDA;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]ASTSTAMM$DB_UA_H0005.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]FEHLER_CREATE_AIJ.LOG;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]CHK_ASTSTAMM$DB_VISION.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]SCHUL_STM$DB_CREATE.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_CONSTRAINTS.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_CREATE.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_DOMAINS.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_LOAD.COM;3 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_POST_INDEX.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_PRE_INDEX.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_STORAGE_AREAS.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_STORAGE_MAPS.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_TABLES.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_TRIGGERS.SQL;2 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_UPDATE.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_UPD_ASTMODUS.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_UPD_BERECHTIGUNG.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_UPD_BEZIRK.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_UPD_BUNDESLAND.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_UPD_GEMEINDE.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$DB_VIEWS.SQL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]STM$PRIV_TABLES.SQL;13 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]TEST.SQL;2 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]TEST_CONVERT_STM.COM;2 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM.NEW]UPD_UNG_ASTPERS.SQL;2 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE.RRD;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE.UNL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE_AST.RRD;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE_AST.UNL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE_SAV.RRD;2 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE_SAV.UNL;2 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE_USER.RRD;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.ASTSTAMM]UNG_ONLINE_USER.UNL;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB.RDB;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_MA_01.RDA;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_SYS.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_UAI01.RDA;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_UAI2.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_UAI3.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-I-NOBACKUP, DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_UA_01.RDA;1 data not copied, file marked NOBACKUP 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_UA_2.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.DB.RUNDEN]NUSS_RUNDEN$DB_UA_3.RDA;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0193.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0195.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0196.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0197.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0199.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0200.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0201.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0202.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0203.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0204.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0205.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0206.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0207.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0208.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0209.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0210.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0211.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0212.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0213.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0214.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0215.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0216.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0217.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0218.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0219.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0220.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0221.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0222.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0223.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0224.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0225.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0226.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0227.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_01_0228.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0208.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0216.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0219.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0220.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0221.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0222.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0223.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0224.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0225.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0226.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0227.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_02_0228.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0614.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0635.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0657.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0660.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0661.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0665.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0666.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0668.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0669.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0670.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0671.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0672.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0673.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0674.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict 
THREAD #1:  %BACKUP-E-OPENIN, error opening DSA80:[NUSS$DISK_2.NUSS.GWWS]GWWS_09_0675.IDX;1 as input 
THREAD #1:  -SYSTEM-W-ACCONFLICT, file access conflict
467.4Some news ?ATZIS3::KARTNER_MHOUSTON, we have a problemTue Jun 03 1997 05:007
    Hi!
    
    Could you find out something?
    
    							thanks
    							Michael
467.5COOKIE::MHUATue Jun 03 1997 11:0919
    
    Michael,

    We did not find anything more than what we can say in .2 of this reply.
    SLS's "storage select" is the function failing at this point.  If this
    ever happened at the customer's site, try the commands that we described
    in .2.  Also, there is a possibility that something went wrong with SLS
    processes.  Restarting SLS may help also.  Do get the robot and drive
    checked, so that the hardware is operating properly.

    This is not a BUG on part of ABS. Someone has to be on the customer's
    system and analyze what is going wrong (in this case, under MDMS layer,
    could be MRU, robot or drive) when the symptom is still there.

    We are still looking into solving the IPMT cases from this customer.
    We would appreciate your effort and cooperation in isolating and 
    diagnosing the problem before reporting to the engineering.

                   Masami