Database in archivelog

my database is in archivelog mode and i have a two database one is db01 which has alok1 tablespace and second is oemrep and i have a tablespace name alok1 and it has 3 tables in it i want to know that if i want to recover alok1 tablespace in second database named oemrep
how could i do it? can i recover that tablespace in hr schema??if yes will this show me those tables which is in alok1 tablespaces ..
please help me .....
thakns in advance ...

i have found in oem that u can back up and recovere the tablespace that's why i was trying it
you can recover tablespaces in the same database where they belonged.
1. what is rec catalog does,if i am using it
RMAN ( CATALOG CREATION ) STEP BY STEP by Joel Pérez
RMAN ( CATALOG CREATION ) STEP BY STEP by Joel Pérez
2. if i have two database db01 and oemrep both database almost have same tablespace in it will it create problem me to backup and recover..
you can not recover a tablespace in another database. Instead of that you can transport that tablespace with the export/import utilities.
3.what should i do if i have to backup db01 database and want to recover it in oemrep database.and
please let me know in detail how could i do that ???
you have to use the feature "Transportable Tablespaces"
On monday I am going to give the needed steps to do that.
Joel Pérez
http://otn.oracle.com/experts

Similar Messages

Problem running oracle 9i database in archivelog mode - database freezes

Greetings,
I recently needed to change a (test) database to archivelog mode to make online back-ups of this database. This posed no real problem although I seem to be unable to set the database to automatic archiving eventhough I edited the init.ora file (translation of the "archive log list" output between square brackets):
SQL> archive log list
Databaselogmodus Archiveermodus [Databaselogmode: Archivemode]
Automatisch archiveren Gedeactiveerd [Automatic archiving: Deactivated]
Archiveerbestemming O:\oracle\ora92\RDBMS [Archivedestionation: O:\oracle\ora92\RDBMS]
Oudste on-line logreeks 12306
Volgende logreeks voor archivering 12306
Huidige logreeks 12308
I added this to my init.ora file:
# Archvie Log Destinations
log_archive_start=TRUE
log_archive_dest_1=%ORACLE_HOME%\database\archive
log_archive_format="%%ORACLE_SID%%t_%s.arc"
However, this is not the real problem (maybe it has something to do with it, which is why I mention it aswell), the real problem is that my database freezes when the archive log file is "full". When the archive file reaches ~102.400Kb it just freezes up and I need to restart the database.
The following error is written to the alert_sid.log file:
Thu Apr 17 09:19:55 2008
Thread 1 cannot allocate new log, sequence 12309
All online logs needed archiving
Current log# 2 seq# 12308 mem# 0: O:\ORACLE\ORADATA\O\REDO02.LOG
The problem seems to be that the oracle service can't start a new logfile when the previous one is full. Does anybody know how I could fix this?
Thanks in advance,
Bram

Hello Maran, thanks for your quick response.
I added the output of archivelog list in the original post, but it's in dutch so here's the (loose) translation of the output:
SQL> archive log list
Databaselog mode Archive mode
Automatic archiving Deactivated
Archive destionation O:\oracle\ora92\RDBMS
Oldest on-line logsequence 12307
Next logsequence for archiving 12307
Current logsequence 12309
Maybe something that can help with the troubleshooting:
The archivelog file is written to O:\oracle\ora92\RDBMS but only AFTER the reboot, I've checked SYSTEM rights to the folder and it has full control.
Babu, thanks aswell for your quick response.
The location exists and space is available but the database doesn't seem to load (that part of) the ora.init file because the output of archive log list still refers to %ORACLE_HOME%\rdbms instead of %ORACLE_HOME%\database\archive.
I've now executed alter system archive log all; and am executing the import where the database usually freezes to see if it still happens. So far I already had this written to the alert_sid.log file after executing the command:
Completed: alter database open
Thu Apr 17 10:00:11 2008
ARCH: Evaluating archive log 1 thread 1 sequence 12307
ARCH: Beginning to archive log 1 thread 1 sequence 12307
Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12307.001'
ARCH: Completed archiving log 1 thread 1 sequence 12307
ARCH: Evaluating archive log 2 thread 1 sequence 12308
ARCH: Beginning to archive log 2 thread 1 sequence 12308
Creating archive destination LOG_ARCHIVE_DEST_1: 'O:\ORACLE\ORA92\RDBMS\ARC12308.001'
ARCH: Completed archiving log 2 thread 1 sequence 12308
And new log files were written to the directory (O:\oracle\ora92\RDBMS) and this time I didn't have to reboot for it to happen. Both were 100mb files without the database actually doing all that much though.
Message was edited by:
user616266

Restore database in archivelog mode

Hello everyone.
I've been looking on google, how to restore my database on archivelog mode, but i did not succeed.
I made my backup using this mode, and now i need to know what is the command need to use to restore this.
Somebody can write the command here please ?
Thanks for help.
Regards,
Dan
ps: Using Oracle 10g XE on Win XP.

user8973191 wrote:
Oh, ok Vijayaraghavan K.
Thx for u help.
And about the users ?
i need to create the "same" user in another machine ?
For example:
In this machine i using the "system" user, where i have my tables.
Another machine, when i restore, my tables will go to the "system" user too? or i can choice? or i need to create one?A true backup is a copy of the data files at the file/block level. The restore is therefore a restore of the data files/blocks. Applying the redo (archive logs) is also done at the block level. None of that knows or cares (or needs to know or care) about logical objects (such as users, tablespaces, tables, rows, etc) within the database. so if you do a proper restore, you are restoring files to a consistent state and thus everything that was defined within those files will be there when restored.

Why we need oracle database reboot to put database in archivelog mode?

I know how to enable archivelog mode, but what is the reason that to enable archive log we need database restart. which process forces to do that.

SantoshGanjure wrote:
Thanks a lot EdStevens for ur prompt response...I need something that satisfies my managers query.
If the question has originated with the PHB, then my flippant answer is even more relevant ...
PHB's are incapable of understanding the technical details, so I prefer to give them the 'executive summary':
"Because that's the way Oracle is written. We can argue over the technical merits of such a requirement 'till the cows come home. But at the end of the day, we have to shut down the database because the 'alter database archivelog' command will only succeed when the database is in mount (not open) mode. Now, let's work out how we can achieve our objective of putting the database in archivelog mode with minimal and appropriately scheduled down time."
As for the actual down time, it's about as minimal as you can get. How long does it take your database to complete a shutdown once the command is given? How long does it take you to type "startup mount"? How long does it take you to type "alter database archivelog"? to type "alter database open;"? For the database to complete the 'open' process? You could even script it so as to eliminate the keyboard typing time.

Can we put RAC database in Archivelog mode without shutting down

All,
Can we put RAC database in Archivelog mode without shutting down.
Currently our new production database (2 node RAC) is in no archive log mode, Need to enable archive log in the database...
I believe we need to set the cluster_database=false and then put the DB in archive log mode then we need to bounce the database to take effect...
Just curious to know in 11gR2 ...Can we put the RAC database in archive log mode without any downtime ...?

Even RAC or non-RAC, database should bounced and enable/disable archive log mode from mount status.

RMAN in 10g database deletes archivelog files before standby receives them

Hi all,
We currently have problem with our Oracle 10gR1 database on Windows 2000 server in that the RMAN backups on the primary database delete archivelogs before the standby database can receive current and new archivelogs from primary database. What happens is that RMAN backs up the archivelogs and deletes them from disk before the archivelogs are sent to the standby. The standby then looks for these archivelogs on the primary but is unable to locate them. Whenever this happens, the production database (primary) hangs and we have to restart the instance on the primary. We have our Data Guard setup in maximum performance mode so this should not happen.
As a short term fix, we have changed the backups to have RMAN backup and delete the archive logs 15 minutes older than current time so that the standby can receive the logs and not have problems. Besides this fix is there a long term solution to the problem or is it a bug in Oracle 10g? The issue came up after we upgraded from 9i to 10g and never saw it before in 9i with RMAN and Data Guard physical standby databases.
Thanks
Ben Prusinski, Oracle DBA

thanks for answer...
did you managed to make it 'work'?
according to doc. if set on standby it should:
<>
Then, these files are eligible for deletion:
Archived redo log files in the flash recovery area that
were applied on the standby database.
<>
and this is to my understanding irespective to retention policy...unfortunately report obsolete does not report applied archived logs as eligable for deletion.
How this works in your case?
regards.
goran

Backup database plus archivelog

Hi
I am using 10.2.0.3. What is the difference between "backup database plus archivelog" and "backup database"?
I deleted the archive logs after disabling the archive log option. How to fix the below problem? thank you
When I do backup database plus archivelog;
ORACLE error from target database:
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=869 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=434 devtype=DISK
archived log /export/home/oracle/archivelog/2008_06_23/o1_mf_1_82_45ymxtqd_.arc not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 82
archived log /export/home/oracle/archivelog/2008_06_23/o1_mf_1_83_45ymxwcs_.arc not found or out of sync with catalog
trying alternate file for archivelog thread 1, sequence 83
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 02/16/2009 11:48:41
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file /export/home/oracle/archivelog/2008_06_23/o1_mf_1_84_45ymxxyf_.arc
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3

Even if you've switched your database to NOARCHIVELOG mode, the ArchiveLogs that were generated earlier are still "known" as they are still cataloged in the control file (a query on V$ARCHIVED_LOG would show them).
As you are running NOARCHIVELOG, you really do not need to do BACKUP DATABASE PLUS ARCHIVELOG;
Your backup would be in MOUNT but not OPEN state so there would be no transactions.
If you really want to "clear" those older archivelogs so that RMAN doesn't attempt to backup them, you need to run these commands in RMAN :
Crosscheck Archivelog All;
Delete Expired ArchiveLog All;The first command will verify the controlfile records against the files actually present on disk and mark as "Expired" all those they do not exist on disk. The second command will "delete" them in that RMAN will no longer look for them.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Alter database into Archivelog mode.

HI Team,
I am using ORACLE 9i.
I want to convert database into archivelog mode from noarchivelog mode.
Using the following SQL Commands I can able to convert my database into the Archivelog.
SQL> connect sys as sysdba
Enter password: *****************
Connected.
SQL> alter database archivelog;
alter database archivelog
ERROR at line 1:
ORA-01126: database must be mounted EXCLUSIVE and not open for this operation
SQL> startup mount;
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 252779340 bytes
Fixed Size 453452 bytes
Variable Size 125829120 bytes
Database Buffers 125829120 bytes
Redo Buffers 667648 bytes
Database mounted.
SQL> alter database archivelog;
Database altered.
My problem is that I had to shutdown the database before converting it in to the archivelog mode...
Is there any way that without shuting down the database i can switch to archivelog mode.
Please comments...
Shatrughan

if we shutdown immediate one's database..do
it's listener terminated too???The database registration with the listener yes, the listener itself no. That is, if you execute a command like "lsnrctl stat" you won't see the database anymore, but the listener is still active. Example :
[ora102 ~ db102]$ lsnrctl stat
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 05-MAY-2007 18:57:51
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date                05-MAY-2007 18:27:34
Uptime                    0 days 0 hr. 30 min. 16 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /home/ora102/OraHome1/network/admin/listener.ora
Listener Log File         /home/ora102/OraHome1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "db102" has 1 instance(s).
Instance "db102", status READY, has 2 handler(s) for this service...
The command completed successfully
[ora102 ~ db102]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Sat May 5 18:58:03 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SYS@db102 SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS@db102 SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[ora102 ~ db102]$ lsnrctl stat
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 05-MAY-2007 18:58:33
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.1.0 - Production
Start Date                05-MAY-2007 18:27:34
Uptime                    0 days 0 hr. 30 min. 58 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /home/ora102/OraHome1/network/admin/listener.ora
Listener Log File         /home/ora102/OraHome1/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[ora102 ~ db102]$

Switched Database to ARCHIVELOG Mode, Then it Hung

Hi everyone,
This db is 9.2 on Windows.
**After switching my database to Archivelog mode and reopening, it hung forever.**
(I had to use Shutdown abort to bring it down - these steps worked to get it back online:
shutdown abort; --startup mount;
alter system archive log all;
alter database noarchivelog;
alter database open;)
The Alert.log shows "Cannot allocate new log" immediately after I switched to Archivelog mode. So it hung at that point. Had I known why it hung, maybe running 'Alter system archive log all' would have fixed everything. But I've never had to run that when I've switched other databases to Archivelog mode.
Does this indicate another problem with this database? I'm leery of it now and feel lucky that I was able to get it up again.
Thanks, John
entries from Alert.log when I switched to Archivelog mode:
ALTER DATABASE MOUNT
Wed Aug 06 11:44:19 2008
Successful mount of redo thread 1, with mount id 1689013583
Wed Aug 06 11:44:19 2008
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Wed Aug 06 11:44:45 2008
alter database archivelog
Wed Aug 06 11:44:45 2008
Starting control autobackup
Control autobackup written to DISK device
handle 'F:\ORACLE\ORA92\DATABASE\C-1602026732-20080806-00'
Completed: alter database archivelog
Wed Aug 06 11:45:17 2008
alter database open
Wed Aug 06 11:45:17 2008
Thread 1 opened at log sequence 9014
Current log# 1 seq# 9014 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO01.LOG
Successful open of redo thread 1
Wed Aug 06 11:45:17 2008
SMON: enabling cache recovery
Wed Aug 06 11:45:17 2008
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Wed Aug 06 11:45:17 2008
SMON: enabling tx recovery
Wed Aug 06 11:45:17 2008
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Wed Aug 06 11:59:58 2008
Thread 1 advanced to log sequence 9015
Current log# 2 seq# 9015 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO02.LOG
Wed Aug 06 12:01:03 2008
Thread 1 advanced to log sequence 9016
Current log# 3 seq# 9016 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO03.LOG
Wed Aug 06 12:09:16 2008
Thread 1 cannot allocate new log, sequence 9017
All online logs needed archiving
Current log# 3 seq# 9016 mem# 0: F:\ORACLE\ORADATA\PBSMEM\REDO03.LOG
**** PrefBid App locked up at this point – hung – users cannot do anything -- Note the gap in log entry time – no further entries until my Shutdown request

Hi,
We can enable automatic archiving after instance startup.
In order to enable automatic archiving without shutting down the current instance, use the SQL command ALTER SYSTEM with the ARCHIVE LOG START parameter.
ALTER SYSTEM ARCHIVE LOG START;
When using this option, the instance does not have to be shut down to enable automatic archiving.
However, if an instance is shutdown and restarted after automatic archiving is enabled using this option, the instance is reinitialized using the settings of the parameter file ("LOG_ARCHIVE_START"), which may or may not enable automatic archiving.
NOTE: On 9i, you can use an SPFILE instead of the standard pfile. The LOG_ARCHIVE_START parmaeter is deprecated with 10g.
alter system set log_archive_start=true scope=spfile;
Did you read the Metalink Note I gave you? These information was there...
Thanks,
Marcello M.

Setting database in ARCHIVELOG and duplicating with RMAN

Hi. I've tried to duplicate a Oracle 11g database that wasn't in ARCHIVELOG mode without success.
Here are the steps I followed:
- Put original database in archivelog (SID: originaldb, startup mount, alter database archivelog, alter database open).
- Configure tnsnames and create remote instance (SID: newdb)
- Start 'newdb' (startup nomount)
- Connect to 'original' using RMAN (rman target sys@originaldb)
- Connect to the remote database 'newdb' (connect auxiliary sys@newdb)
- Duplicate database (duplicate target database to newdb from active database nofilenamecheck)
Then I get the following error: "RMAN-20208: UNTIL CHANGE is before RESETLOGS change"
How should I proceed? Do I have to create a backup before trying to duplicate database?
Thanks.

Hi,
Thanks a lot.
I don't think that archivelogs were relocated, except I changed the location yesterday.
As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

10g rman database and archivelogs backup with multipled archlog destination

I would like to use the 10g database and archivelogs backup statetement
backup database plus archivelog;
I would like to restrict the location of the archivelogs backed out as I am multiplexing the
archivelogs
I did not find a LIKE statement and the backup database plus archivelog
Did i miss something
patrick boulay

I meant backup
I just want to restrict rman form backing up the two location using the 'one shot' 10g syntax
I used to backup using two steps
1) datafile
2) archlogs with a LIKE expression to tell Rman where to find the archlogs
1+2 with autobackup of control+spfile
the 'backup database plus archivelog ' syntax does accept a 'LIKE' expression
patrick

Should I keep media after "BACKUP DATABASE PLUS ARCHIVELOG"?

Hi there,
If I do full backup like this ...
BACKUP DATABASE PLUS ARCHIVELOG
... do I have to keep copy of media (database files)? I am under impression that as long as my recovery window falls between "BACKUP DATABASE PLUS ARCHIVELOG" and NOW ... I don't have to keep media files.
Am I right or wrong?
Thanks to all answers!

Sure..if you don't need to restore back to one of the previous backups, then they are no longer needed.
Configuring a retention policy will handle this maintenance for you automatically.
However, some people will keep them around as a fall back if something should happen to their most recent backup. It depends on your paranoia level and amount of disk/tape space that you have.

I can't backup database plus archivelog

Hi.
I lost few previous archivelogs, and can't run "backup database plus archivelog;".
That's what I got from rman:
RMAN> backup database plus archivelog;
Starting backup at 12-APR-09
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 04/12/2009 13:06:14
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /u01/app/oracle/backup/ORCL/archivelog/2008_08_04/o1_mf_1_11_49f37bn1_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
How to fix it ?
Hi
Run commands:
RMAN> CROSSCHECK ARCHIVELOG ALL;
RMAN> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
And then "backup database plus archivelog;"
Edited by: val75 on Apr 12, 2009 11:31 AM

