ORA-19625: error identifying file /u01/backup1_7_1132351466.dbf ORA-27037: unable to obtain file status

Rameshdba.com

 The contents are of my own testing and deployments. Not guaranteed that these might work in your environment. Please test before usage.

In this blog, I will teach you How to solve the above ora error!

Cause: Users try to take an archive log backup in rman.

But they are getting below error!


Error:

channel ORA_DISK_24: SID=372 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/14/2023 22:31:52
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file /u01/backup1_7_1132351466.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3


Solution :

1)The Rman utility is not able to find the archive log location that's why we are getting the above error.

Let's see the practical session.

Connect the RMAN utility then fire the Crosscheck archivelog all.

RMAN>  crosscheck archivelog all;

released channel: ORA_DISK_1
released channel: ORA_DISK_2
released channel: ORA_DISK_3
released channel: ORA_DISK_4
released channel: ORA_DISK_5
released channel: ORA_DISK_6
released channel: ORA_DISK_7

2)Now try to backup those archive logs, 

RMAN> backup archivelog all;

Starting backup at 14-APR-23
current log archived
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
using channel ORA_DISK_4
using channel ORA_DISK_5
using channel ORA_DISK_6
using channel ORA_DISK_7
using channel ORA_DISK_23
using channel ORA_DISK_24
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=30 RECID=24 STAMP=1134167261
channel ORA_DISK_1: starting piece 1 at 14-APR-23
channel ORA_DISK_2: starting archived log backup set
channel ORA_DISK_2: specifying archived log(s) in backup set
input archived log thread=1 sequence=28 RECID=22 STAMP=1133974236
channel ORA_DISK_2: starting piece 1 at 14-APR-23
channel ORA_DISK_3: starting archived log backup set
channel ORA_DISK_3: specifying archived log(s) in backup set
input archived log thread=1 sequence=31 RECID=25 STAMP=1134167503
channel ORA_DISK_3: starting piece 1 at 14-APR-23
channel ORA_DISK_4: starting archived log backup set
channel ORA_DISK_4: specifying archived log(s) in backup set
input archived log thread=1 sequence=29 RECID=23 STAMP=1134167188
channel ORA_DISK_4: starting piece 1 at 14-APR-23
channel ORA_DISK_5: starting archived log backup set
channel ORA_DISK_5: specifying archived log(s) in backup set
input archived log thread=1 sequence=27 RECID=21 STAMP=1133948927
channel ORA_DISK_5: starting piece 1 at 14-APR-23
channel ORA_DISK_6: starting archived log backup set
channel ORA_DISK_6: specifying archived log(s) in backup set
input archived log thread=1 sequence=32 RECID=26 STAMP=1134167593
channel ORA_DISK_6: starting piece 1 at 14-APR-23
channel ORA_DISK_3: finished piece 1 at 14-APR-23
piece handle=/u01/ramesh/backup/Ramesh_FULL_PROD_t1134167594_s71_p1 tag=TAG20230414T223313 comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_4: finished piece 1 at 14-APR-23
piece handle=/u01/ramesh/backup/Ramesh_FULL_PROD_t1134167594_s72_p1 tag=TAG20230414T223313 comment=NONE
channel ORA_DISK_4: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_6: finished piece 1 at 14-APR-23
piece handle=/u01/ramesh/backup/Ramesh_FULL_PROD_t1134167594_s74_p1 tag=TAG20230414T223313 comment=NONE
channel ORA_DISK_6: backup set complete, elapsed time: 00:00:01
channel ORA_DISK_1: finished piece 1 at 14-APR-23
piece handle=/u01/ramesh/backup/Ramesh_FULL_PROD_t1134167594_s69_p1 tag=TAG20230414T223313 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_2: finished piece 1 at 14-APR-23
piece handle=/u01/ramesh/backup/Ramesh_FULL_PROD_t1134167594_s70_p1 tag=TAG20230414T223313 comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:00:03
channel ORA_DISK_5: finished piece 1 at 14-APR-23
piece handle=/u01/ramesh/backup/Ramesh_FULL_PROD_t1134167594_s73_p1 tag=TAG20230414T223313 comment=NONE
channel ORA_DISK_5: backup set complete, elapsed time: 00:00:03
Finished backup at 14-APR-23

RMAN>

                                        Thanks for your time!











0 Comments

DELETE Statement in ORACLE DB— Step by Step Internal Flow with classroom example.

by
Imagine your Oracle database like a school, and you’re Teacher decides to remove a student (row) from the classroom(table). Let’s see how the journey works step by step: 1)Classroom = Oracle Table 2)Students = Rows (Records) 3)Class Teacher = Oracle Server Process 4)Attendance Register = Data Dictionary User fires DELETE statement: DELETE FROM students WHERE grade = 'D'; Internal Processing Steps: Client Process Sends DELETE Statement to Server Process The teacher receives a request to remove a student from the classroom. Syntax Check (Parsing) The teacher checks if the request is grammatically correct — proper command, keywords, and a semicolon. Semantic Check Teacher verifies if the classroom exists and whether the condition (like grade = 'D') makes sense. Object Resolution Teacher confirms that the ‘students’ classroom (table) exists in the school records (data dictionary). Optimization Decides the fastest way to find those students — by roll number, grade, or al...
Image