RMAN jobs

Hello

I start two jobs in crontab for the same full backup twice by accident.

Could someone tell me please how to stop one of the jobs?

Thank you

God

There is no way you can stop the current rman work. The alternate would be to kill the SID that started the work.

Hare krishna
Alok

Tags: Database

Similar Questions

How to kill a job RMAN?
I'm under 11.2.0.2 on Solaris and want to know what is the right way to kill a RMAN backup task that has already begun?

This looks like something as simple as: ps - ef | grep rman, then, kill-9 the two processes of rman. Right? Fake!
```
$ /home/oracle>ps -ef |grep rman
  oracle 27493 10700   0 14:08:44 pts/1       0:00 /bin/ksh rman_bkup_db_lvl0.ksh MYDB
  oracle 27524 11155   0 14:09:00 pts/3       0:00 grep rman
  oracle 27508 27493   0 14:08:44 pts/1       0:01 rman target /

$ /home/oracle>kill -9 27493 27508

$ /home/oracle>ps -ef |grep rman
  oracle 27552 11155   0 14:09:56 pts/3       0:00 grep rman
```
RMAN process seems to be killed.
But looking in the database, the process is still ongoing.
```
SQL> select username, program from v$session where username = 'SYS';

USERNAME                 PROGRAM
------------------------ ------------------------------------------------
SYS                      rman@myhost (TNS V1-V3)
SYS                      rman@myhost(TNS V1-V3)
SYS                      OMS
SYS                      sqlplus@myhost (TNS V1-V3)
SYS                      rman@myhost (TNS V1-V3)

(and several others from previous runs that I killed off at the OS level)
```
When I looked in OEM, I could see a pic of the e/s sys user and the I/O and the processes are the RMAN.

I found a web page that says if I choose to leave and join V$ SESSION_WAIT, V$ SESSION and V$ PROCESS
WHERE s.client_info LIKE '% rman', I get the SID and serial no to kill the sessions in the database.

Is there an easier way to do that? In my case, I ended up using Toad and killed all RMAN process, but then I hit 11872103 bug which left status showing running and causing a performance problem during resync'ing of the catalogue.
Hello

Follow the documentation on this subject:

Termination of an RMAN command
http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmtroub.htm#BRADV176

Any doubt post here.

RMAN utility is only a Client who has opened on the Oracle server. RMAN doesn't create or read the files in data/backupset but is no Oracle server... RMAN will manage and control.
If you kill only the RMAN Client process, it is not guaranteed on the Oracle Server session will also be killed. So, if you want to stop RMAN job you have to kill the session not RMAN Client.

Kind regards
Levi Pereira

Published by: Levi Pereira on December 11, 2012 14:26

Corrective action - script using RMAN catalog?
Hi all

for ways to avoid an archiver stuck, I implemented a FRA_USAGE metric and corrective action for this measure which runs a RMAN script, back up and delete the archived logs. This so far works fine.
However, what I would really like to do is to connect to our catalogue and then back up the archive logs - is it at all possible and if so, how?

Thanks for your comments.
Step 1 Add the recovery catalog to GC. See http://diandiandiandididi.blogbus.com/logs/62862298.html (stop at the point "Use Recovery Catalog")
Step 2 for each db for which you want to use tracking the catalog to retrieve the in the mentioned link step "Using Recovery Catalog" to stop at the "backup." planned to specify
Step 3 (sorry, now I have to do in the lead) create action: installation, library of Corrective Action if I remember correctly, you can create a RMAN job just the way you want it to be.
Step 4 change your UDM (FRA_USAGE) so that the corrective action will be run step 3 created new RMAN script.

Now, you can also create and schedule backups RMAN (using the RC) without using the operating system script.

Eric

How to ensure the rman backup is successful?
Hello

We have scheduled backup rman jobs.
1. but how do ensure us that all rman backups are successful?
2. If the rman written directly to tape, how to ensure that all tape backup are successful?

Thank you

Andrew
Not sure why you were not able to download. I sent you a copy.

Kind regards
S.K.

Typical interview question

Hi all
I have a typical interview question, I tried the solution, but did not find.
1 Int that: scheduled backup RMAN is running normal and run DBA "shutdown" command for an interview without knowing about backup, will, RMAN work ends or gets killed?
My answer: because it's a normal shutdown, it should wait until existing complete process and restrict new connections
2 Int that: If there are two channels allocated for the backup of the db and a channel separate for archivelog, the rman job status is db backup is complete and has been asked to stop, he will start archivelog backup channel?
Run {allocate channel d1 type disk;}
allocate channel d2 type disk;
backup database;
output channel d1;
output channel d2;
allocate channel d3 type disk;
ARCHIVELOG backup all;
output channel d3;
}
I'm confused here, I tried to find the answer on the forum, as well as google, but did not find. Unfortunately I do not have a test machine to try this scenario myself. Therefore, ask your valuable contributions.
Also let me know if my assumption is correct and to expect all connections stop normal and transactional (only users or RMAN, expdp, etc as well), I check this link, but it is not categorize connections http://docs.oracle.com/cd/E11882_01/server.112/e16604/ch_twelve042.htm
Thank you very much in advance!
AbbasDBA

As the session already exists, rman allocates channels at the initial stage only, it reuses just channel placement phase by phase. So in this case it will not stop, it will continue with archives too

stretch of metro exadata (10 km)

Hi guys,.
just a strange question.
is it possible to stretch an exadata in Metro style?
do not have recovery of cars if I pass data center?
My question:
Some applications really do not reconnect after the switch with for example dataguard :-(
Chris

Hello

actually what you want to say

Failover or move?

It depends on how much 'action' is on your primary database?

Are 100 or 10,000 user connected and online to make the DML heavy or something else.

In our enviroenment 11.2 on Exa Production 4 databases of transactions not so much, it takes 2 minutes for a passage to the.

But beware any rman job is running.

concerning

Full database backup time varies after you apply the hotfix.
Hello gurus,

I applied a patch last week to my database to 10.2.0.5, initially it was 10.2.0.1.Before the patch of the database took 10 hours to finish the job of backup rman through OEM and used to seize the 590 GB of data. After the patch, that the rman job complete in 2 hours and it is only win about 220 GB without errors

The total size is 590 GB but 220 used space and free is 370 gb.

Magic question is why it takes 2 hours to complete and only backup 220 GB in 10.2.0.5 compare to 10.2.0.1.

I used this query to check the size of the database.

SESSION_KEY, INPUT_TYPE, STATUS,
TO_CHAR (START_TIME, "mm/dd/yy HH24 '") start_time,
TO_CHAR (END_TIME, "mm/dd/yy HH24 '") end_time.
elapsed_seconds/3600 hrs
v $ RMAN_BACKUP_JOB_DETAILS
order by session_key;
There are several bugs fixed in 10.2.0.5 which can realize:

6967455 RMAN BACKUP FILE may be slow
7119336 backup backupset RMAN does not parallelize in multiple channels
7173341 internal cleaning RMAN can be slow

This note MOS can provide more details:

10.2.0.5 Patch set - list of bug fixes by problem Type [ID 1088172.1]

Best regards

mseberg

Snapshot controlfile enqueue wait.
Hello
I was running Backup complete level 0 on a single session and when you are connected with the other attempted session archivelogs backup I got
'pending snaphsot controlfile enqueue' message and was not able to run the report need backup.
So my question is rman taking snapshot controlfile to process any backup or in special cases such as synchronisation?
BTW, full backup seems stuck so maybe that wasn't normal behavior with snapshot CF enqueue.
I'm talking about 10.2.0.3 DB.
Concerning
GregG
Hello

I was running Backup complete level 0 on a single session and when you are connected with the other backup archivelogs tried session

It can be a normal behavior since you made the simultaneous backup.
When RMAN needs to backup or re-sync the control file, it first creates a snapshot or a coherent picture of the control file. If RMAN jobs is already backed up the control file while the other one needs to create a new snapshot control file, then you can see this message.
```
Error:     ORA 230
Text:     operation disallowed: snapshot controlfile enqueue unavailable
---------------------------------------------------------------------------
Cause:     The attempted operation cannot be executed at this time because
     another process currently holds the snapshot controlfile enqueue.
Action:     Retry the operation after the concurrent operation that is holding the
     snapshot controlfile enqueue terminates.
```
Options:
-Wait until the work of creating the queue ends
-Cancel the task in progress and restart once completed the task of creation of the queue
-Cancel the task create the queue

See this note:
RMAN: Backup snapshot fails with ORA-230 Controlfile Enqueue unavailable [ID 145619.1]

Kind regards
Levi Pereira

Schedule a task to run at a date given by month
I don't think its possible but hoping that someone will be able to work around the problem.

I rman jobs run every day, to work click on calendar > each week and Monday to Thursday only

Each week, calendar > weekly > Friday only

I want to perform monthly tasks on the Friday or Saturday of the last month. I don't see how I can do this, I can click on every 4 weeks, but after 5-6 months the calendar must be interrupted a few months have 5 weeks. Theres I see nowhere to click "run only the last Saturday of the month.

anyone?
These hours are currently not supported, but will be made available in a future version of Enterprise Manager.

Backup e-mail reports
Hi all

I am new to Oracle and have recently implemented incremental backups on multiple databases. I am currently looking at backup through OEM reports and it would be nice to have these reports and their results by e-mail to a central location, so that I can quickly check the success of a backup without having to connect individually to each database.

Could someone point me in the right direction to know where to start to do so or if it is still possible? This would be by changing the current scheduled RMAN jobs I have configured through OEM?
You can do this with Enterprise manager.

Preferences--> general--> to put your email
Preferences--> rules--> to clean the rules of your e-mail (send email when the job finished, what database down,...)

implement a RMAN script in a cron job with a cold way of database

Hello
I want to run the Rman script in a cron job. But my question is: is it possible to make a backup of cold with the editing of the database and change at the end of the backup?
here my sample rman script
#! / bin/ksh
export ORACLE_SID = test
ORACLE_HOME=/U01/app/Oracle/product/11.2.0/dbhome_1; Export ORACLE_HOME
PATH = / usr/sbin: $PATH: $ORACLE_HOME/bin. export PATH
ORACLE_HOME/bin/rman target = / < < EOF
Run {}
SQL! connect / as sysdba;
SQL! stop immediately;
SQL! Startup mount;
allocate channels ch1 disc type
disc format ' / u01/app/oracle/backup/full_%d_T%T_s%s_p%p'(database).
backup database archivelog;
remove obsolete;
output channel ch1
SQL! alter database open
}
"exit";
EXPRESSIONS OF FOLKLORE
Thank you

