- 论坛徽章:
- 1
|
本帖最后由 yddll 于 2010-12-10 16:02 编辑
从头理一遍吧- 1) All references to WPAR in this document must be viewed as RSET-controlled system WPAR, application workload partitions are not supported.
- 2) O/S Version AIX 6.1 TL-02 SP2 (6100-02-02-0849), and later 6.1 versions are certified
- 3) Installation requires APAR # IZ52319 & IZ54871
- 4) Users need to set the environment variable AIXPERFSTAT_SCOPE to M for Oracle processes to insure they display accurate OS statistics in WPAR environment. The method of setting up an environment variable for Oracle processes depends on how the Oracle instance is started up. User is advised to follow Oracle's general recommendation for setting up an environment variable. The following example provides a quick overview.
- In simple cases a modification of startup dot files for Oracle user is enough.
- For the connections through listener either initial listener session needs to have environment variable set or listener.ora needs to be changed to include ENVS key for the specific SID_DESC.
- On Korn Shell
- $ export AIXPERFSTAT_SCOPE=M
- On C Shell % setenv AIXPERFSTAT_SCOPE M
- AIXPERFSTAT_SCOPE environment variable must be set in the environment:
- 1. prior to starting the listener and database
- 2. for all local connections
- If remote connections are used, the AIXPERFSTAT_SCOPE environment variable must be set in the listener.ora, one way to do this is by adding the following to it:
- (SID_LIST =
- (SID_DESC =
- (SID_NAME = v102)
- (ORACLE_HOME = /home/oracle/o102)
- (ENVS = 'AIXPERFSTAT_SCOPE=M')
- )
- )
- v102 for SID_NAME and /home/oracle/o102 for ORACLE_NAME are used as example purpose. Customer should use appropriate SID_NAME and ORACLE_HOME in connection string.
- 5) Only AIX JFS2 or Oracle certified NAS devices are supported for data storage, ASM can not be used at this time.
- 6) By design, WPARs share a common OS image which prevents loading kernel extensions in a particular WPAR. A kernel extension can only be loaded in the global environment, and when loaded is available on all WPARS sharing the OS. Since Oracle rootpre.sh loads kernel extensions it must be executed in the global environment. Note: When executed in a WPAR rootpre.sh errors as follows: The kernel extension fails to load. Error messages as below:
- CMD: /etc/loadext -L /etc SYS_SINGLELOAD: Permission denied kmid: 0 (0x0)path: '/etc/pw-syscall.64bit_kernel' libpath: '' ERROR: The kernel extension was not loaded. Cannot create directory /opt/ORCLfmap/ and couldn't copy over the files in that directory.
- 7) Oracle root.sh will fail to execute when run in a shared systemWPAR unless the Oracle installation is pointed to a manually created local directory with write access to users, for example /home/oracle/bin. Note: Omitting this step causes a silent error when root.sh fails to copy dbhome, oraenv and coraenv to the default /usr/local/bin/ which is a read only file system in the shared system WPAR.
- 8) Configuration of Asynchronous I/O and POSIX Asynchronous I/O must be done at the global environment because these operations involve loading kernel extensions. This operation needs to be performed only once since all WPARS will share the global OS characteristics.
复制代码 |
|