| Oracle® Enterprise Manager Configuration Change Console Installation Guide 10g Version 10.2.0.5 for Windows or UNIX Part Number E15311-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Configuration Change Console Installation Guide 10g Version 10.2.0.5 for Windows or UNIX Part Number E15311-01 |
|
|
PDF · Mobi · ePub |
Before creating the database for the Configuration Change Console, you first need to install the software for the Oracle database. The server will work with an Oracle 10g (version 10.2.0.4 or greater) database on any operating system. The product requires Oracle Database Enterprise Edition. Standard Edition will not work because features such as partitioning, bitmap indexes and materialized views are used.
A basic installation requires three tablespaces totalling 8 gigabytes of space in addition to the space required for the Oracle database software.
Please refer to the Oracle installation guide for the database you are installing for more information about how to install the software.
Once you have the Oracle database software installed, you need to create a database instance for the Configuration Change Console server to use for its repository. The instructions displayed here apply to an Oracle 10g database running on Windows. The process is the same for Unix-based databases as well.
On the machine featuring your Oracle database installation, click Start -> Run
From the Run box, enter dbca in the Open field. Click OK. This will launch the Database Configuration Assistant.
The welcome screen will display. Click Next.
Select the operation Create a Database, and click Next.
Select General Purpose and click Next.
Enter gateway in the Global Database Name field. The SID field will populate automatically. This is the suggested name for the database as it is used throughout the documentation. Click Next.
Configure the management options according to how you normally manage your databases. By default, Enterprise Manager and Database Control will be selected. Click Next.
Specify the password for the sys account. You will need to know this password later in the installation. Click Next.
Select the storage mechanism you would like to use for the database. This will depend on your environment. The default option is File System. Click Next.
Select the locations for database files. This will depend on your environment. The default is Use Database File Locations from Template. Click Next.
Specify your recovery options. This setting depends on your environment. If you are unsure, use the default settings. click Next.
No sample schemas or scripts are to be run during this database creation. Click Next.
On the Memory tab, set the amount of memory you want to use for this database. If you are on a database server dedicated to Configuration Change Console, increase the memory to fully utilize the server.
On the Character Sets tab, select Use Unicode (AL32UTF8).
Under the Connection Model tab, select Dedicated Server Mode. Click Next.
Review the Database Storage settings and change according to your environment requirements. Click Next.
On the final screen, check mark Create Database and click Finish.
On the summary screen, verify all parameters and correct any errors, the click OK.
Follow these steps to configure the database:
Start Oracle Enterprise Manager Database Control. From the Start menu, navigate to Programs --> Oracle-OraDb10g home1 and then click on Database Control - gateway.
Log into Database Control as the sys user with the sysdba role.
In this section, you will create the following tablespaces. Even if you use a different name for the database SID, you must use the tablespace names specified in this document.
GATEWAY
GATEWAY_LGDATA
GATEWAY_INDEX
When configuring the tablespace sizes, you must first determine the database size from the Determining the Database Size section. For this example we will assume the minimum size which is suitable for an evaluation set up with up to 20 agents.
The GATEWAY tablespace should be a minimum of 2 GB for a production environment
The GATEWAY_LGDATA tablespace should be a minimum of 2 GB but must be large enough to accommodate any expected data growth
The GATEWAY_INDEX tablespace is typically twice as big as the GATEWAY_LGDATA tablespace
The GATEWAY_INDEX tablespace should be a minimum of 4 GB but must be large enough to accommodate any expected data growth
Follow these steps to create the tablespace manually. See below for instructions on finding a script to help with tablespace creation:
From the Database Instance: Gateway screen, click on the Administration tab.
Navigate to Database Administration --> Storage and then click on the Tablespaces link.
Click Create.
Enter gateway in the Name field. You can leave all other tablespace settings the same or change them depending on your environment.
Click Add under the Datafiles section.
Enter the file system name for the datafile. For example, gateway_01
Set the file size for this datafile. If using the minimum requirements discussed above, enter 2 GB.
Click Continue.
Add more datafiles if necessary, depending on Oracle database recommendations for maximum datafile size on your operating system.
Click Create.
A screen should appear indicating the creation of the tablespace. Click OK.
Repeat steps 1 through 11 for the GATEWAY_LGDATA and GATEWAY_INDEX tablespace. Substitute the tablespace name, datafile name, and size to match what is required for each tablespace.
If you do not want to create the tablespaces manually, there is a script available with the product. Locate the oracle-install.zip file that comes with the Configuration Change Console media. Unzip this file and locate the file oracle-install\scripts\dbstructure\tablespaces.sql.
You can modify this script and run it to create the tablespaces. Note that this script will not work without customization for your environment.
For an evaluation environment for the Configuration Change Console, the out-of-the-box TEMP and UNDO tablespace sizes should be sufficient.
For an environment with a large number of agents, you should allocate 4 GB for the TEMP tablespace and 4 GB for the UNDO tablespace.
For an evaluation environment or production environment with a small number of agents and low change rate, the out-of-the-box REDO log settings should be sufficient.
For an environment with a large number of agents or high change rate, more redo logs and redo log groups may be needed. Given the potential high transaction rate of Configuration Change Console, each redo log should be at least 500MB in size. Check with your database administrator for guidelines on how to properly configure the REDO log management.
The users.sql script is used to create the gateway user. Copy the oracle-install folder from the Configuration Change Console media to a folder installed on your system (parent directory where you placed the oracle-install folder is referred to as <BASE_PATH> in this document).
The users.sql script can be found in the following location:
<BASE_PATH>\oracle-install\scripts\dbstructure\users.sql
Note:
The Oracle database and tablespaces must already exist as documented above before creating the user.To create the gateway user, open a command prompt and enter the following command:
sqlplus /nolog
Log in as the sys user with dba privileges where <password> is the sys account password:
connect sys/<password>@gateway as sysdba
Run the users.sql script by typing the following where you replace <BASEPATH> with the directory to where you copied oracle-install:
@<BASE_PATH>\oracle-install\scripts\dbstructure\users.sql
You will be prompted to delete an existing user. If you are performing a fresh install, ignore the error message that the user could not be found. If you have a user already configured on the system that you would like to replace, then enter this user name here.
At the prompt, enter the user name for the user that the server will connect as to the database. The suggested user name is gateway. Enter a password for the user when prompted. The password will not be shown to the screen.
At the prompt, enter a role name. The suggested role name is gateway_dba. This step creates a specific role for database maintenance and other assignments. The user you are creating will automatically be assigned to this new role.
The configuration of initialization parameters for the database instance should be created according to your typical production standard configurations.
For Oracle 10g, the default initialization parameters are known to work out of the box with the Configuration Change Console server.
When sizing your database, you should consider the number of concurrent processes and sessions your database has configured.For a non-clustered installation, Weblogic is configured to use, at most, 200 JDBC connections. The database should be configured to have 250 processes and 375 sessions (1.5 x processes). If you increase the Weblogic JDBC pool size, the database must be adjusted accordingly.For a large environment, the cluster configuration determines how many connections will be needed in the database. For example, if you have a clustered environment with a Primary Server, 3 Secondary Servers, and 4 Messaging Brokers, you may have the Weblogic JDBC connection pool set to 300 connections. The determination of the number of connections is described in more detail in Adjusting the Database Connection Sizes related to Cluster Installations. With these 4 servers connecting to the database, Weblogic will consume, at most, 1200 connections. To support this, the database will need 1250 processes and 1875 sessions.
Load the schema and seed-data for the Configuration Change Console by following these steps:
Open a command window or shell
Change your directory to <BASE_PATH>/oracle-install where you copied this directory from the Configuration Change Console media.
At a prompt, run the following command:
DBCreateEE.bat gateway password sid > dbload.out
On UNIX, use the following procedure where you replace password with your gateway user password and replace sid with the name of the database.:
DBCreateEE.sh gateway password sid > dbload.out
Once the script is finished running, open the dbload.out file and review it to ensure there are no errors. This is a very important step as any errors caused at database schema load time will most likely cause failures in the server operation.
At this point, database installation is finished and you can now move on to the Configuration Change Console Server installation.
|
 Copyright © 2003, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
