Chat now with support
Chat with Support

Stat 6.0 - User Guide

Introduction to Stat Connecting to Stat Change/Service Requests Stat Consoles Tasks and Time Entries Stat Projects Search Engines Reports and Graphs Personal Rules Object Tools and Wizards Change Management for PeopleSoft
Object Management (PeopleSoft) Object Archives (PeopleSoft) Object Migrations (PeopleSoft)
Change Management for Oracle Applications
Object Management (Oracle Applications) Patch Management Object Archives (Oracle Applications) Object Migrations (Oracle Applications)
Change Management for Generic Applications
Object Management (Generic Applications) Object Archives (Generic Applications) Object Migrations (Generic Applications)
Appendix: Troubleshooting Chart Appendix: Migration Options Appendix: User-Specific Parameters Appendix: Supported PeopleSoft Proprietary Objects Appendix: Stat Reports

Viewing Log Files and Agent Messages

In the Process Request tabs of the Change Management/Version Control window and the Oracle Applications Management Console, you can view the log files and the messages the Stat Oracle Agent generated while processing object management requests (including patch applications, backouts, and impact analysis as well as archiving and migrating objects). These log files include detailed information that pinpoint the source of warnings and errors generated during processing.

Be aware that the Process Request tab in the Change Management/Version Control window only shows processes specific to that CSR, while the Process Request tab in the Oracle Applications Management Console shows the process requests of all active CSRs. For more information, see Process Request Tab .

For R12.2 environments, a large number of log files may be generated at the end of each cycle. Typically the following directory is created $NE_BASE/EBSapps/log/adop/<session id> and log files for each phase of the Patch Cycle are placed there. Stat by default captures all *.log and *.lgi files. You can configure the following new environment variable to control this pattern:

<env>.env.ADOP_LOG_PATTERN defaults to "(.*\\.log)|(.*\\.lgi)". This is a regular expression that captures all *.log and *.lgi file extensions. If you also need to capture *.out files, override the pattern like so:
<env>.env.ADOP_LOG_PATTERN: (.*\\.log)|(.*\\.lgi)|(.*\\.out).

2
Click View Log.

The Agent Logs window displays all the log entries generated for the selected process request. The Status field indicates if the log includes an error or a warning. Logs that do not include errors or warnings have a status set to ‘Information.’ Also, if a user has manually changed the status of a process request, that user must submit a written explanation of the reason for the change, which is then processed as an information log by the agent. These information logs display the filenames Process Status Change. For more information, see Changing Process Event Statuses .

If you want to export the log as a text file, click Export, and then specify the file name. Exporting log files may be helpful if the file is especially large (1MB or greater) as indicated in the File Size column of the Agent Logs window, if you intend to view the log at a later time, or if you intend to process the log programmatically.

To view a log, double-click on it or select it and click View. Stat displays the log in the Event Log window.

 

Change Management for Generic Applications

Object Management (Generic Applications)

Although Quest® Stat® is designed as a complete change management solution for PeopleSoft® and Oracle® Applications, this support can be extended to other file-based (i.e., generic) applications. This is done by system administrators who define in Stat the connection pathways and source directories of the application servers or databases, as well as the types of objects that Stat will support. Once these configuration parameters are in place, users can lock, archive, and migrate objects in generic application environments the same way they do objects in PeopleSoft and Oracle Applications environments.

In Stat, any action you take involving an object is handled and recorded on its associated CSR, including editing, archiving, or migrating it to other environments. Also, Stat lets you place a lock on an object once you associate it with a CSR. Object locking promotes coordination between developers by ensuring that they do not overwrite each other’s work.

For generic applications, there are three classes of objects that you can associate with CSRs:

Classification of Supported Objects

Although Quest® Stat® is designed as a complete change management solution for PeopleSoft® and Oracle® Applications, this support can be extended to other file-based (i.e., generic) applications. This is done by system administrators who define in Stat the connection pathways and source directories of the application servers or databases, as well as the types of objects that Stat will support. Once these configuration parameters are in place, users can lock, archive, and migrate objects in generic application environments the same way they do objects in PeopleSoft and Oracle Applications environments.

In Stat, any action you take involving an object is handled and recorded on its associated CSR, including editing, archiving, or migrating it to other environments. Also, Stat lets you place a lock on an object once you associate it with a CSR. Object locking promotes coordination between developers by ensuring that they do not overwrite each other’s work.

For generic applications, there are three classes of objects that you can associate with CSRs:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating