Crash Recovery (crash recovery) with AutoRestart parameters

The impact of this parameter setting has been experienced two times in the production system:
For the first time there is a set of less important systems installed on the virtual machine, and all applications of this system (DB2 was IHS) are configured to/etc/ rc.local, each boot machine will automatically pull up the application, and then a virtual machine down, after restarting to check that each application process starts normally, but the foreground page access exception is inaccessible, and then to the background to manually connect to the database report:
sql1015n the database is a inconsistent state. sqlstate=55025
According to sql1015n hint: need to execute restart Database dbname command, after execution, then databases can connect normally

The second is a set of HA server host power failure system switchover, after switching to the standby, check that the application is normally pulled up, but the foreground is inaccessible, and the first time is the same problem, the AutoRestart parameter is set off

This parameter is explained as follows:
If the DB2 database suffers a power outage or shuts down unexpectedly, the database does not shut down cleanly, then the database will be crash recovery when it is started. However, if the database parameter AutoRestart is set to OFF, DB2 does not crash RECOVERY after starting the database. About crash recovery, in the Db2diag.log log will have a relevant expression

This scenario is reproduced below:

[CPP]View Plaincopy

2. /* 1 set AutoRestart to OFF */
4. [Email protected] ~]$ DB2 UPDATE DATABASE CONFIGURATION for limtdb USING autorestart OFF IMMEDIATE
6. Db20000i the UPDATE DATABASE CONFIGURATION command completed successfully.
8. [[Email protected] ~]$ DB2 get DB cfg for limtdb|grep-i AutoRestart
10. Auto restart enabled (autorestart) = OFF
14. [Email protected] yunwei]$ DB2 connect to Limtdb
18. Database Connection Information
22. Database Server = db2/linuxx8664 10.1.0
24. SQL Authorization ID = Db2inst1
26. Local Database alias = Limtdb
30. /* 2 Insert a piece of data but not commit, for the database is inconsistent */
32. [[Email protected] yunwei]$ DB2 +c "INSERT into A values (15485, ' Asdas ', ' Asdas ')"
34. db20000i the SQL command completed successfully.
36. [Email protected] yunwei]$
38. /* 3 Kill database to simulate abnormal outage conditions */
40. [Email protected] yunwei]$ Ps-ef|grep Db2sys
42. Db2inst1 5287 5285 1 08:07 pts/1 00:00:04 DB2SYSC 0
44. Db2inst1 5827 3612 0 08:12 pts/1 00:00:00 grep db2sys
46. [Email protected] yunwei]$ kill-9 5287
48. /* 4 Start the database and the database does not crash recovery because AutoRestart is off */
50. [Email protected] yunwei]$
52. [Email protected] yunwei]$ Db2start
54. 12/19/2014 08:13:04 0 0 sql1063n db2start processing was successful.
56. SQL1063N Db2start processing was successful.
58. [Email protected] yunwei]$
60. [Email protected] yunwei]$
62. /* 5 Here the error is because the DB2BP process has not terminate */
64. [Email protected] yunwei]$ DB2 connect to Limtdb
66. SQL0752N connecting to a database are not permitted within a logical unit of
68. Work when the CONNECT type 1 setting are in use. sqlstate=0a001
70. [Email protected] yunwei]$ DB2 terminate
72. db20000i the TERMINATE command completed successfully.
74. /* 6 Report database inconsistency when starting again */
76. [Email protected] yunwei]$ DB2 connect to Limtdb
78. sql1015n the database is a inconsistent state. sqlstate=55025
80. /* 7 DB2? SQL1015N has one suggestion: using the RESTART DATABASE command*/
82. [Email protected] yunwei]$ DB2 restart database Limtdb
84. db20000i the RESTART DATABASE command completed successfully.
86. / * 8 database can be connected normally * /
88. [Email protected] yunwei]$ DB2 connect to Limtdb
92. Database Connection Information
96. Database Server = db2/linuxx8664 10.1.0
98. SQL Authorization ID = Db2inst1
100. Local Database alias = Limtdb
104. /* 9 The following is the setting AutoRestart to on the case of database downtime restart (no need to execute restart) */
106. [Email protected] yunwei]$
108. [Email protected] yunwei]$ DB2 UPDATE DATABASE CONFIGURATION for limtdb USING AutoRestart on IMMEDIATE
110. Db20000i the UPDATE DATABASE CONFIGURATION command completed successfully.
112. [Email protected] yunwei]$
114. [[Email protected] yunwei]$ DB2 get DB cfg for limtdb|grep-i AutoRestart
116. Auto restart enabled (AutoRestart) = On
118. [Email protected] yunwei]$
120. [Email protected] yunwei]$
122. [[Email protected] yunwei]$ DB2 +c "INSERT into A values (15485, ' Asdas ', ' Asdas ')"
124. db20000i the SQL command completed successfully.
126. [Email protected] yunwei]$ Ps-ef|grep Db2sys
128. Db2inst1 5870 5868 1 08:13 pts/1 00:00:03 DB2SYSC 0
130. Db2inst1 6122 3612 0 08:16 pts/1 00:00:00 grep db2sys
132. [Email protected] yunwei]$ kill-9 5870
134. [Email protected] yunwei]$ Db2start
136. 12/19/2014 08:16:35 0 0 sql1063n db2start processing was successful.
138. SQL1063N Db2start processing was successful.
140. [Email protected] yunwei]$ DB2 connect to Limtdb
142. SQL0752N connecting to a database are not permitted within a logical unit of
144. Work when the CONNECT type 1 setting are in use.
146. [Email protected] yunwei]$ DB2 terminate
148. db20000i the TERMINATE command completed successfully.
150. [Email protected] yunwei]$ DB2 connect to Limtdb
154. Database Connection Information
158. Database Server = db2/linuxx8664 10.1.0
160. SQL Authorization ID = Db2inst1
162. Local Database alias = Limtdb

Crash Recovery (crash recovery) with AutoRestart parameters