JP2002366400A - Data transfer method, program, and storage medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data transfer method which reduces the burden on operator's operation and shortens the transfer time at the time of transferring a file in a database. SOLUTION: The data transfer method includes a plurality of transfer source servers 2 to 7 in which files of the database are stored and a device 1 as the data transfer destination which acquires files of the database which are stored in transfer source servers 2 to 7. A stop instruction is sent from transfer source servers 2 to 7 to a control part 11 in the device 1 as the data transfer destination. The control part 11 receives the stop instruction to start a data acquisition part 12 and acquires files stored in respective servers. Acquired files are stored in storage parts 16a to 16f, and control files generated by a control file generation part 13 are added, and environmental variables are set again by an environmental variable resetting part 14. Thereby, the database can be started even in the transfer destination.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data migration method, a program, and a storage medium for migrating database files stored in a plurality of migration source servers to a migration destination storage device.

[0002]

2. Description of the Related Art Conventionally, to migrate a database,
There are methods such as creating an intermediate file and migrating the database, and using a database link. The following is a brief description with reference to the drawings.

FIG. 5 is a block diagram showing the transfer of a database stored in a server to a data transfer destination device using an intermediate file.

[0004] A data transfer destination apparatus 10 shown in FIG. 1 is a data transfer destination server 2 which stores database files.
7, intermediate files 20 to 70 for temporarily storing files sent from the source servers 2 to 7, and a data transfer destination device 10 for collecting and storing files stored in the intermediate files 20 to 70. It is a configuration that includes.

[0005] First, the operation of Oracle of the migration source servers 2 to 7 is stopped. Then select the files needed to use the database that will be sent to the destination. Next, a file to be temporarily transmitted is stored in the intermediate files 20 to 70. Then, the data transfer destination device 10 is started up, and a transfer destination area is secured so that files temporarily stored in the intermediate files 20 to 70 can be inserted into the transfer destination. When the area is secured, the intermediate files 20 to 7
The file is migrated from 0 to the data migration destination device 10.

[0006] The intermediate files 20 from the source servers 2 to 7
A file required to use the source Oracle is read at one time at ~ 70. Then, all tables at the migration source are deleted. Then, the files stored in the intermediate files 20 to 70 are read into the data transfer destination device 10 at one time.

[0007] It takes about one day to read and write using the intermediate file and migrate the source table.

FIG. 6 is a configuration diagram showing the transfer of the database stored in the server to the data transfer destination device by using the database link.

The source servers 2 to 7 store database files used in the operations of each server. The data transfer destination device 10 includes transfer source servers 2 to 7
Is a data transfer destination device in which a database file sent from the server is stored.

The database link means the source server 2
7 to send a file to the data transfer destination apparatus 10, an area necessary for acquisition is secured in advance so that a file to be sent to the data transfer destination apparatus 10 can be acquired, and the file is stored in the secured area. This is the method of shifting. Set an instance to use Oracle in the reserved area. Then, the data is inserted into the set instance. When the insert operation is completed, the database files stored in the source servers 2 to 7 are deleted.

[0011]

However, in the above-described method of migrating a database, the method of migrating a database file stored in each server to a storage device of a migration destination requires a medium when migrating a database. Since the files of the database were migrated due to the files and the database link, there was a problem that it took time to migrate the files. Further, in the method requiring an intermediate file, a large amount of work area is required, so that the operation load of the operator is also caused in setting for securing the work area.

In the present invention, in view of the above-mentioned problems, an operation performed by an operator by acquiring a database file sent from each server, storing the file in one storage location, generating a new file, and constructing the database. It is an object of the present invention to provide a data migration method that reduces the load on the database and shortens the migration time when migrating database files.

[0013]

In order to solve the above-mentioned conventional problems, a data migration method according to a first aspect of the present invention provides a data migration method for acquiring a database distributed and arranged on a plurality of servers. A data migration method, wherein an acquisition step of sequentially acquiring files to be migrated stored in the databases of the plurality of servers according to a preset acquisition procedure, and storing the acquired plurality of files in one storage location Generating a new file by storing the file.

According to the first aspect of the present invention, files to be migrated stored in databases of a plurality of servers are sequentially acquired according to an acquisition procedure set in advance by an acquiring step, and the acquired plurality of files are acquired. Since the file is stored in one storage location and a new file is generated by the generation step, it is possible to save time and effort in the operation of setting the area required for migrating the database. As a result, it is possible to reduce the burden of the operation performed by the operator and to shorten the migration time when migrating the database.

[0015] A data migration program according to a second aspect of the present invention is a data migration program for acquiring a database distributed to a plurality of servers and stored in the databases of the plurality of servers. An acquisition step of sequentially acquiring the files to be migrated according to a preset acquisition procedure, and a generation step of storing the acquired plurality of files in one storage location and generating a new file. It is characterized by.

According to a third aspect of the present invention, a computer-readable storage medium storing a data migration program stores a data migration program for acquiring a database distributed and arranged in a plurality of servers. An acquisition step of sequentially acquiring files to be migrated stored in the databases of the plurality of servers in accordance with a preset acquisition procedure; and Generating a new file by storing the new file in one storage location.

[0017]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a configuration diagram showing a configuration of a data transfer destination apparatus according to an embodiment of the present invention.

Files required when using a database are transferred from a plurality of transfer source servers to a large-capacity storage device holding one high-speed large-capacity storage area.

The large-capacity storage device is a device to which data is migrated, and here is the device 1 to which data is migrated.
The plurality of servers as transfer sources are the input server 2, the cost calculation server 3, the information utilization server 4, the purchase server 5, the management accounting server 6, and the fund management server 7.

Each of the migration source servers 2 to 7 is connected to the data migration destination device 1 via a network.

The data transfer destination device 1 includes a control unit 11
Data acquisition unit 12, control file generation unit 13, environment setting unit 14, address book 15, storage units 16a to 16
f.

The control unit 11 detects a business stop request sent from each of the source servers 2 to 7. In addition, it controls the operation of each processing unit such as the data acquisition unit 12 and the control file generation unit 13.

The data acquisition unit 12 is connected to each of the source servers 2 to
7. Obtain the files needed to use the database stored in 7.

When the data acquisition unit 12 acquires a file necessary for using a database stored for each server, it does not acquire a control file in the database file.

The control file generation unit 13 collects database files acquired from the respective servers, and generates a control file that can use the collected database files with database software such as Oracle.

The environment setting unit 14 sets an environment for handling the acquired database file, and sets an address book 15
Stores addresses corresponding to the source servers 2 to 7, respectively. The storage units 16a to 16f store database files acquired from the respective servers.

The input server 2 includes an address 21 and a storage unit 22. The address 21 indicates a storage location of a database file stored in the input server 2.
In addition, the storage unit 22 stores input data such as sales management such as contract management, billing management, and order management, and communication charge management and expenses.

The cost calculation server 3 includes an address 31 and a storage unit 32. The address 31 is used when acquiring a file of a database stored in the cost calculation server 3. This makes it possible to transfer the database file stored in the cost calculation server 3. The storage unit 32 stores data on which the cost has been calculated.

The information utilization server 4 includes an address 41 and a storage unit 42. The address 41 is used when acquiring a database file stored in the information utilization server 4. This makes it possible to transfer the database file stored in the information utilization server 4. The storage unit 42 stores purchase, contract, billing data, and the like as secondary data processed so as to be easily referred to by customers.

The purchase server 5 includes an address 51 and a storage unit 52. The address 51 is used when acquiring a database file stored in the purchase server 5. This makes it possible to transfer the database file stored in the purchase server 5. Further, the storage unit 52 stores data relating to purchase such as purchase requests and approval.

The management accounting server 6 has an address 61 and a storage unit 62. The address 61 is used when acquiring a database file stored in the management accounting server 6. This makes it possible to transfer the database file stored in the management accounting server 6. The storage unit 62 stores data relating to management accounting such as a business plan, an execution plan, and a monthly analysis.

The fund management server 7 has an address 71 and a storage unit 72. The address 71 is used when acquiring a database file stored in the fund management server 7. Thereby, it becomes possible to transfer the files of the database stored in the fund management server 7. Further, the storage unit 72 stores data relating to fund management obtained by processing data such as contracts and purchases.

FIG. 2 is a configuration diagram showing the configuration of a file stored in the server of the present invention.

The storage unit 22 stores files for constituting a database. Specifically, a configuration file 22a required to use the database, a data file 22b,
The configuration includes a DO log file 22c.

The configuration file 22a sets the path of the control file stored in the source server. The data file 22b manages data used as a database as a file.
Further, the REDO log file 22c is used when starting up the database.

The configuration file 22a, the data file 22b, and the REDO log file 22c are transmitted from the respective source servers to the data transfer destination apparatus 1 as the destination.

In this case, the configuration file 22
a, data file 22b, REDO log file 22
Although the three types of files c have been described, in addition to the above, all files used to configure the database are migrated to the data migration destination device 1 except for the control file. However, for archive files,
Only specify the file.

FIG. 3 is a flowchart showing the operation of the data transfer destination device.

In step S11, the source servers 2 to 7
Detects a business stop command sent from. Specifically, S
QL (Structured Query Langu)
The shell script of “age” is started, and the operations of the source servers 2 to 7 are stopped.

At this time, database information is output so that the state before the file transfer and the state after the file transfer can be compared.

The database information output here includes table information, snapshot information, index information, snapshot index information, view schema information, index column information, number of tables, number of snapshots, number of views, and table space. Information.

In step S12, the source servers 2 to 7
The operation of obtaining file data is performed in accordance with the business stop command sent from the server. Specifically, UNIX (registered trademark)
Is started and read by the data acquisition unit 12 to acquire the file data stored in the storage units of the source servers 2 to 7. As a result, the migration time when migrating the database file can be reduced.

In step S13, the data files stored in the specified storage units in the specified migration source servers 2 to 7 are acquired and stored in the storage units 16a to 16f. Specifically, the UNIX shell script in step S12 is read by the data acquisition unit 12, and when the input server 2 is specified, the storage unit 2 of the server is specified.
Get the file from 2. Similarly, when the cost calculation server 3 is specified, the file is acquired from the storage unit 32 of the server.

In step S14, a control file required to use the data files collected from each server is generated.

The control file referred to here is a file for managing a database.

In step S15, the environment variables are reset. Specifically, the UNIX shell script is read into the environment variable setting unit, and the environment variables are reset.

In step S16, the database is started after the file is obtained. Specifically, by reading the SQL shell script, the database can be activated even in the data migration device at the migration destination.

At this time, information used in the database is output. The information output is table information,
The information includes snapshot information, index information, snapshot index information, view schema information, index column information, the number of tables, the number of snapshots, the number of views, and table space information.

Here, the information output in the processing of step S11 before the transfer and the information output after the transfer are UNIX.
Are compared using the diff command. As a result of the comparison, if there is no particular difference, the migration of the file from the migration source server to the data migration destination device 1 ends.

FIG. 4 is a flowchart showing the operation of the migration source server.

In step S21, the business process of the server is stopped. Specifically, the SQL shell script of the data migration destination device 1 is read in response to a stop request from the migration source servers 2 to 7, and the operation shifts to an operation of transmitting a file to the data migration destination device 1.

In step S22, the setting of the environment variables of the used Oracle is released. Specifically, the UNIX shell script is read in response to the stop request in step S21, and the set environment variables are released.

In step S23, the configuration file 22a of the used Oracle is modified. This is because the modification of the configuration file 22a performed here is necessary to use the unmodified control file when the generation of the control file performed by the data migration destination device 1 as the migration destination fails. .

In step S24, the used data file 22b and redo log file 22c are copied. More specifically, since the purpose is to activate the database in the data transfer destination device 1 as the transfer destination, the configuration file 22a other than the data file 22b and the REDO log file 22c is also copied. In the case of an archive file, only the specification is changed so that the file can be called from the migration destination without being migrated.

The processing program for performing the above-described processing corresponds to the data migration program of the present invention, and is readable by a computer such as a semiconductor memory, a magnetic disk, an optical disk, a magneto-optical disk, and a magnetic tape. It can be distributed by storing it on a recording medium. In addition, it is possible to transmit via a communication network such as the Internet.

[0057]

As described above, according to the present invention,
Data files are sequentially acquired in accordance with a preset acquisition procedure, stored in one storage location, a new file is generated and a database is constructed, thereby reducing the burden of operations performed by the operator, and the database file is saved. It is possible to provide a data migration method that reduces the migration time when migrating.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing a configuration of a data migration destination device according to an embodiment of the present invention.

FIG. 2 is a configuration diagram showing a configuration of a file stored in a migration source server of the present invention.

FIG. 3 is a flowchart illustrating an operation of a data transfer destination device.

FIG. 4 is a flowchart illustrating an operation of a migration source server.

FIG. 5 is a configuration diagram showing migration of a database stored in a conventional server to a data migration destination device using an intermediate file.

FIG. 6 is a configuration diagram showing migration of a database stored in a conventional server to a data migration destination device by using a database link.

[Explanation of symbols]

 Reference Signs List 1 device to which data is transferred 11 control unit 12 data acquisition unit 13 control file 14 environment variable resetting unit 15 address book 16a to 16f storage unit 2 input server 21 address 22 storage unit 3 cost calculation server 31 address 32 storage unit 4 information utilization Server 41 address 42 storage unit 5 purchasing server 51 address 52 storage unit 6 management accounting server 61 address 62 storage unit 7 fund management server 71 address 72 storage unit

Claims (3)

[Claims] 1. A data migration method for acquiring a database distributed and arranged on a plurality of servers, the method comprising: acquiring files to be migrated stored in the databases of the plurality of servers according to a preset acquisition procedure. A data migration method, comprising: an acquiring step of sequentially acquiring; and a generating step of storing the acquired plurality of files in one storage location and generating a new file. 2. A data migration program for acquiring a database distributed and arranged on a plurality of servers, wherein a migration target file stored in the databases of the plurality of servers is acquired according to a preset acquisition procedure. A data migration program, comprising: an acquisition step of sequentially acquiring a plurality of files; and a generation step of generating a new file by storing the acquired plurality of files in one storage location. 3. A computer-readable storage medium storing a data migration program for acquiring a database distributed and arranged on a plurality of servers, wherein a migration target stored in the databases of the plurality of servers is provided. And an acquisition step of sequentially acquiring the files according to a preset acquisition procedure, and a generation step of storing the acquired plurality of files in one storage location and generating a new file. Computer-readable storage medium storing a data migration program to be executed.