1. Community Tip: Please Give Thanks to Those Sharing Their Knowledge.
    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.
  2. Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)
    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Unable to start instance (username and/or password invalid)

Discussion in 'TSM Operation' started by sandragon, Aug 28, 2017.

  1. sandragon

    sandragon ADSM.ORG Member

    Joined:
    Aug 26, 2014
    Messages:
    52
    Likes Received:
    0
    Our TSM instance began acting oddly today and was having issues unlocking tape devices, reporting they were in use when they were not, etc.
    We halted the instance to run diags on the tapes, found nothing, so tried to start again. No changes have been made to the system, but I am getting this error:
    Code:
    ANR7801I Subsystem process ID is 4653134.
    ANR0900I Processing options file /home/tsm01/tsminst1/dsmserv.opt.
    ANR7811I Using instance directory /home/tsm01/tsminst1.
    ANR4726I The ICC support module has been loaded.
    ANR0990I Server restart-recovery in progress.
    ANR0152I Database manager successfully started.
    ANR0162W Supplemental database diagnostic information:  -1:08001:-30082 ([IBM][CLI Driver] SQL30082N  Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").  SQLSTATE=08001).
    ANR1820E The server could not connect to the database manager by using TCP/IP port 51500.
    
    I can log in with the instance owner (tsm01) and run db2start without issue. I can connect to the database when I'm the instance owner, and using the instance owner's ID from another account (connect to tsmdb1 user tsm01 using [password]). I have a PMR open with IBM but we are hard down and I can't seem to find any indications of this kind of behavior before.
     
  2.  
  3. LED888

    LED888 ADSM.ORG Moderator

    Joined:
    Oct 15, 2002
    Messages:
    809
    Likes Received:
    62
  4. sandragon

    sandragon ADSM.ORG Member

    Joined:
    Aug 26, 2014
    Messages:
    52
    Likes Received:
    0
    I did run across that message. However, this is a single instance server.
     
  5. verpeaux

    verpeaux ADSM.ORG Member

    Joined:
    Sep 17, 2002
    Messages:
    3
    Likes Received:
    1
    If you installed the latest TSM client, it upgraded GSKit8 which seems uncompatible.

    You have to downgrade GSKit8 (and the client) or to upgrade the server to 8.1.2.
     
    BDMcGrew likes this.
  6. sandragon

    sandragon ADSM.ORG Member

    Joined:
    Aug 26, 2014
    Messages:
    52
    Likes Received:
    0
    I actually ended up identifying that with IBM as well. The technicians were largely unaware of this, it took a backline/T3 support agent to identify the error. They made that big of a change in GSK8 and the technote that talks about it is buried deep. Didn't come up at all when evaluating 8.1.2 client (we have the issue where 8.1.0 was identifying single or 2 level directory trees as being 'too big' with too many sub-directories.)
     
  7. BDMcGrew

    BDMcGrew ADSM.ORG Member

    Joined:
    Mar 9, 2015
    Messages:
    72
    Likes Received:
    1
    Thanks for the save verpeaux. Wish I'd found this last night because the error is quite ambiguous and a simple server restart to kick a library turned into 18 hours of downtime. And yes, I'd upgraded the client a few weeks ago just as your post suggests was the problem.

    Thanks again,

    -b
     

Share This Page