Home » Server Options » Replication » Apply Process is not working (Oracle 11g , Windows 2003 server )
Apply Process is not working [message #525753] Wed, 05 October 2011 03:10 Go to next message
pradies
Messages: 250
Registered: May 2008
Senior Member
Hi,

I have created Replication process for a single table using the below mentioned script.
connect sys/afccv@afccv as sysdba

show parameter open_cursor

create user STRMADMIN identified by STRMADMIN;

ALTER USER STRMADMIN DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS;

GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE,DBA to STRMADMIN;

execute DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE('STRMADMIN'); 

connect sys/vxmldb@vxmldb as sysdba

create user STRMADMIN identified by STRMADMIN;

ALTER USER STRMADMIN DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS;

GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE,DBA to STRMADMIN;

execute DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE('STRMADMIN'); 

conn STRMADMIN/STRMADMIN@afccv

BEGIN
DBMS_STREAMS_ADM.SET_UP_QUEUE(
queue_name => 'STREAMS_QUEUE',
queue_table =>'STREAMS_QUEUE_TABLE',
queue_user => 'STRMADMIN');
END;
/
conn STRMADMIN/STRMADMIN@afccv

create database link vxmldb connect to STRMADMIN identified by STRMADMIN using 'vxmldb'; 

select sysdate from dual@vxmldb;


conn STRMADMIN/STRMADMIN@vxmldb

BEGIN
DBMS_STREAMS_ADM.SET_UP_QUEUE(
queue_name => 'STREAMS_QUEUE',
queue_table =>'STREAMS_QUEUE_TABLE',
queue_user => 'STRMADMIN');
END;
/

conn STRMADMIN/STRMADMIN@afccv


BEGIN 
DBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES( 
table_name => 'AFCCV.TBL_VOICECHAT', 
streams_name => 'STRMADMIN_PROP', 
source_queue_name => 'STRMADMIN.STREAMS_QUEUE', 
destination_queue_name => 'STRMADMIN.STREAMS_QUEUE@vxmldb', 
include_dml => true, 
include_ddl => true, 
source_database => 'afccv'); 
END; 
/ 

BEGIN   
DBMS_STREAMS_ADM.ADD_TABLE_RULES(   
  table_name     => 'AFCCV.TBL_VOICECHAT',   
  streams_type    => 'CAPTURE',   
  streams_name    => 'STRMADMIN_CAPTURE',   
  queue_name      => 'STRMADMIN.STREAMS_QUEUE',   
  include_dml     => true,   
  include_ddl     => true,   
  source_database => 'AFCCV');   
END;   
/  
conn STRMADMIN/STRMADMIN@vxmldb

BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'AFCCV.TBL_VOICECHAT',
streams_type => 'APPLY',
streams_name => 'STRMADMIN_APPLY',
queue_name => 'STRMADMIN.STREAMS_QUEUE',
include_dml => true,
include_ddl => true,
source_database => 'afccv');
END;
/ 

BEGIN 
  DBMS_APPLY_ADM.ALTER_APPLY( 
    apply_name => 'STRMADMIN_APPLY', 
    apply_user => 'afccv'); 
END; 
/  

BEGIN 
  DBMS_APPLY_ADM.SET_PARAMETER( 
    apply_name => 'STRMADMIN_APPLY', 
    parameter  => 'disable_on_error', 
    value      => 'n'); 
END; 
/ 



=============================== EXPORT IMPORT ==============================

exp system/afccv@afccv TABLES=AFCCV.tbl_voicechat FILE=C:\tbl.dmp 
LOG=C:\tbl_exp.log OBJECT_CONSISTENT=Y STATISTICS=NONE 

imp SYSTEM/vxmldb@vxmldb CONSTRAINTS=Y fromuser=afccv touser=afccv FILE=c:\tbl.dmp 
IGNORE=Y COMMIT=Y LOG=c:\tbl_imp.log STREAMS_INSTANTIATION=Y

=============== Replication Process Started using the below commands ==========

conn STRMADMIN/STRMADMIN@vxmldb

BEGIN 
DBMS_APPLY_ADM.START_APPLY(apply_name => 'STRMADMIN_APPLY'); 
END; 
/  

conn STRMADMIN/STRMADMIN@afccv

BEGIN 
DBMS_CAPTURE_ADM.START_CAPTURE(capture_name => 'STRMADMIN_CAPTURE'); 
END; 
/  


According to Alert log file Replication process started( Refer Alert log content below


Wed Oct 05 12:45:53 2011
Streams CAPTURE CP01 for STRMADMIN_CAPTURE started with pid=256, OS id=8692
Starting persistent Logminer Session with sid = 41 for Streams Capture STRMADMIN_CAPTURE
Wed Oct 05 12:46:20 2011
LOGMINER: Parameters summary for session# = 41
LOGMINER: Number of processes = 3, Transaction Chunk Size = 1
LOGMINER: Memory Size = 10M, Checkpoint interval = 1000M
LOGMINER: SpillScn 0, ResetLogScn 893188
Wed Oct 05 12:52:54 2011


***********************************************************************

Fatal NI connect error 12170.

  VERSION INFORMATION:
	TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
	Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
	Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
  Time: 05-OCT-2011 12:52:54
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12535
    
TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    
TNS-00505: Operation timed out
    nt secondary err code: 60
    nt OS err code: 0
  Client address: <unknown>
Wed Oct 05 13:07:16 2011
Thread 1 advanced to log sequence 77431
  Current log# 4 seq# 77431 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG



Now When I am checking the apply status then it is showing Dequeue message

SQL> l
  1* select apply_name,state,DEQUEUE_TIME from  V$STREAMS_APPLY_READER
SQL> /

APPLY_NAME                     STATE             DEQUEUE_TIME
------------------------------ ----------------- --------------------
STRMADMIN_APPLY                DEQUEUE MESSAGES



when I am checking the number of rows on both tables (source and destination) , at destination it is not applying any thing.

SO Can someone please tell me where I should check to resolve this .

Thanks on advance


Pradeep

[Updated on: Wed, 05 October 2011 03:37] by Moderator

Report message to a moderator

Re: Apply Process is not working [message #525757 is a reply to message #525753] Wed, 05 October 2011 03:42 Go to previous messageGo to next message
Michel Cadot
Messages: 68624
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-12535: TNS:operation timed out
 *Cause: The requested operation could not be completed within the time out
 period.
 *Action: Look at the documentation on the secondary errors for possible
 remedy. See SQLNET.LOG to find secondary error if not provided explicitly.
 Turn on tracing to gather more information.

ORA-12560: TNS:protocol adapter error
 *Cause: A generic protocol adapter error occurred.
 *Action: Check addresses used for proper protocol specification. Before
 reporting this error, look at the error stack and check for lower level
 transport errors. For further details, turn on tracing and reexecute the
 operation. Turn off tracing when the operation is complete.


Give the name of the database link in upper case in "source_database", verify the database link works.

Regards
Michel
Re: Apply Process is not working [message #525765 is a reply to message #525753] Wed, 05 October 2011 04:29 Go to previous messageGo to next message
John Watson
Messages: 8922
Registered: January 2010
Location: Global Village
Senior Member
For a simple replication, I wouldn't do it that way. I would create database links in both directions, and then use dbms_streams_adm.maintain_tables to do it all in one procedure call. Much easier.
Re: Apply Process is not working [message #525778 is a reply to message #525757] Wed, 05 October 2011 05:25 Go to previous messageGo to next message
pradies
Messages: 250
Registered: May 2008
Senior Member
Hi Michal,

I again recreated the replication with the following commands. and I am using source db name in Caps. DB link between databases is working ok.

connect sys/*****@afccv as sysdba

create user STRMADMIN identified by STRMADMIN;

ALTER USER STRMADMIN DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS;

GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE,DBA to STRMADMIN;

execute DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE('STRMADMIN'); 

connect sys/*****@vxmldb as sysdba

create user STRMADMIN identified by STRMADMIN;

ALTER USER STRMADMIN DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP QUOTA UNLIMITED ON USERS;

GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE,DBA to STRMADMIN;

execute DBMS_STREAMS_AUTH.GRANT_ADMIN_PRIVILEGE('STRMADMIN'); 

conn STRMADMIN/STRMADMIN@afccv

BEGIN
DBMS_STREAMS_ADM.SET_UP_QUEUE(
queue_name => 'STREAMS_QUEUE',
queue_table =>'STREAMS_QUEUE_TABLE',
queue_user => 'STRMADMIN');
END;
/
conn STRMADMIN/STRMADMIN@afccv

create database link vxmldb connect to STRMADMIN identified by STRMADMIN using 'vxmldb'; 

select sysdate from dual@vxmldb;


conn STRMADMIN/STRMADMIN@vxmldb

BEGIN
DBMS_STREAMS_ADM.SET_UP_QUEUE(
queue_name => 'STREAMS_QUEUE',
queue_table =>'STREAMS_QUEUE_TABLE',
queue_user => 'STRMADMIN');
END;
/

conn STRMADMIN/STRMADMIN@afccv


BEGIN 
DBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES( 
table_name => 'AFCCV.TBL_VOICECHAT', 
streams_name => 'STRMADMIN_PROP', 
source_queue_name => 'STRMADMIN.STREAMS_QUEUE', 
destination_queue_name => 'STRMADMIN.STREAMS_QUEUE@vxmldb', 
include_dml => true, 
include_ddl => true, 
source_database => 'AFCCV'); 
END; 
/ 

BEGIN   
DBMS_STREAMS_ADM.ADD_TABLE_RULES(   
  table_name     => 'AFCCV.TBL_VOICECHAT',   
  streams_type    => 'CAPTURE',   
  streams_name    => 'STRMADMIN_CAPTURE',   
  queue_name      => 'STRMADMIN.STREAMS_QUEUE',   
  include_dml     => true,   
  include_ddl     => true,   
  source_database => 'AFCCV');   
END;   
/  
conn STRMADMIN/STRMADMIN@vxmldb

BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'AFCCV.TBL_VOICECHAT',
streams_type => 'APPLY',
streams_name => 'STRMADMIN_APPLY',
queue_name => 'STRMADMIN.STREAMS_QUEUE',
include_dml => true,
include_ddl => true,
source_database => 'AFCCV');
END;
/ 

BEGIN 
  DBMS_APPLY_ADM.ALTER_APPLY( 
    apply_name => 'STRMADMIN_APPLY', 
    apply_user => 'AFCCV'); 
END; 
/  

BEGIN 
  DBMS_APPLY_ADM.SET_PARAMETER( 
    apply_name => 'STRMADMIN_APPLY', 
    parameter  => 'disable_on_error', 
    value      => 'n'); 
END; 
/ 



=============================== EXPORT IMPORT ==============================

exp system/afccv@afccv TABLES=AFCCV.tbl_voicechat FILE=C:\tbl.dmp 
LOG=C:\tbl_exp.log OBJECT_CONSISTENT=Y STATISTICS=NONE 

=====================================================================================================================
/*Step 6 - Transfer the export dump file to destdb and import */
=====================================================================================================================
imp SYSTEM/vxmldb@vxmldb CONSTRAINTS=Y fromuser=afccv touser=afccv FILE=c:\tbl.dmp 
IGNORE=Y COMMIT=Y LOG=c:\tbl_imp.log STREAMS_INSTANTIATION=Y


conn STRMADMIN/STRMADMIN@vxmldb

BEGIN 
DBMS_APPLY_ADM.START_APPLY(apply_name => 'STRMADMIN_APPLY'); 
END; 
/  

conn STRMADMIN/STRMADMIN@afccv

BEGIN 
DBMS_CAPTURE_ADM.START_CAPTURE(capture_name => 'STRMADMIN_CAPTURE'); 
END; 
/  



Alert log content after the replication on source database is .


  Client address: <unknown>
Wed Oct 05 13:07:16 2011
Thread 1 advanced to log sequence 77431
  Current log# 4 seq# 77431 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG
Wed Oct 05 13:29:30 2011
Thread 1 advanced to log sequence 77432
  Current log# 5 seq# 77432 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO05.LOG
Wed Oct 05 13:51:02 2011
Streams CAPTURE CP01 for STRMADMIN_CAPTURE with pid=256, OS id=8692 stopped
Wed Oct 05 13:58:48 2011
Thread 1 advanced to log sequence 77433
  Current log# 6 seq# 77433 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO06.LOG
Wed Oct 05 14:20:04 2011
Thread 1 advanced to log sequence 77434
  Current log# 4 seq# 77434 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG
Wed Oct 05 14:39:38 2011
Streams downstream capture: turning off downstream_real_time_mine
i_sched_prop: DEBUG : removed job 
Wed Oct 05 14:48:40 2011
Thread 1 advanced to log sequence 77435
  Current log# 5 seq# 77435 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO05.LOG
Wed Oct 05 14:49:48 2011
Thread 1 advanced to log sequence 77436
  Current log# 6 seq# 77436 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO06.LOG
Wed Oct 05 14:49:50 2011
Wed Oct 05 14:49:50 2011
Logminer Bld: Build started
Thread 1 cannot allocate new log, sequence 77437
Checkpoint not complete
  Current log# 6 seq# 77436 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO06.LOG
Wed Oct 05 14:50:06 2011
Thread 1 advanced to log sequence 77437
  Current log# 4 seq# 77437 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG
Wed Oct 05 14:50:06 2011
Wed Oct 05 14:50:06 2011
Logminer Bld: Lockdown Complete.  DB_TXN_SCN is 5 1642555417 LockdownSCN is 23117391827
Wed Oct 05 14:50:18 2011
Thread 1 cannot allocate new log, sequence 77438
Checkpoint not complete
  Current log# 4 seq# 77437 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG
Wed Oct 05 14:50:38 2011
Thread 1 advanced to log sequence 77438
  Current log# 5 seq# 77438 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO05.LOG
Wed Oct 05 14:50:40 2011
Wed Oct 05 14:50:40 2011
Logminer Bld: Done
STREAMS: dictionary dumped, now wait for inflight txn
knlciWaitForInflightTxns: wait for inflight txns at this scn: 
scn: 0x0005.61e7f3e3
 [23117427683]
knlciWaitForInflightTxns: Done with waiting for inflight txns at this scn: 
scn: 0x0005.61e7f3e3
 [23117427683]
Wed Oct 05 15:01:40 2011
Streams downstream capture: turning off downstream_real_time_mine
i_sched_prop: DEBUG : removed job 
Wed Oct 05 15:11:00 2011
Thread 1 advanced to log sequence 77439
  Current log# 6 seq# 77439 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO06.LOG
Wed Oct 05 15:11:08 2011
Wed Oct 05 15:11:08 2011
Logminer Bld: Build started
Thread 1 advanced to log sequence 77440
  Current log# 4 seq# 77440 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG
Wed Oct 05 15:11:09 2011
Logminer Bld: Lockdown Complete.  DB_TXN_SCN is 5 1643457697 LockdownSCN is 23118294129
Wed Oct 05 15:11:32 2011
Thread 1 cannot allocate new log, sequence 77441
Checkpoint not complete
  Current log# 4 seq# 77440 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG
Wed Oct 05 15:12:06 2011
Thread 1 advanced to log sequence 77441
  Current log# 5 seq# 77441 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO05.LOG
Wed Oct 05 15:12:08 2011
Wed Oct 05 15:12:08 2011
Logminer Bld: Done
STREAMS: dictionary dumped, now wait for inflight txn
knlciWaitForInflightTxns: wait for inflight txns at this scn: 
scn: 0x0005.61f5a282
 [23118324354]
knlciWaitForInflightTxns: Done with waiting for inflight txns at this scn: 
scn: 0x0005.61f5a282
 [23118324354]
Warning: STREAMS failed to prepare instantiation for table "AFCCV"."TBL_VOICECHAT".
Wed Oct 05 15:38:43 2011
Streams CAPTURE CP01 for STRMADMIN_CAPTURE started with pid=274, OS id=9268
Streams CAPTURE CP01 for STRMADMIN_CAPTURE with pid=274, OS id=9268 is in combined capture and apply mode.
Starting persistent Logminer Session with sid = 81 for Streams Capture STRMADMIN_CAPTURE
LOGMINER: Parameters summary for session# = 81
LOGMINER: Number of processes = 3, Transaction Chunk Size = 1
LOGMINER: Memory Size = 10M, Checkpoint interval = 1000M
LOGMINER: SpillScn 0, ResetLogScn 893188
Wed Oct 05 15:38:54 2011
LOGMINER: session#=81, reader MS00 pid=159 OS id=12248 sid=2746 started
Wed Oct 05 15:38:54 2011
LOGMINER: session#=81, builder MS01 pid=276 OS id=12532 sid=2837 started
Wed Oct 05 15:38:54 2011
LOGMINER: session#=81, preparer MS02 pid=277 OS id=1608 sid=2704 started
LOGMINER: Begin mining logfile during dictionary load for session 81 thread 1 sequence 77440, E:\ORADATA\ARCH\ARC_1_77440_708389902.ARC
Wed Oct 05 15:39:05 2011
Thread 1 advanced to log sequence 77442
  Current log# 6 seq# 77442 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO06.LOG
Wed Oct 05 15:39:21 2011
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_PROPS$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ENC$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SUBCOLTYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRIBUTE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_NTAB$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_REFCON$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OPQTYPE$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_KOPM$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_PARTOBJ$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOGMNR_BUILDLOG have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_SEED$ have been marked unusable
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_DICTIONARY$ 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_ENC$ 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_KOPM$ 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_LOGMNR_BUILDLOG have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_NTAB$ 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_OPQTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_PARTOBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_PROPS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_REFCON$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_SEED$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_SUBCOLTYPE$ 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
Wed Oct 05 15:40:58 2011
LOGMINER: End mining logfiles during dictionary load for session 81
Wed Oct 05 15:41:01 2011
LOGMINER: Begin mining logfile for session 81 thread 1 sequence 77440, E:\ORADATA\ARCH\ARC_1_77440_708389902.ARC
LOGMINER: End mining logfile for session 81 thread 1 sequence 77440, E:\ORADATA\ARCH\ARC_1_77440_708389902.ARC
LOGMINER: Begin mining logfile for session 81 thread 1 sequence 77441, D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO05.LOG
Wed Oct 05 15:48:41 2011
LOGMINER: End mining logfile for session 81 thread 1 sequence 77441, D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO05.LOG
LOGMINER: Begin mining logfile for session 81 thread 1 sequence 77442, D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO06.LOG
Wed Oct 05 15:50:12 2011
Thread 1 advanced to log sequence 77443
  Current log# 4 seq# 77443 mem# 0: D:\APP\ADMINISTRATOR\ORADATA\AFCCV\REDO04.LOG



Few errors occured in the alert log file. like "Warning: STREAMS failed to prepare instantiation for table " I googled for this but no a specific one related to this.

Can you please tell me what should I do now.

Thanks

PRadeep

[Updated on: Wed, 05 October 2011 05:35] by Moderator

Report message to a moderator

Re: Apply Process is not working [message #525780 is a reply to message #525778] Wed, 05 October 2011 05:36 Go to previous messageGo to next message
pradies
Messages: 250
Registered: May 2008
Senior Member
Hi John,

As you said, I can created the db link for both side. but I don't know abut the procedure which you are telling.

Can you please tell me the same step by step.

Thnks

Pradeep S
Re: Apply Process is not working [message #525784 is a reply to message #525780] Wed, 05 October 2011 05:49 Go to previous message
John Watson
Messages: 8922
Registered: January 2010
Location: Global Village
Senior Member
There are simple tutorial in the docs:
http://www.oracle.com/pls/db112/to_toc?pathname=server.112%2Fe17516%2Ftoc.htm&remark=portal+%28Books%29
Have you had problems doing them?

Previous Topic: Replicate "A" schema objects to "B" schema
Next Topic: Error in refreshing MV
Goto Forum:
  


Current Time: Thu Mar 28 03:54:46 CDT 2024