hi,

Thanks for your reply.

Servicename is already entered in tnsnames.ora file.

Thanks,

vnd

If you try a tnsping does server reply?

If your service name is set in the tnsnames.ora file then there is really only a couple things that could be wrong.  As previously stated, verify that the server replies with tnsping.  If it does, verify that your sqldb parameter in the sm.ini file is set to the service name, and also verify the sqllogin parameter in the sm.ini file is correct.

SM 7 XX is a 32 bits application support 11.1g and not 11.2g, however you can raise a case with HP support for some plugins.

Issue with the db user access. Issue has been resolved after giving resource and connect access to db user on database.

Thanx

Dear Guest,

We have same problem.Two application server look one database and these servers work active.

We have problem when try to work both of them.When One server works normally but other doesn't work at the same time.

When we have problem,this error write at sm.log file. We dont have this problem ,we want connect via ORACLE 10g.But 11g is problem.

Can you give me detail of this problem resolution ?

Many Thanks

Hello there,

today I had the same issue, it took me a while to figure out the problem i had (it was quit simple):

You have to take care that the entries for your host in "tnsnames.ora" AND "listener.ora" file are the same.

That files are stored in your dbhome folder under /network/admin

Best Ben

Hello all,

Here is some additional information about this I wanted to share:

ORA-12154:TNS:could not resolve the connect identifier specified

Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.

Action: - If you are using local naming (TNSNAMES.ORA file):

- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)

- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.

- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.

- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.

- If you are using directory naming:

- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

- Verify that the LDAP directory server is up and that it is accessible.

- Verify that the net service name or database name used as the connect identifier is configured in the directory.

- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier

- If you are using easy connect naming:

- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

- Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.

Regards,

Alex