Rman backup in noarchivelog mode

hi all,
My database(ORCL) is in noarchivelog mode
I am taking RMAN backup using recovery catalog(backupdb)
target database(ORCL) is in mount mode
I am getting following errors:
RMAN> backup database;
Starting backup at 01-AUG-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel defaul
t
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 a
nd serial=:2
RMAN-10002: ORACLE error: ORA-12571: TNS:packet writer failure
RMAN-03002: failure of backup command at 08/01/2008 15:52:03
ORA-03114: not connected to ORACLE
I again tried and then i got these errors:
C:\Documents and Settings\Administrator>set oracle_sid=backupdb
C:\Documents and Settings\Administrator>rman catalog rman1/rman
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
RMAN> connect target sys/sys@orcl
connected to target database (not started)
RMAN> backup database;
Starting backup at 01-AUG-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/01/2008 16:12:40
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
RMAN>
please explain
Message was edited by:
ArchanaTewatia

Hi,
Try to study the errors Correctly ..
RMAN> connect target sys/aqtechmvardi@orcl
connected to target database (not started)
RMAN> backup database;
Starting backup at 01-AUG-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/01/2008 16:12:40
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Try to mount the Target DataBase it will work.
Thanks
Pavan Kumar N

Similar Messages

RMAN backup with NOARCHIVELOG mode

Hi,
Is it possible to EXCULDE TABLESPACE with rman using NOARCHIVELOG database ?
Thanks

Use following persistent setting:
RMAN> CONFIGURE EXCLUDE for tablespace <Tablespace Name>;
N.B. You will not be able to do this for system tablespace.
Regards,
S.K.

Hot backup on NOARCHIVELOG mode?

DB version:10gR2, 11G
Why is it not possible to do a Hot Backup in NOARCHIVELOG mode? What role does archived redo log files have in a Hot backup?

Because it takes more than zero seconds to backup a database.
Say your database consists of 1 single datafile of 10MB. This datafile, at the OS filesystem level, consists of 2,560 blocks of 4KB each.
If you start a backup of the datafile, the OS utility (tar, cp, cpio, whatever command) reads the first 4KB block and copies it out. It then, after a certain time, reads the next block. And so on till it gets to the last block of the file.
However, since the database is "open" transactions may have updated blocks in the datafile.
Therefore, at time t0, block 1 may have been copied out. At time t5, block 128 may have been copied out. At time t32, block 400 may have been copied out. Unfortunately, some user may have updated block 1 at time t3 and block 128 at time t8.
What would happen if these blocks, having been copied out at different times were restored ? They would be inconsistent !!
It is the ArchiveLog mechanism that allows Oracle to know that a datafile was "active" when it was being backed up. Oracle has to "re-play" all changes that occurred on the datafile from the time the datafile backup began (at t0) till it ended (at the 2,560th block).

What files can be excluded from user-managed backup in noarchivelog mode?

what files can be excluded from user-managed backup in noarchivelog mode?
control files,
sqlnet.ora file,
tnsnames.ora,
datafiles associated with read-only tablespaces,
datafiles associated with read/write tablespaces,
of these, what can be excluded and what have to be included?
Thanks.

... and don't forget pfile or spfile... it can help too.
Re: What are generally backed up during the backup?
Nicolas.

ORA-01152 when restoring from RMAN backupset in NOARCHIVELOG mode

Hi all,
I got the error ORA-01152 when I tried restoring an Oracle 10g R1 database from an RMAN backupset into a new server. The error returned when it reached to the level of opening the database in resetlogs.
The database runs on NOARCHIVELOG mode and on Windows 2003 Server SP2 32-bit.
Following is what I did in RMAN:
set ORACLE_HOME=D:\oracle\product\10.1.0\db_1
set ORACLE_SID=DAWA
set PATH=D:\oracle\product\10.1.0\db_1\bin;%PATH%
cd %ORACLE_HOME%\bin
rman target sys/mypassword
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Feb 13 00:36:55 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount pfile=X:\temp\DawaPFILE.ORA
connected to target database (not started)
Oracle instance started
Total System Global Area 1048576000 bytes
Fixed Size 792200 bytes
Variable Size 551807352 bytes
Database Buffers 494927872 bytes
Redo Buffers 1048576 bytes
RMAN> restore controlfile from
'X:\temp\Flash_Rec\DAWA\AUTOBACKUP\2011_07_16\O1_
MF_S_756655133_7226R018_.BKP';
Starting restore at 19-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=270 devtype=DISK
channel ORA_DISK_1: restoring controlfile
channel ORA_DISK_1: restore complete
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL01.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL02.CTL
output filename=D:\ORACLE\ORADATA\DAWA\CONTROL03.CTL
Finished restore at 17-AUG-11
alter database mount;
database mounted
catalog backuppiece 'X:\temp\PUMHJATD_1_1';
catalog backuppiece 'X:\temp\PTMHJ91Q_1_1';
/* Rename the Redologfiles,so that they can be created in new locations
the database is opened in resetlogs */
SQL>conn sys as sysdba
-- get registered files from SELECT * FROM V$LOGFILE
SQL> alter database rename file
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO01.LOG' to
'X:\oracle\oradata\dawa\REDO01.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO02.LOG'
to 'X:\oracle\oradata\dawa\REDO02.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO03.LOG'
to 'X:\oracle\oradata\dawa\REDO03.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO04.LOG'
to 'X:\oracle\oradata\dawa\REDO04.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO05.LOG'
to 'X:\oracle\oradata\dawa\REDO05.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO06.LOG'
to 'X:\oracle\oradata\dawa\REDO06.LOG';
alter database rename file 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\REDO07.LOG'
to 'X:\oracle\oradata\dawa\REDO07.LOG';
/* Now in RMAN: restore the datafiles
    to new locations and recover. */
RMAN> run{
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS201' TO
'D:\oracle\oradata\dawa\UNDOTBS201';
set newname for datafile
'E:\ORACLE\PRODUCT\10.1.0\ORADATA\DAWA\UNDOTBS202' TO
'D:\oracle\oradata\dawa\UNDOTBS202';
restore database;
switch datafile all;
alter database open resetlogs;
.../* alter database open resetlogs returned the errors: */
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 08/18/2011 08:44:45
ORA-01152: file 2 was not restored from a sufficiently old backup
ORA-01110: data file 2: 'D:\ORACLE\ORADATA\DAWA\UNDOTBS206'Thanks in advance.

SYS @ DAWA> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SYS @ DAWA> startup mount
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size                   792200 bytes
Variable Size             551807352 bytes
Database Buffers          494927872 bytes
Redo Buffers                1048576 bytes
Database mounted.
SYS @ DAWA> recover database using backup controlfile until cancel;
ORA-00279: change 329012 generated at 03/08/2005 16:24:46 needed for thread 1
ORA-00289: suggestion :
X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC
ORA-00280: change 329012 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'X:\ORACLE\ORADATA\FLASH_REC\DAWA\ARCHIVELOG\2011_08_18\O1_MF_1_6_%U_.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'X:\ORACLE\ORADATA\DAWA\SYSTEM01.DBF'You can download the alert log from here:
http://ahmedbaraka.com/temp/alertdawa.log

Restore using incremental backup with noarchivelog mode

Hello experts,
We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
Thank You
Regards,
Venkateshwar

If you do not want to read the whole doc This is the snippet for you.
Recovering a NOARCHIVELOG Database with Incremental Backups
Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
Media recovery is not possible because no archived redo logs exist.
You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
To recover a NOARCHIVELOG database with incremental backups:
After connecting to the target database and the recovery catalog, place the database in a mounted state:
STARTUP FORCE MOUNT
Restore and recover the database.
For example, you can perform incomplete recovery with the following commands:
RESTORE DATABASE
FROM TAG "consistent_whole_backup";
RECOVER DATABASE NOREDO;
Open the database with the RESETLOGS option.
For example, enter the following command:
ALTER DATABASE OPEN RESETLOGS;

Backup in NOARCHIVELOG mode using RMAN

I'm trying to do a cold backup of a database as outlined in the 'Backup and Recovery Guide':
- shutdown database using SVRMGRL
- run the backup from RMAN:
However I get the following error messages:
RMAN> run {
2> allocate channel dev1 type disk;
3> backup (database format '/oracle/backup/bp_%s_%p');}
RMAN-03022: compiling command: allocate
RMAN-03026: error recovery releasing channel resources
RMAN-00569: ================error message stack follows================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: allocate
RMAN-06003: ORACLE error from target database: ORA-01012: not logged on
It looks like RMAN wants to connect to the database I want to backup...
What am I doing wrong????
null

You've probably already figured this out, but you need to connect to the target database before doing backup/restore operations, using a command like
RMAN> connect target user/pw ...

RMAN backup in no archivelog mode

what are possible ways to backup the database which is in no archivelog mode using RMAN
regards,
Sakthivel
Edited by: SAKTHIVEL on Jul 22, 2011 1:02 AM

Hi;
Please check:
backup in noarchivelog mode using RMAN
backup in noarchivelog mode using RMAN
Regard
Helios

RMAN backup problems, which one first?

Oracle 11g on Windows 2008Std I've inherited. It has a nightly backup job set in Ent Mgr, the Oracle-suggested disk backup, script:
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA\$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database;
The backup fails every night with log:
allocate channel oem_disk_backup device type disk;
recover
allocated channel: oem_disk_backup
channel oem_disk_backup: SID=154 device type=DISK
Starting recover at 08-JUL-10
Finished recover at 08-JUL-10
no copy of datafile 5 found to recover
no copy of datafile 4 found to recover
no copy of datafile 3 found to recover
no copy of datafile 2 found to recover
no copy of datafile 1 found to recover
Starting backup at 08-JUL-10
input datafile file number=00002 name=C:\ORACLE\ORADATA\UC4\UC4\SYSAUX01.DBF
input datafile file number=00001 name=C:\ORACLE\ORADATA\UC4\UC4\SYSTEM01.DBF
channel oem_disk_backup: specifying datafile(s) in backup set
channel oem_disk_backup: starting incremental level 1 datafile backup set
channel oem_disk_backup: starting piece 1 at 08-JUL-10
input datafile file number=00004 name=C:\ORACLE\ORADATA\UC4\UC4\USERS01.DBF
input datafile file number=00003 name=C:\ORACLE\ORADATA\UC4\UC4\UNDOTBS01.DBF
input datafile file number=00005 name=C:\ORACLE\ORADATA\UC4\UC4\APPWORX1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 52428800 bytes disk space from 2147483648 limit
I see the space limit error. The database is defined with flash_recovery_area 2GB. So I should just enlarge the flash_recovery_area to make the backup work. BUT the real puzzler before I go making changes is, this database is in NOARCHIVELOG mode. What I find in the books say don't do incremental backups in NOARCHIVELOG mode; and don't do NOARCHIVELOG unless you don't care much about being able to recover your data. So, not being able to ask the guy who set this up, "Why is it NOARCHIVELOG, especially when set for incremental backups, I pose these here:
1. Switch to ARCHIVELOG?
2. Enlarge flash_recovery_area to get these backups working first?

You can do incremental backups in noarchivelog mode - it's just that the database must be in mount mode. But I agree - unless the data is not important (and if you are taking backups then it seems to be important) I would have the database in archivelog mode.

Can't backup database in NOarchivelog mode

Hi there,
I get this error when I run this command from rman:
backup database
Starting backup at 19-JAN-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/19/2011 17:18:10
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
please help.
Thanks in advance!

user13286861 wrote:
ok it finally shutdown cleanly.
I altered it in archivelog mode.
Now I can run a backup database command from rman?What does it cost to try it and see? What would be the worst thing that could possibly happen? An error message saying you can't do that?
And please note, this forum is not a chat line. Operators are NOT standing by. Posting a new message every two minutes to give an update on the fact that the database hasn't shut down yet is not necessary and not productive.
If there are a lot of pending transactions when you issue SHUTDOWN IMMEDIATE, they will all have to be rolled back as part of the shutdown. That can take some time. And if you bypass that with SHUTDOWN ABORT, they will have to be rolled back as part of instance crash recovery on the next startup, which will also take some time. Five minutes may feel like an eternity when you are sitting there waiting for your command to complete, but is no reason to panic.

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Hi All
Its my first time to use RMAN in our ERP EBSR12
our database version is 11g
Please help how to resolv and make successfully backup
RMAN> backup database;
Starting backup at 24-JAN-11
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 24-JAN-11
channel ORA_DISK_1: finished piece 1 at 24-JAN-11
piece handle=/oracle/mybackup_db/PROD2/backupset/2011_01_24/o1_mf_ncnnf_TAG20110 124T111824_6msvw4cv_.bkp tag=TAG20110124T111824 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/24/2011 11:18: 25
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
RMAN>
Thanks

ORA-19602: cannot backup or copy active file in NOARCHIVELOG modeIs your database in archivelog or noarchivelog mode?
How to Turn Archiving ON and OFF [ID 69739.1]
Please also see these docs/links.
ORA-19602 Using RMAN to Backup Database [ID 246183.1]
COLD RMAN backup fails: Ora-19602 even after SHUTDOWN IMMEDIATE and STARTUP MOUNT [ID 373828.1]
Backup & Recovery
http://www.oracle.com/pls/db112/portal.portal_db?selected=14&frame=#backup_and_recovery
Thanks,
Hussein

Backup/restore tablespaces in noarchivelog mode

In our office there is a oracle 10g box that's used for testing purposes.
It's only got 1 database, but each user has their own tablespace.
As it's not a 'live' box, archivelog and flashrecovery have been disabled by the dba probably in favour of speed.
I have a NUnit test suit that runs across a tablespace, and I am trying to restore the tablespace before each run.
In noarchivelog mode, RMAN allows me to take the tablespace offline, and create a backup - so far so good.
Later on, I am able to take the tablespace offline again, and issue a "RESTORE TABLESPACE" command.
But then I cannot bring the tablespace online without issuing a "RECOVER" command.
I have tried the NOREDO option but it still says that the file needs a media recovery before it can be brought online.
Is there a way to bring the tablespace online without applying the REDO logs ?
Or is tablespace backup/restore not possible because of noarchivelog ?
Thanks.

I tried the TTS method, and it was only marginally quicker than a data_only impdp.
I suspect this is due to the nature of a fresh nunit test database, where the metadata (huge tables structure, stored proc, etc) is often larger than the table contents itself.
In the grand scheme of things it might even end up slower, as i need to drop the tablespace including contents if i want to use TTS to load up the backed up dbf.
From the comments I'm guessing that there's no way of just updating the timestamp of the tablespace without applying the REDO logs then ?
I've tested other methods as well.
Flash recovery could only work on a table or db level, I can't take the db offline as there are other users on it with their own tablespace/schemas. (it was an old dev's box, we're reusing what we can)
impdb with the truncate and data_only flag seems to be the only viable option so far, with TTS up for consideration.

RMAN in noarchivelog mode

Hi Experts
I need to confirm ,,, Can I use RMAN to do incremental backup level 0 and 1 in noarchivelog mode?,
if yes can you give me script as example , please note I can't take database in nomount mode.

This forum is for the Berkeley DB replication product. We cannot answer RMAN questions. I believe the forum for RMAN is:
Recovery Manager (RMAN)
Paula Bingham
Oracle

System datafile block corruption - no backups and database in NOARCHIVELOG mode

Dear All,
Database version - oracle 11.1 Enterprise
OS - RHELinux 5.8
What are the options of recovering from physical block corruption when there are no backup available to perform block media recovery?
V$DATABASE_BLOCK_CORRUPTION reports two segments corrupted (please see attached image for details).
1 table in system datafile - sys_fba_barrierscn
1 index - (applicaiton index)
What are my options?
I know there is a possibility that the database will not restart after a shutdown due to corruption in system tablespace.
Database is in noarchivelog mode. So online backups are not possible and there aren't any full backups either.
I am thinking of below,
1. Run dbms_repair with fix_block_corruption. - Still database startup might fail?
2. Shutdown the database and take offline full backup with RMAN MAXCorrupt option.
Appreciate your suggestions and advises.
Thanks
Stefan

Thanks Sybrand,
Agree with your first two suggestions .
Also scheduled a expdp job tonight. (Only backup like thing they had was a expdp cron, but until today all the large tables were failing due to small undo_retention).
Yes. Flashback is not used. So hopefully it will not affect the a database restart i guess?
Related to dbms_repair, I was referring to - http://askdba.org/weblog/2010/08/physical-corruption-ora-1578-part-3/.
Where DBMS_REPAIR.FIX_CORRUPT_BLOCKS and DBMS_REPAIR.SKIP_CORRUPT_BLOCKS used.
Which i think will not use any redo.
Thanks
Stefan

Backup of one tablespace in noarchivelog mode

Hi,
I am running 10g.
Is it possibe to backup a specific tablespace in noarchive mode?
Thanks

Hi
I am able to backup the tablespace,
but after the recovery loosing the table data.
The database is in noarchivelog mode!
here is what I am doing:
my_table TABLE has 100 rows, and is saved under my_tablespace TABLESPACE.
RMAN> sql 'alter tablespace my_tablespace offline';
RMAN> backup tablespace my_tablespace;
RMAN> sql 'alter tablespace my_tablespace online';
Now I truncate the table
TRUNCATE TABLE my_table;
RMAN> sql 'alter tablespace my_tablespace offline';
RMAN> restore tablespace my_tablespace;
RMAN> recover tablespace my_tablespace;
RMAN> sql 'alter tablespace my_tablespace online';
Now the my_table TABLE is after the rcovery empty :-(
What I am doing wrong

Rman backup in noarchivelog mode

Similar Messages

Maybe you are looking for