Automated integrated high availability of the in-memory database cache and the backend enterprise database
    1.
    发明授权
    Automated integrated high availability of the in-memory database cache and the backend enterprise database 有权
    自动集成高可用性的内存数据库缓存和后端企业数据库

    公开(公告)号:US08306951B2

    公开(公告)日:2012-11-06

    申请号:US12719264

    申请日:2010-03-08

    IPC分类号: G06F17/30

    摘要: A cluster manager is configured to manage a plurality of copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager to behave in this fashion during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

    摘要翻译: 集群管理器被配置为将中间层数据库的多个副本作为中间层数据库集群进行管理。 集群管理器可以同时管理后端数据库系统。 集群管理器配置为监视中层数据库节点的故障并对其做出反应。 集群管理器可以通过例如分配新的活动节点,创建新的备用节点,创建中间层数据库的新副本,实现新的复制或备份方案来对中间层数据库故障作出反应,重新分配节点的虚拟 地址到另一个节点,或将直接链接到中间层数据库的应用程序重新定位到另一个主机。 基于常见的集群配置信息,每个节点或相关联的代理可以在初始化期间将集群管理器配置为以这种方式行事。 中间层数据库的每个副本可以是例如内存驻留数据库。 因此,节点必须将整个数据库重新加载到内存中以恢复数据库的副本。

    AUTOMATED INTEGRATED HIGH AVAILABILITY OF THE IN-MEMORY DATABASE CACHE AND THE BACKEND ENTERPRISE DATABASE
    2.
    发明申请
    AUTOMATED INTEGRATED HIGH AVAILABILITY OF THE IN-MEMORY DATABASE CACHE AND THE BACKEND ENTERPRISE DATABASE 有权
    内存数据库高速缓存和后端企业数据库的自动化高可用性

    公开(公告)号:US20110071981A1

    公开(公告)日:2011-03-24

    申请号:US12719264

    申请日:2010-03-08

    IPC分类号: G06F17/30

    摘要: A cluster manager is configured to manage a plurality of copies of a mid-tier database as a mid-tier database cluster. The cluster manager may concurrently manage a backend database system. The cluster manager is configured to monitor for and react to failures of mid-tier database nodes. The cluster manager may react to a mid-tier database failure by, for example, assigning a new active node, creating a new standby node, creating new copies of the mid-tier databases, implementing new replication or backup schemes, reassigning the node's virtual address to another node, or relocating applications that were directly linked to the mid-tier database to another host. Each node or an associated agent may configure the cluster manager to behave in this fashion during initialization, based on common cluster configuration information. Each copy of the mid-tier database may be, for example, a memory resident database. Thus, a node must reload the entire database into memory to recover a copy of the database.

    摘要翻译: 集群管理器被配置为将中间层数据库的多个副本作为中间层数据库集群进行管理。 集群管理器可以同时管理后端数据库系统。 集群管理器配置为监视中层数据库节点的故障并对其做出反应。 集群管理器可以通过例如分配新的活动节点,创建新的备用节点,创建中间层数据库的新副本,实现新的复制或备份方案来对中间层数据库故障作出反应,重新分配节点的虚拟 地址到另一个节点,或将直接链接到中间层数据库的应用程序重新定位到另一个主机。 基于常见的集群配置信息,每个节点或相关联的代理可以在初始化期间将集群管理器配置为以这种方式行事。 中间层数据库的每个副本可以是例如内存驻留数据库。 因此,节点必须将整个数据库重新加载到内存中以恢复数据库的副本。

    Distributed consistent grid of in-memory database caches
    7.
    发明授权
    Distributed consistent grid of in-memory database caches 有权
    分布式一致的内存数据库缓存网格

    公开(公告)号:US08401994B2

    公开(公告)日:2013-03-19

    申请号:US12562928

    申请日:2009-09-18

    IPC分类号: G06F17/00

    CPC分类号: G06F17/30312 G06F12/084

    摘要: A plurality of mid-tier databases form a single, consistent cache grid for data in a one or more backend data sources, such as a database system. The mid-tier databases may be standard relational databases. Cache agents at each mid-tier database swap in data from the backend database as needed. Consistency in the cache grid is maintained by ownership locks. Cache agents prevent database operations that will modify cached data in a mid-tier database unless and until ownership of the cached data can be acquired for the mid-tier database. Cache groups define what backend data may be cached, as well as a general structure in which the backend data is to be cached. Metadata for cache groups is shared to ensure that data is cached in the same form throughout the entire grid. Ownership of cached data can then be tracked through a mapping of cached instances of data to particular mid-tier databases.

    摘要翻译: 多个中间层数据库形成用于一个或多个后端数据源(例如数据库系统)中的数据的单一,一致的高速缓存网格。 中间层数据库可以是标准关系数据库。 每个中间层数据库的缓存代理根据需要从后端数据库交换数据。 高速缓存网格中的一致性由所有权锁定维护。 高速缓存代理阻止数据库操作,将修改中间层数据库中的缓存数据,除非可以为中间层数据库获取缓存数据的所有权。 缓存组定义可以缓存哪些后端数据,以及要缓存后端数据的一般结构。 共享缓存组的元数据,以确保数据在整个网格中以相同的格式缓存。 然后可以通过将缓存的数据实例映射到特定中间层数据库来跟踪缓存数据的所有权。