Audit User`s Manual - ALTIBASE Customer Support
Contents
1. curly braces used to indicate that a property value spans multiple lines 1 semicolon serves as a delimiter to separate multiple values double quotation marks are used to enclose a string such as a user name password table name or column name that includes one or more reserved words or special characters In ALTIBASE HDB the following are special characters S AB _ 2 1 E 1 Property Name A property name consists of characters other than spaces and identifies a property within a group 2 1 2 Property Value A property value be a single value multiple values or an expression The expression may include blanks Most properties have this format e g 1 TABLE EMPLOYEES A multiple value comprises several values separated by the delimiter and must be con tained within when it occupies more than one line see Example 2 The EXCLUDE group allows multiple values e g 2 EXCLUDE ENO DNO E FIRSTNAME or EXCLUDE ENO DNO E FIRSTNAME Expressions are character strings can include spaces and must be enclosed within The WHERE property is an expression e g 3 WHERE ENO gt 1000 and ENO lt 2000 2 1 3 Data Type Support ALTIBASE HDB does not support the use of CLOB and BLOB with Oracle databases The EXCLUDE property is used as follows to exclude a particular column or columns from Audit processing Audit2. 3 1 1 DIFF Example 1 Assuming that DB MASTER is set to host1 DB_SLAVE is set to host2 and that all records in each table are to be compared the environment file would appear as follows DB MASTER altibase sys man ager DSN host1 PORT NO 10111 NLS USE US7ASCII DB SLAVE altibase sys manager DSN host2 PORT NO 20111 NLS USE US7ASCII OPERATION DIFF MAX THREAD 1 DELETE IN SLAVE ON INSERT TO SLAVE ON INSERT TO MASTER ON UPDATE TO SLAVE ON AUTODETECT UNIQ INX ON LOG DIR M LOG FILE sample log EMP TABLE EMPLOYEES SCHEMA SYS DEPARTMENTS TABLE DEPARTMENTS SCHEMA SYS As can be seen in the above example the target tables in the master server host1 and the slave server host2 can have different names 3 1 2 DIFF Example 2 In the following example the ENO column of the EMP table is used as the basis for record selection and the JOIN DATE and SEX columns are excluded from the comparison According to the value of the CONDITION property the records in EMP that will be compared are limited to those for which ENO is greater than or equal to 1 and less than or equal to 20 In addition according to the value of the EXCLUDE property JOIN DATE and SEX will be excluded from the comparison In other words if only JOIN DATE and SEX differ as long as the other columns are the same the records will be han dled as though they were the same EMP TABLE EMPLOYEES
3. 5 MOSX NO MXSO NO MOSO SU Operation Type MASTER SLAVE INSERT Try 0 0 Audit User s Manual 22 3 2 Synchronization SYNC Example Fail 0 0 UPDATE Try X 0 Fail X 0 DELETE Try X 0 Fail X 0 UPDATE Try 0 0 Fail 0 0 OOP TPS 0 00 SCAN TPS 60240 96 Time 0 00 sec EMPLOYEES gt EMPLOYEES Fetch Rec In Master 20 Fetch Rec In Slave 15 MOSX NO MXSO NO MOSO SU Operation Type MASTER SLAVE INSERT Try 0 5 Fail 0 0 UPDATE Try X 0 Fail X 0 DELETE Try X 0 Fail X 0 UPDATE Try 0 5 Fail 0 0 OOP TPS 576 04 SCAN TPS 2304 15 Time 0 01 sec 23 Examples 3 2 Synchronization SYNC Example Audit User s Manual 24 Index A audit Environment File 4 audit execution option 9 audit property file 8 AUTODETECT_UNIQ_INX 10 Automatic synchronization 15 C CHECK INTERVAL 10 configuring audit utility 8 D DB MASTER 9 DB SLAVE 9 DELTE IN SLAVE 9 DIFF 4 13 18 different record DIFF 2 E EXCLUDE 11 Extraction DIFF Records logs 13 F FILE MODE MAX ARRAY 10 I INSERT_TO_ MASTER 9 INSERT_TO_SLAVE 9 M master DB 2 master server 2 MAX_THREAD 10 MOSO Inconsistency 2 MOSX Inconsistency 2 MXSO Inconsistency 2 O OPERATION 9 P property name 8 property value 8 S slave DB 2 slave server 2 25 SYNC 4 15 synchronization 20 synchronization policy MI Policy 3 SD Policy 3 SI Policy 3 SU Policy 3 T TABLE 11 TABLES group 10 U UPDATE TO
4. SYNC MAX THREAD 1 DELETE IN SLAVE OFF INSERT TO SLAVE ON INSERT TO MASTER OFF UPDATE TO SLAVE ON AUTODETECT UNIO INX ON LOG DIR LOG FILE sample log EMP TABLE EMPLOYEES SCHEMA SYS DEPARTMENTS TABLE DEPARTMENTS SCHEMA SYS As the SI policy is the synchronization policy used to resolve MOSX inconsistencies the INSERT TO SLAVE property value has been set to ON In contrast because MXSO inconsistencies are to be ignored the INSERT TO MASTER and DELETE IN SLAVE properties which are related to the MI and SD policies have been set to OFF 3 2 2 SYNC Example2 Suppose that records with MOSX inconsistencies i e that exist in the master server but not in the slave server are to be inserted into the slave server and that records with MXSO inconsistencies i e that exist in the slave server but not in the master server are to be inserted into the master server Master Server altibase sys man ager DSN host1 PORT NO 10111 NLS USE US7ASCII Slave Server altibase sys man ager DSN host2 PORT NO 20111 NLS USE US7ASCII OPERATION SYNC MAX THREAD 1 DELETE IN SLAVE OFF INSERT TO SLAVE ON Audit User s Manual 20 3 2 Synchronization SYNC Example INSERT TO MASTER ON UPDATE TO SLAVE ON AUTODETECT UNIQ INX ON LOG DIR LOG FILE sample log EMP TABLE EMPLOYEES SCHEMA SYS DEPARTMENTS TABLE DEPARTMENTS SCHEMA SYS As the SI poli
5. User s Manual 8 2 1 Configuring the Audit Utility Example 4 You should exclude certain column for AUDIT when CLOB column exists on EMP table TABLE EMP EXCLUDE ccc 2 1 2 Execution Options These options specify the information for accessing the local server and the remote server compari son DIFF and synchronization SYNC tasks and synchronization policies governing the handling of inconsistent records The properties that can be set in this group are as follows 2 1 2 1 DB MASTER This is used to set the server whose contents are to be accepted as correct if inconsistent records are found between two servers Set the user name and password the name or IP address of the server and NLS USE The property values must match the information in the property file in the Altibase home directory 2 1 2 2 DB SLAVE This is used to set the other server Set the user name and password the name or IP address of the server and NLS USE The property values must match the information in the property file in the Altibase home directory Additionally a text DB can be specified for the other server In this case the following format is used for this property where log is the directory containing the text DB DB SLAVE text user ID PW log 2 1 2 3 OPERATION This is set to DIFF for a comparison task or to SYNC for a synchronization task 2 1 2 4 INSERT TO SLAVE Sets the SI policy used to resolve MOSX inconsisten
6. Values error is raised in the Slave DB when inserting or updating data from the Master DB to the Slave DB This property value may be set to ON or OFF ON signifies that the record is to be deleted and OFF that it is not to be deleted This option can be set to ON only when both the INSERT_TO_SLAVE and DELETE IN SLAVE properties are also set to ON 2 1 2 9 CHECK_INTERVAL Sets the interval between the completion of a SYNC operation ona table and the start of a SYNC operation on the next table Expressed in units of ms milliseconds 2 1 2 10 MAX_THREAD Specifies the maximum number of threads that can run concurrently Set to 1 to specify an unlim ited number of threads 2 1 2 11 FILE MODE MAX ARRAY If its value is greater than 1 audit writes the fetched data to a file and then starts a SYNC or DIFF operation on the file This value is used to set the maximum size of array s for fetching data audit fetches a number of records equal to this value and writes them to a csv file This option can be used to realize better performance However when a target table has many LOB type columns this option may not improve performance This option can only be used between Alti base databases Example FILE MODE MAX ARRAY 1000 2 1 3 Table Group For defining information related to target table s The number of descriptions in the group must be as many as the number of target tables and the name
7. WHERE ENO gt 1 and ENO lt 20 EXCLUDE JOIN DATE SEX DEPARTMENTS 3 1 3 DIFF Example 3 In this example records are selected based on the ENO and JOIN_DATE columns of the EMP table Audit User s Manual 18 3 1 Comparison DIFF Example and the SEX column is excluded from the comparison EMP TABLE EMPLOYEES WHERE ENO gt 1 and ENO lt 20 or JOIN DATE gt 20001010 EXCLUDE SEX DEPARTMENTS According to the WHERE property the EMP records that will be compared are limited to those for which ENO is greater than or equal to 1 and less than or equal to 20 and for which JOIN_DATE is on or after October 10 2000 Also according to the EXCLUDE property SEX will be excluded from the comparison 19 Examples 3 2 Synchronization SYNC Example 3 2 Synchronization SYNC Example An example that uses OPERATION and TABLE in a synchronization policy to resolve inconsistent records will now be presented 3 2 1 SYNC Example 1 Suppose that records with MOSX inconsistencies i e that exist in the master server but not in the slave server are to be inserted into the slave server and that records with MXSO inconsistencies i e that exist in the slave server but not in the master server are to be ignored Master Server altibase sys man ager DSN host1 PORT NO 10111 NLS USE US7ASCII Slave Server altibase sys man ager DSN host2 PORT NO 20111 NLS USE US7ASCII OPERATION
8. comprises information about synchronization tasks conducted on inconsistent records and an error log that includes information about the errors that occurred during execution 2 3 3 1 Execution Log File This file is created with the name script file name log and displays the contents of the executed environment file as well as the summary of the synchronization SYNC task for the table s in each TABLES group The contents of the environment file are written to the log file as follows INFO MNG Tread O0 init is OK INFO MNG Tread 0 start is OK TAB 2 TAB 2 Fetch Rec In Master 3 Fetch Rec In Slave 2 MOSX SI MXSO MOSO SU MXSX Operation Type MASTER SLAVE INSERT Try 0 1 Fail 0 0 UPDATE Try X 1 Fail X 0 DELETE Try X 0 Fail x 0 15 Resolving Data Inconsistencies 2 3 Synchronization SYNC Function UPDATE Try 0 2 Fail 0 0 OOP TPS 13698 63 SCAN TPS 20547 95 Time 0 00 sec If a failure occurs for any record the cause of the error and the record contents are written to the log file Audit User s Manual 16 3 Examples This chapter describes examples of the use of the comparison DIFF and synchronization SYNC functions 17 Examples 3 1 Comparison DIFF Example 3 1 Comparison DIFF Example In the following example the EMP table on host1 is compared with the EMPLOYEES table on host2 and the DEPARTMENTS table on host1 is compared with the DEPARTMENTS table on host2
9. on a table by table basis and reconciling any inconsistencies that may be found between them Chapter2 Resolving Data Inconsistencies This chapter describes the Audit environment file which contains information for executing Audit and then describes the comparison DIFF and synchronization SYNC functions Chapter3 Examples This chapter describes examples of the use of the comparison DIFF and synchronization SYNC features References Audit User s Manual ii About This Manual For more detailed information please refer to the following documents ALTIBASE HDB Administrator s Manual ALTIBASE HDB Replication Manual ALTIBASE HDB iSQL User s Manual ALTIBASE HDB Utilities Manual ALTIBASE HDB Error Message Reference Online Manual Online versions of our manuals PDF or HTML are available from the Altibase Download Center http atc altibase com Altibase Welcomes Your Opinions Please feel free to send us your comments and suggestions regarding this manual Your comments and suggestions are important to us and may be used to improve future versions of the manual Please send your feedback to support altibase com making sure to include the following informa tion The name and version of the manual that you are using Your comments and suggestions regarding the manual Your full name address and phone number In addition to suggestions this address may also be used to report any errors or omissions di
10. other server in the event that a record is found to be inconsistent between two servers Either server can be designated as the slave server when Audit is executed 1 1 1 4 Slave DB The database on the slave server 1 1 2 Inconsistent Records An inconsistent record is a record in which a disagreement between column values is found when a designated table in the Master DB is compared with the corresponding table in the Slave DB on the basis of a primary key There are three types of inconsistency MOSX Inconsistency when a record based on a primary key can be found in the Master DB but not in the Slave DB MOSO Inconsistency when a record based on a primary key can be found in both the master and slave tables but the record contents are different MXSO Inconsistency when a record based on a primary key can be found in the Slave DB but not in the Master DB Audit User s Manual 2 1 1 Introduction 1 1 3 Synchronization Policy A Synchronization Policy is a policy that specifies how to synchronize inconsistent records The Audit application usually treats the Master DB as the reference DB and synchronizes the Slave DB with it ALTIBASE HDB provides four synchronization policies SU Policy This policy resolves MOSO inconsistencies by updating the Slave DB with the con tents of the Master DB Master DB Slave DB SI Policy This policy resolves MOSX inconsistencies by inserting records from the Master DB into t
11. Altibase Tool amp Utilities Audit User s Manual Release 5 5 1 amp ALTIBASE PERFORMANCE SOLUTIONS January 15 2013 Altibase Tools amp Utilities Audit User s Manual Release 5 5 1 Copyright 2001 2010 Altibase Corporation All rights reserved This manual contains proprietary information of Altibase Corporation it is provided under a license agreement containing restric tions on use and disclosure and is also protected by copyright patent and other intellectual property law Reverse engineering of the software is prohibited All trademarks registered or otherwise are the property of their respective owners Altibase Corporation 10F Daerung PostTower Il 182 13 Guro dong Guro gu Seoul 152 847 Korea Telephone 82 2 2082 1000 Fax 82 2 2082 1099 E mail support altibase com www http www altibase com Contents AE BIRA T E AE EAP EEE EEA E OEE E AE A SEE E EE E ves E Un ced dna a Se c Usi ee i About ThissMan al 4 2t aec d bee Re P e SER A NED dee Ni ii Intended AUG ICT e EE RR met ii Software Environment sotto ooi ari ei dea sueann dis arem elis epe bi perd obo tet ae ii How THIS Manuals Str ct red u ioter tti tete PR td aeneo Quaere Cone pedet R ii REfEr ENCES minisari ri i nAn E LL ii Online Man Wall RR ENE ERT e entend desert ssc iii Altibase Welcomes Your OpiniOFis ii tiet ten ede rtc dineerde nennen terende iii T OverVI W ns ssis 1 1
12. IntroductiOn annen 1 1 1 Audit Terminology 1 1 2 Inconsistent Records 1 1 3 Synchronization Policy 1 2 Executing the Audit Utility 2 Resolving Data EC II 7 2 1 Configuring the A dit Utility ertet Repetitio ei ette iceberg 8 2 1 1 THE AUGIE Environment ile ora cocotte ocu cnac ei et be ceto tube oer ce erbe ue AAA 8 2 12 Execution OPTIONS ua teet ee eee ede e veo ie Pe eee dende ede 9 2 4 35Table GrOUp casie asas ernst nantes aen EET on ba 10 2 2 Comparison DIFF deser o 13 2 2 1 Setting the DIFF Option in the Environment File essssssssssesccsseccsseecccssccsssseccssseccesusecessseescnsecesneeeesnseesssees 13 2 2 2 EXeCUtIOFDU sd edere HIT e AREE CAR ARNERER CR ANI EEER PEU ACERO EM CRI FERE EAR RENE Ie EXER 13 2 2 3 Execution Res lts zac tetti recon cia voit ctp a eati a E race aedi Aor rU 13 23 Synchronization SYNC FUMEHION sas rrt tertie dennen itl bre iddelen ellende eae huie 15 2 3 1 Setting the SYNC Option in the Environment File uu caanssenannseouneeeneunseeeanseeeuneeeeeunseeeunseeeuneerenevecenseenensee 15 2 3 2 EXeCULIOLIS cohors eet tta edi ON e dE AD eR TEN eU 15 2 3 3 Execution Results 25 3 b on ree ro e eia ee o ace RR E Po RE e ente ce mc cati 15 Bs EXAIMPIOS mee R 17 3 1 Comparison DIFF Example c ssscsssssssscsssssssessssssssscssscsssscsssssssscssnssssscsessessscssscsenscss
13. SLAVE 10 WwW WHERE 11 Index
14. base for each execu tion log file which includes execution result summary information and each table and creates an execution result file that includes the contents of the inconsistent columns of the records in which inconsistencies were found For example when running an Audit command such as user charlie altibase home audit audit sample cfg if the Audit command is executed successfully a file containing table information and named mas tertable username slavetable log is created in the audit directory for each table alongside sam ple log 2 2 3 1 Execution log file This file is created with the name script file name log and contains the contents of the executed environment file along with a summary of the comparison DIFF task for each table in the TABLES group The contents of the environment file are displayed as follows INFO MNG Tread O0 init is OK INFO MNG Tread O start is OK TAB 2 TAB 2 Fetch Rec In Master 3 Fetch Rec In Slave 2 MOSX DF Count 1 MXSO DF Count 0 MOSO DF Count 1 SCAN TPS 20547 95 Time 0 00 sec 2 2 3 2 Execution Result File This file is created with the name mastertable username slavetable log and displays the compari 13 Resolving Data Inconsistencies 2 2 Comparison DIFF Function son results in the following format DF m n COL N Vn M Vn_S PK gt PCOL V DF the type of inconsistency MOSX MOSO MXSO m the record number on the Mas
15. chema sql in the altibase home sample directory First a replication 21 Examples 3 2 Synchronization SYNC Example connection is established between the local server and the remote server On the local server IP 192 168 1 11 iSQL gt CREATE REPLICATION repl WITH 127 0 0 1 56342 FROM sys employees TO sys employees FROM sys departments TO sys departments Create Success isQL On the remote server IP 127 0 0 1 iSQL gt CREATE REPLICATION repl WITH 192 168 1 11 65432 FROM sys employees TO sys employees FROM sys departments TO sys departments Create Success isQL Here the current directory is user charlie altibase home audit vi sample cfg Master Server altibase sys man ager DSN 127 0 0 1 PORT NO 20582 NLS USE US7ASCII Slave Server altibase sys man ager DSN 192 168 1 11 PORT NO 20582 NLS USE US7ASCII OPERATION SYNC MAX THREAD 1 DELETE IN SLAVE ON INSERT TO SLAVE ON INSERT TO MASTER OFF UPDATE TO SLAVE ON AUTODETECT UNIO INX ON LOG DIR LOG FILE sample log EMPLOYEES WHERE ENO gt 1 and ENO lt 20 TABLE EMPLOYEES SCHEMA SYS DEPARTMENTS TABLE DEPARTMENTS SCHEMA SYS audit f sample cfg cat sample log INFO MNG Tread O0 init is OK INFO MNG Tread 1 init is OK INFO MNG Tread 0 start is OK INFO MNG Tread 1 start is OK DEPARTMENTS DEPARTMENTS Fetch Rec In Master 5 Fetch Rec In Slave
16. cies Specifies whether to insert the record in question into the Slave DB The property value is set to ON to specify that the record is to be inserted and OFF to specify that it is not to be inserted 2 1 2 5 INSERT TO MASTER Sets the MI policy used to resolve MXSO inconsistencies Specifies whether to insert the record in question into the Master DB The property value is set to ON to specify that the record is to be inserted and OFF to specify that it is not to be inserted This property and DELETE IN SLAVE can not both be set to ON simultaneously 2 1 2 6 DELETE IN SLAVE Sets the SD policy used to resolve MXSO inconsistencies Specifies whether to delete the record in 9 Resolving Data Inconsistencies 2 1 Configuring the Audit Utility question from the Slave DB The property value is set to ON to specify that the record is to be deleted and OFF to specify that it is not to be deleted This property and INSERT_TO_MASTER can not both be set to ON simultaneously 2 1 2 7 UPDATE_TO_SLAVE Sets the SU policy used to resolve MOSO inconsistencies Specifies whether to update the record in question in the Slave DB The property value is set to ON to specify that the record is to be changed and OFF to specify that it is not to be changed 2 1 2 8 AUTODETECT_UNIQ_INX Specifies whether to delete the record in question from the Slave DB and repeat the insert or update action if a Duplicate Key
17. cy is the synchronization policy used to remove inconsistent MOSX records the INSERT TO SLAVE property has been set to ON Moreover because records with MXSO inconsis tencies must be inserted into the master server the MI policy is necessary Therefore the INSERT TO MASTER property which is related to the MI policy is set to ON and the DELETE IN SLAVE property is set to OFF 3 2 3 SYNC Example 3 Suppose that the slave server is to be synchronized with the master server Master Server altibase sys man ager DSN host1 PORT NO 10111 NLS USE US7ASCII Slave Server altibase sys man ager DSN host2 PORT NO 20111 NLS USE US7ASCII OPERATION SYNC MAX THREAD 1 DELETE IN SLAVE ON INSERT TO SLAVE ON INSERT TO MASTER OFF UPDATE TO SLAVE ON AUTODETECT UNIO INX ON LOG DIR no LOG FILE sample log EMP TABLE EMPLOYEES SCHEMA SYS DEPARTMENTS TABLE DEPARTMENTS SCHEMA SYS To synchronize the slave server with the master server the Sl and SD synchronization policies are necessary Therefore the INSERT TO SLAVE and DELETE IN SLAVE properties are set to ON 3 2 4 Example This is a simple example that compares the employees table on the local server host1 with the employees table from which records having ENOs from 16 to 20 have been deleted on the remote server host2 and synchronizes SYNC the departments table on host1 with the departments table on host2 please refer to s
18. he Slave DB Master DB Slave DB MI Policy This policy resolves MXSO inconsistencies by inserting records from the Slave DB into the Master DB Master DB Slave DB SD Policy This policy resolves MXSO inconsistencies by deleting records from the Slave DB 3 Overview 1 1 Introduction Master DB Slave DB ee The SU policy SI policy MI policy and SD policy are set in the Audit environment file Note that the MI policy and the SD policy are mutually exclusive meaning that they cannot both be enabled at the same time 1 1 3 1 DIFF Creates an execution result file that identifies inconsistent records found during replication between the Master DB and the Slave DB 1 1 3 2 SYNC Identifies inconsistent records between the Master DB and the Slave DB bidirectionally resolves the inconsistencies according to the synchronization policy set in the Audit environment file and cre ates an execution result file including execution summary information and error information 1 1 3 3 Audit Environment File An environment file for setting options for Audit execution This file includes connection informa tion Audit function settings synchronization policies and the like Audit User s Manual 4 1 2 Executing the Audit Utility 1 2 Executing the Audit Utility To use the functions of Audit an Audit environment file which contains information about the table s on which DIFF or SYNC is to be executed must f
19. irst be created The Audit environment file will be explained in the Audit Environment File section of Chapter 2 Resolving Data Inconsistencies Audit commands have the following form audit f script file name script file name File name including the path of the environment file If current directory is as follows user charlie altibase home audit user charlie altibase home audit audit script file name or user charlie altibase home audit audit script file name 5 Overview 1 2 Executing the Audit Utility Audit User s Manual 2 Resolving Data Inconsistencies In this chapter the Audit environment file which contains information necessary for executing Audit is first explained and then the comparison DIFF and synchronization SYNC features are described 7 Resolving Data Inconsistencies 2 1 Configuring the Audit Utility 2 1 Configuring the Audit Utility Each of the comparison and synchronization tasks which are described in the environment file has its own unique properties The properties provide information necessary for running the Audit util ity Please refer to the sample cfg file in the ALTIBASE_HOME audit directory 2 1 1 The Audit Environment File Properties have the form property name property value and are case insensitive The following symbols have special meanings when used in the environment file it indicates a comment and causes the remainder of the line to be ignored
20. of each group must correspond to the name of a table in the Master DB The following properties can be set Audit User s Manual 10 2 1 Configuring the Audit Utility 2 1 3 1 WHERE Used to set conditions for selecting table records This property is described in the same way as a WHERE clause of a SQL statement Multiple values are permitted but the delimiter cannot be used to specify multiple values Moreover this property cannot be commented Applies to the comparison DIFF and synchronization SYNC functions Excluded Column DB DB2 DBi DB2 Vb 2 1 3 2 EXCLUDE For setting conditions for the projection of table records The property may have multiple values The specified columns are excluded from comparison and synchronization operations Applies to comparison DIFF and synchronization SYNC functions By suitably combining WHERE and EXCLUDE properties the result of a combined selection and projection operation can be obtained and an auditing task can be conducted on the result Excluded Column DB1 DB2 2 1 3 3 TABLE For setting the Slave DB table name In cases where the table names on the Master DB and the Slave 11 Resolving Data Inconsistencies 2 1 Configuring the Audit Utility DB differ from each other this must be explicitly described in order to use the comparison DIFF and synchronization SYNC functions When omitted it is assumed that the table name on the Slave DB is the
21. same as that on the Master DB The table name can contain Roman alphabetic characters numbers and the following special characters space S A amp _ However it cannot contain Korean characters This is specified for Audit to check table schema in Slave database Table schema in ALTIBASE HDB contains information of user s account If the schema of a user accessing the Slave database differs from the target table s schema this must be explicitly stated If this is not stated the error Table not found may occur when you try to execute Audit If this property is omitted the schema of the user accessing the Slave database will be used Audit User s Manual 12 2 2 Comparison DIFF Function 2 2 Comparison DIFF Function This function identifies inconsistent records that are found during replication between the Master DB and the Slave DB and creates an execution result file 2 2 1 Setting the DIFF Option in the Environment File In the Audit environment file set the OPERATION property to DIFF All execution option properties must be specified and the table group properties WHERE EXCLUDE TABLE and SCHEMA can be optionally specified 2 2 2 Execution The comparison DIFF function is executed as follows audit f script file name Script file name File name including the path of the environment file 2 2 3 Execution Results This function compares the contents of the Master Database and the Slave Data
22. scov ered in the manual which we will address promptly If you need immediate assistance with technical issues please contact the Altibase Customer Support Center We always appreciate your comments and suggestions iii Preface About This Manual Audit User s Manual 1 Overview This Chapter describes Audit and the consistency control methods for ALTIBASE HDB Replication Servers 1 Overview 1 1 Introduction 1 1 Introduction The intended use of the ALTIBASE HDB Audit utility is as a means of monitoring the progress of repli cation between two Altibase databases and resolving data inconsistencies that arise during the course of replication Audit compares an Altibase database with either an Altibase database or an Oracle database on a table by table basis and outputs information about any inconsistencies it finds It also includes functionality for synchronizing two databases in the event that data inconsistencies are discovered Note The Windows version of the ALTIBASE HDB server does not include the Audit utility 1 1 1 Audit Terminology 1 1 1 1 Master Server This is the server whose contents are accepted as correct in the event that a record is found to be inconsistent between two servers Either server can be designated as the master server when Audit is executed 1 1 1 2 Master DB The database on the master server 1 1 1 3 Slave Server This is the server whose contents are updated with the contents of the
23. sesensccsuscsssscesscssssessussessccssscsssccessesssecessesesss 18 3 T1 DIFF Example T ete nt E cete eo nene redeneerde n 18 3 1 2 DIFF Example 2 we 18 3 1 3 DIFF Example 3 we 18 3 2 Synchronization SYNC Example 3 2 1 SYNC Example 1 3 2 2 SYNC Example2 we 20 3 2 3 SYNC Example 3 21 3 24 Examples tese EAM M M MN M P M M D O 21 Preface About This Manual About This Manual This manual explains how to compare and check databases on replicated servers on a table by table basis and reconcile any inconsistencies that may be found between them Intended Audience The following users of ALTIBASE HDB will find this manual useful Database administrators Database users Technical support workers It is recommended that those reading this manual possess an understanding of the following back ground knowledge Basic knowledge in the use of computers operating systems and operating system utilities Experience in using relational databases and an understanding of database concepts Computer programming experience Experience in database server operating system or network administration Software Environment This manual has been written assuming that ALTIBASE HDB 5 5 1 is used as the database server How This Manual is Structured This manual has been organized as follows Chapter1 Overview This manual explains the functions for comparing databases on replication servers
24. ter server n the record number on the Slave server COL N the name of the first column found to contain differing values as the result of compar ison Vn M the value in the corresponding column on the Master server Vn S the value in the corresponding column on the Slave Server However for records that have LOB type columns the LOB column value is not output Audit User s Manual 14 2 3 Synchronization SYNC Function 2 3 Synchronization SYNC Function This function identifies records that are inconsistent between the Master DB and the Slave DB bidi rectionally resolves the inconsistencies according to the synchronization policy in the Audit configu ration file and creates an execution result file including execution summary information and error information 2 3 1 Setting the SYNC Option in the Environment File In the Audit environment file set the OPERATION property to SYNC All execution option properties must be described and the table group properties WHERE EXCLUDE TABLE and SCHEMA can be optionally specified 2 3 2 Execution The synchronization SYNC function is executed as follows shell gt audit f script file name script file name File name including the path of the configuration file 2 3 3 Execution Results This function compares the Master DB with the Slave DB for each execution log file which includes a summary of execution results and each table and outputs an execution result file that
Download Pdf Manuals
Related Search