Errors while viewing data through Teradata Enterprise Stage

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
gsherry1
Charter Member
Charter Member
Posts: 173
Joined: Fri Jun 17, 2005 8:31 am
Location: Canada

Errors while viewing data through Teradata Enterprise Stage

Post by gsherry1 »

Hello Forum,

I get the following Error messages while attempting to view data from client in the Teradata Enterprise stage:
#E TCOS 000005 09:55:01(004) <main_program> Invalid identifier: $
>##E TCOS 000048 09:55:01(005) <main_program> Parameter not resolvable:
##W TCOS 000049 09:55:01(017) <main_program> Parameter specified but not used in flow: _TDDB1
##W TCOS 000049 09:55:01(018) <main_program> Parameter specified but not used in flow: _TDPwd1
##W TCOS 000049 09:55:01(019) <main_program> Parameter specified but not used in flow: _TDUserId1
##W TCOS 000049 09:55:01(020) <main_program> Parameter specified but not used in flow: _TDPID
>##E TCOS 000020 09:55:01(023) <main_program> Parameterization Error: Parameterization failed.
However, the program runs fine and selects data from these stages with no warnings.

My read method is user defined sql with parameter references and Connection settings is using the DB Options with $ parameter references. The parameters shown in the warnings are the ones specified in the connection settings, but in the warnings it has replaced the $ with an _.

Any suggestions?

Thanks,

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

Post by ray.wurlod »

Does your stage include a non-well-formed reference to a job parameter (for example not enclosed in "#" characters)?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
gsherry1
Charter Member
Charter Member
Posts: 173
Joined: Fri Jun 17, 2005 8:31 am
Location: Canada

Post by gsherry1 »

I believe them to be all well formed, and all references have # # around them.

All options where set with 'Insert Job Parameter' option to prevent typos. The only exception was the following setting:
user=#$TDUserId1#,password='#$TDPwd1#',RequestedSessions=4
This one was partially generated by DS and then I appended the RequestedSessions setting.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Looks reasonable. At the risk of running in sequential mode, does it generate the warnings if you only use the built parameters? Can you post the message from the job log where the "$" characters have been converted to "_"? I haven't got a chance to investigate this this week but am beginning to suspect a bug in the stage's View Data function.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vinaymanchinila
Premium Member
Premium Member
Posts: 353
Joined: Wed Apr 06, 2005 8:45 am

Post by vinaymanchinila »

Hi,
I am getting the same error, even though the parameters are all correct !

Error executing View Data command:

##E TCOS 000005 10:52:03(000) <main_program> Invalid identifier: $

##E TCOS 000005 10:52:03(000) <main_program> Invalid identifier: $
##E TCOS 000048 10:52:03(001) <main_program> Parameter not resolvable:
##E TCOS 000005 10:52:03(025) <main_program> Invalid identifier: $
##E TCOS 000048 10:52:03(026) <main_program> Parameter not resolvable:
##E TCOS 000020 10:52:03(049) <main_program> Parameterization error: Parameterization failed..

Was it a bug? I dont get the issue if I dont use TD Enterprise stage and use a TD API stage.

Thanks,
Thanks,
Vinay
bobyon
Premium Member
Premium Member
Posts: 200
Joined: Tue Mar 02, 2004 10:25 am
Location: Salisbury, NC

Post by bobyon »

Ray,

I too suspect a bug. I just experienced the same behaviour. View data presented almost identical errors, but when actually running the job, it runs fine.
Bob
Post Reply