安裝Oracle Enterprise Manager 10g Grid Control Release 10.1.0.3

1.2 Installation
1.2.1 Resuming Agent Installations After Failure
While performing "Complete Enterprise Manager with a Database", "Complete Enterprise Manager in an Existing Database" or "Additional Management Service" install, if the agent install fails, you can resume the Management Agent install after exiting Oracle Universal Installer by performing the following steps :

a) Set the environment variable EM_REPOS_PWD to the value of sysman schema password entered in the OMS install, using "setenv" for C-Shell and export for Korn shell .
b) If the install performed was "Complete Enterprise Manager with a Database" or "Complete Enterprise Manager in an Existing Database", set the environment variable EM_REPOS_DBSYSPWD to the value of sys schema password
c) Execute the installer using the following command:

runInstaller -responseFile /agent/agent.rsp

Alternately, you can run the installer in GUI (interactive) mode and invoke the "Additional Management Agent" installation for the agent home. The agent home is typically created at the same level as the Enterprise Manager home. However, it may be nested within the Enterprise Manager home in cases where the parent directory of the Enterprise Manager home cannot be written onto.


1.2.2 Installation of the OMS and Agent on machines with multiple network interfaces and/or virtual hosts
Machines with multiple network interfaces or virtual hosts bound to single or multiple network adapters are accessible by more than one IP address. The Enterprise Manager installation for both the Management Service and the Management Agent will always select the primary machine alias.

1.2.2.1 Changing Management Service IP Address
Changing Management Service IP address after initial installation is not currently supported without deinstalling and reinstalling the Management Service.


1.2.2.2 Changing the Management Agent IP address after initial installation
If the existing host name remains unchanged but resolves to a new IP address, then no changes are required.

If the Agent host is assigned a new machine name (a new primary alias that resolves to the current IP address, or a new IP address), then the following steps will rename the Agent on the managed node.

a) Create a backup of the existing targets.xml
b) Edit the existing targets.xml, replacing the old host name with the new host name
c) Alter the Management Agent configuration file:

Edit the EMD_URL property in
$ORACLE_HOME/sysman/config/emd.properties to reflect the new host name.

d) Shut down and restart the Management Agent
e) Verify that the new host name appears in the Enterprise Manager console along with its associated targets.



Note:
i)The targets associated with the old host name will continue to be displayed in the Enterprise Manager console. If the historical data are not required, it is recommended that the targets associated with the old host name be removed using the Enterprise Manager console UI.
ii) In a RAC environment the emd.properties file would be under $ORACLE_HOME//sysman/config directory.

1.2.3 Retrying Secure Agent action
During the configuration portion of the agent install, the Secure Agent action may fail if the OMS is down or busy processing other requests.

This operation can be retried multiple times from the installer by retrying the "Secure Agent action" until the agent is secured successfully. Another alternative is to complete the installation with this failure and use:


emctl secure agent

at the command line to secure the agent.

1.2.4 Securing OMS via EMCTL Changes Upload Port
When using non-default ports, the command

emctl secure oms

does not retain the console upload ports specified at install time. The ports are always defaulted to 4889 (unsecure) and 4888 (secure). This is bug 3346036

To workaround this problem, set:

EM_UPLOAD_PORT to oracle.sysman.emSDK.svlt.ConsoleServerPort in $ORACLE_HOME/sysman/config/emoms.properties.

EM_UPLOAD_HTTPS_PORT in $ORACLE_HOME/sysman/config/emoms.properties should be set to the port number being used for secure upload.

After setting these variables, rerun emctl secure oms.


Note that in a RAC environment the emoms.properties file would be under $ORACLE_HOME//sysman/config directory.

1.2.5 De-installation
If you de-install the Enterprise manager 10g ORACLE_HOME using Oracle universal installer (OUI), it de-registers the ORACLE_HOME from the central inventory and the oratab file. It may, however, leave some files within the ORACLE_HOME. If the ORACLE_HOME has been successfully removed (it can be verified from OUI by clicking on 'Installed products' button) one can manually delete the files using the appropriate command on the Operating System.

