Configuring OID and logging into a database with a OID username\password

Question

I've installed the Oracle database software (v9.2.0.2.1) and created a database called OIDDB. I then installed the "Management and Integration" portion of the Oracle database software which includes "Oracle Management Server" and "Oracle Internet Directory". All of this installation is on the same database box.
On another server, my other database (called: BAHDB) resides that I OID enabled. I've already used the "Database Configuration Assistant" to register it with the directory service.
What else needs to be done at this point to log into the database without a Oracle username and password? What high level main steps am I missing? Do I need to do anything with Oracle wallets?

Answer 1

There's now a difference when you use domains in your network configuration:
tnsping server.at.your.domain should get resolved through tnsnames.
tnsping server shoudl get resolved through the LDAP server.
The illegal userid/password error makes me suspect you try to logon with the fully qualified server name; LDAP should respond with something like "no nickname found".
Also - the guest user is only used as a "stub" - you should be able to login with a name, defined in OID - not defined in the database!
Things to check:
- rdbms_server_dn - DBCA should take care of it during registration of the database in OID, but it does not always do that. Setting it requires a restart. Remeember, it is case sensitive! Format is cn=SID,cn=OracleContext,dc=<your realm here>
- Wallet. Was it created, what is in it?
- User mapping (Use the Enterprise Security Manager - part of the client install); open Realms, open OracleDefaultDomain within Enterprise Domains, third tab ("Database Schema Mapping"), select "Add".
Navigate to cn=Users,dc=<your realm>. Make sure Subtree level is selected, and use your globally identified user (you used guest) for schema; click OK.
Click Apply
You should now be able to logon as any user, defined in the OID under cn=Users,dc=<your realm> - orcladmin should do.
when logged on, show user will respond with "guest"; use select sys_context('userenv','external_name') from dual; to find out the real user.
The way you now set it up probably will fail to login with 'user lacks create session privilege' - for test purposes, grant create session to guest - in a 'normal' eenviroment, you would use enterprise roles, and assign these to the OID defined users, not directly to the "stub user" (guest in your example)