I've looked over the log file but no one here speaks db2.........
David Tyree
System Administrator
South Georgia Medical Center
229.333.1155
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Loon, EJ van (ITOPT3) - KLM
Sent: Tuesday, November 18, 2014 03:43
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] corrupted db on test system
Hi David!
I think so too. Did you check the db2diag.log for additional messages?
Otherwise It might be a good moment to open a PMR...
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tyree, David
Sent: maandag 17 november 2014 16:38
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: corrupted db on test system
Since Friday afternoon.
I'm pretty sure it should be done by now...
David Tyree
System Administrator
South Georgia Medical Center
229.333.1155
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Loon, EJ van (ITOPT3) - KLM
Sent: Monday, November 17, 2014 10:27
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] corrupted db on test system
Hi David!
Sql code 1117 means SQLE_RC_ROLLFWD_PEND ( -1117 ). From the message manual:
SQLE_RC_ROLLFWD_PEND ( -1117 ) indicates a database Roll Forward operation is
pending and must complete before activating the database. After the Roll
Forward recovery step is complete, the database can be activated by starting
the server.
How long are you waiting?
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tyree, David
Sent: maandag 17 november 2014 15:06
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: corrupted db on test system
I guess I'm further along but after I got the database restored I tried to
restart the TSM box and it's not coming up.
I'm getting:
ANR0238E A database recovery task is prohibiting activation of TSMDB1 with
sqlcode -1117.
Not much success getting an idea what that actually means...
Any suggestions?
David Tyree
System Administrator
South Georgia Medical Center
229.333.1155
-----Original Message-----
From: Tyree, David
Sent: Thursday, November 13, 2014 16:23
To: 'ADSM: Dist Stor Manager'
Subject: RE: corrupted db on test system
I manually put the tape in the library and then did some hacking around in the
devconfig file to tell TSM just where the tape was.
Fired off the restore db command again and I saw the library mount the correct
tape.
Now I'm seeing a db restore running so I think I'm in business now.
I understand that a db restore takes about 2 to 3 times as long as a db backup
so it should finish in about 3 hours or so...
Thanks for pointing me in the right direction.
David Tyree
System Administrator
South Georgia Medical Center
229.333.1155
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Thomas Denier
Sent: Thursday, November 13, 2014 15:46
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] corrupted db on test system
----David Tyree wrote-----
We are running TSM v6.3.1 on a test box and we had a drive fail
and it has a corrupted database now and won't start.
I did the "dsmserv remove db tsmdb1" to get rid of the old
database and now I'm about to start the actual database restore.
While I was waiting for the offsite database backup tape to be
brought back onsite I issued the "dsmserv restore db" to see what would happen.
It failed like I expected because it couldn't find the tape in the library.
At least it's seeing the library and all the drives.
My question is how do I check in that tape to the library?
I can physically put the tape in the library but until TSM knows that it's
actually checked in I'm stuck.
TSM won't see it until it's checked in but TSM is down.
How would I be able to read that tape once I get it on site?
The restore process gets all its information about tape volumes from the volume
history file and possibly the device configuration file.
One approach recommended by some TSM sites is to use a device configuration
file modified to show a manual library and then use a library control utility
to mount the tape when requested.
If you want to use a device configuration files that shows the actual library
type, the process depends on the type of library.
For a SCSI library you would need to get the tape into the library and add a
volume location record for the volume to the device configuration file.
For a 3494 I think you would just need to put the volume in the library and use
a library control utility to set the category appropriately.
Thomas Denier
Thomas Jefferson University Hospital
The information contained in this transmission contains privileged and
confidential information. It is intended only for the use of the person named
above. If you are not the intended recipient, you are hereby notified that any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact the
sender by reply email and destroy all copies of the original message.
CAUTION: Intended recipients should NOT use email communication for emergent or
urgent health care matters.
********************************************************
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
********************************************************
********************************************************
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
********************************************************
|
