Re: DB2/TSM
2005-09-08 08:53:52
Will,
I subscribed to this list yesterday and my inbox has been
flooded with mail because people are sending to the wrong
e-mail address:
To send a message to all the people currently subscribed to the
list, just send mail to ADSM-L AT VM.MARIST DOT EDU. This is called "sending
mail to the list," because you send mail to a single address and
LISTSERV makes
copies for all the people who have subscribed. This
address
(ADSM-L AT VM.MARIST DOT EDU) is also called the "list address." You must
never try to send any command to that address, as it would be
distributed to all the people who have subscribed. All commands must
be sent to the "LISTSERV address," LISTSERV AT VM.MARIST DOT EDU (or
[email protected]).
I may have to unsubscribe, though I'm in the process of
installing Tivoli and had hoped the list would be useful.
-- Marc Robinson
10700 E. 350 Highway
Raytown, MO 64138
816-737-7725
-----Original Message-----
From: will aire [mailto:waire AT HOTMAIL DOT COM <mailto:waire AT HOTMAIL DOT
COM> ]
Sent: Thursday, September 08, 2005 7:31 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] DB2/TSM
Hello,
We have recently upgraded our DB2 database from fixpak 6 to fixpak 9,
and now we are unable to run DB2 backups. The backup command is " db2
backup db reg11db online use tsm", The error message is
"SQL2062N: An error occurred while accessing the media.
"/rmdata/REGION11/db2home/sqllib/adsm/libtsm.a" Reason code: "-53". ".
Also the db2 utility "db2adutl" would not run. We have restarted the
database and i have restarted tsm client but to no avail. I noticed that
fixpak9 had put some entries in /db2home/sqllib/db2profile. These
entries are set for DSMI variable and they overwrite the original
entries set for DSMI variables in the db2 instance owner's .profile i.e
/db2home/.profile.
db2profile is called from /db2home/.profile. The db2home/.profile was
altered by adding DSMI variables as the last entry in this profile. The
variables were set i.e path to tsm_config, dsm.opt, and tsm_logs, but
database backups are still failing
Any ideas please
Wil
|
|
|