hi

i got this info from db2diag.log

2009-11-18-13.13.59.287926-330 E505379174C405 LEVEL: Warning
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-362 APPID: *LOCAL.SCHNAM.091118184355
FUNCTION: DB2 UDB, data protection, sqlufrol, probe:8180
MESSAGE : ADM1611W The rollforward recovery phase has been completed.

2009-11-18-13.17.22.636528-330 E505379580C461 LEVEL: Error (OS)
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, oper system services, sqloexec2, probe:2
CALLED : OS, -, unspecified_system_function
OSERR : ENOENT (2) "A file or directory in the path name does not exist."

2009-11-18-13.17.22.647536-330 E505380042C457 LEVEL: Error (OS)
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, oper system services, sqloexec2, probe:2
CALLED : OS, -, unspecified_system_function
OSERR : EBADF (9) "A file descriptor does not refer to an open file."

2009-11-18-13.17.22.883103-330 I505380500C506 LEVEL: Warning
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, PSM - SQL Procedure, psm_recover_all_procs, probe:10
MESSAGE : SQL procedure executables recovery has been initiated.
DATA #1 : Hexdump, 8 bytes
0x2FF14E10 : 5544 494E 4736 3034 SCHNAM

2009-11-18-13.17.22.896518-330 E505381007C457 LEVEL: Error (OS)
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, oper system services, sqloexec2, probe:2
CALLED : OS, -, unspecified_system_function
OSERR : EBADF (9) "A file descriptor does not refer to an open file."

2009-11-18-13.17.22.904888-330 E505381465C457 LEVEL: Error (OS)
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, oper system services, sqloexec2, probe:2
CALLED : OS, -, unspecified_system_function
OSERR : EBADF (9) "A file descriptor does not refer to an open file."

2009-11-18-13.17.22.934316-330 I505381923C495 LEVEL: Warning
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, PSM - SQL Procedure, psm_recover_all_procs, probe:900
MESSAGE : SQL procedure executables recovery ended. RC:
DATA #1 : Hexdump, 4 bytes
0x2FF14DF4 : 0000 0000 ....

2009-11-18-13.22.52.130556-330 E505382419C440 LEVEL: Warning
PID : 48506 TID : 1 PROC : db2agent (SCHNAM) 0
INSTANCE: SCHNAM NODE : 000 DB : SCHNAM
APPHDL : 0-365 APPID: *LOCAL.SCHNAM.091118184655
FUNCTION: DB2 UDB, data management, sqldBeginIndexCreate, probe:1
MESSAGE : ADM5540W Beginning index rebuild of "1" indexes on table
"SCHNAM.TMAST".

after rollforward completed, the db started rebuild of index any suggest would be a great help
regds
Paul

as per the doc it says index can be invalid when fatal disk problem occurs
as per db2diag before starting rebuild of index is giving some OS error
is my predication correct
kindly suggest
regds
Paul

i mean prediction

Paul, you can go back to your own post and edit it if you want to change it. just click on Edit

Paul there are some possibilities for index rebuild. I am including the possibilities below.
The index rebuild depends on these parameters

indexrec - Index re-creation time configuration parameter
Configuration Type
Database and Database Manager


This parameter indicates when the database manager will attempt to rebuild invalid indexes, and whether or not any index build will be redone during DB2rollforward or HADR log replay on the standby database.

logindexbuild - Log index pages created configuration parameter

This parameter specifies whether index creation, recreation, or reorganization operations are to be logged so that indexes can be reconstructed during DB2rollforward operations or high availability disaster recovery (HADR) log replay procedures.

A crash in the index rebuild during a offline reorg or classic reorginzation phase means we already have the new object so nothing is redone. (As above, indexes are not rebuilt, but are marked invalid during crash recovery, and the database will follow the normal rules to determine when they are rebuilt, either at database restart or upon first access to the indexes.)

And I have some more questions for you Did you perform any offline reorg in your database? And did anything like database crash occured ?

Just need this to help you out further. I had similar issue but I resolved mine already. So just trying to give you some suggestions based on your input.


Thanks

actually this the develop server, we performed a offline reorg in prod server and the backup and logs were restored in the development server, in which the index was invalid as all the logs were applied, for the diag file its says that rebuilt of index on the table, the index which got corrupted but if in all the logs have been applied in the server how come the index became invalid
regds
Paul

I don't know, but just access the table with any select and db2 will rebuild the index if indexrec was set. have a look in infocenter for different settings