Conference cookie::archive_backup

    Hi!
    
    Please provide more information. For trapping an ABS bug you
    need at least:
    
    		-) definition of starage class
    		-) definition of execution environment
    		-) $storage sho volume of the volumes stated in you logs
    
    Is the MDMS authorization done correctly ?
    
    							thanks
    							Michael
    
    PS.: By the way .. the best way to read the status block in the
    	 logfiles is from backwards. The last line is the most important
    	 one. "Failed to extend Storage Class" is a very generic error
    	 that doesn't say much

    
    Hi,
    
    Michael did a good job summerizing what we are looking for in -1.
    
    The issue of consolidation criteria (interval and size) should have
    nothing to do with the problem reported here.  Something is wrong with
    the volume level, either in MDMS, hardware or actual tape media. 
    
    We'll wait for more info., to be posted.
    
    Masami
    

    Hi!

      Thank you for your quick reply .

      The following are more information abort multi_volume error :
    
...............................................................................
(a) definition of starage class - DB_DUMP_001

Storage Class
    Name      - DB_DUMP_001
    Version   - 4
    UID       - B712CE65-DBFB-11D0-9D3C-463246533031 
    Node Name - F2FS01
    Archive File System
        Primary Archive Location    - 
    Staging Location    - 
        Primary Archive Type         - SLS/MDMS
        Staging Archive Type         - NOT IMPLEMENTED
        Staging Retention Period - 17-NOV-1858 00:00:00.00
    Owner     - F2FS01::SYSTEM
    Access Right - F2FS01::SYSTEM
        Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
    Tape Pool - SABLEPOOL
    Volume Set Name     - None
    Retention Criteria
        Number Of Copies - 4
        Retention Period -   21 00:00:00.00
    Consolidation Criteria
        Count    - 0
        Capacity - 0
        Size     - 4
        Interval-   2 00:00:00.00
    Catalog Name          - ABS_CATALOG
    Retain When Idle Flag - NO
    Streams               - 3
    Media Management Info
        Media Location        - None
        Media Type  - TK88_SWXNA
        Device Name     - None

...............................................................................
(b) definition of execution environment : DB_DUMP_001_ENV
 
Execution Environment
    Name      - DB_DUMP_001_ENV
    Version   - 4
    UID       - 10D2A4B1-DB25-11D0-9D3C-463246533031 
    Data Safety Options - FULL_DATA_VERIFICATION, XOR_REDUNDANCY_GROUPS, CRC_VERIFICATION, TAPE_READ_VERIFICATION
    Listing Option - NO_LISTING
    Span Filesystem Options - SPAN FILESYSTEMS
    Symbolic Links Option - LINKS_ONLY
    Compression Options - None
    User Profile
                Node - F2FS01
             Cluster - F2FSB
                User - <REQUESTER>
               Privs - 
         Platform ID - 0
        Access Right - None
    Owner     - F2FS01::SYSTEM
    Access Right - F2FS01::SYSTEM
        Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL, EXECUTE
    Notification Method - NOTIFY_BY_MAIL
    Notification List   - RTSMC1::MJCHOU,RTSMC1::KCWEI,RTSMC1::SYLINB,SABLE5::ORACLE7
    Notification Reason - ON_WARNING_CONDITION, ON_ERROR_CONDITION, ON_FATAL_ERROR_CONDITION, AT_COMPLETION

    Agent Filesystem Options - FILE_IGNORE_WRITERS
    Logging Option           - NOT SUPPORTED 
    Number of Drives         - 1
    Staging Option           - STAGING_ALLOWED
    Retry Count      - None
    Retry Interval   - None
    Prologue Command - @$1$DUA17:[ABSMGR.MANUAL.ORACLES]F2FS_SETABS001.COM
    Epilogue Command - @$1$DUA17:[ABSMGR.MANUAL.ORACLES]F2FS_NEXT001.COM

...............................................................................
(c) $storage sho volume of the volumes stated in you logs :

  Volume:      ALX110               Owner:      F2FS01::ABS
  Format:      BACKUP               Brand:      
  Allocated:    3-JUN-1997 19:00    Scratch:    25-JUN-1997 03:28
  Purchased:   21-MAR-1997 17:45    Cleaned:    21-MAR-1997 17:45
  Media type:  TK88_SWXNA           Length:          0
  Mounts:           3               UIC:        [ABS]
  Location:    HEADQUARTERS         Protection: S:RW,O:RW,G:R,W:
  Notes:       
  Offsite:                          Onsite:                
  IO Errors:        0               Flag:       ALLOCATED
  Next volume: *none*               Previous:   *none*
  Pool:        SABLEPOOL            Rec len: 0  Block factor: 0
  Initialized:  3-JUN-1997 19:00    Density:    COMP
  Slot number:         
  Side:                             Other side:         
  Jukebox / slot:     TL810_SWXNA / 10
  Drive:       *F2FS01::$1$MUA140             
  Volume is in a jukebox slot.
  Volume is not in a magazine.

...............................................................................
(d) volume summary:
                    Run date  5-JUN-1997 10:15                   

