Hello,

I am using "DB2 v9.1.0.1" on SunOS.

Facing a problem in db2start.

-bash-3.00$ db2start
07/04/2008 11:55:07 0 0 SQL1042C An unexpected system error occurred.
SQL1032N No start database manager command was issued. SQLSTATE=57019
-bash-3.00$


i tried db2iupdt, but it doesn't worked.

What should i do??

Have u check the db2comm parameter and other instance settings ?

Just send all the results of db2set -i command ......

I get it. "DB2DBMSADDR" was set to "ON"... which i think was wrong.

-bash-3.00$
-bash-3.00$ db2set -i
DB2DBMSADDR=ON
DB2COMM=tcpip
-bash-3.00$
-bash-3.00$

I reset its value
i.e. -bash-3.00$ db2set DB2DBMSADDR=

Now db2start is successful!! Thanks!

But now am getting another problem: cannot connect to database!

-bash-3.00$ db2 connect to sample
SQL1042C An unexpected system error occurred. SQLSTATE=58004
-bash-3.00$

after checking the log, i found: database is marked BAD!!


2008-07-04-12.24.55.587714 Instance:db2inst1 Node:000
PID:4278(db2star2) TID:1 Appid:none
base sys utilities DB2StartMain Probe:911

ADM7513W Database manager has started.

2008-07-04-12.26.00.413273 Instance:db2inst1 Node:000
PID:4395(db2agent (SAMPLE) 0) TID:1 Appid:*LOCAL.db2inst1.080704065557
base sys utilities sqleMarkDBad Probe:10

ADM7518C "SAMPLE " marked bad.

Execute this one and check ur tablespace states
list tablespaces show detail

and also check ur table space containers

How can i check status of tablespaces, b'coz i am not even able to connect to database.

-bash-3.00$ db2 list tablespaces show detail
SQL1024N A database connection does not exist. SQLSTATE=08003
-bash-3.00$

Tell me have u performed any
backup or restore ?

Applying fix packs some times helps

No i haven't performed backup or restore.

I'd do some reading on db2dart in the Command Ref.....you should be able to inspect the tablespaces and see if there are problems and you don't need a connection

i tried db2dart... it is giving warning database is in inconsistent state.

bash-3.00$ db2dart sample /DTSF

Warning: The database state is not consistent.

Warning: Errors reported about reorg rows may be due to the inconsistent state of the database.
DB2DART Processing completed with warning(s)!


i also checked for all database [db2dart sample /db]
it gave "inspection phase start ....few lines......inspection phase end."
for all the objects in dart file. I think there is no problem with tblsps.

Please suggest. what to do next? or tell me if i have misinterpreted the dart file or if i have not used db2dart correctly.

Hi,

This seems to be like the Databse got corrupted.
try Decativating\activating database........same time tail the diag.log in other session and see anything useful. I strongly belive ur diag on activation will show u something useful...........Please share the infor from diag...........Thank U

Hello,
Sorry for being late at response."Activate db" command generated the following lines in db2diag.log file.
Here i illuminated few warnings b'coz of text limit.

2008-08-05-10.15.45.897202+330 I14791793E508 LEVEL: Warning
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqleCalculateDbHeaps, probe:95
MESSAGE : DATABASE_MEMORY cfg value too small, defaulting to (hex):
DATA #1 : Hexdump, 8 bytes
0xFFFFFD7FFFDE5B90 : F777 0000 0000 0000 .w......

