|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
|
Previous |
Next |
This chapter describes issues with Oracle Enterprise Manager. It includes the following topics:
This section describes general issues and their workarounds for Oracle Enterprise Manager 10g Application Server Control Console. It includes the following topics:
Section 9.1.1, "Setting Globalization Support and Operating System Locale Environment Variables"
Section 9.1.3, "Errors When Configuring Components or Adding or Removing OC4J Instances"
Section 9.1.4, "Problems with the Progress Page When Using a Macintosh Browser"
Section 9.1.5, "Error When Clicking Topology Link from Host Page"
Section 9.1.6, "Error When Using the ADF Business Component Link on the Host Page"
If you launch a command line tool such as emctl in a non-English setup environment to start a process, then ensure that the operating system locale and the NLS_LANG environment variable settings are configured properly and consistently. This is applicable to the emctl command line utility that is available with Oracle Application Server installations as well as with the emctl utility available with Grid Control Console installations.
If these environment variables are not set prior to Oracle Application Server or Grid Control Console installations, then non-ASCII characters will appear incorrectly in Application Server Control Console or Grid Control Console. To prevent this problem from occurring, set these two environment variables prior to installation. If you cannot set the environment variables prior to installation, then set the two environment variables after installation, and restart the Management Agent.
Refer to the following sections for details on how to check and set the values for the environment variables:
Section 9.1.1.3, "Checking the NLS_LANG Environment Variable"
Section 9.1.1.4, "Setting the NLS_LANG Environment Variable"
Ensure that the LC_ALL or LANG environment variables have the correct value. To check the current setting, issue the following command:
$PROMPT> locale
If you are using bash or zsh, then to set the locale environment variable of the operating system, run the export command. For example:
export LANG=zh_CN
In this example, the variable is being set to Simplified Chinese. For the specific value in each operating system, refer to the documentation specific to the operating system.
If you are using csh or tcsh, then issue the setenv command:
setenv LANG zh_CN
Ensure that the NLS_LANG environment variable is set to a compatible value with the operating system locale setting. In addition, if Grid Control is being used to centrally manage Oracle Application Server, then ensure that the Grid Control Management Repository database character is set. For a specific value of the language or the character set, refer to Oracle Application Server Globalization Guide.
If the platform is a Windows-based operating system, then the default NLS_LANG setting in the registry should be used as is. In addition, check if the NLS_LANG setting exists in Oracle_Home/opmn/conf/opmn.xml on UNIX or ORACLE_HOME\opmn\conf\opmn.xml on Windows. For example, the opmn.xml file should have the following content:
<environment>
<variable id="TMP" value="/tmp"/>
<variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/>
</environment>
If the NLS_LANG setting exists, then ensure that the NLS_LANG setting in the opmn.xml file is identical to the NLS_LANG environment variable.
If you are using bash or zsh, then to set the NLS_LANG environment variable, issue the export command. For example:
export NLS_LANG="Simplified Chinese_China.ZHS16GBK"
In this example, the variable is set to Simplified Chinese. For the specific value in each operating system, refer to documentation specific to the operating system.
If you are using csh or tcsh, then issue the setenv command. For example:
setenv NLS_LANG "Simplified Chinese_China.ZHS16GBK"
The log file timestamps shown by the operating system, which are displayed in Log Viewer of Application Server Control Console, are not always correct. The log file may contain recent log messages, but the timestamp available from the operating system is normally older than the last message written to the file.
While installing Oracle Management Agent 10.1.0.2 on a computer, which has one or more instances of Oracle Application Server 10g (10.1.2), you may encounter errors in Application Server Control Console if you modify your component configuration. For example, you may receive errors if you create or remove an OC4J instance or if you configure an Oracle Application Server component after you have installed the application server.
To workaround this problem, install Oracle Management Agent 10.1.0.3 or later patchsets.
When you perform an operation with Application Server Control Console, such as creating a OC4J instance, Enterprise Manager displays a progress page that indicates that the operation is still in progress.
When using the Apple Safari browser on a Macintosh computer, the progress page continues to display even after the operation is complete. As a result, the operation confirmation page is not displayed.
To solve this problem, set the EM_OC4J_OPTS environment variable to the following value and restart Application Server Control:
-Doracle.sysman.emSDK.eml.util.iAS.waitForCompletion=true
|
See Also: Appendix "Managing and Configuring Application Server Control" of Oracle Application Server Administrator's Guide for more information about using theEM_OC4J_OPTS environment variable
|
In the Host page of Application Server Control, when you click the Topology link, the following error occurs:
Could not determine the oracle home for this component
To workaround this error, navigate to the Farm page, and click the Topology link from that page.
In the Host page of Application Server Control, when you click the ADF Business Components target in the Targets section, the following error occurs:
Error: Failed to connect to OC4J null instance now, please click refresh page to try again!
To avoid this error, navigate to the OC4J Administration page, and click the ADF Business Components link in the Related Links section.
After you configure security for Application Server Control, you may find intermittent issues with form data updates in the Logging pages. These issues may occur with Microsoft Internet Explorer browsers after you install the 832894 (MS04-004) security update or the 821814 hotfix. Microsoft Internet Explorer has known issues regarding using a form on a HTTPS Web page. Problem related to these updates have been seen in the Advanced Search feature of the Search Log Repository page.
To workaround this problem, download the Microsoft Q831167.exe package and any other related patch recommended by Microsoft.
|
See Also: http://support.microsoft.com/default.aspx?kbid=831167 for details about the Q831167.exe package
|
If an Oracle Application Server 10g (9.0.4) or 10g Release 2 (10.1.2) target is removed from the Grid Control Console, then the Infrastructure page in Application Server Control Console shows Central Management as Configured.
To reset the Central Management section of the page, delete the following file from centralagents.lst in the application server Oracle home:
In UNIX, $ORACLE_HOME/sysman/emd/centralagents.lst
In Windows, ORACLE_HOME\sysman\emd\centralagents.lst
You can use the Application Server Control Console to change the password for a component schema in the OracleAS Metadata Repository.
However, when you perform this task in the Application Server Control Console, the new password you enter will be saved in clear text format in the following log file:
ORACLE_HOME\sysman\log\em-web-access.log
In addition, if the Application Server Control Console has not been secured, the new schema password will be transmitted unencrypted from the client-side browser to the machine where the Console is running.
|
See Also: "Configuring Security for the Application Server Control Console" in the chapter " Enabling SSL in the Infrastructure" in the Oracle Application Server Administrator's Guide for more information about the benefits of configuring security for the Application Server Control Console |
To avoid these potential security issues, perform the following procedure before changing a schema password in the Application Server Control Console:
Stop the Application Server Control.
You can stop the Application Server Control by stopping the Application Server Control service in the Services control panel.
|
See Also: The "Starting and Stopping" chapter of the Oracle Application Server Administrator's Guide |
Secure the Application Server Control by entering the following command:
|
See Also: "Configuring Security for Enterprise Manager Application Server Control Console" in Appendix A of the Oracle Application Server Administrator's Guide |
Use a text editor to open the following configuration file in the application server Oracle home:
ORACLE_HOME\sysman\j2ee\config\emd-web-site.xml
Locate the following entry in the emd-web-site.xml file:
<!-- Access Log, where requests are logged to --> <access-log path="..\..\log\em-web-access.log" />
Modify the access-log path entry so it describes the format of each log entry, as follows:
<!-- Access Log, where requests are logged to -->
<access-log path="..\..\log\em-web-access.log"
format="$ip - [$time] '$path' $status $size"/>
Save and close the emd-web-site.xml file.
Start the Application Server Control.
You can start the Application Server Control by starting the Application Server Control service in the Services control panel.
|
See Also: The "Starting and Stopping" chapter of the Oracle Application Server Administrator's Guide |
When you use Application Server Control Console to monitor an instance of OracleAS Portal that has been configured to use Secure Sockets Layer (SSL), some performance metrics for OracleAS Portal may not display.
To correct this problem you must allow the Application Server Control to recognize the Certificate Authority that was used by the Web Site to support HTTPS. You must add the Certificate of that Certificate Authority to the list of Certificate Authorities recognized by the Application Server Control.To configure Application Server Control to recognize the Certificate Authority:
Obtain the Certificate of the Web Site's Certificate Authority, as follows:
In Microsoft Internet Explorer, connect to the HTTPS URL of the application server you are attempting to monitor.
Double-click the lock icon at the bottom of the browser screen, which indicates that you have connected to a secure Web site.
The browser displays the Certificate dialog box, which describes the Certificate used for this Web site. Other browsers offer a similar mechanism to view the Certificate detail of a Web Site.
Click the Certificate Path tab and select the first entry in the list of certificates.
Click View Certificate to display a second Certificate dialog box.
Click the Details tab on the Certificate window.
Click Copy to File to display the Certificate Manager Export wizard.
In the Certificate Manager Export wizard, select Base64 encoded X.509 (.CER) as the format you want to export and save the certificate to a text file with an easily-identifiable name, such as portal_certificate.cer.
Open the certificate file using your favorite text editor.
The content of the certificate file will look similar to the content shown in Example 15–1.
Update the list of Certificate Authorities, as follows:
Locate the b64InternetCertificate.txt file in the following directory of the Oracle Application Server Oracle home:
ORACLE_HOME\sysman\config\
This file contains a list of Base64 Certificates.
Edit the b64InternetCertificate.txt file and add the contents of the Certificate file you just exported to the end of the file, taking care to include all the Base64 text of the Certificate including the BEGIN and END lines.
Copy the text file that contains the certificate (for example, the file you named portal_certificate.cer earlier in this procedure) to the OracleAS Portal middle tier.
Use the orapki utility to update the monwallet Oracle wallet by using the following command:
ORACLE_HOME/bin/orapki wallet add -wallet ORACLE_HOME/sysman/config/monwallet -trusted_cert -cert certificate_location
When you are prompted for a password, enter the password for the monwallet wallet. The default password is "welcome".
In the example, replace certificate_location with the full path to the text file that contains the certificate you saved earlier in this procedure and that you copied to the OracleAS Portal middle tier. For example:
D:\oracle\portal_certificate.cer
Restart the Application Server Control.
After you restart the Application Server Control, Enterprise Manager detects your addition to the list of Certificate Authorities and you can successfully monitor the OracleAS Portal metrics using the secure Application Server Control Console.
In both non-distributed and distributed OracleAS Cold Failover Cluster (Infrastructure) configurations, you can run the Database Console only from the node where you installed the OracleAS Metadata Repository. For example, if your hardware cluster consists of node A and node B, and you performed the installation from node A, then you can only run the Database Console from node A. The reason for this is that the Database Console uses the physical hostname instead of the virtual hostname.
If node A fails, you will not be able to run Database Console from node B. To manage the OracleAS Metadata Repository database from node B, you have to use other tools, such as SQL*Plus.
This section provides a compatibility matrix that you can use as a quick reference for identifying potential compatibility issues and a comprehensive list of the compatibility problems and solutions you might have to consider.
|
See Also: Section "Using 10(10.1.2) Compatibility Matrix in Oracle Application Server Upgrade and Compatibility Guide for details |
This section describes documentation errata. It includes the following topics:
Section 9.3.1, "Online Help for the Application Server Control All Metrics Page"
Section 9.3.2, "Error in Online Help Topic About Regular Expressions"
Most of the component home pages within Application Server Control include the All Metrics link. When you click this link, Enterprise Manager displays the All Metrics page, which provides a comprehensive list of all the performance metrics you can monitor for the selected component.
In some cases, you can click a metric name on the All Metrics page to display the Metric Details page, and then click Help to get more information about the selected metric.
However, for some metrics, when you click Help, a Topic not found error is displayed. This problem will be addressed in a future version of Oracle Application Server.
In rest of the cases, the online help provided for a particular metric might refer to features available only when you are centrally managing your application server instance with Grid Control Console. For example, the online help might refer to thresholds, alerts, or the display of historical data about a metric. In those cases, you can access these additional monitoring features by installing and configuring Grid Control Console.
|
See Also: http://www.oracle.com/technology/documentation/oem.html for details on Application Server Control All Metrics page
|
