DSXchange

Thanks Ray

Craig,

Can you please explain how this daemon (deadlock) works?

Thanks
Yamini

Even with NLS included, it did not take more than 2 hours, for us, to upgrade from 7.1 to 7.5

Vijay,

We have developed many jobs which update rows in a table and never received such warnings

Yamini
P.S. As Ray said may be our DBA did something in Oracle not to generate any messages

Hello Ray,

These are the vaules from dsdlockd.config file:

start=0
timer=900
res=0
log=

Can you please tell me how I can enable auto-start of the deadlock daemon? Also, when you said "every time the daemon wakes" do you mean that it wakes every time we restart the engine?

Thanks
Yamini

aakashmalu,

I tried the same thing and found out that it wont help in retrieving the data by entering a higher value to prefetch the rows

Yamini

Indrani,

If the DBA is not willing to switch off logging, you can ask him to increase the size of the log

Yamini

Naveen,

We got a similar error message when our Server was too busy to trigger a job. We did not face the problem after reducing the load on the server

Hope this helps
Yamini

Indrani,

Stopping the job depends on the current state of the job. If possible, try to kill the job from DataStage Director (Job==>Cleanup Resources)
If not, ask your DBA to release any locks on the table

Yamini

Indrani,

Place a Transformer also

Hash File ==>Transformer==>ODBC Stage

Yamini

PS I think you can use a query similar to this one in the ODBC Stage:

DELETE XYZ WHERE XYZ.Col1=:1

Indrani, I have designed a similar job sometime ago. In order to speed up the process, after reading the data from the table and doing the necessary transformations, I captured the primary key of the table in a hash file. In a different job I deleted the rows from the table based on the keys present...

Thanks for the info guys...

Hi Arnd,

Can you tell me where I can find a job's Basic code?

Thanks
Yamini

Hello there,

We got the same error when there were unwanted quotes present in the data. In our case we surpressed the quotes by using '000' as quote character and the problem was solved

Hope this helps
Yamini

Anil,

When you define the Stage variables assign them an initial value which wont appear in the input data

Yamini