Cross platform transportable tablespaces

• US 8,554,806 B2
• Filed: 10/14/2004
• Issued: 10/08/2013
• Est. Priority Date: 05/14/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Hu, Wei, Hwang, Alexander, Meng, Shen-Ban, Pareek, Alok, Potapov, Dmitry, Sanchez, Francisco
• Primary Examiner(s): MENG, JAU SHYA
• Application Number:
  US10/966,679
• Publication Number:
  US 20050253739A1
• Time in Patent Office: 3,281 Days
• Field of Search: 707/3, 707/10, 707/100, 707/204
• US Class Current: 707/809
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

Stored data are transported between different systems having different platforms by converting the format of the stored data into a common format either before or after transmitting the stored data from the source database system to the target database system. The common format may be a format that is universal in that the common format is not machine dependent. The stored data may be kept in the common format at the target database system and never converted to another format. Optionally, the stored data may be converted from the common format to a format associated with the target database system, thereby facilitating backward compatibility. A tool may be provided for performing the conversion.

Claims

1. A method comprising the steps of:

converting, within a first collection of physical files, metadata contained in a plurality of database data blocks in the first collection of files from a first format to a second format;

wherein the first collection of files includes one or more tablespaces;

wherein converting includes, for each database data block of the plurality of database data blocks;

reading the each database data block from a corresponding file of the first collection of files into a computer memory, the each database data block read into the computer memory having metadata in the first format,

converting, in the computer memory, metadata of the each database data block, from the first format to the second format, and

storing the converted each database data block in the corresponding file of the first collection of files, wherein metadata of the converted each database data block stored in the corresponding file of the first collection of files is in the second format;

wherein, prior to the converting, the first collection of files is attached to the first database system;

after said converting, attaching the first collection of files to a second database system;

the second database system using the attached first collection of files to store database data;

wherein the first format is compatible with the first database system;

wherein the first format is incompatible with the second database system;

wherein the second format is incompatible with the first database system;

wherein the second format is compatible with the second database system;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, wherein the converting further comprises:

declaring all convertible on-disk data structures;

automatically deriving conversion functions from the declaring of the convertible on-disk data structures; and

calling the conversion functions based on the convertible on-disk data structures declared.

3. The method of claim 1, wherein the converting further comprises:

adding a header associated with the second format to a file associated with the first collection of files, if the header is not already present.

4. The method of claim 3, wherein the header includes at least a platform identification that identifies a platform associated with the first system.

5. The method of claim 1, further comprising:

after the converting, copying or moving the first collection of physical files from the first database system to the second database system; and

wherein the converting is performed at the first database system.

6. The method of claim 1, further comprising:

prior to the converting, copying or moving the first collection of physical files from the first database system to the second database system; and

wherein the converting is performed at the second database system.

7. The method of claim 1, wherein the first format is one of big-endian byte ordering or little-endian byte ordering and the second format is the other of big-endian byte ordering or little-endian byte ordering.

8. A computer-readable non-transitory storage medium storing one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform:

converting, within a first collection of physical files, metadata contained in a plurality of database data blocks in the first collection of files from a first format to a second format;

wherein the first collection of files includes one or more tablespaces;

wherein converting includes, for each database data block of the plurality of database data blocks;

reading the each database data block from a corresponding file of the first collection of files into a computer memory, the each database data block read into the computer memory having metadata in the first format,

converting, in the computer memory, metadata of the each database data block, from the first format to the second format, and

storing the converted each database data block in the corresponding file of the first collection of files, wherein metadata of the converted each database data block stored in the corresponding file of the first collection of files is in the second format;

wherein, prior to the converting, the first collection of files is attached to the first database system;

after said converting, attaching the first collection of files to a second database system;

the second database system using the attached first collection of files to store database data;

wherein the first format is compatible with the first database system;

wherein the first format is incompatible with the second database system;

wherein the second format is compatible with the second database system;

wherein the second format is incompatible with the first database system.

9. The medium of claim 8, wherein the converting further comprises:

declaring all convertible on-disk data structures;

automatically deriving conversion functions from the declaring of the convertible on-disk data structures; and

calling the conversion functions based on the convertible on-disk data structures declared.

10. The medium of claim 8, wherein the converting further comprises:

adding a header associated with the second format to a file associated with the first collection of files, if the header is not already present.

11. The medium of claim 10, wherein the header includes at least a platform identification that identifies a platform associated with the first system.

12. The medium of claim 8, further storing one or more sequences of instructions which, when executed by the one or more processors, causes the one or more processors to perform:

after the converting, copying or moving the first collection of physical files from the first database system to the second database system; and

wherein the converting is performed at the first database system.

13. The medium of claim 8, further storing one or more sequences of instructions which, when executed by the one or more processors, causes the one or more processors to perform:

prior to the converting, copying or moving the first collection of physical files from the first database system to the second database system; and

wherein the converting is performed at the second database system.

14. The medium of claim 8, wherein the first format is one of big-endian byte ordering or little-endian byte ordering and the second format is the other of big-endian byte ordering or little-endian byte ordering.