Hello

No problem, when you use the rman target / it to connect with the RMAN and RMAN fast turns. You can change your order something like that

#! / bin/ksh

export ORACLE_SID = test

ORACLE_HOME=/U01/app/Oracle/product/11.2.0/dbhome_1; Export ORACLE_HOME

PATH = / usr/sbin: $PATH: $ORACLE_HOME/bin. export PATH

ORACLE_HOME/bin/rman target = /.<>

Run {}

stop immediately;

bootable media;

allocate channels ch1 disc type

format ' / u01/app/oracle/backup/full_%d_T%T_s%s_p%p';

backup database archivelog;

remove obsolete;

output channel ch1.

ALTER database open;

}

"exit";

EXPRESSIONS OF FOLKLORE

HTH

Follow-up of RMAN backup job details

Version:11.2.0.3/Solaris 11
Follow the details of the work of backup RMAN, this point of view view/dyn.performance dictionary do you use?
In our store, we use the incremental update (progressive fusion). For details of the previous work of RMAN, I tried to use
v$ rman_status
and
v$ rman_backup_job_details
But the information provided by these 2 views do not match. For example, on June 26, 2013, there is an incremental backup and a backup archivelog. According to the v$ rman_status, both of them took 61 minutes (46 + 15)
According to v$ rman_backup_job_details, backup jobs took 96 minutes. It doesn't seem to provide all the info about archive newspaper bkp however.
The start_time and end_time provided by two of these points of view is not math!
Col starttime format a25
Col endtime format a25
Select the status, object_type, to_char (start_time, 'dd' / MY/yyyy:hh:mi:ss) as starttime,
TO_CHAR (end_time, 'dd' / my/yyyy:HH:mi:ss) as end time,
TO_NUMBER(end_time-start_time) * 24 * 60 duration_minutes
of sys.v$ rman_status where start_time > trunc (sysdate) - 20-operation = "BACKUP."
end_time desc order.
OBJECT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS
----------------------- ------------- ------------------------- ------------------------- ----------------
FAILED ARCHIVELOG 07/JUN / 2013:08:47:44
ARCHIVELOG FINISHED 26/JUN / 2013:06:49:16 26/JUN / 2013:07:36:14 46.9666667
FINISHED THE INCR DB 26/JUN / 2013:06:33:18 26/JUN / 2013:06:49:16 15.9666667
ARCHIVELOG FINISHED 25/JUN / 2013:06:50:55 25/JUN / 2013:07:58:01 67.1
FINISHED THE INCR DB 25/JUN / 2013:06:25:06 25/JUN / 2013:06:50:55 25.8166667
ARCHIVELOG COMPLETED 24/JUN / 2013:06:15:42 24/JUN / 2013:07:07:54 52.2
FINISHED DB INCR 24/JUN / 2013:06:01:09 24/JUN / 2013:06:15:42 14.55
COMPLETED ARCHIVELOG 23/JUN / 2013:09:47:48 23/JUN / 2013:10:01:19 13.5166667
FINISHED THE DB INCR 23/JUN / 2013:09:40:27 23/JUN / 2013:09:47:48 7.35
ARCHIVELOG FINISHED 22/JUN / 2013:07:23:18 22/JUN / 2013:07:41:29 18.1833333
FINISHED INCR DB 22/JUN / 2013:07:15:35 22/JUN / 2013:07:23:17 7.7
COMPLETED ARCHIVELOG 21/JUN / 2013:07:30:33 21/JUN / 2013:09:05:50 95.2833333
FINISHED THE INCR DB 21/JUN / 2013:06:39:35 21/JUN / 2013:07:30:33 50.9666667
ARCHIVELOG FILLED 20/JUN / 2013:07:35:54 20/JUN / 2013:09:25:03 109.15
FINISHED THE INCR DB 20/JUN / 2013:06:55:08 20/JUN / 2013:07:35:54 40.7666667
ARCHIVELOG COMPLETED 19/JUN / 2013:07:20:10 19/JUN / 2013:08:27:28 67.3
FINISHED THE INCR DB 19/JUN / 2013:07:00:02 19/JUN / 2013:07:20:10 20.1333333
ARCHIVELOG COMPLETED 18/JUN / 2013:07:27:30 18/JUN / 2013:09:19:50 112.333333
FINISHED THE INCR DB 18/JUN / 2013:07:02:09 18/JUN / 2013:07:27:30 25,35
ARCHIVELOG COMPLETED 17/JUN / 2013:07:42:20 17/JUN / 2013:08:40:29 58,15
FINISHED DB INCR 17/JUN / 2013:07:22:29 17/JUN / 2013:07:42:20 19.85
ARCHIVELOG COMPLETED 17/JUN / 2013:06:28:16 17/JUN / 2013:07:42:44 74.4666667
FINISHED DB INCR 17/JUN / 2013:01:57:49 17/JUN / 2013:06:28:11 270.366667
ARCHIVELOG FINISHED 16/JUN / 2013:02:18:02 16/JUN / 2013:04:22:26 124.4
FINISHED DB INCR 16/JUN / 2013:01:48:18 16/JUN / 2013:02:18:02 29.7333333
ARCHIVELOG FINISHED 14/JUN / 2013:07:27:44 14/JUN / 2013:08:40:53 73.15
FINISHED DB INCR 14/JUN / 2013:07:01:19 14/JUN / 2013:07:27:43 26.4
ARCHIVELOG COMPLETED 13/JUN / 2013:06:56:13 13/JUN / 2013:07:47:50 51.6166667
FINISHED THE INCR DB 13/JUN / 2013:06:42:11 13/JUN / 2013:06:56:13 14.0333333
ARCHIVELOG FILLED 12/JUN / 2013:07:12:43 12/JUN / 2013:08:12:10 59.45
FINISHED INCR DB 12/JUN / 2013:06:45:51 12/JUN / 2013:07:12:43 26.8666667
ARCHIVELOG FINISHED 11/JUN / 2013:07:21:36 11/JUN / 2013:08:46:11 84.5833333
FINISHED THE INCR DB 11/JUN / 2013:06:52:29 11/JUN / 2013:07:21:36 29.1166667
ARCHIVELOG COMPLETED 10/JUN / 2013:07:04:49 10/JUN / 2013:07:55:15 50.4333333
FINISHED THE INCR DB 10/JUN / 2013:06:49:10 10/JUN / 2013:07:04:49 15.65
COMPLETED ARCHIVELOG 09/JUN / 2013:08:10:13 09/JUN / 2013:09:04:10 53.95
FINISHED DB INCR 09/JUN / 2013:07:50:24 09/JUN / 2013:08:10:13 19.8166667
COMPLETED ARCHIVELOG 08/JUN / 2013:07:37:09 08/JUN / 2013:08:33:58 56.8166667
FINISHED DB INCR 08/JUN / 2013:07:17:56 08/JUN / 2013:07:37:09 19.2166667
COMPLETED ARCHIVELOG 07/JUN / 2013:08:32:01 07/JUN / 2013:09:34:11 62.1666667
FINISHED DB INCR 07/JUN / 2013:07:36:27 07/JUN / 2013:08:32:01 55.5666667
COMPLETED ARCHIVELOG 07/JUN / 2013:08:48:10 07/JUN / 2013:11:28:14 160.066667
42 selected lines.
-Output from v$ rman_backup_job_details
Select the State, input_type;
to_char(start_time,'dd/mm/yyyy:HH:mi:ss') as starttime,
to_char(end_time,'dd/mm/yyyy:HH:mi:ss') as end time,
TO_NUMBER(end_time-start_time) * 24 * 60 duration_minutes
V $ rman_backup_job_details
where start_time > trunc (sysdate) - 20
end_time desc order.
INPUT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS
----------------------- ------------- ------------------- ------------------- ----------------
FAILED ARCHIVELOG 07/06 / 2013:08:47:44
FINISHED THE INCR DB 26/06 / 2013:06:00:09 26/06 / 2013:07:36:14 96.0833333
FINISHED THE INCR DB 25/06 / 2013:06:00:08 25/06 / 2013:07:58:01 117.883333
FINISHED THE INCR DB 24/06 / 2013:06:00:09 24/06 / 2013:07:07:54 67.75
FINISHED THE DB INCR 23/06 / 2013:08:07:56 23/06 / 2013:10:01:19 113.383333
FINISHED THE INCR DB 22/06 / 2013:06:00:10 22/06 / 2013:07:41:29 101.316667
FINISHED THE INCR DB 21/06 / 2013:06:00:12 21/06 / 2013:09:05:50 185.633333
FINISHED THE INCR DB 20/06 / 2013:06:00:12 20/06 / 2013:09:25:03 204.85
FINISHED THE INCR DB 19/06 / 2013:06:00:11 19/06 / 2013:08:27:28 147.283333
FINISHED THE INCR DB 18/06 / 2013:06:00:16 18/06 / 2013:09:19:50 199.566667
FINISHED THE INCR DB 17/06 / 2013:06:00:13 17/06 / 2013:08:40:29 160.266667
FINISHED THE INCR DB 16/06 / 2013:06:04:02 17/06 / 2013:07:42:44 818,7
FINISHED THE INCR DB 15/06 / 2013:06:05:12 16/06 / 2013:04:22:26 617.233333
FINISHED THE INCR DB 14/06 / 2013:06:00:09 14/06 / 2013:08:40:53 160.733333
FINISHED THE INCR DB 13/06 / 2013:06:00:09 13/06 / 2013:07:47:50 107.683333
FINISHED THE INCR DB 12/06 / 2013:06:00:10 12/06 / 2013:08:12:10 132
FINISHED THE INCR DB 11/06 / 2013:06:00:17 11/06 / 2013:08:46:11 165,9
FINISHED THE INCR DB 10/06 / 10/06 2013:06:00:14 / 2013:07:55:15 115.016667
FINISHED THE INCR DB 09/06 / 2013:06:00:10 09/06 / 2013:09:04:10 184
FINISHED THE DB INCR 08/06 / 08/06 2013:06:00:09 / 2013:08:33:58 153.816667
FINISHED THE DB INCR 07/06 / 2013:06:00:19 07/06 / 2013:09:34:11 213.866667
COMPLETED ARCHIVELOG 07/06 / 2013:08:48:10 07/06 / 2013:11:28:14 160.066667
22 selected lines.

When I run a full/incremental backup archivelog with it shows only as a job in v$ rman_backup_job_details. If I run explicitly just a backup archivelog all RMAN makes it appear separately as an ARCHIVELOG backup in v$ rman_backup_job_details.

rman_status indicates the individual pieces of the jobs. For example, for a full backup, it shows the db backup and the archivelog.

The start and end time in rman_status should match with $rman_backup_job_details.

Lets take the 25th, for example:

In man_backup_job_details

INPUT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS

----------------------- ------------- ------------------- ------------------- ----------------

FINISHED THE INCR DB 25/06 / 2013:06:00:08 25/06 / 2013:07:58:01 117.883333

In v$ man_status:

OBJECT_TYPE STARTTIME ENDTIME DURATION_MINUTES STATUS

----------------------- ------------- ------------------------- ------------------------- ----------------

ARCHIVELOG FINISHED 25/JUN / 2013:06:50:55 25/JUN / 2013:07:58:01 67.1

FINISHED THE INCR DB 25/JUN / 2013:06:25:06 25/JUN / 2013:06:50:55 25.8166667

You should view your log files to see what rman was between 06:25:06 and 06:00:08 when work began at the start of the incremental backup.

You can see that the end time is the same in both views.

Not easy to explain but I hope that helps.

RMAN delete obsolete job fails due to the error of peripheral distribution
Experts, I need help, please.

It's on Windows 10.2.0.1

RMAN > DELETE NOPROMPT OBSOLETE;

RMAN retention policy apply to the order
RMAN retention policy is set to 3 days recovery window
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 130 devtype = DISK
output channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the delete command at 15/05/2012 14:10:17
ORA-19554: error device allocation, type of device: SBT_TAPE device name:
ORA-27211: unable to load the media management library

I ran RMAN > set up the device type 'SBT_TAPE' clear;
but I still get the same error.

I backup to disk, not tape

Note the reference to SBT_TAPE:

RMAN configuration parameters are:
SET UP THE DEVICE TYPE DISK PARALLELISM BACKUPSET BACKUP TYPE 1;
SET UP THE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default

What should I do to be able to run REMOVE OBSOLETE;?

Thank you, John
Try to use the OVERLAPPING BACKUP first and then repeat DELETE OBSOLETE

RMAN script does not work as a cron job, but works when explicitly executed
Oracle 10 g 2 10.2.0.1, Oracle Enterprise Linux 4 U7.

I've added a task to crontab of the oracle user who looks like the following:
```
#ORACLE_HOME,ORACLE_SID and PATH are set in the user's profie
TAG=`date|awk '{print $1"_"$2"_"$3}'| tr [:lower:] [:upper:]`

echo "backup started on`date` "> /home/oracle/rman.log

rman target / LOG='/home/oracle/rman_run.log' << EOF

run{

sql 'aler system switch logfile';
backup full database tag='$TAG' include current controlfile;
delete noprompt obsolete;

}
exit;
EOF

echo "rman finished, returned $? " >> /home/oracle/rman.log
echo "Backup ended on `date` " >> /home/oracle/rman.log
```
the tracks work as expected but the rman command never works the inside of cron, it always returns code 1, but if I call the script itself from the command line
It works smoothly and the backup is performed.

what I am doing wrong?
what I am doing wrong?

no no no ORACLE_HOME and ORACLE_SID is defined in script
The script does not source in the script of environmental requirements

env | Tri o /tmp/capture.env

above indicates how deficient the script environment cron is really

RMAN validate in Noarchive mode - is no longer available in 12 c?

We conducted a weekly working on our bodies to detect corruption. A simple RMAN "check logical backup validate database;"
We have a few instances that are running in NOARCHIVE mode. As we were moving from 11G to 12 c NOARCHIVE instances jobs were failing.
RMAN > check logical backup validate database.
2 > output
From backup 5 October 15
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 800 type device = DISK
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command to backup to 10/05/2015 05:00:06
RMAN-06149: cannot BACKUP of DATABASE in NOARCHIVELOG mode
Complete recovery manager.

Are we on this GROUND? Is there no way less of 12 c to validate a database in NOARCHIVE mode?

Guys...

This is a bug!

DOC - ID 21132367.8

If the necessary patch, bug 21132367 , you may need to create a SR.

Thank you

RMAN jobs

Similar Questions

Maybe you are looking for