Friday, July 24, 2015

Installing Enterprise Manager System-6

6 Installing Enterprise Manager System

This chapter describes how you can install a new Enterprise Manager system while utilizing an existing, certified Oracle Database to store Oracle Management Repository (Management Repository). In particular, this section covers the following:

Overview

You can install Enterprise Manager Cloud Control with either simple or advanced configuration.

Simple

Installs with typical, default configuration. As the name suggests, it is simple and quick — you are prompted to enter only the administrator password and the database connection details. While the database connection details are used for connecting to your existing, certified Oracle Database, the administrator password is used as a common password for SYSMAN user account, WebLogic user account, node manager user account, and also for authenticating new Oracle Management Agents that join the Enterprise Manager system.
The rest of the installation comes with default settings and preferences that Oracle believes you will need for a complete Enterprise Manager system.
This option is meant for administrators who do not worry about the granular control of the installer and want to install the Enterprise Manager System quickly.

Advanced

Installs with custom or advanced configuration, and is more flexible — you are prompted to enter WebLogic Server details, database connection details, data file locations for tablespaces, a password for creating the SYSMAN user account, and also customize ports according to your environment.

As part of a new Enterprise Manager system, the installation wizard does the following:

Installs the following components in the middleware home you enter in the installation wizard:
- Java Development Kit (JDK) 1.6 v24
- Oracle WebLogic Server 11g Release 1 (10.3.5)
- Oracle Management Service 12c Release 1 (12.1.0.1)
- Oracle Management Agent 12c Release 1 (12.1.0.1)
- Oracle JRF 11g Release (11.1.1.4.0), which includes oracle_common directory
- Oracle Web Tier 11g Release (11.1.1.4.0), which includes Oracle_WT directory
- Oracle Management Plug-Ins
  - Oracle Database Management Plug-In
  - Oracle Fusion Middleware Management Plug-In
  - Oracle My Oracle Support Management Plug-In
  - Oracle Exadata Management Plug-In
  - Note:
    - Java Development Kit (JDK) 1.6 v24 and Oracle WebLogic Server 11g Release 1 (10.3.5) are installed only if they do not exist in your environment.
    - If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.5), then follow the guidelines outlined in Before You Begin.
    - In addition to the mandatory plug-ins listed above, you can optionally install other plug-ins available in the software kit (DVD, downloaded software). The installer offers a screen where you can select the optional plug-ins and install them. However, if you want to install some plug-ins that are not available in the software kit (DVD, downloaded software), then refer to Advanced Installer Options.
Creates an Oracle WebLogic domain called GCDomain. For this WebLogic Domain, a default user account, weblogic, is used as the administrative user. You can choose to change this, if you want, in the installer.
Creates a Node Manager user account called nodemanager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.
Configures an Oracle Management Service Instance Base location (gc_inst) in the Oracle Middleware Home (middleware home), for storing all configuration details related to Oracle Management Service 12c. You can choose to change this, if you want, in the installer.
For example, if the middleware home is /u01/app/Oracle/Middleware/, then the instance base location is /u01/app/Oracle/Middleware/gc_inst. You can choose to change this, if you want, in the installer. However, you can change it for only advanced installation and not for simple installation.
Configures Oracle Management Repository in the existing, certified Oracle Database.
Runs the following configuration assistants to configure the installed or upgraded components:
- Plugins Prerequisites Check
- Repository Configuration Assistant
- MDS Schema Configuration Assistant
- OMS Configuration Assistant
- Plugins Deployment and Configuration Assistant
- Start Oracle Management Service Configuration Assistant
- Plugins Inventory Migration Configuration Assistant
- Oracle Configuration Manager Repeater Configuration Assistant
- Oracle Configuration Manager for OMS Configuration Assistant
- Agent Configuration Assistant

By default, the following are the contents of the middleware home for this type of installation:

<middleware_home>
    |_____wlserver_10.3
    |_____jdk16
    |_____oms
    |_____plugins
         |_____oracle.sysman.db.oms.plugin_12.1.0.1.0
         |_____oracle.sysman.emas.oms.plugin_12.1.0.1.0
         |_____oracle.sysman.mos.oms.plugin_12.1.0.1.0
    |_____agent
         |_____plugins
               |_____oracle.sysman.db.agent.plugin_12.1.0.1.0
               |_____oracle.sysman.db.discovery.plugin_12.1.0.1.0
               |_____oracle.sysman.emas.agent.plugin_12.1.0.1.0
               |_____oracle.sysman.emas.discovery.plugin_12.1.0.1.0
         |_____core
               |_____12.1.0.1.0
         |_____agent_inst
         |_____sbin
         |_____agentimage.properties
    |_____gc_inst
    |_____Oracle_WT
    |_____oracle_common
    |_____utils
    |_____logs
    |_____modules
    |_____user_project
    |_____ocm.rsp
    |_____registry.dat
    |_____domain-registry.xml
    |_____registry.xml

Before You Begin

Before you begin, keep these points in mind:

You can install Enterprise Manager Cloud Control using the installation wizard only on a single host, that is, locally on the server where the wizard is invoked. You cannot install on multiple or remote hosts.
Enterprise Manager Cloud Control can communicate only with Oracle Management Agent 12c and not with any earlier release of the Management Agent.
While installing on hosts that have multiple host names (for example, virtual hosts), you can pass the fully qualified host name using the ORACLE_HOSTNAME argument. Ensure that the host name you enter does not have underscores.
For example:
./runInstaller ORACLE_HOSTNAME=host1.foo.com
You must not set the ORACLE_HOME and ORACLE_SID environment variables. You must ensure that the Oracle directories do NOT appear in the PATH.
You must set the DISPLAY environment variable.
- In bash terminal, run the following command:
  export DISPLAY=<hostname>:<vnc port>.0
  For example, export DISPLAY=my.example.com:1.0
- In other terminals, run the following command:
  setenv DISPLAY <hostname>:1.0
  For example, setenv DISPLAY my.example.com:1.0
The Enterprise Manager Cloud Control Installation Wizard installs Java Development Kit (JDK) 1.6 v24 and Oracle WebLogic Server 11g Release 1 (10.3.5) only if they do not exist in your environment.
If Oracle WebLogic Server 11g Release 1 (10.3.5) does not exist and if you want to manually install it, then ensure that you install it using JDK 1.6 v24+ (64-bit version for 64-bit platforms and 32-bit version for 32-bit platforms).
- Download JDK 1.6 v24+ for your platform from the platform vendor's Web site. For example, download SUN JDK 1.6 v24+ for Linux platforms from Oracle Web site. Similarly, download the JDK for other platforms from other vendors' trusted Web sites.
- If you already have JDK, then verify its version by navigating to the <JDK_Location>/bin directory and running the following command:
  "./java -fullversion"
  To verify whether it is a 32-bit or a 64-bit JDK, run the following command:
  "file *"
- JROCKIT is not supported.
- If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.5) on Linux 64-bit platforms, first install the 64-bit JDK for that platform, and then download and use the wls1035_generic.jar file to install Oracle WebLogic Server.
  For example,
  <JDK home>/bin/java -d64 -jar <absolute_path _to_wls1035_generic.jar>
- If you want to manually install Oracle WebLogic Server 11g Release 1 (10.3.5) on Linux 32-bit platforms, then download and use either the wls1035_linux32.bin file or the wls1035_generic.jar file.
  For example,
  <JDK home>/bin/java -jar <absolute_path _to_wls1035_generic.jar>
- You must download the Oracle WebLogic Server software from Oracle Web site, and follow the instructions outlined in the Oracle® Fusion Middleware Installation Guide for Oracle WebLogic Server to install it. The guide is available in the Fusion Middleware documentation library available at:
  http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html
- You must ensure that the Oracle WebLogic Server installation is a typical installation, and even if you choose to perform a custom installation, ensure that components chosen for custom installation are the same as the ones associated with a typical installation.
- You must ensure that the user installing the WebLogic Server is the same as the one installing Enterprise Manager Cloud Control.
You must not install Enterprise Manager Cloud Control in a middleware home that is on an NFS-mounted drive. Installing Enterprise Manager on an NFS-mounted drive causes the Oracle HTTP Server to restart frequently, which in turn makes the OMS inaccessible.
If you are forced to install on such a shared drive, then perform an advanced installation as described in Installing with Advanced Configuration so that you can enter a non-NFS-mounted location for the OMS instance base directory (gc_inst). In simple installation, you have no control over the OMS instance base directory location, as the default location is set by the installation wizard.
You must ensure that the Oracle WebLogic Server 11g Release 1 (10.3.5) installed by the Enterprise Manager Cloud Control Installation Wizard or by you is dedicated for Enterprise Manager Cloud Control. You must not have any other Oracle Fusion Middleware product installed in that middleware home.
Enterprise Manager Cloud Control cannot coexist with any Oracle Fusion Middleware product in the same middleware home because the ORACLE_COMMON property is used by both the products.
Oracle offers bug fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for bug fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:
http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf
When determining supportability and certification combinations for an Enterprise Manager Cloud Control installation, you must consider Enterprise Manager Cloud Control's framework components as well as the targets monitored by Enterprise Manager Cloud Control. Oracle recommends keeping your Cloud Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license.
You must upgrade all existing EMCLI clients of the earlier release to 12c Release 1 so that they can work with Enterprise Manager Cloud Control. This means, you must discard the old one and set up a new one.
For information about setting up a new EMCLI client, see the Enterprise Manager Command Line Interface Download page within the Cloud Control console. To access that page, in Cloud Control, from the Setup menu, select My Preferences, and then, click Command Line Interface.
In addition to the mandatory plug-ins listed above, you can optionally install other plug-ins available in the software kit (DVD, downloaded software). The installer offers a screen where you can select the optional plug-ins and install them. However, if you want to install some plug-ins that are not available in the software kit (DVD, downloaded software), then refer to Advanced Installer Options.
You can find the OMS and Management Agent entries in the /etc/oragchomelist file for all UNIX platforms except HPUNIX, HPia64, Solaris Sparc.
On HPUNIX, HPia64, Solaris Sparc platforms, the entries are present in /var/opt/oracle/oragchomelist.

Prerequisites

Table 6-1 lists the prerequisites you must meet before installing Enterprise Manager Cloud Control.

Table 6-1 Prerequisites for Installing Enterprise Manager Cloud Control

Requirement	Description
Hardware Requirements	Ensure that you meet the hard disk space and physical memory requirements as described in Chapter 2.
Operating System Requirements	Ensure that you install Enterprise Manager Cloud Control only on certified operating systems as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support. To access this matrix, follow these steps: Log in to My Oracle Support, and click the Certifications tab. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Cloud Control. From the Release list, select 12.1.0.1.0, and click Search. Note: If you use Oracle Solaris 10, then ensure that you have update 9 or higher installed. To verify whether it is installed, run the following command: `cat /etc/release` You should see the output similar to the following. Here, `s10s_u6` indicates that update 6 is already installed. `Solaris 10 10/08 s10s_u6wos_07b SPARC`
Package Requirements	Ensure that you install all the operating system-specific packages as described in Chapter 3.
Operating System Groups and Users Requirements	Ensure that you create the required operating system groups and users as described in Chapter 4.
Unique Host Name and Static IP Address Requirements	Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network. Note: You must use only a static IP address. If you use a dynamic IP address, the installation will fail.
Temporary Directory Space Requirements	Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. By default, the temporary directory location set to the environment variable `TMP` or `TEMP` is honored. If both are set, then TEMP is honored. If none of them are set, then the following default values are honored: `/tmp` on UNIX hosts and `c:\Temp` on Microsoft Windows hosts.
Central Inventory Requirements	Ensure that you allocate 100 MB of space for the central inventory directory. Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.
UMASK Value Requirements	Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file. For example: Bash Shell `$ . ./.bash_profile` Bourne or Korn Shell `$ . ./.profile` C Shell `% source ./.login`
File Descriptor Requirements	Ensure that you set the file descriptor to a minimum of 4096. To verify the current value set to the file descriptors, run the following command: `/bin/sh -c "ulimit -n`" If the current value is not 4096 or greater, then as a root user, update the `/etc/security/limits.conf` file with the following entries: `<UID> soft nofile 4096` `<UID> hard nofile 4096`
Existing Database Version Requirements	Ensure that the existing database is a certified database as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support. To access this matrix, follow these steps: Log in to My Oracle Support, and click the Certifications tab. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Cloud Control. From the Release list, select 12.1.0.1.0, and click Search. Important: Ensure that the database is patched with all the Patch Set Updates (PSU) or Critical Patch Updates (CPU) released for that release. Also ensure that you apply the patches If you use Oracle Database 11g Release 2 (11.2.0.1), then ensure that you apply the patches for bugs 10014178 and 8799099. If you use Oracle Database 11g Release 1 (11.1.0.7), then ensure that you apply Patch Set Update 2 and the patches for bugs 8644757 and 7525072.
Host File Requirements	Ensure that the host name specified in the `/etc/hosts` file is unique, and ensure that it maps to the correct IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page. The following is the recommended format of the `/etc/hosts` file: `<ip> <fully_qualified_host_name> <short_host_name>` For example, `141.81.5.71 host1.foo.com host1` According to RFC 952, the following are the assumptions: A name (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of domain style names. No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character. Also, if DNS server is configured in your environment, then you should be able to use DNS to resolve the name of the host on which you want to install the OMS. For example, all these commands must return the same output: `nslookup host1` `nslookup host1.foo.com` `nslookup 141.81.5.71`
Installing User Requirements	Ensure that you meet the following requirements: (For UNIX only) The installation must NOT be run by a root user. (For Microsoft Windows only) User must be part of the ORA-DBA group and have administrator permissions. (For Microsoft Windows only) User must belong to the DBA group, and have permissions to perform the following: Act as part of the operating system, Create a token object, Log on as a batch job, and Adjust memory quotas for a process. To verify whether the install user has these rights, from the Start menu, click Settings and then select Control Panel. From the Control Panel window, select Administrative Tools, and from the Administrative Tools window, select Local Security Settings. In the Local Security Settings window, from the tree structure, expand Local Policies, and then expand User Rights Assignment.
Permission Requirements	Ensure that you have write permission in the middleware home and the Oracle Management Service Instance Base location. Ensure that you have write permission in the temporary directory where the executables will be copied. For example, `/tmp` or `c:\Temp`. Ensure that you have write permission in the location where you want to create the Central Inventory (`oraInventory`) if it does not already exist. If the Central Inventory already exists, then ensure that you have write permission in the inventory directory. Ensure that the user who installed the existing Oracle Database has write permission in the data file locations where the data files for the new tablespaces will be copied. These tablespaces and data files are created while configuring Enterprise Manager Cloud Control. While installing with simple configuration ( Installing with Simple Configuration), the installer automatically honors the default locations so you are not prompted for them. However, while installing with custom configuration ( Installing with Advanced Configuration), the installer prompts you to validate or enter the locations explicitly.
Central Inventory Location Requirements	Ensure that the Central Inventory (`oraInventory`) is not in a shared location. When you use the `/etc/oraInst.loc` file, ensure that the inventory location specified there is not pointing to a shared location. If it is, change it to a non-shared location.
Proximity Requirements	Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond.
Port Requirements	Ensure that the ports you assign (within the given range) to the following components are free and available: Admin Server HTTP SSL Port = 7101 - 7200 Enterprise Manager Upload HTTP Port = 4889 - 4898 Enterprise Manager Upload HTTP SSL Port = 1159, 4899 - 4908 Enterprise Manager Central Console HTTP Port = 7788 - 7798 Enterprise Manager Central Console HTTP SSL Port = 7799 - 7809 Oracle Management Agent Port = 3872, 1830 - 1849 To verify if a port is free, run the following command: `netstat -anp \| grep <port no>`
Internet Connection Requirements	Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

Installation Procedure

This section describes the following:

Installing with Simple Configuration

To install Enterprise Manager Cloud Control with simple configuration, follow these steps:

Invoke the Enterprise Manager Cloud Control Installation Wizard
Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Chapter 4.
<Software_Location>/runInstaller
In this command, <Software_Location> is either the DVD location or the location where you have downloaded the software kit.
Enter My Oracle Support Details

(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).
If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.
Click Next.
Install Software Updates

On the Software Updates screen, select one of the following sources from where the software updates can be installed while the installation of the Enterprise Manager system is in progress. If you do not want to apply them now, then select Skip.
- (Recommended) Select Search for Updates, and then, select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location. Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.
  - If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes and if the software updates are available in /scratch/OracleHomes/Updates, then enter /scratch/OracleHomes/Updates.
  - If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /home/john and if the software updates are available in /home/john/Updates, then enter /home/john/Updates.
- Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.
  Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch
Note:
If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches. To do so, log in to Enterprise Manager Cloud Control, and from the Setup menu, select My Oracle Support, and then, click Set Credentials. On the My Oracle Support Preferred Credentials page, enter the credentials and click Apply.
Click Next.
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:
```
<system drive>\Program Files\Oracle\Inventory
```
Enter Oracle Inventory Details
On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.
1. Enter the full path to a directory where the inventory files and directories can be placed.
  Note:
  - The central inventory location you enter must NOT be on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1
  - If this is the first Oracle product on the host, then the default central inventory location is <home directory>/oraInventory. However, if you already have some Oracle products on the host, then the central inventory location can be found in the oraInst.loc file. The oraInst.loc file is located in the /etc directory for Linux and AIX, and in the /var/opt/oracle directory for Solaris, HP-UX, and Tru64.
2. Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.
Click Next.
Check Prerequisites

On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.
The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.
The status of the prerequisite check can be either Warning, Failed, or Succeeded.
- If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.
  If you prefer to hide the successful checks and view only the ones with Warning or Failed status, then click Hide Successful Checks.
- Although Oracle recommends you to investigate and correct the problems, if you are compelled to proceed without resolving them, then select Ignore to ignore the warnings and failures.
  However, all package requirements must be met or fixed before proceeding any further. Otherwise, the installation might fail.
Click Next.
Select Installation Type

On the Install Types screen, do the following:
1. Select Create a New Enterprise Manager System, and then, select Simple.
2. Validate or enter the middleware home.
  Note:
  - If you have Oracle WebLogic Server and Java Development Kit already installed, then ensure that they are of the supported releases—Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24+. If you have the supported releases, the installer automatically detects them and displays the absolute path to the middleware home where they are installed. In this case, validate the middleware home. If the location is incorrect, then enter the path to the correct location. Ensure that the middleware home you select or enter is a middleware home that does not have any Oracle homes for Oracle Management Service and Oracle Management Agent.
  - If you do not have Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24+, then the installer automatically installs them for you while installing the Enterprise Manager system. In this case, enter the absolute path to a directory where you want to have them installed. For example, /oracle/software/. Ensure that the directory you enter does not contain any files or subdirectories.
  - If you manually install Oracle WebLogic Server 11g Release 1 (10.3.5), then follow the guidelines outlined in Before You Begin.
Click Next.
Enter Configuration Details

On the Configuration Details screen, do the following:
1. Enter an administrator password, which can be used as a common password for configuring the Enterprise Manager Cloud Control.
  
  Note:
  Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
  The administrator password is used as a common password for SYSMAN user account, WebLogic user account, node manager user account, and also for authenticating new Oracle Management Agents that join the Enterprise Manager system.
2. Enter the fully qualified name of the host where the existing database resides, the database's listener port and its service name or system ID (SID), and the SYS user account's password.
  The installer uses this information to connect to the existing, certified Oracle Database for creating the SYSMAN schema. SYSMAN schema holds most of the relational data used in managing Enterprise Manager Cloud Control.
  
  Note:
  If any repository-related prerequisite check fails, see Appendix A to manually run the prerequisite check.
Click Next.
Note:
- If you are connecting to an Oracle RAC database, and if you have specified the virtual IP address of one of its nodes, then the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster. Update the connection string and click OK. If you want to test the connection, click Test Connection.
- If you see an error stating that the connection to the database failed with ORA-01017 invalid user name/password, then follow these steps to resolve the issue:
  (1) Verify that SYS password provided is valid.
  (2) Verify that the database initialization parameter REMOTE_LOGIN_PASSWORDFILE is set to Shared or Exclusive.
  (3) Verify that password file with the file name orapw<SID> exists in the <ORACLE_HOME>/dbs directory of the database home. If it does not, create a password file using the ORAPWD command.
Review and Install
On the Review screen, review the details you provided for the selected installation type.
- If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.
- After you verify the details, if you are satisfied, click Install to begin the installation process.
On the Install Progress screen, view the overall progress (in percentage) of the installation and the status of each of the configuration assistants. Configuration assistants are run for configuring the installed components of Enterprise Manager Cloud Control.
Note:
- If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and rerun the configuration assistant.
  For more information, see the appendix on troubleshooting tips in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
- If you accidently exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the OMS home to rerun the Configuration Assistant in silent mode. For Microsoft Windows platforms, invoke runConfig.bat script.
  $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<absolute_path_to_OMS_home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
Once the software binaries are copied and configured, you are prompted to run the allroot.sh script, and the oraInstRoot.sh script if this is the first Oracle product installation on the host. Open another window, log in as root, and manually run the scripts.
If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script.
On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.
For more information about this installation, refer to the following file in the OMS home:
$<OMS_HOME>/install/setupinfo.txt

Note:

If the installation fails for some reason, review the log files available in the following locations of the OMS home:

$oraInventory/logs/installActions<timestamp>.log
$oraInventory/logs/emdbprereqs/LATEST
$<OMS_HOME>/cfgtoollogs/oui/installActions<timestamp>.log
$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log
Configuration Assistant-Related Log Files:
The OMS Configuration Assistant-related log files are available at:
$<OMS_HOME>/cfgtoollogs/omsca/*.*
The Repository Configuration Assistant-related log files are available at:
$<OMS_HOME>/sysman/log/schemamanager

Installing with Advanced Configuration

To install Enterprise Manager Cloud Control with advanced configuration, follow these steps:

Invoke the Enterprise Manager Cloud Control Installation Wizard
Invoke the installation wizard as a user who belongs to the oinstall group you created following the instructions in Chapter 4.
<Software_Location>/runInstaller
In this command, <Software_Location> is either the DVD location or the location where you have downloaded the software kit.

Note:
For information about the additional, advanced options you can pass while invoking the installer, refer to Advanced Installer Options. To make yourself aware of some installation-related known issues, see Limitations.
Enter My Oracle Support Details

(Optional) On the My Oracle Support Details screen, enter your My Oracle Support credentials to enable Oracle Configuration Manager. If you do not want to enable Oracle Configuration Manager now, go to Step (3).
If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support.
Click Next.
Install Software Updates

On the Software Updates screen, select one of the following sources from where the software updates can be installed while the installation of the Enterprise Manager system is in progress. If you do not want to apply them now, then select Skip.
- (Recommended) Select Search for Updates, and then, select Local Directory if you have already manually downloaded the software updates to an accessible local or remote location.
  Enter the location where the updates are available, and click Search for Updates. To search the computer and select the location, click Browse. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch.
  - If the updates have been downloaded to the default location, then select or enter the full path to the scratch path location. For example, if the scratch path location is /scratch/OracleHomes and if the software updates are available in /scratch/OracleHomes/Updates, then enter /scratch/OracleHomes/Updates.
  - If the software updates have been downloaded to a custom location, then select or enter the full path to the custom location. For example, if the custom location is /home/john and if the software updates are available in /home/john/Updates, then enter /home/john/Updates.
- Select Search for Updates, and then, select My Oracle Support if you want the installer to connect to My Oracle Support and automatically download the updates from there.
  Enter the My Oracle Support account user name and password, and click Search for Updates. Once the search results appear with patch numbers and their details, click the patch number to view the ReadMe associated with that patch
Note:
If you choose to skip installing the software updates during installation by not providing the My Oracle Support credentials, you can always register the credentials later using the Enterprise Manager Cloud Control console and view the recommended security patches. To do so, in Cloud Control, from the Setup menu, select Security, and then, click Preferred Credentials. On the Preferred Credentials page, click Set MOS Credentials and register the credentials.
Click Next.
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on UNIX operating system, then the Oracle Inventory screen appears. For details, see step (6). Otherwise, the Check Prerequisites screen appears. For details, see step (8).
If Enterprise Manager Cloud Control is the first Oracle product you are installing on the host that is running on Microsoft Windows operating system, then the Oracle Inventory screen does not appear. On Microsoft Windows, the following is the default inventory directory:
```
<system drive>\Program Files\Oracle\Inventory
```
Enter Oracle Inventory Details
On the Oracle Inventory screen, do the following. You will see this screen only if this turns out to be your first ever installation of an Oracle product on the host.
1. Enter the full path to a directory where the inventory files and directories can be placed.
  Note:
  - The central inventory location you enter must NOT be on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1
  - If this is the first Oracle product on the host, then the default central inventory location is <home directory>/oraInventory. However, if you already have some Oracle products on the host, then the central inventory location can be found in the oraInst.loc file. The oraInst.loc file is located in the /etc directory for Linux and AIX, and in the /var/opt/oracle directory for Solaris, HP-UX, and Tru64.
2. Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.
Click Next.
Check Prerequisites

On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful installation.
The installation wizard runs the prerequisite checks automatically when you come to this screen. It checks for the required operating system patches, operating system packages, and so on.
The status of the prerequisite check can be either Warning, Failed, or Succeeded.
If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the installation. The screen provides details on why the prerequisites failed and how you can resolve them. After you correct the problems, return to this screen and click Rerun to check the prerequisites again.
If you prefer to hide the successful checks and view only the ones with Warning or Failed status, then click Hide Successful Checks.

Note:
You can choose to ignore the checks with Warning status by clicking Ignore. However, all package requirements must be met or fixed before proceeding any further.
Click Next.
Select Installation Type

On the Install Types screen, do the following:
1. Select Create a New Enterprise Manager System, and then, select Advanced.
2. Validate or enter the middleware home.
  Note:
  - If you have Oracle WebLogic Server and Java Development Kit already installed, then ensure that they are of the supported releases—Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24+. If you have the supported releases, the installer automatically detects them and displays the absolute path to the middleware home where they are installed. In this case, validate the middleware home. If the location is incorrect, then enter the path to the correct location. Ensure that the middleware home you select or enter is a middleware home that does not have any Oracle homes for Oracle Management Service and Oracle Management Agent.
  - If you do not have Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24+, then the installer automatically installs them for you while installing the Enterprise Manager system. In this case, enter the absolute path to a directory where you want to have them installed. For example, /oracle/software/. Ensure that the directory you enter does not contain any files or subdirectories.
  - If you manually install Oracle WebLogic Server 11g Release 1 (10.3.5), then follow the guidelines outlined in Before You Begin.
Click Next.
Select Plug-Ins

On the Select Plug-Ins screen, select the optional plug-ins you want to install from the software kit (DVD, downloaded software) while installing the Enterprise Manager system. The screen lists the mandatory plug-ins as well as the optional plug-ins. The grayed rows indicate the mandatory plug-ins that will be installed.

Note:
During installation, if you want to install a plug-in that is not available in the software kit, then refer to Advanced Installer Options for the point that describes how you can install additional plug-ins.
Click Next.
Enter WebLogic Server Configuration Details

On the WebLogic Server Configuration Details screen, enter the credentials for the WebLogic Server user account and the Node Manager user account, and validate the path to the Oracle Management Service instance base location.

Note:
Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
By default, the WebLogic Domain name is GCDomain, and the Node Manager name is nodemanager. These are non-editable fields. The installer uses this information for creating Oracle WebLogic Domain and other associated components such as the admin server, the managed server, and the node manager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.
Click Next.
Enter Database Connection Details

On the Database Connection Details screen, enter the fully qualified name of the host where your existing, certified Oracle Database resides, its listener port and its service name or system ID (SID), and the SYS user account's password.
The installer uses this information to connect to the existing, certified Oracle Database for creating the SYSMAN schema. SYSMAN schema holds most of the relational data used in managing Enterprise Manager Cloud Control.

Note:
If any repository-related prerequisite check fails, see Appendix A to manually run the prerequisite check.
Click Next.
Note:
- If you are connecting to an Oracle RAC database, and if you have specified the virtual IP address of one of its nodes, then the installation wizard prompts you with a Connection String dialog and requests you to update the connection string with information about the other nodes that are part of the cluster. Update the connection string and click OK. If you want to test the connection, click Test Connection.
- If you see an error stating that the connection to the database failed with ORA-01017 invalid user name/password, then follow these steps to resolve the issue:
  (1) Verify that SYS password provided is valid.
  (2) Verify that the database initialization parameter REMOTE_LOGIN_PASSWORDFILE is set to Shared or Exclusive.
  (3) Verify that password file with the file name orapw<SID> exists in the <ORACLE_HOME>/dbs directory of the database home. If it does not, create a password file using the ORAPWD command.
Enter Repository Configuration Details

On the Repository Configuration Details screen, do the following:
1. For SYSMAN Password, enter a password for creating the SYSMAN user account. The SYSMAN user account is used for creating the SYSMAN schema, which holds most of the relational data used in managing Enterprise Manager Cloud Control. SYSMAN is also the super administrator for Enterprise Manager Cloud Control.
  
  Note:
  Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
2. For Registration Password, enter a password for registering the new Management Agents that join the Enterprise Manager system.
  
  Note:
  Ensure that your password contains at least 8 characters without any spaces, begins with a letter, and includes at least one numeric value.
3. For Management Tablespace, enter the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored. The installer uses this information for storing data about the monitored targets, their metrics, and so on. Ensure that the specified path leads up to the file name.
  For example, /u01/oracle/prod/oradata/mgmt.dbf
4. For Configuration Data Tablespace, enter the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf) can be stored. This is required for storing configuration information collected from the monitored targets. Ensure that the specified path leads up to the file name.
  For example, /u01/oracle/prod/oradata/mgmt_ecm_depot1.dbf
5. For JVM Diagnostics Data Tablespace, enter the full path to a location where the data file for JVM Diagnostics data tablespace (mgmt_ad4j.dbf) can be stored. Ensure that the specified path leads up to the file name. Enterprise Manager Cloud Control requires this data file to store monitoring data related to JVM Diagnostics and Application Dependency Performance (ADP).
  For example, /u01/oracle/prod/oradata/mgmt_ad4j.dbf
Note:
If you are configuring the Management Repository on a database that uses Oracle Automatic Storage Management (Oracle ASM) for storage, then when you enter the data file location, only the disk group is used for creating the tablespaces. For example, if you specify +DATA/a.dbf, then only +DATA is used for creating the tablespaces on Oracle ASM, and the exact location of the data file on the disk group is decided by Oracle Managed Files.
Click Next.
Customize Ports

On the Port Configuration Details screen, customize the ports to be used for various components.

Note:
If all the ports on this screen appear as -1, then it indicates that the installer is unable to bind the ports on the host. To resolve this issue, exit the installer, verify the host name and the IP configuration of this host (ensure that the IP address of the host is not being used by another host), restart the installer, and try again.
You can enter a free custom port that is either within or outside the port range recommended by Oracle.
To verify if a port is free, run the following command:
netstat -anp | grep <port no>
However, the custom port must be greater than 1024 and lesser than 65535. Alternatively, if you already have the ports predefined in a staticports.ini file and if you want to use those ports, then click Import staticports.ini File and select the file.

Note:
If the staticports.ini file is passed during installation, then by default, the ports defined in the staticports.ini file are displayed. Otherwise, the first available port from the recommended range is displayed.
Click Next.
Review and Install
On the Review screen, review the details you provided for the selected installation type.
- If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes.
- After you verify the details, if you are satisfied, click Install to begin the installation process.
On the Install Progress screen, view the overall progress (in percentage) of the installation and the status of each of the Configuration Assistants. Configuration Assistants are run for configuring the installed components of Enterprise Manager Cloud Control.
Note:
- If a configuration assistant fails, the installer stops and none of the subsequent configuration assistants are run. Resolve the issue and rerun the configuration assistant.
  For more information, see the appendix on troubleshooting tips in the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
- If you accidently exit the installer before clicking Retry, then do NOT restart the installer to reach the same screen; instead, invoke the runConfig.sh script from the OMS home to rerun the Configuration Assistant in silent mode. For Microsoft Windows platforms, invoke runConfig.bat script.
  $<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<absolute_path_to_OMS_home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
Once the software binaries are copied and configured, you are prompted to run the allroot.sh script, and the oraInstRoot.sh script if this is the first Oracle product installation on the host. Open another window, log in as root, and manually run the scripts.
If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script. You will directly reach the Finish screen as described in Step (25).
On the Finish screen, you should see information pertaining to the installation of Enterprise Manager. Review the information and click Close to exit the installation wizard.
For more information about this installation, refer to the following file available in the OMS home:
$<OMS_HOME>/install/setupinfo.txt

Note:

If the installation fails for some reason, review the log files available in the following locations of the OMS home:

$oraInventory/logs/installActions<timestamp>.log
$oraInventory/logs/emdbprereqs/LATEST
$<OMS_HOME>/cfgtoollogs/oui/installActions<timestamp>.log
$<OMS_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log
Configuration Assistant-Related Log Files:
The OMS Configuration Assistant-related log files are available at:
$<OMS_HOME>/cfgtoollogs/omsca/*.*
The Repository Configuration Assistant-related log files are available at:
$<OMS_HOME>/sysman/log/schemamanager

Advanced Installer Options

The following are some additional, advanced options you can pass while invoking the installer:

By default, GCDomain is the default name used for creating the WebLogic Domain. To override this and use a custom WebLogic Domain name, invoke the installer with the WLS_DOMAIN_NAME option, and enter a unique custom name.
For example, if you want to use the custom name EMDomain, then run the following command:
./runInstaller WLS_DOMAIN_NAME=EMDomain
By default, a Provisioning Advisor Framework (PAF) staging directory is created for copying the Software Library entities related to the deployment procedures. By default, this location is the scratch path location (/tmp). The location is used only for provisioning activities—entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.
If you want to override this location with a custom location, then invoke the installer with the EM_STAGE_DIR option, and enter a unique custom location.
For example,
./runInstaller EM_STAGE_DIR=/home/john/software/oracle/pafdir
During installation, if you want to install some plug-ins that are not in the software kit (DVD, downloaded software), then follow these steps:
1. Manually download the plug-ins from the Enterprise Manager download page on OTN, and store them in an accessible location:
  http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html
2. Invoke the installer with the following option, and pass the location where the plug-ins you want to install are available:
  ./runInstaller -pluginLocation <absolute_path_to_plugin_software_location>
  This displays a list of plug-ins available in the software kit (DVD, downloaded software) as well as the plug-ins available in this custom location. You can choose the ones you want to install.
After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer with START_OMS and b_startAgent options, and set them to TRUE or FALSE depending on what you want to control.
For example, if you do not want the Management Agent to start automatically, then run the following command:
./runInstaller START_OMS=TRUE b_startAgent=FALSE
To understand the limitations involved with this advanced option, see Limitations.
While installing on hosts having multiple IP addresses, the host name is derived from the ORACLE_HOSTNAME variable that is passed while invoking the installer. Ensure that the host name you enter does not have underscores.
For example:
./runInstaller ORACLE_HOSTNAME=host1.foo.com

Limitations

When you use START_OMS and b_startAgent as advanced options to control the way the OMS and the Management Agent start up automatically, sometimes the Management Agent and the host on which it was installed do not appear as targets in the Cloud Control console.
Table 6-2 lists the different combinations of these advanced options, and describes the workaround to be followed for each combination:

Table 6-2 Advanced Options and Workarounds

Advanced Option	Workaround
`START_OMS=FALSE` `b_startAgent=FALSE`	Start the OMS: `$<OMS_HOME>/bin/emctl start oms` Secure the Management Agent: `$<AGENT_HOME>/bin/emctl secure agent` Start the Management Agent: `$<AGENT_HOME>/bin/emctl start agent` Add the targets: `$<AGENT_HOME>/bin/emctl config agent addinternaltargets` Upload the targets: `$<AGENT_HOME>/bin/emctl upload agent` Manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface Guide.
`START_OMS=TRUE` `b_startAgent=FALSE`	Secure the Management Agent: `$<AGENT_HOME>/bin/emctl secure agent` Start the Management Agent: `$<AGENT_HOME>/bin/emctl start agent` Add the targets: `$<AGENT_HOME>/bin/emctl config agent addinternaltargets` Upload the targets: `$<AGENT_HOME>/bin/emctl upload agent`
`START_OMS=FALSE` `b_startAgent=TRUE`	Start the OMS: `$<OMS_HOME>/bin/emctl start oms` Secure the Management Agent: `$<AGENT_HOME>/bin/emctl secure agent` Add the targets: `$<AGENT_HOME>/bin/emctl config agent addinternaltargets` Upload the targets: `$<AGENT_HOME>/bin/emctl upload agent` Manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface Guide.

After You Install

After you install, do the following:

(Only for UNIX Operating Systems) If you did not run the allroot.sh script when the installer prompted you to do so, then run them manually now:
- If this is the first Oracle product you just installed on the host, then run the oraInstroot.sh script from the inventory location specified in the oraInst.loc file that is available in the Management Agent home.
  For example, if the inventory location specified in the oraInst.loc file is $HOME/oraInventory, then run the following command:
  $HOME/oraInventory/oraInstRoot.sh
  
  Note:
  If you are not a root user, then use SUDO to change to a root user. For example, run the following command: /usr/local/bin/sudo $HOME/oraInventory/oraInstRoot.sh
- Run the allroot.sh script from the OMS home:
  $<OMS_HOME>/allroot.sh
  
  Note:
  If you are not a root user, then use SUDO to change to a root user. For example, run the following command: /usr/local/bin/sudo $<OMS_HOME>/allroot.sh
Verify the installation:
1. Navigate to the OMS home and run the following command to see a message that confirms that OMS is up and running.
  $<OMS_HOME>/bin/emctl status oms
2. Navigate to the Management Agent home and run the following command to see a message that confirms that the Management Agent is up and running.
  $<AGENT_HOME>/bin/emctl status agent
3. Navigate to the Management Agent home and run the following command to see a message that confirms that EMD upload completed successfully.
  $<AGENT_HOME>/bin/emctl upload agent
Note:
By default, you can access Enterprise Manager Cloud Control only using the HTTPS protocol. If you want to use the HTTP protocol, then unlock it by running the following command from the OMS home: emctl secure unlock -console
Verify if all the plug-ins were installed successfully. To do so, access the following log file from the Management Agent home, and search for the sentence WARN:Plugin configuration has failed.
$<AGENT_HOME>/cfgtoollogs/cfgfw/CfmLogger-<timestamp>.log
If you find the sentence, resolve the issue by running the AgentPluginDeploy.pl script from the Management Agent home.
$<MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/perl/bin/perl <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome <MIDDLEWARE_HOME>/agent/core/12.1.0.1.0 -agentDir <AGENT_BASE_DIR> -pluginIdsInfoFile <AGENT_BASE_DIR>/plugins.txt -action configure -emStateDir <AGENT_INSTANCE_HOME>
For example,
/u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/perl/bin/perl /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/bin/AgentPluginDeploy.pl -oracleHome /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/ -agentDir /u01/app/Oracle/Middleware/agent -pluginIdsInfoFile /u01/app/Oracle/Middleware/agent/core/12.1.0.1.0/sysman/install/plugins.txt -action configure -emStateDir /u01/app/Oracle/Middleware/agent/agent_inst
(Optional) If the repository prerequisites had failed, and if you had manually run the EM Prerequisite Kit and taken corrective actions to meet the repository requirements, then run the utility again to reset the repository settings to what it had originally:
/install/requisites/bin/emprereqkit -executionType install -prerequisiteXMLLoc <prereq_xml_location> -connectString <connect_string> -dbUser SYS -dbPassword <db_password> -reposUser sysman -reposPassword <repo_user_password> -dbRole sysdba -runPrerequisites -runPostCorrectiveActions -useHistory

Note:
If you had run the installation wizard and let the installation wizard take corrective actions to correct the repository settings, and if you had exited the wizard without completing the installation process, then remember that the repository settings might not reset to their original values because you abruptly ended the installation. In this case, before invoking the installation wizard again, run this command to manually reset the values.
By default, the following targets get automatically discovered and monitored in the Enterprise Manager Cloud Control console:
- Oracle WebLogic Domain (for example, GCDomain)
- Oracle WebLogic AdminServer
- Oracle WebLogic Server
- Oracle Web Tier
- Application deployments, one for the Enterprise Manager Cloud Control console and one for the platform background services.
- Oracle Management Service
- Oracle Management Repository
- Oracle Management Agent
- The host on which you installed Enterprise Manager Cloud Control
However, the other targets running on that host and other hosts do not get automatically discovered and monitored. To monitor the other targets, you need to add them to Enterprise Manager Cloud Control either using the Auto Discovery Results page, the Add Targets Manually page, or the discovery wizards offered for the targets you want to monitor.
For information about discovering targets in Enterprise Manager Cloud Control, refer to the chapter on adding targets in the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Configure your proxy server as described in .
(Optional) If you want to connect to another Management Repository, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]

Note:
On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not. For example, on Linux:
emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc '"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb)))"' -repos_user sysman
For example, on Microsoft Windows:
emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb))) -repos_user sysman
(Optional) If you want to change the SYSMAN password, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -change_repos_pwd

ALTER SYSTEM SQL COMMAND

ALTER SYSTEM

Purpose

Use the ALTER SYSTEM statement to dynamically alter your Oracle Database instance. The settings stay in effect as long as the database is mounted.

Prerequisites

You must have ALTER SYSTEM system privilege.

Syntax

alter_system::=

Description of the illustration alter_system.gif

(archive_log_clause ::=, checkpoint_clause::=, check_datafiles_clause::=, distributed_recov_clauses::=, end_session_clauses::=, quiesce_clauses::=, alter_system_security_clauses::=, shutdown_dispatcher_clause::=, alter_system_set_clause::=, alter_system_reset_clause::=)

archive_log_clause ::=

Description of the illustration archive_log_clause.gif

checkpoint_clause::=

Description of the illustration checkpoint_clause.gif

check_datafiles_clause::=

Description of the illustration check_datafiles_clause.gif

distributed_recov_clauses::=

Description of the illustration distributed_recov_clauses.gif

end_session_clauses::=

Description of the illustration end_session_clauses.gif

quiesce_clauses::=

Description of the illustration quiesce_clauses.gif

alter_system_security_clauses::=

Description of the illustration alter_system_security_clauses.gif

shutdown_dispatcher_clause::=

Description of the illustration shutdown_dispatcher_clause.gif

alter_system_set_clause::=

Description of the illustration alter_system_set_clause.gif

alter_system_reset_clause::=

Description of the illustration alter_system_reset_clause.gif

Semantics

archive_log_clause

The archive_log_clause manually archives redo log files or enables or disables automatic archiving. To use this clause, your instance must have the database mounted. The database can be either open or closed unless otherwise noted.

INSTANCE Clause

This clause is relevant only if you are using Oracle Database with the Real Application Clusters option. Specify the name of the instance for which you want the redo log file group to be archived. The instance name is a string of up to 80 characters. Oracle Database automatically determines the thread that is mapped to the specified instance and archives the corresponding redo log file group. If no thread is mapped to the specified instance, then Oracle Database returns an error.
In earlier releases, you could identify the redo log file group to be archived by thread as well as instance. That syntax is now supported for backward compatibility only. The INSTANCE clause achieves the same purpose and is easier to use.

SEQUENCE Clause

Specify SEQUENCE to manually archive the online redo log file group identified by the log sequence number integer in the specified thread. If you omit the THREAD parameter, then Oracle Database archives the specified group from the thread assigned to your instance.

CHANGE Clause

Specify CHANGE to manually archive the online redo log file group containing the redo log entry with the system change number (SCN) specified by integer in the specified thread. If the SCN is in the current redo log file group, then Oracle Database performs a log switch. If you omit the THREAD parameter, then Oracle Database archives the groups containing this SCN from all enabled threads.
You can use this clause only when your instance has the database open.

CURRENT Clause

Specify CURRENT to manually archive the current redo log file group of the specified thread, forcing a log switch. If you omit the THREAD parameter, then Oracle Database archives all redo log file groups from all enabled threads, including logs previous to current logs. You can specify CURRENT only when the database is open.
NOSWITCH Specify NOSWITCH if you want to manually archive the current redo log file group without forcing a log switch. This setting is used primarily with standby databases to prevent data divergence when the primary database shuts down. Divergence implies the possibility of data loss in case of primary database failure.
You can use the NOSWITCH clause only when your instance has the database mounted but not open. If the database is open, then this operation closes the database automatically. You must then manually shut down the database before you can reopen it.

GROUP Clause

Specify GROUP to manually archive the online redo log file group with the GROUP value specified by integer. You can determine the GROUP value for a redo log file group by querying the data dictionary view DBA_LOG_GROUPS. If you specify both the THREAD and GROUP parameters, then the specified redo log file group must be in the specified thread.

LOGFILE Clause

Specify LOGFILE to manually archive the online redo log file group containing the redo log file member identified by 'filename'. If you specify both the THREAD and LOGFILE parameters, then the specified redo log file group must be in the specified thread.
If the database was mounted with a backup controlfile, then specify USING BACKUP CONTROLFILE to permit archiving of all online logfiles, including the current logfile.
Restriction on the LOGFILE clause You must archive redo log file groups in the order in which they are filled. If you specify a redo log file group for archiving with the LOGFILE parameter, and earlier redo log file groups are not yet archived, then Oracle Database returns an error.

NEXT Clause

Specify NEXT to manually archive the next online redo log file group from the specified thread that is full but has not yet been archived. If you omit the THREAD parameter, then Oracle Database archives the earliest unarchived redo log file group from any enabled thread.

ALL Clause

Specify ALL to manually archive all online redo log file groups from the specified thread that are full but have not been archived. If you omit the THREAD parameter, then Oracle Database archives all full unarchived redo log file groups from all enabled threads.

START Clause

In earlier releases, this clause enabled automatic archiving of redo log file groups for the thread assigned to your instance. This clause has been deprecated, because Oracle Database automatically enables automatic archiving of redo log file groups. This clause has no effect. If you specify it, Oracle Database writes a message to the alert log.

TO location Clause

Specify TO 'location' to indicate the primary location to which the redo log file groups are archived. The value of this parameter must be a fully specified file location following the conventions of your operating system. If you omit this parameter, then Oracle Database archives the redo log file group to the location specified by the initialization parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DEST_n.

STOP Clause

In earlier releases, this clause disabled automatic archiving of redo log file groups for the thread assigned to your instance. This clause has been deprecated. It has no effect, and if you specify it, Oracle Database writes a message to the alert log.

checkpoint_clause

Specify CHECKPOINT to explicitly force Oracle Database to perform a checkpoint, ensuring that all changes made by committed transactions are written to datafiles on disk. You can specify this clause only when your instance has the database open. Oracle Database does not return control to you until the checkpoint is complete.
GLOBAL In a Real Application Clusters environment, this setting causes Oracle Database to perform a checkpoint for all instances that have opened the database. This is the default.
LOCAL In a Real Application Clusters environment, this setting causes Oracle Database to perform a checkpoint only for the thread of redo log file groups for the instance from which you issue the statement.

See Also:

"Forcing a Checkpoint: Example"

check_datafiles_clause

In a distributed database system, such as a Real Application Clusters environment, this clause updates an instance's SGA from the database control file to reflect information on all online datafiles.

Specify GLOBAL to perform this synchronization for all instances that have opened the database. This is the default.
Specify LOCAL to perform this synchronization only for the local instance.

Your instance should have the database open.

end_session_clauses

The end_session_clauses give you several ways to end the current session.

DISCONNECT SESSION Clause

Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever). To use this clause, your instance must have the database open. You must identify the session with both of the following values from the V$SESSION view:

For integer1, specify the value of the SID column.
For integer2, specify the value of the SERIAL# column.

If system parameters are appropriately configured, then application failover will take effect.

The POST_TRANSACTION setting allows ongoing transactions to complete before the session is disconnected. If the session has no ongoing transactions, then this clause has the same effect described for as KILL SESSION.
The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
- If you also specify POST_TRANSACTION and the session has ongoing transactions, then the IMMEDIATE keyword is ignored.
- If you do not specify POST_TRANSACTION, or you specify POST_TRANSACTION but the session has no ongoing transactions, then this clause has the same effect as described for KILL SESSION IMMEDIATE.
  
  See Also:
  "Disconnecting a Session: Example"

KILL SESSION Clause

The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources. To use this clause, your instance must have the database open, and your session and the session to be terminated must be on the same instance. You must identify the session with both of the following values from the V$SESSION view:

For integer1, specify the value of the SID column.
For integer2, specify the value of the SERIAL# column.

If the session is performing some activity that must be completed, such as waiting for a reply from a remote database or rolling back a transaction, then Oracle Database waits for this activity to complete, marks the session as terminated, and then returns control to you. If the waiting lasts a minute, then Oracle Database marks the session to be terminated and returns control to you with a message that the session is marked to be terminated. The PMON background process then marks the session as terminated when the activity is complete.
Whether or not the session has an ongoing transaction, Oracle Database does not recover the entire session state until the session user issues a request to the session and receives a message that the session has been terminated.

See Also:

"Terminating a Session: Example"

IMMEDIATE Specify IMMEDIATE to instruct Oracle Database to roll back ongoing transactions, release all session locks, recover the entire session state, and return control to you immediately.

distributed_recov_clauses

The DISTRIBUTED RECOVERY clause lets you enable or disable distributed recovery. To use this clause, your instance must have the database open.
ENABLE Specify ENABLE to enable distributed recovery. In a single-process environment, you must use this clause to initiate distributed recovery.
You may need to issue the ENABLE DISTRIBUTED RECOVERY statement more than once to recover an in-doubt transaction if the remote node involved in the transaction is not accessible. In-doubt transactions appear in the data dictionary view DBA_2PC_PENDING.

DISABLE Specify DISABLE to disable distributed recovery.

FLUSH SHARED_POOL Clause

The FLUSH SHARED POOL clause lets you clear all data from the shared pool in the system global area (SGA). The shared pool stores

Cached data dictionary information and
Shared SQL and PL/SQL areas for SQL statements, stored procedures, function, packages, and triggers.

This statement does not clear shared SQL and PL/SQL areas for items that are currently being executed. You can use this clause regardless of whether your instance has the database dismounted or mounted, open or closed.

See Also:

"Clearing the Shared Pool: Example"

FLUSH BUFFER_CACHE Clause

The FLUSH BUFFER_CACHE clause lets you clear all data from the buffer cache in the system global area (SGA).

Caution:

This clause is intended for use only on a test database. Do not use this clause on a production database, because as a result of this statement, subsequent queries will have no hits, only misses.

This clause is useful if you need to measure the performance of rewritten queries or a suite of queries from identical starting points.

SWITCH LOGFILE Clause

The SWITCH LOGFILE clause lets you explicitly force Oracle Database to begin writing to a new redo log file group, regardless of whether the files in the current redo log file group are full. When you force a log switch, Oracle Database begins to perform a checkpoint but returns control to you immediately rather than when the checkpoint is complete. To use this clause, your instance must have the database open.

See Also:

"Forcing a Log Switch: Example"

SUSPEND | RESUME

The SUSPEND clause lets you suspend all I/O (datafile, control file, and file header) as well as queries, in all instances, enabling you to make copies of the database without having to handle ongoing transactions.
Restrictions on SUSPEND and RESUME SUSPEND and RESUME are subject to the following restrictions:

Do not use this clause unless you have put the database tablespaces in hot backup mode.
Do not terminate the session that issued the ALTER SYSTEM SUSPEND statement. An attempt to reconnect while the system is suspended may fail because of recursive SQL that is running during the SYS login.
If you start a new instance while the system is suspended, then that new instance will not be suspended.

The RESUME clause lets you make the database available once again for queries and I/O.

quiesce_clauses

Use the QUIESCE RESTRICTED and UNQUIESCE clauses to put the database in and take it out of the quiesced state. This state enables database administrators to perform administrative operations that cannot be safely performed in the presence of concurrent transactions, queries, or PL/SQL operations.

Note:

The QUIESCE RESTRICTED clause is valid only if the Database Resource Manager is installed and only if the Resource Manager has been on continuously since database startup in any instances that have opened the database.

If multiple QUIESCE RESTRICTED or UNQUIESCE statements issue at the same time from different sessions or instances, then all but one will receive an error.

QUIESCE RESTRICTED

Specify QUIESCE RESTRICTED to put the database in the quiesced state. For all instances with the database open, this clause has the following effect:

Oracle Database instructs the Database Resource Manager in all instances to prevent all inactive sessions (other than SYS and SYSTEM) from becoming active. No user other than SYS and SYSTEM can start a new transaction, a new query, a new fetch, or a new PL/SQL operation.
Oracle Database waits for all existing transactions in all instances that were initiated by a user other than SYS or SYSTEM to finish (either commit or abort). Oracle Database also waits for all running queries, fetches, and PL/SQL procedures in all instances that were initiated by users other than SYS or SYSTEM and that are not inside transactions to finish. If a query is carried out by multiple successive OCI fetches, then Oracle Database does not wait for all fetches to finish. It waits for the current fetch to finish and then blocks the next fetch. Oracle Database also waits for all sessions (other than those of SYS or SYSTEM) that hold any shared resources (such as enqueues) to release those resources. After all these operations finish, Oracle Database places the database into quiesced state and finishes executing the QUIESCE RESTRICTED statement.
If an instance is running in shared server mode, then Oracle Database instructs the Database Resource Manager to block logins (other than SYS or SYSTEM) on that instance. If an instance is running in non-shared-server mode, then Oracle Database does not impose any restrictions on user logins in that instance.

During the quiesced state, you cannot change the Resource Manager plan in any instance.

UNQUIESCE

Specify UNQUIESCE to take the database out of quiesced state. Doing so permits transactions, queries, fetches, and PL/SQL procedures that were initiated by users other than SYS or SYSTEM to be undertaken once again. The UNQUIESCE statement does not have to originate in the same session that issued the QUIESCE RESTRICTED statement.

alter_system_security_clauses

The alter_system_security_clauses let you control access to the instance.

RESTRICTED SESSION

The RESTRICTED SESSION clause lets you restrict logon to Oracle Database. You can use this clause regardless of whether your instance has the database dismounted or mounted, open or closed.

Specify ENABLE to allow only users with RESTRICTED SESSION system privilege to log on to Oracle Database. Existing sessions are not terminated.
This clause applies only to the current instance. Therefore, in a Real Application Clusters environment, authorized users without the RESTRICTED SESSION system privilege can still access the database by way of other instances.
Specify DISABLE to reverse the effect of the ENABLE RESTRICTED SESSION clause, allowing all users with CREATE SESSION system privilege to log on to Oracle Database. This is the default.

See Also:

"Restricting Sessions: Example"

SET ENCRYPTION WALLET Clause

Use this clause to manage database access to information in the server wallet. Although this statement begins with the keyword ALTER, an ALTER SYSTEM SET ENCRYPTION WALLET statement is not a DDL clause. However, you cannot roll back such a statement.
OPEN When you specify this clause, the database uses the specified password to load information from the server wallet into memory for database access for the duration of the instance. This clause lets the database retrieve keys from the server wallet without an SSO wallet. If the server wallet is not available or is already open, the database returns an error.
CLOSE Use this clause to remove the server wallet information from memory.

SET ENCRYPTION KEY Clause

Use this clause to generate a new encryption key and to set it as the current transparent data encryption master key. This clause also loads information from the server wallet into memory for database access. The certificate_id is the integer that identifies the certificate. It is not required if you are using basic keys, but it is required if you are using PKI-based keys. You can find this value by querying the CERT_ID column of the V$WALLET dynamic performance view. For password, specify the password used to connect to the security module. If you specify an invalid certificate_id or password, then the database returns an error.
An ALTER SYSTEM SET KEY statement is a DDL statement and will automatically commit any pending transactions in the schema.
You must set both an encryption wallet and an encryption key to use the transparent data encryption feature.

See Also:

Oracle Advanced Security Administrator's Guide for more information on using the server wallet and encryption keys and on transparent data encryption
the description of the CREATE TABLE "ENCRYPT encryption_spec " for information on using that feature to encrypt table columns
"Establishing a Wallet and Encryption Key"

shutdown_dispatcher_clause

The SHUTDOWN clause is relevant only if your system is using the shared server architecture of Oracle Database. It shuts down a dispatcher identified by dispatcher_name.

Note:

Do not confuse this clause with the SQL*Plus command SHUTDOWN, which is used to shut down the entire database.

The dispatcher_name must be a string of the form 'Dxxx', where xxx indicates the number of the dispatcher. For a listing of dispatcher names, query the NAME column of the V$DISPATCHER dynamic performance view.

If you specify IMMEDIATE, then the dispatcher stops accepting new connections immediately and Oracle Database terminates all existing connections through that dispatcher. After all sessions are cleaned up, the dispatcher process shuts down.
If you do not specify IMMEDIATE, then the dispatcher stops accepting new connections immediately but waits for all its users to disconnect and for all its database links to terminate. Then it shuts down.

Specify REGISTER to instruct the PMON background process to register the instance with the listeners immediately. If you do not specify this clause, then registration of the instance does not occur until the next time PMON executes the discovery routine. As a result, clients may not be able to access the services for as long as 60 seconds after the listener is started.

See Also:

Oracle Database Concepts and Oracle Net Services Administrator's Guide for information on the PMON background process and listeners

alter_system_set_clause

The alter_system_set_clause lets you set or reset the value of any initialization parameter. The parameters are described in "Initialization Parameters and ALTER SYSTEM".
The ability to change initialization parameter values depends on whether you have started up the database with a traditional client-side initialization parameter file (pfile) or with a server parameter file (spfile). To determine whether you can change the value of a particular parameter, query the ISSYS_MODIFIABLE column of the V$PARAMETER dynamic performance view.
When setting a parameter value, you can specify additional settings as follows:

COMMENT

The COMMENT clause lets you associate a comment string with this change in the value of the parameter. If you also specify SPFILE, then this comment will appear in the parameter file to indicate the most recent change made to this parameter.

DEFERRED

The DEFERRED keyword sets or modifies the value of the parameter for future sessions that connect to the database. Current sessions retain the old value.
You must specify DEFERRED if the value of the ISSYS_MODIFIABLE column of V$PARAMETER for this parameter is DEFERRED. If the value of that column is IMMEDIATE, then the DEFERRED keyword in this clause is optional. If the value of that column is FALSE, then you cannot specify DEFERRED in this ALTER SYSTEM statement.

See Also:

Oracle Database Reference for information on the V$PARAMETER dynamic performance view

SCOPE

The SCOPE clause lets you specify when the change takes effect. Scope depends on whether you started up the database using a client-side parameter file (pfile) or server parameter file (spfile).
MEMORY MEMORY indicates that the change is made in memory, takes effect immediately, and persists until the database is shut down. If you started up the database using a parameter file (pfile), then this is the only scope you can specify.
SPFILE SPFILE indicates that the change is made in the server parameter file. The new setting takes effect when the database is next shut down and started up again. You must specify SPFILE when changing the value of a static parameter that is described as not modifiable in Oracle Database Reference.
BOTH BOTH indicates that the change is made in memory and in the server parameter file. The new setting takes effect immediately and persists after the database is shut down and started up again.
If a server parameter file was used to start up the database, then BOTH is the default. If a parameter file was used to start up the database, then MEMORY is the default, as well as the only scope you can specify.

SID

The SID clause is relevant only in a Real Application Clusters environment. This clause lets you specify the SID of the instance where the value will take effect.

Specify SID = '*' if you want Oracle Database to change the value of the parameter for all instances.
Specify SID = 'sid' if you want Oracle Database to change the value of the parameter only for the instance sid. This setting takes precedence over previous and subsequent ALTER SYSTEM SET statements that specify SID = '*'.

If you do not specify this clause:

If the instance was started up with a pfile (client-side initialization parameter file), then Oracle Database assumes the SID of the current instance.
If the instance was started up with an spfile (server parameter file), then Oracle Database assumes SID = '*'.

If you specify an instance other than the current instance, then Oracle Database sends a message to that instance to change the parameter value in the memory of that instance.

See Also:

Oracle Database Reference for information about the V$PARAMETER view

alter_system_reset_clause

In a Real Application Clusters (RAC) environment, the alter_system_reset_clause gives you separate control for an individual instance over parameters that may have been set for all instances in a server parameter file. The SCOPE clause has the same behavior as described for the alter_system_set_clause.
SID Specify the SID clause to remove a previously specified setting of this parameter for your instance--that is, a previous ALTER SYSTEM SET ... SID = 'sid' statement. (In a non-RAC environment, you can specify SID = '*' for this clause.) Your instance will assume the value of the parameter as specified in a previous or subsequent ALTER SYSTEM SET ... SID = '*' statement.

See Also:

Oracle Real Application Clusters Administrator's Guide for information on setting parameter values for an individual instance in a Real Application Clusters environment

Initialization Parameters and ALTER SYSTEM

You can change the value of many initialization parameters for the current instance, whether you have started the database with a traditional client-side parameter file (pfile) or with a server parameter file (spfile). Oracle Database Reference indicates these parameters in the "Modifiable" category of each parameter description. If you are using a pfile, then the change will persist only for the duration of the instance. However, if you have started the database with an spfile, then you can change the value of the parameter in the spfile itself, so that the new value will occur in subsequent instances.
Three lists follow:

The first is a list of basic parameters. Database administrators should be familiar with and consider the setting for all of the basic parameters.
The second list shows the initialization parameters by their functional category.
The third list includes all initialization parameters in alphabetical order.

For a description of these parameters, please refer to Oracle Database Reference.

See Also:

the following examples of using the ALTER SYSTEM statement: "Changing Licensing Parameters: Examples", "Enabling Query Rewrite: Example", "Enabling Resource Limits: Example", "Shared Server Parameters ", and "Changing Shared Server Settings: Examples"

Basic Parameters

CLUSTER_DATABASE
COMPATIBLE
CONTROL_FILES
DB_BLOCK_SIZE
DB_CREATE_FILE_DEST
DB_CREATE_ONLINE_LOG_DEST_n
DB_DOMAIN
DB_NAME
DB_RECOVERY_FILE_DEST
DB_RECOVERY_FILE_DEST_SIZE
DB_UNIQUE_NAME
INSTANCE_NUMBER
JOB_QUEUE_PROCESSES
LOG_ARCHIVE_DEST_n
LOG_ARCHIVE_DEST_STATE_n
NLS_LANGUAGE
NLS_TERRITORY
OPEN_CURSORS
PGA_AGGREGATE_TARGET
PROCESSES
REMOTE_LISTENER
REMOTE_LOGIN_PASSWORDFILE
ROLLBACK_SEGMENTS
SESSIONS
SGA_TARGET
SHARED_SERVERS
STAR_TRANSFORMATION_ENABLED
UNDO_MANAGEMENT
UNDO_TABLESPACE

Parameters by Functional Category

ANSI Compliance

BLANK_TRIMMING
Backup and Restore

BACKUP_TAPE_IO_SLAVES
RECYCLEBIN
TAPE_ASYNCH_IO
BFILEs

SESSION_MAX_OPEN_FILES
Buffer Cache and I/O

DB_nK_CACHE_SIZE
DB_BLOCK_BUFFERS
DB_BLOCK_SIZE
DB_CACHE_ADVICE
DB_CACHE_SIZE
DB_FILE_MULTIBLOCK_READ_COUNT
DB_KEEP_CACHE_SIZE
DB_RECYCLE_CACHE_SIZE
DB_WRITER_PROCESSES
DBWR_IO_SLAVES
DISK_ASYNCH_IO
FILESYSTEMIO_OPTIONS
READ_ONLY_OPEN_DELAYED
USE_INDIRECT_DATA_BUFFERS
Cursors and Library Cache

CURSOR_SHARING
CURSOR_SPACE_FOR_TIME
OPEN_CURSORS
SESSION_CACHED_CURSORS
Database/Instance Identification

DB_DOMAIN
DB_NAME
INSTANCE_NAME
Diagnostics and Statistics

BACKGROUND_CORE_DUMP
BACKGROUND_DUMP_DEST
CORE_DUMP_DEST
DB_BLOCK_CHECKING
DB_BLOCK_CHECKSUM
EVENT
MAX_DUMP_FILE_SIZE
SHADOW_CORE_DUMP
STATISTICS_LEVEL
TIMED_OS_STATISTICS
TIMED_STATISTICS
TRACE_ENABLED
TRACEFILE_IDENTIFIER
USER_DUMP_DEST
Distributed, Replication

COMMIT_POINT_STRENGTH
DISTRIBUTED_LOCK_TIMEOUT
GLOBAL_NAMES
HS_AUTOREGISTER
OPEN_LINKS
OPEN_LINKS_PER_INSTANCE
REPLICATION_DEPENDENCY_TRACKING
File Locations, Names, and Sizes

AUDIT_FILE_DEST
BACKGROUND_CORE_DUMP
BACKGROUND_DUMP_DEST
CONTROL_FILES
CORE_DUMP_DEST
DB_CREATE_FILE_DEST
DB_CREATE_ONLINE_LOG_DEST_n
DB_FILES
DB_RECOVERY_FILE_DEST
DB_RECOVERY_FILE_DEST_SIZE
FILE_MAPPING
IFILE
LOG_ARCHIVE_DEST_n
SPFILE
Globalization

NLS_CALENDAR
NLS_COMP
NLS_CURRENCY
NLS_DATE_FORMAT
NLS_DATE_LANGUAGE
NLS_DUAL_CURRENCY
NLS_ISO_CURRENCY
NLS_LANGUAGE
NLS_LENGTH_SEMANTICS
NLS_NCHAR_CONV_EXCP
NLS_NUMERIC_CHARACTERS
NLS_SORT
NLS_TERRITORY
NLS_TIMESTAMP_FORMAT
NLS_TIMESTAMP_TZ_FORMAT
Java

JAVA_MAX_SESSIONSPACE_SIZE
JAVA_POOL_SIZE
JAVA_SOFT_SESSIONSPACE_LIMIT
Job Queues

JOB_QUEUE_PROCESSES
License Limits

LICENSE_MAX_SESSIONS
LICENSE_MAX_USERS
LICENSE_SESSIONS_WARNING
Memory

LARGE_POOL_SIZE
SHARED_POOL_RESERVED_SIZE
SHARED_POOL_SIZE
Miscellaneous

AQ_TM_PROCESSES
COMPATIBLE
FIXED_DATE
Networking

LOCAL_LISTENER
REMOTE_LISTENER
SERVICE_NAMES
Objects and LOBs

OBJECT_CACHE_MAX_SIZE_PERCENT
OBJECT_CACHE_OPTIMAL_SIZE
OLAP

OLAP_PAGE_POOL_SIZE
Optimizer

OPTIMIZER_DYNAMIC_SAMPLING
OPTIMIZER_FEATURES_ENABLE
OPTIMIZER_INDEX_CACHING
OPTIMIZER_INDEX_COST_ADJ
OPTIMIZER_MODE
OPTIMIZER_SECURE_VIEW_MERGING
QUERY_REWRITE_ENABLED
QUERY_REWRITE_INTEGRITY
STAR_TRANSFORMATION_ENABLED
Parallel Execution

PARALLEL_ADAPTIVE_MULTI_USER
PARALLEL_EXECUTION_MESSAGE_SIZE
PARALLEL_MAX_SERVERS
PARALLEL_MIN_PERCENT
PARALLEL_MIN_SERVERS
PARALLEL_THREADS_PER_CPU
PL/SQL

PLSQL_NATIVE_LIBRARY_DIR
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT
PLSQL_V2_COMPATIBILITY
REMOTE_DEPENDENCIES_MODE
UTL_FILE_DIR
PL/SQL Compiler

PLSQL_CC_FLAGS
PLSQL_CODE_TYPE
PLSQL_DEBUG
PLSQL_OPTIMIZE_LEVEL
PLSQL_WARNINGS
NLS_LENGTH_SEMANTICS
SGA Memory

DB_nK_CACHE_SIZE
DB_CACHE_ADVICE
DB_CACHE_SIZE
HI_SHARED_MEMORY_ADDRESS
JAVA_POOL_SIZE
LOCK_SGA
OLAP_PAGE_POOL_SIZE
PGA_AGGREGATE_TARGET
PRE_PAGE_SGA
SGA_MAX_SIZE
SHARED_MEMORY_ADDRESS
Real Application Clusters

ACTIVE_INSTANCE_COUNT
CLUSTER_DATABASE
CLUSTER_DATABASE_INSTANCES
CLUSTER_INTERCONNECTS
GC_FILES_TO_LOCKS
INSTANCE_GROUPS
INSTANCE_NUMBER
MAX_COMMIT_PROPAGATION_DELAY
PARALLEL_INSTANCE_GROUP
THREAD
Redo Logs, Archiving, and Recovery

CONTROL_FILE_RECORD_KEEP_TIME
DB_CREATE_ONLINE_LOG_DEST_n
DB_RECOVERY_FILE_DEST
DB_RECOVERY_FILE_DEST_SIZE
FAST_START_MTTR_TARGET
LOG_BUFFER
LOG_CHECKPOINT_INTERVAL
LOG_CHECKPOINT_TIMEOUT
LOG_CHECKPOINTS_TO_ALERT
LOG_ARCHIVE_CONFIG
LOG_ARCHIVE_DEST_n
LOG_ARCHIVE_DEST_STATE_n
LOG_ARCHIVE_DUPLEX_DEST
LOG_ARCHIVE_FORMAT
LOG_ARCHIVE_MAX_PROCESSES
LOG_ARCHIVE_MIN_SUCCEED_DEST
LOG_ARCHIVE_TRACE
RECOVERY_PARALLELISM
Resource Manager

RESOURCE_LIMIT
RESOURCE_MANAGER_PLAN
Security and Auditing

AUDIT_FILE_DEST
AUDIT_SYS_OPERATIONS
AUDIT_SYSLOG_LEVEL
AUDIT_TRAIL
O7_DICTIONARY_ACCESSIBILITY
OS_AUTHENT_PREFIX
OS_ROLES
RDBMS_SERVER_DN
REMOTE_LOGIN_PASSWORDFILE
REMOTE_OS_AUTHENT
REMOTE_OS_ROLES
SQL92_SECURITY
Sessions and Processes

CPU_COUNT
PROCESSES
SESSIONS
Shared Server Architecture

CIRCUITS
DISPATCHERS
MAX_DISPATCHERS
MAX_SHARED_SERVERS
SHARED_SERVER_SESSIONS
SHARED_SERVERS
Standby Database

ARCHIVE_LAG_TARGET
DB_FILE_NAME_CONVERT
DB_UNIQUE_NAME
DG_BROKER_CONFIG_FILEn
DG_BROKER_START
FAL_CLIENT
FAL_SERVER
LOG_FILE_NAME_CONVERT
STANDBY_ARCHIVE_DEST
STANDBY_FILE_MANAGEMENT
Temporary Sort Space

BITMAP_MERGE_AREA_SIZE
CREATE_BITMAP_AREA_SIZE
HASH_AREA_SIZE
PGA_AGGREGATE_TARGET
SORT_AREA_RETAINED_SIZE
SORT_AREA_SIZE
WORKAREA_SIZE_POLICY
Transactions

COMMIT_WRITE
DML_LOCKS
FAST_START_PARALLEL_ROLLBACK
TRANSACTIONS
Undo Management

RESUMABLE_TIMEOUT
ROLLBACK_SEGMENTS
TRANSACTIONS_PER_ROLLBACK_SEGMENT
UNDO_MANAGEMENT
UNDO_RETENTION
UNDO_TABLESPACE

All Parameters in Alphabetical Order

ACTIVE_INSTANCE_COUNT
AQ_TM_PROCESSES
ARCHIVE_LAG_TARGET
ASM_DISKGROUPS
ASM_DISKSTRING
ASM_POWER_LIMIT
AUDIT_FILE_DEST
AUDIT_SYS_OPERATIONS
AUDIT_SYSLOG_LEVEL
AUDIT_TRAIL
BACKGROUND_CORE_DUMP
BACKGROUND_DUMP_DEST
BACKUP_TAPE_IO_SLAVES
BITMAP_MERGE_AREA_SIZE
BLANK_TRIMMING
CIRCUITS
CLUSTER_DATABASE
CLUSTER_DATABASE_INSTANCES
CLUSTER_INTERCONNECTS
COMMIT_POINT_STRENGTH
COMMIT_WRITE
COMPATIBLE
CONTROL_FILE_RECORD_KEEP_TIME
CONTROL_FILES
CORE_DUMP_DEST
CPU_COUNT
CREATE_BITMAP_AREA_SIZE
CREATE_STORED_OUTLINES
CURSOR_SHARING
CURSOR_SPACE_FOR_TIME
DB_nK_CACHE_SIZE
DB_BLOCK_BUFFERS
DB_BLOCK_CHECKING
DB_BLOCK_CHECKSUM
DB_BLOCK_SIZE
DB_CACHE_ADVICE
DB_CACHE_SIZE
DB_CREATE_FILE_DEST
DB_CREATE_ONLINE_LOG_DEST_n
DB_DOMAIN
DB_FILE_MULTIBLOCK_READ_COUNT
DB_FILE_NAME_CONVERT
DB_FILES
DB_FLASHBACK_RETENTION_TARGET
DB_KEEP_CACHE_SIZE
DB_NAME
DB_RECOVERY_FILE_DEST
DB_RECOVERY_FILE_DEST_SIZE
DB_RECYCLE_CACHE_SIZE
DB_UNIQUE_NAME
DB_WRITER_PROCESSES
DBWR_IO_SLAVES
DG_BROKER_CONFIG_FILEn
DG_BROKER_START
DISK_ASYNCH_IO
DISPATCHERS
DISTRIBUTED_LOCK_TIMEOUT
DML_LOCKS
EVENT
FAL_CLIENT
FAL_SERVER
FAST_START_MTTR_TARGET
FAST_START_PARALLEL_ROLLBACK
FILE_MAPPING
FILEIO_NETWORK_ADAPTERS
FILESYSTEMIO_OPTIONS
FIXED_DATE
GC_FILES_TO_LOCKS
GCS_SERVER_PROCESSES
GLOBAL_NAMES
HASH_AREA_SIZE
HI_SHARED_MEMORY_ADDRESS
HS_AUTOREGISTER
IFILE
INSTANCE_GROUPS
INSTANCE_NAME
INSTANCE_NUMBER
INSTANCE_TYPE
JAVA_MAX_SESSIONSPACE_SIZE
JAVA_POOL_SIZE
JAVA_SOFT_SESSIONSPACE_LIMIT
JOB_QUEUE_PROCESSES
LARGE_POOL_SIZE
LDAP_DIRECTORY_ACCESS
LICENSE_MAX_SESSIONS
LICENSE_MAX_USERS
LICENSE_SESSIONS_WARNING
LOCAL_LISTENER
LOCK_SGA
LOG_ARCHIVE_CONFIG
LOG_ARCHIVE_DEST
LOG_ARCHIVE_DEST_n
LOG_ARCHIVE_DEST_STATE_n
LOG_ARCHIVE_DUPLEX_DEST
LOG_ARCHIVE_FORMAT
LOG_ARCHIVE_LOCAL_FIRST
LOG_ARCHIVE_MAX_PROCESSES
LOG_ARCHIVE_MIN_SUCCEED_DEST
LOG_ARCHIVE_TRACE
LOG_BUFFER
LOG_CHECKPOINT_INTERVAL
LOG_CHECKPOINT_TIMEOUT
LOG_CHECKPOINTS_TO_ALERT
LOG_FILE_NAME_CONVERT
MAX_COMMIT_PROPAGATION_DELAY
MAX_DISPATCHERS
MAX_DUMP_FILE_SIZE
MAX_SHARED_SERVERS
NLS_CALENDAR
NLS_COMP
NLS_CURRENCY
NLS_DATE_FORMAT
NLS_DATE_LANGUAGE
NLS_DUAL_CURRENCY
NLS_ISO_CURRENCY
NLS_LANGUAGE
NLS_LENGTH_SEMANTICS
NLS_NCHAR_CONV_EXCP
NLS_NUMERIC_CHARACTERS
NLS_SORT
NLS_TERRITORY
NLS_TIMESTAMP_FORMAT
NLS_TIMESTAMP_TZ_FORMAT
O7_DICTIONARY_ACCESSIBILITY
OBJECT_CACHE_MAX_SIZE_PERCENT
OBJECT_CACHE_OPTIMAL_SIZE
OLAP_PAGE_POOL_SIZE
OPEN_CURSORS
OPEN_LINKS
OPEN_LINKS_PER_INSTANCE
OPTIMIZER_DYNAMIC_SAMPLING
OPTIMIZER_FEATURES_ENABLE
OPTIMIZER_INDEX_CACHING
OPTIMIZER_INDEX_COST_ADJ
OPTIMIZER_MODE
OPTIMIZER_SECURE_VIEW_MERGING
OS_AUTHENT_PREFIX
OS_ROLES
PARALLEL_ADAPTIVE_MULTI_USER
PARALLEL_EXECUTION_MESSAGE_SIZE
PARALLEL_INSTANCE_GROUP
PARALLEL_MAX_SERVERS
PARALLEL_MIN_PERCENT
PARALLEL_MIN_SERVERS
PARALLEL_THREADS_PER_CPU
PGA_AGGREGATE_TARGET
PLSQL_CCFLAGS
PLSQL_CODE_TYPE
PLSQL_DEBUG
PLSQL_NATIVE_LIBRARY_DIR
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT
PLSQL_OPTIMIZE_LEVEL
PLSQL_V2_COMPATIBILITY
PLSQL_WARNINGS
PRE_PAGE_SGA
PROCESSES
QUERY_REWRITE_ENABLED
QUERY_REWRITE_INTEGRITY
RDBMS_SERVER_DN
READ_ONLY_OPEN_DELAYED
RECOVERY_PARALLELISM
RECYCLEBIN
REMOTE_DEPENDENCIES_MODE
REMOTE_LISTENER
REMOTE_LOGIN_PASSWORDFILE
REMOTE_OS_AUTHENT
REMOTE_OS_ROLES
REPLICATION_DEPENDENCY_TRACKING
RESOURCE_LIMIT
RESOURCE_MANAGER_PLAN
RESUMABLE_TIMEOUT
ROLLBACK_SEGMENTS
SERVICE_NAMES
SESSION_CACHED_CURSORS
SESSION_MAX_OPEN_FILES
SESSIONS
SGA_MAX_SIZE
SGA_TARGET
SHADOW_CORE_DUMP
SHARED_MEMORY_ADDRESS
SHARED_POOL_RESERVED_SIZE
SHARED_POOL_SIZE
SHARED_SERVER_SESSIONS
SHARED_SERVERS
SKIP_UNUSABLE_INDEXES
SMTP_OUT_SERVER
SORT_AREA_RETAINED_SIZE
SORT_AREA_SIZE
SPFILE
SQL92_SECURITY
SQLTUNE_CATEGORY
STANDBY_ARCHIVE_DEST
STANDBY_FILE_MANAGEMENT
STAR_TRANSFORMATION_ENABLED
STATISTICS_LEVEL
STREAMS_POOL_SIZE
TAPE_ASYNCH_IO
THREAD
TIMED_OS_STATISTICS
TIMED_STATISTICS
TRACE_ENABLED
TRACEFILE_IDENTIFIER
TRANSACTIONS
TRANSACTIONS_PER_ROLLBACK_SEGMENT
UNDO_MANAGEMENT
UNDO_RETENTION
UNDO_TABLESPACE
USE_INDIRECT_DATA_BUFFERS
USER_DUMP_DEST
UTL_FILE_DIR
WORKAREA_SIZE_POLICY

System Parameters and ALTER SYSTEM

This section describes system parameters. These parameters are not initialization parameters, so you cannot set them in a pfile or spfile. However, you can set them using an ALTER SYSTEM statement.

USE_STORED_OUTLINES

Syntax:

USE_STORED_OUTLINES = { TRUE | FALSE | category_name }

The USE_STORED_OUTLINES parameter determines whether the optimizer will use stored public outlines to generate execution plans. USE_STORED_OUTLINES is not an initialization parameter.

TRUE causes the optimizer to use outlines stored in the DEFAULT category when compiling requests.
FALSE specifies that the optimizer should not use stored outlines. This is the default.
category_name causes the optimizer to use outlines stored in the category_name category when compiling requests.

Shared Server Parameters

When you start your instance, Oracle Database creates shared server processes and dispatcher processes for the shared server architecture based on the values of the SHARED_SERVERS and DISPATCHERS initialization parameters. You can also set the SHARED_SERVERS and DISPATCHERS parameters with ALTER SYSTEM to perform one of the following operations while the instance is running:

Create additional shared server processes by increasing the minimum number of shared server processes.
Terminate existing shared server processes after their current calls finish processing.
Create more dispatcher processes for a specific protocol, up to a maximum across all protocols specified by the initialization parameter MAX_DISPATCHERS.
Terminate existing dispatcher processes for a specific protocol after their current user processes disconnect from the instance.

Examples

Archiving Redo Logs Manually: Examples The following statement manually archives the redo log file group containing the redo log entry with the SCN 9356083:

ALTER SYSTEM ARCHIVE LOG CHANGE 9356083;

The following statement manually archives the redo log file group containing a member named 'diskl:log6.log' to an archived redo log file in the location 'diska:[arch$]':

ALTER SYSTEM ARCHIVE LOG 
    LOGFILE 'diskl:log6.log' 
    TO 'diska:[arch$]';

Enabling Query Rewrite: Example This statement enables query rewrite in all sessions for all materialized views for which query rewrite has not been explicitly disabled:

ALTER SYSTEM SET QUERY_REWRITE_ENABLED = TRUE;

Restricting Sessions: Example You might want to restrict sessions if you are performing application maintenance and you want only application developers with RESTRICTED SESSION system privilege to log on. To restrict sessions, issue the following statement:

ALTER SYSTEM
   ENABLE RESTRICTED SESSION;

You can then terminate any existing sessions using the KILL SESSION clause of the ALTER SYSTEM statement.
After performing maintenance on your application, issue the following statement to allow any user with CREATE SESSION system privilege to log on:

ALTER SYSTEM
   DISABLE RESTRICTED SESSION;

Establishing a Wallet and Encryption Key The following statements load information from the server wallet into memory and set the transparent data encryption master key:

ALTER SYSTEM SET ENCRYPTION WALLET OPEN AUTHENTICATED BY "welcome1";
ALTER SYSTEM SET ENCRYPTION KEY AUTHENTICATED BY "welcome1";

These statements assume that you have initialized the security module and created a wallet with the password welcome1.
Clearing the Shared Pool: Example You might want to clear the shared pool before beginning performance analysis. To clear the shared pool, issue the following statement:

ALTER SYSTEM FLUSH SHARED_POOL;

Forcing a Checkpoint: Example The following statement forces a checkpoint:

ALTER SYSTEM CHECKPOINT;

Enabling Resource Limits: Example This ALTER SYSTEM statement dynamically enables resource limits:

ALTER SYSTEM SET RESOURCE_LIMIT = TRUE;

Changing Shared Server Settings: Examples The following statement changes the minimum number of shared server processes to 25:

ALTER SYSTEM SET SHARED_SERVERS = 25;

If there are currently fewer than 25 shared server processes, then Oracle Database creates more. If there are currently more than 25, then Oracle Database terminates some of them when they are finished processing their current calls if the load could be managed by the remaining 25.
The following statement dynamically changes the number of dispatcher processes for the TCP/IP protocol to 5 and the number of dispatcher processes for the ipc protocol to 10:

ALTER SYSTEM 
   SET DISPATCHERS = 
      '(INDEX=0)(PROTOCOL=TCP)(DISPATCHERS=5)',
      '(INDEX=1)(PROTOCOL=ipc)(DISPATCHERS=10)';

If there are currently fewer than 5 dispatcher processes for TCP, then Oracle Database creates new ones. If there are currently more than 5, then Oracle Database terminates some of them after the connected users disconnect.
If there are currently fewer than 10 dispatcher processes for ipc, then Oracle Database creates new ones. If there are currently more than 10, then Oracle Database terminates some of them after the connected users disconnect.
If there are currently existing dispatchers for another protocol, then the preceding statement does not affect the number of dispatchers for that protocol.
Changing Licensing Parameters: Examples The following statement dynamically changes the limit on sessions for your instance to 64 and the warning threshold for sessions on your instance to 54:

ALTER SYSTEM 
   SET LICENSE_MAX_SESSIONS = 64 
   LICENSE_SESSIONS_WARNING = 54;

If the number of sessions reaches 54, then Oracle Database writes a warning message to the ALERT file for each subsequent session. Also, users with RESTRICTED SESSION system privilege receive warning messages when they begin subsequent sessions.
If the number of sessions reaches 64, then only users with RESTRICTED SESSION system privilege can begin new sessions until the number of sessions falls below 64 again.
The following statement dynamically disables the limit for sessions on your instance. After you issue this statement, Oracle Database no longer limits the number of sessions on your instance.

ALTER SYSTEM SET LICENSE_MAX_SESSIONS = 0;

The following statement dynamically changes the limit on the number of users in the database to 200. After you issue the preceding statement, Oracle Database prevents the number of users in the database from exceeding 200.

ALTER SYSTEM SET LICENSE_MAX_USERS = 200;

Forcing a Log Switch: Example You might want to force a log switch to drop or rename the current redo log file group or one of its members, because you cannot drop or rename a file while Oracle Database is writing to it. The forced log switch affects only the redo log thread of your instance. The following statement forces a log switch:

ALTER SYSTEM SWITCH LOGFILE;

Enabling Distributed Recovery: Example The following statement enables distributed recovery:

ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY;

You might want to disable distributed recovery for demonstration or testing purposes. You can disable distributed recovery in both single-process and multiprocess mode with the following statement:

ALTER SYSTEM DISABLE DISTRIBUTED RECOVERY;

When your demonstration or testing is complete, you can then enable distributed recovery again by issuing an ALTER SYSTEM statement with the ENABLE DISTRIBUTED RECOVERY clause.
Terminating a Session: Example You might want to terminate the session of a user that is holding resources needed by other users. The user receives an error message indicating that the session has been terminated. That user can no longer make calls to the database without beginning a new session. Consider this data from the V$SESSION dynamic performance table, when the users SYS and oe both have open sessions:

SELECT sid, serial#, username
   FROM v$session; 

       SID    SERIAL# USERNAME
---------- ---------- ------------------------------
        29         85 SYS
        33          1
        35          8
        39         23 OE
        40          1
. . .

The following statement terminates the session of the user scott using the SID and SERIAL# values from V$SESSION:

ALTER SYSTEM KILL SESSION '39, 23';

Disconnecting a Session: Example The following statement disconnects user scott's session, using the SID and SERIAL# values from V$SESSION:

ALTER SYSTEM DISCONNECT SESSION '13, 8' POST_TRANSACTION;