The proper sequence of de-installation is:
a) Shutdown the repository database (if it is a part of the de-installation)
b) Shutdown the database listener
c) Shutdown Apache using "opmnctl stopall"
d) Shutdown Application Server Console using "emctl stop em"
e) Shutdown agent in the chained agent home using "emctl stop agent".
f) Run the Oracle Universal Installer and select the ORACLE_HOME to de-install. It would then be removed from the Central Inventory.
g) Remove stray files from the ORACLE_HOME by appropriate operating system command. .


1.2.6 Problems With Agent Shutdown Operation on NT 4.0

If you are running the agent on a Windows NT 4.0 host, you may find that the agent does not shutdown or recover gracefully from a timeout. This may lead to an inconsistency between the status reported by ‘emctl’ and the status reported by Windows service control manager. To workaround this issue the following internal command “emctl istop agent” can be issued to shutdown the agent. You may then bring up the agent using your Windows service control manager (Bug 3320183)

1.2.7 Verify NLS settings are configured properly
If you launch opmnctl or emctl in non English environment, make sure the OS default locale and the NLS_LANG settings are configured properly. (Bug 3128644)

1.2.7.1 OS default locale

a) Make sure LC_ALL or LANG environment variables are set with the appropriate value. To check the current setting, issue locale command:
% locale for the specific value in each OS, refer to the platform specific documents.



1.2.7.2 Make sure NLS_LANG environment variable is set with the appropriate and compatible value with the OS default locale setting and the repository database character set. For the specific value for the language or the character set, refer to the Globalization Support Guide of the Oracle product you are using.
If the platform is Microsoft Windows based Operating System, the default NLS_LANG setting in the registry should be used as it is. You usually do not have to change the value.



1.2.8 National Language Support: Performance Analysis Findings Return As Garbled Text
If the NLS settings of the Enterprise Manager repository database are different from the NLS settings of a managed database target, the Performance Analysis findings may return as garbled text, e.g. question marks. The workaround is to click on the finding text, which will display the finding in the language of the database target (Bug 3351589)



1.2.9 Changing the agent port for a secured agent
You can change the listen port of an agent by editing the EMD_URL property in the $OH/sysman/config/emd.properties file. If you do this for an agent that has already been secured, you will need to resecure the agent (via emctl secure agent). If you do not resecure the agent, agent uploads to the OMS will fail - data will back up at the agent, and the OMS will not be able to contact the agent to retrieve real time metric values (Bug 2814831). In a RAC environment the emd.properties file would be under $ORACLE_HOME//sysman/config directory.





1.2.10 OMS Fails to Secure

If all registration passwords are removed, the OMS will not secure any new agents. You will get the following error:



The OMS is not set up for Enterprise Manager Security.



To workaround this issue, login to Enterprise Manager as a Super Administrator and add a new registration password from the Setup -> Registration Passwords page. Once this is finished, resecure the agent using the emctl secure agent command. (Bug 3356147)



1.2.11 Use of a RAC database as 10g Grid Repository
The database provided in the installation of the 10g Grid Management Server is a single instance 9.0.1.5 database. In order to have a real application cluster instance, the installation of the 10g Grid Management Server must be done using the using an existing database option.

In the course of the installation, the installer will request a SID to be specified. Chose one instance of the Oracle RAC and specify its SID. When prompted for the location of the 10g Grid management tablespaces, insure that the location is one mutually accessible by all members of the RAC.

Upon completion of the installation, edit the $ORACLE_HOME/sysman/config/emoms.properties file. Alter the property of the name oracle.sysman.eml.mntr.emdRepConnectDescriptor to represent the SERVICE_NAME of the RAC instead of the SID that will be found there.

Restart the OMS.

Subsequent additions of other Management Servers that wish to use the RAC database should perform the installation choice of an 'Additional Management Service'. When prompted for the connection information, they too should specify the SID of one of the database instances comprising the RAC. After the installation has completed, the emoms.properties file in that newly added 10g Grid Management Server's home should be altered in the same manner as in the initial installation. (Bug 3259014)



1.2.12 Oracle Universal Installer Does Not Start Up on Windows 2000

Oracle Universal Installer may not start up properly (appear and then disappear) on Windows 2000 with Service pack 4. This is
due to an underlying JRE bug. You need to run 'installwin32setup.exe -J-Dsun.java2d.noddraw=true' to workaround the issue.



