Professional Documents
Culture Documents
com
Date : 18-JUN-2009
Status : Draft
Author : Sethunath.U
File : Oracle_OEM10g_Grid_Control_Solaris.doc
Pages : 75
Classification: Technology Guidelines
History
References
1. Oracle® Enterprise Manager Grid Control Quick Installation Guide for Solaris (SPARC) 10g
Release 2 (10.2) - b31198
2. oracle.ittoolbox.com-Workaround for ''Management Services and Repository' Target is
Temporarily in Status Pending State'
3. Metalink Notes 418199.1, 419886.1, 734981.1, 303359.1
4. http://www.oracle.com/corporate/pricing/technology-price-list.pdf
5. http://www.oracle.com/technology/documentation/oem.html
6. http://www.oracle.com/technology/obe/fusion_middleware/wls103/InstallConfig/install_wls/Install_
WLS.htm
Table of Contents
1 Introduction ................................................................................................................ 9
2 Purpose ...................................................................................................................... 9
3 Disclaimer .................................................................................................................. 9
11 Licensing............................................................................................................... 67
II. Appendix 2 Oracle 10g Grid Control management packs Licensing information................... 75
Table of Figures
Figure 1: Start Oracle Universal Installer ....................................................................................................... 14
Figure 2: Specify Installation Location ........................................................................................................... 14
Figure 3: Specify Inventory directory and Location ........................................................................................ 15
Figure 4: product specific pre-requisite checks.............................................................................................. 16
Figure 5: Specify configuration....................................................................................................................... 17
Figure 6: Specify optional configuration ......................................................................................................... 18
Figure 7: Specify security option .................................................................................................................... 18
Figure 8: Summary of installation options selected ....................................................................................... 19
Figure 9: Installation screen ........................................................................................................................... 20
Figure 10: Execute configuration scripts ........................................................................................................ 20
Figure 11: DB Configuration Assistant ........................................................................................................... 24
Figure 12: Grid control Configuration Assistants .......................................................................................... 24
Figure 13: End of installation.......................................................................................................................... 25
Figure 14: Starting Agent installation ............................................................................................................. 26
Figure 15: Specify agent installation location................................................................................................. 26
Figure 16: product specific checks for Agent installation ............................................................................... 27
Figure 17: Specify Oracle Management Service Location ............................................................................. 27
Figure 18: Specify agent registration password ............................................................................................. 28
Figure 19: Specify OCM registration .............................................................................................................. 28
Figure 20: Specify connection settings .......................................................................................................... 29
Figure 21: Agent installation progress ........................................................................................................... 29
Figure 21: Execute root.sh for agent installation ........................................................................................... 30
Figure 23: End of agent installation ............................................................................................................... 30
Figure 24: Grid control login ........................................................................................................................... 31
Figure 25: Search and find target .................................................................................................................. 31
Figure 26: Added target and it’s details ......................................................................................................... 32
Figure 27: Added targets and it’s details ........................................................................................................ 32
Figure 28: Specify Home Details (OMS Upgrade) ......................................................................................... 39
Figure 29: Provide Metalink Credentials (OMS Upgrade) ............................................................................. 40
Figure 30: Product Specific Checks (OMS Upgrade) .................................................................................... 40
Figure 31: Provide Repository Administrator Password(OMS Upgrade) ....................................................... 41
Figure 32: Provide Application Instance Password(OMS Upgrade) .............................................................. 41
List of Tables
Table 1: Certification Matrix – OMS and Agent Vs Weblogic ........................................................................ 62
Table 2: Management Pack Price List ........................................................................................................... 70
1 Introduction
The Oracle Grid offers a proven solution that allows businesses to heighten application
performance and deliver unparalleled IT infrastructure reliability. Businesses of all sizes attain
measurable IT cost savings by extending the availability of computing resources, cultivating more
productive and effective administrators, and achieving higher quality of service—all direct benefits
of the Oracle Grid. A critical ingredient to achieving the full benefits of the Oracle Grid is
employing the right solution for managing the grid systems and, most importantly, the applications
that run on those systems.
Oracle Enterprise Manager 10g is Oracle's single, integrated solution for managing all aspects of
the Oracle Grid and the applications running on it. Grid Control couples a potent, top-down
monitoring approach to delivering the highest quality of service for applications with a cost-
effective automated configuration management, provisioning, and administration solution. This
powerful combination provides unequaled management for any size Oracle data center.
2 Purpose
This document describes how to quickly install and configure Oracle Enterprise Manager Grid
Control on Solaris (SPARC) systems.
3 Disclaimer
You may use this document on your on responsibility and the author of this document is not
responsible for any damage that are caused by the actions described in this document. Though
the steps described in this document has strictly followed oracle documentation, it reflects the
author’s point of view and NOT Oracle Corporation’s . This document is not certified by Oracle.
Use this document at the user’s discretion and risk.
Oracle ™, Solaris ™, Sun ™ are registered trademarks of Oracle Corporation and Sun Micro
Systems respectively. All other trademarks are registered trademarks of the corresponding
organizations.
Author is not responsible for any legal issues associated with the actions described in this
document. This is strictly a technology guide and freely accessible service document open for all
interested parties.
If you copy the contents of this document elsewhere make sure to keep the trademarks,
copyrights, references and credits described in this document.
4 The environment
The environment used in this document is
Server : Sun Fire V245 (Sparc)
OS : Solaris 10
5 System Requirements
The system or systems must meet the minimum hardware and software requirements given in the
following sections. Even though Oracle Universal Installer runs prerequisite checks on your
system to verify that it meets the listed requirements, to make sure that prerequisite checks do not
fail, you should verify the requirements before running Oracle Universal Installer.
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=256
set shmsys:shminfo_shmmax=4294967295
set shmsys:shminfo_shmmni=100
1. Make a project named "user.oracle" in /etc/project with the user oracle as it's only member. (If it
does not exist)
bash-3.00# projadd -U oracle -K \
> "project.max-shm-memory=(priv,4096MB,deny)" user.oracle
2. Verify it
# cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::
user.oracle:100::oracle::project.max-shm-memory
=(priv,4294967296,deny)
bash-3.00# cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::
user.oracle:100::oracle::project.max-shm-memory=(priv,4294967296,deny)
bash-3.00$ cd /data1/oracle/dvd
bash-3.00$ ./ runInstaller
Select one of the installation types provided. The complete installation type is chosen by default.
Specify the "parent" directory location for the installation. All Oracle homes created during installation will
be placed as subdirectories under the parent directory.
Appears only during the first installation of Oracle products on a system. Specify the full path of the Oracle
Inventory directory. Make sure to select the appropriate operating group.
Verify that all prerequisite checks succeed. OUI checks the system to verify that it is configured correctly
to support your Oracle software. If you have met all hardware and software requirements in this guide, all
of the checks should pass. If a check fails, review the cause of failure, rectify the problem, and retry the
check. You can also choose to manually verify failed checks if you are satisfied that your system meets the
requirements.
Appears only for the "Enterprise Manager Grid Control Using a New Database" installation type.
Specify the name of the database you want to create, as well as the location to store the
Management Repository files. Choose a file location outside of the Oracle home. Select the
OSDBA and OSOPER groups that you are a member of. These memberships are required to
grant the SYSDBA and SYSOPER privileges required to create the new database.
All parameters can be configured through Grid Control after installation. If you want, set the parameters
for email notification, OracleMetaLink credentials, and proxy configuration settings.
Appears only for the "Enterprise Manager Grid Control Using a New Database" installation type.
Specify password used to secure the Management Service, as well as passwords to secure the
Management Repository Database. The first password will be asked during agent installation .
Reference Link : 8.5 Specify agent registration password
This screen displays status information while the product is being installed.
When prompted, read the instructions and run the scripts listed here. You must run the scripts as root
from a terminal window.
Login as root and run the above two scripts. The output will be as follows.
# /data2/oracle/oraInventory/orainstRoot.sh
-e
Starting to execute allroot.sh .........
ORACLE_OWNER= oracle
ORACLE_HOME= /data2/oracle/OracleHomes/db10g
Adding to inittab
Contains important information about your installation, including the URLs configured for your
applications. Make a note of these URLs. The port numbers used in these URLs are recorded in the
following file: $ORACLE_HOME/install/portlist.ini
Note : At the end of the instllation one configuration assistant was failed with error
'oracle.sysman.emcp.agent.AgentPlugIn has failed'. A work around has been implemented to solve this
issue, which is detailed under section Exception Number - 1
Make an appropriate directory for the agent software to be loaded into, like:
Enter the name of grid control server followed by port number. Make sure your grid control server up and
running and the server is reachable from the monitored host target (her the Linux box where the agent is
being installed)
This is the password you entered during Grid Control server setup. Reference Link 7.7 Specify security
option
Enter the Oracle CSI number and metalink account name if you want to enable oracle configuration
manager.
Click in (Targets) tab and enter the host name where the agent had been installed,
up and running.
This will display the specified target and it’s details as above.
a. Backup $AGENT_HOME,$OMS_HOME,$DB_HOME
b. Backup Database (Cold backup)
c. Backup Inventory directory
2. Make sure that you meet the product pre-requisites (operating system patches, packages
etc.) for the 10.2.0.5 patch set. For information about platform-specific package and kernel
requirements, refer to the Enterprise Manager Grid Control Installation and Basic
Configuration Guide.
3. Before upgrading your Oracle Management Service, ensure that the shared pool size is
set in your Grid Control repository database as per your infrastructure. Minimum size for
shared pool is 512 MB. For information about the fixed initialization parameter values,
refer to the pre-installation requirements described in the Enterprise Manager Grid Control
Installation and Basic Configuration Guide.
4. Be sure that the partitioning option is enabled in the database that contains the Grid
Control repository (Sysman schema) . Connect to the Database as sysdba and run the
following query to determine whether the Partitioning Option is installed:
5. Both the DBSNMP and SYSMAN users require the EXECUTE privilege on the
DBMS_RANDOM package in the Repository Database. You must grant the privilege to
both users as follows:
a. Log into the Repository Database as SYSDBA.
b. Run the following SQL commands:
c. Verify that the query below does not return any invalid objects:
6. If the repository database is configured with the UTF8 character set, the value of
NLS_LENGTH_SEMANTICS needs to be set to BYTE. To check this in the database, run
the following command :
8. If the database containing the Grid Control repository is linked with a Data Guard
database, the database must be forced in logging mode before the upgrade starts to force
all index maintenance commands to be propagated to the standby database. The upgrade
by default will perform the index maintenance commands in a 'NOLOGGING' mode. This
means that any Data Guard database linked to the repository database will not have these
index operations replicated to it.
To make sure these commands get replicated to the Data Guard instance, force the
database into logging mode:
9. If your Enterprise Manager is shut down for a long period of time, you must follow the
below steps before conducting the upgrade:
a. Log into the Repository Database as SYSMAN
b. Run the following SQL:
10. Make sure that there are no invalid sysman objects present in your Grid Control repository.
Important: Oracle recommends that you back up your database before you perform the
upgrade operation. Perform the following steps before upgrading:
a. Login into the Database as SYS user.
b. Check if there are any invalid SYSMAN objects.
c. Go to step b again to be sure all SYSMAN objects are valid. If you still have invalid
SYSMAN objects that are not in the Recycle bin, contact Oracle support.
d. Check to be sure there is no invalid SYS object:
e. If any of the packages fail to become valid even after recompilation, then Contact Oracle
Support to assist you. Once this verification is done, continue through with the rest of the
pre-installation tasks.
11. If the 10.1.0.5.0 database containing the Grid Control repository does not have the CPU
Jan 2008 patch 6826532 applied, then make sure that you apply this patch. If you have
applied the latest CPU Jan 2009 patch 7592360 on your database containing the Grid
Control repository, then you do not need to apply the old CPU Jan 2008 patch 6826532.
12. If you have applied the latest CPU Jan 2009 patch 7608318 to your Oracle Management
Service (OMS) before upgrading, then make sure that permission of the following files
under the Oracle home directory of OMS <ORACLE_HOME>/rdbms/admin is set to 664.
(dbmsaqds.plb,dbmsaw.plb,prvtlmd.plb,prvtpexp.plb,prvtlsby.plb,prvtlms.plb,prvtaqip.plb,p
rvtstas.plb,prvtsqlt.plb,prvttxfm.plb,prvtaqdi.plb,prvtaqds.plb,prvtcdpu.plb,prvtcdpi.plb,prvt
meti.plb,prvtxdbz.plb,exfeapvs.plb,prvtdupg.plb,prvtupgi.plb,prvtkupc.plb,prvtbpw.plb,prvta
qiu.plb,prvtaqim.plb,prvtbsqu.plb,prvtbut4.plb,prvtmetu.plb,prvtmeta.plb,prvtcdcp.plb,prvtc
dcu.plb)
If the permission is not set to 664 for the above files, you will get a permission denied error
during the upgrade.
For example: Error in writing to file
'/u01/app/oracle/product/10.2.0/oms10g/rdbms/admin/dbmsaw.plb' Permission denied
13. Before proceeding with the upgrade, make sure that the dbms jobs are stopped. To do
this, follow these steps:
a. Login into the Database as SYSMAN.
b. Run the following SQL command:
3. Turn off the DBMS Scheduler by running (for version 10.1+ RDBMS) by the following
command:
Make sure that you follow the Pre-installation steps described in the above section 9.1 Pre-
installation Tasks before upgrading any existing Oracle Enterprise Manager 10g Grid Control
Release 2 (10.2.0.x) or higher to Oracle Enterprise Manager 10g Grid Control Release 5
(10.2.0.5)
Note: Make sure that you first upgrade the Oracle Management Service (OMS), and then the
Management Agent before upgrading the database that contains the Management repository
(sysman schema).
Enter the following command to unzip and extract the installation files from the downloaded
software.
$ unzip gc_10205_1of2.zip
$ unzip gc_10205_2of2.zip
This will extract 3731593_10205_SOLARIS64.zip,3731596.zip,3822442.zip and
p3731593_10205_SOLARIS64.zip to the directory.
$ unzip p3731593_10205_SOLARIS64.zip.
This extracts the files to the "3731593" directory.
To stop all the Grid Control components on a host, follow these steps:
1. Stop the Oracle Management Service (OMS) by running the following command from the
Oracle home directory of the OMS, where $ORACLE_HOME is the Oracle home directory
of the Oracle Management Service:
2. Stop the Application Server Control Console, which is used to manage the Oracle
Application Server instance used to deploy the Management Service:
3. Stop all the application server components, such as Oracle HTTP Server and OracleAS
Web Cache by running the following command from the Oracle home directory of the
OMS.
4. Wait four to five minutes to ensure that all the OPMN processes are stopped and TCP
ports are released.
5. Set the Oracle_Home to your Oracle home directory of the Oracle Management Services
before applying the patch set. Set the display as well.
bash-3.00# ORACLE_HOME=/data2/oracle/OracleHomes/oms10g
bash-3.00# export $ORACLE_HOME
bash-3.00# DISPLAY=192.168.6.149:0.0
bash-3.00# export DISPLAY
bash-3.00# cd 3731593/Disk1
bash-3.00# ./runInstaller
Run root.sh while logged in as root and upon completion of running the script, click OK button
above.
9.2.2.9 Configuration Assistants
Note :
The script preinstall.pl, which can be found at the top directory of the extracted patch set, must be
run as perl preinstall.pl <OMSHome> before a Grid Control 10.2.0.5 OMS upgrade if the one-off
#7214697 was applied in the OMSHome before the upgrade. However if the one-off was not
applied,running the script will not cause an issue.
Note: This will only upgrade your Management Agent residing on the OMS host. For detailed
instructions refer to section 4 "Installation Procedure" of the Release notes under the "doc"
directory.The upgrade process then upgrades the Oracle Management Service (OMS), Oracle
Management Repository and the Management Agent on the same host as the OMS to the latest
Enterprise Manager 10g Release 5 (10.2.0.5). This will not upgrade the Database in which
Management repository resides.
Figure 38: Specify Oracle Management Agent Home (OM Agent Upgrade)
Execute the above root.sh script while logged in as root and click OK button above.
10.2.1 Scalability
Grid Control has been designed for scalability. In heterogeneous environments, which include
databases and application servers of different versions on different platforms, the Grid Control
framework scales seamlessly even when the environment has a large number of servers (see
Figure 2). To add a new system to the management target list, the administrator simply installs
the management agent on the system. As the IT infrastructure grows, administrators can add
more management servers for server load balancing.
This home page provide so many information at a glance. The first section “All targets Status”
shows the status of hosts managed by grid control and the total availability percentage. The “All
Targets Alerts” section describes the Critical and Warning alert in various targets and the link
towards the details of alerts.The “All targets Jobs” shows the status of jobs scheduled as
failed/succeeded/suspended etc. Grid control closely watches the security policy violations
through section “Security Policy Violations” The links from each sub sections such as ‘Critical’/
‘Warning’ will show you the details of each of the violation for which you can take remedial
actions. The “critical patch advisories” section shows the live patch update information available
from Oracle Metalink. “Deployment summary” section displays the type of installations, number of
targets against each type, no of installations of each type and patch information for each type.
10.3.4.2 Schedules
Configuring schedules are of extreme importance to receive notifications. You need to set up your
notification schedule in order to receive e-mail notifications for alerts. For each day in the
schedule, specify the e-mail addresses that should be used to send you e-mail notifications. If
multiple teams are working on different work schedules or shifts, the email addresses of those
teams should be entered here. There may be different administrators for different set of targets.
You may change the administrator by selecting the specific administrator( ) and click
“Change”. Then, the schedules for that administrator will be displayed here. Each administrator
has exactly one notification schedule. When an alert needs to be e-mailed to an administrator,
Enterprise Manager consults that administrator's notification schedule to determine the e-mail
address to be used.
In a notification schedule, an administrator can specify different e-mail addresses based on day of
the week and time of the day. When sending e-mail notifications, Enterprise Manager will use the
e-mail addresses appropriate for that day and time. Time periods that are left empty signify
periods where no e-mail notifications should be sent. A notification schedule repeats every
interval specified in the notification schedule definition. Clicking “Continue” will take you to the
following page.
Enter e-mail addresses in each time slot to specify how you should be notified. To fill in many time slots at
once, use 'Batch Fill-in'. Click button to select email addresses you specified in Step 10.3.4.1 E-mail
addresses as below. Then after filling in the email addresses, click to complete the schedule info.
Click in Preferencespreferred Credentials and click against ‘Database Instance’ target type
to navigate to a screen as follows
Click the radio button against a notification rule and click the buttons available in the window to create,
edit, create like or delete a notification rule.
The option “Apply rule to all Database Instance targets” apply the rules to all the database
instances. If you change the option to “Apply rule to specified Database Instance targets or
groups containing Database Instance targets” the screen will be changed as follows.
Click “Add” and add the database targets to which the notification rules will be applied.
OMS and Agent Versions WebLogic 10.x WebLogic 9.x WebLogic 8.1.x and 7.x
10.2.0.2 No No Yes
Select “Oracle Weblogic Server Domain” from the drop down list
and click GO
10.3.7.3 Provide Weblogic Management Server Credentials
Browse and Select / Type the Weblogic Admin Server hostname. Select the correct version of
weblogic server. Enter the weblogic admin server credentials. If the OM Agent is installed in the
same host where Oracle Weblogic Management Server is running, “Agent Host” is not required.
Type the directory name of “weblogic.jar” is located in the host where Oracle Weblogic
Management Server is running. Click next
11 Licensing
It is extremely important to understand the OEM grid Control Licensing policy. Oracle does not
charge anything for OEM Grid Control as a product. Instead the licensing is based on the
“Management Pack” usage per server per processor.
The following packs are available for database management. Click Preferences
When you select each pack against a target database, a license should be acquired for that pack.
Eg : If you select “Database Diagnostic Pack “ for the database “CORPprd1”, and the database is
having 2 processors, total license fee payable for that pack for “CORPprd1” is 2 X 3500 = USD
7000.
• User-defined metrics
• Blackouts/Planned Outages
• Monitoring templates
• Corrective actions (including response actions)
• Adaptive metric thresholds
• Metric Baselines
• Memory Access Mode
• Diagnostic, Performance and Event reports
• Database and repository tables/views/api's that store/expose the above data
The license for the above is same as described under previous section.
Provides performance and availability data collection, real-time and historical monitoring, event
management/monitoring, notifications, and performance reporting for host systems. This plug-in
includes:
• Real-time and historical performance monitoring and trending (Host target)
• Event management/monitoring (Host target)
• Event/Alert Notifications: Notification Methods, Rules and Schedules
• Event/Alert history/metric history (Host target)
• User-defined metrics
• Metric Snapshots
• Blackouts/Planned Outages
• Monitoring templates
• Corrective actions (including response actions)
• Performance and Event reports
• Repository tables/views that store/expose the above data
Offers a complete, cost-effective, and easy to use solution for managing the performance of
Oracle Application Server environments by providing unique functionality such as automatic
identification of performance bottlenecks, guided problem resolution, and comprehensive system
monitoring. The Diagnostics Pack includes:
• Root cause diagnostics of Java application performance issues
• Historical performance monitoring and trending (Application Server and Host target)
• Monitoring of JMX/Web Services endpoints hosted on the Oracle Application Server
• Event/Alert Notifications: Notification Methods, Rules and Schedules
• Event/Alert history/metric history (Application Server and Host target)
• User-defined metrics
• Blackouts/Planned Outages
• Monitoring templates
• Corrective actions (including response actions)
• Metric Snapshots
• Real end user performance monitoring
• End to end tracing with middle tier and database drill downs (database SQL level
diagnostics requires Diagnostics Pack for Oracle Database)
• Prices based on Oracle Technology Global Price List April 28, 2009
• http://www.oracle.com/corporate/pricing/pricelists.html
Grid control is failing at the agent installation with the following error:
Command =
Exception :
java.lang.Exception: 6
-----------------------------------------------------------------------------
/usr/local/oracle/product/agent10g
script contains all commands that failed, were skipped or were cancelled.
This file may be used to run these configuration assistants outside of OUI.
Note that you may have to up date this script with passwords (if any)
-----------------------------------------------------------------------------
recommended that you retry the configuration assistants at this time. Not successfully
running any "Recommended" assistants means your system will not be correctly configured.
1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
3. Select the failed assistants and click the 'Retry' button to retry them.
-------------------------------------------------------------------------
12.1.1.1 Troubleshooting
Checked the logfiles at $AGENT_HOME/ cfgtoollogs/cfgfw
/data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/ oracle.sysman.top.agent_<timestamp>log
data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log
And found that the following error occurred.
Exception : java.lang.Exception: 6
Connected.
no data found
BEGIN
ERROR at line 1:
12.1.1.2 Cause
From the configuration logs we can see that only website creation target has failed. Other than
that everything works fine. This can happen if the machine is to slow/busy for the Agent to upload
data to OMS during installation. The log clearly says that "no data found" as the Agent was not
able to upload data during the configuration phase
12.1.1.3 Solution
1. Backup the following files:
$AGENT_HOME/sysman/emd/targets.xml
$AGENT_HOME/sysman/config/emd.properties
2. Then run "$AGENT_HOME/bin/agentca -f" command.
(Under heavy load it may take some time to create the website target)
3. Click finish to end the installation. Even though the OUI announce that some configuration
assistants failed, it will work fine.
Grid control is failing at the agent installation with the following error:
Command =
Exception :
java.lang.Exception: 6
-----------------------------------------------------------------------------
/usr/local/oracle/product/agent10g
script contains all commands that failed, were skipped or were cancelled.
This file may be used to run these configuration assistants outside of OUI.
Note that you may have to up date this script with passwords (if any)
-----------------------------------------------------------------------------
recommended that you retry the configuration assistants at this time. Not successfully
running any "Recommended" assistants means your system will not be correctly configured.
1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
3. Select the failed assistants and click the 'Retry' button to retry them.
-------------------------------------------------------------------------
12.1.2.1 Troubleshooting
Checked the logfiles at $AGENT_HOME/ cfgtoollogs/cfgfw
/data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/ oracle.sysman.top.agent_<timestamp>log
data2/oracle/OracleHomes/agent10g/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log
And found that the following error occurred.
Exception : java.lang.Exception: 6
Connected.
no data found
BEGIN
ERROR at line 1:
12.1.2.2 Cause
From the configuration logs we can see that only website creation target has failed. Other than
that everything works fine. This can happen if the machine is to slow/busy for the Agent to upload
data to OMS during installation. The log clearly says that "no data found" as the Agent was not
able to upload data during the configuration phase
12.1.2.3 Solution
1. Backup the following files:
$AGENT_HOME/sysman/emd/targets.xml
$AGENT_HOME/sysman/config/emd.properties
2. Then run "$AGENT_HOME/bin/agentca -f" command.
(Under heavy load it may take some time to create the website target)
3. Come back to the OUI installation screen and click finish to end the installation. Even though
the OUI announce that some configuration assistants failed, it will work fine.
Appendix
Total
No Of License
Suppor Processo Price(US
Packs Unit License Price t rs D)
System Monitoring Plug-in Process
for Hosts or 1800 396 4 7200
Diagnostics Pack for Oracle Process
Middleware or 7000 1540 0 0
Process
Database Diagnostics Pack or 3500 770 4 14000
Total 21200
Discount (Change
Here)==>> 35% 7420
Net 13780
Core Total
Total CPU(Core) Core Factor Cores
Hosts 2 2 2 0.5 4
Databases 2 2 2 0.5 4
Weblogic Servers 0 4 2 0.25 0
Ref : Prices based on Oracle Technology Global Price List as on April 28, 2009
II. Appendix 2 Oracle 10g Grid Control management packs Licensing information
Oracle Enterprise
Manager 10g Release 5 Grid Control License Information.mht