有時候LOG壞了或者丟了，APPLY LOG出了ABEND,NORMAL RESTART ABEND 或者 HUNG住了，在正常RESTART 不能正常work的情況下，只能上COLD RESTART, COLD RESTART不到萬不得已，一定不能使用，因爲即使在DB2 RESTART之後,DB2仍然可能出在inconsistent狀態。
執行COLD RESTART DB2之前，除了做COLD RESTART的member,其他所有member都要關掉。COLD RESTART一定要用ACCESS(MAINT)啓動DB2,再解決了所有的inconsistencises後，再正常啓動DB2(WITHOUT ACCESS(MAINT))
• Stop all other members of the data sharing group, except the one needs to do cold start.
• Cold start the member using ACCESS (MAINT), after resolving the data inconsistencies,
restart without ACCESS (MAINT).
COLD RESTART步驟：
Run DSNJU004 to print BSDS
• Find the RBA for the most recent CHECKPOINT
• Run DSN1LOGP with SUMMARY(ONLY) from the last begin checkpoint to the end of the log
• Find the RBA/LRSN of the last log records has been written, then round up to the next CI as the cold start RBA
寫的最後一個LOGRBA是00000000000052BCA310，入到下一個CI就是00000000000052BCB000
• Get the incomplete URs list and pending write list from summary report, the object accessed by these incomplete URs need to be recovered.
在EC上，暫時沒法構造一個incomplete的UR,所以即使是ignore這個TS後，數據仍然是consistent的。但是如果是這一段log客戶丟了，沒法正常RESTART,那麼繞過這段LOG去做COLD RESTART就能在不apply log的情況下把DB2啓起來，DB2就會處於inconsistent的狀態。
• DSNJU003 to create CRCR using RBA from DSN1LOGP.
