All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

Re: Calling a package over a database link

Nigel Thomas


Did you get errors 2 and 3 the right way round?
Version 3 is 'obviously' wrong - as it refers to database link @remote_database which you haven't got; this seems to be the message you've given as #2. PL/SQL can't dereference a variable to be a DB link name (just the same as it can't dereference a variable to be a table name, except by building it into the dynamic SQL string).
Version 2 looks identical to version 1 (except for the use of dynamic SQL). I'm guessing that PL/SQL buggers up the (valid) SQL in some way. I can't try it here right now - with luck someone else will solve that for you ...

----- Original Message ----
From: "Lawie, Duncan" <duncan.lawie@credit-suisse.com>
To: oracle-l@freelists.org
Sent: Monday, September 25, 2006 3:09:11 PM
Subject: Calling a package over a database link


I have a piece of code which works fine if I hard code my remote database name, but which fails badly if I try to make the remote database a variable.  Is there a variation on this concept which works, or do I need to find another approach altogether.


remote_database varchar2(100);
v_sql varchar2(1000);

remote_database := 'FRED';
v_sql := 'manage_remote_partitions.grant_tablespace_access@' || remote_database ||' ( ''DCL_ARC'', ''CCDATA'' )';

-- 1
manage_remote_partitions.grant_tablespace_access@FRED('DCL_ARC', 'CCDATA' );
-- 2
execute immediate v_sql;
manage_remote_partitions.grant_tablespace_access@remote_database('DCL_ARC', 'CCDATA' );


Version 1 works.

Version 2 gives me
ERROR at line 14:
ORA-06550: line 14, column 1:
PLS-00352: Unable to access another database 'REMOTE_DATABASE'
ORA-06550: line 14, column 1:
PLS-00201: identifier 'OGB_MANAGE_REMOTE_PARTITIONS@REMOTE_DATABASE' must be declared
ORA-06550: line 14, column 1:
PL/SQL: Statement ignored

Version 3 gives me
ERROR at line 1:
ORA-00900: invalid SQL statement
ORA-06512: at line 11


Duncan Lawie
DBE - Oracle
020 788 3 9229

"There will always be plenty of things to compute in the detailed affairs of millions of people doing complicated things."  -- Vannevar Bush, As We May Think; Atlantic Monthly - July 1945.

Please access the attached hyperlink for an important electronic communications disclaimer: