My Oracle Support Banner

ORA-23605 When Specifying Tables Owned By Different Schemas In MAINTAIN_TABLES Procedure (Doc ID 735464.1)

Last updated on AUGUST 18, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.6 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.


Symptoms

Calling DBMS_STREAMS_ADM.MAINTAIN_TABLES specifying tables owned by different schemas , as follows:

DECLARE
tables DBMS_UTILITY.UNCL_ARRAY;
BEGIN
tables(1) := 'scott.NEWT';
tables(2) := 'strmuser.NEWTABLE';

DBMS_STREAMS_ADM.MAINTAIN_TABLES(
table_names => tables,
source_directory_object => 'STREAMS_SRC_DIR',
destination_directory_object => 'STREAMS_DEST_DIR',
source_database => 'STRM102A',
destination_database => 'STRM102B',
perform_actions => TRUE,
script_name => 'configure_rep.sql',
script_directory_object => 'STREAMS_SRC_DIR',
dump_file_name => 'tabs3061807.dmp',
capture_name => 'strmuser_capture',
capture_queue_table => 'strmuser_cap_q_table',
capture_queue_name => 'strmuser_cap_q',
capture_queue_user => NULL,
propagation_name => 'strmuser_propagate',
apply_name => 'strmuser_apply',
apply_queue_table => 'strmuser_apply_q_table',
apply_queue_name => 'strmuser_apply_q',
apply_queue_user => NULL,
log_file => 'instantiate_strmuser.log',
bi_directional => true,
include_ddl => true,
instantiation => DBMS_STREAMS_ADM.INSTANTIATION_TABLE);
END;
/

or

BEGIN
DBMS_STREAMS_ADM.MAINTAIN_TABLES(
table_names => 'scott.NEWT, strmuser.NEWTABLE',
source_directory_object => 'STREAMS_SRC_DIR',
destination_directory_object => 'STREAMS_DEST_DIR',
source_database => 'STRM102A',
destination_database => 'STRM102B',
perform_actions => TRUE,
script_name => 'configure_rep.sql',
script_directory_object => 'STREAMS_SRC_DIR',
dump_file_name => 'tabs3061807.dmp',
capture_name => 'strmuser_capture',
capture_queue_table => 'strmuser_cap_q_table',
capture_queue_name => 'strmuser_cap_q',
capture_queue_user => NULL,
propagation_name => 'strmuser_propagate',
apply_name => 'strmuser_apply',
apply_queue_table => 'strmuser_apply_q_table',
apply_queue_name => 'strmuser_apply_q',
apply_queue_user => NULL,
log_file => 'instantiate_strmuser.log',
bi_directional => true,
include_ddl => true,
instantiation => DBMS_STREAMS_ADM.INSTANTIATION_TABLE);
END;
/

Fails with:

ERROR at line 1:
ORA-23605: invalid value "tabs3061807.dmp" for STREAMS parameter dump_file_name
ORA-06512: at "SYS.DBMS_LOGREP_UTIL", line 80
ORA-06512: at "SYS.DBMS_LOGREP_UTIL", line 123
ORA-06512: at "SYS.DBMS_STREAMS_ADM_UTL", line 325
ORA-06512: at "SYS.DBMS_STREAMS_MT", line 7507
ORA-06512: at "SYS.DBMS_STREAMS_ADM", line 2476
ORA-06512: at line 7

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


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