Commands for checking and repairing projects
You can check whether the design-time assets of a project are synchronized with its corresponding InfoSphere® DataStage® server project assets, and make repairs if necessary.
If the design-time assets for a project that are held in the metadata repository are out of step with the server project, then the server project, or assets within the server project, can become unusable.
You can use the SyncProject command to check for inconsistencies, and to repair inconsistencies if any are detected. You might use the command as part of your normal maintenance schedule to check for problems. If any problems are detected, use the command in repair mode to fix the problems. Alternatively, you can use the command interactively and be prompted if repair action is needed.
- Project missing in metadata repository
- This fault arises if a server project exists, but the corresponding project does not exist in the metadata repository. SyncProject attempts to repair the fault by removing the server project.
- Server project missing
- This fault arises if a project exists in the metadata repository, but the corresponding server project does not exist. SyncProject attempts to repair the fault by recreating the server project. If SyncProject succeeds in recreating the project, any jobs that the project contains must be recompiled.
- Server project files are corrupted
- The server project holds descriptions of project objects in files. If these files are corrupted, SyncProject attempts to resolve the issue by returning the corrupted project file to its initial state.
- Job or shared container missing from the metadata repository
- This fault arises if a server job or shared container exists, but the corresponding metadata repository job or shared container does not exist. SyncProject attempts to repair the fault by removing the server job or shared container.
- Server job or shared container missing
- This fault arises if a job or shared container exists in the metadata repository, but the corresponding server job or shared container does not exist. SyncProject attempts to repair the fault by recreating the server job or shared container. If SyncProject succeeds in recreating the job, it must be recompiled.
- Corrupted server engine job files
- This fault arises if the files in which the server engine defines an executable job and its state become corrupted. To recover a corrupted file, SyncProject recreates an empty file. As a consequence, the job might need to be recompiled and the job log history and current job status information might be lost.
- Incorrect server job or shared container folder
- This fault arises if a job or shared container is in a different folder on the server compared to the metadata repository. SyncProject attempts to repair the fault by updating the folder attribute of the job or shared container in the server project.
If the SyncProject command cannot repair a server project, you can use the SyncProject command to reconstruct the project from the metadata repository.