DataStage Version Control Issue/Problem
Posted: Wed Nov 24, 2004 4:52 am
Hi,
We are having a sporadic problem with DataStage Version Control.
It manifests itself occasionally when a job is promoted. If the promoted job is then viewed, it can be a completely different job from that that was supposed to be promoted. It cannot always be fixed by promoting it again and we have had to create new jobs and copy them to get the desired result. This has happened when promoting into various environments (test/prod fix/prodution).
We have repaired the indices on the version project but not yet sure if that has fixed the problem or if it will reoccur.
Because of this, our main concern is we cannot rely on this for integrity of promoting into our production system without a lot of manual checking etc.
This has been logged with Ascential and is an open issue, however we would like to know if anybody else is experiencing this problem or has workarounds for this?
Does anybody else use any other version/source control/build systems? Are there good alternatives?
PS There has been suggestion here in house that it happens at times when the client is under pressure for resources. This is currently only one suggestion of a possibility.
regards,
B.
We are having a sporadic problem with DataStage Version Control.
It manifests itself occasionally when a job is promoted. If the promoted job is then viewed, it can be a completely different job from that that was supposed to be promoted. It cannot always be fixed by promoting it again and we have had to create new jobs and copy them to get the desired result. This has happened when promoting into various environments (test/prod fix/prodution).
We have repaired the indices on the version project but not yet sure if that has fixed the problem or if it will reoccur.
Because of this, our main concern is we cannot rely on this for integrity of promoting into our production system without a lot of manual checking etc.
This has been logged with Ascential and is an open issue, however we would like to know if anybody else is experiencing this problem or has workarounds for this?
Does anybody else use any other version/source control/build systems? Are there good alternatives?
PS There has been suggestion here in house that it happens at times when the client is under pressure for resources. This is currently only one suggestion of a possibility.
regards,
B.