F
Troubleshooting

This chapter describes possible troubleshooting issues.

• Reporting Problems to Oracle Support Services

• Troubleshooting the Enterprise Manager Configuration Assistant

• Changing the Permissions on the omsconfig.properties File

• Troubleshooting the Management Server

• Troubleshooting the Paging Server

• Troubleshooting the Web Browser

• Changing the Repository User Password

• Resetting the Password

• Setting the Format of Dates

• Troubleshooting for Reporting

Reporting Problems to Oracle Support Services

When you use Oracle Enterprise Manager and encounter problems, you can turn to many sources for help.

Before you contact Oracle Support Services, please take the time to consult your manuals and the Oracle Enterprise Manager Readme. A list of Oracle Enterprise Manager manuals are listed in the Preface under Documentation Set on page xvi.

Manuals

Manuals of particular interest are listed below:

• The Oracle Enterprise Manager Readme Release 9i provides important notes on updates to the software and other late-breaking news, as well as any differences between the product's behavior and how it is documented.

• The Oracle Intelligent Agent Users Guide describes how to administer the Oracle Intelligent Agent and provides troubleshooting information.

• The Oracle Enterprise Manager Messages Manual Release 9i contains probable causes and recommended actions for Oracle Enterprise Manager errors.

MetaLink

In addition to the manuals and online help, Oracle offers OracleMetaLink, an electronic support service available to Oracle customers with active support service contracts, 24 hours a day, seven days a week. Customers can register on-line through http://www.oracle.com/support.

MetaLink includes the following features:

• My Headlines

  Uses push technology to provide you with proactive notifications. My Headlines gives you the ability to customize information in your user profile such that you get only the specific information you desire when you access the My Headlines section of MetaLink. You can also choose to have this information sent to you via email. The information delivered to you falls into the following categories and can be personalized by product and platform: News & Notes, Knowledge Base, Patches, Bugs, TAR Updates, Product Lifecycle, and Forum Updates.

• User Administration

  Gives companies the ability to manage access of MetaLink users at the support identifier/CSI level. In situations where you want to restrict the access to certain areas of MetaLink to specific users at your site, this feature enables that control. For example, only internal help desk employees at your site may be allowed to create TARs in MetaLink.

• User Profile

  You can update your contact information, add and remove support identifiers, view other users registered under the same support identifier, customize MetaLink, change your password, and view your license information. You will now have a choice of languages in which to view the MetaLink interface: English, German, or French.

• Technical Libraries

  Organized by product and platform, these libraries enable you to access information that support analysts have determined will aid you in your installation and use of Oracle products (documentation, white papers, problem/solution articles, and more).

• Forums

  You can post questions to technical analysts and receive responses within two business days. Users also share information and ideas with other Oracle users.

• File Access

  Previously referred to as Download, this section provides you the ability to download patches and patch sets directly from within MetaLink. View the Readme files to find out which bugs have been fixed in the patch sets.

• Knowledge Base Search

  Allows you to do a full-text search against the internal repositories within Oracle Support Services. Advanced searching is also available.

• Bug Search

  Provides you with query access to published header and abstract information in the Oracle Bug Database.

• Product Lifecycle

  Product availability, product alerts, certifications, and de-support information online

• Enter TARs Online

  Submit, update, review, and close your TARs online (not available in some countries)

• Skills-Based Routing

  TARs submitted electronically are automatically matched to the right technical resource within Oracle Support Services (not available in some countries)

• TAR Access and Reporting

  Track issues by generating and viewing TAR reports

• Context-Sensitive Help

  Learn the features of MetaLink and see "how to" instructions

• Feedback

  Enter feedback about MetaLink

Oracle Support Services

If the manuals and MetaLink do not answer your questions, contact Oracle Support Services and provide them with the following information:

1. What is the problem?

2. What were you doing when the problem occurred?
   • In which product or component is the problem occurring?

   • What operations were you performing? Is the problem reproducible? What are the steps you took to see the problem?

