来自oracle metalink，通过它来了解MRP运行一些功能与原理，尤其MRP执行Snapshots前后过程。
有时系统在运行此处被卡住。[@more@]
ECHNICAL OVERVIEW
I. Standard Planning Engine.
1. Exploder.
- Explodes through BOMs and ECOs.
- Determines low level codes.
- Identifies end assemblies.
2. Snapshot Workers.
- Snapshots item and transaction system data.
- Deletes snapshot data from previous planning run.
3. Planner, Planner Workers.
- Performs gross-to-net explosion.
- Deletes planning data from previous planning run.
- All processes are in the critical path.
- Each process "deletes, generates and loads".
II. Memory-Based Planning Engine.
1. The Exploder process is eliminated. These tasks are handled within the
snapshot.
2. Other than item information, the DELETE and LOAD tasks are removed
from the critical path.
3. DELETE and LOAD tasks are handled by separate processes.
4. MBP Concurrent processes.
- MRCNSP: Memory-Based Snapshot
- MRCMON: Snapshot Monitor
- MRCNSW: Memory Based Snapshot Worker
- MRCSDW: Snapshot Delete Worker
- MRCSLD: Loader Worker
- MRCNEW: Memory Based Planner
- MRCPDW: Planner Delete Worker
a. Memory-Based Snapshot.
- Writes a file containing the list of planned items. No
other snapshot task can begin until this file is written.
- Performs pre-processing tasks.
- Launches the Snapshot Monitor.
- Performs MB Snapshot Worker tasks after writing the file
containing the list of items.
b. Snapshot Monitor.
- Launches and controls remaining snapshot processes.
- Maintains list of snapshot and delete tasks.
- Uses inter-process communication to communicate with spawned
worker processes (database pipe).
c. Memory Based Snapshot Worker.
- Spawned by the Snapshot Monitor.
- Writes snapshot data to flat files.
- Snapshot Monitor assigns snapshot tasks to workers until all
tasks are complete.
- MRP:Snapshot Workers:
- If zero: none of these workers is spawned.
- If one or greater: corresponding number of workers is spawned.
d. Snapshot Delete Worker.
- Spawned by the Snapshot Monitor.
- Deletes snapshot and planning data from previous planning run.
- Number of workers spawned is determined by the site-level profile
MRP:Snapshot Workers. If this profile is set to zero, this
process runs single-threaded.
e. Loader Worker.
- Spawned by the Snapshot Monitor and MBP.
- Invokes SQL*Loader to load data written to flat files into
the database.
- One loader worker spawned per database table to be loaded.
- MRP:Use Direct Load Option:
- Yes: uses SQL*Loader direct path load.
- No : uses SQL*Loader conventional path load.
- Direct path load is faster, but requires exclusive locks
on the table (and its indexes) being loaded.
f. Memory Based Planner.
- Spawned by the Snapshot Monitor.
- Loads flat files written by snapshot workers into memory.
- Performs gross-to-net explosion.
- Is a single-threaded process.
- May launch Loader Workers if number of records to load exceeds
10,000.
g. Planner Delete Worker.
- Spawned by the MB Planner only when run without the snapshot.
- Planner Delete Worker is a single-threaded process.
- Deletes planning data from the previous planning run.
421
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
