How to Verify if OID services are Completely Down

Dear All,

We had a situation where in we were asked to rebuild indexes of OID using "bulkload".Within OID all attributes needs to be indexed or attributes which are indexed needs to be rebuild.

Before we start rebuilding activity the OID should be either in 'read-only' mode or 'shutdown'.I have issued 'opmnctl stopall' and all services were shutdown cleanly,but when we ran bulkload we got the message that OID services are still running ,pelase shutdown.

So below are simple steps to check if OID services are shutdown cleanly.

1. First step is to use the normal 'OS command'

ps -ef | grep -i oid ( or ) ps -ef | grep -i <username>

<username> - is the user which you start/stop OID services

2. The next step is to use the 'oidctl' utility

$ oidctl connect=<servicename> status

<service name> - is the name of the DB service.

Eg
===
$ oidctl connect=OIDB status (in my case 'OIDB' is the database name)
NLS_LANG not set in environment
Setting NLS_LANG to AMERICAN_AMERICA.AL32UTF8
oidctl:Checking Oracle Internet Directory Processes ...
Process oidmon is not running ------------------> if any OID process is running,it would give you the PID
Checking OIDLDAPD instance 1 ...
Instance is shutdown ------------------> if any OIDLDAPD process is running,it would give you the PID and ports of dispatcher and server
OIDREPLD instance is not configured
ODISRV instance is not configured



3. The third step is to check the table 'ODS.ODS_PROCESS'

Normally after OID is shutdown there are no entries on these tables.Sometimes if the shutdown is not clear or due to any bugs
there are normally some entries on the table.Use the below query to check

set lines 200
col HOSTNAME format a30
col FLAGS format a20

select instance,PID,SERVERID,FLAGS,HOSTNAME,STATE,RETRYCOUNT,LASTWAKETIME from ods.ods_process;

If the above query returns any values after stopping OID,then it is not a clean shutdown. After ensuring the OID services are down ,truncate the table ODS.ODS_PROCESS.

truncate table ODS.ODS_PROCESS;

So now we have gone through the different ways/methods of how to check if OID services are down before starting any maintenance activities.

Users Receive Blank Screen when logging into EBS in a SSO Integrated System

Hello All,

Last week was such a hectic one with one kind of a peculiar problem not seen before.
Users created after a particular date,logging into Oracle Apps via third party authentication,integrated with OID/SSO were getting blank pages.

On analysis we found that the user_guid column with the 'FND_USER' table was null for these users.
Verified OID the attribute 'orclguid' was there ,but it was not synching with FND_USER table,inspite the profile option 'Applications SSO Auto Link User" (APPS_SSO_AUTO_LINK_USER)' was set to 'ENABLED'
at site level.

I had a very hard feeling that the linking between EBS and OID was broken.To my surprise that was the case .
I dont know how many of you are aware of an user named 'AppsDN'.This "AppsDN" user is a special administration account which eBiz uses to connect
to OID for management and administrative tasks when integrating with OID/SSO.

- Determine the 'AppsDN' username/password connected to EBS as apps user

SQL> select fnd_preference.get('#INTERNAL', 'LDAP_SYNCH','USERNAME') Apps_Instance_OID_Account from dual;

APPS_INSTANCE_OID_ACCOUNT
--------------------------------------------------------------------------------
orclapplicationcommonname=prod,cn=ebusiness,cn=products,cn=oraclecontext,dc=thirdparty,dc=users

SQL> select fnd_preference.eget('#INTERNAL', 'LDAP_SYNCH','EPWD','LDAP_PWD') Apps_Password from dual;

APPS_PASSWORD
--------------------------------------------------------------------------------
1applin


- Test the username/password.Use the following command on your node where OID is running to confirm if the password works or not

'ldapbind -D 'Apps Instance OID Account' -w 'Apps Password' -h 'OIDserver' -p 'OIDport' '

Eg:-
===
ldapbind -D orclapplicationcommonname=prod,cn=ebusiness,cn=products,cn=oraclecontext,dc=thirdparty,dc=users -w 1applin -h server11 -p 389


- On executing the above ldapbind command you should recieve 'Bind Successful'.In my case it was returning 'Password Policy Error :9000: GSL_PWDEXPIRED_EXCP :Your Password has expired'

- Navigate through the "Entry Management" tree to the appropriate context (the reversed path of the orclApplcationCommonName)
Follow the below steps to set the password in OID

1) Launch oidadmin console
2) Login as user ‘orcladmin’
3) Select and expand ‘Entry Management’
4) Select and expand ‘dc=users’
5) Select and expand ‘dc=thirdparty’ under ‘dc=users’
6) Select and expand ‘cn=OracleContext’ under ‘dc=thirdparty’
7) Select and expand ‘cn=Products’
8) Select and expand ‘cn=EBusiness’
9) Select orclApplicationCommonName=PROD
10) Under the Properties tab update the 'userpassword' attribute with the password from SQL Query in my case '1applin'
11) Click on ‘Apply’

- Then bounce the OID components.

- Now we requested the users to login into Oracle Apps and they no longer get the blank screen and OID was synching up the guid to FND_USER table.