From the Monitoring tab on the OAM Site Map, you can access these utilities.
Navigation: Site Map > Monitoring > Forms (under Availability)
This page lists the service instances for the Forms Listeners. From this page you can edit information for a selected service instance. You can also view its status, view processes, and view information on its Forms Runtime Processes. Also, you can start, stop, abort, or restart the instance.
Navigation: Site Map > Monitoring > SQL Activity (under Performance)
This page provides data regarding SQL Activity:
SQL_HASH
Physical Reads
Logical Reads
Total Sorts
Execs
Total Loads
Load
For more information on these columns, see the Oracle database documentation.
Main Navigation Path: Site Map > Monitoring (subtab) > Performance (heading) > Concurrent Request Runaways (link)
System performance can potentially be affected by database sessions that should have ended when their corresponding concurrent requests were canceled, but for some reason did not.
If any such database sessions are currently active, they will be reported on this page. The table supplies context information for each session: request ID, AUDSID, program, user name, start time, phase, status, Oracle SPID, and PID. You can delete a session by selecting it in the table and clicking Terminate. You can drill down on the links in the request ID, AUDSID, program, and user name columns to view the respective details.
The following information is shown:
Navigation: Site Map - Monitoring > Forms Sessions (under Current Activity)
This page shows information on the current forms sessions. Every open form has its own database session, or "form session."
The profile option "Sign-On:Audit Level" should be set to 'Form' to use this feature. If this profile option is not set to 'Form', the Forms Sessions table will show an empty table even when there are active forms sessions.
To filter the display by Form Name, Username, Responsibility, or Application, make the appropriate selection from the drop-down menu, enter the search string in the field provided, and click Go.
The following data is shown for each session:
Form Name
AUDSID - The auditing session ID. Click on the value to drill down to the Database Session information page.
RTI_PID - The runtime instance process ID. Click on the value to drill down to the Forms Sessions for Process ID page.
Username
Responsibility
Application
LRs (Session Logical Reads) - Input/output (I/O) is one of the most expensive operations in a database system. SQL statements that are I/O-intensive can monopolize memory and disk use and cause other database operations to compete for these resources. To prevent single sources of excessive I/O, Oracle lets you limit the logical data block reads per call and per session. Logical data block reads include data block reads from both memory and disk. The limits are set and measured in number of block reads performed by a call or during a session.
PRs (Physical Reads) - The total number of data blocks read from the disk for the session.
CPU
PGA (Session Program Global Area memory) - The PGA is a memory buffer that contains data and control information for a server process. A PGA is created by Oracle when a server process is started. The information in a PGA depends on the configuration of Oracle
UGA - User Global Area memory used by the session.
Duration - in HH:MM:SS
Click on the Session Details button or the AUDSID to view database information for the selected forms session.
Use the Diagnostics On/Off button to turn on or off the Forms Runtime Diagnostics (FRD) for the runtime process. If this button is disabled, make sure your Forms patch set level is 12 or higher (that is, 6.0.8.20 or higher) and then set the environment variable FORMS60_OAM_FRD for the Forms Listener process.
If you click on the RTI_PID from the Forms Session window, or if you click on the PID from the Forms Runtime Processes window you will see the fields described above as well as the following data for the Process ID:
Client IP Address
Server Host Name
CPU Time
Memory Usage (KB)
Diagnostics (On/Off)
Log File Name
Use the View Diagnostics button to view the Forms Runtime Diagnostics (FRD) log file. The log file can be added to the Support Cart.
Navigation: Site Map - Monitoring > Forms Runtime Processes (under Current Activity)
This page shows information about Forms runtime processes. You must first register and start a service instance of the OAM Generic Collection Service to collect this information. The Generic Collection Service must be running for the information to be collected.
You can filter your view by Node or Username.
The following columns are shown for each session:
PID - The ID of the runtime process for the user session. Click this value to drill down to the Forms Sessions for Process ID page.
Node
Memory (KB) - The memory used by the runtime process in kilobytes. For HP and AIX platforms, this is the virtual memory size. For all other platforms, this is the resident set size.
CPU
Duration
Client IP Address - The IP address of the client machine used to connect to the Forms Services.
Username - The database username used by the Forms application for the user session.
Diagnostics - On/Off
Last Update Time
Use the Upload button to refresh the data on this page.
Use the Terminate button to end a selected process.
Click on the Sessions button or click on the PID to view the Forms Sessions for Process ID page.
Navigation: Site Map > Activity Monitors (under Activity)
This region displays information on the system's activity.
A Database Sessions graph displays the number of database sessions related to the following:
Login sessions
Oracle E-Business Suite forms sessions
Services
Requests
A Concurrent Requests graph displays the number of requests with the following statuses:
Pending
Running
Waiting on a lock
Inactive
Completed in the last hour
Click on the bar for any status to drill down to more information on requests of each status.
Navigation: Site Map - Monitoring > Forms Sessions (under Current Activity) > (B) Session Details
This page displays detailed information about the selected database session. Click Terminate to end the database session.
Form or Service Name
Username
Responsibility
Logon Time
Serial Number
OS PID
Status
Session ID
Oracle SPID
User
SQL Hash - If the value shown is a link, you can click on it to view a page showing the SQL statement that is currently executing, as well as an execution plan for the statement. For more information on execution plans, see the Oracle database documentation.
OS User
Machine
Process
Terminal
Module
Module Hash
Action
Program
Event
Wait Time
Timeouts
Average Wait
Total Wait
Maximum Wait
Set the trace options to the level desired. Options available are:
Normal Trace
Trace with Waits
Trace Off
Trace with Binds
Trace with Binds and Waits
Click Apply to apply any changes made to the Tracing Options. Click View Trace to view the current trace information.
The following information is shown:
The feature monitors an Oracle E-Business Suite user's current activity within the system, with respect to the system components. It monitors the user's current activity within forms and concurrent programs. Sign-on Audit should be turned on for Form Activity data to be available.
Navigation: Site Map > Monitoring > Invalid Objects (under Current Activity)
This page lists invalid objects in the database. To remove invalid objects, you can compile the APPS schema (for invalid objects in the APPS schema) or run a script provided with the database (for other invalid objects). See Maintaining the Databasefor more information on compiling objects.
Navigation: Site Map > Monitoring (subtab) > Current Activity (heading) > Forms Runaway Processes (link) Overview
You can also access this page by clicking the View Runaways button on the Forms Runtime Processes page.
Running Oracle E-Business Suite requires the creation of many system-level processes. On occasion, processes can behave incorrectly and have a negative impact on system performance. In Oracle Applications Manager, you can:
Configure thresholds (maximum memory size, maximum CPU percent, maximum duration in minutes) for tracking runaway processes. These settings take immediate effect as soon as you click Apply. These settings are used to raise system alerts on the Applications Dashboard.
See the user name and IP address of runaway processes.
Terminate processes.
See the parameters of the OAM Generic Collection Service (the background process which runs on all Forms nodes).
Open the associated log file.
You can define memory, CPU, and duration thresholds. Memory refers to process memory size, resident set size, or total virual memory size based on the platform. On a UNIX system, CPU refers to the cumulative execution time of the process. On a Windows NT system, CPU is, CPMemory - Process memory size, Kb, resident set size or total virtual memory size based on the platform. CPU - On UNIX, it is the percentage of CPU use. If the system has both UNIX and Windows NT nodes, then CPU refers to the percentage of CPU use. In all cases Duration refers to the total time elapsed since a connection was established.
The default values of the thresholds are as follows:
Maximum memory: 1.0 MB
Maximum CPU: 25%
Maximum duration: 20.0 minutes
Navigation: Site Map > Monitoring (tab) > Applications Usage Reports (under Usage)
The Applications Usage page contains links to the following pages:
Products Installed
Applications Users Per Module Summary
Page Access Tracking and Sign-On Audit: Configuration, Reports
Applications Usage Reports: Purchase Lines Processed, Order Entry Lines Processed, and more
Navigation:
Applications Systems > (B) Configuration > Products Installed
or
Applications Systems > (menu) Applications Usage > (B) Go > Products Installed
This page lists the following information for Oracle E-Business Suite products:
Application Short Name
Application Name
Version
Status - A product's status can be Installed, Shared, or Inactive. Installed indicates that the product has been licensed and installed. The Shared status is used for products that other products are dependent upon. Products that are neither Installed nor Shared have an Inactive status.
Navigation: All Applications Systems > (pull down menu) Applications Usage > (B) Go > Application Users Per Module Summary
This page lists the following information for Oracle E-Business Suite modules:
Application Short Name
Module Name
Count - number of current users
You can view details for a particular module by selecting its radio button on the left and clicking the View Details button. This takes you to a page that lists the following:
Module Name
User Name
Description of User
Creation Date of User
Last Log On Date
Click Show All to see a format suitable for printing that lists all users. Within the Show All format, click on Show Set to see the table format of the list.
Page Access Tracking and Sign-on Audit tracks the accesses of Oracle E-Business Suite JSPs and Oracle Forms for usage pattern analysis and performance statistics. The Reports screen displays the complete flow of accesses across technology stacks within a user session. It also aggregates collected metrics and display summary statistics.
Use these reports to collect information on specific applications usage. Your License Management Services analyst may ask you to collect such information, or you can use these reports for your own monitoring.
The following reports can generate information on various licensing metrics in a time period you specify. However, for the purposes of License Management, a twelve (12) month period is used.
These reports generate information for the licensing metric Purchase Line. Purchase Line is defined as the total number of purchase line items processed by the application during a 12 month period. Multiple purchase lines may be created on either a requisition or purchase order or may be automatically generated by other Oracle E-Business Suite programs. For iProcurement, Purchase Lines are counted as all line items on an approved requisition created in iProcurement. For Internet Supplier Portal and Purchasing Intelligence, Purchase Lines are counted as the line items on purchase orders processed through each of those applications. This does not include communication on the same Purchase Order. For each application, you may not exceed the licensed number of Purchase Lines during any 12-month period unless you acquire additional Purchase Line licenses from us. You may acquire a different number of Purchase Line licenses for each program (Number of Purchase Lines for iProcurement could be a smaller number than for Internet Supplier Portal).
For Internet Supplier Portal, use the Suppliers script to generate a list of suppliers and their IDs. You can then use this information when running the Purchase Line Items Processed report for Internet Supplier Portal.
This report is used for the licensing metric Order Line, which is defined as the total number of order entry line items processed by the program during a 12 month period. Multiple order entry line items may be entered as part of an individual customer order or quote and may also be automatically generated by the Oracle Configurator. You may not exceed the licensed number of Order Lines during any 12 month period.
This report is used for the licensing metric Expense Report, which is defined as the total number of expense reports processed by the iExpenses during a 12 month period. You may not exceed the licensed number of Order Lines during any 12 month period.
This report is used for the licensing metric Invoice Line, which is defined as the total number of invoice line items processed by the program during a 12 month period. You may not exceed the licensed number of Invoice Lines during any 12 month period unless you acquire additional Invoice Line licenses from us.
Use this page to run seeded and custom scripts.
Navigation: Site Map > SQL Extensions (under Others)
Click on the icon in the Focus column to display only those reports from the selected group.
Use the Hide/Show icon next to the group name to hide or display the reports contained in the group.
The following columns are shown for each report:
Name - Click on the name of the report to display the report details.
Description
Protected - A "locked" icon indicates that a password is required to submit the report.
Run Report - Click on the icon in this column to run the report. If a password or parameters are required, the SQL File Details page will display. Otherwise, the output of the report will display in the Results page.
Use the Reload button to reload the displayed reports from the metadata file.
You can have your custom scripts automatically discovered by Oracle Applications Manager and available to run from the SQL Extensions page.
Create a new SQL script. Multiple SQL statements are allowed within the same file. For example: a report called "Get Sysdate": sysdate.sql
Create a directory called /custom/sql for your custom SQL files under <APPL_TOP>/admin. Your directory structure should look like <APPL_TOP>/admin/custom/sql.
Copy your SQL files to <APPL_TOP>/admin/custom/sql directory.
Now log in to Oracle Applications Manager and navigate to Site Map > SQL Extensions.
The discovered SQL files will be under the "DefaultC" group.
After the files are discovered, you can customize the grouping, protection, and execution method of these scripts.
To customize the grouping, protection, report format, or drill-downs for your automatically discovered scripts, you must edit oamcustext.amx located under <APPL_TOP>/admin/custom/xml.
For each discovered script, the oamcustext.amx file will contain an entity similar to the following example that defines the grouping, protection, and report format:
<cReport type="SQL" group="DefaultC">
<title>sysdate.sql</title> <script name="sysdate.sql" protected="yes" execMode="SQLPLUS" parameters="unknown">
</script>
</cReport>
You can change the group that your report displays under.
In the oamcustext.amx file, change the value of "group" to the name of the group you want your report to appear in. For example, to change the group to "Custom Reports", the result would be:
<cReport type="SQL" group="Custom Reports">
<title>sysdate.sql</title>
<script name="sysdate.sql" protected="yes" execMode="SQLPLUS"
parameters="unknown">
</script>
</cReport>
Log in to Oracle Applications Manager and navigate to the SQL Extensions page (Site Map > SQL Extensions).
Click the Reload button to reload the metadata. Your script will appear under the new group.
You can change the password protection that is set on your report.
In the oamcustext.amx file set the value of "protected" to "yes", if you want password protection enabled on your script. Set it to "no" to remove password protection. For example, to set the protection to "no", the result would be:
<cReport type="SQL" group="Custom Reports">
<title>sysdate.sql</title>
<script name="sysdate.sql" protected="no" execMode="SQLPLUS" parameters="unknown">
</script>
</cReport>
Log in to Oracle Applications Manager and navigate to the SQL Extensions page (Site Map > SQL Extensions).
Click the Reload button to reload the metadata. Your script will appear with the "unlocked" icon.
In the oamcustext.amx file set the value of "execMode" to "SQLPLUS" text format, or set it to JDBC for HTML format. For example, to set the report format to HTML, the result would be:
<cReport type="SQL" group="Custom Reports">
<title>sysdate.sql</title>
<script name="sysdate.sql" protected="no" execMode="JDBC" parameters="unknown">
</script>
</cReport>
Log in to Oracle Applications Manager and navigate to the SQL Extensions page (Sitemap > SQL Extensions).
Click the Reload button to reload the metadata.
For reports defined in HTML format, you can provide drill-downs from the results of your script to other Oracle Applications Manager pages. Currently drill-downs are supported for requests based on REQUEST_ID and database session information based on AUDSID.
Example:
Suppose your SQL script returns REQUEST_ID as the first column of the report, you can link it to the Request Details page as follows:
Ensure that execMode="JDBC"
Add the following to the entry for your SQL script:
<keyColumns>
<column position="1" key="REQUEST_ID"/>
</keyColumns>
Here, position="1" indicates that the REQUEST_ID column is the first column reported by your select statement. Currently the possible values for the key attribute are REQUEST_ID and AUDSID.
The new full entry for your SQL script will look like the following:
<cReport type="SQL 'group="Custom Reports">
<title>sysdate.sql</title> <script name="sysdate1.sql" protected="no" execMode="JDBC"
parameters="unknown">
</script>
<keyColumns>
<column position="1" key="REQUEST_ID"/>
</keyColumns>
</cReport>
If you try to execute a SQL script and encounter the following error message:
An error has occurred!
<filename>(No such file or directory)
The SQL file does not exist under <APPL_TOP>/admin/custom/sql. Make sure you have copied the file into this directory.
If your SQL script takes input parameters, ensure that you provide the parameters one per line in the Input Parameters text field. The result will contain errors if you do not provide the necessary parameters.
Navigation: Site Map > SQL Extensions >(select report name)
This page displays information based on the report definition. Information may include:
Description
Report Format - HTML or Text
Applications Schema Password - If the report is password-restricted, enter the password here.
Input Parameters - Enter any required or optional parameters.
You can run the report from this window by clicking the Run Report button.
Navigation: Site Map > SQL Extensions (Run Report)
The contents and format of this page will vary depending on the report run.
Report results returned in HTML allow you to filter the report by a specific Column value.
Use the Refresh button to rerun a report from this page.
Click Add to Support Cart to add your report results to the Support Cart.