Thank you guys,
Sorry for all the confusion , Let me try to be more clear on this matter:
I'm just trying to understand how DSI works in a WS pair when an attempt of duplicate key insert on a table with unique index or similar should happen at a primary ASE1.DB1 site .
- I'm clear that the replicate site must not be modified( U;D,I) [ok]
- Load of secondary site must be done only by replication methods [ok]
-When an attempt to insert a duplicate key avle at the primary site the Tx is rolled back and it's not read by the rep agent , thus it does not flow to the replicate site.
Then as Mark mentioned and assuming everything is working and set up correctly, this is :
Create new PDB/RDB databases; create identical/empty table 't1' in both databases; create identical unique index on both tables
- create brand new WS setup (create logical connection; rs_init ASE1.DB1 as active db; rs_init ASE2.DB2 as standby)
- verify replication is working by submitting rs_ticket in PDB and verify it comes out in the RDB; once replication if verified then ...
- insert first record into t1 in the PDB and verify it gets inserted to RDB's t1 table
- insert duplicate record into t1 in the PDB and see what happens
Then :
DSI for ASE1.DB1 stays up(running)
DSI ASE2.DB2 stays up.(running)
Then the question is : Assuming that at the replicate site ASE2.DB2, no manual modifications are done, under which possible circumstances DSIs to ASE2.DB2 would shutdown ?
Thank you
Regards
Jose