UrgentCan't restore/ORA-19723:Cannot recreate plugged in read-onlydatafile

I created this rman backup before I droped the tablespace and used the tansportable tablespaces to plug in two tablespaces.
Later on I wanted to use the backup with tag "before_drop_tablespace" to bring back the databases but got following errors.
creating datafile fno=5 name=/u01/app/oracle/oradata1/REQTST02/req_index_ts01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 04/30/2008 15:17:21
ORA-19723: Cannot recreate plugged in read-only datafile 5
ORA-01110: data file 5: '/u01/app/oracle/oradata1/REQTST02/req_index_ts01.dbf'

You are getting this error because your tablespace is read only. If you want to bring the database to a state before you dropped the tablespace, you need to perform point-in-time recovery.

Similar Messages

ORA-19723: while restoring datafile from backup

I am getting ORA-19723: Cannot recreate plugged in read-only datafile ... while restoring datafles. All datafiles are online and in read_write mode on the database. Tablespaces are also online.
This same backup has worked before.
This most be a misleading error...
Please comment/advise
Thanks

These particular files were not restored/copied to the specified location with set newname.
All the files have plugged_in=0 as stated below
+USADBP_DATA_01/usadbp/repl_mgr_data01.dbf
0

Ora-1276 cannot add controlfile - rman duplicate asm database

Hi,
I am trying to duplicate an asm database olddb -> asm database dup in the same diskgroup. somehow got error 0ra-1276 Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.
There is nothing in the asm directory +DISK1/dup/controllfile before I run the rman.
in the initdup.ora
control_files=+DISK1,+DISK1 <--- just the disk group, not the file name
db_name='dup'
db_file_name_convert=+DISK1,+DISK1/dup
log_file_name_convert=+DISK1,+DISK1
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Jun 18 20:58:06 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect target sys/oracle@OLDDB
connect auconnected to target database: OLDDB (DBID=1142960293)
RMAN> xiliary /
connected to auxiliary database: DUP (not mounted)
RMAN> duplicate target database to dup
logfile group 1 ('+DISK1/dup') size 200k ,
group 2 ('+DISK1') size 200k;
2> 3>
Starting Duplicate Db at 2011/06/18 20:58:39
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=153 devtype=DISK
WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
contents of Memory Script:
set until scn 1613638;
set newname for datafile 1 to
"+DISK1";
set newname for datafile 2 to
"+DISK1";
set newname for datafile 3 to
"+DISK1";
set newname for datafile 4 to
"+DISK1";
set newname for datafile 6 to
"+DISK1";
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 2011/06/18 20:58:42
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DISK1
restoring datafile 00002 to +DISK1
restoring datafile 00003 to +DISK1
restoring datafile 00004 to +DISK1
restoring datafile 00006 to +DISK1
channel ORA_AUX_DISK_1: reading from backup piece +DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=+DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731 tag=TAG20110522T000530
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:06
Finished restore at 2011/06/18 20:59:48
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUP" RESETLOGS ARCHIVELOG
MAXLOGFILES 192
MAXLOGMEMBERS 3
MAXDATAFILES 1024
MAXINSTANCES 32
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '+DISK1/dup' ) SIZE 200 K ,
GROUP 2 ( '+DISK1' ) SIZE 200 K
DATAFILE
'+DISK1/dup/datafile/system.1674.754174727'
CHARACTER SET WE8ISO8859P1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/18/2011 20:59:48
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.
RMAN>
thank you very much for your help.
thanks
andrew

RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181. File has an Oracle Managed Files file name.Are you sure is it running under pfile?
Ok, connect to auxiliary intance and post
show parameter db_create
show parameter control_filesIn your pfile, Have you mentioned single quotes?
If your database with OMF then if you give it as below. as there is some work around
Control_files='+DISK1/DUP/controlfile/control01.ctl','+DISK1/DUP/controlfile/control02.ctl'
Check this too *Ora-1276 Error Recreating The Controlfile When Using +Asm [ID 303187.1]*

HT1212 I am unable to get our of a continuous cycle when trying to update or restore my iPad 2. Plug in to iTunes 12.0.1 (latest version). Click update, told can't update, have to restore. Restore fails with error 9. Any help appreciated.

