My Oracle Support Banner

DBMS_STREAMS_ADM.REMOVE_STREAMS_CONFIGURATION Fails With ORA-1918 (Doc ID 735136.1)

Last updated on MAY 31, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner. 

Executing DBMS_STREAMS_ADM.REMOVE_STREAMS_CONFIGURATION fails with ORA-01918 when a ROLE is created after the DBMS_CAPTURE_ADM.PREPARE_GLOBAL_INSTANTIATION. The scenario would be as follows:

1. Executing DBMS_CAPTURE_ADM.PREPARE_GLOBAL_INSTANTIATION

2. Creating a database ROLE. The ROLE creation can happen as part of any database component
     installation like installing Oracle JVM or XDB etc.

3. Now if you try to abort the instantiation using DBMS_CAPTURE_ADM.ABORT_GLOBAL_INSTANTIATION or remove streams using DBMS_STREAMS_ADM.REMOVE_STREAMS_CONFIGURATION would raise a ORA-01918 error.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.