List_Plan[=output-file]

    Specifies that Oracle RMU should generate a plan file and write
    it to the specified output file. A plan file is a text file that
    contains all the qualifiers specified on the RMU Load command
    line. In addition, it specifies the executor names (if you are
    performing a parallel load operation), the directory for the .ruj
    files, the exception files, and the file created by the Place_
    Only qualifier (if specified).

    Oracle RMU validates the Oracle RMU command prior to generating
    the plan file to ensure that an invalid plan file is not created.
    (This is true regardless of whether or not you specify the
    Noexecute qualifier.) For example, the following command is
    invalid and returns an error message because it specifies
    conflicting qualifiers (Corresponding and Fields):

    $ RMU/LOAD/RECORD_DEF=FILE=NAMES.RRD/CORRESPONDING -
    _$ /FIELDS=(LAST_NAME, FIRST_NAME)/LIST_PLAN=my_plan.plan -
    _$ MF_PERSONNEL.RDB EMPLOYEES NAMES.UNL
    %RMU-F-CONFLSWIT, conflicting options CORRESPONDING and FIELDS...

    See the description of the Execute qualifier for a description
    of what items are included when Oracle RMU validates the RMU
    Load command. See the Examples section for a complete example and
    description of a plan file.

    You can use the generated plan as a starting point for building a
    load operation that is tuned for your particular configuration.
    The output file can be customized and then used with subsequent
    load operations as the parameter to the RMU Load Plan command.
    See Load Plan for details.

    If you want to create only a load plan file and do not want
    to execute the load plan when the RMU Load command is issued,
    specify the Noexecute qualifier. When you specify the Noexecute
    qualifier, you must specify a valid Oracle RMU command.

    One way to prototype a plan file prior to creating a potentially
    very large .unl file is to specify the List_Plan qualifier and
    the Noexecute qualifier along with a valid record definition
    (.rrd) file and an empty .unl file on the RMU Load command
    line. The .rrd file contains the information Oracle RMU needs
    to perform the validation of the plan file; however, because data
    is not loaded when you specify the Noexecute qualifier, Oracle
    RMU does not attempt to load the .unl file. Note, however, that
    you cannot specify the Fields qualifier when using this strategy.
    (When you specify the Fields qualifier, Oracle RMU checks to make
    sure the number of columns specified with the Fields qualifier
    match the number of columns specified in the .unl file.)

    If you do not specify a file extension, the default file
    extension for the plan file is .plan.