Scenario:
A stand alone database is getting converted to RAC/ASM using rconfig command, which internally uses RMAN for the conversion.
DB Version: 11.2.0.3.0
The DB conversion was failing every time on the redo logs addition phase of the conversion.
The source database was in an NFS shared storage. And the conversion was to an Exadata box.
Error:
ORA-00321: log 1 of thread 1, cannot update log file header
ORA-00312: online log 1 thread 1: '/redo_log_path/log3.dbf'
ORA-27072: File I/O error
Linux-x86_64 Error: 12: Cannot allocate memory
Verification:
Since there was not much beyond the above mentioned error in any of the log files, it was difficult to fix the issue. The DB folder had to be physically removed from the ASM instance each time rconfig was run, on the basis of a trial and error approach. This is because the DB instance creation was succesfull every time when rconfig is run.
Luckily we got hold of a support doc which had resemblance with the issue we had.
The Doc ID: 1532488.1 was about failure of RMAN and EXPDP in NFS mount, when Exadata11.2.3.2.1 image is used.
Solution:
Applied patch 16432033 on all compute nodes.
Restarted the RAC conversion after restoring DB from a backup
The patch helped in fixing the error and RAC/ASM conversion was successful.
Note: The patch is not persistent across reboots. If the system is rebooted, the customer needs to reapply the patch each time
A stand alone database is getting converted to RAC/ASM using rconfig command, which internally uses RMAN for the conversion.
DB Version: 11.2.0.3.0
The DB conversion was failing every time on the redo logs addition phase of the conversion.
The source database was in an NFS shared storage. And the conversion was to an Exadata box.
Error:
ORA-00321: log 1 of thread 1, cannot update log file header
ORA-00312: online log 1 thread 1: '/redo_log_path/log3.dbf'
ORA-27072: File I/O error
Linux-x86_64 Error: 12: Cannot allocate memory
Verification:
Since there was not much beyond the above mentioned error in any of the log files, it was difficult to fix the issue. The DB folder had to be physically removed from the ASM instance each time rconfig was run, on the basis of a trial and error approach. This is because the DB instance creation was succesfull every time when rconfig is run.
Luckily we got hold of a support doc which had resemblance with the issue we had.
The Doc ID: 1532488.1 was about failure of RMAN and EXPDP in NFS mount, when Exadata11.2.3.2.1 image is used.
Solution:
Applied patch 16432033 on all compute nodes.
Restarted the RAC conversion after restoring DB from a backup
The patch helped in fixing the error and RAC/ASM conversion was successful.
Note: The patch is not persistent across reboots. If the system is rebooted, the customer needs to reapply the patch each time
Hi my friend! I wish to say that this post is amazing, great
ReplyDeletewritten and include almost all important infos.
I would like to look extra posts like this .
My personal webpage concerning technology: best surround sound speaker (payingforlong.com)