CN116679965A - Database client upgrading method and system - Google Patents

Database client upgrading method and system Download PDF

Info

Publication number
CN116679965A
CN116679965A CN202310827289.3A CN202310827289A CN116679965A CN 116679965 A CN116679965 A CN 116679965A CN 202310827289 A CN202310827289 A CN 202310827289A CN 116679965 A CN116679965 A CN 116679965A
Authority
CN
China
Prior art keywords
database
client
characteristic information
database client
plug
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.)
Pending
Application number
CN202310827289.3A
Other languages
Chinese (zh)
Inventor
夏旭东
殷德明
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dbsec Technology Co ltd
Original Assignee
Beijing Dbsec Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Dbsec Technology Co ltd filed Critical Beijing Dbsec Technology Co ltd
Priority to CN202310827289.3A priority Critical patent/CN116679965A/en
Publication of CN116679965A publication Critical patent/CN116679965A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application discloses a method and a system for upgrading a database client, wherein the method comprises the following steps: determining that the database client needs to be upgraded, and judging whether a plug-in is installed on the database client; acquiring a database type corresponding to a database client; determining a storage mode of characteristic information of the database according to the type of the database; and updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information. The application solves the problem that when the plug-in is used for acquiring the database flow, if the database client is upgraded, the plug-in can not work so as to influence the database audit, thereby ensuring that the plug-in can still normally capture the database flow after the database client is upgraded and ensuring the normal running of the database audit.

Description

