ADSM-L

Re: [ADSM-L] *EXTERNAL* Re: tsm/db2 won't start after boot drive crash/recovery

2016-09-14 08:21:58
Subject: Re: [ADSM-L] *EXTERNAL* Re: tsm/db2 won't start after boot drive crash/recovery
From: "Rhodes, Richard L." <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 14 Sep 2016 12:20:19 +0000
I found a db2nodes.cfg in the sqllib dir.  
The sqllib dir is NOT on rootvg so it wasn't lost.

  rssymapi2p:/tsmdata/tsmoc/config/sqllib==>cat db2nodes.cfg
  0 rssymapi2p 0

The instance was a fully good/running TSM/DB2 system, although all it ever did 
was run the OC hub.

For example, I found out about this cmd fighting a db2 problem some time ago.  

Running db2ilist returns nothing.
   ./db2ilist        (no output)
On other TSM instances db2ilist returns our DB2 owner. 


The doc you mentioned says to check /etc/services.
On a good/running TSM I find these:
  DB2_tsmuser     60000/tcp
  DB2_tsmuser_1   60001/tcp
  DB2_tsmuser_2   60002/tcp
  DB2_tsmuser_END 60003/tcp
They are missing on this system we recovered rootvg.  Will try adding them back 
in.



Rick





-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Loon, Eric van (ITOPT3) - KLM
Sent: Wednesday, September 14, 2016 7:42 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: *EXTERNAL* Re: tsm/db2 won't start after boot drive crash/recovery

Hi Richard!
Did you check the contents of the db2nodes.cfg file? It should contain the 
local host name of the TSM server.
You should also check if the instance is created successfully using the 
db2ilist command and also take a look at the following technote: 
http://www-01.ibm.com/support/docview.wss?uid=swg1IC67141
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Rhodes, Richard L.
Sent: dinsdag 13 september 2016 21:29
To: ADSM-L AT VM.MARIST DOT EDU
Subject: tsm/db2 won't start after boot drive crash/recovery

Hello,

We have a TSM v7.1.4 instance called TSMOC.  Its sole purpose in life is to run 
Operations Center.  It runs on an AIX lpar that's used for some other things.

Last Friday the AIX rootvg was lost during a live migration to a new storage 
system.  We decided to recover by installing a mksysb from a partner lpar which 
had the same AIX version and application version, but NOT TSM.  So the lpar got 
back up and running quickly - only took an hour, but it's missing the TSM 
install.  All the TSM instance files (dsmserv.opt, etc) and DB2 filesystems 
(data, logs, sqllib, etc) exist with all their data.  They weren't lost since 
they were on a different lun and volume group.

We installed TSM v7.1.4 and I then created the AIX db2 instance owner and 
group.  We then tried to start TSM.  We got msgs below.

ANR7801I Subsystem process ID is 16056324.
ANR0900I Processing options file /tsmdata/tsmoc/config/dsmserv.opt.
ANR7811I Using instance directory /tsmdata/tsmoc/config.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0172I rdbinst.c(3942): Error encountered performing action UPDATE DBM CFG.
ANR0162W Supplemental database diagnostic information:  -6031:**No State 
Information Available
(-2)**:-6031 (SQL6031N  Error in the db2nodes.cfg file at line number "0".  
Reason code "11".
).
ANR0171I dbiconn.c(1844): Error detected on 0:1, database in evaluation mode.
ANR0162W Supplemental database diagnostic information:  -1:08001:-1032 
([IBM][CLI Driver] SQL1032N  No start database manager command was issued.  
SQLSTATE=57019


I think I've got to tell db2 about the database that exists on disk.
We are going to call support, but figured I'd ask here first!

Any thought/comments are appreciated!

Rick


-----------------------------------------The information contained in this 
message is intended only for the personal and confidential use of the 
recipient(s) named above. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately, and delete the original message.
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        


-----------------------------------------
The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.