Home » RDBMS Server » Security » Audit Vault Collectors (Oracle Audit Vault 10.2.3.2 & Linux Red Hat 5 on a V.M. box)
Audit Vault Collectors [message #486112] Mon, 13 December 2010 12:22 Go to next message
stevejbr
Messages: 2
Registered: December 2010
Location: Massachusetts
Junior Member
Oracle Audit Vault 10.2.3.2 & Linux Red Hat 5 on a V.M. box

I'm new to the Audit Vault and am experiencing some issues. Right now my biggest question is how does A.V. deal with TNS issues (allowing the collectors to find remote target db's) when we do not add any tns entries to the local tnsnames file?

We've recently added more space and our sysadmins have moved all of our AV data to the new disk space and have supposedly updated pointers allowing us to continue seamlessly. However now my collectors won't start, they are complaining with message below. These had started previously before the space add.

==============================================================
Dec 13, 2010 11:44:35 AM Thread-10 FINEST: resp.getData:<?xml version='1.0' encoding='UTF-8'?>
<auditException errKey="av.auditservice.DAO_INITIALIZATION_FAILED.9" ><nestedException message="ORA-12154: TNS:could not resolve the connect identifier specified " exceptionClass="java.sql.SQLException"/></auditException>

===============================================================

Thanks for any insight you may provide.
Steve
Re: Audit Vault Collectors [message #486113 is a reply to message #486112] Mon, 13 December 2010 13:29 Go to previous messageGo to next message
BlackSwan
Messages: 21955
Registered: January 2009
Senior Member
>ORA-12154
this error means one thing & one thing only.
error occurs when tns_alias in connection string is NOT found in tnsnames.ora file.
so 2 variables come into play
1) tns_alias in connection string
2) which actual tnsnames.ora file was searched.
The connection request failed on client & DB server is 100% not relevant to this error.
Re: Audit Vault Collectors [message #486438 is a reply to message #486113] Wed, 15 December 2010 09:31 Go to previous messageGo to next message
stevejbr
Messages: 2
Registered: December 2010
Location: Massachusetts
Junior Member
Thanks Blackswan for you input

I do see all of the tns aliases that (I presume) the audit vault add source process creates for you. Both the audit vault server and audit vault agents are installed on the same box in seperate oracle homes, and both homes have tnsnames files with the full set of tns aliases. So this may not be the issue.

Thanks
Steve
Re: Audit Vault Collectors [message #486440 is a reply to message #486438] Wed, 15 December 2010 09:37 Go to previous message
BlackSwan
Messages: 21955
Registered: January 2009
Senior Member
>So this may not be the issue.
so you say.
Oracle is too dumb to lie about this error.
12154, 00000, "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.


ENJOY your mystery
Previous Topic: SYS/SYSDBA is special
Next Topic: User Locked
Goto Forum:
  


Current Time: Sun Apr 20 19:41:13 CDT 2014

Total time taken to generate the page: 0.08314 seconds