|Applies To||RSA Product Set: RSA Tokenization Server appliance (RTS)|
|Issue||Does RTS provide "Replication Collision Avoidance"?|
RTS token creation.
|Resolution||The "Replication Collision Avoidance" functionality isn't implemented with RTS, but rather some logic that will make RTS create tokens locally or remotely.|
The following was clarified regarding RTS:
The below two columns (schema.table.column) contain the settings to determine how and where tokens per token type are created:
RTSNOREPLICATE.RTM_DB_CURRENTINSTANCE.instanceID - is the node identifier
RTSOWNER.TSCYTYP.create_on_instanceID - tells you for this token type where the token is created. (each token type can have a different value)
So if the two columns are equal, the creation stays local (you are a master node for this token type).
If the columns are not equal then you go to the node specified by RTSOWNER. TSCYTYP. create_on_instanceID
In order to fully use all nodes, make each node #1 (INSTANCEID=1), and have all the creation stay local (CREATE_ON_INSTANCEID=1). That way every node is a reader and writer.
Steps to verify on RTS nodes:
ssh to RTS appliance
su - root
su - oracle
sqlplus / as sysdba
SQL> select INSTANCEID from RTSNOREPLICATE.RTM_DB_CURRENTINSTANCE;
SQL> select SCY_OBJ_TYP_CD, CREATE_ON_INSTANCEID from RTSOWNER.TSCYTYP;
no rows selected