The oracle catalog mode is abnormal or the metadata synchronization of the FE node is abnormal #49071
Unanswered
koooolllll
asked this question in
A - General / Q&A
Replies: 1 comment 1 reply
-
This issue appears to have been fixed, and it is recommended that you upgrade to apache doris version 2.1.8. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The oracle catalog mode is abnormal or the metadata synchronization of the FE node is abnormal
Machine environment: 3 * FE + 3 * BE,
Database version: doris-2.0.11,
Description: When linking Oracle using the catalog method, the following situation occurred: The FE of the master node and one of the slave nodes have no issues and can be used normally, but the other slave node cannot use the created catalog.
And it will prompt the following content:
And I'm pretty sure there's nothing abnormal between the master node and the other slave node!
The catalog creation statement used is as follows:
View the log information of the abnormal FE node as follows:
I also checked the metadata version of each FE node and found that there was no difference between them.
This is information from a normal FE node
This is information from an abnormal FE node
This is the information about a normal FE master node
Next, I checked the version of the jdbc driver in the FE node server. Of course, in order to ensure that the jdbc driver is not different, I also uploaded a new jdbc driver.
However, I found other anomalies in the "warn" log of the FE node in question, I am not sure if it is related to this.
Below is the warn log for this node:
fe.warn.log
Beta Was this translation helpful? Give feedback.
All reactions