RMAN executable corrupted

Hi,
I am working on AIX with an Oracle Database 9i I have been trying to use the rman but it seems that it is not working;
The executable seems corrupted
test01-/dev01/app/oracle/product/9.2.1.0/bin>ls -al rman*
-rwxr-x--x 1 oracle oinstall 0 Nov 01 17:06 rman
-rwxr-x--x 1 oracle oinstall 22974515 Mar 01 2009 rmanO
I know that I will have to relink the executable but I am trying to look for the reason that it got corrupted in the first place. Additionally the backup jobs are being executed through a software and not through crontab.
Please any indicators or pointers will be of great help.
Thanks.

user8676543 wrote:
Hi,
I am working on AIX with an Oracle Database 9i I have been trying to use the rman but it seems that it is not working;
The executable seems corrupted
test01-/dev01/app/oracle/product/9.2.1.0/bin>ls -al rman*
-rwxr-x--x 1 oracle oinstall 0 Nov 01 17:06 rman
-rwxr-x--x 1 oracle oinstall 22974515 Mar 01 2009 rmanO
I know that I will have to relink the executable but I am trying to look for the reason that it got corrupted in the first place. Additionally the backup jobs are being executed through a software and not through crontab.
Please any indicators or pointers will be of great help.
Thanks.The output is most telling, though it would have been easier to read if you had enclosed it in code tags:
test01-/dev01/app/oracle/product/9.2.1.0/bin>ls -al rman*
-rwxr-x--x 1 oracle oinstall 0 Nov 01 17:06 rman
-rwxr-x--x 1 oracle oinstall 22974515 Mar 01 2009 rmanOSo we see that the rman executable file has a length of zero. We can safely dismiss any suggestions of "supported" or "PATH" issues.

Similar Messages

RMAN identifies corrupt block

Hi,
If Rman identify corrupt block while performing a backup of the archive logfiles, it failover to an existing intact copy...wht does tht mean...

If there is no copy available then RMAN backup fails. You can override this by using skip inaccessible option with backup command.
RMAN > BACKUP DATABASE PLUS ARCHIVELOG SKIP INACCESSIBLE; OR
rman > BACKUP ARCHIVELOG ALL SKIP INACCESSIBLE;
BUT this compromises sthe database recovery as missed archivelog file is not present is the backup. The SKIP INACCESSIBLE option just asks the RMAN to continue the backup if an archivelog is missing . This completes the backup of all other datafiles, archivelog files , controlfiles . The backup will not fail in this case.

RMAN Block Corruption

Hi,
i am using oracle 11g R1 database in windows 2003 server. i need to stimulate two scenario
1 . I want to corrupt a block and identify the corrupt block using RMAN.
2 . I need to corrupt a block and while taking backup using RMAN it should tell that the block is corrupt.
can anyone tell me how to do the above scenario
Regards,
007

007 wrote:
Hi,
i am using oracle 11g R1 database in windows 2003 server. i need to stimulate two scenario
1 . I want to corrupt a block and identify the corrupt block using RMAN.
2 . I need to corrupt a block and while taking backup using RMAN it should tell that the block is corrupt.
can anyone tell me how to do the above scenario
Regards,
007Check the link I've provided:
https://forums.oracle.com/forums/thread.jspa?messageID=9850924#9850924

Corrupted block rman

Hi
As far as I know, if rman finds block corruption, it will terminate the backup session.
However, in my scenerio, rman skipped the corrupted block and continue taking backup of remaining datafiles.
What is the reason for this?
Note that, I didnt use maxcorrupt in rman script.
The below is the end of the logfile:
channel t4: backup set complete, elapsed time: 01:02:50
released channel: t1
released channel: t2
released channel: t3
released channel: t4
released channel: t5
released channel: t6
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on t2 channel at 03/20/2010 17:29:52
ORA-19566: exceeded limit of 0 corrupt blocks for file /dbs02/prd/mis_refrence.dbf01
Recovery Manager complete.

