Schema Separation

Schema separation in transact system allows to store tables with respect to the company and/or to categories the Temenos Transact tables based on the functional nature. This will help the customers to have better control over the Temenos Transact tables from database level. This section provides details about the schema separation configuration and sample screen captures of the scripts with and without schema separation.

DLM allows the same mechanism as per Temenos Transact (company level and table level schema) for tables in the Read Only (RO) database.

For example, if TELLER is in BUSINESS schema in transact database, then the same BUSINESS schema is to be followed in TELLER$HIS$RO in NVDB and TELLER$HIS$ARC to be followed in the same BUSINESS schema.

Schema Separation Configuration

The tables in transact are classified into fixed schema category based on the functionality and will be used as part of the SCHEMA name. In addition, the schema name is stored in TAFJ_VOC table under the OTHERATTRIBUTES column. The following screen capture shows the TELLER application added under the BUSINESS schema.

Schema Separation in DLM

To enable schema separation, you need to run DL.INITIAL.SEPARATION and verify the LIST.GEN output in the files folder.

The tables in LIVE database can be classified into two types as follows.

ClosedCompanyNonVolatileTables

Companynonvolatile table should have otherattributes value appended with it. 

TELLER$HIS*FBNK.TELLER$HIS*D_F_TELLER*FBNK_TELLER#HIS*VALUE.DATE.1VALUE.DATE.2EXPOSURE.DATE.2*BUSINESS

If the table is available under default schema, then it will be appended with null value. 

FUNDS.TRANSFER$HIS*FBNK.FUNDS.TRANSFER$HIS*D_F_FUNDS_TRANSFER*FBNK_FUNDS_TRANSFER001*PROCESSING.DATE*
ClosedNonVolatileDataTables

Nonvolatiledatable files are updated by reading the content from companynonvolatiletable content and this should be updated with the schema value (otherattributes value).

With Schema Separation

Without Schema Separation

Scripts Execution

This section provides the scripts with and without schema separation in DLM.

ClosedLive Master scripts

ClosedRO Master Scripts

ClosedFBNK_RO-CreateDataTables.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_RO-CopyToDataTables.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_RO-CreateDataIndexes.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_RO-CreateRoViews.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_RO-CreateSynonms.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_LIVE-CreateIndexInitialMove.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_LIVE-CreateSynonms.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_LIVE-CreateRoViews.sql

With Schema Separation

Without Schema Separation

ClosedFBNK_LIVE-DeletePDateBatch.sql

ClosedFBNK_LIVE-DeleteSingleBatch.sql

With Schema Separation

Without Schema Separation

ClosedVOC update

With Schema Separation 

UPDATE TAFJ_VOC SET ASSOCIATED = 'FBNK.TELLER$HIS$RO' WHERE RECID = 'FBNK.TELLER$HIS';
INSERT INTO TAFJ_VOC (RECID,ORCLFILENAME,ORCLDICTNAME,ISBLOB,ISREADONLY,OTHERATTRIBUTES) VALUES('FBNK.TELLER$HIS$RO','RO.ro.FBNK_TELLER#HIS#RO','D_F_TELLER','X','Y',CONCAT('BUSINESS',CONCAT(FM(),CONCAT('',CONCAT(FM(),'')))));
UPDATE TAFJ_VOC SET ORCLFILENAME='RO.ro.FBNK_TELLER#HIS#ARC' WHERE RECID='FBNK.TELLER$ARC';

Without Schema Separation 

UPDATE TAFJ_VOC SET ASSOCIATED = 'FBNK.FUNDS.TRANSFER$HIS$RO' WHERE RECID = 'FBNK.FUNDS.TRANSFER$HIS';
INSERT INTO TAFJ_VOC (RECID,ORCLFILENAME,ORCLDICTNAME,ISBLOB,ISREADONLY,OTHERATTRIBUTES) VALUES('FBNK.FUNDS.TRANSFER$HIS$RO','RO.ro.FBNK_FUNDS_TRANSFER001#RO','D_F_FUNDS_TRANSFER','X','Y',CONCAT('',CONCAT(FM(),CONCAT('',CONCAT(FM(),'')))));
UPDATE TAFJ_VOC SET ORCLFILENAME='RO.ro.FBNK_FUNDS_TRANSFER001#ARC' WHERE RECID='FBNK.FUNDS.TRANSFER$ARC';


Bookmark Name Actions
BACK

In this topic

Feedback
x

Are you sure you want to log-off?