Install Oracle software and create Oracle Database. Refer to the following chapters.
Note
Be careful of the following points at the time of Oracle installation, and database creation.
About the allocation of Oracle software and a database, read description of the above-mentioned chapter as follows.
It is necessary to replace "local disk" with "Volume for root file system of non-global zone".
It is necessary to replace "shared disk" with "Volume for Oracle data allocation".
When non-global zone image is shared, because the operation node and standby node shares the root file system of non-global zone, installation/setup of Oracle software, and creation/setup of a database are only once carried out by operation node.
When non-global zone image is not shared, installation/setup of Oracle software are carried out by all the nodes. creation/setup of database are only once carried out by operation node, and database setup of operation node is copied to standby node using the cloracpy command.
Carry out registration of the SYSTEM user’s password by the clorapass command in every non-global zone.
Oracle listeners' IP address is set up according to the use existence or nonexistence of the Gls resource on non-global zone. When you don't use Gls resource, specify the IP address of non-global zone. When you use a Gls resource, specify the virtual IP (taking over IP).
In order to use ASM in Oracle Solaris Zones environment, for the specification of Oracle Database, it is necessary to add a proc priocntl privilege toward non-global zone in advance.
Execute the following commands.
# zonecfg -z <zone name> set limitpriv=default,proc_priocntl
