2009-07-19 05:30:27 UTC
The Troubleshooting Guide in ASE11 and 12 used to have a section called
Encyclopedia of Tasks, and it included a section on loading the master
database from backup. It described a simple three-step process: restart the
database in single-user mode (with -m), issue a "load database master"
command, then restart the database in multi-user mode.
The Troubleshooting Guide in ASE15 seems to lack this section. Instead,
chapter 13 of the System Administration Guide describes a very complicated
procedure for recovering master, including rebuilding the master device and
all the databases residing on it. It seems to make no mention of the simple
three-step process. (When I look back at the System Administration Guide for
ASE11 and 12, I see the same thing, though I never noticed that before.)
Furthermore, the -m option is called master-recover mode (even back in the
SAG for ASE11 and 12). However, the Utility Commands Reference in ASE15
still calls it single-user mode!
Today I have a master database that has gone slightly corrupt. The server
still runs, and dbcc reports that only one table is damaged (a messed up
page chain or something). I have a dump from yesterday, and I would like to
simply reload that dump into master. I have not made any recent changes in
master. In the past I would have simply used the three-step process to get
my database back.
My question is, can I use the old three-step method in ASE15, even though it
seems to have been removed from the manual? The new SAG seems to be saying
that when I start up in master-recover (-m) mode I will get some sort of
"generic" master database with a reset sa password, that I'll have to do
some stuff to before I can even load into it. [Does this have something to
do with the incorporation of buildmaster into dataserver?] I'm pretty sure
that in the old days when I started in single-user (-m) mode I'd see my
normal master database and could immediately load into it.
So, in my situation, when the master device is okay and all I want to do is
reload the master database, would it be true to say that there's now a
simple four-step process? Restart the database in master-recover mode
(with -m), update sysservers with my Backup Server info, issue a "load
database master" command, then restart the database in normal mode. It seems
like that should work, but I am nervous because it seems like something has
changed from what I'm accustomed to.
Another question: In older versions I'm pretty sure I could startup in -m
mode, then shutdown and startup without the -m, and my result would be just
exactly how I started. But the ASE15 System Administration Guide is
confusing, it implies that when you start in -m mode the master database
gets *overwritten* with some sort of generic master. Does that mean that if
you then restart without the -m, that your master database has been trashed?
The manual for dataserver doesn't make any mention of that, it just refers
to -m as "single-user" mode, like always. So what is with this "generic"
master that the SAG refers to?