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
doh! stupid datafiles

doh! stupid datafiles

2004-11-11       - By Charles Hart

Reply:     1     2     3     4     5     6  

If someone does not care enough to backup a database then I would
assume that it is not in archive log mode. Use this as a learning
experience.

It all depends on what the tablespace the datafiles are part of, if
they belong to a tablespace that has mostly indexes. I would build
scripts to rebuild the indexes and drop indexes (or whatever) in that
tablespace, drop tablespace. Then rebuild that tablespace and
indexes. Then bring any data over from production that was in this
tablespace (sql copy, export/import - whatever you are more
confortable with).

If the tablespace or tablespaces contained large amount of data, I
would probally use transportable tablespaces from production. If it
is a good fit.

Doing a clone from production is easy and depending on the size of
production, could be very fast.
--
http://www.freelists.org/webpage/oracle-l