DSXchange

Hi, The parallel job is not letting any data pass through the transformer. There are not constraints. There are no warnings in the director. I am completely lost. :? I read a post here regarding transformer issue between 8.5 and 9.1. But I am designing on 8.5 and running on 8.5 too. Regards, Samyam

Thanks Ray.

Will check this one out.

Hi Ray,

I am checking the uvodbc.config, I don't see any entry in it for the old server.
Do you still want me to configure it?

Regards,
Samyam

Hi All, I am trying to connect to a new Netezza database. There are two servers one old and one new. I am getting the below run time error when trying to run the job against the new server. "Could not connect to datasourceCommunication link failure" The old server is working as it was befo...

whats the error?

You can make the schemafile a parameter and make the invocation pass the value of the parameter.

You can read only the field you need using a cut command in UNIX.
replace '\n' with a ',' and write the sql into a .sql file.

in the DB stage use read SQL from file option.

Try
StringToTimestamp("0001-01-01 00:00:00","%yyyy-%mm-%dd %hh:%nn:%ss")

did you try creating a new job.
if this doesn't work. Then there is an issue for sure.

Do not do any partitioning any where till this logic is executed.
Just run this job on a single node APT config file.

For this logic to work the records have to be read into the transformer in the same order that you have shown in your initial post.

Yes like Craig mentioned.
check out this post


viewtopic.php?t=130373

One of the ways would be to.

read only the field you need using a cut command in UNIX.
replace '\n' with a ','.
pass this as a parameter to the job or sequence.

Have you tried a job with just a row generator writing into a dataset. then another job reading that dataset into a peek. Is this the only job that uses dataset in your project. what about other jobs. has this been happening only now or has it been happening from a long time.(begining of this datast...

Also keep an eye on other jobs that run between the time the read job was running fine and the read job started failing and check if any of the jobs are coruupting the dataset. and keep track of the activities on the server to check if any other process is corrupting the dataset.