My Oracle Support Banner

ORA-1405 When Starting the Capture Process - DBMS_RULE_ADM.ALTER_RULE Nulls Out the Rule Condition (Doc ID 358674.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 10.2.0.1 [Release 9.2 to 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.

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

Symptoms

When creating a Streams capture rule implicitly using dbms_streams_adm.create_capture, and then modifying it with dbms_rule_adm.alter_rule to add a very long rule condition (about 7800 characters in length), the rule condition is nulled out. The procedure executes successfully and no error is reported, but the rule condition itself is erased. This can result in a ORA-1405 'fetched column value is NULL' when starting the capture process.


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
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.