Release 2 (9.2.0.3) for Linux Intel
Part No. B10925-01
 Contents |
 Index |
|
Oracle9 Database Certified Configuration Installation Guide
Release 2 (9.2.0.3) for Linux Intel Part No. B10925-01 |
|
This appendix contains information on the ocheck environment checking tool. The following topics are included:
The tool uses several files which all begin with ocheck. These files must be located in the same directory as the main program. The following command shows the syntax for the tool:
/admin/dbcc/3.1.0/ref_config/ocheck/ocheck -productprod_namephase
The following table lists the tool parameters.
Table A-1 ocheck Tool Parameters
| Parameter | Description |
|---|---|
product |
Checks the product name defined by the prod_name option. The ocheck.chk file lists the product names.
|
phase |
Defines the phase of the installation. The ocheck.chk file lists the phases. Currently, the following phases are available:
|
The ocheck tool displays the following exit status numbers:
Status number of 0 (zero) indicates all checks passed successfully.
Status number of 1 indicates the wrong arguments were used to call the tool.
Status numbers 2 through 29 indicate a problem occurred when running the tool.
Status numbers 30 through 99 indicate the highest severity of system misconfigurations encountered by the tool during its run.
The following table lists each check and its description. The variable names that begin with OCC_ are defined in the genocc data files or the ocheck.conf file. If a value depends on the setting for a specific database, then it will be in the genocc file. If the value is fixed and defined by the certified configuration, then it will be in the ocheck.conf file.
Table A-2 Check Definitions
| Check | Description |
|---|---|
| check_active_instance | Checks if a SQL*Plus connection can be made, and if more than one instance is found. |
| check_clusterware_install | Checks if the Oracle UDLM and Sun Cluster packages are installed on the system. This is for Solaris operating system only. |
| check_clusterware_running |
Checks if the scstat program returns a successful exit status.
|
| check_cm_running | Checks if the lsnodes program returns a successful exit status. |
| check_cpu_count | Checks if the number of processors installed and running is above a given minimum count. The source for the minimum is OCC_CPU_COUNT_MIN, and is 2. |
| check_cpu_power | Checks if the Oracle processor power number is above a given minimum value. The power number is the sum of the MHz of all running processors. The source for the minimum is OCC_CPU_COUNT_MIN * OCC_CPU_CLOCKSPEED_MIN. The Linux Intel minimum is 1400, and the Solaris operating system minimum is 800. |
| check_cpu_speed | Checks if the processor MHz of all processors is above a given minimum value. The source for the minimum is OCC_CPU_CLOCKSPEED_MIN. The Linux Intel minimum is 700, and the Solaris operating system minimum is 400. |
| check_executable_bc |
Checks if the bc program is installed on the system.
|
| check_executable_ksh |
Checks if the ksh program is installed on the system.
|
| check_executable_oracle | Checks if the Oracle program is installed, has the correct ownership and permissions, and can resolve all references to shared libraries. |
| check_external_storage | Checks if raw devices for Oracle data storage exist for the system. The sources are OCC_EXTERNAL_DATA_STORAGE_DEVICE and OCC_EXTERNAL_REDO_STORAGE_DEVICE. |
| check_filesystem_data_storage | Checks if the file system used for Oracle data files is at least a given minimum size. The source for the minimum is OCC_FILESYSTEM_SIZE_DATA_MIN_MB. The value is 9216. |
| check_filesystem_data_storage_mount_opts |
Checks if the file system used for Oracle data files is mounted with the correct options. The source is OCC_MOUNT_NFS_OPTIONS. The options are the following:
|
| check_filesystem_program_space | Checks if the file system used for the Oracle program files has a given minimum amount of free space. The source is OCC_FILESYSTEM_AVAIL_SW_INSTALL_MIN_MB. The value is 5210. |
| check_filesystem_program_storage | Checks if the file system for the Oracle program files is at least a given minimum size. The source is hard-coded. The value is 9216. |
| check_filesystem_sizes |
Checks if several standard file systems are at least a given minimum size. The source is OCC_FILESYSTEM_SIZES.
The following are the Linux Intel values:
The following are Solaris operating system values:
|
| check_gcc_version | Checks if the version and revision values of the installed gcc compiler are correct. The sources are OCC_GCC_VERSION and OCC_GCC_RELEASE. The Linux Intel values are 2.96, and 108.1, respectively. |
| check_group_dba | Checks if the Oracle DBA group exists. The source is OCC_ORACLE_DBA_GROUP. The value is group:db{lowercase(OCC_DB_NAME)}. |
| check_group_install |
Checks if the Oracle software owner group oinstall exists.
|
| check_gsd_running |
Checks if the gsdctl program returns a successful exit status.
|
| check_httpd |
Checks if an httpd process is running on the system.
|
| check_install_log | Checks if the Oracle Installer log is not empty. If it is not empty, then it contains error messages. |
| check_listener_running |
Checks if the tnslsnr process is running on the system.
|
| check_mirrored_sw_disks | This check is not implemented in this release. |
| check_mount_options | Checks if UFS partitions are mounted with the logging option. |
| check_network_interfaces | Checks if the number of configured network interfaces is above a given minimum. The source is OCC_NIC_COUNT. The value is 2. |
| check_network_interfaces_rac | Checks if the number of configured network interfaces is above a given minimum. The source is OCC_NIC_COUNT_RAC_MIN. The value is 4. |
| check_oracle_home |
Checks if the ORACLE_HOME and ORACLE_SID variables are set, and if the $ORACLE_HOME/bin/oracle directory exists in the system.
|
| check_oracle_user |
Checks if the Oracle user account exists, has the correct login shell, such as /bin/bash or /bin/ksh, and is in the Oracle DBA group. The sources are OCC_ORACLE_DBA_USER and OCC_ORACLE_DBA_GROUP. The user value is or{lowercase(OCC_DB_NAME_)}. The group value is db{lowercase(OCC_DB_NAME)}.
|
| check_oracle_user_groups | Checks if the Oracle user is in the Oracle DBA group, is in the Oracle software owner group, and has the Oracle software owner group as its primary group. |
| check_oracle_user_home | Checks if the Oracle user exists and has the correct home directory set, and if the home directory exists and is owned by the Oracle user. The sources are OCC_ORACLE_DBA_USER and OCC_ORACLE_DBA_USER_HOME. The user value is or{lowercase(OCC_DB_NAME_)}. The directory value is /{lowercase(OCC_DB_NAME_}/oracle. |
| check_os_64bit | Checks if the operating system can run 64-bit applications. This is for Solaris operating system only. |
| check_os_cluster_patches | Checks if the required clusterware patches have been installed on the system. The source is OCC_PATCHES_RAC. The value is 110648-20. This is for Solaris operating system only. |
| check_os_patches | Checks if the required operating system patches have been installed on the system. The source is OCC_PATCHES. The Solaris value is 108528-15 112953-02. |
| check_os_version |
Checks if the operating system is correct. The sources are OCC_OS_VERSION, OCC_OS_VERSION_NAME_LINUX, and OCC_OS_VERSION_SUNOS_UPDATE.
The Linux Intel values are as follows:
The Solaris operating system values are as follows:
|
| check_packages_rac | Checks if the required packages for Real Application Clusters are installed on the system. The source is OCC_PACKAGES_RAC. The value is "". |
| check_physical_memory | Checks if the amount of installed RAM is above a given amount. The source is (OCC_CPU_COUNT_MIN * OCC_RAM_PER_CPU_MIN_MB) - 128. The value is 1920. |
| check_private_network | This check is not implemented in this release. |
| check_public_network | Checks if a network adapter is up and running. |
| check_remote_rsh_oracle |
Checks if the oracle user is able to use rsh to reach all cluster nodes. The source is nodes:OCC_RAC_NODES. The value is variable.
|
| check_remote_rsh_root |
Checks if the root user is able to use rsh to reach all cluster nodes. The source is nodes:OCC_RAC_NODES. The value is variable.
|
| check_remote_time | Checks if the date and time on all cluster nodes is within two seconds of those on the local node. The source is nodes:OCC_RAC_NODES. The value is variable. |
| check_shared_memory | Checks if the system shared memory and semaphore parameters are set correctly. The Linux Intel source is hard-coded. The Solaris operating source is OCC_KERNEL_PARAMS. |
| check_shared_storage_files | This check is not implemented in this release. |
| check_snmp_agent |
Checks if the agentctl program returns a successful exit status.
|
| check_sqlplus_connect |
Checks if the sqlplus program is able to log in as SYSOPER and access the DUAL table.
|
| check_sqlplus_login |
Checks if the sqlplus program is able to log in as SYSDBA.
|
| check_swap_space | Checks if the amount of swap configured is above a given minimum. The source is OCC_SWAP_SIZE_MIN. The value is 4 GB - 96 MB. |
| check_swap_space_avail | Checks if the amount of swap space available is above a given minimum. The source is hard-coded. The Linux Intel value is not implemented in this release. The Solaris operating system value is 4 GB. |
| check_tnsping |
Checks if the tnsping program returns a successful exit status when pinging the database service. The source is service name:OCC_DB_NAME. The value is variable.
|
| check_volmgr_installed | Checks if the VERITAS volume manager is installed on the system. This is for Solaris operating system only. |
The ocheck tool checks specific items depending on the product and phase parameters used with the ocheck command. This section includes the following topics:
Oracle9i Database Certified Configuration Single-instance System Checks
Oracle9i Database Certified Configuration Real Applications Clusters System Checks
Oracle9i Database Certified Configuration single-instance can be checked using the rdbms product parameter with the different phase parameters to check the system. This section describes the checks for each phase parameter. The following topics are included in this section:
The following items are checked when using the rdbms parameter and the preinstall parameter:
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_filesystem_program_space
check_filesystem_program_storage
check_filesystem_sizes
check_gcc_version
check_group_dba
check_group_oinstall
check_mirrored_sw_disks
check_mount_options
check_network_interfaces
check_oracle_user
check_oracle_user_groups
check_oracle_user_home
check_os_64bit
check_os_patches
check_os_version
check_physical_memory
check_swap_space
check_swap_space_avail
The following items are checked when using the rdbms parameter and the postinstall parameter:
check_executable_oracle
check_install_log
check_sqlplus_login
The following items are checked when using the rdbms parameter and the preconfig parameter:
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_executable_oracle
check_filesystem_data_storage
check_filesystem_data_storage_mount_opts
check_gcc_version
check_group_dba
check_group_oinstall
check_install_log
check_mirrored_sw_disks
check_mount_options
check_network_interfaces
check_oracle_user
check_oracle_user_groups
check_oracle_user_home
check_os_64bit
check_os_patches
check_os_version
check_physical_memory
check_public_network
check_shared_memory
check_sqlplus_login
check_swap_space
check_swap_space_avail
The following items are checked when using the rdbms parameter and the postconfig parameter:
check_httpd
check_listener_running
check_oracle_home
check_snmp_agent
check_sqlplus_connect
check_tnsping
The following items are checked when using the rdbms parameter and the preimage parameter:
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_filesystem_data_storage
check_filesystem_data_storage_mount_opts
check_filesystem_program_space
check_filesystem_program_storage
check_filesystem_sizes
check_gcc_version
check_group_dba
check_group_oinstall
check_mirrored_sw_disks
check_mount_options
check_network_interface
check_oracle_user
check_oracle_user_groups
check_oracle_user_home
check_os_64bit
check_os_patches
check_os_version
check_physical_memory
check_swap_space
check_swap_space_avail
check_public_network
The following items are checked when using the rdbms parameter and the postimage parameter:
check_executable_oracle
check_install_log
check_sqlplus_login
The following items are checked when using the rdbms parameter and the reconfig parameter:
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_executable_oracle
check_gcc_version
check_group_dba
check_group_oinstall
check_install_log
check_mirrored_sw_disks
check_mount_options
check_network_interfaces
check_oracle_user
check_oracle_user_groups
check_oracle_user_home
check_os_64bit
check_os_patches
check_os_version
check_physical_memory
check_public_network
check_shared_memory
check_sqlplus_login
check_swap_space
check_swap_space_avail
The following items are checked when using the rdbms parameter and the system parameter:
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_filesystem_sizes
check_gcc_version
check_mirrored_sw_disks
check_os_64bit
check_os_patches
check_os_version
check_physical_memory
check_swap_space
check_swap_space_avail
Oracle9i Database Certified Configuration Real Application Clusters can be checked using the rac product parameter with the different phase parameters to check the system. This section describes the checks for each phase parameter. The following topics are included in this section:
The following items are checked when using the rac parameter and the preinstall parameter:
check_clusterware_installed
check_clusterware_running
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_filesystem_program_space
check_filesystem_program_storage
check_filesystem_sizes
check_gcc_version
check_group_dba
check_group_oinstall
check_mirrored_sw_disks
check_mount_options
check_network_interfaces_rac
check_oracle_user
check_oracle_user_groups
check_os_64bit
check_oracle_user_home
check_os_cluster_patches
check_os_patches
check_os_version
check_packages_rac
check_physical_memory
check_swap_space
check_swap_space_avail
check_volmgr_installed
The following items are checked when using the rac parameter and the postinstall parameter:
check_executable_oracle
check_install_log
check_sqlplus_login
The following items are checked when using the rac parameter and the preconfig parameter:
check_cpu_count
check_cpu_speed
check_cpu_power
check_clusterware_installed
check_clusterware_running
check_executable_bc
check_executable_ksh
check_executable_oracle
check_external_storage
check_gcc_version
check_group_dba
check_group_oinstall
check_install_log
check_mirrored_sw_disks
check_mount_options
check_network_interfaces_rac
check_oracle_user
check_oracle_user_groups
check_os_64bit
check_oracle_user_home
check_os_cluster_patches
check_os_patches
check_os_version
check_packages_rac
check_physical_memory
check_private_network
check_public_network
check_remote_rsh_oracle
check_remote_rsh_root
check_remote_time
check_shared_memory
check_shared_storage_files
check_sqlplus_login
check_swap_space
check_swap_space_avail
check_volmgr_installed
The following items are checked when using the rac parameter and the postconfig parameter:
check_active_instance
check_gsd_running
check_httpd
check_listener_running
check_oracle_home
check_snmp_agent
check_sqlplus_connect
check_tnsping
The following items are checked when using the rac parameter and the preimage parameter:
check_clusterware_installed
check_clusterware_running
check_cpu_speed
check_cpu_count
check_cpu_power
check_executable_bc
check_executable_ksh
check_external_storage
check_filesystem_program_space
check_filesystem_program_storage
check_filesystem_sizes
check_gcc_version
check_group_dba
check_group_oinstall
check_mirrored_sw_disks
check_mount_options
check_network_interfaces_rac
check_oracle_user
check_oracle_user_groups
check_oracle_user_home
check_os_64bit
check_os_cluster_patches
check_os_patches
check_os_version
check_packages_rac
check_physical_memory
check_public_network
check_private_network
check_remote_rsh_root
check_remote_time
check_shared_storage_files
check_swap_space
check_swap_space_avail
check_volmgr_installed
The following items are checked when using the rac parameter and the postimage parameter:
check_executable_oracle
check_install_log
check_sqlplus_login
The following items are checked when using the rac parameter and the reconfig parameter:
check_clusterware_installed
check_clusterware_running
check_cm_running
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_executable_oracle
check_gcc_version
check_group_dba
check_group_oinstall
check_install_log
check_mirrored_sw_disks
check_mount_options
check_network_interfaces-rac
check_oracle_user
check_oracle_user_groups
check_oracle_user_home
check_os_64bit
check_os_cluster_patches
check_os_patches
check_os_version
check_packages_rac
check_physical_memory
check_private_network
check_public_network
check_remote_rsh_oracle
check_shared_memory
check_sqlplus_login
check_swap_space
check_swap_space_avail
check_volmgr_installed
The following items are checked when using the rac parameter and the system parameter:
check_cpu_count
check_cpu_power
check_cpu_speed
check_executable_bc
check_executable_ksh
check_filesystem_sizes
check_gcc_version
check_mirrored_sw_disks
check_network_interfaces-rac
check_os_64bit
check_os_patches
check_os_cluster_patches
check_os_version
check_physical_memory
check_swap_space
check_swap_space_avail
The ocheck report output is printed to the screen. To print the output to a file, use the -o option. The output consists of a header, body, and footer. Informational messages about the progress of the program and errors may be printed to standard output.
The report header contains the following:
Version of ocheck tool
Time the report was generated
Name of the system, and the name of the database being examined
Product and phase being checked
Report body column headings
The following is an example of a report header:
ocheck 3.7b (library C313b/S37) 10-Mar-2003 11:44:04 PST system: systhost1 (ORCL) RDBMS "system" check Check Value Expected Status
The report body consists of the section header lines and the check output lines. The section header lines consist of descriptive text used to categorize groups of checks. The check output lines consists of one line of formatted output, and an optional line of text with additional information or an explanation of an error.
The following is an example of a report body:
Operating System and Software Configuration Filesystem size: /dgold/oradata 0 MB >= 8192 MB fail -- directory "/dgold/oradata" does not exist
In the preceding example, the first column, Filesystem size: /data, contains the name of the check and describes what was examined by the check. The second column, 0 MB, contains the current value or state of the checked item. The third column, 8192 MB, specifies the expected value or state that would make the check successful. It is preceded by a logical operator, such as ==, <=, or >=, that indicates how the value in the second column compares with the value in the third column. The fourth column indicates the status of the check. The status is either pass or fail. An optional warn status is not used currently. The optional line of additional information is always preceded by two hyphens, and explains the check status.
The ocheck tool checks the hardware, software and operating system for compatibility with Oracle9i Database Certified Configuration. The tool uses several files which all begin with ocheck. These files must be located in the same directory as the main program. If the script succeeds, then the system can run an Oracle9i Database Certified Configuration. If the script halts, then the system cannot run the certified configuration. Check the log, correct any problems, and rerun the script.
The following tasks describe how to run the ocheck tool:
Log in to the system.
Run the script using one of the following commands:
To run the script without capturing the data:
/admin/dbcc/3.1.0/ref_config/ocheck/ocheck [-single|-rac] -system
To run the script and capture the data:
/admin/dbcc/3.1.0/ref_config/ocheck/ocheck [-single|-rac] -system -o /var/tmp/ocheck.system.log
|
 Copyright © 2002, 2003 Oracle Corporation All rights reserved |
|