My version is 17.1.717.3711
After I followed the instructions, the status still couldn't change to 'green pass'.
The database status in Instance Manager seems to conflict with the fact that I can successfully establish a connection by TNS.
We use
- TNSPing for listener status
- If this fails we mark all with an X and do not move on.
- If this passes we mark Listener with a green check and move on
- Ping for node status
- if this fails we mark Node and Database with an X and do not move on
- if this passes we mark Node with a green check and move on
- A connection attempt for the "Database" and "version" columns.
- You must have connection info filled in on the "Connection" column (or an active connection already to that DB
It's possible that PING is blocked on your server, but you are still able to connect. That would explain this.
Thank you so much for your explanation.
It helped me understand a bit more. 
In my environment, all Oracle components are installed on the same machine.
TNSPing is working fine.
However, there’s something weird.
I can successfully Ping the hostname or 127.0.0.1 from the command prompt, but TOAD still marks Node and Database with an X .
This doesn’t match the ping results.
OK, here is the problem.
When we ping a remote server, we get a result like this:
We look for "=32" in the result, and if we find it, we know that the ping was successful. We cannot look for the word "Reply" because that only works when the user's local language is English.
When pinging localhost, the result looks like this:
As you can see, there is no "bytes=32" in the result when pinging localhost. This is why it fails.
Do you really want to use this feature with localhost or are you just testing? If just testing, please try it with your actual remote servers instead of localhost.
Having said all of this, I don't think we should stop if ping fails, so I will make a change to this effect. I will also make a change to handle localhost better.
Thank you for your detailed explanation.
I now understand how Toad is working with localhost.
At the beginning, I’ve tried connecting to a remote host, but the servers listed in Toad seem different from those on the remote host.
I suspect that Toad displays services from my localhost instead.
Just this environment happens to have everything installed on the same machine, I decided to observe how Toad interacts with localhost first.
As shown in the screenshot, when I switch to a remote connection, the services listed in Instance Manager differ from those in the TNS file on the remote host.
If possible, I’d appreciate it if you could provide some guidance on how to use this feature, as there seems to be very limited documentation available.
I'm also curious about what the question mark indicates?
The grid only lists connections which are in your TNSNames.ora file (or LDAP).
It does not list direct connections from the login window. You don't have to make connections first before testing them in instance manager. The idea for instance manager is that shows all of your databases (from tnsnames/ldap) and tells you if they are running or not.
The question mark means "test not performed"
The X means failed
The green check means passed.
If you look in your TNSNames.ora, I think you'll find that ORA_CLR_CONNECTION_DATA does not have host info, so we didn't ping it or attempt a connection.
If you want to test all of your connections in the login window, including the direct connections, you can do so like this:
- select the connections that you want to test
- click "Test Selected Login Records"
- This window appears and connection test begins automatically
Thank you for taking the time to explain everything in detail.
It really helped me better understand how it works.
For me, observing through the TNS tab in the login window feels easier to use.
I’m very glad to have the opportunity to interact with experts like you in the TOAD Forum in real-time. 