CN111400110A - Database access management system - Google Patents
Database access management system Download PDFInfo
- Publication number
- CN111400110A CN111400110A CN202010164911.3A CN202010164911A CN111400110A CN 111400110 A CN111400110 A CN 111400110A CN 202010164911 A CN202010164911 A CN 202010164911A CN 111400110 A CN111400110 A CN 111400110A
- Authority
- CN
- China
- Prior art keywords
- database
- router
- external service
- service application
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004458 analytical method Methods 0.000 claims description 4
- 230000003993 interaction Effects 0.000 claims description 4
- 238000007726 management method Methods 0.000 description 37
- 238000010586 diagram Methods 0.000 description 8
- 238000013507 mapping Methods 0.000 description 5
- 101001110283 Canis lupus familiaris Ras-related C3 botulinum toxin substrate 1 Proteins 0.000 description 3
- 101001110313 Homo sapiens Ras-related C3 botulinum toxin substrate 2 Proteins 0.000 description 3
- 102100022122 Ras-related C3 botulinum toxin substrate 1 Human genes 0.000 description 3
- 102100022129 Ras-related C3 botulinum toxin substrate 2 Human genes 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 108010062302 rac1 GTP Binding Protein Proteins 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000013523 data management Methods 0.000 description 1
- 238000000034 method Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
Abstract
The embodiment of the invention discloses a database access management system. The system comprises: the system comprises a database routing management layer and a database deployed at the cloud end, wherein the database routing management layer comprises routers with a set number, and the set number is the same as the number of the databases deployed at the cloud end; each router manages a database of the cloud in a one-to-one correspondence mode, each database is marked as a main database in a corresponding router, each router also manages a standby database in a one-to-one correspondence mode, and the standby database is a database which is deployed at the cloud and is different from the main database in the router to which the standby database belongs; and the router is used for controlling the managed standby library to respond to the database access request so as to realize data write access of the external service application to the standby library if the managed main library is monitored to be in a downtime state when the database access request of the external service application is received. According to the technical scheme of the embodiment of the invention, the implementation of the external service application is not influenced by the downtime of the database, and the stability of the system is improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of database application, in particular to a database access management system.
Background
The Oracle RAC (Real Application Clusters) is a technology adopted in an Oracle new database, is a high-availability technology, and is also a core technology of the Oracle database supporting a network computing environment.
The Oracle RAC provides cluster software and storage management software at the present stage, application cost is reduced for users, when application scale needs to be expanded, the performance of the system can be ensured only by expanding the system as required, and high availability of the system is set based on hardware, namely, the system is set based on hardware facilities of a physical machine, the load of a plurality of nodes is balanced, and when one RAC is down, problems can be found and eliminated in time.
When the Oracle RAC is deployed on the cloud virtual machine, since hardware facilities of the virtual machine are virtual, the high availability of the Oracle RAC becomes unpredictable, and when the RAC is down, external service applications calling the RAC are also affected, thereby reducing the availability and stability of the system.
Disclosure of Invention
The invention provides a database access management system, which aims to realize high availability of a database and improve the stability of the system.
An embodiment of the present invention provides a database access management system, including: a database routing management layer and a database deployed in the cloud,
the database routing management layer comprises a set number of routers, wherein the set number is the same as the number of databases deployed at the cloud end;
each router manages a database of the cloud in a one-to-one correspondence mode, each database is marked as a main database in a corresponding router, each router also manages a standby database in a one-to-one correspondence mode, and the standby database is a database which is deployed at the cloud and is different from the main database in the router to which the standby database belongs;
and the router is used for controlling the managed standby library to respond to the database access request so as to realize data write access of the external service application to the standby library if the managed main library is monitored to be in a downtime state when the database access request of the external service application is received.
Further, the database access management system further includes: a routing configuration layer for configuring the routing of the packet,
and the routing configuration layer is respectively connected with the external service application and the database routing management layer and is used for analyzing the database access request sent by the external service application, determining a target router corresponding to the database routing management layer of the external service application and forwarding the database access request to the target router.
Further, the routing configuration layer comprises:
the information analysis module is used for analyzing a database access request sent by the external service application and acquiring database access object information of the external service application;
the target determining module is used for determining a target router corresponding to the external service application according to the database access object information;
and the request forwarding module is used for forwarding the database access request to the target router.
Further, the target determination module specifically includes:
the first determining unit is used for determining a target router according to a special routing configuration rule when an external service application corresponding to the database access object information and other external service applications share a data table with the same table name, wherein the database comprises a plurality of data tables;
the second determining unit is used for determining a target router according to a naming space routing configuration rule when the external service application corresponding to the database access object information does not share the data table with the same table name with other external service applications and the database access object information contains a valid naming space;
and the third determining unit is used for determining the target router according to the default routing configuration rule when the external service application corresponding to the database access object information does not share the data table with the same table name with other external service applications and the database access object information does not contain an effective name space.
Further, the first determining unit is specifically configured to:
determining a first data table with an identification field according to an external service application corresponding to the database access object information;
and determining a target database where the first data table is located, and determining a router taking the target database as a main database as a target router.
Further, the second determining unit is specifically configured to:
determining a second data table corresponding to the database access object information according to the effective name space contained in the database access object information;
and determining a target database where the second data table is located, and determining the router taking the target database as a main database as a target router.
Further, the third determining unit is specifically configured to:
and selecting a database deployed by the cloud as a target database according to a random principle, and determining a router taking the target database as a main database as a target router.
And furthermore, the database deployed at the cloud is used for synchronizing the service data stored corresponding to the external service application into the database serving as the main database in the router to which the service data belongs after the interaction with the external service application is finished when the database serving as the standby database in the router is accessed by the external service application, and clearing the service data.
Further, the router is further configured to, after controlling the managed standby library to respond to the database access request, control the main library to respond to the database access request if it is monitored that the main library is currently in a normal operating state or is restored to the normal operating state from a downtime.
The embodiment of the invention provides a database access management system, which comprises: the system comprises a database routing management layer and a database deployed at the cloud end, wherein the database routing management layer comprises routers with a set number, and the set number is the same as the number of the databases deployed at the cloud end; each router manages a database of the cloud in a one-to-one correspondence manner, each database is marked as a main database in the corresponding router, each router also manages a standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed at the cloud and is different from the main database in the router; and the router is used for controlling the managed standby library to respond to the database access request so as to realize data write access of the external service application to the standby library if the managed main library is monitored to be in a downtime state when the database access request of the external service application is received. By adopting the technical scheme, the main database and the standby database which are in one-to-one correspondence with the cloud deployment databases are configured in each router, when the main database is in a downtime state, the standby database is controlled to complete response to the database access request and write access to external service application data, the problem that high availability cannot be predicted when the databases are deployed on the cloud virtual machine can be solved, when one database is in a downtime state, the other database is started in time, so that the implementation of external service application is not affected by the downtime of the databases, and the stability of the system is improved.
Drawings
Fig. 1 is a schematic structural diagram of a database access management system according to a first embodiment of the present invention;
fig. 2 is a schematic structural diagram of a database access management system in the second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a routing configuration layer in the second embodiment of the present invention;
fig. 4 is a diagram illustrating an exemplary configuration of a database access management system according to a second embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures. In addition, the embodiments and features of the embodiments in the present invention may be combined with each other without conflict.
Example one
Fig. 1 is a schematic structural diagram of a database access management system according to an embodiment of the present invention, where the database access management system includes: a database route management layer 10 and a database 11 deployed in the cloud.
The database routing management layer 10 includes a set number of routers 12, where the set number is the same as the number of databases 11 deployed in the cloud.
Each router 12 manages one database 11 of the cloud in a one-to-one correspondence manner, each database 11 is a main database in the corresponding router 12, each router 12 also manages one backup database in a one-to-one correspondence manner, and each backup database is a database 11 which is deployed at the cloud and is different from the main database in the router 12.
The router 12 is configured to, when receiving a database access request of the external service application 13, if it is monitored that the managed main library is in a downtime state, control the managed standby library to respond to the database access request, so as to implement data write access from the external service application 13 to the standby library.
The database routing management layer 10 may be understood as a layer consisting of a set number of routers 12 for managing data objects of a plurality of different routers 12.
The router 12 may be understood as a hardware device for connecting two or more networks, and may be understood as a hardware device for managing two or more databases 11 deployed in the cloud. The number of the routers 12 is the same as that of the databases 11 deployed at the cloud, one database 11 is managed as a main library in a one-to-one correspondence manner, and meanwhile, one database 11 different from the main library is managed as a standby library in a one-to-one correspondence manner, optionally, the main library in one router 12 is the standby library in another router 12 matched with the main library, and the main library in another router 12 matched with the main library is the standby library in the router 12.
The database 11 is understood to be a repository that organizes, stores and manages data according to a data structure, and is a collection of data that is stored together in a manner that can be shared by multiple users, has as little redundancy as possible, and is independent of the application. Illustratively, in an Oracle database architecture, a Real Application Cluster (RAC) may be understood as a database.
Specifically, a plurality of databases 11 are deployed at the cloud, and correspondingly, routers 12 with the same number as the cloud databases are deployed in the database routing management layer 10. Each router 12 and the database 11 in the cloud form a one-to-one corresponding management relationship, the database 11 managed correspondingly is a main database in the corresponding router 12, each router 12 manages one database 11 in the cloud except the main database as a standby database, wherein the two databases 11 are the main database and the standby database in each other in a pair of routers 12, that is, the main database in one router 12 is the standby database in the other router 12, and the standby database in one router 12 is the main database in the other router 12. When receiving a database access request from the external service application 13, if it is monitored that the main library managed by the router is in a downtime state, the router 12 controls the standby library managed by the router to respond to the database access request so as to respond to the external service application 13, thereby realizing data write access of the external service application 13.
The external service application 13 may be an external application program that performs a rewrite call to the database contents through a Data Access Object (DAO) input system.
Further, the database 11 deployed at the cloud is configured to, when being accessed by the external service application 13 as a standby database in one router 12, synchronize the service data stored by the corresponding external service application 13 into the database 11 serving as the main database in the router 12 to which the external service application 13 belongs after the interaction with the external service application 13 is finished, and clear the service data.
Wherein, the service data stored by the external service application 13 can be written into the database in the form of a data table.
Specifically, when the router 12 receives the access of the external service application 13, the main library is in a down state, the standby library in the router 12 is accessed, at this time, data writing access from the external service application 13 to the standby library and reading access to data already stored in the standby library can be completed, after the standby library finishes interaction with the external service application 13, the standby library synchronizes the service data written from the external service application 13 to the database 11 serving as the main library in the router 12 to which the standby library belongs, and clears the service data in the standby library.
Further, the router 12 is further configured to, after controlling the managed standby library to respond to the database access request, if it is monitored that the main library is currently in a normal state or is recovered from a downtime state to a normal operating state, control the main library to respond to the database access request.
Specifically, the router 12 monitors the working state of the master library through a heartbeat procedure, and when the master library is in a normal working state, the master library is used as the current use library to respond to the database access request. And when the main library is in a downtime state, the standby library is used as the current use library to respond to the database access request, meanwhile, the working state of the main library is monitored continuously, and when the working state of the main library is recovered to be normal, the main library is used as the current use library again to respond to the database access request. Optionally, after the main library recovers to the normal working state, the service data stored in the downtime external service application 13 is synchronized from the standby library to the main library, and the service data stored in the standby library is deleted at the same time.
The embodiment of the invention provides a database access management system, which comprises: the system comprises a database routing management layer and a database deployed at the cloud end, wherein the database routing management layer comprises routers with a set number, and the set number is the same as the number of the databases deployed at the cloud end; each router manages a database of the cloud in a one-to-one correspondence manner, each database is marked as a main database in the corresponding router, each router also manages a standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed at the cloud and is different from the main database in the router; and the router is used for controlling the managed standby library to respond to the database access request so as to realize data write access of the external service application to the standby library if the managed main library is monitored to be in a downtime state when the database access request of the external service application is received. By adopting the technical scheme, the main database and the standby database which are in one-to-one correspondence with the cloud deployment databases are configured in each router, when the main database is in a downtime state, the standby database is controlled to complete response to the database access request and write access to external service application data, the problem that high availability cannot be predicted when the databases are deployed on the cloud virtual machine can be solved, when one database is in a downtime state, the other database is started in time, so that the implementation of external service application is not affected by the downtime of the databases, and the stability of the system is improved.
Example two
Fig. 2 is a schematic structural diagram of a database access management system according to a second embodiment of the present invention, where the technical solution of this embodiment is further refined based on the above technical solution, and the database access management system includes: a database route management layer 10 and a database 11 deployed in the cloud.
The database routing management layer 10 includes a set number of routers 12, where the set number is the same as the number of databases 11 deployed in the cloud.
Each router 12 manages one database 11 of the cloud in a one-to-one correspondence manner, each database 11 is a main database in the corresponding router 12, each router 12 also manages one backup database in a one-to-one correspondence manner, and each backup database is a database 11 which is deployed at the cloud and is different from the main database in the router 12.
The router 12 is configured to, when receiving a database access request of the external service application 13, if it is monitored that the managed main library is in a downtime state, control the managed standby library to respond to the database access request, so as to implement data write access from the external service application 13 to the standby library.
The database access management system further includes a routing configuration layer 14, where the routing configuration layer 14 is connected to the external service application 13 and the database routing management layer 10, respectively, and is configured to analyze a database access request sent by the external service application 13, determine a target router corresponding to the external service application 13 on the database routing management layer 10, and forward the database access request to the target router.
The routing configuration layer 14 may be understood as a data management layer for determining a target database according to the database access request of the external service application 13 and allocating the router 12 in which the target database exists as a target router to the external service application 13 for access response.
Specifically, the external service application 13 sends a database access request through the DAO layer, the routing configuration layer 14 receives the database access request to determine the database 11 that the external service application 13 needs to access, and determines the router 12 that uses the database 11 as a master base as a target router according to the determined database 11, determines the position of the target router in the database routing management layer 10 and forwards the database access request to the target router, and the target router monitors the working state of the master base therein and completes data write access of the external service application 13 according to the working state of the master base.
Further, fig. 3 is a schematic structural diagram of a routing configuration layer according to a second embodiment of the present invention, where the routing configuration layer 14 specifically includes: an information analysis module 21, a target determination module 22, and a request forwarding module 23.
The information analysis module 21 is configured to analyze a database access request sent by the external service application 13, and acquire database access object information of the external service application 13. And the target determining module 22 is used for determining the target router corresponding to the external service application 13 according to the database access object information. A request forwarding module 23, configured to forward the database access request to the target router.
Further, the goal determining module 22 includes:
a first determining unit, configured to determine the target router according to a special routing configuration rule if the external service application 13 corresponding to the database access object information shares a data table with a same table name with other external service applications 13, where the database includes multiple data tables;
a second determining unit, configured to determine the target router according to a namespace routing configuration rule if the external service application 13 corresponding to the database access object information does not share a data table with the same table name with other external service applications 13, and the database access object information includes a valid namespace;
a third determining unit, configured to determine the target router according to a default routing configuration rule if the external service application 13 corresponding to the database access object information does not share a data table with the same table name with other external service applications 13, and the database access object information does not include an effective namespace.
The data table in which the external service application 13 corresponding to the database access object information and the other external service applications 13 share the same table name may be understood as a data table in which two external service applications 13 correspond to the same table name, the data table exists in two different databases 11, the two data tables have different stored data, and the external service application 13 identifies the corresponding data table through an identification field.
The special routing configuration rule can be understood as mapping the router according to a Thread local variable (Thread L ocal), and mapping the data table with the same table name and different identification fields, the database to which the data table belongs and the router by setting a Thread L ocal variable to the service layer code.
Therein, a namespace may be understood as a code number, like a name, for organizing and utilizing code for representing data table names under the iBatis database management framework in the object mapping framework.
The namespace routing configuration rule can be understood as that a corresponding database and a router are determined according to a namespace obtained from database access object information and configured namespace mapping.
The default routing configuration rule may be understood as an unconfigured configuration rule that randomly selects one of the cloud-deployed databases 11 to access the router 12 using the database 11 as a master.
The priority order of the three routing configuration rules is firstly configured according to the special routing configuration rule, the routing configuration of the name space is carried out under the condition of no special routing configuration, and if the two routing configuration rules do not exist, the target router is determined according to the default routing configuration rule.
Further, the first determining unit is specifically configured to:
when the external service application 13 corresponding to the database access object information and other external service applications 13 share a data table with the same table name, determining a first data table with an identification field according to the external service application 13 corresponding to the database access object information; the database 11 where the first data table is located is determined as a target database, and the router 12 using the target database as a main database is determined as a target router.
Specifically, when the external service application 13 corresponding to the database access object information is an application that shares the same table name data table with other external service applications 13, the routing configuration layer 14 obtains, from the database access object information, an identification field that is different between the external service application 13 that sent the database access object information and the other external service applications 13, determines the first data table and the database 11 that includes the first data table according to the identification field, uses the database 11 as a target database, and finds the router 12 that uses the target database as a master database in the database routing management layer 10 to determine the router as the target router.
Further, the second determining unit is specifically configured to:
when the external service application 13 corresponding to the database access object information does not share the data table with the same table name with other external service applications 13 and the database access object information contains an effective name space, determining a second data table corresponding to the database access object information according to the effective name space contained in the database access object information; the target database where the second data table is located is determined, and the router 12 having the target database as the master database is determined as the target router.
Specifically, when the external service application 13 corresponding to the database access object information does not share a data table with the same table name as the other external service applications 13, a namespace corresponding to the database access object information under the iBatis framework is obtained according to the function, whether the namespace corresponding to the database access object information is an effective namespace is judged according to the configured namespace mapping, if the namespace is the effective namespace, a second data table corresponding to the effective namespace is determined according to the effective namespace, the database 11 containing the second data table is determined, the database 11 is used as a target database, and the router 12 which takes the target database as a main database is found in the database routing management layer 10 and determined as a target router.
Further, the third determining unit is specifically configured to:
when the external service application 13 corresponding to the database access object information does not share the data table with the same table name with other external service applications 13 and the database access object information does not contain an effective name space, selecting one cloud deployed database 11 as target data according to a random principle, and determining the router 12 taking the target database as a main database as a target router.
For example, fig. 4 is a diagram illustrating a structure of a database access management system according to a second embodiment of the present invention, specifically, an external service application accesses a DAO layer and sends a database access request to the DAO layer, determines a database access object and database access object information, and sends the database access request to a routing configuration layer, where the routing configuration layer determines a sub-base and sub-table route to which the external service application should access according to a preset routing configuration rule, and each sub-base and sub-table route includes two databases, which are a main base and a backup base. Taking the two databases as RAC1 and RAC2 as examples, the sub-base and sub-table route 1 uses RAC1 as the main base and the priority use base, RAC2 as the standby base, and the sub-base and sub-table route 2 uses RAC2 as the main base and RAC1 as the standby base, so that the sub-base and sub-table routes 1 and 2 are a pair of routers which manage a pair of databases which are the main base and the standby base. When one of the sub-base sub-table routes receives the database access request information transmitted by the route configuration layer, the sub-base sub-table route acquires the working state of the main base in the route from the main base monitor. The monitoring comprises two conditions, namely monitoring whether the main library is down when the main library is not down, and monitoring whether the main library is recovered when the main library is in a down state. When the work state of the master library is monitored to be normal, the master library is used as a current use library, and a database access request of external service application is responded; and when the main library is monitored to be down, the standby library is used as the current use library to respond to a database access request of the external service application, wherein the data write-in request in the database access request and the read request of the existing data in the backup library can only be responded. When the working state of the main library is monitored to be recovered to normal, the data received by the standby library in the downtime phase of the main library can be automatically or manually synchronized to the main library, and the data in the standby library is deleted. Further, if the main library and the standby library are in the downtime state, the access of the external service application fails, and error information is returned and the background is reminded to perform manual processing.
According to the technical scheme, the data table corresponding to access is determined according to the database access request sent by the external service application, the corresponding target database and the target router determined by the scenario target database are determined according to the data table, the databases in different routers are mutually the main database and the backup database, the problems that the utilization rate of the database serving as the backup database is low and resources are wasted when the main database in the router is not down are solved, the utilization rate of the database is improved, meanwhile, the database is timely switched to the backup database when the main database is down, the response of the external service application is guaranteed, and the stability and the availability of the system are improved.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (9)
1. A database access management system, comprising: a database routing management layer and a database deployed in the cloud,
the database routing management layer comprises a set number of routers, wherein the set number is the same as the number of databases deployed at the cloud end;
each router manages a database of the cloud in a one-to-one correspondence manner, each database is recorded as a main database in the corresponding router, each router also manages a standby database in a one-to-one correspondence manner, and the standby database is a database which is deployed at the cloud and is different from the main database in the router to which the router belongs;
the router is used for controlling the managed standby library to respond to the database access request so as to realize data write access of the external service application to the standby library if the managed main library is monitored to be in a downtime state when the database access request of the external service application is received.
2. The system of claim 1, further comprising: a routing configuration layer for configuring the routing of the packet,
the routing configuration layer is respectively connected with the external service application and the database routing management layer and is used for analyzing a database access request sent by the external service application, determining a target router corresponding to the database routing management layer of the external service application and forwarding the database access request to the target router.
3. The system of claim 2, the routing configuration layer, comprising:
the information analysis module is used for analyzing the database access request sent by the external service application and acquiring the database access object information of the external service application;
the target determining module is used for determining a target router corresponding to the external service application according to the database access object information;
and the request forwarding module is used for forwarding the database access request to the target router.
4. The system of claim 3, wherein the goal determination module specifically comprises:
a first determining unit, configured to determine the target router according to a special routing configuration rule when the external service application corresponding to the database access object information shares a data table with a same table name as another external service application, where the database includes multiple data tables;
a second determining unit, configured to determine the target router according to a namespace routing configuration rule when the external service application corresponding to the database access object information does not share a data table with the same table name with other external service applications, and the database access object information includes a valid namespace;
and a third determining unit, configured to determine the target router according to a default routing configuration rule when the external service application corresponding to the database access object information does not share a data table with the same table name as another external service application, and the database access object information does not include an effective namespace.
5. The system according to claim 4, wherein the first determining unit is specifically configured to:
determining a first data table with an identification field according to the external service application corresponding to the database access object information;
and determining a target database where the first data table is located, and determining a router taking the target database as a main database as the target router.
6. The system according to claim 4, wherein the second determining unit is specifically configured to:
determining a second data table corresponding to the database access object information according to the effective name space contained in the database access object information;
and determining a target database where the second data table is located, and determining a router taking the target database as a main database as the target router.
7. The system according to claim 4, wherein the third determining unit is specifically configured to:
and selecting one database deployed by the cloud as a target database according to a random principle, and determining a router taking the target database as a main database as a target router.
8. The system according to claim 1, wherein the cloud-deployed database is configured to synchronize the service data stored in the external service application to the database serving as the main database in the router to which the external service application belongs after the interaction with the external service application is ended when the database serving as the backup database in the router is accessed by the external service application, and to clear the service data.
9. The system according to claim 1, wherein the router is further configured to, after controlling the managed standby library to respond to the database access request, control the main library to respond to the database access request if it is monitored that the main library is currently in a normal operating state or is restored from a downtime state to a normal operating state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010164911.3A CN111400110B (en) | 2020-03-11 | 2020-03-11 | Database access management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010164911.3A CN111400110B (en) | 2020-03-11 | 2020-03-11 | Database access management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111400110A true CN111400110A (en) | 2020-07-10 |
| CN111400110B CN111400110B (en) | 2023-12-19 |
Family
ID=71430804
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010164911.3A Active CN111400110B (en) | 2020-03-11 | 2020-03-11 | Database access management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111400110B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114238521A (en) * | 2022-02-25 | 2022-03-25 | 梅州客商银行股份有限公司 | High-availability deployment method and device for bank core system database and electronic equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5999978A (en) * | 1997-10-31 | 1999-12-07 | Sun Microsystems, Inc. | Distributed system and method for controlling access to network resources and event notifications |
| US20140258224A1 (en) * | 2013-03-11 | 2014-09-11 | Oracle International Corporation | Automatic recovery of a failed standby database in a cluster |
| CN104408174A (en) * | 2014-12-12 | 2015-03-11 | 用友软件股份有限公司 | Database routing device and method |
| CN105095317A (en) * | 2014-05-23 | 2015-11-25 | 中国银联股份有限公司 | Distributive database service management system |
| CN106294565A (en) * | 2016-07-27 | 2017-01-04 | 中国农业银行股份有限公司 | A kind of data bank access method and system |
| CN106503163A (en) * | 2016-10-31 | 2017-03-15 | 用友网络科技股份有限公司 | Based on the global configuration multi-tenant dynamic data origin system that SaaS is applied |
| CN107085570A (en) * | 2016-02-14 | 2017-08-22 | 华为技术有限公司 | Data processing method, application server and router |
| US20170344618A1 (en) * | 2010-12-23 | 2017-11-30 | Eliot Horowitz | Systems and methods for managing distributed database deployments |
| US20180246945A1 (en) * | 2017-02-27 | 2018-08-30 | Sap Se | Workload Capture and Replay for Replicated Database Systems |
-
2020
- 2020-03-11 CN CN202010164911.3A patent/CN111400110B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5999978A (en) * | 1997-10-31 | 1999-12-07 | Sun Microsystems, Inc. | Distributed system and method for controlling access to network resources and event notifications |
| US20170344618A1 (en) * | 2010-12-23 | 2017-11-30 | Eliot Horowitz | Systems and methods for managing distributed database deployments |
| US20140258224A1 (en) * | 2013-03-11 | 2014-09-11 | Oracle International Corporation | Automatic recovery of a failed standby database in a cluster |
| CN105095317A (en) * | 2014-05-23 | 2015-11-25 | 中国银联股份有限公司 | Distributive database service management system |
| CN104408174A (en) * | 2014-12-12 | 2015-03-11 | 用友软件股份有限公司 | Database routing device and method |
| CN107085570A (en) * | 2016-02-14 | 2017-08-22 | 华为技术有限公司 | Data processing method, application server and router |
| CN106294565A (en) * | 2016-07-27 | 2017-01-04 | 中国农业银行股份有限公司 | A kind of data bank access method and system |
| CN106503163A (en) * | 2016-10-31 | 2017-03-15 | 用友网络科技股份有限公司 | Based on the global configuration multi-tenant dynamic data origin system that SaaS is applied |
| US20180246945A1 (en) * | 2017-02-27 | 2018-08-30 | Sap Se | Workload Capture and Replay for Replicated Database Systems |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114238521A (en) * | 2022-02-25 | 2022-03-25 | 梅州客商银行股份有限公司 | High-availability deployment method and device for bank core system database and electronic equipment |
| CN114238521B (en) * | 2022-02-25 | 2022-06-24 | 梅州客商银行股份有限公司 | High-availability deployment method and device for bank core system database and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111400110B (en) | 2023-12-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11360854B2 (en) | Storage cluster configuration change method, storage cluster, and computer system | |
| CN109040212B (en) | Method, system, device and storage medium for accessing device to server cluster | |
| JP5047165B2 (en) | Virtualization network storage system, network storage apparatus and virtualization method thereof | |
| US5890156A (en) | Distributed redundant database | |
| US7260656B2 (en) | Storage system having a plurality of controllers | |
| US8676951B2 (en) | Traffic reduction method for distributed key-value store | |
| US7237027B1 (en) | Scalable storage system | |
| US9454444B1 (en) | Using location tracking of cluster nodes to avoid single points of failure | |
| US7966470B2 (en) | Apparatus and method for managing logical volume in distributed storage systems | |
| CN108183961A (en) | A kind of distributed caching method based on Redis | |
| US10320905B2 (en) | Highly available network filer super cluster | |
| JP2010134757A (en) | Method and device for controlling fail over of server and computer system group | |
| JP2007079885A (en) | Data input and output load distribution method, data input and output load distribution program, computer system, and management server | |
| CN110175089A (en) | A kind of dual-active disaster recovery and backup systems with read and write abruption function | |
| CN109391487A (en) | A kind of configuration update method and system | |
| CN112416892A (en) | Emergency video data cloud storage system | |
| US10057348B2 (en) | Storage fabric address based data block retrieval | |
| CN108462756A (en) | A kind of method for writing data and device | |
| CN111400110B (en) | Database access management system | |
| JP2020191100A (en) | System, control method therefor, and program | |
| CN111381766B (en) | Method for dynamically loading disk and cloud storage system | |
| KR20120063946A (en) | Memory apparatus for collective volume memory and metadate managing method thereof | |
| CN112860480B (en) | Double-live storage system and data processing method thereof | |
| CN209134427U (en) | A kind of vehicle-mounted command communications system of complete disaster tolerance | |
| US20040022200A1 (en) | Method, system, and program for providing information on components within a network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220914 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |