Not much today, this is just a place holder as we evaluate conflict resolution schemes for ATG and Golden Gate. Out of the box, it uses an application based sequence generator (DAS_ID_GENERATOR table). You can (and are encouraged to) prepend a string, such as the data center location to the application provided ID. The application fetches a set iof ID’s and incrementas the counter in DAS_ID_GENERATOR. I don’t know if it does a “SELECT FOR UPDATE” when it fetches the next range. If it doesn’t, and the fetch is done at the same time, it could get the same range on two different applciation servers.<\/p>\n
RAC contention could be an issue (monotonically increasing sequences can be problematic in RAC). Since we will prepend the data center to the string, we shouldn’t have many conflicts, if any.<\/p>\n
ATG primary key data types…<\/p>\n
\r\nselect count(*),dc.table_name,data_type\r\n from dba_constraints dc \r\n inner join dba_cons_columns dcc on dc.constraint_name = dcc.constraint_name \r\n and dc.owner = dcc.owner\r\n inner join dba_tab_columns dtc on dcc.column_name = dtc.column_name\r\n and dcc.table_name = dtc.table_name\r\n and dcc.owner = dtc.owner \r\n where dc.owner like 'ATG%'\r\n and constraint_type = 'P'\r\n and dc.table_name not like 'BIN$%'\r\n group by dc.table_name,data_type;\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"Not much today, this is just a place holder as we evaluate conflict resolution schemes for ATG and Golden Gate. Out of the box, it uses an application based sequence generator (DAS_ID_GENERATOR table). You can (and are encouraged to) prepend…<\/p>\n