Unable To Create Standby Physical Database TNS-12537 ora-600 [ksiotranslateIO03]
(Doc ID 1630655.1)
Last updated on NOVEMBER 26, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
You have a new Data Guard Standby Server. You installed ASM 184.108.40.206 and RDBMS 220.127.116.11 using job role separation.
The grid home on the standby site is owned by grid user oinstall group.
The db home on the standby site is owned by oracle user oinstall group.
The asm disks on the standby site is owned by grid user asmadmin group.
When you try to create a physical standby using rman duplicate, it fails with ora-15183 and ora-600 [ksiotranslateIO03]
because the owner and group of oracle binary are different from the owner and group of asm disks so that the oracle user
couldn't access the asm disks.
As suggested in
<Note 1084186.1>: Database Creation on 11.2 Grid Infrastructure with Role Separation ( ORA-15025, KFSG-00312, ORA-15081 )
you run setasmgidwrap so that the database oracle binary was owned by asmadmin group.
Then you could create the physical standby database.
But the primary database couldn't connect to the standby database and failed with TNS-12537.
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious
data from the Oracle sample schema(s),Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document