I am using db2 9.1 on SunOS.

When i activate database it gives error:
SQL1042C An unexpected system error occurred. SQLSTATE=58004

And following error msgs are generated in db2diag.log


2008-11-26-13.14.46.698818+330 I514338E724 LEVEL: Error
PID : 12771 TID : 1 PROC : db2loggr (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgolf, probe:570
MESSAGE : Extent headers have Chk1 6 and 0, FileName:
DATA #1 : Hexdump, 70 bytes
0xFFFFFD7FFFDFD1F8 : 2F65 7870 6F72 742F 686F 6D65 2F64 6232 /export/home/db2
0xFFFFFD7FFFDFD208 : 696E 7374 312F 6462 3269 6E73 7431 2F4E inst1/db2inst1/N
0xFFFFFD7FFFDFD218 : 4F44 4530 3030 302F 5351 4C30 3030 3032 ODE0000/SQL00002
0xFFFFFD7FFFDFD228 : 2F53 514C 4F47 4449 522F 5330 3030 3030 /SQLOGDIR/S00000
0xFFFFFD7FFFDFD238 : 3030 2E4C 4F47 00.LOG

2008-11-26-13.14.46.700767+330 I515063E164 LEVEL: Error
PID:12771 TID:1 NODE:000 Title: SQLPG_XHDR
Dump File:/export/home/db2inst1/sqllib/db2dump/127711.000

2008-11-26-13.14.46.701063+330 I515228E164 LEVEL: Error
PID:12771 TID:1 NODE:000 Title: SQLPG_XHDR
Dump File:/export/home/db2inst1/sqllib/db2dump/127711.000

2008-11-26-13.14.46.701190+330 I515393E308 LEVEL: Error
PID : 12771 TID : 1 PROC : db2loggr (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgole, probe:1710
MESSAGE : Error -2045771763 opening database log extent 0:

2008-11-26-13.14.46.701316+330 I515702E384 LEVEL: Error
PID : 12771 TID : 1 PROC : db2loggr (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgicl, probe:2130
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.



The problem seems with the file "/export/home/db2inst1/db2inst1/NODE0000/SQL00002/SQLOGDIR/S0000000.LOG" & with the process db2loggr.
But i don't undrstand what is need to read(deal with) transaction log file while activiting a database even though the database is in circular logging mode (LOGARCHMETH1 is OFF).

Can anybody help me to understand the internal process when we activate the database?

Can you tell me before running the ACTIVATE command, what was done in the database. Anything special you would like to mention? Looking into the ZRC code from the diag.log, it seems the Logs are corrupted.

Yes, earlier I had tried the tablespace level restore which was not successful. finally i restored full db.

Hi,
Is it SAMPLE database that got corrupted? In that case, you again reinstall the SAMPLE (db2 default db).

If the above assumption is wrong, then you can try the following. IBM SUPPROT recommended:

"If the log file DB2 is trying to open is empty (as
it would be if you are activating the database after a clean
shutdown), then you can move the log out of the active log path
into another directory that DB2 will not access and reissue the
connect. You should not delete the log though because it is
never safe to delete log files."

Hi,
Yes you are right, its a sample db. This problem occured twice. I am trying to learn the things which may help me in real working environments.

If IBM support is only the solution, Then i will leave it; otherwise i will try 4 the sol.

Removing the logs does't worked. So i placed them again.

db2 SAMPLE database can be recreated using the command. If path is not specified the db will be created in the path specified by the DFTDBPATH database manager configuration parameter