Using Oracle RDBMS With Sun. Scott Canaan Rochester Institute of Technology

Transcription

1 Using Oracle RDBMS With Sun Solaris Containers (Zones) Scott Canaan Rochester Institute of Technology

2 Sun Solaris Zones Overview Virtual OS environments Each local zone is a mini Solaris box Separate name, IP address, IP ports Each local zone can be addressed independently Global zone vs. local zone Global zone is the machine Local zones are contained inside the global zone

3

4 Global zone The server itself System-wide configuration & control Only 1 per system Can see all local zones Always has at least 1 CPU

5 Local zones Independent OS environment Independent administration Secure from other local zones Have their own IP, ports Can limit system resources

6 Zone File System Layout Global Zone Global root / /zone /usr /dev zone1 zone2 zone3 Zone root /etc /bin Local zones /usr /dev

7 Global zone view: $ ps -ef grep smon oracle Oct 12? 1:29 ora_smon_clawprod oracle :50:19? 0:15 ora_smon_regdprod oracle Oct 12? 0:39 ora_smon_omgrprod oracle :12:07? 0:15 ora_smon_dwksprod srcdco :24:37 pts/17 0:00 grep smon oracle :26:23? 0:10 ora_smon_dwhsprod oracle :28:31? 0:06 ora_smon_jiraprod oracle Oct 12? 0:34 ora_smon_awrxprod oracle :05:02? 0:32 ora_smon_advcconv oracle :56:49? 0:13 ora_smon_dwmtdevl oracle :21:00? 0:18 ora_smon_simsprod oracle :53:13? 0:15 ora_smon_admmprod oracle :13:23? 0:14 ora_smon_dwhsdevl oracle :04:30? 0:37 ora_smon_adv1

8 Local zone view: -ef grep smon oracle :26:23? 0:10 ora_smon_dwhsprod oracle :25:47 pts/3 0:00 grep smon oracle@sc2oracle42:dwhsprod>

9 Some advantages: Security Segregation Control over access at the zone level Independence Each zone can t see or affect other zones directly Better use of hardware Virtual environment uses hardware more efficiently Easier administration SA can administer global zone and local zones together or independently

10 Oracle installations Oracle installed in local zones Install only in the local zones that need Oracle More granular control over patching and upgrades Can lower Oracle licensing costs: Document: partitioning.pdf, page 2 Hard Partitioning Limits exposure of Oracle to other applications

11 Oracle Installations, continued Oracle installed in the global zone Oracle installation is available to all local zones Other zones that need the Oracle client or libraries will have access All Oracle databases must be patched / upgraded together An option is to create additional Oracle Homes for each patch or Oracle version needed Does not limit Oracle licensing costs

12 Issues: Security Oracle needs to write back to the Oracle Home Had to allow local zones the ability to write to the global zone Specified the directories that needed write access

13 Issues continued: Dynamic CPU allocation caused Oracle to crash Only when CPU count was reduced Crashed at 10:00pm (auto statistics collection) Possibly fixed Other applications linked to Oracle libraries Causes problems at upgrade / patching time Can t delete old versions until applications changed

14 Clustering all this Originally used Sun Cluster Have to keep Oracle Homes the same on all nodes We do one install, the SA copies the Oracle Home and orainventory to the other nodes (and clusters)

15 RITs implementation: Dumped Sun Cluster SA wrote cluster software (medacluster) Disk is mapped to a zone Zone and disk fail from node to node together Oracle software always on /u02 Database on /u01 or /u03 (if more than one in a zone) Applications are in their own zones Applications and databases don t share zones

16 Cluster and zone commands: All cluster and zone commands can only be run in the global zone havi vi that allows copying to all nodes in the cluster when done: oratab --- do edits --- Do you want to syncronize oratab to other node(s)? [y]y Copying file to node...vmz07...vmz38...vmz41...vmz43...vmz44...

17 hacp cp that does the copy on all nodes in the cluster harun runs whatever command follows on all nodes in the cluster (must be in double quotes)

18 zz_fill_cfae.sql test.sql test.sql "ls -lia test.sql" -----vmz03 command: ls -lia test.sql rw-r oracle dba Oct 15 16:18 test.sql -----vmz07 command: ls -lia test.sql rw-r oracle dba Oct 15 16:18 test.sql -----vmz38 command: ls -lia test.sql rw-r oracle dba Oct 15 16:18 test.sql -----vmz41 command: ls -lia test.sql rw-r oracle dba Oct 15 16:18 test.sql -----vmz43 command: ls -lia test.sql rw-r oracle dba Oct 15 16:18 test.sql -----vmz44 command: ls -lia test.sql rw-r oracle dba Oct 15 16:18 test.sql oracle@vmz03:dwhsprod>

19 Cluster and zone commands continued: hacheck checks that the named file is on all nodes and is the same test.sql Using "vmz03" as master copy of file: "test.sql" Checking remote server: "vmz07"...files same Checking remote server: "vmz38"...files same Checking remote server: "vmz41"...files same Checking remote server: "vmz43"...files same Checking remote server: "vmz44"...files same

20 hacrontab runs crontab and allows the cron file to be copied to each node in the cluster e --- do edits --- Do you want to syncronize cron to other node(s)? [y]y Copying cron to node...vmz07...vmz38...vmz41...vmz43...vmz44... oracle@vmz03:dwhsprod>

21 zonecrontab runs crontab and allows the cron file to be coped to each node in the cluster and each zone on each node e Do you want to syncronize cron to other node(s)? [y]y Copying cron to node...vmz07...vmz38...vmz41...vmz43...vmz vmz03 command: /opt/ha/zonecp /tmp/mycron Copying to sc2oracle01: /tmp/mycron Copying to sc2oracle09: /tmp/mycron Copying to sc2oracle10: /tmp/mycron Copying to sc2oracle21: /tmp/mycron Copying to sc2oracle29: /tmp/mycron Copying to sc2oracle26: /tmp/mycron Copying to sc2oracle44: /tmp/mycron Copying to sc2oracle42: /tmp/mycron Copying to sc2oracle13: /tmp/mycron Copying to sc2oracle34: /tmp/mycron Copying to sc2oracle35: /tmp/mycron..4567

22 --- lots of additional verbage vmz03 command: /opt/ha/zonerun /bin/crontab /tmp/mycron Running in sc2oracle01: /bin/crontab /tmp/mycron Running in sc2oracle09: /bin/crontab /tmp/mycron Running in sc2oracle10: /bin/crontab /tmp/mycron Running in sc2oracle21: /bin/crontab /tmp/mycron Running in sc2oracle29: /bin/crontab /tmp/mycron Running in sc2oracle26: /bin/crontab /tmp/mycron Running in sc2oracle44: /bin/crontab /tmp/mycron Running in sc2oracle42: /bin/crontab /tmp/mycron Running in sc2oracle13: /bin/crontab /tmp/mycron Running in sc2oracle34: /bin/crontab /tmp/mycron Running in sc2oracle35: /bin/crontab /tmp/mycron even more verbage ---

23 Bibliography / Resources Used: Solaris 10 Containers Kimberly Chang, Sun Microsystems Working With Solaris Containers and the Solaris Service Manager Joost Pronk van Hoogeveen, Solaris Software, Sun Microsystems, 2006 Running Oracle Database in Solaris 10 Containers Best Practices, Oracle, 2006 (metalink Note: )