Page 1 of 1

Unable to view data in input stage

Posted: Thu Dec 03, 2009 11:12 am
by pebbles
I receive the following error whenever I try to view data in an iput stage:

Error calling subroutine: DSD.Browse (Action=5); check DataStage is set up correctly in project pricing_dev
Warning: Data that exceeds the maximum display length has been truncated

Posted: Thu Dec 03, 2009 11:14 am
by pebbles
I need urgent help on this please

Posted: Thu Dec 03, 2009 11:37 am
by chulett
What 'input stage'? One in particular? Depends on the data?

Cut down your Display sizes to avoid the warning noted.

Re: Unable to view data in input stage

Posted: Thu Dec 03, 2009 11:39 am
by algfr
pebbles wrote:I receive the following error whenever I try to view data in an iput stage:

Error calling subroutine: DSD.Browse (Action=5); check DataStage is set up correctly in project pricing_dev
Warning: Data that exceeds the maximum display length has been truncated
Could you explain a bit more. Does this happen only with this dataset ?

By the way, it is a forum where people are volunteering so please do not be aggressive like that otherwise you risk getting no answer.

Posted: Thu Dec 03, 2009 12:28 pm
by pebbles
Yes.
Regardless of which stage (oracle, datasaet, DRS,etc) I still get this error when I try to view data.
This never happened before I introduced this particular job. Since then, I van't view data in any other job in the same project but I can view data from all jobs in the other projects.

Thanks

Posted: Thu Dec 03, 2009 1:58 pm
by sjfearnside
Are you connecting thru an ODBC driver? If so, check your odbc.ini and uvodbc.config settings.

Posted: Thu Dec 03, 2009 2:44 pm
by vinnz
Since you say this is "urgent" - Do you get the error only when viewing data or do you get it when you actually run the job as well? Do the display lengths defined on your input stage match the lengths defined in the database?

Posted: Thu Dec 03, 2009 2:54 pm
by pebbles
Please ignore my "urgent" comment. That's me bad.
The error also shows up when I try to run the job.
One hint though is that no errors show up when another ID is used to either view data or run the job.

Thanks
Pebbles

Posted: Fri Dec 04, 2009 3:05 am
by Sainath.Srinivasan
That appears to be permission problem.

What ID did you change ? OS or rdbms ?