2008-08-05-10.15.47.955211+330 I14793485E724 LEVEL: Error
PID : 11455 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
0xFFFFFD7FFFDFD2A8 : 2F65 7870 6F72 742F 686F 6D65 2F64 6232 /export/home/db2
0xFFFFFD7FFFDFD2B8 : 696E 7374 312F 6462 3269 6E73 7431 2F4E inst1/db2inst1/N
0xFFFFFD7FFFDFD2C8 : 4F44 4530 3030 302F 5351 4C30 3030 3032 ODE0000/SQL00002
0xFFFFFD7FFFDFD2D8 : 2F53 514C 4F47 4449 522F 5330 3030 3030 /SQLOGDIR/S00000
0xFFFFFD7FFFDFD2E8 : 3030 2E4C 4F47 00.LOG
2008-08-05-10.15.48.149636+330 I14794210E164 LEVEL: Error
PID:11455 TID:1 NODE:000 Title: SQLPG_XHDR
Dump File:/export/home/db2inst1/sqllib/db2dump/114551.000
2008-08-05-10.15.48.165555+330 I14794375E164 LEVEL: Error
PID:11455 TID:1 NODE:000 Title: SQLPG_XHDR
Dump File:/export/home/db2inst1/sqllib/db2dump/114551.000
2008-08-05-10.15.48.165678+330 I14794540E308 LEVEL: Error
PID : 11455 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-08-05-10.15.48.199877+330 I14794849E384 LEVEL: Error
PID : 11455 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.
2008-08-05-10.15.48.621150+330 I14795234E390 LEVEL: Error
PID : 11455 TID : 1 PROC : db2loggr (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgLoggrInit, probe:1150
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-08-05-10.15.48.621506+330 I14795625E163 LEVEL: Error
PID:11455 TID:1 NODE:000 Title: SQLP_DBCB
Dump File:/export/home/db2inst1/sqllib/db2dump/114551.000
2008-08-05-10.15.48.632428+330 I14795789E301 LEVEL: Severe
PID : 11455 TID : 1 PROC : db2loggr (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, data protection services, sqlpgasn, probe:4000
MESSAGE : Logging can not continue due to an error.
2008-08-05-10.15.48.633012+330 I14796091E471 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data protection services, sqlpgint, probe:9030
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-08-05-10.15.48.976513+330 I14796563E471 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data protection services, sqlpgint, probe:3600
RETCODE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used"
DIA8414C Logging can not continue due to an error.
2008-08-05-10.15.49.002586+330 I14797035E424 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:120
DATA #1 : Hexdump, 4 bytes
0xFFFFFD7FFFDE5C34 : 0D00 1086 ....
2008-08-05-10.15.49.012318+330 I14797460E423 LEVEL: Error
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqledint, probe:120
DATA #2 : Hexdump, 4 bytes
0xFFFFFD7FFFDE5C34 : 0D00 1086 ....
2008-08-05-10.15.49.298965+330 E14797884E374 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:10
MESSAGE : ADM7518C "SAMPLE " marked bad.
2008-08-05-10.15.49.764773+330 I14798259E422 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:10
MESSAGE : DIA0505I Execution of a component signal handling function has begun.
2008-08-05-10.15.49.794029+330 I14798682E174 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** DRDA ASCB ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.807883+330 I14798857E179 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** DRDA CMNMGR CB ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.816584+330 I14799037E179 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** RECEIVE BUFFER ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.816699+330 I14799217E177 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** SEND BUFFERS ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.816790+330 I14799395E182 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** CONNECTION HANDLE ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.817212+330 I14799578E180 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** DRDA ATTRIBUTES ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.817306+330 I14799759E179 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: **** AS UCINTERFACE ****
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.817396+330 I14799939E435 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:20
MESSAGE : DIA0506I Execution of a component signal handling function is
complete.
2008-08-05-10.15.49.817548+330 I14800375E167 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_AGENTCB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.817715+330 I14800543E175 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.817824+330 I14800719E164 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_DBCB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.818327+330 I14800884E173 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_MASTER_APP_CB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.818543+330 I14801058E166 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_APP_CB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.818702+330 I14801225E174 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_COORDINATOR_CB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.818802+330 I14801400E169 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: REPLY_NODE_MAP
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.818893+330 I14801570E172 LEVEL: Severe
PID:12313 TID:1 NODE:000 Title: SQLE_APP_GROUP_CB
Dump File:/export/home/db2inst1/sqllib/db2dump/123131.000
2008-08-05-10.15.49.842641+330 I14801743E432 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (SAMPLE) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqleFirstConnect, probe:100
DATA #1 : Hexdump, 4 bytes
0xFFFFFD7FF8B9A8EC : EEFB FFFF ....
2008-08-05-10.15.49.915791+330 I14802176E471 LEVEL: Severe
PID : 12313 TID : 1 PROC : db2agent (idle) 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-394 APPID: *LOCAL.db2inst1.080805044544
AUTHID : DB2INST1
FUNCTION: DB2 UDB, base sys utilities, sqlescln, probe:24
DATA #1 : String, 22 bytes
sqlm_d_exit is failed.
DATA #2 : Hexdump, 4 bytes
0xFFFFFD7FFFDE592C : 0100 0000 ....