Assumptions :
DB2 version is 8.X
Solaris Local Zones are booted automatically on reboot.
Solaris Local Zone Name: zone1

Whenever the Solaris Local Zone is not under VCS control using hazonesetup the error is observed in engine_A.log.

Since Local Zone is not defined under VCS configuration, Local Zone is not able to write the logs in Global Zone.

To overcome this problem, execute below steps to configure VCS without defining the zone.

#haconf -makerw

#vcsencrypt -vcs password

#haclus -modify UserNames -add z_zonename password_encrypted  
e.g. #haclus -modify UserNames -add z_zone1 bMJhMMmLMjMNlL

#hauser -addpriv z_zonename Administrator -group Service_Group
e.g. #hauser -addpriv z_zone1 Administrator -group db2sg

Create VCS_HOST environment :

#zlogin zonename VCS_HOST=hostname+domainname;
e.g. #zlogin mandar1 VCS_HOST=

#export VCS_HOST;

#/opt/VRTSvcs/bin/halogin z_zonename password

Above step creates the file .vcspwd inside the local zone's ROOT directory

Now Login to Zone using root :

bash-3.00# zlogin -l root zonename
e.g. #zlogin -l root zone1

[Connected to zone 'zone1' pts/7]

Check if .vcspwd file is  created

# ls -la .vcspwd
-rw-------   1root     root          63 Feb 20 14:42.vcspwd

Verify the contents of the file.

# more .vcspwd
100 hostname+domainname z_zonename encrypted_paasword


Now create the .vcshost file in local zone's /etc/VRTSvcs directory.
Normally, the zone agent does this for us. Since we don't have the zone resource under VCS control, we need to manually create this file

# pwd
/etc/VRTSvcs

# more .vcshost
hostname+domainname




Test the agent's ability to log messages to engine_A.log using following command..
#hares -probe Res_Name -sys SystemName

Check the status of the Resource

#hares -probe Res_Name -sys SystemName
#tail -f /var/VRTSvcs/log/engine_A.log