How to fix a problem ...

Question

Hi,
I did all that I read in the document "Steps To Setup Replication Using Oracle Streams". I had no errors but the modifications are not propagated in the destination database.
in alert.log of source DB I have:
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 83886080
__large_pool_size = 0
__java_pool_size = 4194304
__streams_pool_size = 0
sga_target = 289406976
control_files = E:\ORADATA\ORCL\CONTROL01.CTL, E:\ORADATA\ORCL\CONTROL02.CTL, E:\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_dest_1 = LOCATION=E:\archive
log_archive_format = %t_%s_%r.dbf
db_file_multiblock_read_count= 16
db_recovery_file_dest = E:/flash_recovery_area
db_recovery_file_dest_size= 2147483648
logmnr_max_persistent_sessions= 1
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain = regress.rdbms.dev.us.oracle.com
global_names = TRUE
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
parallel_max_servers = 10
audit_file_dest = E:\ADMIN\ORCL\ADUMP
background_dump_dest = E:\ADMIN\ORCL\BDUMP
user_dump_dest = E:\ADMIN\ORCL\UDUMP
core_dump_dest = E:\ADMIN\ORCL\CDUMP
open_links = 4
db_name = orcl
open_cursors = 300
pga_aggregate_target = 95420416
aq_tm_processes = 1
Obsolete system parameters with specified values:
log_parallelism
End of obsolete system parameter listing
Deprecated system parameters with specified values:
logmnr_max_persistent_sessions
End of deprecated system parameter listing
PMON started with pid=2, OS id=1028
PSP0 started with pid=3, OS id=1380
MMAN started with pid=4, OS id=4076
DBW0 started with pid=5, OS id=908
LGWR started with pid=6, OS id=2964
CKPT started with pid=7, OS id=2372
SMON started with pid=8, OS id=3960
RECO started with pid=9, OS id=296
CJQ0 started with pid=10, OS id=2076
MMON started with pid=11, OS id=1776
MMNL started with pid=12, OS id=2332
Tue Mar 13 18:15:59 2007
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Tue Mar 13 18:15:59 2007
ALTER DATABASE MOUNT
Tue Mar 13 18:16:04 2007
Setting recovery target incarnation to 2
Tue Mar 13 18:16:04 2007
Successful mount of redo thread 1, with mount id 1144926559
Tue Mar 13 18:16:04 2007
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Tue Mar 13 18:16:04 2007
ALTER DATABASE OPEN
Tue Mar 13 18:16:04 2007
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=15, OS id=1888
Tue Mar 13 18:16:04 2007
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=17, OS id=2668
Tue Mar 13 18:16:04 2007
Thread 1 opened at log sequence 14
Current log# 1 seq# 14 mem# 0: E:\ORADATA\ORCL\REDO01.LOG
Successful open of redo thread 1
Tue Mar 13 18:16:04 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Tue Mar 13 18:16:04 2007
ARC0: STARTING ARCH PROCESSES
Tue Mar 13 18:16:04 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Tue Mar 13 18:16:04 2007
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
ARC2 started with pid=18, OS id=2552
Tue Mar 13 18:16:04 2007
SMON: enabling cache recovery
Tue Mar 13 18:16:05 2007
Successfully onlined Undo Tablespace 1.
Tue Mar 13 18:16:05 2007
SMON: enabling tx recovery
Tue Mar 13 18:16:06 2007
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=2496
Tue Mar 13 18:16:12 2007
Completed: ALTER DATABASE OPEN
Tue Mar 13 18:16:13 2007
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Mar 13 18:17:32 2007
Streams CAPTURE C001 started with pid=27, OS id=2912
Tue Mar 13 18:17:35 2007
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 1
LOGMINER: Memory Size = 10M, Checkpoint interval = 10M
LOGMINER: session# = 1, reader process P000 started with pid=28 OS id=2184
LOGMINER: session# = 1, builder process P001 started with pid=29 OS id=3268
LOGMINER: session# = 1, preparer process P002 started with pid=30 OS id=2952
Tue Mar 13 18:17:44 2007
LOGMINER: Begin mining logfile: E:\ARCHIVE\1_10_616852400.DBF
Tue Mar 13 18:18:27 2007
LOGMINER: End mining logfile: E:\ARCHIVE\1_10_616852400.DBF
Tue Mar 13 18:18:28 2007
LOGMINER: Begin mining logfile: E:\ARCHIVE\1_11_616852400.DBF
Tue Mar 13 18:18:32 2007
Thread 1 advanced to log sequence 15
Current log# 2 seq# 15 mem# 0: E:\ORADATA\ORCL\REDO02.LOG
Tue Mar 13 18:18:40 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Tue Mar 13 18:18:41 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Tue Mar 13 18:18:42 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Tue Mar 13 18:18:42 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Tue Mar 13 18:18:42 2007
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
Indexes of table SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
Indexes of table SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
Tue Mar 13 18:19:12 2007
LOGMINER: Begin mining logfile: E:\ARCHIVE\1_10_616852400.DBF
Tue Mar 13 18:19:16 2007
LOGMINER: End mining logfile: E:\ARCHIVE\1_10_616852400.DBF
Tue Mar 13 18:19:16 2007
LOGMINER: Begin mining logfile: E:\ARCHIVE\1_11_616852400.DBF
Tue Mar 13 18:19:25 2007
LOGMINER: End mining logfile: E:\ARCHIVE\1_11_616852400.DBF
Tue Mar 13 18:19:26 2007
LOGMINER: Begin mining logfile: E:\ARCHIVE\1_12_616852400.DBF
Tue Mar 13 18:19:29 2007
LOGMINER: End mining logfile: E:\ARCHIVE\1_12_616852400.DBF
Tue Mar 13 18:19:29 2007
LOGMINER: Begin mining logfile: E:\ORADATA\ORCL\REDO03.LOG
Tue Mar 13 18:19:30 2007
LOGMINER: End mining logfile: E:\ORADATA\ORCL\REDO03.LOG
Tue Mar 13 18:19:30 2007
LOGMINER: Begin mining logfile: E:\ORADATA\ORCL\REDO01.LOG
Tue Mar 13 18:20:06 2007
LOGMINER: End mining logfile: E:\ORADATA\ORCL\REDO01.LOG
Tue Mar 13 18:20:06 2007
LOGMINER: Begin mining logfile: E:\ORADATA\ORCL\REDO02.LOG
Tue Mar 13 18:21:05 2007
Shutting down archive processes
Tue Mar 13 18:21:10 2007
ARCH shutting down
ARC2: Archival stopped ??? Is that correct ?
and in alert.log of destination DB I hav:
[b]Threshold validation cannot be done before catproc is loaded.
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=15, OS id=3132
Tue Mar 13 17:25:53 2007
Completed: ALTER DATABASE OPEN
Tue Mar 13 17:25:54 2007
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Mar 13 17:31:49 2007
Streams APPLY A001 started with pid=21, OS id=3508
Streams Apply Server started P001 with pid=23 OS id=3556
Streams Apply Reader started P000 with pid=22 OS id=3604
Could anybody tell me what's happening here ? Or, could anybody tell me how could I trace an error in a stream ?
Thanks, Paul

Answer 1

Sorry, I got the answer. I had Objects not instantiated when using DBMS_APPLY_ADM.SET_SCHEMA_INSTANTIATION_SCN. Note:272731.1 on Metalink helped me.