CN109299072A - A kind of method and device that database migrates online - Google Patents
A kind of method and device that database migrates online Download PDFInfo
- Publication number
- CN109299072A CN109299072A CN201811202820.3A CN201811202820A CN109299072A CN 109299072 A CN109299072 A CN 109299072A CN 201811202820 A CN201811202820 A CN 201811202820A CN 109299072 A CN109299072 A CN 109299072A
- Authority
- CN
- China
- Prior art keywords
- database
- data block
- data
- target
- target database
- 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.)
- Granted
Links
Abstract
The present invention proposes a kind of method that database migrates online, source database successively reads the data block of all data blocks and all changes in source database online, they are synchronized to target database, data block is written to local data file by target database, and changed by target database in the additions and deletions for locally completing these data blocks, to reach and the consistent state of source database.If it is spanning operation system platform, the migration of file type, object library client database completes conversion and targeted database data file is written in data block, and the present invention also provides a kind of devices that database migrates online, database not only may be implemented to migrate online, and database cross operating system platform, the online migration across data file class may be implemented, reduce business interruption time, improve transport efficiency, reduces the technical requirements to database transport extraction teacher.
Description
Technical field
The present invention relates to database migration method and devices, more particularly, to a kind of method and device that database is online.
Background technique
There are the change request of many databases in relevant database use process, such as: server replacement, storage
Replacement, computer room resettlement etc., these change request may need database moving to new system from a system.Database
Migration is general, and there are as below methods: the backup logic carried using database and recovery, database included physical backup and recovery,
Database close after cold duplication, use and store included copy function and realize that data copy between two storages.These migrations
More or less all there are some scene restrictions in method, such as: backup logic, which restores migration pattern, to be needed to stop operation system completely,
Data are completely consistent database just can guarantee migration in the case where changing there is no additions and deletions after, and the bigger service disconnection of data volume
Time is longer, is suitable only for allowing downtime long enough and the less big database migration of data volume；Physical backup is extensive
Then multiple migration pattern can be restored in the non-stop-machine situation of operation system to database online backup in target side,
The backup and recovery for carrying out increment again after stopping operation system are migration patterns more commonly used at present, but it requires source
It is identical with target end-host operating system platform (such as: LINUX to LINUX, AIX (Advanced Interactive
EXecutive is a set of class UNIX operating system of IBM exploitation) arrive AIX etc.), if CPU platform different operation gets up to compare
Complexity, so substantially only being migrated between biconditional operation system platform, in addition physical backup restores migration pattern to engineer
Technical requirements are higher, and operation difficulty is larger.
Summary of the invention
The present invention proposes what a kind of database migrated online to solve the problems, such as that database migrates online in the prior art
Method and apparatus, source database read all data blocks in source database online, they are synchronized to target database, by target
Data block is written to local data file by client database, is changed by target database in the additions and deletions for locally completing these data blocks,
To reach with the consistent state of source database, and if it is the migration of spanning operation system platform, object library client database meeting
It is automatically performed the conversion of size byte and data file is written into data block, if the data of source database and target database are literary
Part type is different, and target client database can be automatically performed conversion, database not only may be implemented and migrate online, but also can be real
Existing database cross operating system platform, the online migration across data file class, transition process do not need to stop operation system and
Database reduces business interruption time, improves transport efficiency, reduces the technical requirements to database transport extraction teacher.
First aspect present invention provides a kind of method that database migrates online, comprising:
Configuration database parameter, starting critical processes and storage allocation are used for target database；
Source database sends data block to target database, migration for spanning operation system platform, target database into
Simultaneously data file is written in data block by row size byte conversion, according to the data file class of target database configuration by data block
Specified data file is written；
Target database modifies change to data block in local after the data block of source database synchronously completes.
With reference to first aspect, in a first possible implementation of that first aspect, the configuration database parameter includes
The parameter of source database and target database is configured, specifically: for specifying the road of source database data block variation record file
The parameter migrate_block_change_trace of diameter and title, data file name is converted into mesh by rule in source database
The parameter migrate_datafile_name_tranform of the data file name in database is marked, migrating processes quantity is used for
The parameter migrate_process_num of control, the parameter of the catalogue for specifying target database migration generation data file
Migrate_datafile_create_directory, for specifying the parameter migrate_target of target database information.
With reference to first aspect, in a second possible implementation of that first aspect, the starting critical processes include writing
Data file process reads data file process, checkpointing, log process, and the storage allocation is used for target database
Including data-block cache area, data dictionary buffer area.
With reference to first aspect, in first aspect in the third possible implementation, the source database sends data block
Be specifically to target database: source database backstage log-on data block sends process, and number of processes is by being used for migrating processes quantity
The parameter migrate_process_num of control is controlled, and the data block that source database is read sends process by data block and is sent to
Target database, target database have a respective data blocks receiving process, and number of processes is by the ginseng that controls for migrating processes quantity
Number migrate_process_num control, data block transmission number of processes is identical with data block receiving process quantity, data block hair
It is sent into the data block reception process that journey goes matching target client database.
With reference to first aspect, in the 4th kind of possible implementation of first aspect, the data block sends process and goes
Data block reception process with target client database is specifically: source block sends process according to target database address, port
The data block reception process of information and target database is connected using the mode of TCP three-way handshake, after three-way handshake success, data
Block sends process and data block reception process establishes connection.
With reference to first aspect, in the 5th kind of possible implementation of first aspect, data block is written target database
Data file is specifically: after target database receives data block, judging that the operating system of source database and target database operate
Whether system is consistent, if unanimously, targeted database data file directly is written in data block, if it is inconsistent, logarithm
Size byte conversion, that is, converted magnitude byte storage tandem is carried out according to block, target data is written into data block again after conversion
Library data file.
With reference to first aspect, described to be configured according to target database in the 6th kind of possible implementation of first aspect
Data file class by data block write-in specified data file be specifically: after target database receives data block, judge source
Whether the file type of database configuration and the file type that target database configures are consistent, if unanimously, directly by data
The data file under the specified file system directories of target database is written in block, if it is inconsistent, being matched according to target database
The parameter and file type set are completed to convert and be written the data file under the specified file system directories of target database.
Second aspect of the present invention provides a kind of device that database migrates online, comprising:
Preparation module, configuration database parameter, starting critical processes and storage allocation are configured for target database use；
Sending synchronization module, source database sends data block to target database, migration for spanning operation system platform,
Target database carries out size byte conversion and data file is written in data block, the data file configured according to target database
Specified data file is written in data block by type；
Modification change module, target database after the data block of source database synchronously completes, local to data block into
Row modification change.
The technical solution adopted by the present invention includes following technical effect:
The present invention proposes a kind of method that database migrates online, and source database reads all data in source database online
They are synchronized to target database by block, data block are written to local data file by target client database, synchronizing process is opened
After beginning, source database will record the data block of all changes in library, at least once transmit the data block of these variations and information
To target database, changed by target database in the additions and deletions for locally completing these data blocks, to reach consistent with source database
State.If it is spanning operation system platform, the migration of file type, object library client database, which can be automatically performed, to be converted and will count
Targeted database data file is written according to block, and the present invention also provides a kind of device that database migrates online, not only may be used
To realize that database migrates online, and database cross operating system platform, moving online across data file class may be implemented
It moves, transition process does not need to stop operation system and database, reduces business interruption time, improves transport efficiency, reduces
To the technical requirements of database transport extraction teacher.
General description and following detailed description more than it should be understood that be only it is exemplary and explanatory, not
It can the limitation present invention.
Detailed description of the invention
Illustrate the embodiment of the present invention or technical solution in the prior art to become apparent from, it below will be to embodiment or existing
Attached drawing needed in technical description is briefly described, it is clear that, for those of ordinary skills,
Under the premise of not making the creative labor, it is also possible to obtain other drawings based on these drawings.
The flow diagram of embodiment of the method one in Fig. 1 the present invention program；
The flow diagram of embodiment of the method two in Fig. 2 the present invention program；
The flow diagram of embodiment of the method three in Fig. 3 the present invention program；
The structural schematic diagram of Installation practice four in Fig. 4 the present invention program.
Specific embodiment
In order to clarify the technical characteristics of the invention, below by specific embodiment, and its attached drawing is combined, to this hair
It is bright to be described in detail.Following disclosure provides many different embodiments or example is used to realize different knots of the invention
Structure.In order to simplify disclosure of the invention, hereinafter the component of specific examples and setting are described.In addition, the present invention can be with
Repeat reference numerals and/or letter in different examples.This repetition is that for purposes of simplicity and clarity, itself is not indicated
Relationship between various embodiments and/or setting is discussed.It should be noted that illustrated component is not necessarily to scale in the accompanying drawings
It draws.Present invention omits the descriptions to known assemblies and treatment technology and process to avoid the present invention is unnecessarily limiting.
Embodiment one
As shown in Figure 1, a kind of method that database migrates online in technical solution of the present invention, comprising:
S1, configuration database parameter, starting critical processes and storage allocation are used for target database；
S2, source database send data block to target database, migration for spanning operation system platform, target database
It carries out size byte conversion and data file simultaneously is written into data block, according to the data file class of target database configuration by data
Specified data file is written in block；
S3, target database modify change to data block in local after the data block of source database synchronously completes.
In step sl, it configures source database and the parameter of target database is specifically included for specifying source database data
Block variation records the path of file and the parameter migrate_block_change_trace of title, data file in source database
Title is converted into the parameter migrate_datafile_name_ of the data file name in target database by rule
Tranform, for the parameter migrate_process_num of migrating processes quantity control, for specifying target database to migrate
The parameter migrate_datafile_create_directory for generating the catalogue of data file, for specifying target database
The parameter migrate_target of information.
Wherein, for specifying the path of source database data block variation record file and the parameter migrate_ of title
Block_change_trace: the parameter is used to specify path and the title of source database data block variation record file, setting
Format is that migrate_block_change_trace='/root/tracefile.trc', wherein file name and suffix do not have
It requires to must be provided with the parameter before thering is fixed requirement, migration to start.
Data file name is converted into the parameter of the data file name in target database by rule in source database
Migrate_datafile_name_tranform: the parameter is for specifying Data Filename transformation rule, i.e., in source database
Data file name is converted into the data file name in target database by the rule, just when building target data lab environment
The parameter is set, that is, starts database before migrating and has set the parameter.If it is empty then not convert file title,
It can specify the title of partial document data transfer.Setting format is migrate_datafile_name_tranform='
Raw1', ' user01.dbf', ' raw2', ' user02.dbf', i.e., by the raw1 data file transition in the library of source at
User01.dbf, by the raw2 data file transition in the library of source at user02.dbf, specific transformation rule is exactly: n-th parameter
Value is title of the data file in the library of source, and the N+1 parameter value is data file corresponding title in object library, i.e. N
A parameter specified data filename can be converted by N+1 parameter name.
Parameter migrate_process_num: the parameter for the control of migrating processes quantity is the control of migrating processes quantity
Parameter processed, at source database end, it is data block transmission number of processes, and the ginseng is just set when building target data lab environment
Number starts database before migrating and has set the parameter.In target side, it is data block reception number of processes, default value
Be 1, maximum can value be 10.Suitably increasing the number of processes can be improved data block transmission efficiency.
For specifying the parameter migrate_datafile_ of the catalogue of target database migration generation data file
Create_directory: the catalogue that the parameter is used to that target database migration to be specified to generate data file, the data received
Block is written in the data file under the catalogue, and setting format is migrate_datafile_create_directory
='/datafiles' ,/datafiles is pathname, and migration requires to must be provided with the parameter before starting.
For specifying the parameter migrate_target: the parameter of target database information for specifying target database to believe
Breath, is connected to target database by the parameter source database, just sets this when building target data lab environment
Parameter starts database before migrating and has set the parameter.Setting format is migrate_target='
10.10.10.12:9530/dbtarget' 10.10.10.12:9530 be target database IP and respective end slogan,
Dbtarget is database-name.
In step sl, the process of the target database of configuration includes writing data file process, reading data file process, inspection
Process, log process are made an inventory of, the storage allocation of the target database of configuration includes data-block cache area, data dictionary buffer area
It needs target database that can start associated process and distribution correspondence memory, as long as database starts, has these processes fortune
It goes and distributes these region of memory (not needing to load and open data file), be connected to target side number convenient for source database
According to library.
In step s 2, the data block of source database is synchronized to target client database is specifically: opening on source database backstage
Dynamic data block sends process (title such as send01, send02), and number of processes is by the parameter that controls for migrating processes quantity
Migrate_process_num control, the data block that source database is read send process by data block and are sent to target database,
Target database has respective data blocks receiving process (title such as rec01, rec02), and number of processes is by being used for migrating processes quantity
The parameter migrate_process_num of control is controlled, and data block transmission number of processes is identical with data block receiving process quantity,
Data block sends the data block reception process that process goes matching target client database.
Data block send process go matching target client database data block reception process be specifically: source block send into
Journey uses the side of TCP three-way handshake according to the data block reception process of target database address, port information and target database
Formula connection, after three-way handshake success, data block sends process and data block reception process formally establishes connection.
In step s 2, the data block of source database includes full dose data block, incremental data block, the incremental number of source database
It is the data block changed after full dose data synchronize fastly according to block, specifically includes newly-increased data block, by modification data block, deleted data
Block.The full dose data block of source database is synchronized to target database, and source database generates data block variation record file, by source number
Data block variation record file is recorded according to the incremental data block of block, and incremental data block in data block variation record file is same
Target database is walked, wherein the data block variation record file of source database is with sequence of event delta data block, tool
Body is:
Some data block of source database has occurred at least once that modification operation, the data block modified can be in different time
Time sequencing is recorded respectively in data block variation record file；
Newly-increased data block can be recorded directly to data block variation record file, if had occurred after the newly-increased data block
Change is changed in record file with sequence of event to data block；
Source database full dose data block synchronizes start after, data block variation record file comes into force and records delta data block,
Record information includes document number, data block where timestamp, data block position, data block hereof；
After source database full dose synchronously completes, executes source database incremental data block and synchronize, incremental data block synch command
Data block variation before initiating time point records the record in file, synchronizes, has synchronously completed to target database
Record can change in record file from data block to be deleted, and source database incremental data block synchronizing process executes at least once.
Design initiates the synchronous order of full dose and initiates the order of increment synchronization: alter systemstartwhole
Migrate is full dose synch command, and database starts to read source database full dose data block and is sent to mesh after which executes
Client database is marked, while generating data block variation record file；Alter system start increment migrate is
Increment synchronization order, the effect of the order are that referred database carries out increment synchronization, and data block is changed in record file and is being increased
Record before amount synch command initiates time point can all be synchronized to object library, and the record synchronously completed can become from data block
Change and is deleted in record file.Increment synchronization can execute at least once, and the effect for executing increment synchronization at least once can reduce
The problem of data block variation records the size of file, can also reduce single increment synchronization overlong time.
Data block variation record file is binary file, and each incremental data block synchronizes rear data block variation record file
Just will be deleted and wherein completed synchronous data block, thus two data blocks variation record file will not become very greatly.
The present invention only data block used in data file is synchronized, distributed but not used data block not by
It is synchronous.
In step s3, target database locally completes logarithm after the incremental data block of source database synchronously completes
It modifies change according to block.
Embodiment two
As shown in Fig. 2, in technical solution of the present invention in a kind of method that database migrates online target database by data
Block write-in data file is specifically:
In step s 201, target database receives data block；
In step S202, judge whether the operating system of source database and target data library operating systems are consistent, if
Judging result be it is yes, then follow the steps S203, if it is judged that be it is no, then follow the steps S204；
In step S203, targeted database data file directly is written into data block；
In step S204, size byte conversion, that is, converted magnitude byte storage tandem is carried out to data block, is turned
Targeted database data file is written into data block again after changing.
In step S201, S202, S203, S204, before data block synchronizes, data block sends process can be to target data
Library sends operating system platform information, and object library is according to the source database operating system platform information and target database received
Operating system platform information be compared, can be to the data block received according to target database platform if platform is different
It is converted, conversion here is mainly change data block byte tandem, and target data is written in the data block after conversion again
The data file in library.If platform is identical, the not byte order of change data block.
The operating systems such as LINUX, AIX, HP-UX, WINDOWS that server is often used they there are the differences on byte order
Not, for example AIX, HP-UX use big byte, and LINUX, WINDOWS use small byte.It is the smallest in a computer
Unit is a byte, and a byte can be understood as any one number between a 0-9 by we, therefore indicate one
It just needs four to indicate when thousands digit, gives a four figures 8765, this value will not become, but when recording this number
Can be write as 8765 also can recorde into 5678, only it is to be understood that being that how to store can.In the operating system of big byte
Kilobit is write on into front, a position is write on into front in the operating system of small byte, so big byte and small byte are in storage side
It is different in formula.If target client database is small byte, the source database data block received is big byte, target side
Database cannot directly the data block, need big byte data block being converted into small byte data block.Data block size word
Section transformation mechanism is exactly can be according to source database operating system platform and target database after target database receives data block
Operating system platform judges automatically whether carry out size byte conversion to data block, if necessary to convert, again by data after conversion
Data file is written in block.Different CPU has different byte sequence styles, these syllable sequences refer to that integer saves suitable in memory
Sequence.There are two types of most common: 1.Little-endian: low sequence byte being stored in initial address, 2.Big-endian: will be high
Sequence byte is stored in initial address.For example double byte 0x01020304 is stored into memory in order, the sequence of big byte is first deposited
A high position, then the sequence stored is 0x01,0x02,0x03,0x04, and the sequence of small byte is first to deposit low level, then storing
Sequence is exactly 0x04,0x03,0x02,0x01.So size Endianess is different, between two kinds of bytes, Data Migration is just
It is related to size byte conversion.Big byte is used by the CPU that AIX and HP operating system uses, LINUX operating system uses
CPU be small byte.This process can carry out size byte conversion with ORACLE RMAN tool when database migration, but unlimited
In ORACLE RMAN tool.
Embodiment three
As shown in figure 3, being matched in a kind of method that database migrates online according to target database in technical solution of the present invention
Data block write-in specified data file is specifically by the data file class set:
In step S211, target database receives data block；
In step S212, judge source database configuration file type and target database configuration file type whether
Unanimously, if it is judged that be it is yes, then follow the steps S213, if it is judged that be it is no, then follow the steps S214；
In step S213, directly by the data text under the specified file system directories of data block write-in target database
Part；
In step S214, completes to convert according to the parameter of target database configuration and file type and number of targets is written
Data file under the file system directories specified according to library.
In step S211, S212, S213, S214, in configuration target database for specifying target database migration life
At the catalogue of data file parameter migrate_datafile_create_directory when, need specified data file to exist
The file system directories that target database uses will be written after the data block that source database is read is received by object library database
Under the file system directories specified to target database, number of targets is converted by rule according to data file name in source database
In the data file converted according to the parameter migrate_datafile_name_tranform of the data file name in library, it is used for
Specified target database migration generate the parameter migrate_datafile_create_directory of the catalogue of data file with
Data file name is converted into the parameter migrate_ of the data file name in target database by rule in source database
Datafile_name_tranform is used cooperatively.
Database generally carrys out storing data file using file system, raw device, ASM etc., is stored using which kind of form
Data file is that determining as needed, different database may carry out storing data file using different forms, this is just needed
When migration between two kinds of databases, needing automatically being capable of conversion data file.For example, such as: source database makes
Raw device storing data file, raw device is located at/dev/raw catalogue under, target database uses file system
The data file of storage, in the parameter for the catalogue that configuration target database is used to that target database migration to be specified to generate data file
The file system for just needing specified data file to use when migrate_datafile_create_directory in target database
Catalogue of uniting (migrate_datafile_create_directory='/dev/raw', '/datafiles'), source database from
The data block read in raw device by object library database receive after, be written to/datafiles catalogue under according to source database
Middle data file name is converted into the parameter migrate_datafile_ of the data file name in target database by rule
In the data file of name_tranform conversion, the ginseng of the catalogue for being used to that target database migration to be specified to generate data file
Number migrate_datafile_create_directory is converted into number of targets by rule with data file name in source database
It is used cooperatively according to the parameter migrate_datafile_name_tranform of the data file name in library.If it is file system
System moves to raw device, it is necessary to which specified data file is migrate_ in the file system directories that target database uses
Datafile_create_directory='/datafiles', '/dev/raw'.File system is moved to if it is ASM, just
The file system directories for needing specified data file to use in target database are migrate_datafile_create_
Directory='+data/datafile', '/datafiles' ,+data is ASM disk group name, is moved to if it is ASM
Raw device, it is necessary to which specified data file is migrate_datafile_ in the file system directories that target database uses
Create_directory='+data/datafile', '/dev/raw'.
Example IV
As shown in figure 4, a kind of device that database migrates online, comprising:
Preparation module 101 is configured, configuration database parameter, simultaneously storage allocation makes starting critical processes for target database
With；
Synchronization module 102 is sent, source database sends data block to target database, for moving for spanning operation system platform
It moves, target database carries out size byte conversion and data file is written in data block, the data configured according to target database
Specified data file is written in data block by file type；
Modification change module 103, target database is after the data block of source database synchronously completes, in local to data block
It modifies change.
Above-mentioned, although the foregoing specific embodiments of the present invention is described with reference to the accompanying drawings, not protects model to the present invention
The limitation enclosed, those skilled in the art should understand that, based on the technical solutions of the present invention, those skilled in the art are not
Need to make the creative labor the various modifications or changes that can be made still within protection scope of the present invention.
Claims (8)
1. a kind of method that database migrates online, characterized in that include:
Configuration database parameter, starting critical processes and storage allocation are used for target database；
Source database sends data block to target database, and migration for spanning operation system platform, target database carries out greatly
Simultaneously data file is written in data block by small byte conversion, and data block is written according to the data file class that target database configures
Specified data file；
Target database modifies change to data block in local after the data block of source database synchronously completes.
2. the method that database according to claim 1 migrates online, characterized in that the configuration database parameter includes
The parameter of source database and target database is configured, specifically: for specifying the road of source database data block variation record file
The parameter migrate_block_change_trace of diameter and title, data file name is converted into mesh by rule in source database
The parameter migrate_datafile_name_tranform of the data file name in database is marked, migrating processes quantity is used for
The parameter migrate_process_num of control, the parameter of the catalogue for specifying target database migration generation data file
Migrate_datafile_create_directory, for specifying the parameter migrate_target of target database information.
3. the method that database according to claim 1 migrates online, characterized in that the starting critical processes include writing
Data file process reads data file process, checkpointing, log process, and the storage allocation is used for target database
Including data-block cache area, data dictionary buffer area.
4. the method that database according to claim 2 or 3 migrates online, characterized in that the source database sends number
Be specifically to target database according to block: source database backstage log-on data block sends process, and number of processes is by being used for migrating processes
The parameter migrate_process_num control of quantity control, the data block that source database is read send process hair by data block
It is sent to target database, target database has respective data blocks receiving process, and number of processes for migrating processes quantity by controlling
Parameter migrate_process_num control, data block send number of processes it is identical with data block receiving process quantity, data
Block sends the data block reception process that process goes matching target client database.
5. the method that database according to claim 4 migrates online, characterized in that the data block sends process and goes
Data block reception process with target client database is specifically: source block sends process according to target database address, port
The data block reception process of information and target database is connected using the mode of TCP three-way handshake, after three-way handshake success, data
Block sends process and data block reception process establishes connection.
6. the method that database according to claim 1 migrates online, characterized in that data block is written target database
Data file is specifically: after target database receives data block, judging that the operating system of source database and target database operate
Whether system is consistent, if unanimously, targeted database data file directly is written in data block, if it is inconsistent, logarithm
Size byte conversion, that is, converted magnitude byte storage tandem is carried out according to block, target data is written into data block again after conversion
Library data file.
7. the method that database according to claim 1 migrates online, characterized in that described to be configured according to target database
Data file class by data block write-in specified data file be specifically: after target database receives data block, judge source
Whether the file type of database configuration and the file type that target database configures are consistent, if unanimously, directly by data
The data file under the specified file system directories of target database is written in block, if it is inconsistent, being matched according to target database
The parameter and file type set are completed to convert and be written the data file under the specified file system directories of target database.
8. a kind of device that database migrates online, characterized in that include:
Preparation module, configuration database parameter, starting critical processes and storage allocation are configured for target database use；
Send synchronization module, source database sends data block to target database, migration for spanning operation system platform, target
Database carries out size byte conversion and data file is written in data block, the data file class configured according to target database
Specified data file is written into data block；
Modification change module, target database repair data block in local after the data block of source database synchronously completes
Change more.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811202820.3A CN109299072B (en) | 2018-10-16 | 2018-10-16 | Method and device for online migration of database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811202820.3A CN109299072B (en) | 2018-10-16 | 2018-10-16 | Method and device for online migration of database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109299072A true CN109299072A (en) | 2019-02-01 |
| CN109299072B CN109299072B (en) | 2022-06-10 |
Family
ID=65162797
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811202820.3A Active CN109299072B (en) | 2018-10-16 | 2018-10-16 | Method and device for online migration of database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109299072B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111064789A (en) * | 2019-12-18 | 2020-04-24 | 北京三快在线科技有限公司 | Data migration method and system |
| CN111125054A (en) * | 2019-11-21 | 2020-05-08 | 青岛聚好联科技有限公司 | Method and device for community data migration |
| CN112015816A (en) * | 2020-08-27 | 2020-12-01 | 北京字节跳动网络技术有限公司 | Data synchronization method, device, medium and electronic equipment |
| CN112035461A (en) * | 2020-06-17 | 2020-12-04 | 深圳市法本信息技术股份有限公司 | Migration method and system for table data file of database |
| CN112463764A (en) * | 2020-11-19 | 2021-03-09 | 苏州浪潮智能科技有限公司 | Method and system for online migration of database |
| CN113127259A (en) * | 2019-12-30 | 2021-07-16 | 北京懿医云科技有限公司 | Data deployment method, device, equipment and storage medium |
| CN113409015A (en) * | 2021-06-21 | 2021-09-17 | 浙江省能源集团有限公司 | ERP system and use method of ERP system in double-activity deployment of double data centers |
| CN113486010A (en) * | 2021-07-01 | 2021-10-08 | 远光软件股份有限公司 | Database synchronization method, device, server and storage medium |
| CN113868188A (en) * | 2021-08-25 | 2021-12-31 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for modifying storage position of database file |
| CN114443654A (en) * | 2022-01-14 | 2022-05-06 | 苏州浪潮智能科技有限公司 | Method and system for modifying length of spatial data block of database table on line |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104573056A (en) * | 2015-01-22 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Database large data volume online migration method based on oracle |
| CN104573122A (en) * | 2015-02-09 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Oracle database migration tool migrating from AIX platform to K-UX platform |
| CN105138603A (en) * | 2015-08-07 | 2015-12-09 | 浪潮电子信息产业股份有限公司 | Oracle database migration tool for carrying out migration from HP-UX platform to K-UX platform |
| CN106446166A (en) * | 2016-09-23 | 2017-02-22 | 郑州云海信息技术有限公司 | Method and device for migrating data from DB2 database to K-DB database |
| CN107193943A (en) * | 2017-05-19 | 2017-09-22 | 郑州云海信息技术有限公司 | A kind of method and apparatus of RDBMS online datas migration |
| CN107315763A (en) * | 2017-04-26 | 2017-11-03 | 杭州沃趣科技股份有限公司 | One kind is directed to oracle database Platform-cross Data Migration method |
| CN107423436A (en) * | 2017-08-04 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of method migrated for online data between distinct type data-base |
-
2018
- 2018-10-16 CN CN201811202820.3A patent/CN109299072B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104573056A (en) * | 2015-01-22 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Database large data volume online migration method based on oracle |
| CN104573122A (en) * | 2015-02-09 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Oracle database migration tool migrating from AIX platform to K-UX platform |
| CN105138603A (en) * | 2015-08-07 | 2015-12-09 | 浪潮电子信息产业股份有限公司 | Oracle database migration tool for carrying out migration from HP-UX platform to K-UX platform |
| CN106446166A (en) * | 2016-09-23 | 2017-02-22 | 郑州云海信息技术有限公司 | Method and device for migrating data from DB2 database to K-DB database |
| CN107315763A (en) * | 2017-04-26 | 2017-11-03 | 杭州沃趣科技股份有限公司 | One kind is directed to oracle database Platform-cross Data Migration method |
| CN107193943A (en) * | 2017-05-19 | 2017-09-22 | 郑州云海信息技术有限公司 | A kind of method and apparatus of RDBMS online datas migration |
| CN107423436A (en) * | 2017-08-04 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of method migrated for online data between distinct type data-base |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111125054A (en) * | 2019-11-21 | 2020-05-08 | 青岛聚好联科技有限公司 | Method and device for community data migration |
| CN111064789A (en) * | 2019-12-18 | 2020-04-24 | 北京三快在线科技有限公司 | Data migration method and system |
| CN113127259A (en) * | 2019-12-30 | 2021-07-16 | 北京懿医云科技有限公司 | Data deployment method, device, equipment and storage medium |
| CN113127259B (en) * | 2019-12-30 | 2024-03-12 | 北京懿医云科技有限公司 | Data deployment method, device, equipment and storage medium |
| CN112035461A (en) * | 2020-06-17 | 2020-12-04 | 深圳市法本信息技术股份有限公司 | Migration method and system for table data file of database |
| CN112015816A (en) * | 2020-08-27 | 2020-12-01 | 北京字节跳动网络技术有限公司 | Data synchronization method, device, medium and electronic equipment |
| CN112463764B (en) * | 2020-11-19 | 2023-01-06 | 苏州浪潮智能科技有限公司 | Method and system for online migration of database |
| CN112463764A (en) * | 2020-11-19 | 2021-03-09 | 苏州浪潮智能科技有限公司 | Method and system for online migration of database |
| CN113409015A (en) * | 2021-06-21 | 2021-09-17 | 浙江省能源集团有限公司 | ERP system and use method of ERP system in double-activity deployment of double data centers |
| CN113486010A (en) * | 2021-07-01 | 2021-10-08 | 远光软件股份有限公司 | Database synchronization method, device, server and storage medium |
| CN113868188A (en) * | 2021-08-25 | 2021-12-31 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for modifying storage position of database file |
| CN114443654A (en) * | 2022-01-14 | 2022-05-06 | 苏州浪潮智能科技有限公司 | Method and system for modifying length of spatial data block of database table on line |
| CN114443654B (en) * | 2022-01-14 | 2024-01-26 | 苏州浪潮智能科技有限公司 | Method and system for on-line modifying length of database table space data block |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109299072B (en) | 2022-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109299072A (en) | A kind of method and device that database migrates online | |
| US10778751B2 (en) | Method of micro-service transformation for power trading functions | |
| WO2019154394A1 (en) | Distributed database cluster system, data synchronization method and storage medium | |
| US9348830B2 (en) | Back up using locally distributed change detection | |
| US7406487B1 (en) | Method and system for performing periodic replication using a log | |
| US9152642B2 (en) | Systems and methods for on-demand data storage | |
| US9448893B1 (en) | Asynchronous replication correctness validation | |
| US9785523B2 (en) | Managing replicated virtual storage at recovery sites | |
| US7484051B2 (en) | Apparatus, system and method for reliably updating a data group in a read-before-write data replication environment using a comparison file | |
| CN108628874B (en) | Method and device for migrating data, electronic equipment and readable storage medium | |
| US7610314B2 (en) | Online tablespace recovery for export | |
| CN110119377A (en) | Online migratory system towards Docker container is realized and optimization method | |
| US10216589B2 (en) | Smart data replication recoverer | |
| US20140181016A1 (en) | Asynchronous replication correctness validation | |
| US20070083570A1 (en) | File system versioning using a log | |
| US20090144344A1 (en) | Apparatus, system, and method for replication of data management information | |
| WO2007053314A2 (en) | Apparatus and method for creating a real time database replica | |
| CN107667351A (en) | The system and method for the full data backup and resume for being automatically based upon cloud on mobile device | |
| CN106844102B (en) | Data recovery method and device | |
| CN103780638A (en) | Data synchronization method and system | |
| CN105260376A (en) | Method, equipment and system used for cluster node contraction and expansion | |
| WO2023103190A1 (en) | Multi-level linkage transparent sample model sharing apparatus for artificial intelligence platform | |
| US7580959B2 (en) | Apparatus, system, and method for providing efficient disaster recovery storage of data using differencing | |
| CN114048370A (en) | Python-based archive file processing, storage and one-stop management platform | |
| US10915513B2 (en) | Archival of data in a relational database management system using block level copy |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |