Change capture not working in 7.5.3

sunayan_pal · Post by **sunayan_pal** » Wed Jul 09, 2008 6:05 am

HI All,

Can anyone confirm why Change capture stage is not working in the Datastage EE 7.5.3
initially the same job was working fine at version 7.5.1.A

I tried a few work around

1. by changing the following enviornment variable
$APT_DISABLE_COMBINATION = TRUE

2. Increase the number of node by 1 to the existing Configuration.apt file

it works.
but why it happen and how the above work around work . even i am surprise.
can anyone confirm what is the best way to resolve ?

regards
Sunayan

mahadev.v · Post by **mahadev.v** » Wed Jul 09, 2008 7:41 am

Without posting the error message you will not get any answer. Copy paste the exact error message you got here.

keshav0307 · Post by **keshav0307** » Wed Jul 09, 2008 7:15 pm

what do you mean by not working? do you mean job is not running?

tell us what is you are expecting from the job and what it is doing?

sunayan_pal · Post by **sunayan_pal** » Fri Jul 11, 2008 6:40 am

Hi All,

the problem with that job was once i run the job it is not generating any log .
basically it took 3 minutes to complete.
but even after 120 minutes also no job log and job still in running stage.
once i click to STOP then only the job start generating the log and will abort.
this is what i mean that CC stage is not working.

OddJob · Post by **OddJob** » Fri Jul 11, 2008 8:02 am

Do you have two DB stages on your job that read and write to the same table?

keshav0307 · Post by **keshav0307** » Sat Jul 12, 2008 1:59 am

you should tell us the job design, what are the stages you have etc.

what is the data volume? what is the job monitor size? etc need to be considered

xinhuang66 · Post by **xinhuang66** » Sat Jul 12, 2008 5:29 am

sunayan_pal wrote:Hi All,

the problem with that job was once i run the job it is not generating any log .
basically it took 3 minutes to complete.
but even after 120 minutes also no job log and job still in running stage.
once i click to STOP then only the job start generating the log and will abort.
this is what i mean that CC stage is not working.

Based on what I experienced recently, even if the job log might stop somewhere before change capture information, it doesn't mean change capture is not working .

Usually, it is your job caused DB lock, I suggest you can do a test when the job is running forever, you can try to look at table job operates, see if you can find some locks on the table