05 December,2010 by Tom Collins
Step 1 - connect to the db, and run the following command
"select substr(reg_var_name,1,24) as reg_var_name, substr(reg_var_value,1,12) as reg_var_value, level from table(sysproc.reg_list_variables()) as registryinfo"
this will return :
REG_VAR_NAME REG_VAR_VALUE LEVEL
------------------------ ------------- -----
DB2AUTOSTART YES I
DB2ADMINSERVER dasusr1 G
DB2COMM tcpip I
DB2SYSTEM ukrhdb2p02.t G
DB2_EEE_LICENSE_POLICY 281479271743 G
with various values . Estimate from these value your next course of action.
You can also use, although beginning with DB2 V8 - this is no longer supported.
db2set DB2AUTOSTART -i <MY INSTANCE NAME>
If DB2AUTOSTART = "YES" than db2autostart is OK ,
If it is set at NO , issue the command , logged in as the instance owner:
db2set DB2AUTOSTART=YES
Step 2 - you will also need to activate the DB2 fault monitor controller command. Two main funcations it serves are 1)it automatically
starts the instance after a crash 2)Restarts the instance on a system restart
This command reconfigures the inittab file , to allow the fault monitor controller to start at startup
/opt/ibm/db2/V9.5/bin/db2fmcu -u -p /opt/ibm/db2/V9.5/bin/db2fmcd
Ref:Jack Vamvas(http://www.dba-db2.com)
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |