topic Re: oracle extproc program:ORA-28575 in Operating System - OpenVMS

oracle extproc program:ORA-28575

ora_lion — Mon, 12 May 2008 07:06:59 GMT

database: oracle 10g
i try to execute my package which uses external procedure;
my procedure:
conn test/test
create or replace library libc_1 as '$1$DGA3:[BENBHM.USERS.LK]test.olb'
/
create or replace package test_utl
as
function test return pls_integer;
end test_utl;
/
create or replace package body test_utl
as
function test return pls_integer
is
external
library libc_1
name "test"
language C;
end test_utl;
/

my listener.ora
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = $22$dkb0:[oracle])
(PROGRAM = extproc)
)
)

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = masic2)(PORT = 1521))
)
)

CALLOUT_LISTENER =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = IPC)
(KEY = aa)
)
)

SID_LIST_CALLOUT_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = aa)
(ORACLE_HOME = $22$dkb0:[oracle])
(PROGRAM = extproc)
)
)
tnsnames.ora
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = aa))
)
(CONNECT_DATA =
(SID = aa)
(PRESENTATION = RO)
)
)
the two Listeners start successfully.
When i try to execute my package which uses external procedure calls i get this ORA-28575 error.
SQL> conn test/test
Connected.
SQL> select test_utl.test from dual;
select test_utl.test from dual
*
ERROR at line 1:
ORA-28575: unable to open RPC connection to external procedure agent

i try this on windows,i can work.

Re: oracle extproc program:ORA-28575

ora_lion — Mon, 12 May 2008 07:09:03 GMT

When i try to execute my package which uses external procedure calls i get this ORA-28575 error.------on openvms

Re: oracle extproc program:ORA-28575

Ruslan R. Laishev — Fri, 30 May 2008 06:46:45 GMT

Hello!

create or replace library libc_1 as '$1$DGA3:[BENBHM.USERS.LK]test.olb'

.OLB ? :-)

Re: oracle extproc program:ORA-28575

Hein van den Heuvel — Fri, 30 May 2008 10:54:03 GMT

Ah yes, I missed this entry earlier.
Ruslan is right about the .olb observation.
The library should be an shareable executable typically called .EXE and created uning 'lnproc' ?

Of course you can be 'cute' and call the EXE file .olb, but that just spells trouble.

Cheers,
Hein.