Is there a way to get the DDL for all the tables?
Thinking to use db2dart to dump necessary sysibm table,

Then recreate similar views
syscat.tables
syscat.views
syscat.columns
syscat.triggers
....
Compose DDL based on those views.

It is really a tedious work.

Any other suggestion?

"Anwei Shen" <shenanwei (AT) gmail (DOT) com> wrote

db2look command (see Command Reference manual)

db2look -d sample -e -a -l > sample.ddl

There are some other options if you also want statistics, etc.

Can you be a little bit more descriptive?

crash recovery failed. so what? are you able to connect to the database?
I'm sorry, how do you think somebody should help you w/o having any info?

What is the error message? What is your problem?

On 23.06.10 23:44 , Anwei Shen wrote:

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/

On Jun 24, 3:43*am, Helmut Tessarek <tessa... (AT) evermeet (DOT) cx> wrote:
db2 is crashed, no connection can be made even the db2look.
when you connect, just give you simple system error.
in db2diag.log, it said crash recovery failed.

Hi Anwei,

db2look won't work, since it has to connect to the database and bind a package
to the db.

The only way for you now is using db2dart and dump the data somehow to disk.

BUT:
If you have a support contract, you can open a PMR with IBM support and
explain your situation. There are ways to get a connection to the database,
but you will have to sign a disclaimer before support will do anything. It
will sat that the database might not be in a consistent state.

I'm sorry, there is nothing I can do. Or let's put it that way: my hands are
tied. You will have to contact support.

I don't know how to say it, so please forgive my blunt delivery:
Why the heck do you think there is a backup command?

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/

Here is some error message.

2010-06-23-12.38.11.725463-240 I4923E509 LEVEL: Error
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:621
MESSAGE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
"Page number exceeds max -8100"
DIA8709E Segmented table page number was too high.

2010-06-23-12.38.11.725720-240 I5433E511 LEVEL: Severe
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data management, sqldRedo, probe:6265
RETCODE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
"Page number exceeds max -8100"
DIA8709E Segmented table page number was too high.

2010-06-23-12.38.11.725977-240 I5945E510 LEVEL: Severe
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data management, sqldmrdo, probe:780
RETCODE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
"Page number exceeds max -8100"
DIA8709E Segmented table page number was too high.

2010-06-23-12.38.11.726196-240 I6456E486 LEVEL: Severe
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data management, sqldmrdo, probe:780
MESSAGE : Error during REDO of LSN:
DATA #1 : Hexdump, 6 bytes
0x000000024B35FD9A : 0074 B884 9C4C .t...L

2010-06-23-12.38.11.726371-240 I6943E499 LEVEL: Severe
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, data management, sqldmrdo, probe:780
MESSAGE : Error during REDO of log record:
DATA #1 : Hexdump, 12 bytes
0x000000024B35FDF0 : 0167 0200 0400 0000 0988
0001 .g..........

2010-06-23-12.38.11.726547-240 I7443E576 LEVEL: Error
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, recovery manager, sqlpRecDbRedo, probe:155
MESSAGE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
"Page number exceeds max -8100"
DIA8709E Segmented table page number was too high.
DATA #1 : <preformatted>
REDO failed on LSN 00000074B8849C4C

2010-06-23-12.38.11.726773-240 I8020E651 LEVEL: Error
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, recovery manager, sqlpRecDbRedo, probe:160
DATA #1 : Hexdump, 32 bytes
0x000000024B35FDA8 : 0C00 0000 5200 0000 0000 0000 0000
0000 ....R...........
0x000000024B35FDB8 : 0A85 62C4 0000 0000 0000 0000 0000
0000 ..b.............
DATA #2 : Hexdump, 12 bytes
0x000000024B35FDF0 : 0167 0200 0400 0000 0988
0001 .g..........

2010-06-23-12.38.11.726932-240 I8672E517 LEVEL: Error
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, recovery manager, sqlpPRecProcLog, probe:250
RETCODE : ZRC=0x84020009=-2080243703=SQLB_RC_PG_NUM_ERR
"Page number exceeds max -8100"
DIA8709E Segmented table page number was too high.

2010-06-23-12.38.11.727114-240 I9190E655 LEVEL: Error
PID : 23864 TID : 47931742066512PROC : db2redow
(REPORTER) 0
INSTANCE: db2inst1 NODE : 000 DB : REPORTER
APPHDL : 0-545 APPID: AC1084CA.F44C.16170C260BA9
AUTHID : DB2INST1
FUNCTION: DB2 UDB, recovery manager, sqlpPRecProcLog, probe:250
MESSAGE : qEntry for 00000074B8849C4CentryFlags 5 queueId 13
waitOthers 0x24b1e4d60 numBlocked 1 lrHeader:
DATA #1 : Hexdump, 32 bytes

Hi Anwei,

As I have already mentioned before, my hands are tied. You will have to open a
PMR with IBM support.

On 28.06.10 18:23 , Anwei Shen wrote:

--
Helmut K. C. Tessarek
DB2 Performance and Development

/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/