DSXchange

Basically We are reading a flat file and the culpret column is coming with null values which is actually a not null column in target and using transformer stage I am trying to load into Teradata table using Mload , but it is again and again failing with 3604 error message (Cannot place a null value ...

Hi All,
I am not able to find if there is an environment variable to insert single space to a field in case incoming data is NULL while loading to a Teradata table.

I am aware that this we can achieve with Oracle DB using APT_ORACLE_PRESERVE_BLANKS, but not sure how to achive in teradata

Any help

Thanks Ray, By the way I just want to let all know that the issue has been fixed now, also the caused because the hashed file was larger than 2 GB hence we Applied RESIZE command to change the hash file size from 32 to 64. also we contacted IBM for the issue where they suggested below solution. but ...

Apologies for posting the issue in rush, and yes this issue is related to server job , not PX , and also I have searched similar post in the dsxchange and found info about DS_RESENU. can anyone help me to fix this issue?, and also let me know what is causing the same. Few more details The job is rea...

Hi All, Could you please help me understanding if there is any harm in replacing DS_RESENU from other project? we are facing some issue where our job is failing because of below error and want to replace DS_RESENU from other project in PRODUCTION environemnt, because it looks like that it corrupted?...

I believe it should never get hung or get locked because of it.

Hi Kumar , thanks for the kind input on this , however I just wanted to know whether this will cause datstage jobs being HUNG/LOCKED or not?

Hi There,

What happens actually if we do not Clear & PH& logs & RT_LOG at regular intervals or if we dont clear the unwanted logs in scratch disk.

Can it cause datstage jobs being HUNG or LOCKED?


thanks in advance for kind input on this.

Akumar

I am not a premium member

Hi All,

APT_TSORT_STRESS_BLOCKSIZE environment variable can be used only when you have a sort stage used in your job design with restrict memory option selected.

Is this right?



Thank you very much in adv for your reply on this.

Regards,
A kumar

Which NLS you are using, are you getting the error while exporting the metadata defination?

Please give some more input.

As you are saying that same job is running fine in dev but not in prod. I wud suggest you to run the same job in production with less number of records e.g. 100 records , this is just to identify that where is the problem.

Stop the job, Try re-running the same job with less data, and see if you are getting the same issue.

chulett wrote:Perhaps APT_PM_PLAYER_TIMING set to True? ...

yes , its correct ...
$APT_PM_PLAYER_TIMING: (set to true)this reporting option lets you see what each operator in a job is doing, especially how much data they are handling and how much CPU they are consuming

parameterize that..