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

how can you protect read-only indexes?

2005-03-03       - By Khedr, Waleed

Reply:     1     2     3     4     5     6     7     8     9     10     >>  

You need to configure accounts and security differently.
Don't give owner id to developers.

Waleed

-- --Original Message-- --
From: Carmen Rusu [mailto:carmen.rusu@(protected)]=20
Sent: Thursday, March 03, 2005 11:03 AM
To: oracle-l@(protected)
Cc: Carmen Rusu
Subject: how can you protect read-only indexes?


Oracle EE 9.2.0.4 64 bit
SunOS 5.8 64bit
data warehouse db ~100gb right now, growing every month
no partitioning yet

Just verified that you can drop an index when its underlying tablespace
is in read-only mode.

It happened when an ETL job ran second time, by mistake. The
corresponding tables, also on read-only tablespaces, survived ok the
truncate op.

So, what can I do to foolproof my ETL, so that the indexes  are not
dropped by mistake next time?=20

Thanks,
-Carmen Rusu
Oracle DBA

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l