Text Load Set Planned Outputs

The system automatically creates four Planned Outputs for Text Load Sets:

• Text Loading Log File (.log). The system writes the job log into the log file.

• Text Loading Control File (.ctl) The system generates the SQL*Loader control file and writes the SQL*Loader options to this file. This is useful when you use bulk loading.

• Text Loading Error File (.err). The system writes each invalid record that got rejected while writing data into a target Table instance into this Planned Output.

• Text Loading Input Data File. If you set the Save Input File attribute to Yes, Oracle LSH uses a Planned Output as a placeholder for the input file saved as an output during execution. If you set Save Input File to No, the system still creates the Planned Output but does not create the actual output when you run the Load Set.

  If you upload a zipped file with Save as Input set to Yes, the system always saves it as TEXTLOAD.ZIP—it does not have its original name when saved.

  Setting Save as Input to Yes when you are loading multiple zipped files is especially useful when uploading data files with multiple date formats. If the date formats are the same, the Save as Input setting is immaterial. If the date formats vary, and the Save as Input option is set to Yes, the system uses the date format specified in each metadata file.

You can classify the Planned Output and view the actual output through the Oracle LSH Outputs user interface, subject to normal Oracle LSH security rules. To view the contents of the file, you must download it and view it through SAS.