Oracle Management Server (OMS) is a pivotal component within the Oracle Enterprise Manager (OEM) framework, acting as the central command and control hub for managing your Oracle environment. For content creators and IT professionals leveraging rental-server.net, understanding how to effectively configure and control your OMS is crucial for optimal system management. This guide delves into the essential aspects of OMS configuration, drawing upon the powerful Enterprise Manager Configuration Assistant (EMCA) to streamline these processes.
Starting the Enterprise Manager Configuration Assistant
The Enterprise Manager Configuration Assistant (EMCA) is your primary tool for configuring the Management Server. In many installation scenarios, particularly when deploying the full Enterprise Manager framework (Console, Management Server, and Intelligent Agents), EMCA launches automatically during the configuration phase. Specifically, installations involving:
- [Installation Scenario 1 – Original Article Context Needed Here If Available]
- [Installation Scenario 2 – Original Article Context Needed Here If Available]
- [Installation Scenario 3 – Original Article Context Needed Here If Available]
trigger an automatic startup of EMCA. However, if you’ve employed other installation methods for Oracle Enterprise Manager, manual initiation of EMCA becomes necessary post-installation.
Important Prerequisite: Before initiating repository creation, ensure a compatible database version for a 9i Management Server repository is installed and running on your network.
To manually launch the Enterprise Manager Configuration Assistant, follow these steps:
[Instructions on starting EMCA – Original Article Context Needed Here If Available. Assuming command line based on later content]
Remember, write access to the omsconfig.properties file located in the $ORACLE_HOMEsysmanconfig directory is mandatory for executing the emca command.
Configuring a Local Management Server for a New 9i Repository
When setting up a new 9i repository, the Enterprise Manager Configuration Assistant automates a series of critical tasks. Whether invoked post-installation or manually, EMCA guides you through the necessary steps.
Navigating the Welcome Page
Upon manual startup, the EMCA process begins with a Welcome page, designed for initial guidance.
By default, the “Show this page next time” option is pre-selected. For experienced users, deselecting this option streamlines future EMCA launches, directly presenting the Configuration Operation page.
Figure 3-1 Welcome Page of Enterprise Manager Configuration Assistant
Selecting the Configuration Operation
Clicking “Next” from the Welcome page transitions you to the Configuration Operation page.
Figure 3-2 Configuration Operation Page in EMCA
To configure your local Management Server by either establishing a new repository or modifying an existing one, choose the “Configure local Management Server” option from the repository operations list and proceed by clicking “Next.”
If no prior configuration exists, the “Configure Oracle Management Server” page will appear directly. However, if a configuration is already present, a dialog box prompts you to either edit the existing configuration or create a new one.
Figure 3-3 Edit or Create Configuration Dialog
Choosing “Edit” directs you to the Edit Configuration Parameters page (details in “Edit Configuration Parameters” of the original article). Selecting “Create” leads you to the “Configure Oracle Management Server” page.
Configuring Oracle Management Server Settings
The Management Server requires a repository to store vital information concerning managed servers and targets.
Figure 3-4 Configure Management Server Page
For new Oracle Enterprise Manager deployments or when configuring the initial Management Server and creating a fresh Release 9i repository, the “Create a new repository” option is the appropriate choice. This option handles both the creation and loading of your Release 9i repository, along with setting up essential configuration parameters for your local Management Server.
Choosing New Repository Creation Options
The Enterprise Manager Configuration Assistant offers flexibility in repository creation, allowing for automated or customized setups.
Note: This page is only visible when EMCA is launched from an Oracle Home containing a 9i database server installation.
Figure 3-5 Create New Repository Options Page
Typical Configuration: Opting for “Typical” initiates a streamlined repository creation process, potentially encompassing actions detailed below without requiring further steps. The subsequent page will be the Create Repository Summary page, pre-populated with default or intelligently determined entries.
Figure 3-6 Create Repository Summary for Typical Setup
Important Password Note: Record the displayed password for the repository user securely. This is the only instance where this password is shown, and it’s necessary for future repository management tasks like dropping or upgrading. Password changes can be performed later, as described in “Changing the Repository User Password” of the original article.
Clicking “Finish” initiates the repository creation process. “Back” allows for modifications to previous settings. Upon “Finish,” EMCA launches the Database Configuration Assistant (DBCA) to create the database instance.
Note: The DBCA activity might not be immediately apparent in the progress dialog.
During the DBCA password configuration step, accepting the default passwords is recommended.
Critical Note: Do not alter the password for SYS at this stage. EMCA assumes the password is “change_on_install,” and modifications at this point will lead to login failures for EMCA. Password changes for SYS can be safely performed after EMCA completes its operations.
Once DBCA completes database instance creation, EMCA attempts to connect using the SYS credentials. Upon successful connection, EMCA creates the repository user and populates the repository schema.
Custom Configuration: Selecting “Custom” offers granular control, allowing you to choose from various actions based on your specific needs.
Choosing “Custom” leads to the “Select Database Location” page.
Specifying Database Location for the Repository
You have the choice to house your Enterprise Manager repository in a new local database or an existing database elsewhere on your network. The chosen database must be compatible with a 9i Management Server repository.
Note: This page appears only when EMCA is run from an Oracle Home containing a 9i database server installation.
Figure 3-7 Select Database Location Page
Selecting “In a new local database instance” without clicking “Change Database SID” takes you directly to the “Repository Login Information” page (details in “Repository Login Information”).
Choosing “In a new local database instance” and clicking “Change Database SID” opens the “Change Database SID” dialog (details in “Change Database SID”).
Selecting “In another existing database” navigates you to the “Select Database for Repository” page (details in “Select Database for Repository”).
Modifying the Database SID
The Change Database SID dialog allows you to customize the Oracle System Identifier (SID) for the local database instance hosting your Enterprise Manager repository.
Figure 3-8 Change Database SID Dialog
Oracle best practices recommend selecting a database SID that is not intended for management by this Enterprise Manager repository instance.
Click “OK” after modifying the database name or SID. Then, click “Next” on the Select Database Location page to proceed to the “Repository Login Information” page (details in “Repository Login Information”).
Selecting a Database for the Repository
Log in to the database designated to host the repository.
Figure 3-9 Select Database for Repository Login Page
User Name and Password: Database login requires a user with DBA privileges. EMCA requests DBA credentials to facilitate new user creation for repository ownership and to enable database/repository queries. This account is a standard database user account, distinct from Oracle Enterprise Manager administrator accounts. For example, you might use system/manager.
Service: Specify the service using the format: <host>:<port>:<SID>.
host: Machine name of the database location.port: Database listener port (typically 1521 or 1526).SID: Database system identifier.
Example: my_em_machine:1521:em92 connects to the em92 database on my_em_machine using port 1521.
Note: Using the service format :: is recommended, but Oracle Net names are also acceptable with proper Oracle Net client configuration.
Click “Next” to continue.
Repository Login Information Setup
An Enterprise Manager repository is associated with a dedicated database user. During repository creation, EMCA creates this repository schema user, using the username and password you provide on this page.
Figure 3-10 Repository Login Information Page
User Name: EMCA defaults to OEM_<TCP/IP hostname of machine>_<SID> as the repository username.
TCP/IP hostname of machine: Machine name where the database resides.SID: Database system identifier.
Ensure the chosen repository username is unique across your network. While you can customize the name, uniqueness remains crucial. The Intelligent Agent identifies each Management Server by its repository name. Naming conflicts can hinder agent-server communication.
Password: Enter and confirm the password for the repository user.
You can choose to save the username and encrypted password in the omsconfig.properties file for automatic login during Management Server startup. Alternatively, for enhanced security, select “Do not save username and password” to operate in secure Management Server mode.
The repository account information is used for repository maintenance operations (create, upgrade, drop). The Configuration Assistant automatically grants the necessary roles and privileges to the repository schema user. For security best practices, avoid granting excessive privileges beyond what is strictly required for Oracle Enterprise Manager operations.
Tablespace Selection for Repository User
Under normal circumstances, the “Select Repository User Tablespaces” page is skipped.
Important Note: Avoid installing the Oracle Enterprise Manager repository into the SYSTEM, ROLLBACK, or TEMPORARY tablespaces, particularly in production databases. These tablespaces have parameter settings unsuitable for Enterprise Manager’s usage. SYSTEM tablespace should be reserved for system entities. ROLLBACK and TEMPORARY tablespaces are subject to dynamic usage patterns that can negatively impact repository performance.
When manually launching EMCA, if the OEM_REPOSITORY tablespace already exists and you specify a different repository user, an error message prompts: “Do you wish to change it to manage the repository owned by user ” on service ”?”. Regardless of your response (“Yes” or “No”), the following page appears if OEM_REPOSITORY exists.
Figure 3-11 Select Repository User Tablespaces when OEM_REPOSITORY Exists
Select the default and temporary tablespaces for the Enterprise Manager repository to utilize.
If the OEM_REPOSITORY tablespace does not exist, the following page is displayed:
Figure 3-12 Select Repository User Tablespaces when OEM_REPOSITORY is New
Choose a default tablespace and a temporary tablespace from the provided lists.
Click “Next” to proceed. If sufficient free space is detected in the default tablespace, the Create Repository Summary page appears. Otherwise, error messages will be displayed.
Reviewing the Repository Creation Summary
If you chose to customize repository creation details, the Create Repository Summary page presents a consolidated view of all provided information.
The following page appears when the “Custom” option was selected earlier.
Figure 3-13 Create Repository Summary Page
Click “Finish” to initiate repository creation or “Back” to modify settings.
Upon clicking “Finish,” the Configuration Assistant Progress window emerges, displaying the ongoing processing steps.
Monitoring the Configuration Assistant Progress
The Configuration Assistant Progress window provides real-time feedback on the repository creation process.
For detailed logs and error information, click “Show Details” to expand the dialog. “Hide Details” collapses the detailed view.
Figure 3-14 Configuration Assistant Progress Window
The “Cancel” button transitions to “Close” upon process completion, regardless of success or failure. A “Processing completed.” message indicates successful completion.
Clicking “Cancel” during processing halts the operation, potentially leaving the repository in an indeterminate state. In such cases, dropping the repository using EMCA is recommended.
Click “Close” to exit the Configuration Assistant.
If repository creation fails, drop the repository, enable Management Server tracing by adding relevant properties to omsconfig.properties, and retry the repository creation procedure. Refer to Appendix B, “Activating Logging and Tracing” of the original article for tracing details. For repository dropping instructions, see “Dropping an Existing Repository”.
Configuring a Local Management Server to Use an Existing Repository
In environments with multiple Oracle Management Servers, sharing a repository among a set of Management Servers is a common practice. Typically, only one Management Server runs per node.
Select the “Configure local Management Server” option in EMCA for tasks such as:
- [Task 1 – Original Article Context Needed Here If Available]
- [Task 2 – Original Article Context Needed Here If Available]
- [Task 3 – Original Article Context Needed Here If Available]
As network size and managed services grow, or if a Management Server becomes overloaded, adding more OMS instances to the middle tier distributes the workload.
Multiple Management Servers enhance fault tolerance. If one OMS fails, others continue operations. Clients connected to the failed OMS can immediately reconnect and register with available OMS instances sharing the same repository, ensuring business continuity. Clients registered with unaffected OMS instances remain operational.
In CPU-bound scenarios, adding Management Servers provides an alternative to increasing node capacity.
Note: All Management Servers sharing a repository must reside within the same DNS Domain.
To deploy an OMS on a specific machine, first install the Oracle Management Server software. Consult the database release installation guide for detailed instructions.
When adding a new Management Server, EMCA must be run to update the configuration on that node. EMCA can only modify configuration parameters (omsconfig.properties) for the local machine. Configuration changes on other OMS instances sharing the repository require running EMCA on each respective machine.
Repository connection information (username, password, service) must be set or updated to point to the correct repository. Consistency in configuration parameters across all OMS instances sharing a repository is crucial.
Note: Password changes for the repository user account necessitate corresponding updates to the Management Server configuration on every OMS instance using that repository. Failure to do so will cause subsequent Management Server startups to fail.
Refer to “Starting the Enterprise Manager Configuration Assistant” for EMCA startup instructions.
Configuration Operation Selection
Select “Configure local Management Server” from the Configuration Operation page and click “Next.”
Refer to “Configuration Operation” for details on this page.
Configure Management Server for Existing Repository
On the Configure Management Server page, choose “Use an existing repository” to configure a secondary or subsequent Management Server to share a repository. Click “Next.”
If a configuration already exists, the Edit or Create Dialog appears (Figure 3-3, “Edit or Create Dialog”). Clicking “Edit” directly navigates to the Edit Configuration Parameters page.
Editing Configuration Parameters for Existing Repository
The Edit Configuration Parameters page is where you direct the local Management Server to utilize an existing repository by providing the username, password, and service details.
- User Name: Enter the username of the existing repository. This is a database username, not an OEM administrator username.
- Password: Enter the password for the repository user.
- Service: Specify the service/database where the repository resides.
These details are used upon the next Management Server startup. Invalid information will prevent successful startup.
Do not save username and password: You can choose whether to save credentials in omsconfig.properties. Storing them enables automatic login. Not saving them activates secure Management Server mode. On Windows, unsaved credentials can be provided in the Control Panel’s Startup Parameters or will prompt a dialog at startup. On UNIX, the Management Server prompts for credentials at startup if not saved.
Click “Next” to proceed.
If credentials are not saved, a login dialog will prompt for them. EMCA validates the repository connection and displays any errors. Successful validation leads to the Select Management Region page.
Selecting a Management Region
Management Regions are beneficial for large, global Enterprise Manager deployments or deployments spanning LANs and WANs. They enhance performance over slower networks by allowing assignment of Management Servers and discovered nodes to specific regions, minimizing cross-regional communication. Management Regions also aid in mapping nodes within firewall boundaries.
Example: Company XYZ with OMS in England managing English targets and OMS in California managing Californian targets. Management Regions prevent cross-regional monitoring and enforce geographical or firewall-based management boundaries.
EMCA creates a default Management Region named DEFAULT. By default, all OMS instances and discovered nodes sharing the repository are placed in DEFAULT. For simpler deployments, DEFAULT may suffice. However, for advanced regional management, creating additional Management Regions and assigning specific nodes and OMS instances is recommended.
If an OMS is not yet assigned to a Management Region, EMCA prompts for assignment or creation of a new region. In most cases, the Select Management Region page will appear with disabled options, indicating pre-assignment. An explanatory message will be displayed.
When the local OMS is not yet assigned, the following page appears:
Figure 3-15 Assign Management Region Page
Note: Management Region creation and assignment are also accessible via the Enterprise Manager Console by Super Administrators.
Choose an existing region or create a new one.
- An existing region: Select from the “Region” dropdown list.
- A new region you create: Enter a “Region Name.”
Note: Changes to either the Edit Configuration Parameters or Select Management Regions page are required to proceed. Clicking “Next” without modifications will trigger an error: “There were no changes to the configuration parameters. Make changes or cancel.”
Configuration Parameters Summary Review
The Configuration Parameters Summary page displays a review of all configuration settings. Click “Finish” to apply changes or “Back” to modify.
Note: EMCA only modifies Management Server configuration parameters in ORACLE_HOMEsysmanconfigomsconfig.properties. It does not change repository usernames or passwords within the repository itself after creation. Password manipulation within the repository only occurs during initial repository creation.
Upgrading a Release 2.x Repository to 9i
Pre-9i repositories are not automatically upgraded during installation. Manual upgrade via EMCA is required post-installation.
EMCA directly upgrades Release 2.x repositories to 9i. Post-upgrade, the repository is at the newer version. Direct migration from Release 1.x to 9i is a two-step process: first migrate 1.x to 2.x using the Enterprise Manager Migration Assistant, then upgrade 2.x to 9i with EMCA. Refer to the Oracle Enterprise Manager Configuration Guide Release 2.2 for 1.x to 2.x migration steps.
Stopping Management Servers and Applications Before Upgrade
Before upgrading, stop all Management Servers and Oracle Enterprise Manager applications using the repository. Active Management Servers will cause upgrade errors.
Repository Backup Prior to Upgrade
Back up the database or repository schema using standard export mechanisms before initiating the upgrade.
Note: Repositories created under the SYS user cannot be exported.
The EXPORT utility is a base Oracle database utility. Refer to Oracle9i Utilities for detailed information. Upgrade failures can render the repository unusable and unlisted for future upgrades.
Coordinating Oracle Enterprise Manager Product Upgrades
When upgrading a Release 2.x repository to 9i, ensure all Oracle Enterprise Manager components are upgraded to 9i before proceeding.
Repository upgrades should be coordinated with software upgrades across all machines sharing the repository. Upgrading the repository without upgrading associated software components can lead to incompatibility. Conversely, older software versions are incompatible with upgraded repositories.
Enterprise Manager Console, Packs, Management Server, and repository must all be of the same release version. For example, a Release 2.2 Management Server and repository cannot be used with a Release 9i Console, and vice versa.
For upgrades, ensure all Enterprise Manager products intended for use with the repository are upgraded to 9i. Do not upgrade the Management Server and repository to 9i if older versions of Packs are still in use.
Note: Reports scheduled and generated with Enterprise Manager Reporting Wizard Release 2.2 cannot be upgraded to Release 9.2.
EMCA Upgrade Steps
Follow these steps to upgrade your repository.
Note: Job and event details are stored in encrypted binary fields using the schema owner name as the decryption key. Repository migration to another database is possible, but the schema name must remain consistent. Schema name changes during export/import will render jobs and events unusable due to decryption key mismatch.
Refer to “Starting the Enterprise Manager Configuration Assistant” for EMCA startup instructions.
Configuration Operation Selection for Upgrade
Select “Upgrade an existing repository” on the Configuration Operation page and click “Next.” The Select Database for Repository page appears.
Selecting Database for Repository Upgrade
Log in to the database containing the repository to be upgraded. DBA privileges are required. The repository schema user lacks sufficient privileges for this step. Use a DBA account like system/manager.
Refer to “Select Database for Repository” for database login details. Successful login leads to the Select Repository page.
Selecting Repository for Upgrade
The Select Repository page lists Release 2.0, 2.1, 2.2, and 9.0.1 repositories available for upgrade. Release 9.2 repositories are not listed as they are already up-to-date.
- Username: Repository username.
- Version: Repository version.
- Type: Repository type (“Enterprise” or “Standalone”).
Select the repository and click “Next.” If no eligible repositories are found, the list is empty, and a “No repositories were found” message appears. Click “Cancel” to exit or “Back” to select a different database.
Repository Login Information for Upgrade
Provide the repository user password on the Repository Login Information page. This user owns the repository and was created during repository creation. Repository upgrade requires logging in as this user.
The username is pre-filled based on your previous selection. Enter the password. Click “Next” to proceed to the Upgrade Repository Summary page.
Upgrade Repository Summary Review
The Upgrade Repository Summary page shows a summary of upgrade settings. Click “Finish” to start the upgrade or “Back” to modify settings.
Monitoring Upgrade Progress
The Configuration Assistant Progress window tracks the upgrade process. Click “Show Details” for detailed logs. “Cancel” changes to “Close” upon completion. “Processing completed.” signifies success. Canceling during upgrade renders the repository unusable. Click “Close” to exit.
During upgrade, the Oracle Management Service will be created if it doesn’t exist and if the upgraded repository is used by the local Management Server.
Dropping an Existing Repository
Dropping a repository requires DBA privileges. Follow these steps to drop a repository and deconfigure the local Management Server if it’s using that repository.
Stopping Management Servers and Applications Before Dropping
Stop all Management Servers and Oracle Enterprise Manager applications using the repository before dropping it. Active Management Servers will cause errors.
Starting the Configuration Assistant for Dropping
Refer to “Starting the Enterprise Manager Configuration Assistant” for EMCA startup instructions.
Drop Repository Configuration Operation Selection
Select “Drop an existing repository” on the Configuration Operation page and click “Next.” The Select Database for Repository page appears.
Selecting Database for Repository Drop
Log in to the database containing the repository to be dropped using DBA privileges, such as system/manager. The repository schema user does not have sufficient privileges.
Refer to “Select Database for Repository” for login details. Successful login leads to the Select Repository page.
Selecting Repository to Drop
The Select Repository page lists all repositories (Release 2.0 and later) for dropping.
- Username: Repository username.
- Version: Repository version.
- Type: Repository type (“Enterprise” or “Standalone”).
Select the repository and click “Next.” If no repositories are found, the list is empty, and a “No repositories were found” message appears. Click “Cancel” to exit or “Back” to select a different database.
Selecting Drop Repository Options
The Select Drop Repository Options page allows you to drop either the repository user and all schema objects or just the repository objects.
Dropping only repository objects requires the repository user’s password for EMCA to connect and execute drop scripts. Only repository objects are removed; other schema objects remain.
Dropping the repository user and all objects does not require a password. Ensure no other valuable objects exist in the schema before proceeding as data loss is possible.
For older repositories, dropping the repository user is the only valid option as drop scripts are designed for the latest version.
If a managed repository is detected in omsconfig.properties and you are not dropping it, EMCA will not modify the Management Server configuration. If you are dropping the managed repository, EMCA will clear the Management Server configuration.
Click “Next” to proceed to the Drop Repository Summary page.
Drop Repository Summary Review
The Drop Repository Summary page summarizes drop operation settings. Click “Finish” to initiate repository removal or “Back” to modify settings.
Monitoring Drop Repository Progress
The Configuration Assistant Progress window tracks the drop process. Click “Show Details” for detailed logs. “Cancel” changes to “Close” upon completion. “Processing completed.” signifies success. Canceling during the drop may lead to an unusable state. Click “Close” to exit.
Controlling the Management Server After Configuration
Post-configuration, the Management Server facilitates distributed control between clients and managed nodes, acting as a central engine for notifications and task processing.
Starting a Local Management Server
The repository database and listener must be running before starting the Management Server.
Starting on Windows
Follow these instructions to start the Management Server on Windows.
Note: Step 4 (presumably related to service configuration based on context, original article needed for details) is a one-time setup.
Note: The Management Server service is automatically started and set to Manual on Windows during repository creation if EMCA was launched from an installation session and repository credentials were saved. If credentials were not saved, they can be entered in the Control Panel’s Startup Parameters or will prompt at startup.
Starting on UNIX
On UNIX, use the command:
% oemctl start omsProvide the repository username and password when prompted if credentials were not saved during configuration. Refer to “Repository Login Information” for repository owner details.
Note: Ensure the ORACLE_HOME environment variable is correctly set to the Management Server’s Oracle home. Incorrect ORACLE_HOME settings can lead to startup failures. Refer to “Management Server May Not Run Correctly from a Non-Default Oracle Home” for environment configuration details.
Checking Management Server Status
To quickly check the status (up or down) on Windows or UNIX, use:
% oemctl ping omsFor detailed status information on a local Management Server, use:
% oemctl status omsYou will be prompted for Oracle Enterprise super administrator credentials.
For remote Management Server status checks, use:
% oemctl status oms sysman/<password>@<connect_string>Example:
% oemctl status oms sysman/sysman@dlsun2305The oemctl status oms command returns information including:
- [Status Detail 1 – Original Article Context Needed Here If Available]
- [Status Detail 2 – Original Article Context Needed Here If Available]
- [Status Detail 3 – Original Article Context Needed Here If Available]
- …
Example output:
OEMCTL for Windows NT: Version 9.2.0.1.0 Copyright (c) 1998, 2002 Oracle Corporation. All rights reserved. The Oracle Management Server on host [znripley-pc.ovenbird.com] is functioning pr operly. The server has been up for 0 00:00:25.953 Target database session count: 0 (session sharing is off) Operations queued for processing: 1 Number of OMS systems in domain: 1 (znripley-pc.ovenbird.com) Number of administrators logged in: 0 Repository session pool depth: 15 Repository session count: 8 in-use and 1 available, pool efficiency: 18%Stopping a Local Management Server
To stop a local Management Server:
- Windows: You will be prompted for Oracle Enterprise super administrator credentials.
- UNIX: Use the command:
% oemctl stop omsYou will be prompted for Oracle Enterprise super administrator credentials.
Figure 3-1 Welcome Page of Enterprise Manager Configuration Assistant
Alt Text: Welcome screen of Oracle Enterprise Manager Configuration Assistant, showing the initial page for configuring the management server.
Figure 3-2 Configuration Operation Page in EMCA
Alt Text: Configuration Operation page within Enterprise Manager Configuration Assistant, highlighting options for configuring the local management server and other repository operations.
Figure 3-3 Edit or Create Configuration Dialog
Alt Text: Dialog box in Enterprise Manager Configuration Assistant asking user to choose between editing an existing management server configuration or creating a new one.
Figure 3-4 Configure Management Server Page
Alt Text: Configure Oracle Management Server page in EMCA, presenting options to create a new repository or use an existing repository for the Oracle management server.
Figure 3-5 Create New Repository Options Page
Alt Text: Create New Repository Options page in Enterprise Manager Configuration Assistant, offering ‘Typical’ and ‘Custom’ methods for setting up a new repository for oracle management server.
Figure 3-6 Create Repository Summary for Typical Setup
Alt Text: Summary page displayed during typical repository creation in Enterprise Manager Configuration Assistant, outlining the configurations for the new oracle management server repository.
Figure 3-7 Select Database Location Page
Alt Text: Select Database Location page in EMCA, allowing users to choose between a new local database instance or another existing database for the Enterprise Manager repository.
Figure 3-8 Change Database SID Dialog
Alt Text: Change Database SID dialog in Enterprise Manager Configuration Assistant, used to modify the Oracle System Identifier for the local database instance.
Figure 3-9 Select Database for Repository Login Page
Alt Text: Select Database for Repository page in EMCA, prompting for database login credentials to access the database intended for the Oracle Management Server repository.
Figure 3-10 Repository Login Information Page
Alt Text: Repository Login Information page in Enterprise Manager Configuration Assistant, requesting username and password details for the repository user account.
Figure 3-11 Select Repository User Tablespaces when OEM_REPOSITORY Exists
Alt Text: Select Repository User Tablespaces page shown when OEM_REPOSITORY exists, allowing selection of default and temporary tablespaces for the repository user.
Figure 3-12 Select Repository User Tablespaces when OEM_REPOSITORY is New
Alt Text: Select Repository User Tablespaces page displayed when OEM_REPOSITORY is new, requiring selection of default and temporary tablespaces for the new repository.
Figure 3-13 Create Repository Summary Page
Alt Text: Create Repository Summary page in Enterprise Manager Configuration Assistant, summarizing all settings before creating the new Oracle Management Server repository.
Figure 3-14 Configuration Assistant Progress Window
Alt Text: Configuration Assistant Progress window displaying the status and steps during Oracle Management Server configuration operations.
Figure 3-15 Assign Management Region Page
Alt Text: Assign Management Region page in Enterprise Manager Configuration Assistant, providing options to assign the management server to an existing or new management region.