3. What is your environment?
   • What is your operating system and version?

   • What version of Oracle Enterprise Manager are you using and where is it installed?

   • What version of the Intelligent Agent are you using and where is it installed?

   • What version of the database are you using and where is it installed?

   • Where is the Management Server installed?

   • Provide schema, data, scripts, or any other relevant information about your environment. If possible, provide log files to assist in problem reproduction.

4. What error messages and numbers did you see?

5. Turn on tracing (when available) and provide tracing information.

6. Look at log files (when available) and provide log information.

Troubleshooting the Enterprise Manager Configuration Assistant

Enterprise Manager Configuration Assistant Errors

This section describes the Enterprise Manager Configuration Assistant error messages and their probable causes, and provides the actions recommended to correct them.

The Database User You Chose Does Not Have the Necessary DBA Privileges

When you login as a DBA user on a selected database, the Configuration Assistant checks whether the user has the necessary privileges. If the user does not have the necessary DBA privileges, a message appears: "The database user you chose does not have the necessary DBA privileges. Logon to the database as a user with DBA privileges." Click OK to dismiss the message box. You must enter the proper credentials in order to continue. Enter the credentials and try again.

Select Database for Repository Login is Unsuccessful

If you have entered an invalid username, password, or service, an error message indicating the failure appears. For example: "Connection failed ORA-01017: Invalid username/password; logon denied" message appears. Click OK to dismiss the message box. Enter the data and try again.

The User Already Exists

The user already exists, and already contains an incomplete Enterprise Manager Release 9 repository. A repository create, drop, or upgrade operation may be in progress, or a previous operation may have failed. Continuing the current operation can replace incomplete components and create missing components in the repository.

What would you like to do?

• Select another user.

• Continue and use the selected repository.

If a repository operation is already actively in progress elsewhere, do not continue. Attempting to perform simultaneous operations on the same repository may cause repository corruption.

The user "<username>" already contains a complete and up-to-date Enterprise Manager Release 9 repository

The user "<username>" already contains a complete and up-to-date Enterprise Manager Release 9 repository. If you wish to overwrite the existing repository, first use the Drop option.

The User Already Exists and Contains a V1 Repository

If the Enterprise Manager Configuration Assistant detects that the chosen repository name is the name of an already existing user/schema in the database and that it contains an Oracle Enterprise Manager Release 1.x repository, a message appears: "The user already exists and contains a V1 repository. A 9i repository may not coexist with a V1 repository in the same schema. Please choose another user name."

The User Already Exists in this Database

If the Enterprise Manager Configuration Assistant detects that the chosen repository name is the name of an already existing user/schema in the database, and that it contains neither an Oracle Enterprise Manager Release 2.x nor Release 1.x repository, a message appears: "The user already exists in this database. Do you wish to create the repository within this user's schema anyway?"

If you choose no, you may select a different user name.

If you choose yes, the "Create Repository Summary" page appears.

The Management Server on this Machine is Currently Managing a Repository Owned by user <user_name> on service <service_name>

During create repository, if the Configuration Assistant detects that a managed repository is already specified in the omsconfig.properties file, and you are creating a repository that is different from the managed repository, a message appears: "The Management Server on this machine is currently managing a repository owned by user <user_name> on service <service_name>. Would you like to change it to now manage the repository owned by user <user_name> on service <service_name>?"

If you choose yes, the configuration will be updated. The Management Server must be stopped and restarted in order for the changes to the configuration file to take effect. If you choose no, the configuration will not be updated. The "Create Repository Summary" page and the steps in the Configuration Assistant Progress Window will reflect your choices.

You have chosen the user's default or temporary tablespace to be SYSTEM.

Note that the Configuration Assistant, when it creates the user for an Oracle Enterprise Manager repository, asks you for the default and temporary tablespaces to use. If you choose SYSTEM for either of these, Configuration Assistant puts up the following warning: "You have chosen the user's default or temporary tablespace to be SYSTEM. We recommend the SYSTEM tablespace be used only for data dictionary tables and the SYSTEM rollback segment. Are you sure?" Pick another tablespace.

The Default Tablespace for the Repository Does Not Contain Enough Free Space

