...

• Finds any Load table objects without an associated Load script and attempts to generate a load script for it using the template assigned in the c4 script. 
• Troubleshooting: Look at the RedCli logs in C:\ProgramData\WhereScape\Work, these will give you the most detail for any given failure. You can also see what command were sent in  each batch by looking for the batch json file in the work directory of the script.
• If you do get failures then, after correcting the underlying configuration problem, subsequent reruns will only pickup failed items or items not yet generated.

...

1_Source_Reports

2_Migrate_Current_Objects

...

Post Migration

Review any stand-alone scripts, such as High Water Mark scripts, these may have specific code in them that calls the old metadata repository directly and/or the legacy callable routines. Additionally the script output protocol of the Azkaban Scheduler is different and the script may need to be updated to conform.

Review stand-alone procedures and blocks, if these operated on the old metadata connection then they will have been retargeted during migration, these should be reviewed to see if they still work as expected. 

...

RUN EITHER c2 OR c3 OR BOTH:

...

long running script, consider running via the scheduled job.

You can run either c2 or c3 or both depending on your Scheduler environments.

...

RUN EITHER c2 OR c3 OR BOTH:

Generates Linux Action Scripts for all objects via RedCli Batch.

...

Long running script, consider running via the scheduled job.

You can run either c2 or c3 or both depending on your Scheduler environments.

...

OPTIONAL: Generates Load/Update routines for all objects.

...