Oracle Applications Manager allows you to run diagnostic utilities from the Diagnostics and Repair tab on the OAM Site Map.
Navigation Path: Site Map > Diagnostics and Repair (tab) > Diagnostics (heading) > Debug Workbench (link)
The Debug Workbench enables you to centrally control and monitor the debugging of Oracle E-Business Suitecomponents. Using the Debug Workbench, you can set up debug rules for system components and view the debug information that has been collected.
The Debug Workbench can be launched from Oracle Applications Manager and from the Standard Request Submission (SRS) form using the button Debug Options... By default, this button is disabled. To enable this button, set the Concurrent: Allow Debugging profile option to Y.
On the main Debug Workbench screen, a table lists summary information (Rule ID, Component Name, and so on) for the debug rules that exist on the system. On this screen, you can:
Filter the table by component type (Concurrent Programs, Forms).
Create debug rules.
Search for past executions of debug rules.
Delete a debug rule.
You create debug rules to collect debug information about specific system components.
To create a new debug rule, use the following procedure:
On the main Debug Workbench screen, click the Create button. This launches a multi-step flow of screens that guide you through the rule-making process.
Choose the component type that you want to debug. Optionally, you can enter a comment to describe the rule.
Choose the component instance.
You must set up at least one debug option. Debug options such as logging level, PL/SQL profiler, SQL trace, and Reports trace are available. For a given rule, you can select any combination of available debug option values.
Specify the context and schedule of the rule. You can set a rule to execute for a specific responsibility or user, and to execute either during a specific span of time or for a certain number of repetitions.
Review your work and click the Finish button to save the new rule.
The new rule will appear on the main Debug Workbench screen.
Main Navigation Path: Site Map > Diagnostics and Repair (subtab) > Diagnostics (heading) > Client System Analyzer Data Collections (link)
In Oracle Applications Manager, you can view the data that has been collected by the Client System Analyzer. For more information about using the Client System Analyzer from the Oracle E-Business Suite, see My Oracle Support Knowledge Document 277904.1.
You can perform the following tasks on the main Client System Analyzer Data Collections page:
Click the refresh icon to update the data displayed in the table.
Filter the table by user name. To do so, select the desired operator (is, contains, starts with, ends with) from the drop-down list, type a search term into the text box, and click Go.
Select one or more rows of data collections and add them to the Support Cart.
Select one or more rows of data collections and delete them.
Sort the table by user name by clicking the Applications User Name column header.
Sort the table by collection date by clicking the Collection Date column header.
Click an icon in the View column to see the details of a particular data collection.
Click the Add to Support Cart button to add the page itself to the Support Cart.
The default set of collected data is organized into categories as follows.
Client Identification Information
OS user name
Host name
Domain
IP address
Network Configuration and Performance Information
Latency
Bandwidth
Subnet
Browser and Java Information
Browser type
JVM vendor
JVM version
Proxy information
Hardware Information
CPU Information
OS Information
OS name
OS vendor
Base version
Update level
OS Components
OS Properties
OS-Registered Software
Oracle Applications Manager provides several wizards:
Concurrent Manager Recovery
Service Infrastructure
Generic Collection Service (GCS) and Forms Monitoring Wizard
CP Signature
Navigation: Site Map - Diagnostics and Repair > Concurrent Manager Recovery (under Troubleshooting Wizards)
Use this feature when the Internal Concurrent Manager fails to start.
Click the Run Wizard button to start the recovery process. You cannot run this process if the Internal Concurrent Manager is currently running.
If you encounter any problems, each wizard screen can be added to the Support Cart.
This screen lists all managers that must be stopped before proceeding with the recovery.
Listed for each manager are:
CP ID - The Concurrent Program ID.
Manager - The manager name.
Node - The node on which the manager is running.
DB Session ID - Drills down to the Database Session Details screen.
Session Status
OS ID
Started At - The time at which the manager was started.
Running Request - Drills down to display the request in the Advanced Search for Requests page.
You may want to wait for any requests that are running to complete before you execute the shutdown. Drill down on the Running Request to view it.
Click Shutdown to shut down all the listed managers, and then click the Refresh icon to verify that they were shut down. If a manager fails to shut down from this page, you can drill down to the Database Session Details page and use the Terminate button to end the session from there. Return to the Concurrent Manager Recovery screen and refresh the page to verify all managers have been shut down before proceeding to the next step.
Any processes listed here must be terminated before continuing. Because these processes have lost their database sessions, they must be manually terminated from the command line. Refer to your operating system documentation for instructions on terminating a process from the command line.
After terminating the processes, click Update to mark the processes as no longer active in the database table. Click the Refresh icon to verify that all processes have been terminated.
Listed for each process are:
CP ID
Manager
Node
OS PID
Started At
Click the Reset button to reset the listed requests for conflict resolution. This action changes requests that are in a Pending/Normal phase and status to Pending/Standby. Click the Refresh icon to verify that all requests have been reset.
You can drill down on the Request ID to view the request in the Advanced Search for Requests screen.
Listed for each request are:
Request ID
Program
User
This page lists the requests that do not have a manager. If any requests have Active Sessions listed, drill down on the session ID and terminate the session from the Database Session Details screen. Return to the Concurrent Manager Recovery screen and click the Refresh icon to verify that the session is no longer active.
Listed for each request are:
Request ID - Drills down to display the request in the Advanced Search for Requests page.
Parent ID
Program
User
Phase
Status
Active Session
The summary page lists the information collected from the previous steps. After reaching this page, you should be able to restart your Internal Concurrent Manager. If you cannot, retry starting the Internal Concurrent Manager with DIAG=Y, refresh the summary page, add it to the Support Cart with the log files, and send them to Oracle Support.
Log Files Collected - Click on the log file name to view it. The log files can be added to the Support Cart.
Report Summary
Active Managers with a Database Session
Managers Deemed Active but Without a Database Session
Reset Conflict Resolution
Requests that are Orphaned
Navigation: Site Map > Diagnostics and Repair > Service Infrastructure (under Troubleshooting Wizards)
Using the Service Infrastructure diagnostic wizard, you can examine existing Generic Service Management data to determine potential problems, and update the data to eliminate the issues.
Click Run Wizard to begin using the wizard.
This screen lists any active nodes without a registered service manager. Concurrent processing requires a registered Service Manager on every registered node. If you need to register service managers for the listed nodes, you can click on the Register button to do so.
This screen lists any concurrent processing nodes that need a registered Internal Monitor. Click the Register button to register Internal Monitors for any listed nodes.
This screen lists service managers and Internal Monitors that are registered for deactivated or nonexistent nodes. If you do not plan on using these nodes in the future, these managers, including the Internal Monitor, can be disabled. Click the Disable button to disable the managers for a node.
All active nodes should have active service managers. This screen lists active nodes without active service managers. Click the Activate button to activate service manager definitions for the listed nodes.
This screen shows service instances without any workshifts defined. You can add the Standard workshift to the listed service instances using the Add Workshifts button.
This screen lists any service instances that are assigned to a node that does not have an uppercase name. Use the Uppercase button to change the names of the listed nodes to uppercase.
This screen lists any processes on nodes that do not have an uppercase name. Use the Uppercase button to change the names of the listed nodes to uppercase.
This screen shows a summary of the data found for each of the previous screens, as well as any changes you made.
Configuration and Log files are listed first. Two log files and two configuration files are listed for each node. You can click on the name of the file to view it and add it to the Support Cart. You can add all the files to the Support Cart using the Add All Files to Support Cart button.
Navigation Path: Site Map > Diagnostics and Repair (tab) > Troubleshooting Wizards (heading) > GCS and Forms Monitoring (link)
The GCS and Forms Monitoring wizard helps you troubleshoot the OAM Generic Collection Service.
The wizard cannot be launched unless the Internal Concurrent Manager (ICM) is up and running.
Click Run Wizard to start the wizard. The steps in the wizard are as follows:
If necessary, register the OAM Generic Collection Service on all listed nodes.
If necessary, enable the OAM Generic Collection Service on all listed nodes.
If necessary, activate the OAM Generic Collection Service on all listed nodes.
See the registration of the Forms Listener.
If necessary, enable the Forms Listener on all listed nodes.
If necessary, set the Sign-On Audit level to "FORM".
See a summary screen where you can view a log file and add files to the Support Cart.
The CP Signature Wizard collects information regarding the current status of concurrent processing on the system.
Navigation: Site Map > Diagnostics and Repair > CP Signature
This wizard collects information on the following:
Configuration status for Parallel Concurrent Processing, Real Application Clusters, and Generic Service Management
Registered nodes
Concurrent processing package versions
Concurrent processing package errors
Concurrent processing profile options
Service instances that could be managed by concurrent processing
Concurrent processing processes
Request processing manager specialization rules
Request Conflict Resolution
Concurrent request processing statistics
Recent requests to run the Purge Concurrent Request and/or Manager Data program
The Support Cart feature allows you to save Oracle Applications Manager pages with their data and then zip them up in a file to send to Oracle Support. Oracle Support can then view your pages in the Oracle Applications Manager display format.
When you click the Add to Support Cart button, the page is added to the Support Cart. If you have filtered or sorted the data, your manipulated view is submitted.
For example, these are some of the pages with the Support Cart feature:
Configuration Overview
Site Level Profile Settings
Recommended/Mandatory Initialization Parameters
ICM Environment
Products Installed
Invalid Objects
Concurrent Manager Recovery
Report Results
All log files
To view the contents of the Support Cart, click on the Support Cart global button.
Click Save Cart to save the contents to a zip file that you can send to Oracle Support.
Any contents of the cart that are not saved are automatically deleted when you log out of Oracle Applications Manager.
To restore a saved cart, click Restore Cart to browse your directory for the saved cart.
To restore a cart file, select a cart file from the list displayed, or use Browse to select a file from the directory. Then click Restore.
Enter a TAR Number and additional details for the Support Cart Contents.
The Support Cart can collect a standard set of information regarding your E-Business Suite system. Oracle Support requires this information when logging a technical assistance request (TAR).
To collect this information, click Collect.
In the Generic region, information is collected on:
Product information - For each product, the version, current patch level, and status (for example, “Installed”) is shown.
Database parameters - The init.ora parameter settings.
Patches - For each individual patch applied, the patch number, type (for example, “Patch Set” or “Maintenance Pack”), and application timestamp is shown.
Topology - This page includes data about all the nodes of the applications infrastructure. For each node, it collects information about the operating system and the different services running on that node.
Database version
Click the View icon to view these pages. If you want to delete a page, select it and click the Delete button. Clicking Collect again will collect information for all four pages again.
In the Nodes region, you can specify to include or exclude output and log files for specific nodes as well.
Pages that you save using the Add to Support Cart button are listed under this tab.
This page displays the log file generated by Oracle Applications Manager.
Navigation: Site Map > Administration > Applications Manager Log (under Others)
The current message level of the log is shown. To change the level, select the desired option and click Go.
Note: Changing the log level from this page will only be effective until the servlet is restarted. For a persistent setting, the log level initialization parameter must be changed in zone.properties. The parameter is: oracle.apps.oam.logger.level
For example:
servlet.weboam.initArgs=oracle.apps.oam.logger.level=USER
Bounce Apache/Jserv for your changes to zone.properties to take effect.
The possible settings are:
USER - includes messages related to Oracle Applications Manager initialization routines, trace information about the error message, and any diagnostic messages related to customizations or extensions that have been added.
SUPPORT - includes the User level messages and additional information useful to support for diagnosing problems (for example, configuration setting details, prerequisite patch-related issues, and module-related information).
DEV - (Development) includes trace information related to code paths (for example, "Inside method A") and any code-related information that could be useful to the developer to diagnose a problem. This level also includes performance-related log messages.
The default is USER.
The log can be added to the Support Cart.