Database client upgrading method and system
Technical Field
The application relates to the field of databases, in particular to a method and a system for upgrading a database client.
Background
Database audit (DBAudio for short) is centered on security events, based on comprehensive audit and accurate audit, database activities on a network are recorded in real time, compliance management of fine-grained audit is performed on database operation, and real-time warning is performed on risk behaviors suffered by the database. The method helps the user to generate compliance reports and accident tracing sources afterwards by recording, analyzing and reporting the behaviors of the user access database, and simultaneously provides high-efficiency inquiry audit reports and positions event reasons through a big data searching technology so as to inquire, analyze and filter the event reasons later, thereby realizing the monitoring and audit of the network behaviors of the internal database and the external database and improving the safety of data assets.
When the database is audited, the slave interaction machine can be adopted to copy and mirror the database flow, and then the copied database flow is sent to the auditing equipment for auditing. The method is applied to the situation that the database client and the database server are not on the same server any more, and at the moment, the traffic between the database client and the database server passes through the switch, so that the traffic passing through the switch can be duplicated.
If the database client and the database server are on the same server, the database traffic between the database client and the server does not pass through the switch, so that the database traffic cannot be copied. In this case, it is necessary to install an agent (simply referred to as agent) on the server. And the agent program grabs a packet on a network card of the server and sends the grabbed database flow to auditing equipment for auditing. In addition to this, a plug-in (referred to as plug in) may be installed on the database client, and the plug-in obtains the database traffic between the database client and the database server, and then the plug-in sends the obtained database traffic to the agent, and then the agent sends the obtained database traffic to the auditing apparatus.
In the scenario of using plug-ins, the inventors have found that in some cases if a database client is upgraded, the plug-ins may be rendered inoperable, thereby affecting the normal operation of database auditing.
Disclosure of Invention
The embodiment of the application provides a method and a system for upgrading a database client, which at least solve the problem that when a plug-in is used for acquiring database traffic, if the database client is upgraded, the plug-in can not work, so that the database audit is affected.
According to one aspect of the present application, there is provided a database client upgrade method, including: determining that a database client needs to be updated, and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the database flow interacted between the database client and a database server, and the database client and the database server are installed on the same server; the method comprises the steps that under the condition that the plug-in is installed on the database client, the database type corresponding to the database client is obtained; determining a storage mode of characteristic information of the database according to the type of the database, wherein the characteristic information is used for indicating information used for connecting with the database; and updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information.
Further, determining a storage mode of the characteristic information of the database according to the database type comprises the following steps: and determining whether the characteristic information of the database is in a file of the database client or in a dynamic database on which the database client depends according to the database type.
Further, updating the database client according to the storage mode of the feature information includes: stripping the plug-in from the database client under the condition that the characteristic information of the database is stored in the file of the database client; upgrading the database client; and reinserting the plug-in into the database client after the database client is upgraded, and updating the characteristic information.
Further, updating the database client according to the storage mode of the feature information includes: monitoring whether the dynamic file is changed or not under the condition that the characteristic information of the database is stored in the dynamic file on which the database client depends; and under the condition that the dynamic file is changed, the characteristic information in the dynamic file is acquired again and updated.
According to another aspect of the present application, there is also provided a database client upgrade system, including: the judging module is used for determining that the database client needs to be updated and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the interactive database flow between the database client and the database server, and the database client and the database server are installed on the same server; the acquisition module is used for acquiring the database type corresponding to the database client under the condition that the plug-in is installed on the database client; the determining module is used for determining a storage mode of characteristic information of the database according to the type of the database, wherein the characteristic information is used for indicating information used for connecting with the database; and the updating module is used for updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information.
Further, the determining module is configured to: and determining whether the characteristic information of the database is in a file of the database client or in a dynamic database on which the database client depends according to the database type.
Further, the update module is configured to: stripping the plug-in from the database client under the condition that the characteristic information of the database is stored in the file of the database client; upgrading the database client; and reinserting the plug-in into the database client after the database client is upgraded, and updating the characteristic information.
Further, the update module is configured to: monitoring whether the dynamic file is changed or not under the condition that the characteristic information of the database is stored in the dynamic file on which the database client depends; and under the condition that the dynamic file is changed, the characteristic information in the dynamic file is acquired again and updated.
According to another aspect of the present application, there is also provided an electronic device including a memory and a processor; wherein the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to perform the method steps described above.
According to another aspect of the present application there is also provided a readable storage medium having stored thereon computer instructions which when executed by a processor perform the above-mentioned method steps.
In the embodiment of the application, the method comprises the steps of determining that a database client needs to be updated, and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the database flow interacted between the database client and a database server, and the database client and the database server are installed on the same server; the method comprises the steps that under the condition that the plug-in is installed on the database client, the database type corresponding to the database client is obtained; determining a storage mode of characteristic information of the database according to the type of the database, wherein the characteristic information is used for indicating information used for connecting with the database; and updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information. The application solves the problem that when the plug-in is used for acquiring the database flow, if the database client is upgraded, the plug-in can not work so as to influence the database audit, thereby ensuring that the plug-in can still normally capture the database flow after the database client is upgraded and ensuring the normal running of the database audit.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:
FIG. 1 is a schematic diagram of three audit modes according to an embodiment of the present application;
FIG. 2 is a schematic diagram of an audit traffic acquisition mode according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an agent crawling database traffic from a network card according to an embodiment of the present application; the method comprises the steps of,
fig. 4 is a flowchart of a database client upgrade method according to an embodiment of the present application.
Detailed Description
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
The English of the probe (also called agent) is agent, the English of the plug-in is plug in, and the functions of the probe and the plug-in are described below in connection with the database auditing product. The database audit product is a product which analyzes the database information and performs audit by analyzing the flow between networks. When the database audit is performed, various acquisition modes aiming at different types of database flows are provided, wherein the acquisition modes comprise a mirror image flow, a local audit mode and a local audit plug-in mode, and the three audit modes respectively aim at different scenes. Fig. 1 is a schematic diagram of three auditing modes according to an embodiment of the present application, as shown in fig. 1, the mirror flow mode is to obtain database flow (also referred to as auditing data) to be audited through a switch mirror flow function, and then send the auditing data to an auditing device (also referred to as auditing service) for auditing. The local auditing mode is to obtain the database flow by deploying a small agent program on the equipment where the database is located, obtaining the database access flow on the local network card and returning to the auditing equipment. The local audit plug-in mode is aimed at the scene that the client and the database are directly used in the same equipment, the client can perform data interaction in the modes of shared memory, pipelines, UDS and the like, and at the moment, the flow cannot be acquired from the network card. At this time, the flow is acquired by deploying a plug in to the client, and the acquired flow is sent to the agent program and then sent to the auditing device by the agent program.
Fig. 2 is a schematic diagram of an audit flow obtaining manner according to an embodiment of the present application, as shown in fig. 2, a database client (db-client) and a database server (db-server) are disposed on a database server, where a plug in is installed on the database client, and the plug in captures data of SQL interaction between the database client and the server, and these data are sent as audit data to a agent, and then the agent sends the audit data to an audit device. The auditing equipment provides an interface and a program (which can be called rms program for short) for receiving the auditing data, and then carries out protocol analysis on the received auditing data to obtain a final auditing result.
In fig. 2, plugin is a program, which may be embedded in a database client, to obtain, through interface feature information, an interaction flow between the database client and a database server. In the following embodiments, the plugin may record the obtained feature information of the database client transceiver packet interface into a certain file, and the feature information is different for different client types and different client versions.
In addition to acquiring the database traffic from the plugin, the Agent also captures the traffic from the network card, fig. 3 is a schematic diagram of the Agent program capturing the database traffic from the network card according to the embodiment of the present application, as shown in fig. 3, the database client and the database server interact through the network card 2, that is, the database traffic between the database client and the database server all passes through the network card 2, the Agent captures the database traffic through the network card, then sends the database traffic to the auditing device through the network card 2, and the auditing device receives the database traffic through the rms program and then performs auditing.
In the scenario shown in fig. 1 to 3, the type of each database of all databases installed on one server is obtained, wherein one database client is used to connect with each database server in all databases; acquiring characteristic information and port numbers of each database according to the type of each database; writing the characteristic information and the port number of each database into a file respectively; and taking the characteristic information of each database and the file corresponding to the port number as the file loaded when the plug-in is started, wherein each file corresponds to one plug-in, the plug-in is used for acquiring the database flow between the database client and the database server corresponding to the file, and the database flow is used for carrying out database audit. The characteristic information is used to indicate information used to connect with the database.
Optionally, the method further comprises: the plug-in sends the acquired database flow to an agent program; and the agent program sends the database flow to auditing equipment for auditing, wherein the agent program and the spread are both deployed on the server.
Optionally, the agent sending the database traffic to the auditing device for auditing includes: the agent program receives information from auditing equipment, wherein the information comprises a port number and an IP address of a database server side; the agent program stores the corresponding relation between the port numbers and the IP addresses of the auditing equipment and the database server; and the agent program sends the database traffic from different port numbers and IP addresses to corresponding auditing equipment according to the corresponding relation.
Optionally, the agent program storing the correspondence between the port numbers and the IP addresses of the auditing device and the database server side includes: the agent program carries out hash operation on the port number and the IP address to obtain an operation result; and the agent program stores the corresponding relation between the auditing equipment and the operation result.
As can be seen from the above description, the plugin is a program embedded in the client program, and obtains the interactive traffic between the client and the server through the interface feature information. Because the plug in is bound and embedded in a database client (db-client), and interface characteristic information needs to be acquired into a specified file, in the case that the db-client needs to be updated, the db-client embedded with the plug in is covered, so that local audit is invalid.
In order to solve the above-mentioned problems, a database client upgrade method is provided in the following embodiment, and fig. 4 is a flowchart of the database client upgrade method according to an embodiment of the present application, as shown in fig. 4, and the steps included in the method referred to in fig. 4 are described below.
Step S402, determining that a database client needs to be updated, and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the interactive database flow between the database client and a database server, and the database client and the database server are installed on the same server.
Step S404, obtaining a database type corresponding to the database client under the condition that the plug-in is installed on the database client.
Step S406, determining a storage mode of characteristic information of the database according to the database type, wherein the characteristic information is used for indicating information used for connecting with the database.
Step S408, updating the database client according to the storage manner of the feature information, where the feature information is updated in the update process of the database client, and the plug-in obtains the database traffic between the database client and the database server by using the updated feature information.
In an optional manner, determining, according to the database type, a storage manner of the feature information of the database includes: and determining whether the characteristic information of the database is in a file of the database client or in a dynamic database on which the database client depends according to the database type.
For example, updating the database client according to the storage mode of the feature information includes: stripping the plug-in from the database client under the condition that the characteristic information of the database is stored in the file of the database client; upgrading the database client; and reinserting the plug-in into the database client after the database client is upgraded, and updating the characteristic information.
For another example, updating the database client according to the storage mode of the feature information includes: monitoring whether the dynamic file is changed or not under the condition that the characteristic information of the database is stored in the dynamic file on which the database client depends; and under the condition that the dynamic file is changed, the characteristic information in the dynamic file is acquired again and updated.
The method solves the problem that when the plug-in is used for acquiring the database flow, if the database client is upgraded, the plug-in can possibly not work to influence the database audit, thereby ensuring that the plug-in can still normally capture the database flow after the database client is upgraded and ensuring the normal running of the database audit.
There are various file storage manners in which the feature information is located, for example, two folders of oracle and mysql may be stored under the dbtap directory, two folders of 1521 and 1522 may be stored under the oracle folder, two folders of 3306 and 3307 may be stored under the mysql folder, and one feature information file (feature) and one plugin (library. So) may be deployed under each folder. Where 1521, 1522, 3306, 3307 each indicate a port number, i.e. each port number creates a folder. In this way, a folder is created for each different type of database, and different instances under the same database use different port numbers, each port number corresponding to a subfolder under the database folder. In this example, multiple databases are installed on the same database server.
The two upgrade scenarios that exist are described below by targeting different database types.
The first case, the characteristic information of the interface, is in (simply referred to as characteristic information) db-client file, such as mysql.
The second case, the characteristic information of the interface, is in a db-client dependent dynamic library, such as oracle.
For the first case, the db-client file is directly replaced during upgrading, and the plugin in the db-client file is covered, so that audit is impossible; in the second case, the feature information stored in the designated file is inconsistent with the original library file information because the used dynamic library is replaced during upgrading, so that audit is impossible or db-client downtime is caused.
For both cases, a processing scheme is provided in this example where the processing upgrade results in an audit failure or db-client downtime. The solutions in this example are described separately for the two cases described above.
For the first case:
1) The plugin was first stripped from the db-client program.
2) The db-client upgrade procedure is executed, at which time db-client is upgraded to the latest version.
3) Reinserting db-client into db-client and updating interface characteristic information into specified file.
In the first case, the above steps may be automatically performed by configuring a program, or may be performed manually or manually.
For the second case:
in this case, since the peeling of the plugin does not need to be handled, the upgrade situation can be dynamically supported without manual intervention.
1) A dynamic library (transient name: ldd.so) whether the task mechanism was changed.
2) At the first start-up, verification information (for example, md 5) of a dynamic file (hereinafter, described as ldd.so) is acquired and recorded in a specified file.
3) And when the method is started for the second time, the md5 of the ldd.so file is re-acquired and compared with the md5 recorded in the file, if no difference exists, the method is ended, and if the difference exists, the method enters the next step.
4) And when the ldd.so files are different, the interface characteristic information of the ldd.so library files is acquired again and updated to the designated files.
5) The md5 information of the ldd.so file is updated again into the specified file.
In the above embodiment, a version corresponds to a file storing feature information, and the file is used by Plugin, and only the feature file Plugin corresponding to the version is used to work normally. The Agent and the plug-in can be arranged inside the container by adopting a containerization technology (i.e. dock), the distribution of the container is an immobilized process, and the newly added container can be automatically scanned when the Agent and the plug-in are placed on a host.
In this embodiment, there is provided an electronic device including a memory in which a computer program is stored, and a processor configured to run the computer program to perform the method in the above embodiment.
The above-described programs may be run on a processor or may also be stored in memory (or referred to as computer-readable media), including both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technique. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device.
These computer programs may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks and/or block diagram block or blocks, and corresponding steps may be implemented in different modules.
Such an apparatus or system is provided in this embodiment. The system is referred to as a database client upgrade system, comprising: the judging module is used for determining that the database client needs to be updated and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the interactive database flow between the database client and the database server, and the database client and the database server are installed on the same server; the acquisition module is used for acquiring the database type corresponding to the database client under the condition that the plug-in is installed on the database client; the determining module is used for determining a storage mode of characteristic information of the database according to the type of the database, wherein the characteristic information is used for indicating information used for connecting with the database; and the updating module is used for updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information.
The system or the device is used for realizing the functions of the method in the above embodiment, and each module in the system or the device corresponds to each step in the method, which has been described in the method, and will not be described herein.
Optionally, the determining module is configured to: and determining whether the characteristic information of the database is in a file of the database client or in a dynamic database on which the database client depends according to the database type.
Optionally, the updating module is configured to: stripping the plug-in from the database client under the condition that the characteristic information of the database is stored in the file of the database client; upgrading the database client; and reinserting the plug-in into the database client after the database client is upgraded, and updating the characteristic information.
Optionally, the updating module is configured to: monitoring whether the dynamic file is changed or not under the condition that the characteristic information of the database is stored in the dynamic file on which the database client depends; and under the condition that the dynamic file is changed, the characteristic information in the dynamic file is acquired again and updated.
According to the method and the device for obtaining the database traffic, the problem that the database audit is affected due to the fact that the plug-in can not work if the database client is upgraded when the plug-in is used for obtaining the database traffic is solved, and therefore the fact that the plug-in can still capture the database traffic normally after the database client is upgraded is guaranteed, and the normal running of the database audit is guaranteed.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims (10)

1. A method for upgrading a database client, comprising:
determining that a database client needs to be updated, and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the database flow interacted between the database client and a database server, and the database client and the database server are installed on the same server;
the method comprises the steps that under the condition that the plug-in is installed on the database client, the database type corresponding to the database client is obtained;
determining a storage mode of characteristic information of the database according to the type of the database, wherein the characteristic information is used for indicating information used for connecting with the database;
and updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information.
2. The method of claim 1, wherein determining a manner of preserving the characteristic information of the database based on the database type comprises:
and determining whether the characteristic information of the database is in a file of the database client or in a dynamic database on which the database client depends according to the database type.
3. The method of claim 2, wherein updating the database client according to the manner in which the characteristic information is stored comprises:
stripping the plug-in from the database client under the condition that the characteristic information of the database is stored in the file of the database client;
upgrading the database client;
and reinserting the plug-in into the database client after the database client is upgraded, and updating the characteristic information.
4. The method of claim 2, wherein updating the database client according to the manner in which the characteristic information is stored comprises:
monitoring whether the dynamic file is changed or not under the condition that the characteristic information of the database is stored in the dynamic file on which the database client depends;
and under the condition that the dynamic file is changed, the characteristic information in the dynamic file is acquired again and updated.
5. A database client upgrade system, comprising:
the judging module is used for determining that the database client needs to be updated and judging whether a plug-in is installed on the database client, wherein the plug-in is used for acquiring the interactive database flow between the database client and the database server, and the database client and the database server are installed on the same server;
the acquisition module is used for acquiring the database type corresponding to the database client under the condition that the plug-in is installed on the database client;
the determining module is used for determining a storage mode of characteristic information of the database according to the type of the database, wherein the characteristic information is used for indicating information used for connecting with the database;
and the updating module is used for updating the database client according to the storage mode of the characteristic information, wherein the characteristic information is updated in the updating process of the database client, and the plug-in acquires the database flow between the database client and the database server by using the updated characteristic information.
6. The system of claim 5, wherein the determination module is configured to:
and determining whether the characteristic information of the database is in a file of the database client or in a dynamic database on which the database client depends according to the database type.
7. The system of claim 6, wherein the update module is configured to:
stripping the plug-in from the database client under the condition that the characteristic information of the database is stored in the file of the database client;
upgrading the database client;
and reinserting the plug-in into the database client after the database client is upgraded, and updating the characteristic information.
8. The system of claim 6, wherein the update module is configured to:
monitoring whether the dynamic file is changed or not under the condition that the characteristic information of the database is stored in the dynamic file on which the database client depends;
and under the condition that the dynamic file is changed, the characteristic information in the dynamic file is acquired again and updated.
9. An electronic device includes a memory and a processor; wherein the memory is for storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method steps of any of claims 1 to 4.
10. A readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method steps of any of claims 1 to 4.
CN202310827289.3A 2023-07-06 2023-07-06 Database client upgrading method and system Pending CN116679965A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310827289.3A CN116679965A (en) 2023-07-06 2023-07-06 Database client upgrading method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310827289.3A CN116679965A (en) 2023-07-06 2023-07-06 Database client upgrading method and system

Publications (1)

Publication Number Publication Date
CN116679965A true CN116679965A (en) 2023-09-01

Family

ID=87782137

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310827289.3A Pending CN116679965A (en) 2023-07-06 2023-07-06 Database client upgrading method and system

Country Status (1)

Country Link
CN (1) CN116679965A (en)

Similar Documents

Publication Publication Date Title
CN112989330B (en) Container intrusion detection method, device, electronic equipment and storage medium
CN111538719A (en) Data migration method, device, equipment and computer storage medium
EP2577458B1 (en) Distillation and reconstruction of provisioning components
CN112818307A (en) User operation processing method, system, device and computer readable storage medium
CN110659259A (en) Database migration method, server and computer storage medium
CN114021176B (en) SELinux dynamic authorization method and system
CN116827830A (en) Database flow audit processing method and system under multiple database servers
CN114528201A (en) Abnormal code positioning method, device, equipment and medium
CN116841645A (en) Database flow processing method and system for database audit
CN109784051A (en) Protecting information safety method, device and equipment
CN116679965A (en) Database client upgrading method and system
CN114860619B (en) Database audit program regression testing method and device
CN111240794B (en) Container mirror image extraction method and device and container mirror image test method and device
CN109587202B (en) Method, device and system for coprocessing between file verification and data processing
CN114756530B (en) Client information processing method based on bastion machine
US20120084264A1 (en) System for configurable reporting of network data and related method
CN112214800A (en) Log data sorting evidence-storing method, system, equipment and medium based on block chain
CN114021123A (en) Construction method, security check method, device and medium of behavior baseline library
CN116866209A (en) Database traffic filtering method and system based on remote call network address
KR20200071787A (en) Method and system for managing integrated storages of on-premise and cloud
CN114978963B (en) Network system monitoring analysis method and device, electronic equipment and storage medium
CN116225497A (en) Flow plug-in upgrading processing method and device
CN115118640B (en) Database auditing processing method and system in presence of proxy equipment
CN114978963A (en) Network system monitoring analysis method and device, electronic equipment and storage medium
CN109032955B (en) UI automation test method, device, equipment and readable storage medium

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