This chapter describes how to complete the postinstallation tasks after you have installed the Oracle Database 12c Release 1 (12.1) with Oracle Real Application Clusters (Oracle RAC) software. This chapter contains the following topics:
Note:
This chapter describes only basic configurations. Refer to Oracle Database Administrator's Guide, and the product administration and tuning guides for more detailed configuration and tuning information. Refer also to Oracle Database Installation Guide for your platform for additional postinstallation configuration information.Perform the following tasks after completing your installation:
Download and install patch updates. See the My Oracle Support website for required patch updates for your installation.
To download required patch updates:
Use a Web browser to view the My Oracle Support website:
Log in to My Oracle Support.
Note:
If you are not a My Oracle Support registered user, then click Register for My Oracle Support and register.On the main My Oracle Support page, click Patches & Updates.
On the Patches and Updates page, click Product or Family (Advanced).
In the Product field, select Oracle Database.
In the Release field, select one or more release numbers. For example, Oracle 12.1.0.1.0.
Click Search.
Any available patch updates are displayed in the Patch Search page.
Click the patch number to download the patch.
Select the patch number and click Read Me. The README page contains information about the patch set and how to apply the patches to your installation.
Return to the Patch Set page, click Download, and save the file on your system.
Use the unzip utility provided with Oracle Database 12c Release 1 (12.1) to uncompress the Oracle patch updates that you downloaded from My Oracle Support. The unzip utility is located in the $ORACLE_HOME/bin directory.
See Oracle Grid Infrastructure Installation Guide for information about how to stop database processes in preparation for installing patches.
On HP-UX platforms only, complete the following procedure to set external jobs ownership to the low-privilege user extjob:
Log on as root.
Change directory to the Oracle Database Oracle home:
# cd $ORACLE_HOME/rdbms/admin/
Open externaljob.ora with a text editor, and find the parameters run_user and run_group.
Set run_user to the external jobs user (extjob), and set run_group to a low-privileged group, such as other. For example:
run_user=extproc run_group=other
Save the file.
Note:
Modifyexternaljob.ora only as root.Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle Database 12c Release 1 (12.1) database products or options, refer to the manual in the product documentation library, which is available on the Oracle Technology Network (OTN) at:
Refer to these sections for information about configuring various products and features after installation:
OUI installs Oracle Database Vault by default when you install the Oracle RAC software, but you must register Oracle Database Vault with the Oracle RAC database and create database user accounts before you can use it. You must create the Database Vault Owner user and, optionally, the Database Vault Account Manager administrative user accounts.
To enable or disable the database security configuration after installation, you must use command-line Oracle Database Configuration Assistant (DBCA) options. By design, the DBCA graphical user interface (GUI) does not have the option to enable or disable secure configuration. For example, to enable the security settings after installation, you would use a command of the following form, where myRACdb1.example.com is the either the name of the local database instance or the DB_UNIQUE_NAME:
dbca –configureDatabase –sourceDB myRACdb1.example.com -SID –enableSecurityConfiguration true
After installation, you must configure Oracle Label Security in a database before you use it. You can configure Oracle Label Security in two ways: with Oracle Internet Directory integration and without Oracle Internet Directory integration.
| Configuration | Requirement |
|---|---|
| With Oracle Internet Directory integration | To configure Oracle Label Security with Oracle Internet Directory integration, Oracle Internet Directory must be installed in your environment and the Oracle database must be registered in the directory. |
| Without Oracle Internet Directory integration | If you configure Oracle Label Security (OLS) without Oracle Internet Directory integration, then you cannot configure it to use Oracle Internet Directory at a later stage. To configure Oracle Label Security with Oracle Internet Directory on your database at a later time, you must remove the OLS option on the database and configure the OLS with Oracle Internet Directory integration option. |
See Also:
Oracle Label Security Administrator's Guide for information about configuring Oracle Label SecurityOracle XML DB is a required component of the Oracle Database installation. However, you must manually configure the FTP and HTTP ports for Oracle XML DB.
See Also:
Oracle XML DB Developer's Guide for information on configuring the FTP and HTTP protocols for Oracle XML DBIf your Oracle RAC database uses files that are external to the database, then the external files should be located on shared storage that is accessible to all nodes. Each node should use the same mount point to access the file. Acceptable shared file systems include Database File System (DBFS), Oracle ASM Cluster File System (Oracle ACFS), or a supported network file system (NFS) using the Direct NFS Client.
The database directory object used to write and read files external to the database must point to a shared storage location, and each node must use the same mount point for the same shared storage location.
Note:
There is no checking of the contents of the external files or directory object specified as part of the external table to ensure that the directory contents are consistent on each node. To avoid unpredictable results, you must ensure that the same file is accessed from all nodes, or that the same file is used on all nodes.See Also:
Oracle Grid Infrastructure Installation Guide for more information about configuring storageRun the utlrp.sql script after creating or upgrading a database. This script recompiles all PL/SQL modules that might be in an invalid state, including packages, procedures, and types. You must do it immediately following installation, not at a later date.
Complete setting up the Oracle software owner user account environment (for example, oracle), as described in Section 5.2.1, "Set the Oracle User Environment Variables".
Start SQL*Plus, as follows:
$ sqlplus "/ AS SYSDBA"
Run the utlrp.sql script, where Oracle_home is the Oracle home path:
SQL> @Oracle_home/rdbms/admin/utlrp.sql
During installation, if you select a multitenant container database (CDB), and configure pluggable databases (PDBs), then you must add services to the PDBs after installation. If you do not add services to PDBs, and then the Oracle RAC One Node CDB fails over to another node, or you manually relocate the CDB to another node, then by default, all PDBs associated with the CDB that do not have registered services are restarted in MOUNTED state.
PDBs are opened in Read Write mode after failover, in case of Oracle RAC One Node database, or relocation in case of any Oracle RAC database, only after you have configured the PDBs to have associated services. If you have not associated services to PDBs, then the PDBs remains in MOUNTED state when the CDB instance restarts.
To add services to a PDB, use the following srvctl command syntax, where cdbname is the name of the CDB, service_name is the name of the service, and pdbname is the name of the PDB:
srvctl add service -d cdbname -s service_name -pdb pdbname
After you add services to your PDBs, if you relocate the CDB with which the PDBs are associated, or the CDB fails over for Oracle RAC One Node databases, then the PDBs associated with that CDB automatically open in Read Write state.
See Also:
Oracle Database Concepts and Oracle Real Application Clusters Administration and Deployment Guide for more information about PDBs and adding servicesOracle recommends that you complete the following tasks after installing Oracle RAC:
On each node, in the installation owner user profile file (in this example, oracle), set the environment variables ORACLE_BASE and ORACLE_HOME, and ORACLE_SID; also add ORACLE_HOME/bin to the path environment variable.
For example:
export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=/u01/app/oracle/12.1.0/dbhome_1 export PATH=$PATH:$ORACLE_HOME/bin export ORACLE_SID=sales1
If the environment variables ORACLE_HOME and ORACLE_SID are not set, and you try to use SQL*Plus or other tools, then you receive an error message requesting that you set these variables.
You can set up additional user accounts to manage your database. For information about setting up additional optional user accounts, see Oracle Database Security Guide.
Download and install the ORAchk utility to perform proactive heath checks for the Oracle software stack.
ORAchk is an expansion of the RACCheck utility. ORAchk extends health check coverage to the entire Oracle software stack, and identifies and addresses top issues reported by Oracle users. ORAchk proactively scans for known problems with Oracle products and deployments, including the following:
Standalone Oracle Database
Oracle Grid Infrastructure
Oracle Real Application Clusters
Maximum Availability Architecture (MAA) Validation
Upgrade Readiness Validations
Oracle Golden Gate
For information about configuring and running the ORAchk utility, refer to My Oracle Support note 1268927.1:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1268927.1
If you have installed Oracle Configuration Manager, then you must run a script to create a database account to collect database configuration collections. You must create this account in both Connected and Disconnected modes. The database account stores the PL/SQL procedures that collect the configuration information, and the account owns the database management system (DBMS) job that performs the collection. After the account has been set up, the account is locked because login privileges are no longer required.
To configure the database for configuration collection, run the following script:
$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s SID -r\ SYSDBA-USER -p SYSDBA-PASSWORD
The script installCCRSQL.sh creates an Oracle Configuration Manager user and loads the PL/SQL procedure into the database defined by the ORACLE_SID. You can also specify the database SID by using the -s option in the command line, as in the following example, where the SID is orcl:
$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s orcl
For Oracle RAC, you must run the database script against only one instance, such as the local instance on which you performed the installation. However, Oracle Configuration Manager must be installed in all instance homes.
See Also:
Oracle Configuration Manager Installation and Administration Guide for more information about Oracle Configuration Manager installationWhen you install Oracle Database, some options are enabled and others are disabled. To enable or disable a particular database feature for an Oracle home, shut down the database and use the chopt tool.
The chopt tool is a command-line utility that is located in the directory ORACLE_HOME/bin. It uses the following syntax, where db_option is the option whose status you want to modify:
chopt [enable | disable] db_option
Table 5-1 shows the possible options for db_option: