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: how can you protect read-only indexes?

Khedr, Waleed


Read only has to do with dml, has nothing to do with ddl.


-----Original Message-----
From: jungwolf [mailto:spatenau@(protected)
Sent: Thursday, March 03, 2005 4:35 PM
To: Khedr, Waleed
Cc: oracle-l@(protected)
Subject: Re: how can you protect read-only indexes?

On Thu, 3 Mar 2005 14:52:15 -0500, Khedr, Waleed <Waleed.Khedr@(protected)>
> I know I'm not answering your question, but I have to say that you
> to fix the processes themselves that are causing these issues.
> Also why does the process drop the indexes if it failed truncating the
> table.
> You need to defined some dependencies and abort mechanisms.
> Regards,
> Waleed

Well, of course the process needs to be reconfigured but that's not
the point at all. The point is, why are objects in a readonly
tablespace vulnerable to being dropped? That's counterintuitive
behavior even if it does make sense after thinking about the
implementation. I think the original poster was asking if she can
make readonly tablespaces act with the expected behavior.

The best idea I've seen has been the trigger option from Juan. I
haven't looked at triggers at the DB level so I'm not sure how much
security it'll provide, but at least it holds promise. For example:
SQL> create trigger boo
before drop
on database
eERROR exception;
raise eerror;
2   3   4   5   6   7   8   9
Trigger created.

SQL> create table boojam (a number);

Table created.

SQL> drop table boojam;
drop table boojam
ERROR at line 1:
ORA-00604: error occurred at recursive SQL level 1
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at line 4

Just needs a lot of spiffing up.