Rowley,
Mike is correct / has provided you with the solution.
In 5.1, "The ContainerName and ContainerType attributes are deprecated." (ref: VCS 5.1 Bundled Agents Guide p176 https://sort.symantec.com/public/documents/sf/5.1/solaris/pdf/vcs_bundled_agents.pdf )
I can't find the exact document you're referenced with that example on p118, however it appears to be pre-5.1 (eg: p169 of the 5.0MP3 bundled agents guide has a config example that matches yours) - if you're using 5.1 you should refer to the documents for that version so you're not trying to use changed/obsolete information. See SORT to select the documentation relevant to your version: https://sort.symantec.com/documents
The equivalent example from the 5.1 Bundled Agents guide (p200) shows:
------------------------------
Application resource in a non-global zone for Solaris 10
In this example, configure a resource in a non-global zone: localzone1. The ZonePath of localzone1 is /zone1/root. The ConainerInfo attribute for this service group is set to ContainerInfo @ sys1 = { Name = “localzone1”, Type = “Zone”, Enabled = 1}. Configure the executable samba as StartProgram and StopProgram, with start and stop specified as command line arguments respectively. Configure the agent to monitor two processes: a process specified by the pid smbd.pid, and the process nmbd.
Application samba_app (
StartProgram = "/usr/sbin/samba start"
StopProgram = "/usr/sbin/samba stop"
PidFiles = { "/localzone1/root/var/lock/samba/smbd.pid" }
MonitorProcesses = { "nmbd" }
)
------------------------------
The VCS 5.1 Agent for Oracle Installation and Configuration Guide has Sample configuration for Oracle instances in Solaris zones (pp138-146) - these are dependency charts rather than main.cf extracts; there are main.cf examples pp120-137, however as you mentioned there isn't a main.cf example showing a non-global zone configuration. As Mike points out this is not required since there is no difference in the configuration of the Oracle resource configuration (ie: the zone config is specified in the sg configuration)
From Veritas Storage Foundation and High Availability Solutions Virtualization Guide - About VCS support for zones p18 (https://sort.symantec.com/public/documents/sf/5.1/solaris/pdf/sfha_virtualization.pdf )
------------------------------
Configuring the ContainerInfo attribute
The service group attribute ContainerInfo specifies information about the zone. When you have configured and enabled the ContainerInfo attribute, you have enabled the zone-aware resources in that service group to work in the zone environment.
VCS defines the zone information at the level of the service group so that you do not have to define it for each resource. You need to specify a per-system value for the ContainerInfo attribute.
------------------------------
The resource type/attribute definitions are in Appendix A of the Oracle Agent installation + configuration guide, so once the service group has been configured to specify the zone, you should hzve enough information to define the Oracle resource to start/stop/monitor in the zone.
regards,
Grace