Using XML for flexible replication of complex types

• US 7,801,856 B2
• Filed: 08/09/2006
• Issued: 09/21/2010
• Est. Priority Date: 08/09/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Warner, James W., Arora, Nimar, Murthy, Ravi, Krishnaprasad, Muralidhar, Liu, Zhen Hua, Lu, Edwina, Arora, Geeta, Abraham, Sundeep
• Primary Examiner(s): Morrison; Jay A
• Application Number:
  US11/502,247
• Publication Number:
  US 20080040369A1
• Time in Patent Office: 1,504 Days
• Field of Search: None
• US Class Current: 707/626
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

Instances of complex types are logically replicated. In general, the logical replication of complex types involves converting a complex type instance from its storage format into a logical representation written in a markup language, like XML. The logical representation is then propagated to a destination (or destinations), which converts the logical representation to a storage format used at the destination for that complex type.

Claims

1. A method of replicating objects at multiple sites, the method comprising the steps of:

converting an instance of a complex type from (a) a first storage format within a first database used at a source site to store the instance of the complex type to (b) a logical representation tat conforms to a markup language and is recognized among the multiple sites;

propagating said logical representation to at least one destination site; and

at a destination site, converting said logical representation to a second storage format used to store instances of the complex type within a second database at the destination site, said second storage format different from said first storage format;

wherein the instance of die complex type in the first storage format within the first database at the source site includes an object identifier that identifies at least part of the instance of the complex type at the source site, wherein the object identifier is tied to the source site and is not used to identify the at least part of the instance of the complex type in the second storage format within the second database at the destination site, and wherein the logical representation includes a globally unique identifier that is recognized among the multiple sites as representing the at least part of the instance of the complex type;

wherein the steps of converting the instance, propagating the logical representation, and converting said logical representation are performed by one or more computing devices.

2. The method of claim 1, wherein the step of converting the instance includes incorporating within said logical representation information that identifies the type of the complex type.

3. The method of claim 1, wherein the steps further include determining that there is a subtype defined for said complex type;

and

in response to determining that there is a subtype defined for said complex type, incorporating within said logical representation information that identifies the subtype.

4. The method of claim 1, wherein

the step of converting the instance includes:

generating a logical representation for said object identifier that is recognized among the multiple sites, and

incorporating said logical representation of said object identifier within said logical representation of said complex type.

5. The method of claim 1, wherein:

said object identifier comprises a table identifier, said table identifier identifying a table at said source site, and wherein said table identifier is not used to identify the table at the destination site;

generating said globally unique identifier of said table identifier that is recognized among the multiple sites as said table; and

incorporating said globally unique identifier within said logical representation of said complex type.

6. The method of claim 5, wherein said logical representation includes a table name of said table.

7. The method of claim 5, wherein:

said table is an object table of an object type;

wherein one or more columns of said object table are primary keys for instances of said object type stored in said object table; and

wherein said logical representation includes a representation of a value for each of said one or more columns.

8. The method of claim 1, wherein said complex type is an opaque type.

9. The method of claim 8, wherein:

converting said instance of said complex type includes invoking a user registered function registered to convert instances of said complex type to logical representations of said instances; and

converting said logical representation to said second storage format includes invoking a user registered function registered to convert logical representations of instances of said complex type to said second storage format.

10. The method of claim 1, wherein:

said source site defines a first version of said complex type;

said destination site defines a second version of said complex type; and

further comprising;

converting said logical representation to a second storage format used to store instances of the complex type within the second database includes transforming said logical representation to represent said second version of said complex type.

11. The method of claim 10, wherein transforming includes changing the order of attributes within said logical representation.

12. The method of claim 10, wherein transforming includes adding or removing attributes not defined by said second version.

13. The method of claim 10, wherein execution of instructions that conform to one or more XML languages causes said transforming said logical representation.

14. The method of claim 13, wherein said one or more XML languages include at least one language from a set languages that include XSLT and XQuery.

15. The method of claim 1, wherein said markup language is either XML or SGML.

16. A non-transitory volatile or non-volatile machine-readable 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 an instance of a complex type from (a) a first storage format within a first database used at a source site to store the instance of the complex type to (b) a logical representation that conforms to a markup language and is recognized among multiple sites;

propagating said logical representation to at least one destination site; and

at a destination site, converting said logical representation to a second storage format used to store instances of the complex type within a second database at the destination site, said second storage format different from said first storage format;

wherein the instance of the complex type in the first storage format within the first database at the source site includes an object identifier that identifies at least part of the instance of the complex type at the source site, wherein the object identifier is tied to the source site and is not used to identify the at least part of the instance of the complex type in the second storage format within the second database at the destination site, and wherein the logical representation includes a globally unique identifier that is recognized among the multiple sites as representing the at least part of the instance of the complex type.

17. The volatile or non-volatile machine-readable storage medium of claim 16, wherein one or more sequences of instructions causes the one or more processors to perform converting the instance by incorporating within said logical representation information that identifies the type of the complex type.

18. The volatile or non-volatile machine-readable storage medium of claim 16, wherein the one or more sequences of instructions further causes the one or more processors to perform:

determining that there is a subtype defined for said complex type; and

in response to determining that there is a subtype defined for said complex type, incorporating within said logical representation information that identifies the subtype.

19. The volatile or non-volatile machine-readable storage medium of claim 16, wherein the one or more sequences of instructions causes the one or more processors to perform converting the instance by:

generating a logical representation for said object identifier that is recognized among the multiple sites, and

incorporating said logical representation of said object identifier within said logical representation of said complex type.

20. The volatile or non-volatile machine-readable storage medium of claim 16, wherein said object identifier comprises a table identifier, said table identifier identifying a table at said source site, and wherein said table identifier is not used to identify the table at the destination site;

and wherein the one or more sequences of instructions further causes the one or more processors to perform;

generating said globally unique identifier of said table identifier that is recognized among the multiple sites as said table; and

incorporating said globally unique identifier within said logical representation of said complex type.

21. The volatile or non-volatile machine-readable storage medium or claim 20, wherein said logical representation includes a table name of said table.

22. The volatile or non-volatile machine-readable storage medium of claim 20, wherein said table is an object table of an object type;

wherein one or more columns of said object table are primary keys for instances of said object type stored in said object table; and

wherein said logical representation includes a representation of a value for each of said one or more columns.

23. The volatile or non-volatile machine-readable storage medium of claim 16, wherein said complex type is an opaque type.

24. The volatile or non-volatile machine-readable storage medium of claim 23,

wherein the one or more sequences of instructions causes the one or more processors to perform converting said instance of said complex type by invoking a user registered function registered to convert instances or said complex type to logical representations of said instances;

and

wherein the one or more sequences of instructions causes die one or more processors to perform converting said logical representation to said second storage format by invoking a user registered function registered to convert logical representations of instances of said complex type to said second storage format.

25. The volatile or non-volatile machine-readable storage medium of claim 16, wherein said source site defines a first version of said complex type;

wherein said destination site defines a second version of said complex type; and

wherein the one or more sequences of instructions causes the one or more processors to perform converting said logical representation to the second storage format by transforming said logical representation to represent said second version of said complex type.

26. The volatile or non-volatile machine-readable storage medium of claim 25, wherein the one or more sequences of instructions causes the one or more processors to perform transforming by changing an order of attributes within said logical representation.

27. The volatile or non-volatile machine-readable storage medium of claim 25, wherein the one or more sequences of instructions causes the one or more processors to perform transforming by adding or removing attributes not defined by said second version.

28. The volatile or non-volatile machine-readable storage medium of claim 25, wherein execution of instructions that conform to one or more XML languages causes said transforming said logical representation.

29. The volatile or non-volatile machine-readable storage medium of claim 28, wherein said one or more XML languages include at least one language from a set languages that include XSLT and XQuery.

30. The volatile or non-volatile machine-readable storage medium of claim 16, wherein said markup language is either XML or SGML.