You also specify the location of the Oracle base directory, which is used by all Oracle software products installed on the server. The first time you install Oracle Database software on a server, you are prompted to specify the location of the inventory directory, called oraInventory.
This directory provides a centralized inventory of all Oracle software products installed on the server. You should use the same value for the Oracle inventory directory each time you perform an Oracle software installation on the server.
A database includes several files that store the user data, database metadata, and information required to recover from failures.
As an administrator, you decide what kind of storage subsystem to use for these files. You can select from the following options:. File System —This default option creates database files that are managed by the file system of your operating system. You can specify the directory path where database files are to be stored. Oracle Database can create and manage the actual files. For environments with a large number of disks, this option simplifies database administration and maximizes performance.
Oracle ASM performs software striping and mirroring at the file level for maximum storage flexibility, performance, and availability. A single Oracle ASM instance can provide storage for multiple databases on the same server. These options include your global database name and system identifier SID. The SID is a unique identifier that is used to distinguish this instance from other Oracle Database instances that you may create later and run concurrently on your system. The global database name is the full name of the database that uniquely distinguishes it from any other database.
The database name portion sales is a simple name you call your database. The database domain portion example. Together, the database name and domain form the global database name.
During advanced installations using the Server Class method you are prompted to make the additional choices listed in this section, and the choices for a typical installation. The installation process provides default values for every choice. This guide describes, but does not document, these additional advanced installation choices. For more information, see Oracle Database Installation Guide for your platform. You choose which language the software should use after it is installed.
You can select multiple languages. The default value is English. If you choose a value other than English, it does not change the language used by the installation. You select a template to use when configuring the database.
Database Configuration Options. You can choose how to configure the database created by the installer. You can select the memory size and management options, the character sets used to store data, the security options for database access, and whether the sample schemas should be installed. To complete the exercises in this guide and related course material, you must install the sample schemas.
This data is also used in most examples throughout Oracle Database documentation. Oracle recommends that you install the sample schemas. This choice is a configuration option only during advanced installation. Sample schemas are installed by default during typical or Desktop class installations.
Database Management Options. You specify whether to manage your database centrally or locally using Oracle Enterprise Manager.
Central management enables you to manage multiple targets, such as databases and application servers, using a single interface. Using local management you can manage only a single database instance at a time. To use central management, you must have an Oracle Enterprise Management agent on each host , or computer that has Oracle Database software installed on it. These agents are responsible for monitoring all components on that host. If an agent is not found on the local host, then this option is disabled during installation.
If you are setting up a single database for the first time, then it is recommended that you configure local management with Oracle Enterprise Manager, which is the default. You can later install additional databases and configure central management using Enterprise Manager. You specify whether automated backups should be configured for the database.
If you choose this option, you must specify whether the recovery area should be stored on the local file system or in an Oracle ASM disk group. You must also specify the operating system credentials the backup job uses when performing backups. When you create a database, certain administrative user accounts are created automatically. You can use the same password for each account, or specify passwords for each account individually. If you do not enter a secure password, you will receive a warning message during installation.
Operating System Groups. Administrative access to the database is granted by membership in certain operating system groups. This section briefly describes the steps for a desktop-class installation. Most steps are common to all platforms and involve running the Oracle Universal Installer. Platform-specific steps are noted.
For further assistance, consult the online Help or the Oracle Database Installation Guide for your platform. Log on to your computer as a member of the administrative group that is authorized to install Oracle Database software and to create and run the database. Refer to your operating system-specific documentation or contact your system administrator to determine whether you have the necessary privileges and permissions to install new software.
If you are installing from distribution media, then insert the distribution media for the database into your computer. If you downloaded the installation software from the Oracle Web site, then follow the instructions on the site to run the Oracle Universal Installer.
Or, see the Oracle Database Installation Guide for your platform. The first window that appears is the Configure Security Updates window. To receive notifications about security issues via e-mail, enter your e-mail address in the Email text field. To receive security updates from My Oracle Support, enter the e-mail address registered with My Oracle Support, select the I wish to receive security updates Choose the Create and configure a database option.
Or, you also have the option of choosing to only install the database software, but then you must create a database in an additional step after the software is installed. If you are currently using a previous version of Oracle Database, choose Upgrade an existing database. After you have chosen an option, click Next. You can choose the Server Class option to customize your installation.
For example, you use this method to configure Oracle Automatic Storage Management for your database, install the Sample Schemas, or configure automated backups. Selecting this option guides you through a series of installation steps that are not documented in this guide. For more information about the advanced choices, see "About Advanced Installation".
Also see Oracle Database Installation Guide for your platform. Oracle Base Location— The Oracle base directory helps to facilitate the organization of multiple Oracle software installations.
You can click Browse to find the directory you want to act as the Oracle base directory. Software Location—The software location is the Oracle home for your database. You must specify a new Oracle home directory for each new installation of Oracle Database software. By default, the Oracle home directory is a subdirectory of the Oracle base directory.
You can click Browse to find the directory where you want to install the Oracle Database software. Database File Location—The database file location is the location where Oracle Database files are stored.
You can click Browse to select a different location. See "Installation Type". Character Set—Choose the character set to use to store the data within the database. You can choose between the Default , which is based on the operating system language settings, or Unicode. Host computer users in this group have administrative privileges on the database. This group is typically named dba.
Global Database Name—Enter the fully qualified global database name. See "Installation Type" for more on global database name. If the password you choose is not a secure password, a warning message will be displayed. If Oracle software has not previously been installed on this server, then the Create Inventory window appears. If this is not the first installation attempt on this server, then the Perform Prerequisite Checks window appears. For first time installations on Linux and UNIX operating systems only , specify a directory for installation files and the name of an operating system group that has write permissions for that directory.
If this is the first time you are installing any Oracle software on this computer, then the Create Inventory Directory window appears. You must specify a local directory for the inventory, which OUI uses to keep track of all Oracle software installed on the computer.
This information is used while applying patches or upgrading an existing installation, and while deinstalling Oracle software. Note that this directory is different from the Oracle home directory. In this window you can also specify the operating system group that has write permissions on the inventory directory. This prevents other users from writing over the Oracle product installation files.
Typically the oinstall group is selected. After you enter a directory path and optionally specify an operating system group, click Next to continue. OUI performs several environment checks and indicates whether the check was a success, or resulted in a warning or failure.
Details of the checks are provided in the displayed window. The installation can proceed only when all checks have a status of either Succeeded or Warning. Strengthen your foundations with the Python Programming Foundation Course and learn the basics. Previous What is Cashless Payment System? Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments.
What's New. Most popular in How To. Table describes the valid execution operations and modes and lists the optional parameters in brackets. Table discusses the flags and their behavior and Table defines the optional parameters in detail.
Multiple parameters can be used in combination at the command line. Use this option to display help messages for the EMCA utility. The options described in Table , Table , and Table , and the valid parameters you may include are listed. Configures Database Control for a database. Options include creating or re-creating the Database Control repository, configuring automatic backups, and performing these operations on a cluster database.
Configures central agent management for a database or an Oracle ASM instance. Options include performing this operation on a cluster environment. This operation will configure the database so that it can be centrally managed by the Oracle Enterprise Manager Grid Control Console. To use this option, you must have previously installed the Oracle Management Service component of Enterprise Manager on a network host. In addition, the Oracle Management Agent must be installed on the host on which you are running the database.
Configures both Database Control and central agent management for a database. The possible configuration options are similar to those described above. Deconfigures Database Control for a database. Options include dropping the Database Control repository and performing these operations on a cluster database. For example, you might use this command to remove the Database Control configuration from a database you are planning to delete.
In such a scenario, remove the Database Control configuration before physically deleting the database. This operation does not remove the actual database or its data files. Deconfigures central agent management for a database or an Oracle ASM instance.
For example, you might use this command to remove the central agent management configuration from a database you are planning to delete. In such a scenario, remove the central agent management configuration before physically deleting the database.
Deconfigures both Database Control and central agent management for a database. The possible deconfiguration options are similar to those described above. This option applies only to Release 11 g.
Deconfigures Enterprise Manager for a node being deleted. This option applies only to Oracle Database Release 11 g. Configures Enterprise Manager for a newly added cluster instance of an administrator-managed database or Oracle ASM storage.
This parameter takes a SID for the instance being added. Deconfigures Enterprise Manager for a newly deleted cluster instance of an administrator-managed database or Oracle ASM storage.
This parameter takes a SID for the instance being deleted. Explicitly reassigns Database Control ports. Reconfigures Database Control deployment for a cluster database. Note that this command must be used with the -cluster option. Displays information about the current deployment configuration of Database Control in a cluster environment. Upgrades the configuration of an earlier release of Enterprise Manager to the current release. This does not upgrade the actual database or Oracle ASM instances, nor does it upgrade the Enterprise Manager software.
Instead, it upgrades the configuration files for the specified instance so that they are compatible with the current version of the Enterprise Manager software.
EMCA will attempt to upgrade all instances of the specified database or Oracle ASM target, or both, on the host, across all Oracle homes because it is likely that certain target properties, such as the listener port or Oracle home, have changed. Restores the current version of Enterprise Manager configuration to an earlier version. This is the inverse of the -upgrade option and will reverse any changes that result from this operation.
Performs the operation for a database including cluster databases. Use this option for databases that use Oracle ASM to store the data files. If a database is using Oracle ASM, all the configuration operations and modes described above except for -upgrade and -restore will detect this automatically and apply the changes to both the database and Oracle ASM instances.
This flag can only be used in -upgrade and -restore mode. Database and Oracle ASM instances may be upgraded or restored separately that is, upgrading an Oracle ASM instance does not require upgrading the database instances it services. Therefore, the Enterprise Manager configuration can be upgraded or restored separately for a database and its respective Oracle ASM instance. Performs the operation without prompting for additional information.
If this mode is specified, all the required parameters must be entered at the command line or specified in an input file using the —respFile argument. You can view a list of the available parameters by entering emca -help at the command line. Configures automatic backup for a database. EMCA will prompt for daily automatic backup options. The default Enterprise Manager settings will be used to backup the database files. If that parameter is not set, EMCA will generate an error.
You can modify these settings later using the Maintenance page in Database Control. For more information, see the Database Control online help. Specifies the path of an input file listing parameters for EMCA to use while performing its configuration operation. Oracle home from which the listener is running. Use this parameter to specify the port you use to display the Database Control Console in your Web browser.
Use this parameter to specify the Management Agent port for Database Control. Node from which Database Control console is to be run for cluster databases. Path to a static file specifying the ports to use. Instead of answering a series of prompts when you run EMCA, you can use the -respFile argument to specify an input file. The input file you create must be in a format similar to the following example:.
For example, to configure the Database Control to perform daily backups and create the Database Control Management Repository, create an input file similar to the one shown in Example and enter the following command at the operating system prompt:.
For example, by default, you access Database Control using port , as shown in the following example:. Alternatively, you can explicitly assign ports after configuring Database Control using the following command:. The following list summarizes the EMCA command-line arguments that control the standard Database Control port assignments:.
For example, if you set this port to , you can then use the following URL to display the Database Control Console:. The default port can be changed if you want to configure a specific port for Database Control. The default port can be changed if the user wants to configure a specific port for Database Control. This port is used by the Database Control Management Agent, which is monitoring and administering the database for the Database Control. However, by default the Database Control Console will only start on the local node.
On every other node of the cluster, only the Enterprise Manager agent will start. This is because the Database Control Console opens several connections to the database. If an instance of the console is running on every host in the cluster, then you may easily exceed the maximum number of permitted open connections on a node or node environment. To remedy this situation, the Database Control is started only on the local node.
On every other node, the commands emctl start dbconsole and emctl stop dbconsole only start and stop the agent. Each of the remote agents will upload their respective data to the console running on the local node, from which you can monitor and manage all the targets in the cluster.
The following subdirectory is created on each instance of the Oracle RAC database where nodename is the name of a node in the cluster, and dbuniquename is the database instance name of the database for release 11 g and later:. For Oracle Database release 10 g , nodename is the name of the node in the cluster and sid is the database instance name:. However, note that if you upgrade an existing Oracle RAC database configured with Database Control to the current release, then the existing Database Control configuration is retained.
The existing Database Control has a Database Control running on each cluster node. Otherwise, the Grid Control Console option is unavailable and you must instead choose to manage your database with Database Control.
For most of the Oracle installation types, you must choose either Database Control or Grid Control as your management option when you create a database during the installation. However, if you create a database using one of the following methods, you can choose not to configure Database Control:.
Choosing the Advanced database configuration option during an Enterprise or Standard Edition installation. You can use DBCA to create a new database or to reconfigure an existing database. Log in to the database host as a member of the administrative group that is authorized to install Oracle software and create and run the database. For more information about Enterprise Manager notifications and daily backups, click Help on the Management Options page.
In release 11 g of the database and later, this directory is named using the following format and contains Database Control configuration and state files specific to the database you just configured:. Likewise in Oracle Database 10 g , for cluster databases the directories are named:. For example, enter the following command to configure Database Control so that it will perform automatic daily backups of your database:. Table describes the valid execution operations and modes and lists the optional parameters in brackets.
Table discusses the flags and their behavior and Table defines the optional parameters in detail. Multiple parameters can be used in combination at the command line.
Use this option to display help messages for the EMCA utility. The options described in Table , Table , and Table , and the valid parameters you may include are listed. Configures Database Control for a database. Options include creating or recreating the Database Control repository, configuring automatic backups, and performing these operations on a cluster database.
Configures central agent management for a database or an Oracle ASM instance. Options include performing this operation on a cluster environment. This operation will configure the database so that it can be centrally managed by the Oracle Enterprise Manager Grid Control Console. To use this option, you must have previously installed the Oracle Management Service component of Enterprise Manager on a network host. In addition, the Oracle Management Agent must be installed on the host on which you are running the database.
Configures both Database Control and central agent management for a database. The possible configuration options are similar to those described above. Deconfigures Database Control for a database. Options include dropping the Database Control repository and performing these operations on a cluster database. For example, you might use this command to remove the Database Control configuration from a database you are planning to delete.
In such a scenario, remove the Database Control configuration before physically deleting the database. This operation does not remove the actual database or its data files. Deconfigures central agent management for a database or an Oracle ASM instance. For example, you might use this command to remove the central agent management configuration from a database you are planning to delete.
In such a scenario, remove the central agent management configuration before physically deleting the database. Deconfigures both Database Control and central agent management for a database. The possible deconfiguration options are similar to those described above. This option applies only to Release 11 g. Deconfigures Enterprise Manager for a node being deleted.
This option applies only to Oracle Database Release 11 g. Configures Enterprise Manager for a newly added cluster instance of an administrator-managed database or Oracle ASM storage. This parameter takes a SID for the instance being added. Deconfigures Enterprise Manager for a newly deleted cluster instance of an administrator-managed database or Oracle ASM storage.
This parameter takes a SID for the instance being deleted.
0コメント