Re: Problems calling oracle stored procedures from powerbuilder

In article <79d6lb$glh_at_portal.gmu.edu>,   pyalaman_at_osf1.gmu.edu (Prasanti Yalamanchili) wrote:
>
> Hi all,
>
> I'm having strange problems while calling oracle stored procedures
> from Powerbuilder.
>
> The versions I'm using are:
>
> Powerbuilder 6.5
> Oracle 8.0.4
> Oracle 8 Client/SQL NET 8
>
> The problems goes like this.
>
> I have couple of stored procedures under a package.
>
> I have created a powerbuilder nonvisual object to call these
> stored procedures from powerbuilder.
>
> In each of my functions in the nonvisual object I'm using Declare,
> execute and fetch to execute and
> retrieve the data using these stored procedures.
>
> I have couple of problems here.
>
> 1. Even though I was given all the privileges to execute this procedure
> Powerbuilder complains that the object doesn't exist. For ex: all the
> procedures are owned by user X and user Y was given all privileges to
> execute these procedures. Now if user Y tries to call these stored
> procedures from a non visual object in powerbuilder using declare
> statement powerbuilder complains that user Y doesn't exist. If we
> connect to the database using user X and tries to compile it works.
>
> 2. The second problem I'm having is, if I use Oracle 8 drive that comes
> with Powerbuilder 6.5, it wont identify the packages. If I call a
> procedure with in a package it complains saying that package not found.
> we created all sorts of synonyms, privilieges etc.. The same code
> works fine if we use powerbuilder oracle 7.3 driver.
>
> If anyone has any ides regarding these problems please let me know.
>
> Thanks in advance.
>
> Prasanti..
>
>

When you use the PBOR860.DLL, you are forced to prefix calls to oracle stored procedures with the owner of the stored procedure name. You have to do this even if PUBLIC SYNONYMS exist for the stored procedures in the ORACLE database. SYBASE blames this on the ORACLE CLIENT version but I feel it is something to do the Powerbuilder Native driver itself. Also, upgrade to the Oracle client 8.0.5 as soon as possible and make sure you have the latest version of the PBOR860.DLL. That would fix some other serious problems associated with SQL statements that have multiple calls to Oracle functions like DECODE(), NVL(),etc.

Hope this helps,

Srinivasan V

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Thu Feb 18 1999 - 13:01:51 CST