Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

RMAN ORA-19502: write error on file ORA-27072: File I/O error

serandrzejMay 18 2020 — edited May 25 2020

Hello,

Oracle 11.2 no patches.

Starting backup at 16-may-2020 05:53:25

using channel ORA_DISK_1

channel ORA_DISK_1: starting compressed incremental level 0 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00001 name=/home/oracle/app/oracle/oradata/orcl/system01.dbf

....

channel ORA_DISK_1: starting piece 1 at 16-may-2020 05:53:26

channel ORA_DISK_1: finished piece 1 at 16-may-2020 05:59:41

...

piece handle=/home/oracle/backup/ORCL/ch1_1qv0akqm_4_1.bk tag=TAG20200516T055325 comment=NONE

channel ORA_DISK_1: starting piece 5 at 16-may-2020 06:18:56

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of backup plus archivelog command at 05/16/2020 06:21:39

ORA-19502: write error on file "/home/oracle/backup/ORCL/ch1_1qv0akqm_5_1.bk", block number 193665 (block size=8192)

ORA-27072: File I/O error

Linux-x86_64 Error: 25: Inappropriate ioctl for device

Additional information: 4

Additional information: 193665

Additional information: 245760

Yesterday and today backup worked fine:

24419   B  A  A DISK    15-MAY-20   1   1   YES    TAG20200515T050008
24420   B  0  A DISK    15-MAY-20   7   1   YES    TAG20200515T054356
24421   B  A  A DISK    15-MAY-20   1   1   YES    TAG20200515T062352
24422   B  F  A DISK    15-MAY-20   1   1   NO     TAG20200515T062427
24434   B  A  A DISK    16-MAY-20   1   1   YES    TAG20200516T050010

...

24443   B  A  A DISK    16-MAY-20   1   1   YES    TAG20200516T050010
24452   B  A  A DISK    17-MAY-20   1   1   YES    TAG20200517T050008

...

24465   B  0  A DISK    17-MAY-20   7   1   YES    TAG20200517T055221
24466   B  A  A DISK    17-MAY-20   1   1   YES    TAG20200517T063207
24467   B  F  A DISK    17-MAY-20   1   1   NO     TAG20200517T063242
24470   B  A  A DISK    18-MAY-20   1   1   YES    TAG20200518T050008

...

24486   B  0  A DISK    18-MAY-20   7   1   YES    TAG20200518T054520
24487   B  A  A DISK    18-MAY-20   1   1   YES    TAG20200518T062516
24488   B  F  A DISK    18-MAY-20   1   1   NO     TAG20200518T062551

Any idea what could happen 16th of May ? As next two days all was ok can I ignore this failure or it should be checked ?

Thanks in advance !

This post has been answered by Dude! on May 18 2020
Jump to Answer

Comments

Post Details

Added on May 18 2020
5 comments
7,836 views