Home
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: disaster recover from RMAN backup

Li Li

2007-06-15

Replies:
Yes, I did the same thing to avoid the hassle :)

On 6/15/07, fmhabash <fmhabash@gmail.com> wrote:
Li Li wrote:
> Just want to give you all an update in case you run into the same
> problem. The problem here is the database was created by RMAN
> duplicate, so the dbid for the read only files are still the original
> dbid.
>
> On 6/13/07, *Li Li* <litanli@gmail.com <mailto: litanli@gmail.com>> wrote:
>
>     Hi, List,
>
>     I am testing a disaster recovery senario. RMAN backup was done
>     with no catalog. Below are what I did:
>
>     1. startup nomount
>     2. restore spfile from xxx
>     3. shutdown
>     4. startup (this time it picks up the restored spfile)
>     5. restore controlfile from xxx
>     6. alter database mount
>     7. restore database check readonly (I have 2 read only tablespaces)
>     8. recover database until logseq 5 (log seq 4 was the last
>     archivelog backed up by rman)
>
>     everything worked fine until step 8, I got an error on step 8
>     until follows:
>
>     ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get
>     error below
>     ORA-01122: database file 9 failed verification check
>     ORA-01110: data file 9: 'H:\xxx\xxx\xxx.dbf'
>     ORA-01206: file is not part of this database - wrong database id
>
>     file 9 is one of the READ ONLY tablespaces.
>     Any comment on what's wrong in here?
>
>     TIA,
>     -Li
>
>
>
>
Yes, this is the intended behavior. As you know, you can take a RO
tablespace across resetlogs but not across a duplicate. I came across
this scenario as you did and the options are you either imp/exp the
tablespace or use transportable tablespace option. To avoid this hassle,
I now check the target DB looking for RO tablespaces and change them to
RW (check to see if you can do that). I then backup them up, then do my
cloning. This way I do not have to worry about this issue.