Last updated on FEBRUARY 03, 2017
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Information in this document applies to any platform.
Streams setup thru DBMS_STREAMS_ADM.MAINTAIN_SCHEMAS may hang in RDBMS 12c. The same setup works fine in 11g.
Tried both methods, running DBMS_STREAMS_ADM.MAINTAIN_SCHEMAS with "perform_actions=>true" and manually with the generated setup scripts, for example:
schema_names => 'SCOTT',
source_directory_object => 'WORK_DIR',
destination_directory_object => 'WORK_DIR',
source_database => 'ORCL',
destination_database => 'ORCL1',
capture_name => 'CAPTURE_SCOTT',
capture_queue_table => 'CAPTURE_QTABLE_SCOTT',
capture_queue_name => 'CAPTURE_QNAME_SCOTT',
capture_queue_user => null,
apply_name => 'APPLY_SCOTT',
apply_queue_table => 'APPLY_QTABLE_SCOTT',
apply_queue_name => 'APPLY_QNAME_SCOTT',
apply_queue_user => null,
propagation_name => 'PROP_SCOTT',
log_file => 'maint_schemas.log',
bi_directional => true,
include_ddl => true,
instantiation => dbms_streams_adm.instantiation_schema,
perform_actions => true,
script_name => 'schema_replication.sql',
script_directory_object => 'work_dir'
Upgraded 11g database to 12c.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms