US20020038315A1 - Replication system and program - Google Patents

Replication system and program Download PDF

Info

Publication number
US20020038315A1
US20020038315A1 US09/809,257 US80925701A US2002038315A1 US 20020038315 A1 US20020038315 A1 US 20020038315A1 US 80925701 A US80925701 A US 80925701A US 2002038315 A1 US2002038315 A1 US 2002038315A1
Authority
US
United States
Prior art keywords
replication
data
master
replica
tables
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US09/809,257
Other languages
English (en)
Inventor
Hiroshi Yokouchi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US10/101,065 priority Critical patent/US20020091716A1/en
Publication of US20020038315A1 publication Critical patent/US20020038315A1/en
Assigned to HITACHI, LTD. reassignment HITACHI, LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: YOKOUCHI, HIROSHI
Priority to US10/785,990 priority patent/US7519620B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275—Synchronous replication
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/273—Asynchronous replication or reconciliation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99932—Access augmentation or optimizing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99933—Query processing, i.e. searching
    • Y10S707/99934—Query formulation, input preparation, or translation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99943—Generating database or data structure, e.g. via user interface

Definitions

  • the present invention relates to a replication system, and in particular, to a replication system in which data of a plurality of master tables of a database is replicated in one replica table.
  • Known replication techniques include, for example, a technique described in JP-A-2000-20374.
  • This prior art relates to a replication system in which when a master table is operated, for example, by transaction processing, replication is automatically conducted for a replica table.
  • Each replica table has one master table in the replication system.
  • DBMS database management system
  • timing of replication must be determined, that is, how to allocate data of a plurality of master tables to the replication in one replica table; which one of the master tables is associated with the replication; or, whether or not replication is conducted after operations of all master tables.
  • a replication system in which according to operation information of addition, update, and deletion in a plurality of master tables associated with a database, one replica table is generated using a plurality of master tables. Replication is conducted such that data items of the master tables are joined with each other by establishing a matching state by use of particular data in the master tables as a joining key to thereby generate one replica table.
  • particular timing is selected from a plurality of timing to conduct a predetermined replication to thereby conduct the replication.
  • FIG. 1 is a block diagram showing constitution of an embodiment of a replication system according to the present invention
  • FIG. 2 is a table showing an example of a data layout of master table operation information
  • FIG. 3 is a table showing an example of a replication definition in a replication program
  • FIG. 4 is a table showing an example of a table indicating replication control tables used to control replication
  • FIG. 5 is a diagram showing an example of a flow of data
  • FIG. 6 is a flowchart showing an example of operation for replication in a replica table
  • FIG. 7 is a block diagram showing a configuration of another embodiment of a replication system according to the present invention.
  • FIG. 1 shows structure of an embodiment of a replication system according to the present invention in a block diagram.
  • the configuration of FIG. 1 includes master systems 100 and 101 , division servers 102 and 103 , job application programs 104 and 105 , database management systems 106 and 107 , master tables 108 and 109 , replication program operation information acquiring functions 110 and 111 , operation information storages 112 and 113 , master table operation information 114 and 115 , a basic job host (replica system) 116 , a replication program operation information reflecting function 117 , replication definition information 118 , a replication control table 119 , a replica database management system (DBMS) 120 , and a replica table 121 .
  • DBMS replica database management system
  • the embodiment of a replication system shown in FIG. 1 is applied to a salary calculation system by way of example.
  • the salary calculation system includes master systems 100 and 101 respectively including firm division servers 102 and 103 to control the master tables 108 and 109 , the replica DBMS 120 constituting the job host 116 of a salary system which manages the replica table 121 to execute monthly processing, and the replication program operation information reflecting function 117 including the replication definition information 118 defining a replication source table name and a replication destination table name and the like for replication.
  • the division server 102 of the employee management system to control the personal information control table (master table) 108 as a replication source and the division server 103 of the workday/holiday management system to control the workday/holiday control table (master table) 109 as a replication source respectively serve as replication source systems.
  • the division servers 102 and 103 respectively include user job application programs (UAP) to execute master table requests according to jobs, the master database management systems (master DBMS) 106 and 107 to respectively control and operate the master tables 108 and 109 , the operation information recording media 112 and 123 to respectively record master table operation information 114 and 115 , and the replication program operation information acquiring functions 110 and 111 to acquire information of master table operations.
  • UAP user job application programs
  • master DBMS master database management systems
  • operation information recording media 112 and 123 to respectively record master table operation information 114 and 115
  • replication program operation information acquiring functions 110 and 111 to acquire information of master table operations.
  • the replication program operation information acquiring functions 110 and 111 write table names associated with the operations, contents of the operations, and the like in files of the master table operation information 114 and 115 , respectively. It is also possible that the replication program operation information acquiring functions 110 and 111 respectively access the master tables 108 and 109 at a fixed interval of time to determine whether or not the master tables 108 and 109 have been changed. According to results of the determination, the replication program operation information acquiring functions 110 and 111 may write table names associated with the operations, contents of the operations, and the like in files of the master table operation information 114 and 115 , respectively.
  • the replication program operation information reflecting function 117 includes a replication defining section 118 to define items such as a name of a replication source table and a name of a replication destination table, which will be described later.
  • the replica DBMS 120 is a salary system to control and to operate the salary table (replica table) 121 .
  • the master table operation information includes a table name 201 of a master table operated, an operation type 202 of “insertion”,“update”, or “deletion”executed for the master table, and table data 203 of a master table for which one of the operations “insertion”, “update”, or “deletion” is conducted as shown in FIG. 2.
  • the replication definition includes a joining table definition 300 to define table names of joining master tables 108 and 109 and a name of a replica table 121 , a joining key definition 301 to define a data field as a key in master table data for a matching to join data items of a plurality of tables with each other, a replication timing definition 302 to define timing to replicate operation information 114 and 115 respectively of the joining master tables 108 and 109 in the replica table 121 , a joining master definition 310 to define a table name of a master table as a joining master in a case in which definitions 304 and 307 in the replication timing definition 302 are specified such that either one of a plurality of replication source tables is assigned as a master (joining master) and replication is conducted in the replica table 121 according to information of operation of the joining master table, an insufficient data definition 311 to define data to be set to the replica table in place of data of a master table having no operation information at this point of time in a case in which in the replication timing definition
  • the replication timing definition 302 defines, for data insertion, ⁇ circle over (1) ⁇ to insert data in the replica table when all data is set to a plurality of replication source tables for joining ( 303 ), ⁇ circle over (2) ⁇ to insert data in the replica table when data is set to primary tables (joining master) among a plurality of replication source tables for joining ( 304 ), or ⁇ circle over (3) ⁇ to insert data in the replica table when data is set to either one of a plurality of replication source tables for joining ( 305 ).
  • the replication timing definition 302 defines ⁇ circle over (1) ⁇ to delete pertinent data from the replica table when pertinent information of a plurality of replication source tables for joining is entirely deleted ( 306 ), ⁇ circle over (2) ⁇ to delete pertinent data from the replica table when primary tables (joining master) among a plurality of replication source tables for joining are deleted ( 307 ), ⁇ circle over (3) ⁇ to replace, for each data deletion of a plurality of replication source tables for joining, pertinent data from the replica table with insufficient data setting value and to delete pertinent data from the replica table when data of pertinent data is entirely deleted from a plurality of replication source tables for joining ( 308 ), or ⁇ circle over (4) ⁇ to delete pertinent data from the replica table when either one of the data items of a plurality of replication source tables for joining is deleted ( 309 ).
  • the input change timing definition 313 defines ⁇ circle over (1) ⁇ to change the input for each input of operation information or ⁇ circle over (2) ⁇ to change the input when next operation information is absent. (Whether or not “all data of a plurality of replication source tables for joining is inserted” of the data insertion ⁇ circle over (1) ⁇ is determined using the replication control information 407 stored in the replication control table shown in FIG. 4. This also applies to the replication timing definitions 304 to 309 . Which one of the operations has been conducted in which one of the tables is determined using the replication control information 407 stored in the replication control table. The replication control table will be described later.)
  • the replication control table 119 is a control table to join data of a plurality of master tables with each other to control replication of data in one replica table.
  • the replication control table 119 includes a table name 400 of a replica table defined in the replication definition, a table name 402 of a joining master table, a joining key 403 which is information for the matching of a plurality of joining master tables, for example, a joining key of a personal identifier number; replication timing 404 , a table 405 of a joining master table, an insufficient data setting value 406 , and replication control information 407 .
  • the system By analyzing the contents of files of the master table operation information 114 and 115 , the system stores in the replication control information 407 master table operation information for each joining key 408 contained in the table data 203 .
  • information of master table operation may be stored as follows.
  • the replication program operation information reflecting function 117 accesses the master table operation information 114 and 115 at a fixed interval of time to determine presence or absence of any information item of the master table operation information 114 and 115 not stored in the replication control information 407 . If such an information item is found, information items such as a joining key and an operation state are extracted from the information item to store the extracted information items in the replication control information 407 for each joining key.
  • the replication control information 407 includes a master table operation information state 409 indicating an operation state of each of the master tables, namely, “insert” to indicate that data of the joining key value is inserted to the master table, “no operation information” to indicate that nor information exists for operation, or “-” to indicate “deletion” and a replication state 410 indicating a replication state in the replica table, namely, “insert” to indicate that data of the pertinent joining key value is inserted in the replica table or “-” to indicate that the data is not inserted therein yet. (That is, the information stored in the replication control information 407 indicates the operation and the master table for which operation is conducted with the data corresponding to the joining key. According to the information, the replication program operation information reflecting function 117 determines operation to be conducted for the replica system.)
  • the replication program 117 may be specified to read the operation information 114 and 115 at a fixed interval of time.
  • a file manager program to control files of the operation information 114 and 115 is activated on a computer connected to the operation information recording media 112 and 113 .
  • the file manager program refers to the files of the operation information 114 and 115 at a fixed period of time to transmit data of updated sections of the files to the replication program 117 .
  • the replication program 117 accordingly updates the contents of the replication control table or reflects the data in the replica system. It is also possible that, each time the master table is operated in each master system, the condition is notified to the replication program operation information reflecting function 117 .
  • the replication program operation information acquiring functions 110 and 111 respectively obtain master table operation information 114 and 115 and then record the information 114 and 115 on the operation information recording media 112 and 113 , respectively.
  • the replication program operation information reflecting function 117 analyzes, at execution of processing of the function 117 , the replication definition 118 and develops the definition 118 in the replication control table 119 (the function 117 reads the replication definition 117 , extracts therefrom information necessary for the table 119 , and then stores the extracted information in the table 119 .) Thereafter, the function 117 reads the operation information 114 and 115 of the master tables 108 and 109 recorded respectively on the operation information recording media 112 and 113 , analyzes the information 114 and 115 , and registers a value to the pertinent joining key value 408 of the replication control table 119 .
  • the replication program operation information reflecting function 117 then makes a condition check according to the replication timing 404 and the control state of the replication control information 407 in the replication control table 119 , joins when necessary the operation information 114 of the master table 108 with the operation information 115 of the master table 109 , and issues an operation request of the replica table 121 to the replica DBMS 120 .
  • the function 117 When the replication program operation information reflecting function 117 is executed, the function 117 first analyzes the replication definition 118 to develop necessary information in the replication control table 119 (step 600 ).
  • FIG. 5 shows an example in which analysis results of the replication definition 118 are reflected in the replication control table 119 .
  • the replica table name is set as “salary”
  • the joining table name is set as “personal//workday/holiday”
  • the joining key is set as “number”
  • the replication timing is set as “at joining master operation”
  • the joining master table name is set as “personal”
  • an insufficient data setting value is set as space ‘ ⁇ ’.
  • the joining tables are “personal table” and “workday/holiday table”
  • the replica table is “salary table”
  • data as a key to join data from the replication source table is “number”
  • the replication timing is “when an operation is conducted in the joining master table”
  • the joining master table name is “personal table”
  • the insufficient data setting value is “space ‘ ⁇ ’”.
  • the system manager may beforehand prepare and stores the replication definition 118 in a recording medium which can be accessed by the replication program. It is also possible to provide a function in which a plurality of replication definitions are beforehand stored in a storage with identifiers assigned to the respective definitions such that the replication program selects a necessary one of the definition using the identifier.
  • the function 117 then inputs the operation information 510 to 513 of the master table 108 and 109 from the operation information recording media 112 and 113 (the function 117 accesses the media 112 and 113 to read information 510 to 513 from the master tables 108 and 109 ).
  • the function 117 analyzes the master table names 504 and 507 , the operation types 505 and 508 , and the joining keys 506 and 509 (step 601 ).
  • a condition check is conducted according to presence or absence of registration of the operation types 505 and 508 of the operation information 510 to 513 and the joining key 516 of the operation information 510 to 513 in the replication control table 119 (step 602 ).
  • step 602 if the joining key 516 of the information 510 to 513 in the table 119 is absent, the joining keys 521 and 535 of the operation information 510 to 513 and the operation information state 517 are registered to the replication control table 119 (step 607 ).
  • the joining key “ 222 ” and the operation type “insert” are extracted from the operation information 510 and are then stored in the pertinent places of the table. Since the table name of the operation information 510 is “personal”, the operation type “insert” is stored in a place 522 corresponding to the joining key “ 222 ” in the column of “personal” in the operation information state 517 .
  • step 602 if the operation types 505 and 508 are “insert” or “delete” and the joining key 516 of the pertinent operation information in the replication control table 119 is present, the operation information state 517 of the replication control table 119 is updated (step 606 ).
  • step 602 if the operation types 505 and 508 are “update”, no operation is conducted for the replication control table 119 .
  • the joining key is defined as “joining key: number” in the replication control table 119
  • the replication program operation information reflecting function 117 extracts the number “ 222 ” from the data of the operation information 510 in the master table operation information 114 and then stores “ 222 ” as the joining key value in the field 521 .
  • the function 117 extracts the operation type “insert” from the data of the operation information 510 .
  • the extracted information “insert” is stored in the field 522 in association with the joining key “ 222 ” and the table name “personal” as the operation object of the operation information 510 .
  • the joining key is set to the field 525 since the value “ 123 ” of the joining key corresponding to the operation information 511 is absent in the replication control table 119 .
  • the operation type of the operation information 511 is “delete”
  • “insert” is set to the operation information state 526 in the personal information management table
  • “-” and “insert” are respectively set to the operation information state 527 and the replication state 528 of the workday/holiday management table.
  • the replication timing is “at joining master table operation” and the joining master table is “personal information management table”, the replication timing is associated with operation of the joining master table.
  • the replication control table 119 since the replication control table 119 includes the joining key 521 , only “insert” is set to the operation information state 523 of the workday/holiday table.
  • the operation information state 526 of the personal information management table set to “insert” in association with the workday/holiday management table control information 511 is changed to “-”.
  • a condition check is made for the operation types 505 and 508 of the operation information 510 to 513 , the definition of the replication timing definition 302 , and the operation information state 517 of the replication control table (steps 608 and 611 ).
  • the joining master is the workday/holiday management table 109
  • the operation is conducted in the same way as in the case in which the “insert” definition of the replication timing definition 302 is “ ⁇ circle over (1) ⁇ Insert data in replica table when all data is set to a plurality of replication source tables for joining” 303 .
  • the definition of “delete” of the replication timing definition 302 is “ ⁇ circle over (2) ⁇ Delete pertinent data from replica table when primary tables (joining master) among a plurality of replication source tables for joining are deleted” 307 and the personal information management table 108 is a joining master, the data field 531 of the operation information 511 in the replica table 121 is updated to “space” at input of the operation information 151 . Thereafter, at input of the operation information 513 , the data 530 is deleted. When the joining master is the workday/holiday management table 109 , the data 530 is deleted at input of the operation 511 . At input of the operation information 513 , operation is not conducted for the replica table 121 .
  • replication can be conducted from a plurality of master tables to one replica table, and a job in which a plurality of tables are accessed can be changed to a job which can be executed by accessing only one replica table. Therefore, the period of time required for the job execution can be reduced.
  • a correspondence is established between particular data in the data of a plurality of master tables and keys (joining keys).
  • the data field for a key is defined by the replication definition 118 .
  • Timing of replication for the replica table 121 is also defined in the program 117 to execute replication.
  • the replication program 117 generates, at execution thereof, the control table 119 according to the definition 118 and manages the operation states of a plurality of master tables 108 and 109 and the replication state of the replica table to thereby conduct replication for the replica table 121 at the defined timing.
  • FIG. 7 shows in a block diagram a configuration of another embodiment of a replication system in accordance with the present invention.
  • the configuration of FIG. 7 includes a hierarchic databases 700 to 702 .
  • the present invention is applied to a hierarchic databases 700 to 702 which is a database of a master system. That is, in place of the master tables 108 and 109 of FIG. 1, a plurality of hierarchic databases 700 , 701 , and 702 are employed as replication sources. Also in this construction, like in the embodiment above, the period of time required for the job execution can be minimized in a replica system in which data of a plurality of master tables is replicated in one replica table.
  • data of a plurality of master tables can be replicated in one replica table. Therefore, a job in which a plurality of tables are accessed can be changed to a job in which one replica table is accessed, and hence the job execution time can be remarkably reduced.
  • the maintenance of the replica table can be also simplified.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
US09/809,257 2000-09-27 2001-03-16 Replication system and program Abandoned US20020038315A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/101,065 US20020091716A1 (en) 2000-09-27 2002-03-20 Replication system and program
US10/785,990 US7519620B2 (en) 2000-09-27 2004-02-26 Replication system, method and program for replicating a plurality of databases into a replica database

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2000294551A JP4497691B2 (ja) 2000-09-27 2000-09-27 データベース管理方法及び管理システム
JP2000-294551 2000-09-27

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US10/101,065 Continuation US20020091716A1 (en) 2000-09-27 2002-03-20 Replication system and program
US10/785,990 Continuation US7519620B2 (en) 2000-09-27 2004-02-26 Replication system, method and program for replicating a plurality of databases into a replica database

Publications (1)

Publication Number Publication Date
US20020038315A1 true US20020038315A1 (en) 2002-03-28

Family

ID=18777138

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/809,257 Abandoned US20020038315A1 (en) 2000-09-27 2001-03-16 Replication system and program
US10/101,065 Abandoned US20020091716A1 (en) 2000-09-27 2002-03-20 Replication system and program
US10/785,990 Expired - Fee Related US7519620B2 (en) 2000-09-27 2004-02-26 Replication system, method and program for replicating a plurality of databases into a replica database

