Surrogate Key Stage Error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
cfuller
Premium Member
Premium Member
Posts: 70
Joined: Mon Mar 24, 2003 10:08 pm
Location: Australia

Surrogate Key Stage Error

Post by cfuller »

I have a job that has run successfully on my dev and uat servers, but is failing in Production. The error seems to be in the Surrogate key stage -
SK_Employer,0: Caught exception from runLocally(): APT_ParseError: Expected "," or "}", got: "*", line 1.
The stage is designed to get a sequence from an Oracle 11g database sequence, and the inputdata to the stage is partioned using the Hash algorithim, and is sortedusing unique on two keys.

Any assistance greatly appreciated.
Regards
Chris Fuller

"Reality is what refuses to go away when you stop believing in it"
BI-RMA
Premium Member
Premium Member
Posts: 463
Joined: Sun Nov 01, 2009 3:55 pm
Location: Hamburg

Post by BI-RMA »

Is the database sequence present on your production database? And has your Oracle-user sufficient privileges to access it? Somehow it looks like something goes wrong when parsing the SQL-statement used to retrieve the next value from the sequence.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
cfuller
Premium Member
Premium Member
Posts: 70
Joined: Mon Mar 24, 2003 10:08 pm
Location: Australia

Post by cfuller »

Hi Roland

Yes the sequence is present, and I have access to sequence to generate the next value...confirmed through Toad
Regards
Chris Fuller

"Reality is what refuses to go away when you stop believing in it"
cfuller
Premium Member
Premium Member
Posts: 70
Joined: Mon Mar 24, 2003 10:08 pm
Location: Australia

Post by cfuller »

I've worked around this problem for now by removing the Surrogate key stage and using the .NEXTVAL function to build the key...but i will chase this issue with IBM for a resolution.
Regards
Chris Fuller

"Reality is what refuses to go away when you stop believing in it"
cfuller
Premium Member
Premium Member
Posts: 70
Joined: Mon Mar 24, 2003 10:08 pm
Location: Australia

Post by cfuller »

The issue is that certain stages have issues with password containing '*'. The resolution is to ensure all password fields wrap the password in double-quotes to ensure the full password is passed back to the database system.

Traps for young players... :o
Regards
Chris Fuller

"Reality is what refuses to go away when you stop believing in it"
BI-RMA
Premium Member
Premium Member
Posts: 463
Joined: Sun Nov 01, 2009 3:55 pm
Location: Hamburg

Post by BI-RMA »

So there was an authentication problem after all... A bit difficult to track down, though. Thanks for sharing.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
Post Reply