When I tried to update my iPad I got an error 9. Now, I am unable to access my iPad. It is in a continuous cycle when I try to update or restore the iPad 2. Plug in to iTunes 12.0.1 (latest version). Click update, told can't update, have to restore. Restore fails with error 9. Any help appreciated.
Here's the cycle:
I plug in my iPad when “cable to iTunes shows on iPad screen. It says "Your iPad can't be updated, you must restore it to factory settings." That bad enough news, but it gets worse.
Click Restore
Extracting software…
Preparing iPad for restore
Waiting for iPad…
Verifying iPad restore with Apple…
(empty bar under the Apple logo…does not show any activity)
“The iPad “iPad” could not be restored. An unknown error occurred (9).”
Notes: I just upgraded to OS X Yosemite 10.10.1 on my iMac (27-inch, Mid 2011) in the last week. It’s the first time I’m tried to backup/update my iPad since the iMac update.
I swapped out the USB cable to a new cable and get the same results.
I also unplugged all other USB devices from the iMac and security on my iPad and still get the same results.
I find it strange that it shows no Serial number for my my iPad 2 when plugged in. It shows “Serial Number: n/a on the screen when it displays: “iPad Recovery Mode To update your iPad without erasing its contents, click Update. To restore your iPad to its factory settings, click Restore iPad.
I prefer to update my iPad, but it displays “Your iPad can’t be updated, you must restore it to factory settings. If you previously backed up the iPad, click Restore Backup after the restore process completes.”
It’s a continuous loop. I get the display on my iPad to plug in the iPad to iTunes, plug it in which ends after going through the above procedure saying an error occurred (9).
So now I cannot use my iPad. When I turn it on I get the display showing me to plug it into iTunes with the cable. Since this is the only option I have I plug it in and the loop begins.
Any advice would be appreciated.
Thanks!

Hello jaybearden,
Thanks for the question. After reviewing your post, it sounds like you are not able to restore the iOS device since you get an error 9. I would recommend that you read this article, it may be able to help the issue.
Resolve iOS update and restore errors - Apple Support
Check your security software
Related errors: 2, 4, 6, 9, 1000, 1611, 9006. Sometimes security software can prevent your device from communicating with either the Apple update server or with your device.
Check your security software and settings to make sure that they aren't preventing a connection to the Apple servers.
Thanks for using Apple Support Communities.
Have a nice day,
Mario

RMAN-03009: failure of delete command on ... ORA-19606: Cannot copy or rest

