The health report shows system status for the application, database, and data warehouse.
The health report also detects any non-compliant governor settings (maximum data limits).
A related discovery analysis report detects system customizations.
The Log Analysis page includes system statistics, daily page or XOG views, and log data.
A Job Monitor page shows the currently running jobs.
In 15.6 and higher, a new Data Warehouse Audit dashboard shows the latest progress of the Load Data Warehouse job.

To run the Health Report, verify that you have the
Administration - Application Setup
global access right.
To view the Log Analysis portlets, verify that you have the
Administration – Access
right and that you are assigned to the Log Analysis Access group.
To run the tomcat access logs, verify that you have the
Jobs - Access
right. Also verify that you have the following instance level job definition access right:
Job - Run
on
Tomcat access log import/analyze
.

Log in to
Classic PPM
with administrative access rights.
Click the
Administration
menu. Under
Security and Diagnostics
, select
Health Report
.
Select one of the following tabs:
Summary
: This tab lists the health status and completion percentage for the application, database, and data warehouse. The % Completed value calculates the total number of settings that require a value during a new install or upgrade. The health report summary shows you what portion those required settings have a value. For example,
88% Complete
indicates that you are still missing valid values for the remaining 12 percent of all settings. When the report shows Setup Complete and a green status icon, the health for that category is good. When setup is not complete, a red icon appears. Click Details to view one of the three other tabs.
Application
: This tab shows application server details. Settings include file locations, URLs, Java version, JVM, LDAP, SSO, SSL, and ports. You also see instance-specific configurations for CSA, background (bg), and beacon services.
To verify settings for
Clarity
, expand Application Instance (app), New User Experience. The
ppm-ux
attribute appears with a red icon when a newer version is available but is not deployed. The
Clarity
features are delivered and updated through a separate Java WAR file. WAR files should have a META-INF folder.
To verify settings for governor limits, expand Governor Limits.
To switch the status of the on-the-fly RateMatrix property, click Enable or Disable. When enabled, the application applies the PRJ_RT_RATES_EXTRACTION rate matrix options. This setting is disabled by default.
Database
: This tab provides information about database connectivity, table spaces, database options, and server parameters.
Data Warehouse
: This tab provides information about data warehouse connectivity, table spaces, data warehouse options, and server parameters. Settings include JDBC URL, database timezone mismatch, database size, and ETL job timeout for the Load Data Warehouse job. This tab also includes setup information for time slices and other application settings for the data warehouse.
Click the
Fix It
link to navigate to the application page where you can fix the non-compliant setting. For example, a red icon and
Fix It
link appear to help you set up entities or time slices. Remember that the 'From Date' and 'Number of Periods' have to match the records in the Data Warehouse for each type of period.
To view the recommended values for each setting on the Database and Data Warehouse tabs:
The Recommended field provides the required values to achieve compliance and improve system health. If no exact value is recommended, the field remains empty.
Hover your mouse over the Status icon to view a recommendation to fix the listed item.
As an Oracle database administrator, you might have permissions to V_$PARAMETER. If you do, expand Database Parameters to view the health of your database and data warehouse parameters. If you do not have permissions, hover over the status icon to show the command to grant access.
To export the complete health report to Excel, click the Download Health Report button on the Summary tab. Open the HealthReport.xlsx.zip file to view the HealthReport.xlsx file in Excel.

  admin healthreport

JDBC URL
Database parameters
SQLNET parameters

New installations are set to the recommended values shown above.
Upgrades preserve your previous settings.

Server setting required for the API calls to work
<accessToServerStatus allow="ALL" />
Navigate to the following API landing page:
http(s)://<server>:<port>/niku/serverstatus/governorlimits
To view the response in HTML format use the following URL:
http(s)://<server>:<port>/niku/serverstatus/governorlimits?run=html
To get the results of the violators use the following url:
http(s)://<server>:<port>/niku/serverstatus/governorlimits?type=violators

