Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


Position of archive volumes in jukebox is incorrectly reported


Product

 
  • Brisque® Serve 4
  • Timna

Platform

 
  • 44P–170—Hammerhead
  • 6F1—Condor
  • F50

Operating system

 

IBM® AIX® 4.2.1, 4.3.3


Symptoms

 

The position of archive volumes in jukebox is incorrectly reported.


Solution

 

Perform the following steps:

  1. Check the SQLtrans.err log file for any database errors related to the inventory reporting. If there are related errors, run oncheck -cID directmgr -y.
  2. If errors are found, correct them.
  3. Using sdsm_out.sh ;mon.sh, open the reporting messages to your terminal.
  4. Run the problematic slot inventory via nwadmin or using the proper sequence (exactly as appears).
    For example: nsrjb -j jbx1 -I -f/dev/rmt0.1 -S4-4
    (refer to this Inventory document).
  5. Check if the reporting from managerLS to the database is correct. If not, proceed to step 6.
  6. Verify that the latest BS version is installed. Type:
    lslpp -l | grep Timna
    Timna.informix.obj 4.0.37.0 COMMITTED informix
    Timna.manager.obj 4.0.37.0 COMMITTED Timna manager
    lslpp -l | grep Upd
    Upd_BS4_FileTrak_OSX.obj 4.0.13.0 COMMITTED Upd_BS4_FileTrak_OSX
    Upd_Fiber_Channel.obj 4.0.17.5 COMMITTED "Update_Fiber_Channel"
    Upd_ZeroId_BS_4037.obj 4.0.37.1 COMMITTED Upd_ZeroId_BS_4037
  7. Use nsrwatch to verify that the latest Legato 6.1.3 version is installed.
  8. Verify that the /backup/bin/nsrjb script is correct. It should be:
    ls -la /backup/bin/nsrjb
    -rwxr-xr-x 1 root system 4996 Jun 18 2003 /backup/bin/nsrjb
  9. Use nsrjb -Cv to verify that Legato reflects the correct slot status. If it does not, try to remove the jukebox definition and recreate it. Then run the jukebox inventory, as explained in the Legato document.
  10. If the problem is still not resolved, there could be inconsistency in the database tables. Refer the problem to your database specialist.

Technical contact(s)
 

Lev Weissman

Submitted by
 

Lev Weissman

Date submitted
 

29 Sep 2005


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.