Cartridge                Status of Jukebox Volumes
slot  Status    Volume    Status  Pool          Allocated        Scratch 
------------------------------------------------------------------------------
0   In Slot   ALX100    Alloc   SABLEPOOL   1-JUN-1997 21:38  16-JUN-1997 21:38
1   In Slot   ALX101    Alloc   SABLEPOOL   2-JUN-1997 18:01  24-JUN-1997 03:17
2   In Slot   ALX102    Free    SABLEPOOL   9-MAY-1997 20:53  23-MAY-1997 21:02
3   In Slot   ALX103    Free    SABLEPOOL   9-MAY-1997 21:17  23-MAY-1997 21:20
5   In Slot   ALX105    Free    SABLEPOOL   9-MAY-1997 19:19  23-MAY-1997 19:41
6   In Slot   ALX106    Free    SABLEPOOL   9-MAY-1997 19:34  23-MAY-1997 19:34
7   In Slot   ALX107    Free    SABLEPOOL  10-MAY-1997 20:01  24-MAY-1997 20:01
8   In Slot   ALX108    Free    SABLEPOOL  13-MAY-1997 13:42  26-MAY-1997 18:01
9   In Slot   ALX109    Alloc   SABLEPOOL  20-MAY-1997 04:10   8-JUN-1997 05:56
10  In Slot   ALX110    Alloc   SABLEPOOL   3-JUN-1997 19:00  25-JUN-1997 03:28
11  In Slot   ALX111    Free    SABLEPOOL   7-MAY-1997 20:01  21-MAY-1997 23:32
12  In Slot   ALX112    Free    SABLEPOOL  13-MAY-1997 15:36  31-MAY-1997 07:20
13  In Slot   ALX113    Free    SABLEPOOL  12-MAY-1997 04:00   1-JUN-1997 05:16
14  In Slot   ALX114    Free    SABLEPOOL   7-MAY-1997 20:11  27-MAY-1997 08:35
15  In Slot   ALX115    Free    SABLEPOOL   7-MAY-1997 20:31  27-MAY-1997 06:21
	.	.	.	.	.	.	.	.
	.	.	.	.	.	.	.	.
	.	.	.	.	.	.	.	.
28  In Slot   ALX128    Alloc   SABLEPOOL  28-MAY-1997 22:31  19-JUN-1997 06:01
29  In Slot   ALX129    Alloc   SABLEPOOL   1-JUN-1997 21:35  16-JUN-1997 01:35
4   In        ALX104    Alloc   SABLEPOOL   3-JUN-1997 18:01  25-JUN-1997 18:00
    jukedrive 
        30 record(s) found

...............................................................................
(e) sys$manager:tapestart.com

	.	.	.	.	.	.	.	.
	.	.	.	.	.	.	.	.
$	TAPE_JUKEBOXES := "TL810_SWXNA" 
$	TL810_SWXNA    := "F2FS01::$1$DUA100:," -
                          "F2FS01::$1$MUA120:," -
                          "F2FS01::$1$MUA130:," -
                          "F2FS01::$1$MUA140:," -
                          "F2FS01::$1$MUA150:" 
$!
$       MTYPE_1  := TK88_SWXNA
$       DENS_1   := COMP
$       DRIVES_1 := "$1$MUA120:,$1$MUA130:,$1$MUA140:,$1$MUA150:" 
$!
	.	.	.	.	.	.	.	.
	.	.	.	.	.	.	.	.
...............................................................................
(f) logfile :

	.	.	.	.	.	.	.	.
