Showing results for 
Search instead for 
Did you mean: 

Oracle 10

Steve Waugh
Frequent Advisor

Oracle 10

Hi there,

Getting the following error message when setting up backup config for DP & SAP R/3 integration.

"ORA-12154" - SP2_0640 & that the TNS Lstner is not running.

The errors details says to run a tnsping of SID.

I run that and it connect.

I've noticed that Data Protector is using & that the tnsnames.ora files have the the host listed as just server.

Should these two match and is this is what is causing the error?

Honored Contributor

Re: Oracle 10


so adapt your tnsnames.ora ( with

and have a look at the sqlnet.ora ( file for this line.


hope this helps

Steve Waugh
Frequent Advisor

Re: Oracle 10

Is that what would be causing the error? The difference in the hostname
Honored Contributor

Re: Oracle 10


ORA-12154: TNS:could not resolve service name

Cause: Oracle Net could not locate the net service name specified in the
tnsnames.ora configuration file.

Action: Perform these steps:

1)Verify that a tnsnames.ora file exists.

2) Verify that there are not multiple copies of the tnsnames.ora file.

3) In the tnsnames.ora file, verify that the net service name specified in your connect string is mapped to a connect descriptor.

4) Verify that there are no duplicate copies of the sqlnet.ora file.

5) If you are using domain names, verify that your sqlnet.ora file contains a NAMES.DEFAULT_DOMAIN parameter. If this parameter does not exist, you must specify the domain name in your connect string.

6)If you are not using domain names, and this parameter exists, delete it or disable it by commenting it out.

7)If you are connecting from a login dialog box, verify that you are not placing an "@" symbol before your connect net service name.

8)Activate client tracing and repeat the operation.

Problem never ends, you must know how to fix it
Rita C Workman
Honored Contributor

Re: Oracle 10

Your tnsname file can reflect JUST the server name, provided that is being used as an alias or entry in DNS, so the clients can resolve to the same place as the FQDN.

Check how you resolve in both HPUX and DNS (if it's on another platform)
Do full dns resolve lookups.
nslookup IP
nslookup server

Repeat above and add for DNS:

If your 'server' was set up as the alias in DNS then you should be able to resolve using just the server.

...very possible if DNS is run from somewhere else than HPUX, then you may find when they never bothered to put in the alias (server name).
A habit they forget here, till they are reminded..

Just a thought,