If the Enterprise Manager Configuration Assistant detects that the default tablespace for the repository does not contain enough free space, the following message appears: "The default tablespace for the repository does not contain enough free space."

Refer to Repository Database Default Tablespace Does Not Contain Enough Free Space on page F-8 for information for possible solutions.

Repository Database Default Tablespace Does Not Contain Enough Free Space

The Configuration Assistant checks that the selected default tablespace for the repository has the appropriate attributes/characteristics, but if it does not contain enough free space, the following message appears: "The default tablespace for the repository does not contain enough free space."

Use the OEM_REPOSITORY tablespace if it exists. It is the default tablespace for Enterprise Manager.

If you are creating a repository in a new user, the Configuration Assistant's Select Repository User Tablespaces page strongly encourages you to create an OEM_REPOSITORY tablespace. Using the Enterprise Configuration Assistant to create the OEM_REPOSITORY tablespace ensures that the tablespace has appropriate attributes/characteristics.

However, if you prefer, you can create another tablespace, or use an existing tablespace. If you decide to use an existing tablespace, you may have to increase its size.

Creating an OEM_REPOSITORY Tablespace if One Does Not Exist

If the OEM_REPOSITORY tablespace has not been created for you, the "Create a new OEM_REPOSITORY tablespace (recommended)" option is available on the "Select Repository User Tablespaces" page of the Enterprise Manager Configuration Assistant.

Select this option if you want to create the OEM_REPOSITORY tablespace. Using the Enterprise Manager Configuration Assistant to create the OEM_REPOSITORY tablespace gives that tablespace appropriate attributes/characteristics. Then use it as the user's default tablespace.

Creating Another Tablespace

Using the Configuration Assistant is the preferred method for creating a tablespace since it creates the tablespace with the proper attributes in any of the supported databases. The attributes of the default tablespace depend on the database version.

To use the Console's Storage Management functionality to create a new tablespace, follow the procedure described in this section:

1. Start the standalone Console.
   • On Windows NT:

     You can start the standalone Console from the Windows Start Menu.

   • On UNIX:

     You can start the standalone Console from the command line using the command:

     oemapp console
     
     

   When the login dialog appears, choose "Launch standalone" and press OK. For more information on using the Console in standalone mode, refer to Chapter 2, "Standalone".

2. Expand the Database folder.

3. Double-click the database node in the navigator tree and connect to the database as a user with the DBA privilege.

4. Select Create from the Object menu. The Create window appears.

5. Expand the database node in the Create window and select Tablespace. Then click the Create button. The Create Tablespace property sheet appears.

6. In the Create Tablespace Property Sheet's General page,
   1. Enter the name of the new tablespace.

   2. Specify that the tablespace will be used to hold permanent database objects.

7. In the Datafile section, enter the size of the new datafile. The File Name and File Directory columns should already contain default entries.

8. Right-click the "+" sign which appears next to the name of the datafile and choose Edit. The Create Datafile property sheet appears.

9. In the Create Datafile's Storage page, select the "Automatically extend datafile when full (AUTOEXTEND)" box so that the datafile will automatically increase in size when more space is needed in the database.

10. Click the OK button in the Create Datafile property sheet.

11. In the Create Tablespace Property Sheet's Storage page, choose a method of space management. You cannot alter the method at a later time.

12. Click the Create button in the Create Tablespace Property Sheet.

Increasing the Size of an Existing Tablespace

Using the Configuration Assistant is the preferred method for creating a tablespace since it creates the tablespace with the proper attributes in any of the supported databases. The attributes of the default tablespace depend on the database version.

To use the Console's Storage Management functionality to increase the size of an existing tablespace, follow the procedure described in this section:

1. Start the standalone Console.
   • On Windows NT:

     You can start the standalone Console from the Windows Start Menu.

   • On UNIX:

     You can start the standalone Console from the command line using the command:

     oemapp console
     
     

   When the login dialog appears, choose "Launch standalone" and press OK. For more information on using the Console in standalone mode, refer to Chapter 2, "Standalone".