These commands are the exclusive method allowed and supported for temporarily bypassing the governor limits up to the established critical limits
Critical limits were determined based on the max numbers set across all our SaaS customers
The only way to bypass the critical limits is through a direct database update (not supported or recommended)

admin governors -set <governorKey> <governorValue>

admin governors -list <governorKey|all|violated>

admin governors -unset <governorKey|all> set to default and enables governor

C:\Windows\System32>admin governors -list MAX_SQL_GEL_ROWS
Code: MAX_SQL_GEL_ROWS
Current Limit: 110000
Critical Limit: 120000
Default Limit: 100000
Active: true
# # # # # # # # # # # # # # # # # #

Log in to
Classic PPM
with administrative access rights.
Click the
Administration
menu. Under
Security and Diagnostics
, select
Health Report
.
Below the Summary tab, click the
Download Discovery Analysis Report
button. The output contains about 20 tabs of data including non-compliant objects, data sources, and grid portlets. Discuss these customizations before upgrading or changing environments.
(Optional) For large deployments, the Discovery Analysis report is also available as a job for your convenience. To prepare this report, select the Active check box for the
Clarity
Customization Discovery Analysis job. The job produces an Excel spreadsheet which can also be e-mailed to the recipient that is specified in the job parameters at the time of execution.

Log in to
Classic PPM
with administrative access rights.
Refer to the
Required Access Rights
section at the start of this document. To refresh the data in these portlets, you first run a job to export the data from the server and import it into the application database.
Click the
Administration
menu. Under
Security and Diagnostics
, select
Log Analysis
.
Select one of the following tabs:
System Stats by Hour/Day
: Use this tab to view average server response times, total sessions, and a list of the slowest actions performed for a specific day.
System Stats by Month
: Use this tab to view monthly page views and XOG requests for all servers or grouped by server. You can also view monthly session counts.
Daily Page/XOG Views
: Use this tab to analyze the top 20 slowest pages. For example, you could troubleshoot the slowest pages and then optimize them for improved performance. This tab includes page views by service or server, daily page views, average response times by day, XOG requests by service or server, their average response times, and the total number of XOG calls by day.
Enter your filter criteria:
Select a
Date
.
Select an
Environment
such as
All
or
local
.
Select a
Hostname
such as
All
or a specific application server.
Click
Filter
.
To export the data, click the
Log Data Export
tab. Specify the
Environment
and the date range for the exported data. Each row of exported data shows the date, total page views by all users, the average page response time in seconds, the total number of XML Open Gateway (XOG) requests, the average XOG response time, and the unique session count for that day.
To configure any of the portlets on these tabs, click
Configure
if available. To export the data to Excel or PowerPoint, click Export to Excel or Export to PowerPoint. Not all portlets support these options.

Log in to
Classic PPM
with administrative access rights.
Select
Administration,  Security and Diagnostics
,
Jobs Monitor
. The following information appears:

Job Name
: The instance of the job that is currently running.
Run ID
: The instance ID for the currently running job.
Job ID
: The ancestor or parent ID for the running job.
Job Definition Name
: The ancestor or parent job name.
Job Definition ID
: The ancestor or parent job definition.
Description
: An optional description of the job.
Scheduler Server
: The server that queued the job process and that is now running the job. For example, [email protected]_server1.xx.yyy

Log in to
Classic PPM
with administrative access rights.
Click
Administration,  Security and Diagnostics
,
Data Warehouse
.
(Optional) To search the audit data, click
+ Expand Filter
, enter your filter criteria, and click
Filter
.
The
Data Warehouse Audit
portlet displays the following fields:
Data Warehouse Table Name
Update Date
Load Start Date-Time Stamp
Load End Date-Time Stamp
Duration (seconds)
Row Count
Examine the audit data. For example, sort by row count or duration to examine the heaviest table loads.
If any errors occurred, the companion
Data Warehouse Error
portlet displays the following fields:
Data Warehouse Table Name
Error Message
Error Number
SQL Command
(Optional) Click
Options
to configure the audit or errors portlet. You can also export the data. For example, export an offending SQL command to a CSV file and send to your troubleshooting team.