Well, let's see;
1) db2diag.log is in the DIAGPATH which is specified in your dbm cfg; that's
instance level and shouldn't be lost as it is not part of any db's. It's
owned by the instance.
2) event logs are db owned and should be found in the database path where
the db was created, in the db2event directory, (their name is 00000000.evt,
00000001.evt, ...) They are generated only if you ran event monitors and
did not specify a target path for the files. They have absolutely nothing to
do with the db's existence and behavior.
3) db2.log is generated by the install process (new or fixpacks). Mine is
20+ MB in size as I've kept it for a long time. It reports installation
events and would not tell you anything about the db "disappearing".
4) db2rhist.asc reports backup, restore, rollforward at the db or tblspc
level as well as all tablespace commands(create, alyter, quiesce, ...). It
also reports other stuff about db object usage but nothing about create or
drop of a db or its "appearance"!
Are you on Windows or ??
If on windows and you know the instance name (most likely DB2 if you did not
create your own).
On the drive where DB2 is installed there will be the following path:
X:\DB2\NODE0000\SQLDBDIR
There's a file with binary contents in there called SQLDBDIR, min looks like
this:
DB2 DIRECTORY
..............................................SES. ...........................D:\DB2................. ....SES
2SQL00001
plus a lot of binary junk I can't copy in the note.
It tells me that the SES database is in that path in SQL00001.
I now know it exists.
Try on a command line:
db2 uncatalog db <dbname>
db2 catalog db <dbname> on drive X where X is where you found your db.
If it comes back and tells you it did not find it, most likely, someone(?)
erased the actual directory and you are totally out of luck if you have no
backup.
HTH, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<jo***@yahoo.com> a écrit dans le message de news:
11**********************@g14g2000cwa.googlegroups. com...
other than the db2diag.log, you can also take a look at the event logs
(if you have any. they should be residing on the same directory as
db2diag.log). To format the event log, you may need to use the utility
like db2evmon??
history file would tell you info about backup and restore. db2 log
tells you database activity (which should not include information about
how a database is lost or crashed).
