ORA-27069: attempt to do I/O beyond the range of the file

After reviewing this error in the alert log, I found that this was pertaining to one particular datafile.  What I did to resolve this issue was the following:

1. Go to the primary database and backup the datafile in question.  In this case, it was datafile #56.


Recovery Manager: Release 11.2.0.1.0 - Production on Tue Dec 20 21:52:01 2011


Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.


connected to target database: POC2 (DBID=1234567890)


RMAN> backup as compressed backupset datafile 56;


Starting backup at 20-DEC-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1492 instance=poc22 device type=DISK
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00056 name=+DATA/poc2/datafile/tg_ods.256.767919427
channel ORA_DISK_1: starting piece 1 at 20-DEC-11
channel ORA_DISK_1: finished piece 1 at 20-DEC-11
piece handle=/mnt/operational_dba/rman/poc2/5smuncca_1_1 tag=TAG20111220T215210 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 20-DEC-11


2. Copy over the backup piece from primary database server to standby database server (if required).


3.  Catalog the backuppiece on the standby controlfile.



RMAN> catalog backuppiece '/mnt/operational_dba/rman/poc2/5smuncca_1_1';


cataloged backup piece
backup piece handle=/mnt/operational_dba/rman/poc2/5smuncca_1_1 RECID=768 STAMP=770421285



4. Restore and recover the datafile.



RMAN> restore datafile 56;


Starting restore at 20-DEC-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1887 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 00056 to /opt/data/poc2adg/datafile/tg_ods.256.767919427
channel ORA_DISK_1: reading from backup piece /mnt/operational_dba/rman/poc2/5smuncca_1_1
channel ORA_DISK_1: piece handle=/mnt/operational_dba/rman/poc2/5smuncca_1_1 tag=TAG20111220T215210
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 20-DEC-11


RMAN> recover database noredo;


Starting recover at 20-DEC-11
using channel ORA_DISK_1


Finished recover at 20-DEC-11


RMAN> exit



5. Re-enable auto recovery on standby.


SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;

Comments

Post a Comment

Popular posts from this blog

ORA-17630: Mismatch in the remote file protocol version client 2 server 3

I was trying to create an Oracle Data Guard environment (physical standby) from an Oracle database running version 12.1.0.2. The database was running an older PSU version ("Database Patch Set Update : 12.1.0.2.161018 (24006101)") to be specific. Upon trying to build the standby by using RMAN DUPLICATE with ACTIVE DATABASE, I ran into the below error: executing Memory Script Starting backup at 16-JUL-18 RMAN-03009: failure of backup command on prm1 channel at 07/16/2018 13:51:46 ORA-17629: Cannot connect to the remote database server ORA-17630: Mismatch in the remote file protocol version client 2 server 3 continuing other job steps, job failed will not be re-run released channel: prm1 released channel: prm2 released channel: prm3 released channel: prm4 released channel: prm5 released channel: stb1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ====================...
Read more

ORA-00338: log {n} of thread {n} is more recent than control file

I received the following error in a primary database's alert log that I was supporting recently.   ORA-00312: online log 5 thread 1: '+DATA/db_name/onlinelog/group_5.297.846947859' ORA-00338: log 5 of thread 1 is more recent than control file The database has a DataGuard environment as well and below are the steps that I took to resolve the issue. 1.  First, I checked the status of the redo logs and their current sizes and status. SQL> select group#,bytes/1024/1024,status from v$log;     GROUP# BYTES/1024/1024 STATUS ---------- --------------- ----------------          1              50 INACTIVE          2              50 INACTIVE          3              50 INACTIVE          4             250 INACTIVE   ...
Read more

RMAN-10038: database session for channel prm3 terminated unexpectedly

Problem: I had an issue where I was trying to build a 1.7 TB Data Guard environment and kept receiving the highlighted error below.  I thought it was some type of fluke so I restarted the job 2 more times only to receive the same error. Fix: After researching the issue, I found it was because the sqlnet.ora needed to be configured correctly.  I added the entry " SQLNET.EXPIRE_TIME = 10 " to the sqlnet.ora on both the source and the target database servers under the RDBMS $ORACLE_HOME/network/admin.  Upon restarting the RMAN active database standby build, it was able to move past this error and built successfully. Starting backup at 07-MAY-17 channel prm1: starting datafile copy input datafile file number=00003 name=+DATA/testdb/datafile/undotbs1.262.940412881 channel prm2: starting datafile copy input datafile file number=00129 name=+DATA/testdb/datafile/welldoc1.390.940509955 channel prm3: starting datafile copy input datafile file number=00130 name=+DATA/...
Read more