Stat 6.3 - User Guide

Migration Indicators

When you migrate an archive set, the target environment graphic appears to fill up. When you migrate an interim archive set, the environment graphic appears half full, and the color changes. When you migrate the final archive set, the environment graphic appears full and the color changes again. Migrating the final archive set fills up both the source and target environments. Also, the graphic for the source environment of the final archive set reads “final src.”

When you migrate an archive set, the line linking the two environment changes color accordingly. When you migrate the base archive set to the Development environment from the Base environment, a curved arc links the two environment graphics.

Migration Details Window

The Migration Details window displays information regarding all the archive set migrations into the selected environment as well as patch applications. To open the Migration Details window, double-click on an environment graphic in the Migration Path tab, or right-click on an environment tree node in the Archive Sets tab and select View Migration Status.

You can also open the Migration Details window from the Migration History Wizard and the Migration Console. For more information, see Migration Details Window .

Stat provides more detailed information regarding the archiving and migrating of objects in the log files and messages generated by the Stat Oracle Agent, which are available in the Process Request tab. For more information, see the next section, Viewing Log Files and Agent Messages .

NOTE: When you open the Migration Details window by double-clicking an environment, the window shows information regarding all the migrations and patch applications that have targeted that environment.

Viewing Log Files and Agent Messages

In the Process Request tabs of the CSR 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 CSR 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).

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