Hi,
RMAN is terminated only when it does not find the data file etc. But it does not terminate due to block corruption.
See the following excerpts from the following oracle document link.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10734/rcmconc1.htm#1016108
RMAN detects and responds to two primary types of backup errors: I/O errors and corrupt blocks. Any I/O errors that RMAN encounters when reading files or writing to the backup pieces or image copies cause RMAN to terminate the backup jobs. For example, if RMAN tries to back up a datafile but the datafile is not on disk, then RMAN terminates the backup. If multiple channels are being used, or redundant copies of backups are being created, RMAN may be able to continue the backup without user intervention.
If BACKUP AS BACKUPSET creates more than one complete backup set and an error occurs, then RMAN needs to rewrite the backup sets that it was writing at the time of the error. However, it retains any backup sets that it successfully wrote before terminating. The NOT BACKED UP SINCE option of the BACKUP command restarts a backup that partially completed, backing up only files that did not get backed up.
RMAN copies datafile blocks that are already identified as corrupt into the backup. If RMAN encounters datafile blocks that have not already been identified as corrupt, then RMAN stops the backup unless SET MAXCORRUPT has been used. Setting MAXCORRUPT allows a specified number of previously undetected block corruptions in datafiles during the execution of an RMAN BACKUP command. If RMAN detects more than this number of corruptions while taking the backup, then the command terminates. The default limit is zero, meaning that RMAN does not tolerate corrupt blocks by default.
When RMAN finds corrupt blocks, until it finds enough to exceed the MAXCORRUPT limit, it writes the corrupt blocks to the backup with a reformatted header indicating that the block has media corruption. If the backup completes without exceeding MAXCORRUPT,then the database records the address of the corrupt blocks and the type of corruption in the control file. Access these records through the V$DATABASE_BLOCK_CORRUPTION view. Note that if more than MAXCORRUPT corrupt blocks are found, the V$DATABASE_BLOCK_CORRUPTION view is not populated. In such a case, you should set MAXCORRUPT higher and re-run the command to identify the corrupt blocks.
Regards
Edited by: skvaish1 on Mar 24, 2010 4:39 PM

How to overcome Block corruption using RMAN

Hi All,
How to overcome bolck corruption using RMAN. What is the procedure to do so.
Thanks & Regards
J.Venugopal

Hi all,
I´ve performed the following command on RMAN:
RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE ARCHIVELOG ALL;After, I query the V$DATABASE_BLOCK_CORRUPTION table, and the below records
was returned:
     FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
        67       4670          1         1202832866 LOGICAL
        68     154131        338         1175601952 LOGICAL
        68     155329         60         1174783128 LOGICAL
        68     155409         60         1174783132 LOGICAL
        68     155471         78         1174783135 LOGICAL
        68     155551         78         1174783139 LOGICAL
        68     155631         18         1174783143 LOGICAL
        68     155651         18         1174783144 LOGICAL
        68     155671         18         1174783145 LOGICAL
        68     155691         18         1174783146 LOGICAL
        68     155711         18         1174783147 LOGICAL
        68     155731         18         1174783148 LOGICAL
        68     155751         18         1174783149 LOGICAL
        68     155771         78         1174783150 LOGICAL
        68     155851         78         1174783154 LOGICAL
        68     155931         49         1174783158 LOGICAL
        73     165758          1         1180191676 LOGICALSo, when I try to recover these blocks by using blockrecover command, I got the error:
RMAN> blockrecover corruption list;
Starting blockrecover at 27-SEP-07
using channel ORA_DISK_1
using channel ORA_DISK_2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of blockrecover command at 09/27/2007 10:22:10
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 73 found to restore
RMAN-06023: no backup or copy of datafile 68 found to restore
RMAN-06023: no backup or copy of datafile 67 found to restoreWhat can I do in this case?
Thank U very much!
[]´s

Backup not being executed

Hi everybody.
In Oracle 10g, Windows, I have a problem: the backup I've scheduled to execute everyday at 2 AM, is not executed if dbconsole is not running.
I thought that scheduling via EM dbconsole was simply an interface to different programs, in this case, for RMAN.
What I'm doing now is to schedule another different job, and then stop dbconsole, although I think it's not going to execute. I have also to check this problem in another 10g DB, but over Linux.
Is it possible to solve this issue?
Thanks.

user8676543 wrote:
Hi,
I am working on AIX with an Oracle Database 9i I have been trying to use the rman but it seems that it is not working;
The executable seems corrupted
test01-/dev01/app/oracle/product/9.2.1.0/bin>ls -al rman*
-rwxr-x--x 1 oracle oinstall 0 Nov 01 17:06 rman
-rwxr-x--x 1 oracle oinstall 22974515 Mar 01 2009 rmanO
I know that I will have to relink the executable but I am trying to look for the reason that it got corrupted in the first place. Additionally the backup jobs are being executed through a software and not through crontab.
Please any indicators or pointers will be of great help.
Thanks.The output is most telling, though it would have been easier to read if you had enclosed it in code tags:
test01-/dev01/app/oracle/product/9.2.1.0/bin>ls -al rman*
-rwxr-x--x 1 oracle oinstall 0 Nov 01 17:06 rman
-rwxr-x--x 1 oracle oinstall 22974515 Mar 01 2009 rmanOSo we see that the rman executable file has a length of zero. We can safely dismiss any suggestions of "supported" or "PATH" issues.

