Alter Database Add Supplemental Log Data Hangs
(Doc ID 406498.1)
Last updated on SEPTEMBER 28, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
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.
As part of the Streams setup you can specify supplemental logging at the database level.
It can be done manually:
or implicitly running procedures like DBMS_STREAMS_ADM.ADD_SCHEMA_RULES
or if you setup Streams using Grid Control it is automatically executed by SrcSchemaRule1 Stage Step 12.
In some cases, this step hangs and the statement ALTER DATABASE ADD SUPPLEMENTAL LOG DATA remains waiting for TX lock in shared mode.
1. Identify the problematic session via
connect / as sysdba
alter session set tracefile_identifier='SUPP';
alter session set max_dump_file_size=unlimited;
alter session set events '32593 errorstack(3) systemstate(266)';
ALTER DATABASE add SUPPLEMENTAL LOG DATA;
Upload the *SUPP* from the database trace directory.
Note that if the database has a lot of sessions associated with it dumping the systemstate will take time and generate a large trace file.
Then kill the session.
Possibly looking at blockers and waiters would be simpler.
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