RMAN full database restoration

Hi All,
I'm doing a test of rman backup. I took full backup of my database (controle file, datafiles and archivelog file). I dropped my database from dbca GUI.
Can i restore my full backup from RMAN in this case. I mean i want to restore my full backup, wht should i do. Should i create new database in the same name of my old database and recover from rman like in export utility or not. What is the issue. Note that i didn't backed up redolofile, password file and parameter file and they are already removed when i dropped the database from DBCA.
If any one have an idea in this case. Note that i took also export full backup if no issue from RMAN i'll restore it from export backup.
Thanks for your help
regards
raitsarevo

And tell us OS and database version (RMAN 8i is not the same as RMAN 9i,10g,11g,...).
Dropping the database through DBCA is not the same as losing it through media failure, that means RMAN can't do the whole work. It does not recreate oratab entries (Unix/Linux) or services (Windows). Delete through DBCA will also remove entries from the sqlnet configuration files, RMAN is not aware of this.
Werner

Similar Messages

RMAN Full Database restore cross platforms

All
I have a database 10.2.0.3 running on Solaris 10 OS.
I have performed a full back up (level 0) of this database using rman utility with auto back up on. I am trying to worl on a scenario where I could restore this backup on another linux machine. so I copied over all the backup pieces into the target linux server. from a local RDBMS installation (10.2.0.3) on the linux machine I am trying to restore the database... but not successful yet..
when I issue restore spfile or restore control file from +<backup file name>+; the prompt continues to search in some location is responding back saying no back up piece found.. below is the sequece of step I am trying ..
1 set up env on the linux server
2 rman target /
(instance not started but rman allows connection)
3 set DBID=+<DB ID of the source database running on Solaris>+
it executes set dbid=
4 startup nomount
as the pfile/spfile is not available under $ORACLE_HOME/dbs on linux machine it picks up default pfile however but the instance stars no mount..
5 restore spfile from '/u01/app/oracle/product/10.2.0/rman_bkp/c-300009955'
here it is not able to restore any thing.same is the case with control file.
Any ideas please advice
Sarat

Sarat Chandra C wrote:
Thanks for the referance. I now understand that I may not be able to use transportable database command to transport the entire db. However there is a line in the +"Restrictions on Cross-Platform Transportable Database"+ which says +"The principal restriction on cross-platform transportable database is that the source and destination platform must share the same endian format. For example, while you can transport a database from Microsoft Windows to Linux for x86 (both little-endian), or from HP-UX to AIX (both big-endian), you cannot transport a whole database from HP_UX to Linux for x86 using this feature. You can, however, create a new database on a destination platform manually, and transport needed tablespaces from the source database using cross-platform transportable tablespace as described in "Cross-Platform Tranportable Tablespace: CONVERT DATAFILE or TABLESPACE"."+
I understand if we are ready to transport every tablespace from Source to Target individually, may then be able to replicate a transportable database. Does the transportable tablespace do not have any restrictions like the transport database has got in respect to Platforms and Endian? Please clarify.
Also is there a support matrix for thr transportable database and tablespaces which we could refer to ?
Regards!
SaratSarat,
The same restriction that is there for the transport of the whole database lies completely true for the transportable tablespace as well if you are going for the cross platform. Endian must match across the platforms than only you can do this otherwise, as like the database feature, you need to convert the source file to the target endian.
If you look at the reference doc for the Trasnport Tablespace command,
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta063.htm#RCMRF1919
This restriction is documented there besides other restrictions
>
Restrictions and Usage Notes
The limitations on creating transportable tablespace sets described in Oracle Database Administrator's Guide apply to transporting tablespaces from backup, with the exception of the requirement to make the tablespaces read-only.
TRANSPORT TABLESPACE does not perform endian format conversion. If the target platform has a different endian format, then you must use the RMAN CONVERT command to perform the separate step of converting the endian format of the datafiles in the transportable set.
>
HTH
Aman....

ORA-12560: TNS Protocol adapter error after full database restore.

Good afternoon,
Following the steps given in page 9-32 of the 2 Day DBA document, after doing a full database restore, the home page shows:
NOTE: all of the output shown in this post is obtained directly from the host not a client. AND all using ENTERPRISE MANAGER.
1. The database instance is down
2. The listener is up
3. Agent Connection to Instance has status of Failed, followed by ORA12505: TNS: listener does not currently know of SID in connect descriptor (DBD ERROR: OCIServerAttach)
When I try to connect as sysdba using SQL Plus, I get the output shown below:
0 18:14 [Oracle] [13G] [2,031M] E:\Oracle\product\11.2.0\dbhome_1\NETWORK\ADMIN>
tnsping dbca
TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 30-AUG-2
010 18:14:36
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
E:\Oracle\product\11.2.0\dbhome_1\network\admin\sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
(HOST = orahost.john.local)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = dbca.
john.local)))
OK (50 msec)
0 18:14 [Oracle] [13G] [2,050M] E:\Oracle\product\11.2.0\dbhome_1\NETWORK\ADMIN>
sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Mon Aug 30 18:17:53 2010
Copyright (c) 1982, 2010, Oracle. All rights reserved.
SQL> connect
Enter user-name: sys as sysdba
Enter password:
ERROR:
ORA-12560: TNS:protocol adapter error
SQL>All I did was perform a full database restore in the same database, the simplest case. Any ideas as to why I can no longer connect ?
Thank you very much for your help,
John.
Edited by: 440bx - 11gR2 on Aug 30, 2010 6:58 PM - added Using Enterprise Manager.

I don't know what else I could have done given the behavior of the service.You can avoid problems like this in the future by avoiding Windows & using any approved *NIX Operating System.
No such "service" or daemon exist on any *NIX OS.

Full database restore and recovery

Hi all,
All my datafiles are corrupted.
I have a incremental level 0 backup
can i restore and recover the db with this backup?
regards,
prem

we went for a point in time recovery
while restoring we received the following error.
Full Database restoration failed with error
ORACLE error from target database:
ORA-00600: internal error code, arguments: [2103], [0], [0], [1], [900], [], [], []
ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 5157
ORA-06512: at line 1
released channel: GMUP1
released channel: GMUP2
released channel: GMUP3
Please help us in this regard

Parrallelization of RMAN Full Database Backup Confusion

Hi,
I am running Oracle 10gR2 on Solaris 5.10 on sparc machine having 16 CPUs.
I am using following RMAN script to take full database backup:
#!/bin/bash
ORACLE_HOME=/u01/app/oracle/product/10g
PATH=$ORACLE_HOME/bin:$PATH
ORACLE_SID=mtcedwp
export ORACLE_HOME ORACLE_SID PATH
rman target / <<EOF
run
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 8;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
ALLOCATE CHANNEL d1 DEVICE TYPE DISK;
ALLOCATE CHANNEL d2 DEVICE TYPE DISK;
ALLOCATE CHANNEL d3 DEVICE TYPE DISK;
ALLOCATE CHANNEL d4 DEVICE TYPE DISK;
ALLOCATE CHANNEL d5 DEVICE TYPE DISK;
ALLOCATE CHANNEL d6 DEVICE TYPE DISK;
ALLOCATE CHANNEL d7 DEVICE TYPE DISK;
ALLOCATE CHANNEL d8 DEVICE TYPE DISK;
BACKUP TAG ATHEER_FULL_DB DATABASE FORMAT '/u01/BACKUPS/WEEKLY_DB_BACKUP/backup_%U';
CROSSCHECK BACKUPSET;
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
RELEASE CHANNEL d1;
RELEASE CHANNEL d2;
RELEASE CHANNEL d3;
RELEASE CHANNEL d4;
RELEASE CHANNEL d5;
RELEASE CHANNEL d6;
RELEASE CHANNEL d7;
RELEASE CHANNEL d8;
EOFWill the above script take the 8-way parrallel backup? or do I need to configure location for every channel separately?
regards

This channel can be allocated manually or can be pre-configured by using
automatic channel allocation.
The number of allocated channels determines the maximum degree of
parallelism that is used during backup restore or recovery. For example if
you allocate 8 channels for a backup operation 8 background processes for the
operation can run concurrently.
Parallelism of backup sets allocates multiple channels and assigns
files to specific channels. You can configure parallel backups by setting a
PARALLELISM option of the CONFIGURE command to a value greater than 1 or by
manually allocating multiple channels.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1012864

RMAN full DB restore on New Host

Hi There,
My RMAN full backup script is like this:
RMAN> CONNECT TARGET *
CONNECT CATALOG *
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=db1,OB2BARLIST=Off-site,OB2BARHOSTNAME=db1.blah.tr)';
backup incremental level 0
format 'Off-site<db1_%s:%t:%p>.dbf'
cumulative
database;
backup
format 'Off-site<db1_%s:%t:%p>.dbf'
archivelog all;
backup
format 'Off-site<db1_%s:%t:%p>.dbf'
current controlfile;
EXITCan you help writing a full restore/recover script...
Thanks
Edited by: user642423 on Jan 24, 2009 11:11 PM

I want to restore to a New Host and the above script will not work for me...
Doing this procedure "http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#i1007814" I get an error like this:
PS: I've set "maxdays 30" but again same "no autobackup found or specified handle is not a valid copy or piece" error...
channel dev_0: looking for autobackup on day: 20090125
channel dev_0: looking for autobackup on day: 20090124
channel dev_0: looking for autobackup on day: 20090123
channel dev_0: looking for autobackup on day: 20090122
channel dev_0: looking for autobackup on day: 20090121
channel dev_0: looking for autobackup on day: 20090120
channel dev_0: looking for autobackup on day: 20090119
channel dev_0: no autobackup in 7 days found
released channel: dev_0
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/25/2009 00:27:00
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece

Full database restoration

Hi All,
I am facing with typical problem with one of my db server.One db server has crashed for some hardware reason.OS is linux.
But there was no backup with that server.Database version is 11G.I have only physical files of database.Now I have both windows server and linux box with 11G.
So is there any process for create the new database with that datafiles with same data.
Please help.
Thanks a lot in advance.
piku

Hi,
Good news. You can open then,
1. you have to create an init.ora (indicate your control_files) -> Do you know how you can? if not, I can explain for you
2. startup mount
3. select name from v$datafile -- to find out database files's orginal location in control file
4. if possible, move dbf files to orginal location, if not, rename them -> Do you know how you can? if not, I can explain for you
5. alter database open
also you should create a password file.
Regards

Blockrecover but full datafile restore + ORA-01193

Hi,
We have a proplem, here is a short sescription:
We have corrupt blocks, how can we solve this problem? Blockrecover uses full datafile restore and finally fails with ORA-01193.
Here is a detailed description:
We have a 330GB datafile (bigfile tablespace) with 46 corrupt block.
DB version 10.2.0.4, Oracle linux, we use ASM.
We would repair these blocks.
V$DATABASE_BLOCK_CORRUPTION after "backup validate check logical datafile 7" :
FILE#     BLOCK#     BLOCKS     CORRUPTION_CHANGE#     CORRUPTION_TYPE
7     16872378     1     0     FRACTURED
7     16872408     40     0     CORRUPT
7     16872379     5     0     CORRUPT
The result is similar by dbv.
We have archivelog mode and backupset created by rman command:
backup as compressed backupset incremental level 0 database;
All of the corrupted blocks are in 1 LOB segment.
We copied the LOB segment, only 5 record cannot be read.
The corrupted LOB segment (and table) was exchanged by the copied (not corrupted) data, so users can work.
We remained the corrupted LOB segment in the database, but it is not in use.
I started blockrecovery by command:
BLOCKRECOVER DATAFILE 7 BLOCK 16872378,...,16872447;
The listed blocks are same as in the V$DATABASE_BLOCK_CORRUPTION, so the command could be:
BLOCKRECOVER CORRUPTION LIST;
The database was opened during blockrecocer and the datafile 7 was online.
A line appeared in the V$SESSION_LONGOPS with:
"RMAN: full datafile restore"
The restore was more than 4 hours, and finally it is failed with error:
Starting blockrecover at 29-AUG-12
starting media recovery
ORA-01193 file % is not the same file seen at start of recovery
Based on V$SESSTAT there were lot of physical read but only some physical write.
Maybe full datafile read, and only corrupted blocks was changed, but I didn't check it exactly.
We retried blockrecover with only one block, but the result was same: it failed after 4 hours with ORA-01193.
We retried the blockrecovery on a mounted but not opened database, and the datafile was offline:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE DATAFILE 7 offline
BLOCKRECOVER ...
The result was same: it failed after 4 hours with ORA-01193.
rman backup failed with error:
RMAN : ORA-19566: exceeded limit of 0 corrupt blocks for file %
After set maxcorrupt, rman backup ran successfuly
SET MAXCORRUPT FOR DATAFILE 7 TO 46;
Based on our current info, these workaround seems best for us:
- rman "set maxcorrupt"
- DB_BLOCK_CHECKING=FULL
- drop corrupted (but copied and not used segment)
- wait until corrupted blocks will be reallocated (checking it periodically by dbv)
- set maxcorrupt to 0
Our questions are:
*1. Why oracle uses "RMAN: full datafile restore" during blockrecover?*
Why needed to read the whole datafile?
One of the advantage of blockrecover should be the relative small IO, and fast restore.
I found only 2 results in google for "blockrecover" and "RMAN: full datafile restore".
(One of the findings was in this forum, but it was no answer for our problem)
*2. ORA-01193: file is not the same, but why?*
It is strange on opened database and online datafile, because other advantage of blockrecover should be the online recovery.
But it is more-more strange on closed(mounted) database and offline datafile. Only the rman blockrecover could change this file.
I found only 3 results in google for "blockrecover" "ORA-01193"
I found only the oerr output in google for "ORA-01193". But what does it mean? Only the rman blockrecover could change this file.
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
Action: Ensure the correct file is available, then retry recovery.
*3. What else can be do to repair these corrupt blocks? What can we do for success blockrecover, or is there any other idea?*
Other infos:
- DB_BLOCK_CHECKING was false, but we changed it to FULL to avoid the subsequent corruptions
ALTER SYSTEM SET DB_BLOCK_CHECKING = FULL scope=both
- DBMS_REPAIR cannot detect the (out-of-line) LOB segment errors.
- rman SET MAXCORRUPT is not a "calming" solution
- When I read on internet, when we drop the corrupted LOB segments, the blocks will remains corrupt.
And the block will be repaired/formatted only when a new segment will allocate these blocks.
Based on metalink 336133.1, we can ensure the new allocation by fill the datafile with dummy data until the corrupted blocks will be allocated.
But this is a very IO intensive task.
- full recovery
very IO intensive, we try to avoid it.
Thx: lados.

Hi,
other infos:
We use ASM, and one of the disk is dropped and added after the last full (incremental level 0) backup. Can this premise causes the slow restore (something physical storage info is changed), or the ORA-01193 error (file % is not the same file seen at start of recovery) ? I don't think that a full db backup is needed after ASM disk drop/add/rebalance. But we tried a full backup (this was when the corrupt block first appeared with ORA-19566).
I found only one finding in the metalink for ORA-01193. The oerr reference (cause,action). It would be strange, if nobady else had problem with this error.
Thx: lados.

Database restore trouble

Hi, All.
We have a backup maked on DB2 8.1.14 32-bit/Windows 2003 <b>x64 </b>
We try to redirect restore this backup under DB2 8.1.14 32-bit/Windows 2003
<b>32-bit, </b> but it's failed with message :
"SQL0902C A system error (reason code = "") occurred. Subsequent SQL
statements cannot be processed. SQLSTATE=58005"
db2diag.log :
2007-05-31-10.36.12.687000+240 I5715632H395 LEVEL: Event
PID : 5524 TID : 5280 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000 DB : B04
APPHDL : 0-71 APPID: *LOCAL.DB2B04.070531111434
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:20
CHANGE : CFG DB B04: "Util_heap_sz" From: "5000" To: "131072"
2007-05-31-10.36.12.765000+240 I5716029H370 LEVEL: Warning
PID : 5524 TID : 4184 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000 DB : B04
APPHDL : 0-98 APPID: *LOCAL.DB2B04.070531112015
FUNCTION: DB2 UDB, relation data serv, sqlrr_db_init, probe:100
MESSAGE : DB2_IMPLICIT_UNICODE enabled
2007-05-31-10.36.12.781000+240 I5716401H323 LEVEL: Warning
PID : 5524 TID : 1140 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluMCReadMediaHeaderFromDevice,
probe:139
MESSAGE : Transfer buffer size was changed from 0 to 786432
2007-05-31-10.36.12.781000+240 I5716726H414 LEVEL: Warning
PID : 5524 TID : 4184 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000 DB : B04
APPHDL : 0-98 APPID: *LOCAL.DB2B04.070531112015
FUNCTION: DB2 UDB, database utilities, sqludPrintStartingMsg, probe:1
DATA #1 : String, 50 bytes
Starting a full database restore.
Agent PID: 4184
2007-05-31-10.36.12.812000+240 I5717142H390 LEVEL: Warning
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqludProcessHistoryFile,
probe:24DATA #1 : String, 107 bytes
An empty database history has been detected.
The database history will be overwritten by the backup image.
2007-05-31-10.36.12.859000+240 I5717534H569 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbGetFileSystemInfo, probe:5
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 30 bytes
Could not get file system info
DATA #2 : Pointer, 4 bytes
0x01fae9f0
DATA #3 : Pointer, 4 bytes
0x0271dea4
DATA #4 : Bitmask, 4 bytes
0x00000180
2007-05-31-10.36.12.859000+240 I5718105H458 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services,
sqlbCopyStoragePathsFromDiskCB, probe:20
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 29 bytes
Error copying paths from disk
2007-05-31-10.36.12.859000+240 I5718565H540 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadStorageGroupEntry,
probe:30
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 38 bytes
Error reading from storage group files
DATA #2 : signed integer, 8 bytes
0
DATA #3 : Pointer, 4 bytes
0x0271e380
2007-05-31-10.36.12.859000+240 I5719107H569 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbGetFileSystemInfo, probe:5
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 30 bytes
Could not get file system info
DATA #2 : Pointer, 4 bytes
0x01fae9f0
DATA #3 : Pointer, 4 bytes
0x0271de78
DATA #4 : Bitmask, 4 bytes
0x00000180
2007-05-31-10.36.12.859000+240 I5719678H458 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services,
sqlbCopyStoragePathsFromDiskCB, probe:20
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 29 bytes
Error copying paths from disk
2007-05-31-10.36.12.859000+240 I5720138H540 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadStorageGroupEntry,
probe:30
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 38 bytes
Error reading from storage group files
DATA #2 : signed integer, 8 bytes
0
DATA #3 : Pointer, 4 bytes
0x0271e37c
2007-05-31-10.36.12.859000+240 I5720680H575 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadStorageGroup, probe:20
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 38 bytes
Error reading from storage group files
DATA #2 : signed integer, 8 bytes
0
DATA #3 : Pointer, 4 bytes
0x01fae8e0
DATA #4 : Pointer, 4 bytes
0x027900b0
2007-05-31-10.36.12.859000+240 I5721257H542 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadStorageGroupTable,
probe:20
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 38 bytes
Failed to read the storage group table
DATA #2 : Pointer, 4 bytes
0x027900b0
DATA #3 : Pointer, 4 bytes
0x01fae8e0
2007-05-31-10.36.12.875000+240 I5721801H588 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupTable,
probe:20
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 44 bytes
Failed to initialize the storage group table
DATA #2 : Pointer, 4 bytes
0x027900b0
DATA #3 : Pointer, 4 bytes
0x02794608
DATA #4 : Pointer, 4 bytes
0x026b4a78
2007-05-31-10.36.12.875000+240 I5722391H600 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, buffer pool services,
sqlbProcessStorageGroupRestore, probe:20
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic error
detected"
DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 51 bytes
Error occurred while processing storage group files
DATA #2 : Pointer, 4 bytes
0x026b4a78
DATA #3 : Pointer, 4 bytes
0x026dbc00
DATA #4 : unsigned integer, 4 bytes
0
2007-05-31-10.36.12.875000+240 E5722993H390 LEVEL: Severe
PID : 5524 TID : 3352 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000
FUNCTION: DB2 UDB, database utilities, sqludProcessSGRestore,
probe:4191RETCODE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error
detected"
DIA8501C A buffer pool logic error has occurred.
2007-05-31-10.36.12.875000+240 I5723385H355 LEVEL: Severe
PID : 5524 TID : 4184 PROC : db2syscs.exe
INSTANCE: DB2B04 NODE : 000 DB : B04
APPHDL : 0-98 APPID: *LOCAL.DB2B04.070531112015
FUNCTION: DB2 UDB, database utilities, sqludrsa, probe:110
MESSAGE : Restore Terminated.
Can anybody comment this situation ?
Thanks!

Hi,
Please let me know patch level
db2level
Regards
Ben

9i Database - Restore to a new host, validating RMAN backup

Hi all,
I could use your help, for any of you who remember how to do this in 9i. On one of my production databases, running 9.2.0.6.0, I have a nightly RMAN script that writes the backup to a large shared drive (this is on a Windows 2003 server). This backup uses a recovery catalog.
I have a test server, and I want to try and restore last night's backup on this test server, without touching the recovery catalog - purely as a means to go through the recovery process, and to validate our backups (this is also for SOX compliance, as this database is for the financial system).
I have been looking through the 9i documentation, and was hoping to have some detailed steps here: http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrecov.htm#1007514
but I don't see a lot of information there.
I believe that this should be a rather simple process. On the test server, I have installed the 9.2.0.6 software, and created the Oracle Service using the same name as production. The test server can also see the shared drive that houses the backup files from the production system.
Here are the steps I am trying, please let me know what I need to change. Thanks all!!
rman target / nocatalog
RMAN> set DBID 3679803977
RMAN> startup nomount
RMAN> restore controlfile from autobackup; --- this throws errors, see below
Starting restore at 11-NOV-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20081111
channel ORA_DISK_1: looking for autobackup on day: 20081110
channel ORA_DISK_1: looking for autobackup on day: 20081109
channel ORA_DISK_1: looking for autobackup on day: 20081108
channel ORA_DISK_1: looking for autobackup on day: 20081107
channel ORA_DISK_1: looking for autobackup on day: 20081106
channel ORA_DISK_1: looking for autobackup on day: 20081105
channel ORA_DISK_1: no autobackup in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/11/2008 16:43:18
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece

Many thanks for the helpful replies so far, Hemant!! I had to shelve this issue for a few days, back at it today.
I have made some progress, I am able to restore the control file now - what I am doing, is copying the autobackup controlfile from the network drive over onto the server locally (E:\oracle\ora92\database\BACKUPCONTROL.ORA), then I am able to restore the controlfile with this:
restore controlfile from 'E:\oracle\ora92\database\BACKUPCONTROL.ORA';
And I can see that it restores all 3 of my controlfiles.
The next step would be to do the database restore. When I issue the "restore database;" command, I can see that it lists out all of the datafiles that it needs to restore from the backup set, but then after about a minute, I see these error messages pop up:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/19/2008 10:55:54
ORA-19587: error occurred reading 0 bytes at block number 1
ORA-27091: skgfqio: unable to queue I/O
ORA-27067: skgfdisp: size of buffer is invalid
OSD-04026: Invalid parameter passed.
When I looked up those last 2 error codes on Metalink, I see document ID 213858.1 that looks like this normally happens when the backup piece that has Read-Only permissions. I have confirmed that the backup files on the network drive are not Read-Only, I have full Read/Write privileges on them. So once again, I am stumped.
Any thoughts? I might go ahead and log an SR for this, to try and get it resolved.
Thanks!

Restore a single table from full database backup

Hi,
I have a full database (10.2.0.1) backup with RMAN.
Suddenly a table got truncated. How to get back that table without restoring and recovering the full database (Point in time recovery) since if I restore the database to an earlier time then the other transactions will hamper.
Also creating a standby database and import export the table will solve my problem. But is there any other way to restore the lost table.
Thanks in advance.

No other way to restore the data if you don't want do point in time recovery. If you drop the table then you can restore it from the recyclebin but for the truncate operation it won't help. If you have enabled the flash back table for that particular table then you can restore the data for only that table.
Regards
Asif Kabir

What order are Archive logs restored in when RMAN recover database issued

Ok, you have a run block that has restored your level-0 RMAN backup.
Your base datafiles are down on disc.
You are about to start recovery to point in time, lets say until this morning at 07:00am.
run { set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
recover database;
So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
required and starts to restore the archive logs. All as expected and works.
My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
Any inputs on experience welcome. I am now drilling into the documentation for any references there.
Thanks

Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
This is from interpreting the list backup of archivelog commands.
Backupset = 122672
==============
Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
Backupset = 122677
==============
Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
Thanks for inputs. Answers some questions.

Full database backup and restore

I have a doubt on the syntax for a full database backup and restore. For a single schema, the syntax for backup & restore is :-
exp JISPREPCORBILLINGPRD501/JISPREPCORBILLINGPRD501 owner=JISPREPCORBILLINGPRD501 STATISTICS=none
log=JISPREPCORBILLINGPRD501_exp.log grants=y constraints=Y rows=y compress=N
file=JISPREPCORBILLINGPRD501
imp <userid/password> file=<export dump file location> fromuser=<export user name> touser=<import user name>
grants=y constraints=Y rows=y log=<import log file location>
I hope, my question is clear.
Please, help in solving the doubt.
regards

hi,
thanks, for your answer. I took a export of one schema of the database. But, when I tried to import the schema to the destination database, it showed
imported with errors with the existence of functions showing. The commands used by me for export and import are as follows:-
exp JISPREPCORBILLINGPRD501/JISPREPCORBILLINGPRD501 owner=JISPREPCORBILLINGPRD501 STATISTICS=none log=JISPREPCORBILLINGPRD501_exp.log grants=y constraints=Y rows=y compress=N file=JISPREPCORBILLINGPRD501
imp JISPREPCORBILLINGPRD501/JISPREPCORBILLINGPRD501 file=JISPREPCORBILLINGPRD501 fromuser=JISPREPCORBILLINGPRD501 touser=JISPREPCORBILLINGPRD501 grants=y constraints=Y rows=y log=JISPREPCORBILLINGPRD501_imp.log
Do, we need to drop the existing schema before importing or somethinig else. Please, help.
regards

Backup/Restore a full Database VM Manager Repository (3.1.1)

Dear All,
My Oracle VM Manager is connect to Oracle Database 11g Standard Release 2. I want to backup and Restore from a full Database VM Manager Repository.
Especially, please kindly give recommend on parameter (Yes/NO) or other clearly.
Thanks and regards,
Vandy

[root@ ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)
[root@~]# uname -a
Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
The firewall is already disabled. Is that the OS is not comnpatible.
But I read in the Oracle VM documents, that the Oracle VM is compatible for RHEL 5.5 and above.....

Urgent -- need to restore table from full database backup

Hello,
Can somebody tell me the process for restoring just a table from a full database backup?
I did a full online database backup yesterday, and one of my tables got ruined today. I need to restore it as soon as possible, but I don't know how. When I tried flashback tables, it said that feature wasn't enabled. Should I restore the datafile or the tablespace?
Thanks much,
Nora

If you only want to recover the table and not the other objects in the tablespace, and assuming the table was damaged by a user statement (and not, say, block corruption), you would need to recover your backup to a different system, export the table that was damaged, and import the table into your real production database. If you can recover the entire tablespace to an earlier point in time, or if you can lose some committed changes to other database objects, you may have other options.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

RMAN full database restoration

Similar Messages

Maybe you are looking for