How To Retrieve Memory Based Planner (MBP) Dat Files

Profile MSC: Write MBP Flat Files = Yes - set at User or Site Level
Profile MSC: File Flush Limit = 1
When to Use These Profiles
We recommend that these profiles be the setup as the default setting at the Site
Level.
IF profiles are not set, then they must be setup and the plan must be re-run wit
h this setting if an error occurs during the Memory Based Planner OR the Plan ou
tput seen in the Planners workbench needs to be investigated.
Why Use These Profiles
This allows Development to run the plan at Oracle using the customer data and de
bug the output.
This is accomplished by generating INPUT files as well as the standard OUTPUT fi
les that are always generated when a plan is run
MSC: File Flush Limit = 1 will generate the proper control (.CTL) files to check
and debug the output of the plan files
When using the profile MSC: Write MBP flat files = Yes, the OUTPUT files will ov
erwrite files generated by previous run of the same plan.
This can benefit DBA s when managing the file system.
How does this help manage the file system?
The output files can be very large and if the profile = No, then every time the
plan is run, we generate unique files and these can use up file system space rap
idly for large plans.
See Note 336724.1 for more info on managing MBP flat files
What The Profile Does On the System
When the profile is setup and the plan is run, the process writes to 2 (or 3*) d
irectories under $APPLCSF/out
data<plan_id>/mbpoutput
data<plan_id>/mbpinput
data<plan_id>/hls_data < * only for Constrained or Optimized plans See 6. How To P
roduce and Retrieve the HLS Data Files>
examples:
/u01/aps/applmgr/apscomn/admin/out/data7761/mbpoutput/MSLD_ ITEM_SUPPLIERS.dat
/u01/aps/applmgr/apscomn/admin/out/data7761/mbpinput/MSLD_ FULL_PEGGING.dat
In the mbpoutput directory there are over 100 files written, and it is not unusu
al for large plans to see this directory create a ZIP file over 100 MB
In the mbpinput directory less files are written and the overall size is almost
always much smaller in size when ZIPped.
1. How to Find the MBP DAT Files
Standard Steps:
Go to the directory $APPLCSF/out/data<plan_id>
You can see this directory in the log file of the Memory Based Planner Log file,
Near the top of the file, the directory is shown just after the ARGUMENTS sectio
n of the log file
Log file example
MSONEW module: Memory Based Planner
+---------------------------------------------------------------------------+
Current system time is 25-JUN-2010 13:19:53
+---------------------------------------------------------------------------+
===================================================================
Debug Mode : Disabled
Output to Terminal : No
Argument Method : Database Fetch
Trace Mode : Disabled
===================================================================

Argument 1 (PLAN_ID) = 7761

Argument 2 (SNAPSHOT_REQ_ID) = 3609183
Argument 3 (BATCH_PROCESS) = 1
Argument 4 (IN_PIPE) =
Argument 5 (OUT_PIPE) =
===================================================================
/u01/aps/applmgr/apscomn/admin/out/data7761/ is already there or cannot be opene
d
mbp input/output directory existing.. check it out
mbp flat file dir /u01/aps/applmgr/apscomn/admin/out/data7761/
2. How to Gather the Files and ZIP
Flash Viewlet available - click to download a visual guide the retrieving compre
ssing and zipping these files
Hint: Use the Pause key at the bottom of the viewlet screen to study the screen
shots as required.
Sign into Unix (or Linux) as applmgr user
We HIGHLY recommend you use ZIP and do NOT use tar or compress or gzip
ZIP compresses better than tar, compress or gzip
Oracle patches are delivered in ZIP format, so this is available on the system.
cd $APPLCSF/out/data<plan_id>
Example using Plan_id from the log file example above
[applmgr@aps ~]$ cd $APPLCSF/out/data7761
[applmgr@aps data7761]$ pwd
this matches directory see in the log
/u01/aps/applmgr/apscomn/admin/out/data7761
file
ZIP the files using the following command (Use zip, not gzip or compress for bes
t results!!)
Small Plans Create a single file for small plans use
zip -r $HOME/data<plan_id> *
Example:
[applmgr@aps data7761]$ zip -r $HOME/data7761 *
Larger Plans - Multiple files for larger plans, Create separate ZIP files for MB
PINPUT and MBPOUTPUT directories. And for Constrained plans, also get the HLS Da
t files (ref #6 below for more information)
Example:
zip -r $HOME/data7761output . -i /mbpoutput/*
zip -r $HOME/data7761input . -i /mbpinput/*
zip -r $HOME/data7761hls . -i /hls_data/* <Only for Constrained Plans>
See the files under the applmgr $HOME directory
example:
[applmgr@aps ~]$ cd $HOME
[applmgr@aps ~]$ ls -ltr data7761*
Single File example for smaller plans
-rw-r--r-- 1 applmgr dba 599621 Feb 23 07:35 data7761.zip
Multiple files example for larger plans
-rw-r--r-- 1 applmgr dba 123511911 Feb 23 07:36 data7761mbpoutput.zip
-rw-r--r-- 1 applmgr dba 54248452 Feb 23 07:41 data7761mbpinput.zip
-rw-r--r-- 1 applmgr dba 12292587 Feb 23 08:00 data7761hls_data.zip
FTP the files to your local machine and then upload to the SR in My Oracle Suppo
rt
We routinely receive files as large 200+ MB via My Oracle Support, so it may tak
e time to upload to the SR, but this allows Support and Dev to have the files av
ailable until the SR is closed.
Sometimes it may be necessary to upload the files to the Oracle FTP site, but th
is is NOT a good idea as the files are removed from the site after just a few da
ys. As a last resort if My Oracle Support is not uploading the files, Reference

Note 549180.1 - How to access Oracle's SFTP server - to get instructions to uplo
ad to the FTP site