ORA-01418 in Logical Standby Database
(Doc ID 2907482.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.6 and laterInformation in this document applies to any platform.
Goal
Disclaimer:
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:
SchemaName: DATA_INDEXES
ObjectName: M_GETPARTINSTANCE_2_FULL_TEXT
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:
SchemaName: DATA_INDEXES
ObjectName: M_GETPARTINSTANCE_2_FULL_TEXT
Frequent alerts on Logical Standby database seen and replication being stopped due to the schema of DATA_INDEXES.
However, the error ORA-01418 still occurs.
Solution
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
| Goal |
| Solution |
| References |