2. Expand the Database folder.

3. Double-click the database node in the navigator tree and connect to the database as a user with the DBA privilege.

4. Expand the Storage Management node.

5. Double-click the datafile you want to increase from the Datafiles folder. The General page of the Datafile property sheet appears, allowing you to edit the file size of the datafile.

6. Click the Apply button in the General page.

7. Click on the Storage tab. The Storage page of the Datafile property sheet appears.

8. Check the "Automatically extend datafile when full (AUTOEXTEND)" box and click the Apply button.

Database Parameters Not Large Enough for Repository Operation

An Oracle Management Server will open a number of repository database sessions while processing work on behalf of clients and managed nodes.

The number of sessions required by a single Management Server generally ranges from 3 to 5, depending on the load placed on the Management Server. More repository database sessions may be required under the following circumstances:

• many Consoles are actively submitting jobs/registering events

• multiple Management Servers are concurrently using the same repository

• many Intelligent Agents are sending notifications back to the Management Servers

If other applications are accessing the same database used for the Enterprise Manager Repository the session load will increase on the database.

If your processes setting is too low for Oracle Enterprise Manager, you will receive an error message similar to the following in the oms.log file located in the Oracle_OEM_Home/sysman/log directory.

can't open a session

For large workloads, or for cases where multiple applications are accessing the database where the repository resides, you can increase the processes parameter in the database init.ora to accommodate the workload.

To use Instance Management functionality to change your database parameters, follow the procedure described in this section:

1. Start the standalone Console.
   • On Windows NT:

     You can start the standalone Console from the Windows Start Menu.

   • On UNIX:

     You can start the standalone Console from the command line using the command:

     oemapp console
     
     

   When the login dialog appears, choose "Launch standalone" and press OK. For more information on using the Console in standalone mode, refer to Chapter 2, "Standalone".

2. Expand the Database folder.

3. Double-click the database node in the navigator tree and connect to the database as a user with the DBA privilege.

4. Expand the Instance Management node.

5. Select the Configuration node.

6. Click the All Initialization Parameters button in the Configuration Property Sheet's General page.

7. Change the value of the parameter.

8. Click Save As button on the All Initialization Parameters page. The Save Initialization Parameters dialog appears.

9. Enter the complete directory path and a file name or use the Browse button to find a location on your local operating system to place the file and enter the file name.

10. Press OK to save the file.

Changing the Permissions on the omsconfig.properties File

If you have chosen to store your repository credentials in the omsconfig.properties file during repository creation, you may want to change the permissions on the file to restrict who can view it.

If you change the file permissions appropriately, other users cannot view or modify the file.

UNIX:

To change the file permissions, at the command prompt, enter:

$ chmod 600 omsconfig.properties 

This command sets the read and write permissions only for the owner of the file.

Windows NT:

To change the file permissions, perform the following steps.

1. From the Start menu->Programs, select the Windows NT Explorer item.

2. From Oracle_Home/sysman/config directory, select the omsconfig.properties file.

3. Right-click the selected file, and then choose the Properties item in the resulting pop-up menu.

4. Select the Security tab from the Properties dialog. Note: This step only applies to NTFS file systems.

5. Press the Permissions push-button on the Security page to display the File Permissions dialog. The default is "Everyone" has Full Control (All). The type of Access is Full Control.

6. Click the Remove button to remove this entry.

7. Click the Add button to display the Add Users and Groups window.

8. Click the Show Users button to view all users.

9. Select the user who starts the Management Server regularly and uses the Enterprise Manager Configuration Assistant for the "type of access" field and select "select full control" from the drop down list.

10. Click the OK button to dismiss the Add Users and Groups dialog.

11. Click the OK button to dismiss the File Permissions dialog.

12. Click the OK button to dismiss the file Properties dialog.

You can provide access to multiple usernames.

Troubleshooting the Management Server

This section contains the following topics:

• Management Server May Not Run Correctly from a Non-Default Oracle Home

• Management Server Does Not Start

• Error Messages When Starting the Management Server

