Pluggable tablespaces for database systems

• US 5,890,167 A
• Filed: 05/08/1997
• Issued: 03/30/1999
• Est. Priority Date: 05/08/1997
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle Corporation
• Inventors: Loaiza, Juan R., Tsukerman, Alex, Lee, J. William, Bridge, William H. Jr., Klein, Jonathan D., Putzolu, GianFranco
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Alam, Hosain T.
• Application Number:
  US08/852,968
• Time in Patent Office: 691 Days
• Field of Search: 707/204, 707/1-4, 707/100, 707/101, 707/202, 707/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A pluggable tablespace is enabled by logically partitioning a database into a set of tablespaces and storing all of the tablespaces disk pointers in tablespace-relative format. A pluggable set of tablespaces is unplugged by exporting the associated metadata, and making a binary copy of the tablespaces. The pluggable set of tablespaces is plugged into a target database by making the pluggable set accessible to the target database and importing the associated metadata, without patching any of the disk pointers.

Claims

1. A method for unplugging a set of tablespaces, associated with metadata and having a plurality of disk pointers, from a source database to a memory, comprising the computer-implemented steps of:

storing said plurality of disk pointers in tablespace-relative format;

saving said metadata into a metadata file; and

making a binary copy of said set of tablespaces and said metadata file to said memory wherein said plurality of disk pointers with said binary copy, when plugged into a target database, is capable of being used for locating associated data items without patching said plurality of disk pointers.

2. The method of claim 1, wherein the step of saving said metadata into a metadata file includes the step of exporting said metadata into the metadata file.

3. The method of claim 2, wherein the step of exporting said metadata into the metadata file includes the steps of:

determining whether said set of tablespaces is self-contained;

if said set of tablespaces is not self-contained, then dropping objects in said set of tablespace that refer to objects not present in said set of tablespaces.

4. The method of claim 2, wherein the step of exporting said metadata into the metadata file includes the steps of:

determining whether said set of tablespaces is self-contained;

if said set of tablespaces is not self-contained, then outputting a message to a user that said set of tablespaces is not self-contained.

5. The method of claim 4, further comprising the step of outputting a second message identifying which tablespaces of said set of tablespace causes said set of tablespaces to be not self-contained.

6. The method of claim 1, further comprising the step of locating a data item within a datafile contained in said tablespace by performing the steps of:

reading a tablespace-relative disk pointer associated with said data item;

determining an identity of said tablespace; and

locating said data item based on said tablespace-relative disk pointer and said identity of said tablespace.

7. A method of plugging in a pluggable set of tablespaces having a plurality of disk pointers and saved metadata, into a target database, comprising the computer-implemented steps of:

incorporating said saved metadata into said target database;

copying each tablespace of said pluggable set of tablespaces into said target database; and

locating a data item associated with any one of said plurality of disk pointers without patching any disk pointer of said plurality of disk pointers.

8. The method of claim 7, wherein the step of incorporating said saved metadata into said target database, includes the step of importing said saved metadata into said target database.

9. The method of claim 7, further comprising the step of assigning a new tablespace number to each tablespace in said pluggable set of tablespaces, wherein each new tablespace number is unique within said target database and said pluggable set of tablespaces.

10. The method of claim 7, further comprising the steps of:

determining whether an external name of an object contained in said pluggable set of tablespaces exists in said target database;

if said external name of said object contained in said pluggable set of tablespaces exists in said target database, then prompting the user to rename an object within said target database having said external name.

11. The method of claim 7, further comprising the step of automatically assigning a new internal name to an object within said pluggable set of tablespaces, wherein said internal name is unique within said target database and said pluggable set of tablespaces.

12. A method of transferring a tablespace, associated with metadata and having a plurality of disk pointers, from a first database to a second database, comprising the steps of:

storing said plurality of disk pointers in tablespace-relative format at first database;

saving said metadata into a metadata file;

making a binary copy of said tablespace and said metadata file;

causing said binary copy to be available to said second database;

incorporating said metadata from said binary copy into said second database; and

locating a data item associated with any one of said plurality of disk pointers without patching said plurality of disk pointers.

13. The method of claim 12, wherein the step of saving said metadata into a metadata file includes the step of exporting said metadata into the metadata file.

14. The method of claim 13, wherein the step of exporting said metadata into the metadata file includes the steps of:

determining whether said set of tablespaces is self-contained;

if said set of tablespaces is not self-contained, then dropping objects in said set of tablespace that refer to objects not present in said set of tablespaces.

15. The method of claim 13, wherein the step of exporting said metadata into the metadata file includes the steps of:

determining whether said set of tablespaces is self-contained;

if said set of tablespaces is not self-contained, then outputting a message to a user that said set of tablespaces is not self-contained.

16. The method of claim 15, further comprising the step of outputting a second message identifying which tablespaces of said set of tablespace causes said set of tablespaces to be not self-contained.

17. The method of claim 12, wherein the step of incorporating said saved metadata into said second database, includes the step of importing said saved metadata into said second database.

18. The method of claim 12, further comprising the step of assigning a new tablespace number to each tablespace in said pluggable set of tablespaces, wherein each new tablespace number is unique within said second database and said pluggable set of tablespaces.

19. The method of claim 12, further comprising the steps of:

determining whether an external name of an object contained in said pluggable set of tablespaces exists in said second database;

if said external name of said object contained in said pluggable set of tablespaces exists in said second database, then prompting the user to rename an object within said second database having said external name.

20. The method of claim 12, further comprising the step of automatically assigning a new internal name to an object within said pluggable set of tablespaces, wherein said internal name is unique within said target database and said pluggable set of tablespaces.

21. A computer readable medium, having stored thereon sequences of instructions for unplugging a tablespace, associated with metadata and having a plurality of disk pointers, from a source database to a memory, said sequence of instructions including instructions for performing the steps of:

storing said plurality of disk pointers in tablespace-relative format;

saving said metadata into a metadata file; and

making a binary copy of said tablespace and said metadata file to said memory wherein said plurality of disk pointers with said binary copy, when plugged into a target database, is capable of being used for locating associated data items without patching said plurality of disk pointers.

22. The computer readable medium of claim 21, further including instructions for performing the step of exporting said metadata into a metadata datafile contained in said tablespace.

23. A computer readable medium, having stored thereon sequences of instructions for plugging in a tablespace, containing saved metadata and a plurality of disk pointers, into a target database, said sequence of instructions including instructions for performing the steps of:

making said unplugged tablespace stored in said memory available to said target database;

incorporating said saved metadata into said target database; and

locating a data item associated with any one of said plurality of disk pointers without patching said plurality of disk pointers.

24. The computer readable medium of claim 23, further including instructions for performing the step of importing said metadata from a metadata datafile contained in said tablespace.