Patent application EP20180094A (EP), filed 2020-06-15
Publication number: EP3751426A1
Title: SYSTEM AND METHOD FOR MIGRATION OF A LEGACY DATASTORE
Abstract: System and method for migration of a legacy datastore include converting legacy datastore information from the legacy datastore to a target database system information. The target database system information belongs to a target database management system. A legacy datastore call is mapped to a data manipulation language (DML) statement. The legacy datastore call requests the legacy datastore information. Scripting language for the target database management system is generated using the DML statement.
IPC codes: G06F  16/    21            A I
Claims: number: 1
text: A system configured for migration of a legacy datastore, the system comprising:
number: 2
text: The system of claim 1, wherein the target database management system is a NoSQL database.
number: 3
text: The system of claim 1, wherein the target database management system is a relational database management system (RDBMS) or a non-relational database management system.
number: 4
text: The system of claim 1, wherein the converting of the legacy datastore information includes,
number: 5
text: The system of claim 1, wherein the converting of the legacy datastore information includes,
number: 6
text: The system of claim 1, wherein the mapping of the legacy datastore call to the at least one DML statement includes
number: 7
text: The system of claim 1, wherein
the generating of the scripting language for the target database management system using the at least one DML statement includes replacing the legacy datastore call with the at least one DML statement, and
the at least one DML statement is equivalent to the legacy datastore call.
number: 8
text: The system of claim 1, wherein the generating of the scripting language for the target database management system using the at least one DML statement further includes
identifying steps containing legacy datastore program by reading at least one source statement in source scripting language,
replacing steps containing the legacy datastore program with skeleton data.
number: 9
text: The system of claim 1, wherein the generating of the scripting language for the target database management system using the at least one DML statement includes identifying legacy datastore programming steps in a scripting language (SL) procedure, and replacing the identified legacy datastore programming steps with a terminal monitor program in the SL procedure.
number: 10
text: The system of claim 1, wherein the converting of the legacy datastore information includes,
reading the legacy datastore information from a corresponding copybook from the at least one legacy datastore, wherein the legacy datastore information is to be migrated from a source database management system, and
if a predetermined number of multi-value (MU) or periodic group (PE) clauses are present in the legacy datastore information, (i) creating a separate child table and (ii) adding a primary key of a parent table as a foreign key in the separate child table and a sequence number field as a key in the separate child table.
number: 11
text: The system of claim 1, wherein the mapping of the legacy datastore call to the at least one DML statement includes
reading an integrated data dictionary (IDD) file to obtain a record structure, and
identifying at least one selected from relationships, keys and data types based on the record structure.
number: 12
text: The system of claim 1, wherein
the generating of the scripting language for the target database management system using the at least one DML statement includes generating a data extraction program that extracts the legacy datastore information from the legacy datastore, and
the scripting language runs the data extraction program and uploads the legacy datastore information into the target database management system.
number: 13
text: The system of claim 1, wherein the instructions further include at least one selected from storing in an in-memory database or using an in-memory data grid, using database parallel execution framework or parallel processing framework, and storing data in a cache.
number: 14
text: A method of migration of a legacy datastore, the method comprising:
number: 15
text: The method of claim 14, wherein the target database management system is a NoSQL database.
number: 16
text: The method of claim 14, wherein the target database management system is a relational database management system (RDBMS) or a non-relational database management system.
number: 17
text: The method of claim 14, wherein the converting of the legacy datastore information includes,
number: 18
text: The method of claim 14, wherein the converting of the legacy datastore information includes,
number: 19
text: The method of claim 14, wherein the mapping of the legacy datastore call to the at least one DML statement includes
retrieving a qualified segment search argument (SSA), wherein the qualified SSA specifies the legacy datastore information, and wherein the legacy datastore information is a segment definition, and
constructing at least one DML statement from command code in the qualified SSA.
number: 20
text: The method of claim 14, wherein
the generating of the scripting language for the target database management system using the at least one DML statement includes replacing the legacy datastore call with the at least one DML statement, and
the at least one DML statement is equivalent to the legacy datastore call.
number: 21
text: The method of claim 14, wherein the generating of the scripting language for the target database management system using the at least one DML statement further includes
identifying steps containing legacy datastore program by reading at least one source statement in source scripting language,
replacing steps containing the legacy datastore program with skeleton data.
number: 22
text: The method of claim 14, wherein the generating of the scripting language for the target database management system using the at least one DML statement includes identifying legacy datastore programming steps in a scripting language (SL) procedure, and replacing the identified legacy datastore programming steps with a terminal monitor program in the SL procedure.
number: 23
text: The method of claim 14, wherein the converting of the legacy datastore information includes,
number: 24
text: The method of claim 14, wherein the mapping of the legacy datastore call to the at least one DML statement includes
reading an integrated data dictionary (IDD) file to obtain a record structure, and
identifying at least one selected from relationships, keys and data types based on the record structure.
number: 25
text: The method of claim 14, wherein
the generating of the scripting language for the target database management system using the at least one DML statement includes generating a data extraction program that extracts the legacy datastore information from the legacy datastore, and
the scripting language runs the data extraction program and uploads the legacy datastore information into the target database management system.
number: 26
text: The method of claim 14, wherein the instructions further include at least one selected from storing in an in-memory database or using an in-memory data grid, using database parallel execution framework or parallel processing framework, and storing data in a cache.
number: 27
text: A non-transitory computer readable medium having instructions embodied thereon that, when executed by a processor, cause the processor to perform operations comprising:
number: 28
text: The non-transitory computer readable medium of claim 27, wherein the target database management system is a NoSQL database.
number: 29
text: The non-transitory computer readable medium of claim 27, wherein the target database management system is a relational database management system (RDBMS) or a non-relational database management system.
number: 30
text: The non-transitory computer readable medium of claim 27, wherein the converting of the legacy datastore information includes,
number: 31
text: The non-transitory computer readable medium of claim 27, wherein the mapping of the legacy datastore call to the at least one DML statement includes
retrieving a qualified segment search argument (SSA), wherein the qualified SSA specifies the legacy datastore information, and wherein the legacy datastore information is a segment definition, and
constructing the at least one DML statement from command code in the qualified SSA.
number: 32
text: The non-transitory computer readable medium of claim 27, wherein
the generating of the scripting language for the target database management system using the at least one DML statement includes replacing the legacy datastore call with the at least one DML statement, and
the at least one DML statement is equivalent to the legacy datastore call.
number: 33
text: The non-transitory computer readable medium of claim 27, wherein the generating of the scripting language for the target database management system using the at least one DML statement further includes
identifying steps containing legacy datastore program by reading at least one source statement in source scripting language,
replacing steps containing the legacy datastore program with skeleton data.
number: 34
text: The non-transitory computer readable medium of claim 27, wherein the generating of the scripting language for the target database management system using the at least one DML statement includes identifying legacy datastore programming steps in a scripting language (SL) procedure, and replacing the identified legacy datastore programming steps with a terminal monitor program in the SL procedure.
number: 35
text: The non-transitory computer readable medium of claim 27, wherein the converting of the legacy datastore information includes,
number: 36
text: The non-transitory computer readable medium of claim 27, wherein the mapping of the legacy datastore call to the at least one DML statement includes
reading an integrated data dictionary (IDD) file to obtain a record structure, and
identifying at least one selected from relationships, keys and data types based on the record structure.
number: 37
text: The non-transitory computer readable medium of claim 27, wherein
the generating of the scripting language for the target database management system using the at least one DML statement includes generating a data extraction program that extracts the legacy datastore information from the legacy datastore, and
the scripting language runs the data extraction program and uploads the legacy datastore information into the target database management system.
number: 38
text: The non-transitory computer readable medium of claim 27, wherein the instructions further include at least one selected from storing in an in-memory database or using an in-memory data grid, using database parallel execution framework or parallel processing framework, and storing data in a cache.
Office action: search_report, dated 2020-12-16
Rejection reasons: novelty_epc_54
Prior art cited: ref_id: US201962861794P
ref_type: patent
severity: background
ref_id: US8745089B2
ref_type: patent
severity: background
ref_id: - "Software Evolution", 1 March 2008, SPRINGER BERLIN HEIDELBERG, Berlin, Heidelberg, ISBN: 978-3-540-76440-3, article TOM MENS ET AL: "Migration of Legacy Information Systems", pages: 105 - 138, XP055745751, DOI: 10.1007/978-3-540-76440-3_6
ref_type: npl
severity: background
ref_id: - ALZA A. MAHMOOD: "Automated Algorithm for Data Migration from Relational to NoSQL Databases", AL-NAHRAIN JOURNAL FOR ENGINEERING SCIENCES, vol. 21, no. 1, 10 February 2018 (2018-02-10), pages 60, XP055745753, ISSN: 2521-9154, DOI: 10.29194/NJES21010060
ref_type: npl
severity: background
ref_id: - GREG SILVA: "Paper 37-25 CODEBOOK: Taking Another Look At Your Data", 24 August 1999 (1999-08-24), XP055745750, Retrieved from the Internet <URL:https://support.sas.com/resources/papers/proceedings/proceedings/sugi25/25/ad/25p037.pdf> [retrieved on 20201102]
ref_type: npl
severity: background
ref_id: - ANONYMOUS: "The eXtensible Past: The Relevance of the XML Data Format for Access to Historical Datasets and a Strategy for Digital Preservation", 1 February 2005 (2005-02-01), XP055745749, Retrieved from the Internet <URL:http://www.dlib.org/dlib/february05/vannispen/02vannispen.html> [retrieved on 20201101]
ref_type: npl
severity: background
ref_id: - SUSHMA VELIMENETI: "Data Migration from Legacy Systems to Modern Database Recommended Citation Velimeneti, Sushma, "Data Migration from Legacy Systems to Modern Database" (2016). Culminating Projects in Mechanical and Manufacturing Engineering", 1 August 2016 (2016-08-01), XP055745748, Retrieved from the Internet <URL:https://repository.stcloudstate.edu/cgi/viewcontent.cgi?article=1054&context=mme_etds> [retrieved on 20201101]
ref_type: npl
severity: background
ref_id: - CHUCK MURRAY: "Oracle® SQL Developer", 1 January 2009 (2009-01-01), XP055745752, Retrieved from the Internet <URL:https://www.oracle.com/technetwork/testcontent/rptug-129645.pdf> [retrieved on 20201101]
ref_type: npl
severity: background
ref_id: US8745089
ref_type: patent
severity: background
ref_id: - Tom Mens ET AL, "Migration of Legacy Information Systems", Software Evolution, Berlin, Heidelberg, Springer Berlin Heidelberg, (20080301), pages 105 - 138, doi:10.1007/978-3-540-76440-3_6, ISBN 978-3-540-76440-3, XP055745751 [X] 1,3,7,10,11,16,20,24,26,30,32,36,37 * page  1  - page  5 * * page  6  - page  8 * * page  10  - page  16 * * page  17  - page  22 * * page  23  - page  31 * * figure 1 * [I] 2,4-6,8,9,12-15,17-19,21-23,25,27-29,31,33-35,38
ref_type: npl
severity: novelty_destroying
ref_id: - ALZA A. MAHMOOD, "Automated Algorithm for Data Migration from Relational to NoSQL Databases", AL-NAHRAIN JOURNAL FOR ENGINEERING SCIENCES, (20180210), vol. 21, no. 1, doi:10.29194/NJES21010060, ISSN 2521-9154, page 60, XP055745753 [A] 1-38 * the whole document *
ref_type: npl
severity: background
ref_id: - Greg Silva, "Paper 37-25 CODEBOOK: Taking Another Look At Your Data", (19990824), URL: https://support.sas.com/resources/papers/proceedings/proceedings/sugi25/25/ad/25p037.pdf, (20201102), XP055745750 [A] 1-38 * the whole document *
ref_type: npl
severity: background
Final disposition: pending (2020-12-16)