• Changing Your Management Server for Client Access

Management Server May Not Run Correctly from a Non-Default Oracle Home

On Unix, if the ORACLE_HOME environment variable is not set to the Oracle home where the management server is running, the management server will not start correctly. It will try to find its class files in the default Oracle home instead of the correct Oracle home.

csh

To set the environment variable:

setenv ORACLE_HOME '/usr/local/oracle'

ksh/sh

To set the environment variable:

ORACLE_HOME = '/usr/local/oracle'
export ORACLE_HOME

On UNIX systems, the Oracle environment can also be set by calling coraenv (for the CSH) or oraenv (for any other shell). This shell script sets the oracle environment for a given identifier. This identifier can be a specific database or it can point to an ORACLE_HOME which contains the Management Server software. These scripts can be customized to include specific machine or server based settings.

Refer to the specific operating system's Oracle Administration documentation for more information about the coraenv and oraenv scripts.

Management Server Does Not Start

For information to troubleshooting the Management Server if it does not start, refer to the following resources:

• the oms.log file

• the oms.nohup file

• the Windows NT Event Log (for Windows NT)

• oemctl batch file

oms.log File

The $ORACLE_HOME\sysman\log directory contains the output of traces that are redirected to disk if logging is enabled. This directory contains the oms.log and oms.nohup files.

The Management Server places all its trace messages in oms.log file. The oms.log file contains messages generated when the Management Server is starting and running.

The Management Server places all its trace messages in Management Server log files (oms.log.0, oms.log.1, oms.log.2, and so on). It writes to one log file, and when the log file is full, it writes to the next file, recycling the last two files.

The Management Server's log files have size limits. By default, when the Management Server starts, it can only create log files with a size of 25 MB. The initial log file name is oms.log.0. If the file reaches its 25 MB limit, a separate log file is created. The separate log file name is oms.log.1. If that file reaches its 25 MB limit, the oms.log.0 file is deleted and a new log file, oms.log.2, is created. The last two log files are kept.

oms.nohup File

The oms.nohup file in the $ORACLE_HOME/sysman/log directory contains Management Server error messages which appear before the Management Server starts up and critical messages during its run.

Windows NT Event Log

To access the Windows NT Event Log to view the events logged by the Management Server.

1. From the Start menu->Programs->Administrative Tools (Common), select the Event Viewer item or search for eventvwr.exe.

2. Select Application from the Log menu.

3. When the log screen appears, double-click any event logged by the Oracle<Oracle_Home_Name>ManagementServer service which has red octagonal stop signs next to them. These will be the errors reported by the Management Server, if any.

Events and event numbers which the Management Server can log in the event viewer are listed below:

Event Number	Message	Meaning
101	(<NT OMS service name>) could not be found. It contains the following insertion string(s): <NT OMS service name>.	Problem starting service. Look at log and trace files for more information
105	The service was started.	Informational message
108	The service was stopped	Informational message
110	The service is entering production run mode	Informational message
112	The service has terminated abnormally.	See the oms.log file for more information.
113	Fatal error Process terminated abnormally	See log file for more information.

Errors will only be reported in the Event Viewer if the Management Server is voluntarily shutting down.

oemctl Batch File

To obtain more information for debugging, you can change the JRE startup command in the oemctl script.

• On Windows, change

  SET JRE=jre -nojit -mx32m
  
  

  to

  SET JRE=jre -nojit -mx32m -verbose
  

• On Unix, change

  JRE="jre -native -nojit -mx32m "
  

  to

  JRE="jre -native -nojit -mx32m -verbose "
  
  

Performing this procedure enables you to identify class loading problems caused by environmental or installation problems. When you have collected the data from the batch file, send the information to Oracle Support Services.

Error Messages When Starting the Management Server

If you receive the following error when starting the Management Server, refer to the solutions below:

Could not start the Oracle<ORACLE_HOME_NAME>ManagementServer 
     service on <HOST NAME>.  
Error 0203:  The system could not find the environment 
     option that was entered.

The Management Server has been installed but not configured. You must run the Enterprise Manager Configuration Assistant to create a new repository or to edit an existing repository.

