When password is changed in Fusion and you change it in DBeaver connection settings, somehow it does not recognize it

[sjurecic-osir-erpis]

I had to change password in Fusion, so I made sure to update it immediately and properly in DBeaver connection settings as well. Then I opened new SQL script window and ran some query and I kept getting authentication failed. Even after closing DBeaver and reopening it, it didn't work.

In the end, I removed the driver, and added it again. Then it start to work.

[krokozyab]

The Root Cause: "Safety Lock" (Circuit Breaker)
The driver includes a protection mechanism called a Circuit Breaker. Its job is to prevent your computer from spamming the Oracle server with bad requests (like a
wrong password), which could get your account locked out on the server side.

1. The Trigger: When you tried to connect with the old password, the driver recorded 5 consecutive failures (the default threshold).
2. The Lockout: Once this threshold was reached, the driver "tripped the breaker" and entered a Safety Mode.
3. The Effect: In this mode, the driver automatically blocks all connection attempts for 60 seconds, regardless of whether the password is now correct. It stops the
   request locally on your machine to let the server "cool down."

Why "Closing and Reopening" Didn't Work
The Circuit Breaker's state (Locked vs. Unlocked) is stored in your application's memory (RAM).

• Application Persistence: DBeaver often keep their internal engine running in the background even if you close a
  specific window or disconnect a session.
• The Memory: Because the application process didn't completely terminate (or was restarted very quickly), the driver stayed loaded in memory, preserving the
  "Locked" state. When you reconnected, you were simply reconnecting to the same blocked driver instance.

Why "Removing and Adding" the Driver Worked
When you deleted the driver from the settings and added it back, you performed a "Hot Reload":

1. The application was forced to unload the old driver code from memory. This destroyed the "Locked" Circuit Breaker.
2. It loaded a fresh copy of the driver. This created a brand new Circuit Breaker in the "Unlocked" (Clean) state.
3. With the fresh state, the driver allowed your request to pass through with the new password.

Summary & Solution
You were temporarily blocked by a local safety feature

For next time:

• Wait: Simply wait 60 seconds. The driver will automatically reset itself.
• Force Reset: You can add ?resetCircuitBreaker=true to your JDBC URL connection string to manually force the lock to open.

[sjurecic-osir-erpis]

Thank you, will try that.