After deleting expired archivelogs, backup is working fine...
RMAN>delete noprompt expired archivelog all;
RMAN>crosscheck archivelog all;
RMAN>backup database plus archivelog;
Actually, what is doing while issuing "crosscheck archivelog all" command????
thanks

Newbie.. is 'backup database plus archivelog...' needed?

On my Oracle 11.1, I'm performing full backup with command:
backup incremental level 0 database plus archivelog delete input tag LEVEL_0_INC;Since this database is not in flashback mode, I'm wondering is it needed to backup archivelogs together with datafiles?
could I done it without achivelogs and to delete them after that?
regards

799165 wrote:
On my Oracle 11.1, I'm performing full backup with command:
backup incremental level 0 database plus archivelog delete input tag LEVEL_0_INC;Since this database is not in flashback mode, I'm wondering is it needed to backup archivelogs together with datafiles?
could I done it without achivelogs and to delete them after that?
regardsYou need to have archived redo log files with your backup in order to perform a complete recovery

Error in recovery after BACKUP DATABASE PLUS ARCHIVELOG

Hi,
With Oracle 9.2.0.6 on Unix Aix 5, I made:
rman ...
RUN
ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/base/tempora/%U';
BACKUP DATABASE PLUS ARCHIVELOG;
Copy files from /base/tempora/% to another server in a directory with the same name.
Recreate the pfile and directory structure, and then
rman...
RUN
ALLOCATE CHANNEL disk1 DEVICE TYPE DISK FORMAT '/base/tempora/%U';
restore controlfile to '/base/rcterefo/oracle/o1_mf_19xw2mvb_.ctl';
restore controlfile from '/base/rcterefo/oracle/o1_mf_19xw2mvb_.ctl';
sql 'alter database mount';
restore database;
recover database;
sql 'alter database open resetlogs';
release channel disk1;
But rman fails at -> recover database; by asking an archive log 6 months old (and not in the backupset):
ORA-00279: change 1224563589 generated at 02/09/2006 16:29:46 needed for thread
1
ORA-00289: suggestion : /base/.../arch/arch0000001819.arc
ORA-00280: change 1224563589 for thread 1 is in sequence #1819
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/base/.../arch/arch0000001819.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Original base seems to works fine (can be stoped and restarted).
I thought that this BACKUP DATABASE PLUS ARCHIVELOG would contain in itself all the data needed to restart the database. Database has been stopped and restarted last week with no problem and I regularly do full backup with RMAN and TSM (we are testing now backups without TSM for a spacial case).
Has someone an idea of what's wrong?
Thanks

Hi,
Thanks for taking care of my problem.
When I try to do a set until sequence..., the RESTORE CONTROLFILE fails, telling it has nothing to restore. I think this is the same kind of problem I encounter with the full restore.
Aniway, the restore being good, i try to finish the recover and it fails, asking for a very old archive. Is it possible a transaction to be active after so much time?
In fact, I just decovered a file is in RECOVER status. I did an :
alter database datafile '...' offline drop;
since that, the recover is ok, from oracle (not rman):
recover database using backup controlfile until cancel;
Thanks again to everyone.
Regards.

1st RMAN backup database plus archivelog fails

Hi
I've just setup RMAN on Oracle 11g within a two node cluster environment.
I have completed the following:
* Created a recovery catalog
* Registed Database
* Configured retention policy window of 7 days
* Configured default device type to disk
* configured controlfile autobackup on;
* configured device type disk backup type to compressed backupset
* configured channel device type disk format
* validated database
* backup database plus archivelog and I received the following error,
RMAN> backup database plus archivelog;
Starting backup at 24/07/2008 17:37:17
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 07/24/2008 17:37:20
RMAN-06059: expected archived log not found, lost of archived log compromises re coverability
ORA-19625: error identifying file /u01/app/product/admin/RAC/arc/rac2_2_4_660689 305.arc
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
On node 2 I can list the file:
SQL> !ls -lt
total 4120
-rw-rw---- 1 rac dba 14336 Jul 24 17:18 rac2_2_5_660689305.arc
-rw-rw---- 1 rac dba 4196352 Jul 24 17:13 rac2_2_4_660689305.arc
SQL>

Read the chapter
http://download.oracle.com/docs/cd/B28359_01/rac.111/b28254/rman.htm#i474611
The node that is doing backups must be configured to have access to archivelogs on all the nodes.
See "RMAN Archiving Configuration Scenarios" -> "Noncluster File System Local Archiving Scheme".

Database in archivelog

Similar Messages

Maybe you are looking for