cabec
ADSM.ORG Member
Hello @all.
I'm a little bit frustrated, because I don't understand the following phenomenon and Google didn't show me a solution (some topics found were not helpful).
After a disk crash, TSM doesn't come up any more. It complains:
ANR0900I Processing options file dsmserv.opt.
ANR7811I Direct I/O will be used for all eligible disk files.
ANR0990I Server restart-recovery in progress.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.06.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.12.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.07.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.08.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.09.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.10.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.11.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.01.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.02.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.03.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.04.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.05.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/log_rootvg.01.
A file or directory in the path name does not exist.
ANR0259E Unable to read complete restart/checkpoint information from any database or recovery log volume.
The files mentioned are our primarie database volumes. But we have 2 additional dbcopy volumes coming via NFS. These are r/w mounted and accepted by TSM, becuase when theses directories are not mounted, TSM also complains these.
I edited the dsmserv.dsk and eliminated all /home/tsm/db_rootvg/db_rootvg* entries, but since TSM keeps track of the databse volumes inside, these files are marked as needed when the existing database vlumes are found during startup.
What I don't understand is: Why do I create these dbcopies when TSM doesn't start if one dbcopy is deleted? Then I don't need this stuff. Were are ma mistakes in thinking?
Nevertheless all other stuff like volume history, device configuration, incremental and full database backups are available. Is the only solution to do a restore of the databse with creating new empty database volumes via dsmfmt?
Waht will happen, when I do create the missing files with the same size and name again via dsmfmt and then just try to restart the TSM server? Will the new ones be marked as staled or offline? I don't want to play too much around with this before grabbing all informations I can get.
Thx for any help,
Carsten
PS: Please don't mind my mistakes/bad english. Hopefully things came over clearly enough to be understood.
I'm a little bit frustrated, because I don't understand the following phenomenon and Google didn't show me a solution (some topics found were not helpful).
After a disk crash, TSM doesn't come up any more. It complains:
ANR0900I Processing options file dsmserv.opt.
ANR7811I Direct I/O will be used for all eligible disk files.
ANR0990I Server restart-recovery in progress.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.06.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.12.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.07.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.08.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.09.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.10.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.11.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.01.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.02.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.03.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.04.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/db_rootvg.05.
A file or directory in the path name does not exist.
ANR7807W Unable to get information for file /home/tsm/db_rootvg/log_rootvg.01.
A file or directory in the path name does not exist.
ANR0259E Unable to read complete restart/checkpoint information from any database or recovery log volume.
The files mentioned are our primarie database volumes. But we have 2 additional dbcopy volumes coming via NFS. These are r/w mounted and accepted by TSM, becuase when theses directories are not mounted, TSM also complains these.
I edited the dsmserv.dsk and eliminated all /home/tsm/db_rootvg/db_rootvg* entries, but since TSM keeps track of the databse volumes inside, these files are marked as needed when the existing database vlumes are found during startup.
What I don't understand is: Why do I create these dbcopies when TSM doesn't start if one dbcopy is deleted? Then I don't need this stuff. Were are ma mistakes in thinking?
Nevertheless all other stuff like volume history, device configuration, incremental and full database backups are available. Is the only solution to do a restore of the databse with creating new empty database volumes via dsmfmt?
Waht will happen, when I do create the missing files with the same size and name again via dsmfmt and then just try to restart the TSM server? Will the new ones be marked as staled or offline? I don't want to play too much around with this before grabbing all informations I can get.
Thx for any help,
Carsten
PS: Please don't mind my mistakes/bad english. Hopefully things came over clearly enough to be understood.