1.2.13 Bug 3417663: This problem occurs when an Oracle Database 10g with Oracle Universal Installer 10.1.0.2.0 or earlier is cloned to a target location on the same host as the source home. Deinstalling the cloned home using OUI will remove some files from the source home and may cause it to be in a non-functional state. This applies to cloning performed by both Oracle Grid Control and Oracle DB Control. The bug has been fixed in Oracle Universal Installer Version 10.1.0.3.0 and will not affect products certified and installed with that version.



1.2.14 Bug 3609193: In non English language environment except Japanese (Brazilian Portuguese, French, German, Italian, Korean, Simplified Chinese, and Spanish), Grid Control online help prints out-of-dated translated contents of "Oracle9iAS Container for Java".(bug#3609193)


In order to work around this issue, the user replaces the out-of-dated translated version of oc_4j_help_.jar files with the English one (oc_4j_help.jar). Specific steps would include:



For UNIX:

As user oracle or the appropriate user id:

% cd $ORACLE_HOME/j2ee/OC4J_EM/applications/em/em/online_help/oc_4j

Perform the following copy command for each .

cp -p oc_4j_help.jar oc_4j_help_.jar

The following b-shell script will do this automatically:

for file in oc_4j_help_*.jar; do

cp -p oc_4j_help.jar $file

done

For Windows:

Perform the same copy operations with Windows Explorer.

1.2.15 File Size Limit on FAT File System (Windows)
On Windows, if the repository database is located on a FAT file system, there is an OS-mandated file limit of 4GB. Even if datafiles are set to auto-extend, they will not be able to exceed 4GB because of the OS limitation. The workaround is to add a new datafile once the 4GB limit is reached. This is not an issue when the repository database is located on NTFS file systems. (Bug 3748521)
1.2.16 Cannot Disable Management Packs for RAC Database and ASM Targets
Disabling access to individual packs using the Management Pack Access interface does not work for cluster database and ASM targets. (Bug 3751881) Note that some cluster database and ASM pages may get blocked because they have the same links as the single-instance equivalent pages. However, pages that are cluster database or ASM specific do not get blocked.

6.1.0 Data Guard

6.1.1 Metric Collection Errors in Standby Databases
After switching a primary database to a standby database you may notice a few metric collection errors for the new standby database. These errors can be ignored. The workaround to clear the metric collection errors is to briefly open the database in read-only mode. (Bug 3312518)

6.1.2 Data Guard: Upgrading Protection Mode Causes Exception With a RAC Database
When upgrading the protection mode in a Data Guard configuration that has a RAC database, connecting to the RAC database at the end of a successful protection mode upgrade may throw an exception. The workaround is to log out of the database and log back in again from Enterprise Manager. (Bug 3345796)

6.1.3 Using Primary Database as Recovery Area for Locally-Archived Logs
If your primary database is using a recovery area for locally-archived logs, ensure that the log_archive_dest_10 parameter is set to the following before creating a physical or logical standby database:

log_archive_dest_10='location=use_db_recovery_file_dest','valid_for=(ONLINE_LOGFILE, ALL_ROLES)'

If this parameter is not set on a primary database that uses a recovery area before switching over to a logical standby database, online logfile archival will fail with an ORA-16104 after the database is activated as a logical standby. If you neglect to set this parameter prior to switchover and see this problem, it can be fixed by setting the above parameter on the logical standby database. (Bug 3349731)

6.1.4 Creating A Standby Database For A Cluster Database (RAC) Primary Database
When creating standby databases for cluster database (RAC) primary databases in Enterprise Manager you must follow all the configuration steps described in Section 2.2 ("Setting Up the Broker Configuration Files") of the Data Guard Broker book in the Oracle Database 10g documentation.

6.1.5 Standby Database Creation Error on Windows
On the Windows platform only, if the name (including the path) of a standby datafile or logfile contains the characters "p" an error will result.
If this occurs in the directory component of a name, either rename the directory and change the standby file names accordingly, or choose a completely different directory to place the files into, and rename the files accordingly using the Customize button on the File Locations page of the Add Standby wizard.
If the "p" occurs in the file name component of the name, rather than the directory component, change the filename using the Customize button on the File Locations page of the Add Standby wizard. (Bug 3655231)

6.2 Reorganize Objects

6.3.0 Net Services Administration
For the 'Directory Naming' feature to work, a valid ldap.ora file must exist in the 'Configuration File Location' selected by the user in the 'Net Services Administration' page. The ldap.ora file should be created using NetCA or OidCA. If the ldap.ora file location is not OH etworkadmin or OHldapadmin, then you must set the TNS_ADMIN / LDAP_ADMIN environment variable to that location before starting Database Control.

6.4.0 Shutting Down the Database
Shutting down a database in normal mode does not work in Enterprise Manager. However, a database can be shut down in transactional, immediate and abort modes with Enterprise Manager. Use SQL*Plus to shut down a database in normal mode. (Bug 3239095)

6.5.0 Running SQL Access Advisor With Materialized View Recommendation May Cause Library Cache Deadlock
A deadlock on the library cache may happen when a select statement is evaluated for rewrite at the same time as a create materialized view statement requests exclusive locks on its base tables. This could happen when a SQL Access Advisor is running to generate materialized view recommendations while another user issues a select statement at the same time that references the same base tables. The workaround is to stop the SQL Access Advisor job and the deadlock will be released. (RDBMS bug 3230878, 2018081, 2124800)

6.6.0 10g RAC Database Recovery in Archivelog Mode
When a 10g cluster database is in archivelog mode, in order to perform a restore and recovery of the entire database, the user should only leave one RAC instance up and shut down all other RAC instances. Affected areas include whole database complete/point-in-time/flashback recovery. (Bug 3334212)

6.7.0 Default Database Credentials May Not Be Used for Cluster Databases
Default database credentials will not be picked up for cluster databases unless at least one cluster database was already discovered at the time when the default credentials were set. The workaround for this problem is to delete and reset the default database credentials. (Bug 3312344)

6.8.0 Launch iSQL*Plus Requires Configuration
For Grid Control, the iSQL*Plus server is not shipped with the OMS (Oracle Management Services). Therefore iSQL*Plus needs to be manually configured to point to any running Oracle Database 10g iSQL *Plus server. All the target databases discovered in this Grid Control application will then use this iSQL*Plus server for their queries.

To configure iSQL*Plus, two entries in the $ORACLE_HOME/sysman/config/emoms.properties file on the OMS (Oracle Management Server) machine needs to be populated by replacing the following placeholders: replace %ISQLPLUS_PROTOCOL%, %ISQLPLUS_HOST% and %ISQLPLUS_PORT% with the protocol, the host and the port of the iSQL*Plus server you want to use.

For example:
oracle.sysman.db.isqlplusUrl=
oracle.sysman.db.isqlplusWebDBAUrl=

For RAC applications, the emoms.properties file for all nodes of the cluster must also have these two entries configured. After configuring the entries, the OMS needs to be restarted to pick up the change.

6.9.0 Editing Objects
Enterprise Manager only supports having one browser window open for editing an object. For example, Enterprise Manager only supports editing one tablespace at a time. Note, if a window is read only, you may have multiple browser windows open.

6.10.0 Target Names For Oracle Suggested Backup Strategy
When Oracle's Suggested Backup Strategy is to be used for offline backups, the target name should be less than 52 characters in length. (Bug 3347338)

6.11.0 Viewing of SQL Execution Plan in Korean
There is a known bug where viewing an execution plan of a Period SQL causes an internal server error. This is a bug that is unique to Korean and does not reproduce in Japanese or Chinese. The only workaround currently available is to run the product in a non-Korean language when you need to view this page. (Bug 3380531)

6.12.0 Garbled Characters Shown in "PGA Memory Usage Details" Page
The "PGA Memory Usage Details" page under Administration -> Instance:Memory Parameters -> PGA will show garbled characters when the product is run in a multi-byte (Asian) language environment. The only workaround currently available is to run the product in a single-byte Western European language when you need to view this page. (Bug 3272773)

6.13.0 Database Performance Page Shows Grey Area Instead of Graphs in Internet Explorer
Sometimes in Internet Explorer the SVG graphs on the Database Performance page don't render. Instead the page displays a large grey area with no graphs at all.
To fix this problem change a setting in your Internet Explorer browser as follows:
Tools -> Internet Options -> Advanced
Scroll down to Security and uncheck "Do Not Save Encrypted Pages to Disk".
This problem does not apply when SVG has not been enabled, i.e. you are viewing the graphs in GIF mode.