I installed 19C grid, then install the 19C software only, all are successful. then I tried to create a database with dbca but got failed, it's very strange that RMAN failed in the logs as below, I doubt it's grid privilege issue but I can't find what it is.
more logs for this question that is before the above logs, kindly help to check it:
[Thread-516] [ 2021-09-20 15:30:13.164 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=allocated channel: ORA_DISK_1 [Thread-516] [ 2021-09-20 15:30:13.169 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=channel ORA_DISK_1: SID=498 device type=DISK [Thread-516] [ 2021-09-20 15:30:13.466 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output= [Thread-516] [ 2021-09-20 15:30:13.631 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=channel ORA_DISK_1: starting datafile backup set restore [Thread-516] [ 2021-09-20 15:30:13.633 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=channel ORA_DISK_1: specifying datafile(s) to restore from backup set [Thread-516] [ 2021-09-20 15:30:13.633 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=channel ORA_DISK_1: restoring datafile 00001 to +ORA [Thread-516] [ 2021-09-20 15:30:13.634 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=channel ORA_DISK_1: reading from backup piece /opt/DB/oracle/product/19c/db/assistants/dbca/templates/Seed_Database.dfb [Thread-516] [ 2021-09-20 15:36:18.706 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=channel ORA_DISK_1: ORA-19870: error while restoring backup piece /opt/DB/oracle/product/19c/db/assistants/dbca/templates/Seed_Database.dfb [Thread-516] [ 2021-09-20 15:36:18.707 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=ORA-19504: failed to create file "+ORA" [Thread-516] [ 2021-09-20 15:36:18.707 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=ORA-17502: ksfdcre:4 Failed to create file +ORA [Thread-516] [ 2021-09-20 15:36:18.707 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=ORA-15001: diskgroup "ORA" does not exist or is not mounted [Thread-516] [ 2021-09-20 15:36:18.707 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=ORA-01017: invalid username/password; logon denied [Thread-516] [ 2021-09-20 15:36:18.707 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output= [Thread-516] [ 2021-09-20 15:36:18.709 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=failover to previous backup [Thread-516] [ 2021-09-20 15:36:18.709 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output= [Thread-516] [ 2021-09-20 15:36:18.728 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=creating datafile file number=1 name=+ORA [Thread-516] [ 2021-09-20 15:36:18.808 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=RMAN-00571: =========================================================== [Thread-516] [ 2021-09-20 15:36:18.808 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== [Thread-516] [ 2021-09-20 15:36:18.808 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=RMAN-00571: =========================================================== [Thread-516] [ 2021-09-20 15:36:18.808 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=RMAN-03002: failure of restore command at 09/20/2021 15:36:18 [Thread-516] [ 2021-09-20 15:36:18.808 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=ORA-01180: can not create datafile 1 [Thread-516] [ 2021-09-20 15:36:18.815 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output= [Thread-516] [ 2021-09-20 15:36:18.815 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=RMAN> [Thread-516] [ 2021-09-20 15:36:18.815 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=echo set on [Thread-516] [ 2021-09-20 15:36:18.822 EDT ] [RMANEngine.readSqlOutput:997] Log RMAN Output=set echo off; [Thread-516] [ 2021-09-20 15:36:18.822 EDT ] [RMANEngine.readSqlOutput:1040] hasError is true [Thread-516] [ 2021-09-20 15:36:18.822 EDT ] [RMANEngine.readSqlOutput:1046] ERROR TRACE DETECTED
Starting restore at 20-SEP-21
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=498 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to +ORA
channel ORA_DISK_1: reading from backup piece /opt/DB/oracle/product/19c/db/assistants/dbca/templates/Seed_Database.dfb
channel ORA_DISK_1: ORA-19870: error while restoring backup piece /opt/DB/oracle/product/19c/db/assistants/dbca/templates/Seed_Database.dfb
ORA-19504: failed to create file "+ORA"
ORA-17502: ksfdcre:4 Failed to create file +ORA
ORA-15001: diskgroup "ORA" does not exist or is not mounted
ORA-01017: invalid username/password; logon denied
failover to previous backup
creating datafile file number=1 name=+ORA
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 09/20/2021 15:36:18
ORA-01180: can not create datafile 1
RMAN>
echo set on
Can anyone give me some suggestion?
Thanks everyone, the issue has been resolved with google help. it's OS setting issue, grid and oracle wasn't set as correct group, with command
usermod -g oinstall -G oinstall,dba,oper oracle
usermod -g oinstall -G oinstall,dba,oper grid
for the details please check below link
https://grepora.com/tag/dbca/
but still has issue after database created, when tried to clean and post configure, still raise error, but database can startup. let me check it and update laterly.
Related
I am getting error in starting PostgreSQL server after a machine restart on windows server 2019.
This server has a multiple databases and in logs it is showing error for one of the database may be corrupted.
I tried restart server few times, but it it is getting shut down after some time. How can I make server up again with other databases running?
2022-04-20 07:32:49.843 PDT [3720] LOG: starting PostgreSQL 13.3, compiled by Visual C++ build 1914, 64-bit
2022-04-20 07:32:49.844 PDT [3720] LOG: listening on IPv6 address "::", port 5432
2022-04-20 07:32:49.844 PDT [3720] LOG: listening on IPv4 address "0.0.0.0", port 5432
2022-04-20 07:32:57.949 PDT [6600] LOG: database system was interrupted while in recovery at 2022-04-20 06:29:00 PDT
2022-04-20 07:32:57.949 PDT [6600] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2022-04-20 07:34:29.599 PDT [852] FATAL: the database system is starting up
2022-04-20 07:44:04.349 PDT [2480] FATAL: the database system is starting up
2022-04-20 07:52:28.107 PDT [4800] FATAL: the database system is starting up
2022-04-20 08:09:30.847 PDT [1872] FATAL: the database system is starting up
2022-04-20 08:21:41.884 PDT [6600] LOG: could not stat file "./base/22504705": Unknown error
2022-04-20 08:21:47.121 PDT [6600] LOG: database system was not properly shut down; automatic recovery in progress
2022-04-20 08:22:01.957 PDT [6600] LOG: redo starts at 22E/5419D678 2022-04-20 08:22:01.994 PDT [6600] FATAL: could not stat directory "base/22504705": Unknown error
2022-04-20 08:22:01.994 PDT [6600] CONTEXT: WAL redo at 22E/5422EDD8 for Heap/LOCK: off 3: xid 26378859: flags 0x00 LOCK_ONLY KEYSHR_LOCK
2022-04-20 08:22:02.000 PDT [3720] LOG: startup process (PID 6600) exited with exit code 1
2022-04-20 08:22:02.000 PDT [3720] LOG: aborting startup due to startup process failure
2022-04-20 08:22:02.085 PDT [3720] LOG: database system is shut down
logs
I am trying to enable a backupset. This backupset physically exists on disk along with other backupsets. I am issuing following command which results in a error:
RMAN> change backupset 4882 available;
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of available command at 07/24/2020 14:37:16
RMAN-06160: no backup pieces found for backup set key: 4882
RMAN> list backupset 4882;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of list command at 07/24/2020 17:39:01
RMAN-06160: no backup pieces found for backup set key: 4882
RMAN>report obsolete;
Backup Set 4872 17-FEB-20
Backup Piece 4872 17-FEB-20 /oracle/app/oracle/fast_recovery_area/cc/cc/90223CE92F61074BE0536A4E110AC491/backupset/2020_02_17/o1_mf_nnnd1_DAILY_IUB_h4l_.bkp
Backup Set 4898 22-JUL-20
Backup Piece 4898 22-JUL-20
/oracle/app/oracle/fast_recovery_area/cc/cc/backupset/2020_07_22/o1_mf_nnndf_TAG20200722T233833_hkjjt55t_.bkp
Backup Set 4899 22-JUL-20
Backup Piece 4899 22-JUL-20 /oracle/app/oracle/fast_recovery_area/cc/cc/backupset/2020_07_22/o1_mf_nnndf_TAG20200722T233833_hkjjtool_.bkp
RMAN> list backup summary
4881 B A A DISK 17-FEB-20 1 1 YES
ARC_DAILY_IUB
4883 B F A DISK 21-FEB-20 1 1 NO
RMAN> validate backupset 4882;
Starting validate at 24-JUL-20
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of validate command at 07/24/2020 17:50:56
RMAN-06160: no backup pieces found for backup set key: 4882
Also, RMAN is also not listing this backupset in LIST BACKUPSET SUMMARY command though it can list other backupsets which physically exists at the same disk location.
Please help me to resolve this problem.
I was taking an RMAN backup.
RMAN> SHUTDOWN IMMEDIATE;
After Shutdown Immediate i am not able to startup database.
I have tried
conn sys#databasename as sysdba
RMAN target sys#database
lsnrctl stop start status
But i am getting this error.
C:\Users\Umair>rman target sys#ora_prep
Recovery Manager: Release 12.1.0.2.0 - Production on Mon Jul 13 00:18:00 2020
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
target database Password:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Advice, please.Thank you.
Oracle 12.1.0
Windows 10
Static listener registration:
https://docs.oracle.com/en/database/oracle/oracle-database/18/spmss/adding-static-service-to-listener.html
https://support.oracle.com/knowledge/Oracle%20Database%20Products/2312510_1.html
I have a strange case where restoring a recently created Oracle RMAN backup sometimes works and at other times does not.
We use Oracle 12c. The database is running in noarchivelog mode.
Full story: We have a large CI setup, where a node can pick up a job, build itself from the repo and run tests. For some of the tests a database build is required. To speed the tests up we
First attempt to restore the database from the backup.
If that fails we then drop the database rebuild the shell and the data. Re-create the backup and then start the tests.
The idea of course is that most of the time restore will work, in reality restore works about 40% of the time, and at other times it fails and the database is rebuild. There does not seem to be any correlation between this happening and individual nodes, it works one time and then does not work.
We use the following script to backup
rman target=/ << EOF
RUN {
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
BACKUP DATABASE;
}
EXIT;
EOF
and the following to restore
rman target=/ << EOF
RUN {
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
}
EXIT;
EOF
When things go badly it happens on the RECOVER step.
The errors are not always the same. Below are a few that I've seen
This one seems to be the most frequent recently
04:23:10 channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
04:23:10 Finished restore at 06-02-2017 04:23:10
04:23:10
04:23:10 Starting recover at 06-02-2017 04:23:10
04:23:10 using channel ORA_DISK_1
04:23:11
04:23:11 starting media recovery
04:23:11
04:23:11 archived log for thread 1 with sequence 52 is already on disk as file /oracle/oradata/DB1/redoDB11.log
04:23:11 archived log for thread 1 with sequence 53 is already on disk as file /oracle/oradata/DB1/redoDB12.log
04:23:11 archived log for thread 1 with sequence 54 is already on disk as file /oracle/oradata/DB1/redoDB13.log
04:23:11 RMAN-08187: WARNING: media recovery until SCN 1662458 complete
04:23:11 Finished recover at 06-02-2017 04:23:11
04:23:11
04:23:15 RMAN-00571: ===========================================================
04:23:15 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
04:23:15 RMAN-00571: ===========================================================
04:23:15 RMAN-03002: failure of sql statement command at 02/06/2017 04:23:14
04:23:15 ORA-01147: SYSTEM tablespace file 1 is offline
04:23:15 ORA-01110: data file 1: '/oracle/oradata/DB1/DB1_system.dbf'
04:23:15
04:23:15 RMAN>
04:23:15
04:23:15 Recovery Manager complete.
Another error
09:49:17 Finished restore at 27-01-2017 09:49:14
09:49:17
09:49:17 Starting recover at 27-01-2017 09:49:14
09:49:17 using channel ORA_DISK_1
09:49:17
09:49:17 starting media recovery
09:49:17
09:49:17 archived log for thread 1 with sequence 52 is already on disk as file /oracle/oradata/DB1/redoDB11.log
09:49:17 archived log for thread 1 with sequence 53 is already on disk as file /oracle/oradata/DB1/redoDB12.log
09:49:17 archived log for thread 1 with sequence 54 is already on disk as file /oracle/oradata/DB1/redoDB13.log
09:49:17 RMAN-08187: WARNING: media recovery until SCN 1755105 complete
09:49:17 Finished recover at 27-01-2017 09:49:15
09:49:17
09:49:17 RMAN-00571: ===========================================================
09:49:17 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
09:49:17 RMAN-00571: ===========================================================
09:49:17 RMAN-03002: failure of sql statement command at 01/27/2017 09:49:16
09:49:17 ORA-01147: SYSTEM tablespace file 1 is offline
09:49:17 ORA-01110: data file 1: '/oracle/oradata/DB1/DB1_system.dbf'
09:49:17
09:49:17 RMAN>
And one more
11:17:55 starting media recovery
11:17:55 media recovery failed
11:17:55 RMAN-00571: ===========================================================
11:17:55 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
11:17:55 RMAN-00571: ===========================================================
11:17:55 RMAN-03002: failure of recover command at 01/27/2017 11:17:55
11:17:55 ORA-00283: recovery session canceled due to errors
11:17:55 RMAN-11003: failure during parse/execution of SQL statement: alter database recover if needed
11:17:55 start until cancel
11:17:55 ORA-00283: recovery session canceled due to errors
11:17:55 ORA-16433: The database or pluggable database must be opened in read/write mode.
11:17:55
11:17:55 RMAN>
And another which is different from the above three, this one fails on RESTORE
09:14:11 Starting restore at 06-02-2017 09:14:11
09:14:11 allocated channel: ORA_DISK_1
09:14:11 channel ORA_DISK_1: SID=12 device type=DISK
09:14:12
09:14:12 creating datafile file number=1 name=/oracle/oradata/DB1/DB1_system.dbf
09:14:12 RMAN-00571: ===========================================================
09:14:12 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
09:14:12 RMAN-00571: ===========================================================
09:14:12 RMAN-03002: failure of restore command at 02/06/2017 09:14:12
09:14:12 ORA-01180: can not create datafile 1
09:14:12 ORA-01110: data file 1: '/oracle/oradata/DB1/DB1_system.dbf'
09:14:12
09:14:12 RMAN>
Any help would be much appreciated. Thank you!
In order to understand why you are getting errors, it is important to understand what each one of those pieces mean from your script:
RESTORE DATABASE;
RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
RESTORE DATABASE; copies the datafiles from your backup set back out to your database location. If the database was shutdown and consistent (was shutdown cleanly) when the backup was taken, then your backup is consistent.
RECOVER DATABASE; first attempts to make your backup consistent by applying backup archived redo logs, archived redo logs, and/or redo logs. Then, it will attempt to roll your database forward from the backup point in time until the most recent redo log. Since you are running in NOARCHIVELOG mode, this step will only produce errors like the ones you are seeing.
ALTER DATABASE OPEN RESETLOGS; brings your database on-line. RESETLOGS clears the redo logs and it is needed after an incomplete recovery (if the database couldn't roll forward and apply all of the redo from the backup archived logs, archived logs, and redo logs).
With this in mind, your script should look like the following:
RUN {
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
RESTORE DATABASE;
ALTER DATABASE OPEN RESETLOGS;
}
As a side note, you should also configure an spfile+controlfile autobackup from RMAN. This backup is automatically taken whenever you backup your database.
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
As JSapkoka said, you should also restore the spfile and controlfile first as well, which, the full restore script would look something like:
RUN {
SHUTDOWN IMMEDIATE;
STARTUP NOMOUNT;
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'autobackup_format';
RESTORE SPFILE FROM AUTOBACKUP;
SHUTDOWN IMMEDIATE;
STARTUP NOMOUNT;
RESTORE CONTROLFILE FROM AUTOBACKUP;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
ALTER DATABASE OPEN RESETLOGS;
}
I have the RMAN full database backup of oracle 10g (10.2.0.3) on Sun Solaris OS which I want to restore on oracle 11g (11.2.0.3) on Linux OS. The backup pieces were transferred to the oracle 11g server manually in binary mode. The Oracle 11g is installed on Linux OS. I have only the RMAN backup and no access to the primary database from where the backup has been taken.
-rwxrwxr-x 1 mepc dba 36356096 Jul 16 14:49 snapcf_MEPC.f
-rwxrwxr-x 1 mepc dba 166028800 Jul 16 15:29 MEPC_full_backup_MEPC_nnnbkn9f_1_1
-rwxrwxr-x 1 mepc dba 169567744 Jul 16 15:29 MEPC_full_backup_MEPC_nmnbkn9f_1_1
-rwxrwxr-x 1 mepc dba 164813824 Jul 16 15:39 MEPC_full_backup_MEPC_nonbkn9f_1_1
-rwxrwxr-x 1 mepc dba 144025600 Jul 16 16:06 MEPC_full_backup_MEPC_nqnbkn9f_1_1
-rwxrwxr-x 1 mepc dba 168576512 Jul 16 16:09 MEPC_full_backup_MEPC_npnbkn9f_1_1
-rwxrwxr-x 1 mepc dba 168649216 Jul 16 17:33 MEPC_full_backup_MEPC_o5nbkpvv_1_1
-rwxrwxr-x 1 mepc dba 162847232 Jul 16 17:34 MEPC_full_backup_MEPC_o6nbkpvv_1_1
-rwxrwxr-x 1 mepc dba 167351808 Jul 16 17:35 MEPC_full_backup_MEPC_o7nbkpvv_1_1
-rwxrwxr-x 1 mepc dba 166838272 Jul 16 17:36 MEPC_full_backup_MEPC_o8nbkpvv_1_1
-rwxrwxr-x 1 mepc dba 166876160 Jul 16 17:37 MEPC_full_backup_MEPC_o9nbkpvv_1_1
-rwxrwxr-x 1 mepc dba 327606272 Jul 16 17:54 MEPC_full_backup_MEPC_o4nbknav_1_1
-rwxrwxr-x 1 mepc dba 549658624 Jul 16 18:26 MEPC_full_backup_MEPC_o2nbknav_1_1
-rwxrwxr-x 1 mepc dba 162984448 Jul 16 18:28 MEPC_full_backup_MEPC_oanbkpvv_1_1
-rwxrwxr-x 1 mepc dba 163567616 Jul 16 18:29 MEPC_full_backup_MEPC_obnbkpvv_1_1
-rwxrwxr-x 1 mepc dba 161380352 Jul 16 18:29 MEPC_full_backup_MEPC_ocnbkpvv_1_1
-rwxrwxr-x 1 mepc dba 1072275456 Jul 18 13:52 MEPC_full_backup_MEPC_o3nbknav_1_1
-rwxrwxr-x 1 mepc dba 1813348352 Jul 18 17:00 MEPC_full_backup_MEPC_o1nbknav_1_1
-rwxrwxr-x 1 mepc dba 36438016 Jul 25 15:45 controlfile_bkup_MEPC_c-1469445140-20120522-09
the backup is taken in the above format. I know the ORACLE_SID and did of the database from which the backup has been taken.
whenever I tried the following command
mepc#tcstctmatson:/mepc_backup/May22fullbkp$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jul 31 12:14:54 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: MEPC (DBID=1595278680)
RMAN> shutdown;
using target database control file instead of recovery catalog
database closed
database dismounted
Oracle instance shut down
RMAN> startup nomount;
connected to target database (not started)
Oracle instance started
Total System Global Area 1071333376 bytes
Fixed Size 1349732 bytes
Variable Size 620758940 bytes
Database Buffers 444596224 bytes
Redo Buffers 4628480 bytes
RMAN> restore spfile to '$ORACLE_HOME/dbs/initMEPC.ora' from autobackup db_recovery_file_dest='/mepc_backup/May22fullbkp' db_name='MEPC';
the following error was notified
Starting restore at 31-JUL-12
using channel ORA_DISK_1
recovery area destination: /mepc_backup/May22fullbkp
database name (or database unique name) used for search: MEPC
channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120731
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120730
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120729
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120728
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120727
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120726
channel ORA_DISK_1: looking for AUTOBACKUP on day: 20120725
channel ORA_DISK_1: no AUTOBACKUP in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 07/31/2012 12:22:06
RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
i tried recovering the rman backup through catalog also and the following error was notified
List of Files Which Where Not Cataloged
=======================================
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nonbkn9f_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_obnbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_ocnbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o7nbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o9nbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nmnbkn9f_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nnnbkn9f_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o3nbknav_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o6nbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/controlfile_bkup_MEPC_c-1469445140-20120522-09
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_npnbkn9f_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_oanbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_nqnbkn9f_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o1nbknav_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o5nbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/snapcf_MEPC.f
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o2nbknav_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o4nbknav_1_1
RMAN-07517: Reason: The file header is corrupted
File Name: /mepc_backup/May22fullbkp/MEPC_full_backup_MEPC_o8nbkpvv_1_1
RMAN-07517: Reason: The file header is corrupted
the file is not corrupted as I checked the checksum on both the servers and it is the same.
Please help me how can I restore the RMAN oracle 10g backup in Oracle 11g and let me know where I am going wrong.
Thanks in advance.
You can not do this.
AFAIK, Solaris - assuming sparc - and Linux - assuming Intel - have different endian formats and this is your problem. You could use the migrate cross platform tablespace scenario.
see Oracle® Database Backup and Recovery Reference
If your endian format does appear to be the same, you should convert the database using rman convert database. In that case you could restore cross platform and cross version.
Not applicable for 10g/11g, but this is different in 12c:
In 12c, rman offers the option following options with the backup command:
FOR TRANSPORT: This options creates a backupset which can be transported to any destination. If the destination database uses a different endian format than the source, the endian format conversion is performed on the destination database.
TO PLATFORM: This option results in the endian format conversion to be performed on the source database and must be used by that supported platform only.
DATAPUMP: This specifies that a data pump export dump file is created while performing a cross-platform backup. The dump file is created in s separate backup set.
Use below command to restore from autobackup, RMAN knows the path and it will restore.
restore controlfile from autobackup;
You need to know first Solaris to Linux are part of same endian or not. I see that Solaris 64 but and Linux 64 bit are same endian.
Even it has same endian you will see this error when " The source Production database, has a 32KB tablespace and an initialisation parameter defined for db_32k_cache_size, but the target pfile didn't have the parameter db_32k_cache_size defined"
Set in the pfile/spfile of the target db_32k_cache_size