THREAD #2:  %BACKUP-I-RESUME, resuming operation on volume 2 
THREAD #2:  %BACKUP-I-READYWRITE, mount volume 2 on _$1$MUA140: for writing 
COORDINATOR:  Mounting volume set member: ALX110 RVN 2
THREAD #2:  Failed to extend Storage Class 
THREAD #2:  Facility ABS:  ABS_ARCHIVE_EXTEND_FAILED, Failed to extend Storage Class 
THREAD #2:     Line = 558, File = RESD$:[SRC]AGENT_STATE_MACHINE.C;1 
THREAD #2:  Facility ABS:  ABS_ARCHIVE_EXTEND_FAILED, Failed to extend Storage Class 
THREAD #2:     Line = 993, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1 
THREAD #2:  Facility ABS:  ABS_ARCHIVE_EXTEND_FAILED, Failed to extend Storage Class 
THREAD #2:     Line = 737, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1 
THREAD #2:  Facility ABS:  ABS_SLS_APPEND_FAILED, Failed to append to volume set via SLS 
THREAD #2:     Line = 5318, File = RESD$:[SRC]SLS_SERVICES.C;1 
THREAD #2:  Facility ABS:  ABS_SLS_APPEND_FAILED, Failed to append to volume set via SLS 
THREAD #2:     Line = 7406, File = RESD$:[SRC]SLS_SERVICES.C;1 
THREAD #2:  Facility ABS:  ABS_SLS_APPEND_FAILED, Failed to append to volume set via SLS 
THREAD #2:     Line = 4295, File = RESD$:[SRC]SLS_SERVICES.C;1 
THREAD #2:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block 
THREAD #2:     %SLS-E-NOTALLOCD, specified volume not allocated to requestor 
THREAD #2:  Enter "YES" when ready:  
COORDINATOR:  Retiring volume set ALX110 (due to fatal error during save)
COORDINATOR:  Dismounting volume set member: ALX110 RVN 1
THREAD #2:  Facility ABS:  ABS_SYSALLOC_FAILED, Failed to allocate device 
THREAD #2:     Line = 1563, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1 
THREAD #2:  Facility ABS:  ABS_SYSALLOC_FAILED, Failed to allocate device 
THREAD #2:     Line = 1307, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1 
THREAD #2:  Facility ABS:  ABS_SYSALLOC_FAILED, Failed to allocate device 
THREAD #2:     Line = 7971, File = RESD$:[SRC]SLS_SERVICES.C;1 
THREAD #2:  Facility ABS:  ABS_SYSALLOC_FAILED, Failed to allocate device 
THREAD #2:     Line = 2284, File = RESD$:[SRC]SLS_SERVICES.C;1 
THREAD #2:  Facility ABS:  ABS_SYSALLOC_FAILED, Failed to allocate device 
THREAD #2:     Line = 1226, File = RESD$:[SRC]TAPE_OPERATIONS.C;1 
THREAD #2:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block 
THREAD #2:     %SYSTEM-W-DEVALLOC, device already allocated to another user 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Facility ABS:  ABS_IN_CSD, node is within the Central Security domain 
THREAD #2:     Line = 1919, File = RESD$:[SRC]SECURITY_UTILITIES.C;1 
THREAD #2:  Failed to allocate device 
COORDINATOR:  Skipping $1$MUA140: to End of Tape...
COORDINATOR:  Dismounting volume set member: ALX110 RVN 1
COORDINATOR:  Failed to access Storage Class
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Failed to extend Storage Class
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 1309, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 801, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 704, File = RESD$:[SRC]COORD_ARCHIVE_MANAGEMENT.C;1
COORDINATOR:  Facility ABS:  ABS_ARCHIVE_ACCESS_FAILED, Failed to access Storage Class
COORDINATOR:     Line = 469, File = RESD$:[SRC]ARCHIVE_FILE_SYSTEM.C;1
COORDINATOR:  Facility ABS:  ABS_SYSSKIPFILE_FAILED, SYS$QIOW with IO$_SKIPFILE failed
COORDINATOR:     Line = 1717, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SYSSKIPFILE_FAILED, SYS$QIOW with IO$_SKIPFILE failed
COORDINATOR:     Line = 4819, File = RESD$:[SRC]SLS_SERVICES.C;1
COORDINATOR:  Facility ABS:  ABS_SYSSKIPFILE_FAILED, SYS$QIOW with IO$_SKIPFILE failed
COORDINATOR:     Line = 540, File = RESD$:[SRC]TAPE_OPERATIONS.C;1
COORDINATOR:  Facility ABS:  ABS_PLATFORM_SPECIFIC_ERROR, Platform-specific error in diag block
COORDINATOR:     %SYSTEM-F-VOLINV, volume is not software enabled
%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000020, PC=005E70D4, PS=0000001B
Exception                          Module                                   Line
Exception Reraised by:             COORDINATOR                               995
exception                          COORDINATOR                               908
COORDINATOR:  Final status is Unexpected exception in Coordinator
%SYSTEM-F-OPINCOMPL, operation is incomplete

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

  problem : 
     How to automatic completed save operation for more than one volume ?
!
!    PS.: By the way .. the best way to read the status block in the
!    	 logfiles is from backwards. The last line is the most important
!    	 one. 
! 
  Q: How to get --> .. the best way to read the status block in the logfiles 
                       is from backwards. The last line is the most important

     best regards
     mtlee

    Hi!
    
    I've got some sugestions for you
    
    1) we made very good experiances with running ABS from the
       ABS account only (owner of all SC,EE,SR,RR + used for 
       all ABS interactions). You will avoide some problems
       by doint so
    2) There is no media location entered in the SC. 
    3) The output of the show of the SC shows no value
       for "volume set name". You havent listed the show storageclass
       command .. did you do a show with a "*" ? It is a known problem
       that using wildcards comes up with some emty fields.
    
       If the first tape of the volumeset is written (which seams so from
       the logfile) the volume set name field MUST NOT be empty.
    
    Have you entered some volumes to the SC by hand? You shouldn't do
    so! ABS builds up its volume set list by itself. The only thing
    ABS needs is a filled tape pool. All listed volume names in the
    SC (should be max 3 with streams = 3) stand for one volume set.
    The volumeset is named after the first tape of the set and the
    name isn't changed. So there is no direct way to find out which
    is the actual tape of the volume set shown there.
    
    The most important point when troubleshooting ABS is to lookout
    for OPERATOR REQUESTS ?
    
    How is your overall status? Works ABS without problems with
    other save requests? 
    
    I hope I could help somewhat
    
    							Michael