For Windows NT: The Enterprise Manager Configuration Assistant has been run, and you have chosen to not save the repository connection's username and password to a file (in secure Management Server mode). You must select the Oracle<ORACLE_HOME_NAME>ManagementServer service and then enter the username and password in the Control Panel's Startup Parameters' field or you must enter the repository credentials when you are prompted for them in a dialog.

Changing Your Management Server for Client Access

If a Management Server fails in a multi-Management Server environment, it only affects the clients connected to it. Each Management Server is independent of the other Management Servers connected to the repository.

To change your Management Server node to another node where a Management Server is still running, follow the procedure below.

1. In the Oracle Enterprise Manager login, select a node that has a Management Server which is configured with the repository you want to access from the Management Server pull-down list.

   If the node name where the Management Server is running does not appear in the pull-down list, follow the instructions below:

   1. Click the Management Servers button. The Management Servers dialog appears.

   2. Type in the name of the node where the Oracle Management Server is running that is configured with the repository you want to access and click OK.

   3. Select the node where the Oracle Management Server is running from the pull-down list.

2. On each machine which runs Oracle Enterprise Manager through a web browser, return to the emwebsite.html page to change the machine name to point to the node where a management server is running. You cannot simply enter a new Management Server machine name at the Oracle Enterprise Manager Login screen.

Running the Management Server on a Multiple NIC Machine

The default behavior of the Management Server when running on a multi NIC machine is to listen on all the network cards. If you want the Management Server to listen only on a specific network card, you must perform the following steps:

1. Add the following property to $ORACLE_HOME/sysman/config/omsconfig.properties

   MULTI_NIC.ENABLED=false 
   
   

2. Modify the BootHost property in $ORACLE_HOME/sysman/config/omsconfig.properties to have the name of the network card on which the Management Server has to listen.

   Change "BootHost=localhost" to "BootHost=<network card host name>

   e.g. If a multi nic machine has 2 network cards and has names host1 and host2, setting "BootHost=host1" will make the Management Server listen on host1

3. Restart the Management Server.

Troubleshooting the Paging Server

If a page notification fails, the paging server will try to resend the page three more times. The interval of time between these retries is a value that can be altered. By default, the interval of time between retries is 1 minute. You can change this default setting by editing the OMSCONFIG.PROPERTIES file located in the Management Server's ORACLE_HOME\sysman\config directory. You can add the property

OEM.PAGING.RETRYINTERVAL=<integer> 

to the OMSCONFIG.PROPERTIES file and replace <integer> with the number of minutes between retries.

Troubleshooting the Web Browser

Console Hangs

If you start the web browser, log in to the Console, but the Console hangs, and the following is displayed in JInitiator Console:

@org.omg.CORBA.INITIALIZE[completed=MAYBE, reason=java.net.BindException: 
Cannot assign requested address]

You must perform the following steps:

1. Check that the JInitiator uses browser settings for the proxy.
   1. From the Windows Start menu, click Programs-> JInitiator Control Panel. A window appears.

   2. Choose the Proxies tab.

   3. View the contents.

2. Append the domain name to the web server address you type in the browser, for example, @.us.oracle.com

3. Edit the browser settings and add that domain to "no proxy settings for" or edit the browser settings and choose Direct Connection to Internet.

Console Does Not Launch Web Browser

If user.browser is not defined properly in the clientconfig properties file, the netscape browser will not launch from within the Enterprise Manager Console. The default Enterprise Manager browser (IceBrowser) will be launched instead.

Viewing reports from the Console does not work, it may be because Netscape is using a script and not the actual program.

You must perform the following task in order for Unix to know how to launch Netscape.

Set the following property in ClientConfig.properties:

user.browser=/usr/local/packages/netscape/netscape 

The user.browser should be set to the actual name of the browser, not a script.

/usr/local/bin/netscape is a script and not an executable.

user.browser should be pointed to an executable and not to a shell script.

Changing the Repository User Password

