@INROWNUM ?

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

What precise version of DataStage?
Please post the derivations of your columns, so we can attempt to reproduce the problem.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
DeepakCorning
Premium Member
Premium Member
Posts: 503
Joined: Wed Jun 29, 2005 8:14 am

Post by DeepakCorning »

Here are the columns --

6006.00000,945.00000,946.00000
6006.00000,946.00000,947.00000
6006.00000,947.00000,948.00000
6006.00000,948.00000,948.00000
6006.00000,949.00000,949.00000
6006.00000,950.00000,950.00000

First Column - Max value of a counter column in the DB
Second Column - If @INROWNUM = 1 Then (StageVariable1+1) Else (Second Column+ 1) (Gets Populated by a stage Variable which gets a value depending on if it is the first row or not - if it is first row it should get the Max value of a counter column in the DB - Right now this is not working as the @INROWNUM never gets a value as 1)
Third Column - @INROWNUM (starts from 2)

Hope this helps.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Can you post precisely what the input file looks like, and the exact derivations of the stage variables and output columns used?

I have been unable to reproduce this on version 7.5.1 on Red Hat Linux.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
sjhouse
Premium Member
Premium Member
Posts: 43
Joined: Tue Nov 02, 2004 12:11 pm
Location: Minneapolis, MN

Post by sjhouse »

Was a cause ever found?

We had the same thing happen in a job that has been running for a couple of years without any issue. We are running on AIX with DataStage server version 7.5.1 In the last run, it had an issue in which Inrownum was the same for 2 consecutive records.

Seq --> Transformer --> Oracle

We exported all of the jobs and the file to our test server. First, we took a piece of the sequential file (where the error occured) and ran this on the test environment and there was no error.

When run with the entire file (large file), we encountered the same error in the same place on the test server.

Stephen House
DeepakCorning
Premium Member
Premium Member
Posts: 503
Joined: Wed Jun 29, 2005 8:14 am

Post by DeepakCorning »

Nope, I did not find the reason but just know that it had something to with that particular "transformaer" stage. SO I shifted my logic to the a stage previous to this one. :(
kris_daredevil
Participant
Posts: 20
Joined: Mon Dec 05, 2005 8:07 pm
Contact:

Post by kris_daredevil »

As Craig said can you place the .dsx somewhere in this forum so that we can have a look at this wierd problem.
KRIS
kris_daredevil
Participant
Posts: 20
Joined: Mon Dec 05, 2005 8:07 pm
Contact:

Post by kris_daredevil »

As Craig said can you place the .dsx somewhere in this forum so that we can have a look at this wierd problem.
KRIS
DeepakCorning
Premium Member
Premium Member
Posts: 503
Joined: Wed Jun 29, 2005 8:14 am

Post by DeepakCorning »

If this question is to me then really sorry I can not and plus I have exported the job and imported in a different server and it works fine in there. But on this server in this project it does not. I think some setting has gone wrong and I am not able to make it correct. Also I have tried exporting the job in DSX and then deleting the job and then reimporting it in the Project but still square one.
DeepakCorning
Premium Member
Premium Member
Posts: 503
Joined: Wed Jun 29, 2005 8:14 am

Post by DeepakCorning »

Work Around = Shifted the processing to the previous stage and now the variable is working fine.
Post Reply