In this DocumentGoal
Solution
References

Applies to:

Oracle Advanced Supply Chain Planning - Version: 11.5.2 to 12.0
Information in this document applies to any platform.
EXECUTABLE:MSRFWOR - Refresh Collection Snapshots

Goal

The Refresh Collection Snapshots can be run as a standalone concurrent request using the following steps

This is recommended as a first step when launching Data Collections for the first time on a new or cloned instance.

Solution

The request is available under the Material Planner responsibility.
OR in 11.5.10 and above in Advanced Supply Chain Planner.
OR using System Administrator, it can be added to the Request Group OM Concurrent Programs
so that it is visible when for ATP Data Collections from Order Management

For Distributed installations with separate ERP and APS instances, this is ALWAYS run on the ERP Source Instance

NAV: Material Planner (or ASCP) / View / Requests / Submit a new Request

Parameters:
1. Refresh Method - Fast / Complete / Automatic
Fast Refresh will only process changes since the last run of the Refresh Snapshots or Data Collections.
Complete Refresh will process all the snapshots and completely refresh the snapshot(s).
Automatic Refresh will truncate the snapshot log and then run a complete refresh of the snapshot(s).
Note: Automatic Refresh does NOT check the profile MSC: Source Setup Required, so if running for the first time after a patch or in an newly cloned instance, then use Complete Refresh

Note: When running Data Collections request set, Refresh Snapshots always uses a Fast Refresh for performance reasons. This is usually not a problem, unless the snapshot logs have grown very large. Then corrective steps are required.

2. Snapshot Name - Use the Default 'All Snapshots' or choose a snapshot from the list

3. Threshold for Truncating Logs - Used only in Automatic Refresh.
Enter the number of lines to check for in the MLOG$ table.
For example, a value of 50 will truncate the log if 50 or more lines are in the MLOG$ snapshot log table and then perform a complete refresh of the snapshot.
Use 0 when running this to help resolve performance issues.

4. Degree - Refers to the degree of Parallelism to be used by the database to process the request.
Maximum value is 10. The higher the degree of parallelism, the faster the process will complete.
Note: Entering a number higher than 10 will result in the use of 10 for this value.

Also see Note 207644.1 Data Collections Fails - First Steps to understand the Setup Requests that are run by the Refresh Snapshots concurrent program when MSC: Source Setup required = Y

For Performance or Errors with Refresh Snapshots standalone or as part of the Data Collection request set

1. First step is to run standalone for All Snapshots with Automatic Refresh and Threshold = 0. Then run Data Collections with a Complete Refresh.
   This step is highly recommended for new or cloned instances before Data Collections request set is launched for the first time.
   The standalone request with Automatic refresh may take a long time to complete if the snapshot logs have become very large. But this should result in better performance when running the Data Collections request set.
2. IF errors with tables or tablespace occur (ORA-1654, ORA-1653, ORA-1652 ORA-1655, ORA-1651), THEN you will need to add space to the system. Note 220115.1 should be helpful for information about managing space requirements for APS.
3. IF snapshot errors occur (ORA-12008, ORA-12057), THEN run Automatic refresh for the individual snapshot listed in the log file to attempt to correct the problem.
   -- Sometimes the next Data Collections set will error on a different snapshot. IF this occurs, THEN run Automatic refresh for ALL Snapshots to resolve the issue.
4. An ORA-12008 or ORA-12057 may be followed by a rollback error (ORA-1555, ORA-30036).
   A lot of rollback is required for large data sets. Try adding more space to the rollback
   OF IF rollback (undo) space is already very large (>= 20 GB), and running Automatic or Complete Refresh for ALL Snapshots fails, THEN run the Refresh Snapshots for EACH snapshot individually using Automatic Refresh Note 266797.1 may also be helpful with information about how to overcome these errors and setting up rollback.
5. This request can be useful in controlling the growth of the MLOG$ Snapshot Logs that are maintained on these snapshots. Please review Note 209571.1 MLOG Management
6. For more information on the latest Data Collections patches please review Note 223026.1 List of High Priority Patches for the APS Suite .

List of Snapshots

The following SQL will reveal the list of snapshots that are available in the release on the system. This list changes with each release or may change depending on the level of code in the release.

11.5.10 listing as an example:

Snapshot Names
PO_ACCEPTANCES_SN
PO_CHANGE_REQUESTS_SN
WIP_WOPR_RESS_SN
AHL_SCH_MTLS_SN
BOM_SUB_COMPS_SN
MTL_RESERVATIONS_SN
BOM_BOMS_SN
BOM_CTO_ORDER_DMD_SN
BOM_INV_COMPS_SN
BOM_OPR_NETWORKS_SN
BOM_OPR_RESS_SN
BOM_OPR_RTNS_SN
BOM_OPR_SEQS_SN
BOM_RES_CHNGS_SN
BOM_SUB_OPR_RESS_SN
MRP_FORECAST_DATES_SN
MRP_FORECAST_DSGN_SN
MRP_FORECAST_ITEMS_SN
MRP_SCHD_DATES_SN
MTL_DEMAND_SN
MTL_MTRX_TMP_SN
MTL_OH_QTYS_SN
MTL_SUPPLY_SN
MTL_SYS_ITEMS_SN
MTL_U_DEMAND_SN
MTL_U_SUPPLY_SN
OE_ODR_LINES_SN
PO_SI_CAPA_SN
WIP_DSCR_JOBS_SN
WIP_FLOW_SCHDS_SN
WIP_REPT_ITEMS_SN
WIP_REPT_SCHDS_SN
WIP_WLINES_SN
WIP_WOPRS_SN
WIP_WREQ_OPRS_SN

References

Note 207644.1 - Data Collections is Failing - All Errors - First Diagnostic StepsNote 209571.1 - MLOG ManagementNote 220115.1 - Managing MSCD and MSCX Tablespaces for APS Implementations - (Data Collections Sizing)Note 223026.1 - List of High Priority Patches for the Advanced Planning & Scheduling SuiteNote 266797.1 - Rollback Segment Assignment and Automatic Undo Management Mode for MRP and APS Applications ORA-01562 ORA-01555

Errors

ORA-12008 error in materialized view refresh pathORA-1655 unable to extend cluster e by for tablespace ORA-12057 materialized view "%s"."%s" is INVALID and must complete rORA-1562 "failed to extend rollback segment (id = %s)"ORA-1651 unable to extend save undo segment by in tablespace ORA-1555 "snapshot too old (rollback segment too small)"ORA-1652 "unable to extend temp segment by %s in tablespace %s"ORA-1653 unable to extend table string.string by # in tablespace stringORA-30036 unable to extend segment by %s in undo tablespace '%s'ORA-1654 unable to extend index by for tablespace