Jack, it sounds like you are running an unsupported server version, so
getting formal support may be difficult.

Are your database volumes mirrored? If so, TSM tries to read the correct
page from a mirror.

The wisdom of other posts on this subject is worthwhile. Barring that, you
are probably looking at a database restore or dump/load/audit scenario.
Hopefully you back up your database daily, and even better, run the
recovery log in "roll forward" mode.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Coats, Jack" <Jack.Coats AT BANKSTERLING DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/31/2003 11:35
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: URGENT: TSM database problem


Thanks Brian.
        The volume it is on is a RAID5 volume and yes, it is till
accessable.
        No changes were made to the database.

        Earlier today I got some messages indicating that the 'server is
out
        of space'.  The recovery log was at 103% of its available size.  I
added
        space to the recovery log today.

        I did reboot.

        The same error occurred after the reboot when I tried to take a
        full backup of the database. ... Bummer.

        Everything else seems to be working OK.

I have a sev1 problem open with IBM now. ... We'll see what happens.

... Jack

-----Original Message-----
From: ZENG Brian (800043) [mailto:brian.zeng AT TORSDC DOT CA]
Sent: Wednesday, December 31, 2003 11:03 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: URGENT: TSM database problem


1. Check hw status of DB4.DBV and see if the hard disk still visible to
the
TSM Server
2. Any recent change to your TSM DB in terms of the disk pool
configuration?
3. If HW OK and no recent change, try to re-boot your TSM Server

Good luck,
Brian

-----Original Message-----
From: Coats, Jack [mailto:Jack.Coats AT BANKSTERLING DOT COM]
Sent: Wednesday, December 31, 2003 11:59 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: URGENT: TSM database problem
Importance: High


12/31/2003 10:45:58   ANR0207E Page address mismatch detected on database
volume
                       D:\TSMDATA\SERVER1\DB4.DBV, logical page 2980223

                       (physical page 160383); actual: 2973949.

12/31/2003 10:45:58   ANR9999D iccopy.c(1586): ThreadId<28> Unable to read
from
                       db volume.

I have TSM 4.3.3 on Winders2K.  How can I recover from this problem on my
database?

... TIA ... Jack