You can change the password on the repository using ALTER USER and then use the Configuration Assistant to edit the configuration parameters.

1. Execute the ALTER USER command once for the database user.

   ALTER USER <repository username>
              IDENTIFIED BY <new password>;
   
   

2. Run the Enterprise Configuration Assistant to edit the Management Server configuration once on each host that is running a Management Server that is using that repository. Refer to Configuring a Local Management Server To Use An Existing Repository on page 3-25.

Resetting the Password

If you forget your SYSMAN password and need to reset it to oem_temp, follow the instructions below:

You must first be connected to the Management Server repository (via SQL*Plus) before using the reset_sysman() procedure.

1. Start SQL*Plus from the command line by typing:

   sqlplus
   

2. When you are prompted for the connection information, type:

   <emrepository>/<emrepository-pwd>@<em-repository> 
   

   to connect to the database.

   For example:

   mynode/mypassword@mynode.world
   
   

   since the default repository name is the hostname.

3. Then type:

   execute smp_maintenance.reset_sysman(); 
   

Setting the Format of Dates

To set up how the order of the date elements are to be displayed in the Oracle Enterprise Manager Console, you must set the following environment variables:

• NLS_DATE_FORMAT for the month, date, and year

  mm-dd-yyyy
  
  

• NLS_TIMESTAMP_FORMAT for the date and time

  mm-dd-yyyy hh:mi pm
  

Windows Platforms

To set the environment variable:

set NLS_DATE_FORMAT = mm-dd-yyyy
set NLS_TIMESTAMP_FORMAT = mm-dd-yyyy hh:mi pm

UNIX

To set the environment variable:

setenv NLS_DATE_FORMAT mm-dd-yyyy
setenv NLS_TIMESTAMP_FORMAT mm-dd-yyyy hh:mi pm

Troubleshooting for Reporting

Webserver Will Be Deconfigured Error

If you access the Enterprise Manager Web site, and you encounter the following error:

The management server <hostname> is using a different webserver <hostname> for 
Enterprise Manager reporting services. This webserver <hostname> will be 
deconfigured and will no longer support Enterprise Manager reporting. To access 
Enterprise Manager Reports in the future, please use the webserver <hostname>

You must perform the following step.

Edit the httpd.conf file located in the $ORACLE_HOME\Apache\apache\ directory by setting the ServerName property to the hostname of the machine running the Oracle HTTP Server for the Enterprise Manager Reporting Web Site.

The ServerName property in the httpd.conf must be the same name as the Oracle Management Server Host in the reporting properties.

Blank Page or Internal Server Error

If you access Enterprise Manager reports from a web browser and see a blank page or the following error:

Internal Server Error: The server encountered an internal error or 
misconfiguration and was unable to complete your request. Please contact the 
server administrator, you@your.address and inform them of the time the error 
occurred, and anything you might have done that may have caused the error. More 
information about this error may be available in the server error log

You must review the Oracle HTTP Server log file for the following exception:

Xlib: Client is not authorized to connect to Server 
java.lang.NoClassDefFoundError: sun/awt/motif/MToolkit. 

The Oracle HTTP Server log file is located in the $ORACLE_HOME/Apache/Apache/logs directory.

If this exception occurred, perform the following steps to fix the problem.

1. Execute the xhost +<host> command on the X Window machine where you are accessing reports from a web browser. For example, if your reporting web server is running on host servlet1 and the X Window is running on host xserv1, then execute the following command on xserv1: xhost +servlet1

2. Specify the DISPLAY environment variable with the X Window machine name on the host where the reporting web server is running. For example, if your reporting web server is running on host servlet1 and X Window is running on host xserv1, then execute the following command on servlet1:
   • if the command shell is C Shell: setenv DISPLAY xserv1:0.0

   • if the command is B or K Shell: DISPLAY=xwerv1:0.0; export DISPLAY

3. Verify that the X Window environment has been configured properly. For example, execute the xclock command. If you see the xclock window on your X Server (i.e. reporting web server), your X Window environment has been configured properly.

4. Restart the Oracle HTTP Server using the command apachectl restart.