Oracle version: 10.2.0.2 and has been deployed with mongouard. Recently, the log of oraclealert in the master database found that ora600 errors are generated almost every day in the last half month.
Oracle version: 10.2.0.2 with data guard. Recently, the oracle alert Log in the master database found that the ora 600 error is generated almost every day in the last half month.
Oracle version: 10.2.0.2 with data guard
Operating System: linux rhat 5.6x64
Recently, the oracle alert Log of the master database found that the ora 600 error occurs almost every day in the last half month, as shown below:
Errors in file/oracle/admin/hycrm/bdump/hycrm_s000_27823.trc:
ORA-00600: internal error code, arguments: [opifal.1], [], [], [], [], [], [], [], []
The standby database's alert Log has
Errors in file/oracle/admin/hycrm/bdump/hycrm_mrp0_8323.trc:
ORA-16099: internal error ORA-00600 occurred at standbydatabase
View the configuration of dg in the master and slave tnsnames. ora as follows:
Hycrm =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.110.23) (PORT = 1521 ))
)
(CONNECT_DATA =
(SERVICE_NAME = hycrm)
)
)
Hycrm_std =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.110.24) (PORT = 1521 ))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SID = hycrm)
)
)
SERVER = DEDICATED is found in the connection string of the master database. After adding the parameter, track and observe that the ora 600 error disappears.
This error should be related to VPC connection.
Related reading:
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
,