I have a streams configuration that's working perfectly well but I have one problem with starting it on production env.
I did exp on production database and imported it on target database.
While starting streams on target database I'm using following code:
iscn NUMBER; -- Variable to hold instantiation SCN value
iscn := DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER@DB.PROD;
source_schema_name => 'STREAMS_SCHEMA',
source_database_name => 'DB.PROD',
instantiation_scn => iscn,
apply_database_link => null,
recursive => true);
But this way after starting capture and apply I do have a gap between the time of export and the time of configuring and starting streams.
How should I set SCN to start the replication so there is no gap?
Thanks for any ideas...
Hi, just a guess, but if you don't give an SCN to start from when you start your capture, shouldn't it start from the current replica's SCN?
I've not yet used streams in a prod env, but I've never had to set a specific SCN...
"Also, when you use *export/import*, transportable tablespaces, or the RMAN TRANSPORT TABLESPACE command to copy database objects from a source database to a destination database, instantiation SCNs can be set for these database objects *automatically*."
you can start the apply process without explicitly setting the instantiation SCN