ADSM-L

Re: oddevaix:/home/archive>db2 backup db archive online use tsm SQL2062N An error occurred while accessing media, Reason Code: "137"

2006-07-12 04:59:13
Subject: Re: oddevaix:/home/archive>db2 backup db archive online use tsm SQL2062N An error occurred while accessing media, Reason Code: "137"
From: IG Coolen <ilja.coolen AT ABP DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 12 Jul 2006 10:49:27 +0200
Hi Nancy,

I was just figuring this out yesterday. Had the same problem, until they
changed into reason code 184.
But this is what i figured out so far.

In order to do online backups, your logging configuration in DB2 should
be set to archive logging. But your DB2 admins will probably know about
this.

Next, make sure you setup all TSM_ (except TSM_PASSWORD) parameters in
the DB2 database to default.
Although i use PASSWORDACCESS generate, i had to set the nodes password
in the database config.

DB2>CONNECT TO <YOURDB>;
DB2>UPDATE DATABASE CFG USING TSM_PASSWORD <YOURPW> IMMEDIATE;
DB2>UPDATE DATABASE CFG USING TSM_NODENAME NULL IMMEDIATE;
DB2>UPDATE DATABASE CFG USING TSM_MGMTCLASS NULL IMMEDIATE;
DB2>CONNECT RESET;

When you set any of the other parameters to anything but NULL, DB2 tries
to apply them to the backupjob, which in return will fail. 

Have you rebooted the DB2 host, or restarted DB2 after setting the
DSMI_* vars?

Last, i would think that the DB2 user (or the user starting the backup
process) cannot read the file you mention (libtsm.a). My reason codes
137 never mentioned a file (It is on Windows though). Have you checked
the permissions on that file in relation to the active user?


Good Luck.

Gr. Ilja

 

-----Oorspronkelijk bericht-----
Van: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Namens Nancy
L Backhaus
Verzonden: dinsdag 11 juli 2006 20:14
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: oddevaix:/home/archive>db2 backup db archive online use tsm
SQL2062N An error occurred while accessing media, Reason Code: "137"

TSM Server 5.3.2.2
TSM DB2 Client 5.3.0.0
DB2 8.2.0


Trying to help our DB2 Admins get a backup.   I know very little about
DB2, so any help is appreciated.

What we have tried/verified:

We can run db2adutl from the client - it was successful

I  see in the 'Backing Up DB2 Using TSM' book, under troubleshooting
suggested for "137' error, is the incorrect password

We compared the .profile with another successful db2 client - that looks
correct, DSM_DIR DSMI_LOG, DSMI_DIR, and DSMI_CONFIG too.

Passwordgenerate set in the options file

Updated the node nodename password on the TSM Server, then regenerated
the password file with db2 command dsmapipw again.




ERROR:

DB2Node :/home/archive>db2 backup db archive online use tsm

SQL2062N  An error occurred while accessing media
"/home/archive/sqllib/adsm/libtsm.a".  Reason code: "137".





Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979

CONFIDENTIALITY NOTICE: This email message and any attachments are for
the sole use of the intended recipient(s) and may contain proprietary,
confidential, trade secret or privileged information.  Any unauthorized
review, use, disclosure or distribution is prohibited and may be a
violation of law.  If you are not the intended recipient or a person
responsible for delivering this message to an intended recipient, please
contact the sender by reply email and destroy all copies of the original
message.


=====DISCLAIMER=================================================================

De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor 
de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u 
contact op te nemen met de afzender per kerende e-mail. Verder verzoeken wij u 
in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan niemand 
openbaar te maken. Wij aanvaarden geen aansprakelijkheid voor onjuiste, 
onvolledige dan wel ontijdige overbrenging van de inhoud van een verzonden 
e-mailbericht, noch voor daarbij overgebrachte virussen.

The information contained in this e-mail is confidential and may be privileged. 
It may be read, copied and used only by the intended recipient. If you have 
received it in error, please contact the sender immediately by return e-mail; 
please delete in this case the e-mail and do not disclose its contents to any 
person. We don't accept liability for any errors, omissions, delays of receipt 
or viruses in the contents of this message which arise as a result of e-mail 
transmission.

De Stichting Pensioenfonds ABP is gevestigd te Heerlen en ingeschreven bij de 
Kamer van Koophandel Zuid Limburg onder nummer 41074000


<Prev in Thread] Current Thread [Next in Thread>