Oracle test problem
Oracle test problem
Hello,
I'm trying to check an oracle base in Oracle 9i release, the test give me the following error :
Oracle error #12154 : ORA-12154:TNS:Could not resolve service name
HM version 8.14, oracle client is installed, oci.dll is ok, tnsnames.ora is ok, tnsping is ok.
During I create/edit test:
When I enter dbname, user and pass correctly and press Test button - nothing happens - no errors, no success messages
When I enter user or pass incorrectly and press Test button I get ORA-01017 - invalid username/password, logon denied
When I enter dbmane incorrectly I get ORA-12154
I tried to enter TNS alias as dbname.domain.ru, that case I also get ORA-12154
When I finally save correct parameters (a set when nothing happens after pressing Test) and run test I get ORA-12154 in "Reply" column and No answer in Status
Could you give me some ideas to fix it?
ODBC Test is not applicable in our case.
Thanks
I'm trying to check an oracle base in Oracle 9i release, the test give me the following error :
Oracle error #12154 : ORA-12154:TNS:Could not resolve service name
HM version 8.14, oracle client is installed, oci.dll is ok, tnsnames.ora is ok, tnsping is ok.
During I create/edit test:
When I enter dbname, user and pass correctly and press Test button - nothing happens - no errors, no success messages
When I enter user or pass incorrectly and press Test button I get ORA-01017 - invalid username/password, logon denied
When I enter dbmane incorrectly I get ORA-12154
I tried to enter TNS alias as dbname.domain.ru, that case I also get ORA-12154
When I finally save correct parameters (a set when nothing happens after pressing Test) and run test I get ORA-12154 in "Reply" column and No answer in Status
Could you give me some ideas to fix it?
ODBC Test is not applicable in our case.
Thanks
Hostmonitor is running as a service on remote machine, so I'd connected and ran test using RMAKS-Soft wrote:Do you perform test directly by HostMonitor or you are using Remote Monitoring Agent (RMA)?
Unfortunately it's impossible due to company's security policyKS-Soft wrote:Can we connect to your server from our site?
Not sure I understand
"Test" button is displayed by HostMonitor (or RCC) GUI. If you click this button and you do not see any error, this means HostMonitor (or RCC) is able to connect to the server.
If you are working with HostMonitors GUI directly, setup the test to be performed by HostMonitor. Test probe should work because "Test" button works. I assume there is some firewall/router restrictions that do not allow connections from system where RMA is running.
If you are managing HostMonitor GUI using RCC (Remote Control Console) installed on some other system (e.g. systemA - oracle server, systemB - HostMonitor, systemC - RCC) and "Test" button does not show any error while test probe shows error, this means RCC (installed on systemC) is able to connect to Oracle server while HostMonitor (installed on systemB) cannot connect to Oracle. I assume there is some firewall/router restrictions that do not allow connections from system where HostMonitor is running.
You should use RMA when HostMonitor cannot connect to some host located in remote network protected by firewall. In your case it looks like HostMonitor may connect without problems so why do you want to use RMA?
Regards
Alex

"Test" button is displayed by HostMonitor (or RCC) GUI. If you click this button and you do not see any error, this means HostMonitor (or RCC) is able to connect to the server.
If you are working with HostMonitors GUI directly, setup the test to be performed by HostMonitor. Test probe should work because "Test" button works. I assume there is some firewall/router restrictions that do not allow connections from system where RMA is running.
If you are managing HostMonitor GUI using RCC (Remote Control Console) installed on some other system (e.g. systemA - oracle server, systemB - HostMonitor, systemC - RCC) and "Test" button does not show any error while test probe shows error, this means RCC (installed on systemC) is able to connect to Oracle server while HostMonitor (installed on systemB) cannot connect to Oracle. I assume there is some firewall/router restrictions that do not allow connections from system where HostMonitor is running.
You should use RMA when HostMonitor cannot connect to some host located in remote network protected by firewall. In your case it looks like HostMonitor may connect without problems so why do you want to use RMA?
Regards
Alex
sorry-sorry-sorry I'd mistaken - of course I told about RCC, not RMAKS-Soft wrote:You should use RMA when HostMonitor cannot connect to some host located in remote network protected by firewall. In your case it looks like HostMonitor may connect without problems so why do you want to use RMA?
RMA is not used
That exactly what is happening, I've discovered that yesterday.KS-Soft wrote:this means RCC (installed on systemC) is able to connect to Oracle server while HostMonitor (installed on systemB) cannot connect to Oracle.
on systemC "Test" button works (via RCC)
on systemB neither "Test" button nor test probe works
But sqlplus connection to Oracle is still available from systemB (HM machine). Tnsping is also ok.
Do environment variables settings involve on work of HM? Maybe that is teh reason. Or maybe I did something wrong while installing Oracle client?
Probably not. Environment variables may point to necessary DLLs however HostMonitor would show different error if it could not load Oracle client library.Do environment variables settings involve on work of HM?
I assume HostMonitor is started as service? Could you try to start it as application using the same account you are using for tnsping?
Regards
Alex
We checked Oracle manuals, there are various reasons for this error but none of them can explain why tnsping started on the same system under the same account works fine.
Yes, it could be mistake in our code or mistake in test settings but this theory does not explain why RCC that uses exactly the same code and the same test settings is able to connect to the server
I am lost
Regards
Alex
Yes, it could be mistake in our code or mistake in test settings but this theory does not explain why RCC that uses exactly the same code and the same test settings is able to connect to the server
I am lost

Regards
Alex