error in view data

Renita · Post by **Renita** » Tue Sep 09, 2008 10:58 pm

Hi,

I am on datastage Server edition 7.5.1 on AIX server.
I am connecting to an oracle database via a DRS stage.
The map runs fine, however when i try to view data. I get the following line or error message

Error calling subroutine: DSD.Browse (Action=3); check DataStage is set up correctly in project PORU02

Data Source is Empty

Error calling subroutine: DSD.Browse (Action=2); check DataStage is set up correctly in project PORU02
(The connection is broken (81002))

Finally I have to close the client to connect to the same job again.

The maps run fine and I am able to import table definitions etc.
I only have a problem with view data!

Awaiting a reply.

Thanks in advance!

Renita

chulett · Post by **chulett** » Tue Sep 09, 2008 11:13 pm

What happens if you use an OCI stage instead?

ps. It's not called a 'map' in this world.

Renita · Post by **Renita** » Wed Sep 10, 2008 12:27 am

Hi chulett,

I agree !! But who would convince the developers!!

I would have to go and change jobs from development to Production for that. Any idea with DRS instead?

Thanks,
Renita

Hemant_Kulkarni · Post by **Hemant_Kulkarni** » Wed Sep 10, 2008 4:02 am

Try to put in a "where" condition to limit the number of rows and see if the error still appears.

Hemant_Kulkarni · Post by **Hemant_Kulkarni** » Wed Sep 10, 2008 4:02 am

Try to put in a "where" condition to limit the number of rows and see if the error still appears.

chulett · Post by **chulett** » Wed Sep 10, 2008 7:21 am

I was thinking of the OCI stage as an experiment. How is the DRS set - to Oracle or ODBC? Is this a source or target stage? Do you have problems with any other job accessing Oracle or is it literally just this one?

Renita · Post by **Renita** » Wed Sep 10, 2008 8:15 pm

Hi Chulett,

I have this issue with all jobs using the Oracle database. The database is set to Oracle.

This problem persists on other projects also on the same datastage server.

Also the problem exists for database stages that are source or target stages.

Thanks,
Renita

Renita · Post by **Renita** » Wed Sep 10, 2008 8:16 pm

Hi Hemant,

The issue exists even after using the while condition. Actually the stage cannot even fetch 3 rows or data and errors out before that.

Thanks,
Renita

chulett · Post by **chulett** » Wed Sep 10, 2008 8:26 pm

Ok, it doesn't sound like you have configured DataStage for Oracle yet. There are specific changes you need to make to your dsenv file that are documented in the configuration guides. Have you done so? Do you have an Oracle client installed on the DataStage server?

Renita · Post by **Renita** » Wed Sep 10, 2008 8:29 pm

Hi Chulett,

I have finished the configuration related to Oracle. The dsenv has been setup correctly all all environment variables are set.

The maps run successfully, hence the server can connect to the database. The outputs also are correct.

However the problem is only with the view data via the database stage.

Thanks,
Renita

chulett · Post by **chulett** » Wed Sep 10, 2008 8:36 pm

Ok. Is your connection information parameterized? Do those parameters reference environment variables? Does the view data work if those values are hard-coded in the stage?

Renita · Post by **Renita** » Wed Sep 10, 2008 11:26 pm

Hi Chulett,

When I need to view data i explicitely provide the database name,user id and password. It does not refer to any variable for the id or password.

Thanks,
Renita

chulett · Post by **chulett** » Thu Sep 11, 2008 7:10 am

Meaning your instance name, userid and password are hard-coded in the stage?

Renita · Post by **Renita** » Thu Sep 11, 2008 8:24 pm

Hi Chulett,

I hardcode the user id and password just to view the data cause I cannot use $PROJDEF when i view the data.

Thanks,
Renita

Renita · Post by **Renita** » Thu Sep 11, 2008 8:26 pm

Hi,

I got the solution for this issue. Its a bug in DS version 7x with DRS stage and Oracle database which has been fixed in version 8. If I use database type to ODBC and view data I can view data.

Thanks for all your help.

Renita