Family Applications After (2)

Application Number Title Priority Date Filing Date
US10/101,065 Abandoned US20020091716A1 (en) 2000-09-27 2002-03-20 Replication system and program
US10/785,990 Expired - Fee Related US7519620B2 (en) 2000-09-27 2004-02-26 Replication system, method and program for replicating a plurality of databases into a replica database

Country Status (2)

Country Link
US (3) US20020038315A1 (https=)
JP (1) JP4497691B2 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240211437A1 (en) * 2022-04-24 2024-06-27 Morgan Stanley Services Group Inc. Distributed query execution and aggregation across multiple datasets

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2384174A1 (en) * 2002-04-29 2003-10-29 Ibm Canada Limited-Ibm Canada Limitee Classification of data for insertion into a database
US20030236874A1 (en) * 2002-06-04 2003-12-25 Timo Hotti Method and arrangement for providing an information management system
US8244913B1 (en) * 2004-10-13 2012-08-14 Progress Software Corporation Replication horizon determination with an independent distributed database system
US7376675B2 (en) * 2005-02-18 2008-05-20 International Business Machines Corporation Simulating multi-user activity while maintaining original linear request order for asynchronous transactional events
US9286346B2 (en) * 2005-02-18 2016-03-15 International Business Machines Corporation Replication-only triggers
US8214353B2 (en) * 2005-02-18 2012-07-03 International Business Machines Corporation Support for schema evolution in a multi-node peer-to-peer replication environment
US8037056B2 (en) * 2005-02-18 2011-10-11 International Business Machines Corporation Online repair of a replicated table
JP5050358B2 (ja) 2006-01-27 2012-10-17 日本電気株式会社 データ複製システムおよびデータ複製方法
US20080059469A1 (en) * 2006-08-31 2008-03-06 International Business Machines Corporation Replication Token Based Synchronization
JP5357068B2 (ja) * 2010-01-20 2013-12-04 インターナショナル・ビジネス・マシーンズ・コーポレーション 情報処理装置、情報処理システム、データ・アーカイブ方法およびデータ削除方法
US9275086B2 (en) 2012-07-20 2016-03-01 Commvault Systems, Inc. Systems and methods for database archiving
US9720787B2 (en) 2013-01-11 2017-08-01 Commvault Systems, Inc. Table level database restore in a data storage system
JP5913440B2 (ja) * 2014-06-10 2016-04-27 株式会社三菱東京Ｕｆｊ銀行 サーバおよびプログラム
US20160210306A1 (en) 2015-01-15 2016-07-21 Commvault Systems, Inc. Managing structured data in a data storage system
US10108687B2 (en) 2015-01-21 2018-10-23 Commvault Systems, Inc. Database protection using block-level mapping
US9904598B2 (en) 2015-04-21 2018-02-27 Commvault Systems, Inc. Content-independent and database management system-independent synthetic full backup of a database based on snapshot technology
US11561993B2 (en) 2018-08-08 2023-01-24 Ab Initio Technology Llc Generating real-time aggregates at scale for inclusion in one or more modified fields in a produced subset of data
US11269732B2 (en) 2019-03-12 2022-03-08 Commvault Systems, Inc. Managing structured data in a data storage system
US11514066B2 (en) * 2019-11-08 2022-11-29 Servicenow, Inc. System and methods for querying and updating databases

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03257529A (ja) * 1990-03-07 1991-11-18 Hitachi Ltd 推論管理システムおよび方法
US5261092A (en) * 1990-09-26 1993-11-09 Honeywell Inc. Synchronizing slave processors through eavesdrop by one on periodic sync-verify messages directed to another followed by comparison of individual status
JP3516344B2 (ja) * 1990-10-22 2004-04-05 株式会社日立製作所 分散処理システムの多重データ処理方法
JPH0798669A (ja) * 1993-08-05 1995-04-11 Hitachi Ltd 分散データベース管理システム
WO1995008809A2 (en) * 1993-09-24 1995-03-30 Oracle Corporation Method and apparatus for data replication
US5553279A (en) * 1993-10-08 1996-09-03 International Business Machines Corporation Lossless distribution of time series data in a relational data base network
GB9402935D0 (en) * 1994-02-16 1994-04-06 British Telecomm A method for controlling access to a database
US5745753A (en) * 1995-01-24 1998-04-28 Tandem Computers, Inc. Remote duplicate database facility with database replication support for online DDL operations
US5757669A (en) * 1995-05-31 1998-05-26 Netscape Communications Corporation Method and apparatus for workgroup information replication
US5937415A (en) * 1995-12-13 1999-08-10 Sybase, Inc. Data base development system with methods facilitating copying of data from one data source to another
US5884324A (en) * 1996-07-23 1999-03-16 International Business Machines Corporation Agent for replicating data based on a client defined replication period
US5758337A (en) * 1996-08-08 1998-05-26 Microsoft Corporation Database partial replica generation system
US5870765A (en) * 1996-10-09 1999-02-09 Oracle Corporation Database synchronizer
US5870761A (en) * 1996-12-19 1999-02-09 Oracle Corporation Parallel queue propagation
US5983217A (en) * 1997-03-21 1999-11-09 At&T Corp Apparatus and method for querying replicated databases
US5873074A (en) * 1997-04-18 1999-02-16 Informix Software, Inc. Applying distinct hash-join distributions of operators to both even and uneven database records
WO1999008209A1 (en) * 1997-08-08 1999-02-18 Bell Communications Research, Inc. High performance asynchronous data replication
US5924096A (en) * 1997-10-15 1999-07-13 Novell, Inc. Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand
US6202070B1 (en) * 1997-12-31 2001-03-13 Compaq Computer Corporation Computer manufacturing system architecture with enhanced software distribution functions
US6532479B2 (en) * 1998-05-28 2003-03-11 Oracle Corp. Data replication for front office automation
US6112209A (en) * 1998-06-17 2000-08-29 Gusack; Mark David Associative database model for electronic-based informational assemblies
US6625593B1 (en) * 1998-06-29 2003-09-23 International Business Machines Corporation Parallel query optimization strategies for replicated and partitioned tables
JP2000020374A (ja) 1998-07-01 2000-01-21 Nec Corp レプリケーション制御システム
US6615223B1 (en) * 2000-02-29 2003-09-02 Oracle International Corporation Method and system for data replication
US6622152B1 (en) * 2000-05-09 2003-09-16 International Business Machines Corporation Remote log based replication solution
US6567823B1 (en) * 2000-08-07 2003-05-20 Corigin Ltd. Change propagation method using DBMS log files
US6745209B2 (en) * 2001-08-15 2004-06-01 Iti, Inc. Synchronization of plural databases in a database replication system

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240211437A1 (en) * 2022-04-24 2024-06-27 Morgan Stanley Services Group Inc. Distributed query execution and aggregation across multiple datasets

Also Published As

Publication number Publication date
JP2002108681A (ja) 2002-04-12
US7519620B2 (en) 2009-04-14
JP4497691B2 (ja) 2010-07-07
US20020091716A1 (en) 2002-07-11
US20040167936A1 (en) 2004-08-26

Similar Documents

Publication Publication Date Title
US7519620B2 (en) Replication system, method and program for replicating a plurality of databases into a replica database
US8103704B2 (en) Method for database consolidation and database separation
US7191184B2 (en) Optimized storage for measurement data
US6367077B1 (en) Method of upgrading a software application in the presence of user modifications
US5613113A (en) Consistent recreation of events from activity logs
US6564215B1 (en) Update support in database content management
US6240416B1 (en) Distributed metadata system and method
US7672966B2 (en) Adding extrinsic data columns to an existing database schema using a temporary column pool
US20060101092A1 (en) Computer system and method for managing file versions
US20030105811A1 (en) Networked data stores for measurement data
US5687367A (en) Facility for the storage and management of connection (connection server)
US5375237A (en) Computerized method of creating a convenient dictionary representing data structures for use by a plurality of program products
US6470343B1 (en) Method, computer program product, system, and data structure for database data model extension
US7236993B2 (en) On-demand multi-version denormalized data dictionary to support log-based applications
US7113951B2 (en) Method and system for detecting tables to be modified
US7376658B1 (en) Managing cross-store relationships to data objects
JP2000163303A (ja) ディレクトリデータ変換方法、ディレクトリデータ変換プログラムが記憶された記憶媒体、およびディレクトリ変換サーバ
US6401100B1 (en) Method for associating classes contained in the same or different models
US20060155747A1 (en) Apparatus and method for automating the logging of table changes in a database
US7526469B2 (en) Method and system of database management with shared area
US20030061195A1 (en) Technical data management (TDM) framework for TDM applications
US7016906B1 (en) Data processing method and apparatus employing OLE DB and having dual schema and auto update features
US6789074B1 (en) Database processing method and apparatus, and medium for recording processing program thereof
US7047234B2 (en) System and method for managing database access
US20070156746A1 (en) Information management system and method

Legal Events

Date Code Title Description
AS Assignment

Owner name: HITACHI, LTD., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YOKOUCHI, HIROSHI;REEL/FRAME:014058/0444

Effective date: 20010226

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION