Page History
...
- Each script will find any object which does not already have an assigned Action Processing Script and generate the script using the associated target connection's default templates.
- Runs in batches: due to the potentially large number of objects to process, the RedCli commands are run in batches and each batch is assessed for failures before continuing with the next batch.
- When running from the UI you can monitor the progress by clicking on the command window to view the progress and time remaining (shown above).
- When run through the scheduler the same progress messages are sent to audit log and can be viewed by refreshing the audit log in the RED Scheduler tab.
- It is common to get failures in these scripts the first few times you run them, especially with large repositories with many target connections, this is usually due to missing default templates on a target connection.
- 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 commands were sent in 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.
...
- 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 commands were sent in 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.
...