Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error ORA-20002 executing Oracle 7.3 remote stored procedure

714 views
Skip to first unread message

Santiago_Orozco

unread,
Jan 14, 2002, 5:14:29 AM1/14/02
to
Hi,

I get error ORA-20002 when executing a stored procedure in a remote Oracle
7.3 database (through a datalink). I know this is caused by the
odessp()function of the Oracle Call Interface (OCI) API which is called by
the Powerbuilder Oracle driver (PBO73050.DLL) to describe the parameters of
a PL/SQL procedure or function stored in an Oracle database. The error is
explained in the Oracle documentation:

-20002: A database link was specified in objnam, either explicitly or by
means of a synonym.

My code is as follows:

String sMyParam
...
lValue = SQLCA.MY_REMOTE_PROCEDURE(sMyParam);

My question is if there is a way to execute a stored procedure avoiding
the describe phase of the statement, being the programmer who define the
number and type of the parameters of the procedure.

Best regards and thanks in advance,

Santiago Orozco

Terry Dykstra

unread,
Jan 14, 2002, 1:11:34 PM1/14/02
to
Dbparm staticbind = 1 turns off the describe. But I'm not sure if that
works with dblinks as well.

NB: ORA-20002 is a user-defined error number

--
Terry Dykstra (TeamSybase)
Please state PB / OS / DB versions in your post.
MySybase http://my.sybase.com/mysybase
Search Deja: http://www.pfcguide.com/_newsgroups/search.asp

<Santiago_Orozco> wrote in message
news:20CBB72FB00929120038421685256B41.0038422B85256B41@webforums...

Santiago_Orozco

unread,
Jan 15, 2002, 5:49:24 AM1/15/02
to
Thank Terry.

I had ran with staticbind = 1 but it follows giving the same error.
Do you know another solution for this problem?

The version of PowerBuilder is 5.0.03
Oracle7 Server Release 7.3.4.2.0
driver to access Oracle7 PBO73050.DLL
Oracle client is 2.3.4.0.0
in the client is Windows NT Workstation

Terry Dykstra

unread,
Jan 16, 2002, 4:36:51 PM1/16/02
to
I've found a case in the Infobase which states this was fixed in PB7.
PB5004 & PB6.5 have the same behavior as you see.
As a workaround you might be able to create a procedure in the local
database which in turn then calls the procedure in the remote database.
You should really consider upgrading. PB5 hasn't been supported for a long
time now. Oracle 734 is also no longer supported by Oracle.

--
Terry Dykstra (TeamSybase)
Please state PB / OS / DB versions in your post.
MySybase http://my.sybase.com/mysybase
Search Deja: http://www.pfcguide.com/_newsgroups/search.asp

<Santiago_Orozco> wrote in message
news:B363B471399E3E02003B746585256B42.003BF69885256B41@webforums...

0 new messages