Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

DB2 VCS agent - DB2 10.1 support?

Created: 15 Nov 2012 • Updated: 20 Nov 2012 | 7 comments
ChrisNiva's picture
This issue has been solved. See solution.

Hi!

Does anyone know when DB2 VCS agent will support DB2 version 10.1?

Thanks!

// Chris

Discussion Filed Under:

Comments 7 CommentsJump to latest comment

mikebounds's picture

Note for VCS DB2 agent to support 10.1, probably just means Symantec need to test it themselves, rather than change agent, but you can confirm this yourself as agent entry points are quite detailed for this agent which are:

 

About the online agent function for VCS agent for DB2
The agent uses the db2gcf program to start a DB2 instance or database partition.
The command is:
# su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -u -I\
$DB2InstOwner -p $nodenum"
This agent can also use the db2start command to start all DB2 partitions.
 
About the offline agent function for VCS agent for DB2
The agent uses the db2gcf program to stop a DB2 database partition. For a database
with only one partition, it stops the instance. The command is:
# su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -d -I\
$DB2InstOwner -p $nodenum"
The agent can also use the db2stop command to stop all DB2 partitions.
 
About the monitor agent function for VCS agent for DB2
The agent executes the
su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -s -I $DB2InstOwner -p $nodenum"
command to check the status of the database
partition or node number. If the exit status of the db2gcf command is 0, the
monitor returns the exit code 110. Otherwise, the monitor returns an exit code
of 100 and the resource is taken offline
 
About the clean agent function for VCS agent for DB2
The agent first uses the db2stop command with the force option. If the command
is unable to clean the agent function, the agent then uses the db2_kill script to
kill the instance. If the db2_kill script fails, the kill -9 command is invoked.
# su $DB2InstOwner -c "$InstHome/sqllib/bin/db2stop force
nodenum $nodenum"
 

So if the commands above have not changed from 9.1/9.5/9.7 for the new 10.1 version, then the agent should work, but if you used agent it would technically be unsupported until Symantec test it themselves

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

ChrisNiva's picture

 

Hi!

Thanks, Mike.

The commands are correct, but it seems that the pid file have been changed from db2pgrp.000 to .db2pgrp.000 (point in front) in DB2 version 10.1

Some output from engine_A.log;

 

2012/11/15 13:24:46 VCS NOTICE V-16-20004-72 (edmdbcmod01) Db2udb:archive_db2:online:DB2 startup returned the output: 11/15/2012 13:24:46     0   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.

2012/11/15 13:26:31 VCS WARNING V-16-20004-83 (XXXX) Db2udb:archive_db2:monitor:Unable to locate Pidfile:[/home/archive/sqllib/ctrl/db2pgrp.000]

*CLEAN / FAULTED*

Any ideas about a work-around?

// Chris

mikebounds's picture

The DB2 agent guide says:

 

When an IMF-enabled agent starts up, the agent initializes the asynchronous
monitoring framework (AMF) kernel driver. After the resource is in a steady state,
the agent registers the details that are required to monitor the resource with the
AMF kernel driver. For example, the DB2 agent registers the PIDs of the processes
with the AMF kernel driver using its own imf_register function
 

and IMF is enabled by default, so if you disabled IMF, then the pid file MAY not be used.  To disable IMF use:

 

hatype -modify Db2udb IMF -update Mode 0
 
Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

ChrisNiva's picture

already tried that, Mike.
Same problem :(

The DB2 tech can´t change anything regarding the pidfile either.

I tried a work-around (not supported of course) and modified all agents script to .db2pgrp.000 but no luck;
Use of uninitialized value $pid in pattern match (m//) at db2lib.pm line 561.

The db2pgrp file in DB2 version 10.1 are different if I compare with older versions (like 9) and the agent can´t handle the "new" file.

Looks like the customer must wait on 10.1 support or downgrade to 9.7.

// Chris

mikebounds's picture

As the error is with the startup you could try using a different startup,so using StartUpOpt attribute set to CUSTOM or set UseDB2start to 1.  Then the online should work, but after the online is called it will call the monitor and the monitor according to docs just does:

 

su $DB2InstOwner -c "$InstHome/sqllib/bin/db2gcf -s -I $DB2InstOwner -p $nodenum"
 
and if this is the case, then it should work, however, often the docs are inaccurate and it well might be checking a PID file.  So, then, yes, customer must wait on 10.1 support or downgrade to 9.7.
 
Mike
 

 

 

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

jdangelo_symc's picture

DB2 10.1 support is targeted for our 6.0.3 release slated for Jan/Feb 2013.  This is of course subject to change. 

Joe D

SOLUTION