Oracle International Corporation

Promethium Limited

Ravikanth Kasamsetty

Srinath Krishnaswamy

Kaycee Kuan-Cheng Lai

Mohammad Shoaib Lari

Kalyanji Chintakayala

Subhranshu Banerjee

Krishna Mohan, Iv

Aleksey Vinokurov

Mohammed Shoaib Lari

Ravi Murthy

Sanjay Kaluskar

Mehul Dilip Bastawala

Rajendra Pingte

Chao Liang

Sundeep Abraham

Rajagopalan Govindarajan

Pranava Jayanthi Krishna

Ravi Koti

An analysis system connects to a set of data sources and perform natural language questions based on the data sources. The analysis system connects with the data sources and retrieves metadata describing data assets stored in each data source. The analysis system generates an execution plan for the natural language question. The analysis system finds data assets that match the received question based on the metadata. The analysis system ranks the data assets and presents the ranked data assets to users for allowing users to modify the execution plan. The analysis system may use execution plans of previously stored questions for executing new questions. The analysis system supports selective preprocessing of data to increase the data quality.

Chat-interface for natural language driven data management

Automated processing of a natural language question based on heterogenous data sources using a machine learning based language model

Querying heterogeneous data sources using machine learning based language model

An object type translator (OTT) determines one or more database object types. The one or more database object types are mapped to a first structural language type definition code. After being generated, the user may add user code to the first structural language type definition code. During regeneration of these files, the first structural language type definition code is then parsed to determine the user code that has been added, based on the start and end markers that the user code segments have been marked with. OTT maps these user-code segments to the corresponding database types and keeps track of the mapping and the user code. When the OTT starts generating the second structural language code, the OTT determines a position where the user code should be inserted into the second structural language type definition code using that mapping. The user code is then inserted in the second structural language code in the position determined. Accordingly, the user code that was added is not lost when the structural language type definition code is regenerated from the one or more database object types.

Preserving user code in OTT-generated classes

A method and apparatus for migrating the session state of an original session from a first node to a second node, such that a process, executing in the migrated session, may enqueue and dequeue messages from a queue of messages and experience the same behavior from the queue of messages as if the process was enqueuing and dequeuing messages in the original session. Advantageously, all the benefits of migrating a session from one node to another node may be realized, even when the session contains queuing state information that describes the state of a queue of messages. Data that indicates how many messages one or more subscribers have removed from the queue of messages may also be stored to preserve proper behavior of the queue of messages for multiple subscribers when sessions are migrated.

Capturing and re-creating the state of a queue when migrating a session

A method for providing memory management for objects is described. Specifically, techniques are described for providing common memory management code to objects that are instances of different classes and for releasing a memory management subtree that starts with a particular object in the memory management tree. A memory management template provides common pre-processor memory management code. A specialized version of the memory management template is used to create a specialized template subclass. When a memory management operator of an object that is an instance of the specialized template subclass is invoked the common memory management code in the specialized template is executed. Memory is associated with each object in a hierarchical tree. Data for the memory is maintained that reflects the hierarchical tree relationship between the objects. A subtree and the associated memory can be released without an application program tracking the relationships.

Providing common memory management code to objects that are instances of different classes

Simplified deallocation of memory for programming objects

Schema conversion approaches convert images of complex objects. The schema conversion is performed on images of complex objects belonging to a root class, whether those objects are instances of the root class or instances of a subclass of the root class. A complex object is an object that is comprised of a collection of objects or that has another object as an attribute. The approaches use change vectors to represent changes to make to an image to convert it between the target schema version and source schema version. Change vectors are generated based on schema version records, each of which describes the properties of a schema version, including the attributes in the schema version and the data type of each of the attributes. The approaches evolve changes that includes addition, modification and deletion of object attributes. They convert from an earlier schema version to a later schema version, and vice versa, i.e. from a later schema version to a earlier schema version.

Schema evolution of complex objects

One embodiment of the present invention provides a system that facilitates transactional consistency for references in an object-relational database. The system operates by first receiving a reference to an object located in the object-relational database. Next, the system creates a reference object within local storage that includes an object descriptor to indicate whether the object has been loaded into local storage. The reference is stored in this reference object. A pointer within an application program can then point to the reference object, so that the application program can use the pointer to access the object.

Method and apparatus to facilitate transactional consistency for references in object-relational databases

The present invention provides a method and mechanism to store and manage self-descriptive heterogeneous data in a database system. In one embodiment, a generic datatype is defined which encapsulate type descriptions along with the actual data itself. Another generic datatype is defined to encapsulate structural information for new datatypes. By using these generic datatypes to encapsulate heterogeneous data, the database system can be made aware of the exact structure and format of the heterogeneous data. This permits users and the database system to store, manage, and access the heterogeneous data like known datatypes in the system. Other objects, advantages, and features of the invention are described in the Drawings, Claims, and Detailed Description.

Method and mechanism for storing and managing self-descriptive heterogeneous data

Growing community of inventors

Union City, CA, United States of America

Ravikanth Kasamsetty