one server using 11.2.0.1.0 under Suse Linux
configured catalog db, main db & jobs & ... almost everything with enterprise manager
keep backups 14 days
To make 14 full online dumps I had to aktive the archive mode and try to get rid of thoose unwanted additional files.
Additional I make every night (less til no db activity) a dump and compress it myself.
After some days the backupjob complain that it can not delete old files.
EM / manage all backups / crosscheck all(
CROSSCHECK BACKUPSET;
CROSSCHECK COPY;
sucessful
EM / manage all backups / delete old backups
DELETE NOPROMPT OBSOLETE;
failed.
script result
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 17:20:55 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: <SID> (DBID=773091283)
RMAN>
connected to recovery catalog database
RMAN>
echo set on
RMAN> DELETE NOPROMPT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=196 device type=DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Control File Copy 3831 03-AUG-10 /opt/oracle/base/product/11gR1/db/dbs/snapcf_<SID>.f
Backup Set 18750 23-AUG-10
Backup Piece 18754 23-AUG-10 /srv/ora/data/flash_recovery_area/<SID>/backupset/2010_08_23/o1_mf_nnndf_BACKUP_<SID>CH0_673c0hbp_.bkp
Backup Set 18751 23-AUG-10
Backup Piece 18755 23-AUG-10 /srv/ora/data/flash_recovery_area/<SID>/backupset/2010_08_23/o1_mf_nnndf_BACKUP_<SID>CH0_673c0hbo_.bkp
Backup Set 19479 24-AUG-10
Backup Piece 19482 24-AUG-10 /tmp/o0lm3qh9_1_1
Backup Set 19490 24-AUG-10
Backup Set 20087 24-AUG-10
Backup Piece 20089 24-AUG-10 /srv/ora/data/flash_recovery_area/<SID>/autobackup/2010_08_24/o1_mf_s_727891232_677n40r3_.bkp
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_DISK_1 channel at 09/07/2010 17:20:57
ORA-19606: Cannot copy or restore to snapshot control file
exit;
Recovery Manager complete.
google found some questions, but not fittung answers.
So far:
- I checked the folder & users rights.
- I found some /tmp/ files - yes I "backup" the backuped archivelogs to-delete files in /tmp - I only active archivelogmode so I can onlinebackup
- I managed to login via rman and execute DELETE OBSOLETE manual - result above.
- Actual I delete the set one by one to find the problem set. (delete backupset 12345 ) from the list manually.
Some a good idea what went wrong?
additional: Is there a way to let oracle delete the empy archvielog-directories after deleting the logs within?
18:00- the command "RMAN> BACKUP CURRENT CONTROLFILE" also fails.
Edited by: 793286 on 07.09.2010 09:00

Meanwhile I managed to delete all backupsets one by one.
The problem with $ORACLE_HOME/dbs/snapcf_<SID>.f persists.
cd $ORACLE_HOME/dbs
mv snapcf_<SID>.f snapcf_<SID>.f.bak
# replaced actual dbsidname with <SID>
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Control File Copy 3831 03-AUG-10 /opt/oracle/base/product/11gR1/db/dbs/snapcf_TARMED1P.f
Do you really want to delete the above objects (enter YES or NO)? y
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_DISK_1 channel at 09/08/2010 09:44:07
ORA-19606: Cannot copy or restore to snapshot control file
mv snapcf_<SID>.f.bak snapcf_<SID>.fRMAN> backup current controlfile;
Starting backup at 08-SEP-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed 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 08-SEP-10
channel ORA_DISK_1: finished piece 1 at 08-SEP-10
piece handle=/srv/ora/data/flash_recovery_area/TARMED1P/backupset/2010_09_08/o1_mf_ncnnf_TAG20100908T095000_68gj1b2m_.bkp tag=TAG20100908T095000 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 08-SEP-10
Starting Control File and SPFILE Autobackup at 08-SEP-10
piece handle=/srv/ora/data/flash_recovery_area/TARMED1P/autobackup/2010_09_08/o1_mf_s_729165003_68gj1d1b_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 08-SEP-10
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 14 days
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
Control File Copy 3831 03-AUG-10 /opt/oracle/base/product/11gR1/db/dbs/snapcf_<SID>.f
Do you really want to delete the above objects (enter YES or NO)? y
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_DISK_1 channel at 09/08/2010 09:52:37
ORA-19606: Cannot copy or restore to snapshot control file
No different effect, if I changed the filename via 2nd terminal to .bak or not.
RMAN> delete controlfilecopy 3831;
will fail, if the file exists or not.
Any chance to reset/kill that file?
Is there a need to restart the dbms after rename the file?

ORA -18808;Cannot find OUTLN schema using Database Link

Hi,
I have to access a database using a database link. When I try to do so I get the message:
ORA -18808:cannot find OUTLN schema
The OUTLN schema really does'nt exist at the target database, but I don't get the message when connecting with the same user outside the database link.
I am trying to avoid to ask them to recreate the schema, since I am the only one that needs the database link working.
Is there any way I can access the database with the database link without messing with the target database?
Thanks in advance for any help.

The error number returned by that error does not seem to be correct. Below is the correct error number:
ORA-18008 cannot find OUTLN schema
Cause: The database creation script that creates this schema must not have been executed.
Action: Review the log files to see what happened when the database was created.
How is the DB link defined to connect as?

Java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DB

I am deploying my application components on Oracle RAC database, when i install my app component i will run a script which creates a user and tablespace on bot rac-nodes(node1 and node2)
as database is clustered, the user are created on 2 nodes and tablespace is stored in a shared location for two rac nodes
i am able to successfully run my script on rac-node1 and and installed my component and when i started installing the app component on node2 getting error
java.sql.SQLException: ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: '/db/db/db/ora10g/10.2.0/admin/dbadmin_01.dbf'
ORA-06512: at "ADMIN.XL_SP_DBCHECK", line 48
ORA-06512: at line 1
"dbadmin_01.dbf is the custom tablespace which created by me"
i a mgetting error while installing the app component on rac-node2

You should not create database files outside of the ASM.
I'm not sure you can move the datafile, I would export the data from the tablespace (if there is data you need there), delete the tablespace and recreate it in the ASM, then import the data back.
If you want to move the datafile, you can try using RMAN (from node1).
First connect to the database with sqlplus and execute:
alter tablespace <tbs_name> offline;Then start RMAN: rman target /
BACKUP AS COPY DATAFILE '<file>' FORMAT '+<ASM_DG>';Then in sqlplus, execute:
alter tablespace <tbs_name> online;I'm not sure it will work, and I hope I got the commands right because I can't check it right now.
Good luck
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Autconfig error : ORA-01400: cannot insert NULL into ("APPLSYS"."FND_NODES"."NODE_NAME")

Good day,
I am running EBS 11.5.10 with DB 10.2.0.4. I applied patch 7429271 following the steps in Doc Id. 233044.1.
After restarting the application, I got a "node id does not exist for the current application" when the forms started.
After purging fnd nodes (exec fnd_conc_clone.setup_clean) I ran autoconfig successfully on the dbtier but got the error below in the apps tier.
I also noticed that the contents of my dbc file has been erased and replaced with the template data (all values are default). I tried restoring it but it just got over written again with default data.
Hope my explanation was clear enough.
Any suggestions?
---error from adconfig.log-----------
Unique constraint error (00001) is OK if key already exists
java.sql.SQLException: ORA-01400: cannot insert NULL into ("APPLSYS"."FND_NODES"."NODE_NAME")
ORA-06512: at "APPS.FND_CONCURRENT", line 1504
ORA-06512: at "APPS.FND_APP_SERVER_PKG", line 163
ORA-06512: at line 1
- Database error modifying the server

Logs after autoconfig and services started - not connection attempted to the application yet.
-----access log--------
mobay.pahq.dom - - [25/Oct/2013:13:28:59 -0500] "GET /oprocmgr-service?cmd=Register&index=0&modName=JServ&grpName=XmlSvcsGrp&port=19000 HTTP/1.1" 200 15 0
mobay.pahq.dom - - [25/Oct/2013:13:28:59 -0500] "GET /oprocmgr-service?cmd=Register&index=0&modName=JServ&grpName=DiscoGroup&port=17000 HTTP/1.1" 200 15 0
mobay.pahq.dom - - [25/Oct/2013:13:28:59 -0500] "GET /oprocmgr-service?cmd=Register&index=0&modName=JServ&grpName=OACoreGroup&port=16000 HTTP/1.1" 200 15 0
----error log--------
[Fri Oct 25 13:28:59 2013] [notice] Oracle HTTP Server Powered by Apache/1.3.19 configured -- resuming normal operations
----error log_pls----
[Fri Oct 25 13:29:00 2013] [notice] Oracle HTTP Server Powered by Apache/1.3.19 configured -- resuming normal operations
Logs after a connection attempt to the application
-----access log-----
mobay.pahq.dom - - [25/Oct/2013:13:28:59 -0500] "GET /oprocmgr-service?cmd=Register&index=0&modName=JServ&grpName=XmlSvcsGrp&port=19000 HTTP/1.1" 200 15 0
mobay.pahq.dom - - [25/Oct/2013:13:28:59 -0500] "GET /oprocmgr-service?cmd=Register&index=0&modName=JServ&grpName=DiscoGroup&port=17000 HTTP/1.1" 200 15 0
mobay.pahq.dom - - [25/Oct/2013:13:28:59 -0500] "GET /oprocmgr-service?cmd=Register&index=0&modName=JServ&grpName=OACoreGroup&port=16000 HTTP/1.1" 200 15 0
192.168.50.80 - - [25/Oct/2013:13:34:32 -0500] "GET / HTTP/1.1" 200 2589 0
192.168.50.80 - - [25/Oct/2013:13:34:33 -0500] "GET /apptitle.html HTTP/1.1" 200 1015 0
192.168.50.80 - - [25/Oct/2013:13:34:33 -0500] "GET /applist.html HTTP/1.1" 200 1602 0
192.168.50.80 - - [25/Oct/2013:13:34:33 -0500] "GET /appdet.html HTTP/1.1" 200 1009 0
192.168.50.80 - - [25/Oct/2013:13:34:33 -0500] "GET /appsmed3.gif HTTP/1.1" 200 1981 0
192.168.50.80 - - [25/Oct/2013:13:34:36 -0500] "GET /aplogon.html HTTP/1.1" 200 1953 0
192.168.50.80 - - [25/Oct/2013:13:34:38 -0500] "GET /OA_HTML/US/ICXINDEX_PROD_mobay.htm HTTP/1.1" 200 417 0
192.168.50.80 - - [25/Oct/2013:13:34:38 -0500] "GET /OA_HTML/AppsLocalLogin.jsp HTTP/1.1" 200 411 0
**the error logs remain unchanged.
Regards,
Shridath.

ORA-01157: cannot identify/lock data file error in standby database.

Hi,
i have a primary database and standby database (11.2.0.1.0) running in ASM with different diskgroup names. I applied an incremental backup on standby database to resolve archive log gap and generated a controlfile for standby in primary database and restored the controlfile in standby database.But when i started the MRP process its not starting and thows error in alert log ORA-01157: cannot identify/lock data file. When i queried the standby database file it shows the location on primary database datafiles names not the standby database.
PRIMARY DATABASE
SQL> select name from v$datafile;
NAME
+DATA/oradb/datafile/system.256.788911005
+DATA/oradb/datafile/sysaux.257.788911005
+DATA/oradb/datafile/undotbs1.258.788911005
+DATA/oradb/datafile/users.259.788911005
STANDBY DATABASE
SQL> select name from v$datafile;
NAME
+STDBY/oradb/datafile/system.256.788911005
+STDBY/oradb/datafile/sysaux.257.788911005
+STDBY/oradb/datafile/undotbs1.258.788911005
+STDBY/oradb/datafile/users.259.788911005
The Actual physical location of standby database files in ASM in standby server is shown below
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
ASMCMD>
ASMCMD> ls
SYSAUX.259.805921967
SYSTEM.258.805921881
UNDOTBS1.260.805922023
USERS.261.805922029
ASMCMD>
ASMCMD> pwd
+STDBY/11gdb/DATAFILE
i even tried to rename the datafiles in standby database but it throws error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Regards,
007

Hi saurabh,
I tried to rename the datafiles in standby database after restoring it throws the below error
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01275: Operation RENAME is not allowed if standby file management is
automatic.
Also in my pfile i have mentioned the below parameters
*.db_create_file_dest='+STDBY'
*.db_domain=''
*.db_file_name_convert='+DATA','+STDBY'
*.db_name='ORADB'
*.db_unique_name='11GDB'
Regards,
007

Blockrecover but full datafile restore + ORA-01193

Hi,
We have a proplem, here is a short sescription:
We have corrupt blocks, how can we solve this problem? Blockrecover uses full datafile restore and finally fails with ORA-01193.
Here is a detailed description:
We have a 330GB datafile (bigfile tablespace) with 46 corrupt block.
DB version 10.2.0.4, Oracle linux, we use ASM.
We would repair these blocks.
V$DATABASE_BLOCK_CORRUPTION after "backup validate check logical datafile 7" :
FILE#     BLOCK#     BLOCKS     CORRUPTION_CHANGE#     CORRUPTION_TYPE
7     16872378     1     0     FRACTURED
7     16872408     40     0     CORRUPT
7     16872379     5     0     CORRUPT
The result is similar by dbv.
We have archivelog mode and backupset created by rman command:
backup as compressed backupset incremental level 0 database;
All of the corrupted blocks are in 1 LOB segment.
We copied the LOB segment, only 5 record cannot be read.
The corrupted LOB segment (and table) was exchanged by the copied (not corrupted) data, so users can work.
We remained the corrupted LOB segment in the database, but it is not in use.
I started blockrecovery by command:
BLOCKRECOVER DATAFILE 7 BLOCK 16872378,...,16872447;
The listed blocks are same as in the V$DATABASE_BLOCK_CORRUPTION, so the command could be:
BLOCKRECOVER CORRUPTION LIST;
The database was opened during blockrecocer and the datafile 7 was online.
A line appeared in the V$SESSION_LONGOPS with:
"RMAN: full datafile restore"
The restore was more than 4 hours, and finally it is failed with error:
Starting blockrecover at 29-AUG-12
starting media recovery
ORA-01193 file % is not the same file seen at start of recovery
Based on V$SESSTAT there were lot of physical read but only some physical write.
Maybe full datafile read, and only corrupted blocks was changed, but I didn't check it exactly.
We retried blockrecover with only one block, but the result was same: it failed after 4 hours with ORA-01193.
We retried the blockrecovery on a mounted but not opened database, and the datafile was offline:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE DATAFILE 7 offline
BLOCKRECOVER ...
The result was same: it failed after 4 hours with ORA-01193.
rman backup failed with error:
RMAN : ORA-19566: exceeded limit of 0 corrupt blocks for file %
After set maxcorrupt, rman backup ran successfuly
SET MAXCORRUPT FOR DATAFILE 7 TO 46;
Based on our current info, these workaround seems best for us:
- rman "set maxcorrupt"
- DB_BLOCK_CHECKING=FULL
- drop corrupted (but copied and not used segment)
- wait until corrupted blocks will be reallocated (checking it periodically by dbv)
- set maxcorrupt to 0
Our questions are:
*1. Why oracle uses "RMAN: full datafile restore" during blockrecover?*
Why needed to read the whole datafile?
One of the advantage of blockrecover should be the relative small IO, and fast restore.
I found only 2 results in google for "blockrecover" and "RMAN: full datafile restore".
(One of the findings was in this forum, but it was no answer for our problem)
*2. ORA-01193: file is not the same, but why?*
It is strange on opened database and online datafile, because other advantage of blockrecover should be the online recovery.
But it is more-more strange on closed(mounted) database and offline datafile. Only the rman blockrecover could change this file.
I found only 3 results in google for "blockrecover" "ORA-01193"
I found only the oerr output in google for "ORA-01193". But what does it mean? Only the rman blockrecover could change this file.
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
Action: Ensure the correct file is available, then retry recovery.
*3. What else can be do to repair these corrupt blocks? What can we do for success blockrecover, or is there any other idea?*
Other infos:
- DB_BLOCK_CHECKING was false, but we changed it to FULL to avoid the subsequent corruptions
ALTER SYSTEM SET DB_BLOCK_CHECKING = FULL scope=both
- DBMS_REPAIR cannot detect the (out-of-line) LOB segment errors.
- rman SET MAXCORRUPT is not a "calming" solution
- When I read on internet, when we drop the corrupted LOB segments, the blocks will remains corrupt.
And the block will be repaired/formatted only when a new segment will allocate these blocks.
Based on metalink 336133.1, we can ensure the new allocation by fill the datafile with dummy data until the corrupted blocks will be allocated.
But this is a very IO intensive task.
- full recovery
very IO intensive, we try to avoid it.
Thx: lados.

Hi,
other infos:
We use ASM, and one of the disk is dropped and added after the last full (incremental level 0) backup. Can this premise causes the slow restore (something physical storage info is changed), or the ORA-01193 error (file % is not the same file seen at start of recovery) ? I don't think that a full db backup is needed after ASM disk drop/add/rebalance. But we tried a full backup (this was when the corrupt block first appeared with ORA-19566).
I found only one finding in the metalink for ORA-01193. The oerr reference (cause,action). It would be strange, if nobady else had problem with this error.
Thx: lados.

ORA-00210: cannot open the specified control file

Hi all,
Initially we faced the following error:
ORA-00214: control file '+DBDG/dws/controlfile/current.256.638648487' version
75647 inconsistent with file '+FLASHDG/dws/controlfile/current.256.638648489'
version 75645
Then the following action:
RMAN> restore controlfile from autobackup;
Starting restore at 05-DEC-07
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=997 devtype=DISK
recovery area destination: +flashdg
database name (or database unique name) used for search: DWS
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: +flashdg/DWS/AUTOBACKUP/2007_12_04/s_640476511.697.640476513
channel ORA_DISK_1: control file restore from autobackup complete
output filename=+DBDG/dws/controlfile/current.256.638648487
output filename=+FLASHDG/dws/controlfile/current.256.638648489
Finished restore at 05-DEC-07
RMAN> recover database;
Starting recover at 05-DEC-07
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/05/2007 15:16:10
ORA-00210: cannot open the specified control file
RMAN>
Any idea why this is happening?
Regards,
Soma Sekhar Karri

Something which you should have looked up prior to posting
00210, 00000, "cannot open the specified controlfile"
// *Cause: Cannot open the controlfile.
// *Action: Check to make sure the controlfile exists and is not locked by
// some other program.
Sybrand Bakker
Senior Oracle DBA

ORA-01407: cannot update ("APEX_040000"."WWV_FLOW_PLUGIN_FILES"."MIME_TYPE)

Hi,
I am getting the following error message when I tried to upload .js file (Plugin creation).
ORA-01407: cannot update ("APEX_040000"."WWV_FLOW_PLUGIN_FILES"."MIME_TYPE") to NULL
Unable to process row of table WWV_FLOW_PLUGIN_FILES.
Regards

Hi Michelle,
can you please report that in the APEX Listener forum ORDS, SODA & JSON in the Database with your exact version number of the APEX Listener you are using.
Thanks!
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins

Error ORA-20003: Cannot read file/... in Cash Management?

Dear All.
I am having this Error in the Cash Management Module on the bank statement load process
Error ORA-20003: Cannot read file /software/d01/oracle/interface/finance/inbound/email.9Nemail.13111507.3445704.cnv.
How do I resolve this error.
Thank you.

Hi Lucy,
The error is probably due to one of the reasons:
1. There is no file in the location: /software/d01/oracle/interface/finance/inbound/email.9Nemail.13111507.3445704.cnv.
2. No permission on the file respective file.
Please get the assistance from the DBA to check on this.
Thanks &
Best Regards,

ORA-00604: error occured at recursive SQL level 1 ORA-12705: Cannot access

Oracle Database 10g Express Edition Release 10.2.0.1.0 on
OS Linux Debian 3.1_r4_stable
SQL> select userenv('LANGUAGE') from dual;
USERENV('LANGUAGE')
RUSSIAN_RUSSIA.AL32UTF8
Client OS MS Vista Ultimate EN , region=RUSSIAN.RUSSIA
Oracle Developer suite 10
SQL-Developer
Version 1.1.0.23.
NLS_LANG=RUSSIAN_RUSSIA.CL8MSWIN1251
Oracle Developer suite 10 is working properly but when
i am attempting a connection between Oracle 10g XE and SQL-Developer.
Need some help to resolve this error message....
ORA-00604: error occured at recursive SQL level 1 ORA-12705: Cannot access NLS data files or invalid enviroment specified

Hi,
You have to set NLS_LANG before connect to Oracle Database.
$export NLS_LANG=.AL32UTF8

ORA-12032: cannot use rowid column

Hi,
on 8.1.7 I have the following error :
ORA-12032: cannot use rowid column from materialized view log on "string"."string"
The solution is :
Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required.
How can I do a complete refresh before the next fast refresh or Add ROWID columns ? How to know if Add ROWID columns is required ?
Thank you.
PS :
my script is :
START WITH TO_DATE('06-jul-2010 17:57:48','dd-mon-yyyy hh24:mi:ss')
NEXT SYSDATE+1/24

user522961 wrote:
Hi,
on 8.1.7 I have the following error :
ORA-12032: cannot use rowid column from materialized view log on "string"."string"
The solution is :
Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required.
How can I do a complete refresh before the next fast refresh or Add ROWID columns ? How to know if Add ROWID columns is required ?
Thank you.run above
EXECUTE DBMS_MVIEW.REFRESH('MV_NAME','C');

UrgentCan't restore/ORA-19723:Cannot recreate plugged in read-onlydatafile

Similar Messages

Maybe you are looking for