TARGET database is not compatible with this version of RMAN

I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
I get the following error:
RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Does this mean that my RMAN database has to be 8.0.4 ?
What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
Thanks for any help,
Sameer

check RMAN compatibility matrix
Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
8.0.3 8.0.3 >=8.x 8.0.3
8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.6 8.0.6 >=8.x 8.0.6
8.0.6 8.0.6 >=8.1.x >=8.1.x
8.1.5 8.1.5 >=8.1.x >= 8.1.5
8.1.6 8.0.6.1 >=8.x 8.0.6
8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
8.1.6 8.1.x >=8.1.x >= RMAN executable
8.1.7 8.0.6.1 >=8.x 8.0.6
8.1.7 8.0.6.1 >=8.1.x >=8.1.x
8.1.7 8.1.x >=8.1.x >= RMAN executable
9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4

TARGET database is not compatible with RMAN version

Hi all,
we have an issue related to RMAN version.
A few weeks ago we update our 10.2.0.1 Oracle Database to 10.2.0.4 using 6810189 pacth set.
Now when we try to execute RMAN this is the output:
Recovery Manager : Release 11.1.0.6.0 - Production on Jue Nov 20 12:20:57 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.4 needed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
(I translate the spanish message, maybe the words is not exactly the same in the english version)
As is shown in the output the RMAN version installed by the pacthset is higher than database version, is there a way to downgrade RMAN or to solve this issue?
Thanks in advance,
Alex

I'm pretty sure patchset 6810189 does not install RMAN executable 11g. I did several patchings to 10.2.0.4 and that never happened. Patching may sometimes leave components at a lower level than the patchset,but never the opposite is true. That would be definitely a bug. So you (or someone else) installed 11g software.
Werner

Problem with RMAN on Oracle8.1.7 on Redhat Linux 6.2

Hi, does anyone who is using Oracle with the configuration listed below having problems running RMAN?
- Redhat 6.2 with kernel upgraded to 2.2.16-3
- Oracle 8.1.7 EE for Linux
I don't seem to be able to start RMAN even though I have enable LARGE_POOL_SIZE in the parameter file.
Whenever I type rman at the prompt, it just hangs!
If I issue rman catalog rman/rmancatdb, it will return with an error saying can't connect to catalog.
I got these messages when creating the recovery catalog for the 1st time.
I suspect its the rman executable that is playing pranks with me. I even issue "relink all" and still can't run rman.
If anyone know a solution to this please reply. Thanks.

Hi there,
Its funny...I found a solution to my problem from oracle metalink.
if anyone face the same problem you can see the solution here.
The solution is....check your PATH in .bash_profile
Make sure the $ORACLE_HOME/bin is specified before the $PATH so that it can call the right Oracle rman executable. This is becoz Linux has a command by the same name rman.
The Oracle metalink explanation is below.
On typing rman at the command prompt, the process goes for a hang. The rman utility
is not invoked nor there is any error message displayed at the prompt.
If the user types rman -h , then the following error message appears on the
screen:
rman
[-f <ASCII|roff|TkMan|Tk|Sections|HTML|SGML|MIME|LaTeX|LaTeX2e|RTF|pod>]
[-S(ource of man page passed in)] [-F(ormatted man page passed in)]
[-r <man reference printf string>] [-l <title printf string>]
[-V(olume) <colon-separated list>] [-U(RLs as hyperlinks)]
[-b (show subsections)] [-k(eep head/foot)]
[-n(ame of man page) <string>] [-s(ection) <string>]
[-p(aragraph mode toggle)] [-t(abstops spacing) <number>]
[-N(ormalize spacing, changebars)] [-y (zap hyphens toggle)]
[-K (declare that page has no breaks)]
[-d(iff) <file> (old version of page source to incorporate)]
[-M(essage) <text> (included verbatim at end of Name section)]
[-R(ebus words for TkMan)] [-C (enable Tcl/Tk formatting)]
[-o (no op)] [-O <arg> (no op with arg)]
[-q(uiet--don't report warnings)] [-h(elp)] [-v(ersion)]
[<filename>]
Solution Description
Find out which rman utility is invoked by typing ,
'which rman' at the command prompt.
Ensure that the correct utility is invoked from $ORACLE_HOME/bin directory.
Explanation
In linux, there is a OS utility called rman. This utility is used for formatting
purposes.This resides in the /usr/bin directory.
If the ORACLE_HOME is not set properly or the PATH variable contains ORACLE_HOME/bin
at the end instead of beginning, then the rman utility provided by oracle is
not invoked.Also, no error message is thrown out, since there is another utility
by the same name.
When the environment variables are properly set, then the correct utility is
invoked from the $ORACLE_HOME/bin
Good Luck to whoever needs this solution.
null

RMAN-06429: RCVCAT database is not compatible with this version of RMAN

Hi There,
I just want to confirm there is no work around for the issue I am having. Here is my situation:
I have four Oracle 8i databases that can not be removed because of client requirements. These 8i databases have there own RMAN catalog which is 10G (Originally there were Oracle 8i, 9i and 10g databases using it but are now moved to 11g catalog). Databases are backing up fine. However, all the other databases are using the RMAN 11g Catalog. I want to point the Oracle 8i databases to point to the RMAN 11g recovery catalog. I created an 8i schema, however, i'm getting the following error message: RMAN-06429: RCVCAT database is not compatible with this version of RMAN. It's pretty straight forward, however, I wanted to put the question out there to see if there are any work arounds. I would prefer to have only one RMAN recovery catalog.
Thanks in advance.
J

Hello;
I know of no way around the RMAN Compatibility Matrix. I would keep a second catalog DB for these older databases. Or go NOCATALOG. I checked all my sources and if there's a better option I sure did not find it. What breaks if these go to Oracle 9?
http://arjudba.blogspot.com/2010/03/about-rman-compatibility-matrix.html
Ask Tom
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:518622203320
Additional Information :
OERR: RMAN 6429 %s database is not compatible with this version of RMAN [ID 70776.1]
RMAN-06439: Compatibility Between 8.1.5 RMAN Executable and 8.1.6 Catalog [ID 104728.1]
Best Regards
mseberg
Edited by: mseberg on Sep 7, 2012 8:27 AM
Edited by: mseberg on Sep 7, 2012 10:53 AM

Calling RMAN script with DBMS_JOB

Hi,
Maybe someone can help me out. I'm perfecting my skills on 9i in the backup area before I have a need to use them and am taking notes.
What I want to do is to store the backup script in the recovery catalog (which I already did under the name BACKUP) and call that script on a daily basis using DBMS_JOBS.
Here is my script:
RMAN>CREATE SCRIPT 'BACKUP'
{ALLOCATE CHANNEL C1 TYPE DISK;
BACKUP INCREMENTAL LEVEL 0 DATABASE
FILESPERSET 4;
BACKUP ARCHIVELOG ALL;
DELETE ARCHIVELOG UNTILTIME 'SYSDATE-7';}
This script compiled and is stored in rman. I ran it and it worked. I also autoconfigured the parameters to backup the controlfile automatically when the backup or copy is done.
Now my next goal is to get this script to run automatically everyday using DBMS_JOBS and this is where it is not working.
I used the DBMS_JOB.SUBMIT parameters to store the job in this feature but first the procedure 'RUNBACKUP' must compile successfully.
DBMS_JOB.SUBMIT(:1,'RUNBACKUP', SYSDATE,'SYSDATE+1');
This RUNBACKUP is a procedure that has to be called by the DBMS_JOBS PACKAGE. But the procedure is where Im having problems trying to write.
I am assuming that rman is not connected to the target database here. So this is what I think it should look like:
CREATE OR REPLACE PROCEDURE RUNBACKUP
BEGIN
RMAN; --the first thing that
has to be called is rman executable.
CONNECT TARGET AL/AL@BBROWN
--now we have to connect the target db to rman.
CONNECT CATALOG RMAN/RMAN@RCAT;
-- connecting to the recovery catalog.
RUN {EXECUTE SCRIPT 'BACKUP';} --execute the stored backup script
END;
Also, at the end of this procedure I would like to exit rman as the final command.
Any ideas on this would be appreciated and thanks for your help in advance.
Al

You need to create a shell script to execute rman and add that script to cron, something like this:
#!/bin/ksh
# Script name: whole_db_backup.ksh
export PATH=/oracle/app/9i/bin:$PATH
export ORACLE_HOME=/oracle/app/9i
export ORACLE_SID=MDR
rman <<EOF
connect target /
connect catalog rmancat/PASS@RMANCAT
run {execute script whole_db_backup;}
exit
EOF

Trying to perform recovery RMAN in OEM. Fails!!!

I am trying to learn to do backups within OEM. I see it uses RMAN behind the scenes.
Anyway, I have 2 databases residing on one machine. A production database "a" and a clone it "b". I performed the cloning in OEM fine.
I then performed a full database backup on "b" using OEM which included the control files. This seemed to go well. I had them created on a mapped drive."s:\"
Now I am trying to use the perform recovery tools in OEM and I can't get anywhere. I am not familiar with RMAN, but I thought that was the purpose of the OEM to provide out of the box solution. The RMAN script generated behind the scenes looks like:
set dbid 1508042233;
set controlfile autobackup format for device type disk to '%F';
run {
allocate channel oem_restore type disk;
restore controlfile from autobackup;
shutdown immediate;
startup mount;
I changed the 2nd line to match my drive mapping 's:\%F';
My error message is as follows and yes it was wrapped this way!
Error in Restoring Control File
Recovery Manager: Release 9.0.1.5.1 - Production (c) Copyright 2001 Oracle Corporation. All rights reserved. RMAN> connected to target database: mycopy1 (not mounted) using target database controlfile instead of recovery catalog RMAN> executing command: SET DBID RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00579: the following error occurred at 08/17/2005 20:57:06 RMAN-03002: failure during compilation of command RMAN-03013: command type: CSET RMAN-06188: cannot use command when connected to target database RMAN> executing command: SET CONTROLFILE AUTOBACKUP FORMAT RMAN> 2> 3> 4> allocated channel: oem_restore channel oem_restore: sid=8 devtype=DISK Starting restore at 17-AUG-05 released channel: oem_restore RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00579: the following error occurred at 08/17/2005 20:57:07 RMAN-03002: failure during compilation of command RMAN-03013: command type: restore RMAN-03002: failure during compilation of command RMAN-03013: command type: IRESTORE RMAN-06495: must explicitly specify DBID with SET DBID command RMAN> Oracle instance shut down RMAN> connected to target database (not started) Oracle instance started database mounted Total System Global Area 151810128 bytes Fixed Size 282704 bytes Variable Size 100663296 bytes Database Buffers 50331648 bytes Redo Buffers 532480 bytes RMAN> Recovery Manager complete. Starting restore at 17-AUG-05 released channel: oem_restore RMAN-00571: ===============================================
I tried going to the command line and working with it
using the following script:
(Note here i tried working on database "a" which I also have a backup for)
set dbid 21410814117;
connect target
set controlfile autobackup format for device type disk to 'S:\%F';
run {
allocate channel oem_restore type disk;
restore controlfile from autobackup;
shutdown immediate;
startup mount;
*********************************88
RMAN> set dbid 21410814117;
executing command: SET DBID
RMAN> connect target
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 08/17/2005 21:18:43
RMAN-06189: current DBID 4294967295 does not match target mounted database (2141081417)
RMAN> set controlfile autobackup format for device type disk to 'S:\%F';
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
using target database controlfile instead of recovery catalog
RMAN>
RMAN> run {
2> allocate channel oem_restore type disk;
3> restore controlfile from autobackup;
4> }
allocated channel: oem_restore
channel oem_restore: sid=10 devtype=DISK
Starting restore at 17-AUG-05
released channel: oem_restore
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 08/17/2005 21:18:45
RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03002: failure during compilation of command
RMAN-03013: command type: IRESTORE
RMAN-06496: must use the TO clause when the database is mounted or open
RMAN>
RMAN> shutdown immediate;
database dismounted
Oracle instance shut down
RMAN> startup mount;
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 151810128 bytes
Fixed Size 282704 bytes
Variable Size 100663296 bytes
Database Buffers 50331648 bytes
Redo Buffers 532480 bytes
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00579: the following error occurred at 08/17/2005 21:19:01
RMAN-06189: current DBID 4294967295 does not match target mounted database (2141081417)
from what I understand my two databases dbid's are "a"=21410814117 and
"b" is 1508042233 I have no idea where this other one is coming from.
Any help would be appreciated. I wouldn't mind being able to do it at the command line, so at least I would have an idea of what is going on, but the OEM doesn't seem to work at all.
Thanks,
John

Do one thng. Keep the target db in nomount mode and then run recovery using OEM.
Regards,
http://askyogesh.com

Is it possible to install and run RMAN remotely ?

Is it possible to install and run RMAN on a separate remote network-connected platform from the platform of the Oracle DB instance with which RMAN was initially installed without any additional licensing ?
I.e. is it possible to copy the RMAN executable and any required libraries to the remote platform and successfully run RMAN on the remote platform to backup the Oracle DB instance with which RMAN was initially installed without any additional licensing ?
This is using RMAN with a recovery catalogue in the target database control file.
Thanks,
Brett.

Hi Kostya,
Depends on what you mean. Default the SOA Suite installs a Oracle Lite database to use for hydration storage. So default there is no real database and therefore you can not install ApEx. But you can configure the SOA Suite to use a "normal" database, and then you can use ApEx.
Regards Pete

Recover Database in RMAN vs SQL*PLUS

Hello,
Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
Thanks.
h3. Solution Summary:
The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
Edited by: Dude on Jan 7, 2011 12:30 PM

Dude wrote:
I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
C:\Documents and Settings\chinar>rman target sys/sm
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
RMAN> startup nomount;
Oracle instance started
Total System Global Area     138412032 bytes
Fixed Size                     1247708 bytes
Variable Size                 71304740 bytes
Database Buffers              58720256 bytes
Redo Buffers                   7139328 bytes
RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
2> ;
Starting restore at 07-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=157 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
Finished restore at 07-JAN-11
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> restore database;
Starting restore at 07-JAN-11
Starting implicit crosscheck backup at 07-JAN-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 1 objects
Finished implicit crosscheck backup at 07-JAN-11
Starting implicit crosscheck copy at 07-JAN-11
using channel ORA_DISK_1
Finished implicit crosscheck copy at 07-JAN-11
searching for all files in the recovery area
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
Finished restore at 07-JAN-11
RMAN> recover database;
Starting recover at 07-JAN-11
using channel ORA_DISK_1
starting media recovery
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
2.0\ORADATA\T\REDO02.LOG
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
media recovery complete, elapsed time: 00:00:03
Finished recover at 07-JAN-11
RMAN> exit
Recovery Manager complete.
C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
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
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
Database altered.
SQL> And above you see lines as
archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
*2.0\ORADATA\T\REDO02.LOG*
archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
ence=7
It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
alter database recover if needed
start until cancel using backup controlfile
Media Recovery Start
parallel recovery started with 2 processes
ORA-279 signalled during: alter database recover if needed
start until cancel using backup controlfile
Fri Jan 07 17:50:34 2011
alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
Fri Jan 07 17:50:34 2011
Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
Fri Jan 07 17:50:34 2011
Incomplete recovery applied all redo ever generated.
Recovery completed through change 665263
Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start until cancel using backup controlfile)
And these is not any difference.
Hope that help you and you got answer.

Creation of Standby Database through Rman.

Hi Everybody,
Oracle Ver: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
Os: Windows Xp
I am trying to create a standby database with the help of Rman..
but when i am trying to invoke the Rman Executable and connect to the primary and auxillary database ie:standby
it's giving me the following error...........
C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 09:28:08 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY (DBID=1503515402)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12541: TNS:no listenerI have restarted my listener service but still getting the error...
here is my Listener.ora entries...........
LISTENER =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1525))
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = PRIMARY)
      (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
standby=
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1526))
SID_LIST_standby =
(SID_LIST =
    (SID_DESC =
      (SID_NAME = standby)
      (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
)any help appreciated
Regards,
Prosenjit Mukherjee

Hi Hemant,
It worked...when I i issued the command as mentioned by you it started the Listener..
lsnrctl start standby
Now I am able to connect to both the Database using Rman..
C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 10:55:08 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: PRIMARY (DBID=1503515402)
connected to auxiliary database: STANDBY (not mounted)
RMAN>Thanks for the Input...
Is there any way by which i can start both the Listener with "lsnrctl start"...........instead of manually starting individual listener's
Regards,
Prosenjit Mukherjee
Edited by: Prosenjit on Oct 2, 2008 11:01 AM

RMAN executable corrupted

Similar Messages

Maybe you are looking for