Log Shipping Monitor problem
-
I am using SQL 2000 log shipping and have a problem with the monitor installed on the secondary server. After installation, everything was fine and the monitor was updating as expected.
We had an outage (no outage window was set) on the secondary server and afterwards part of the monitor has not updated. The names of the last file copied and loaded and the timestamps for both have not updated since the outage. Obviously the delta information is way off base. BTW, the last backup information stays current.
Further, the copy and load history shows the tlog backups are copied and loaded successfully on the secondary server and I can also confirm the successful restores from the sql log on the secondary server. I can see the tlog files in the shared folder on the secondary server.
I have found two KB articles(KB311177 & KB329133) but the suggestions listed do not apply. Anyone else seen this?
John Langston
Cimarex Energy Company
-
I have had the same issue with the log shipping monitor when there was a huge number of changes that occurs on the primary data base (i.e. a massive data conversion or a massive table update - which does not occur very often:whistling
. I noted that even though the logs was being transported and restored successfully, the log monitor will not update properly and always show that it is out of sync.My solution would be to redo the log shipping definition (in other words, start over) for each of the databases effected. At least Microsoft included a wizard in the enterprise version of SQL 2000 to make setting up a little easier.
-
Mike,
That is exactly where I am headed...this weekend to be exact.
John Langston
Cimarex Energy Co.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply