Hello everyone!!
I am trying to Onboard JDBC source. My VA cluster is up and running, but “VA Cluster Unavailable” error is popping up.
Please help me to resolve this error.
This is my VA Cluster:
This is My JDBC Source:
Hello Narendra,
You can try to follow the steps mentioned in this thread.
I can able to select VA Cluster, but ISC is still showing "VA Cluster Unavailable"
Hello Narendra,
Can you try running Test Connection on the JDBC source once?
I experienced something similar with my AD source. The VA and source configuration looked correct, but ISC was still showing VA Cluster Unavailable. After I ran Test Connection, the VA error cleared and the cluster showed Healthy again.
If your source configuration is already complete, it may be worth trying the same.
Hi @punna0001
tried, its throwing this error.
Status changed from “VA Cluster Unavailale” to “Not Responding”
Hello Narendra. From your latest screenshot, I do not think the VA cluster is the current issue. Your VA shows Connected, and the JDBC Test Connection is reaching the database. The actual error is:
Access denied for user 'root'@'192.168.0.106' (using password: YES)
This indicates the connection is reaching MySQL, but MySQL is rejecting the configured account.
I would verify the JDBC username and password, and confirm that the MySQL user is allowed to connect from the host/IP shown in the error rather than being restricted to localhost. MySQL accounts are matched by both username and client host, so there needs to be an account definition that allows connections from 192.168.0.106. MySQL
Preferably use a dedicated database service account with the required permissions instead of root. After correcting the database access, run Test Connection again. I have also seen cases where the source status showed unavailable even though the VA configuration was correct, and running Test Connection refreshed the status.
SailPoint lists Test Connection as part of validating and troubleshooting source connectivity: Managing Sources Overview. I would not delete and recreate the VA cluster yet, since your test is already reaching the target database.
Hi @narendrachintu As per this error, your issue is not with Virtual Appliance connection Issue is with the user of the DB with which you are trying to connect. I would suggest, verify the username and password of the DB.