|10R2 Source/ 11gR2 Target applies to wrong destination [message #467221]
||Thu, 22 July 2010 13:29
Registered: March 2008
Location: Laurel, MD USA
Hi All, |
After configuring Streams (local capture) with 10R2 as source & 11gR2 as target, my tables are replicated to the STREAMS ADMIN's schema, rather than the schema i intended for them (SAPR3).
I actually pre-created the same schema in the target db as that in the Source db before implemenenting my Streams Process.
The capture/propagation completes successfully, but at the source database, not only are the tables applied to the wrong destination (STREAMS_ADMIN schema, rather than SAPR3 schema), they don't show within the target db as tables (they still show as rules) (see SQL query results below)
SQL> select object_name,object_type,owner
2 from all_objects where object_name like '%/BIC%';
OBJECT_NAME OBJECT_TYPE OWNER
------------------------- --------------- -------------------------
/BIC/APSLEN2R0030 RULE STREAMS_ADMIN
/BIC/APSLEN2R0029 RULE STREAMS_ADMIN
/BIC/APSPROJID0035 RULE STREAMS_ADMIN
/BIC/APSPUO3CR0033 RULE STREAMS_ADMIN
/BIC/APSPROJID0034 RULE STREAMS_ADMIN
/BIC/APSPUO3CR0032 RULE STREAMS_ADMIN
Below is the PL/SQL procedure I executed successfully at the source db to set the rules for this implementation, after setting up the necessary pre-requisites both in the Source (BWD) & Target (MDMD) databases.
TABLES(1) := 'SAPR3."/BIC/APSLEN2R00"';
TABLES(2) := 'SAPR3."/BIC/APSPUO3CR00"';
TABLES(3) := 'SAPR3."/BIC/APSPROJID00"';
TABLE_NAMES => TABLES,
SOURCE_DIRECTORY_OBJECT => 'STREAMS_DIR',
DESTINATION_DIRECTORY_OBJECT => 'STREAMS_DIR',
SOURCE_DATABASE => 'BWD',
DESTINATION_DATABASE => 'MDMD',
CAPTURE_NAME => 'CAPTURE_BWD',
CAPTURE_QUEUE_TABLE => 'SOURCE_BWD_QT',
PROPAGATION_NAME => 'PROPAGATION_MDMD1',
APPLY_NAME => 'APPLY_MDMD1',
APPLY_QUEUE_TABLE => 'DESTINATION_MDMD_QT',
BI_DIRECTIONAL => FALSE,
INCLUDE_DDL => TRUE,
INSTANTIATION => DBMS_STREAMS_ADM.INSTANTIATION_TABLE);
I'll appreciate are positive in puts to guide me correct whatever mistakes I'm making here.
N.B: My tables are special SAP tables that need the double quotes & slashes.
- divroro12 -