ORA-7445:[__strstr_sse42] After Upgrade To 188.8.131.52
(Doc ID 2053231.1)
Last updated on MAY 22, 2020
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
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.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Data Guard Configuration: DBM_DG
DB_unique_name: dbm001b - Net Connection Alias: DBM001B,DBM001B.< domain name >
The alert log of the Primary database logged the below ORA-07445 errors. However the primary and standby database were running fine and in sync.
The databases were upgraded to 18.104.22.168
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