DSXchange

Yes you were right it was a data type mismatch.

I was pulling in a job parameter as the start value within the surrogate key stage. It seems the supplied start parameter needs to be a string.

I am encountering the following warning message:-

APT_CombinedOperatorController,1: Failure parsing the init expression X+part; the default value of 0 will be used.

but the job produces the expected output.

Any ideas what the warning relates to?

Guys,
you were right, we have exceeded the unix limit for subdirectories.

Can this limit be increased or is it fixed?

Tried the rebuild index command but still get the same error.

When trying to save a job the following message is encountered
'cannot open executable job file RT_CONFIG6311'

Any ideas?

If a hashed file is converted to 64-bit do all the DS jobs that access the file need recompiling.

Also are there performance implications of using 64-bit hashed files.

Yes i am using automatic mode.

I will change the job to use SQL*Loader instead.

Thanks for your help.

When encountering oracle error
'ORA-01653: unable to extend table VAM_OWNER.ASAT_ARECVBL by 3200 in tablespace ASA_DATA_LM_50M using the oracle bulkloader stage the stage nor the job aborts.

Is there a way to ensure that the job aborts if the above oracle error message is encountered.

Thanks Ray.

We are trying to import 2000 job designs using DS manager and then compile them.
It is taking 5 hours to complete the import and 2 hours to compile them.
The jobs already exist in the target project but are being updated with new versions.

Is there any way i can speed up the process.

i imported the old project into a new project.
This resolved the problem.

If this happens again i will use the 'LIST.ITEM VOC 'job number' command as suggested.

Is there a TCL command that will tidy up a corrupted job.

I ran DS.TOOLS and rebuilt the indicies and it resolved the problem.

Thank for your help.

I have tried rebooting and the error still occurs.
Also in designer there are two versions of the job; not sure why.

DS version is 7.5.1.

I created a copy version of the job and created another RT_CONFIG1521 file based on the RT_CONFIG file associated with the copy version.

This allowed me to delete the sequence job.

It is affecting all clients.