1.1.1. ORA-19502, ORA-27072
Date:
Environment: Testing Machine
[Error code]
$ Oerr ora 1, 19502
19502,000 00, "write error on file \" % s \ ", block number % s (block size = % s )"
// * Cause: write error on output file
// * Action: check the file
$ Oerr ora 1, 27072
27072,000 00, "File I/O error"
// * Cause: read/write/readv/writev system call returned error, additional
// Information indicates starting block number of I/O
// * Action: check errno
[Scenario description]
When the backup database plus archivelog command is executed in RMAN for database backup, an error is reported and the backup fails.
[Error message]
Error message during command execution in RMAN
Input datafile file number = 00004 name =/U01/app/Oracle/oradata/testdb/users01.dbf
Channel ORA_DISK_1: starting piece 1 at2014-05-11 23:56:38
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error messagestack follows ======================
RMAN-00571: ========================================================== ==============================
RMAN-03002: failure of backup plusarchivelog command at 05/11/2014 23:56:53
ORA-19502: write error on file "/U01/app/test/rman/fra/TESTDB/backupset/2014_05_11/o1_mf_nnndf_tag201401_t235638_9pz7fpb5 _. bkp", block number 46336 (block size = 8192)
ORA-27072: File I/O error.
Additional information: 4
Additional information: 46336
Additional information: 53248
View the alert. log:
No error message is generated.
[Error cause]
When RMAN reports an error, the system prompts that a problem occurs when the backup set file is generated. The file I/O is incorrect. Therefore, check whether the backup space is full, insufficient space is found to create backup set files.
[Solution]
Delete useless/expired backup sets, release space, and then run the BACKUP command again.
ORA-01172, ORA-01151 error handling
ORA-00600 [2662] troubleshooting
Troubleshooting for ORA-01078 and LRM-00109
Notes on ORA-00471 Processing Methods
ORA-00314, redolog corruption, or missing Handling Methods
Solution to ORA-00257 archive logs being too large to store