.ora-code.com

Links
Home
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
PL/SQL unit MIA

PL/SQL unit MIA

2005-08-05       - By Billy Verreynne (JW)
Reply:     1     2     3     4     5     6     7     8  


rjamya [mailto:rjamya@(protected)] wrote:

> is there a privilege issue here?

Was thinking along those lines but do not see how. All the objects
(tables and PL/SQL units) belong to the same schema. The DBMS_JOB is
scheduled in that schema.

The data is subject to FGAC though, but the schema is excempt from it
(access policy). I have the PL/SQL stack logged at the time of the
error (have a custom rolled applog API that logs errors and PL/SQL
stacks) - this shows nothing unusual. The anon block (from DBMS_JOB)
calling the main procedure and it failing.

Anyway, have a hack in place to work around this (specified proc has
now been disabled as the data it creates is currently not used by the
web reporting front-end). Job runs fine without it.

Oh well, if you run into a wall, spray grafitti on it. ;-)

--
Billy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail and its contents are subject to the Telkom SA Limited
e-mail legal notice available at
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
http://www.freelists.org/webpage/oracle-l