Database Validation Failed When Creating OAM Database Instance for Audit to Oracle RDBMS
Last updated on MARCH 08, 2017
Applies to:COREid Access - Version: 10.1.4.2 to 10.1.4.3.0 - Release: 10g to
Information in this document applies to any platform.
Creation of RDBMS Directory Profile for Auditing to RDBMS in the Oracle Access Manager (OAM) Access System Console fails.
The Create Database Instance screen fails to save the connection details entered and displays the following error in red:
Database Validation Failed.
The following have been verified:
- TNS_ADMIN environment variable is set to the directory where the tnsnames.ora file is located, when Identity Server and Access Server are started.
- The sqlnet.ora file does not exist in the TNS_ADMIN location. If it does exist there, it has TNSNAMES listed first in the NAMES.DIRECTORY_PATH setting.
- The TNS alias that is specified for the directory profile Global Database Name has been verified to be valid for connection to the database, by copying the tnsnames.ora entry for that alias to another machine where SQLPlus exists and testing successful connection using the following:
Steps to reproduce
1. Login to Access System Console as OAM Administrator and go to System Configuration -> Server Settings.
2. In the Configure RDBMS Profiles section click the Add button
3. Enter a Name for the profile, check the OCI radio button and the User By: Auditing and Reporting checkboxes
4. Click the Add button to add a Database Instance
5. In the resulting Create Database Instance page enter:
Global Database Name: TNS_ALIAS_NAME
User Name: DB_USERNAME
Leave other values at defaults.
6. Click Save: the page is re-displayed with the following error in red font: Database Validation Failed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms